xinux/settings
Watch
15
0
Fork
You've already forked settings
 2
Code Issues 30 Pull requests 8 Projects Releases Wiki Activity Actions

fix(readme): new forgejo domain link #51

Merged
bahrom04 merged 3 commits from bahrom04-patch-1 into main 2026-08-01 08:40:00 +00:00
Conversation 13 Commits 3 Files changed 1 +2 -2
bahrom04 commented 2026-07-23 12:53:43 +00:00
Owner
Copy link
No description provided.
fix(readme): new forgejo domain link
Some checks failed
Test CI / flake-check (push) Has been cancelled
Details
Test CI / build (push) Has been cancelled
Details
Test CI / flake-check (pull_request) Has been cancelled
Details
Test CI / build (pull_request) Has been cancelled
Details
d3466fbd06
akmal approved these changes 2026-07-23 15:38:09 +00:00
akmal commented 2026-07-23 15:39:08 +00:00
Member
Copy link

Fixes: #45

Fixes: #45
bahrom04 commented 2026-07-23 17:09:08 +00:00
Author
Owner
Copy link

@akmal wrote in #51 (comment):

Fixes: #45

Not yet fixed. Dunno how to fix :(
image

@akmal wrote in https://git.oss.uzinfocom.uz/xinux/settings/pulls/51#issuecomment-3333: > Fixes: #45 Not yet fixed. Dunno how to fix :( ![image](/attachments/7cb7c9f6-7d29-4c32-9f8b-fd709b4ec9b1)
image.png
7.7 KiB
akmal commented 2026-07-24 21:52:43 +00:00
Member
Copy link

Good news.

I found several badges from forgejo documentations, we can use some of them. Such as:

Test CI

It just shows waiting because the last test workflow is on wait. More about badges, maybe we can add more good looking ones too:

https://forgejo.org/docs/latest/user/repository/readme-badges/

TL;DR:

The badges are returned in SVG format and are available under the https://forgejo.example.com/{username}/{repository}/badges path. Forgejo currently supports generating the following badges:

  • /release.svg: The latest release made in the repository.
  • /stars.svg: The number of stars the repository has.
  • /issues.svg: The total number of issues in the repository, open and closed combined.
  • /issues/open.svg: The number of open issues.
  • /issues/closed.svg: The number of closed issues.
  • /pulls.svg: The number of pull requests against the repository, open and closed combined.
  • /pulls/open.svg: The number of open pull requests.
  • /pulls/closed.svg: The number of closed pull requests.
  • /workflows/{workflow_file}/badge.svg: The status of the {workflow_file} workflow. Additional restrictions can be given for this badge by using the branch and/or event query parameters. The branch query parameter will display the status of the workflow from the given branch (defaulting to the repository’s main branch if not explicitly specified), while the event parameter will only display results if a run was triggered by the specified event.
Good news. I found several badges from forgejo documentations, we can use some of them. Such as: <a href="https://github.com/xinux-org/settings/actions/workflows/test.yml"><img align="center" src="https://git.oss.uzinfocom.uz/xinux/settings/badges/workflows/test.yml/badge.svg?logo=forgejo" alt="Test CI"></a> It just shows waiting because the last test workflow is on wait. More about badges, maybe we can add more good looking ones too: https://forgejo.org/docs/latest/user/repository/readme-badges/ TL;DR: The badges are returned in SVG format and are available under the https://forgejo.example.com/{username}/{repository}/badges path. Forgejo currently supports generating the following badges: - `/release.svg`: The latest release made in the repository. - `/stars.svg`: The number of stars the repository has. - `/issues.svg`: The total number of issues in the repository, open and closed combined. - `/issues/open.svg`: The number of open issues. - `/issues/closed.svg`: The number of closed issues. - `/pulls.svg`: The number of pull requests against the repository, open and closed combined. - `/pulls/open.svg`: The number of open pull requests. - `/pulls/closed.svg`: The number of closed pull requests. - `/workflows/{workflow_file}/badge.svg`: The status of the `{workflow_file}` workflow. Additional restrictions can be given for this badge by using the branch and/or event query parameters. The branch query parameter will display the status of the workflow from the given branch (defaulting to the repository’s main branch if not explicitly specified), while the event parameter will only display results if a run was triggered by the specified event.
akmal commented 2026-07-24 22:15:53 +00:00
Member
Copy link

You can ignore the previous message, I guess I found what I needed.

Test CI




The link is: https://img.shields.io/badge/Rust-95%25-blue?logo=Rust. But the problem is that it is hardcoded, I'm thinking about building a small app for constructing this URL.

We have a Forgejo API and it's swagger is at https://git.oss.uzinfocom.uz/api/swagger

curl -X 'GET' \
        'https://git.oss.uzinfocom.uz/api/v1/repos/xinux/settings/languages' \
        -H 'accept: application/json' | jq

{
  "Rust": 420308,
  "CSS": 47584,
  "Meson": 7153,
  "Nix": 3437,
  "Just": 1389
}

It returns the bytes, so we can do some math:

420308(Rust) / 420308 + 47584 + 7153 + 3437 + 1389 (All Combined) = 0.87587705862 = 87%

You can ignore the previous message, I guess I found what I needed. <a href="https://github.com/xinux-org/settings/actions/workflows/test.yml"><img align="center" src="https://git.oss.uzinfocom.uz/xinux/settings/badges/workflows/test.yml/badge.svg?logo=forgejo" alt="Test CI"></a> <img src="https://img.shields.io/badge/Rust-95%25-blue?logo=Rust"> <br><br> The link is: `https://img.shields.io/badge/Rust-95%25-blue?logo=Rust`. But the problem is that it is hardcoded, I'm thinking about building a small app for constructing this URL. We have a Forgejo API and it's swagger is at https://git.oss.uzinfocom.uz/api/swagger ```shell curl -X 'GET' \ 'https://git.oss.uzinfocom.uz/api/v1/repos/xinux/settings/languages' \ -H 'accept: application/json' | jq ``` ```json { "Rust": 420308, "CSS": 47584, "Meson": 7153, "Nix": 3437, "Just": 1389 } ``` It returns the bytes, so we can do some math: 420308(Rust) / 420308 + 47584 + 7153 + 3437 + 1389 (All Combined) = 0.87587705862 = 87%
👍 2
akmal self-assigned this 2026-07-25 05:01:13 +00:00
chore: fix badges
Some checks failed
Test CI / flake-check (push) Has been cancelled
Details
Test CI / build (push) Has been cancelled
Details
Test CI / flake-check (pull_request) Has been cancelled
Details
Test CI / build (pull_request) Has been cancelled
Details
e079746a86
akmal commented 2026-07-25 20:49:35 +00:00
Member
Copy link

Now it fixes: #45

Now it fixes: #45
bahrom04 reviewed 2026-07-26 05:32:37 +00:00
README.md Outdated
@ -10,2 +10,2 @@
<img align="center" src="https://img.shields.io/github/languages/top/xinux-org/settings?style=flat&logo=rust&logoColor=5277C3&labelColor=ffffff&color=ffffff" alt="Top Used Language">
<a href="https://github.com/xinux-org/settings/actions/workflows/test.yml"><img align="center" src="https://img.shields.io/github/actions/workflow/status/xinux-org/settings/test.yml?style=flat&logo=github&logoColor=5277C3&labelColor=ffffff&color=ffffff" alt="Test CI"></a>
<a href="https://git.oss.uzinfocom.uz/xinux/settings/actions?workflow=test.yml"><img align="center" src="https://git.oss.uzinfocom.uz/xinux/settings/badges/workflows/test.yml/badge.svg?logo=forgejo" alt="Test CI"></a>
<img src="https://badge.ae5259.deno.net/?instance=git.oss.uzinfocom.uz&owner=xinux&repo=settings" align="center" alt="Most used Language">
bahrom04 commented 2026-07-26 05:32:34 +00:00
Author
Owner
Copy link

badge.ae5259.deno.net why your username?

badge.ae5259.deno.net why your username?
bahrom04 commented 2026-07-26 05:33:55 +00:00
Author
Owner
Copy link

you created small app right as you mentioned previous comment? Can you share source code?

you created small app right as you mentioned previous comment? Can you share source code?
akmal commented 2026-07-26 14:29:33 +00:00
Member
Copy link

@bahrom04 wrote in #51 (comment):

badge.ae5259.deno.net why your username?

Deno Deploy used my old username because I signed up using that username. I linked https://badges.aelloc.uz too. We can change links to it. I was just wondering maybe we should use the one Deno Deploy generated for us, in case my domain name dies xD

@bahrom04 wrote in https://git.oss.uzinfocom.uz/xinux/settings/pulls/51#issuecomment-3382: > badge.ae5259.deno.net why your username? Deno Deploy used my old username because I signed up using that username. I linked https://badges.aelloc.uz too. We can change links to it. I was just wondering maybe we should use the one Deno Deploy generated for us, in case my domain name dies xD
akmal commented 2026-07-26 14:29:49 +00:00
Member
Copy link

@bahrom04 wrote in #51 (comment):

you created small app right as you mentioned previous comment? Can you share source code?

Yeah, https://github.com/aelloc/badges

@bahrom04 wrote in https://git.oss.uzinfocom.uz/xinux/settings/pulls/51#issuecomment-3384: > you created small app right as you mentioned previous comment? Can you share source code? Yeah, https://github.com/aelloc/badges
akmal changed title from fix(readme): new forgejo domain link to WIP: fix(readme): new forgejo domain link 2026-07-27 15:41:03 +00:00
bahrom04 reviewed 2026-07-27 16:15:52 +00:00
bahrom04 left a comment
Copy link

Ready to merge after those issues: #1 and #2 issues

https://github.com/aelloc/badges/issues

Ready to merge after those issues: #1 and #2 issues https://github.com/aelloc/badges/issues
akmal changed title from WIP: fix(readme): new forgejo domain link to fix(readme): new forgejo domain link 2026-07-27 17:41:05 +00:00
bahrom04 commented 2026-07-28 17:58:53 +00:00
Author
Owner
Copy link

@akmal what have been changed so far?

@akmal what have been changed so far?
bahrom04 reviewed 2026-07-28 17:59:34 +00:00
bahrom04 left a comment
Copy link

No logo?

image

No logo? ![image](/attachments/30c5d974-2ea7-4827-b893-af993423b1e1)
image.png
8.6 KiB
fix: domain link
Some checks failed
Test CI / flake-check (push) Has been cancelled
Details
Test CI / build (push) Has been cancelled
Details
Test CI / flake-check (pull_request) Has been cancelled
Details
Test CI / build (pull_request) Has been cancelled
Details
d0d4c877be
akmal commented 2026-07-29 04:49:22 +00:00
Member
Copy link

There was a problem with the link, I fixed it. However, unfortunately, I couldn't get to close those 2 issues you have filed in GitHub yet, I'll let you know once I do.

There was a problem with the link, I fixed it. However, unfortunately, I couldn't get to close those 2 issues you have filed in GitHub yet, I'll let you know once I do.
👀 1
akmal commented 2026-07-31 19:02:20 +00:00
Member
Copy link

@bahrom04 wrote in #51 (comment):

Ready to merge after those issues: #1 and #2 issues

https://github.com/aelloc/badges/issues

Can you check those issues? I have some updates on them.

@bahrom04 wrote in https://git.oss.uzinfocom.uz/xinux/settings/pulls/51#issuecomment-3419: > Ready to merge after those issues: #1 and #2 issues > > https://github.com/aelloc/badges/issues Can you check those issues? I have some updates on them.
bahrom04 commented 2026-08-01 08:39:45 +00:00
Author
Owner
Copy link

LGTM!

LGTM!
❤️ 1
bahrom04 deleted branch bahrom04-patch-1 2026-08-01 08:40:00 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
akmal
Labels
Clear labels
  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
fix
fixing good

  
good first issue

   
gui
Gui related

  
nix
Nix config related issue

  
planned
planned on the future

  
question
More information is needed

  
refactor
not affecting to logic

  
security
Security related issue

No labels
bug
duplicate
enhancement
fix
good first issue
gui
nix
planned
question
refactor
security
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
akmal
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
xinux/settings!51
No description provided.