Feature request: Project badges #2708

New Issue

GiteaMirror · 2025-11-02T04:45:10-06:00

GiteaMirror commented

2025-11-02 04:45:10 -06:00

Originally created by @ntimo on GitHub (Jan 4, 2019).

Description

It would be super nice if you could add bagdes to a project like the way you can add them in Gitlab this would enable repository maintainers to clearly show the status of their pipelines or code coverage reports without having to out the into the readme.md. The badges should addable via the repo settings with a link_url and a image_url setting.

Screenshots

Example from GitLab:

Originally created by @ntimo on GitHub (Jan 4, 2019). ## Description It would be super nice if you could add bagdes to a project like the way you can add them in Gitlab this would enable repository maintainers to clearly show the status of their pipelines or code coverage reports without having to out the into the readme.md. The badges should addable via the repo settings with a link_url and a image_url setting. ## Screenshots Example from GitLab: ![gitlab-project-badges](https://user-images.githubusercontent.com/6145026/50697075-801fd800-1041-11e9-934e-ccfab9b1b03a.png)

GiteaMirror added the type/feature type/proposal labels 2025-11-02 04:45:10 -06:00

GiteaMirror commented

2025-11-02 04:45:10 -06:00

@StevenPolley commented on GitHub (Jan 6, 2019):

I haven't used gitlab but aren't these badges typically a part of the CICD system and not the version control system?

@StevenPolley commented on GitHub (Jan 6, 2019): I haven't used gitlab but aren't these badges typically a part of the CICD system and not the version control system?

GiteaMirror commented

2025-11-02 04:45:10 -06:00

@ntimo commented on GitHub (Jan 6, 2019):

Kind of yes, but you can also use them to display your code coverage report from SonarQube for example :)

@ntimo commented on GitHub (Jan 6, 2019): Kind of yes, but you can also use them to display your code coverage report from SonarQube for example :)

GiteaMirror commented

2025-11-02 04:45:11 -06:00

@strk commented on GitHub (Jan 19, 2022):

It would be great to be able to finally STOP polluting the README.md with all the non-human-readable crap

@strk commented on GitHub (Jan 19, 2022): It would be great to be able to finally STOP polluting the README.md with all the non-human-readable crap

GiteaMirror commented

2025-11-02 04:45:11 -06:00

@lunny commented on GitHub (Jan 20, 2022):

But you can preview the README badges when you clone it locally.

@lunny commented on GitHub (Jan 20, 2022): But you can preview the README badges when you clone it locally.

GiteaMirror commented

2025-11-02 04:45:11 -06:00

@wxiaoguang commented on GitHub (Jan 20, 2022):

What about putting the badges in the repository description? Then render these images in Markdown.

@wxiaoguang commented on GitHub (Jan 20, 2022): What about putting the badges in the repository description? Then render these images in Markdown.

GiteaMirror commented

2025-11-02 04:45:11 -06:00

@strk commented on GitHub (Jan 20, 2022):

But you can preview the README badges when you clone it locally.

Do people actually tend to open README.md files with tools capable of rendering the images in them ?
Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption!

Badges in repository description I guess would be a possible workaround, but proper space for badges sounds even better to me, given the widespread use of badges.

@strk commented on GitHub (Jan 20, 2022): > But you can preview the README badges when you clone it locally. Do people actually tend to open README.md files with tools capable of rendering the images in them ? Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption! Badges in repository description I guess would be a possible workaround, but proper space for badges sounds even better to me, given the widespread use of badges.

GiteaMirror commented

2025-11-02 04:45:11 -06:00

@strk commented on GitHub (Jan 24, 2022):

I just experienced that the GitLab way of doing this has the limit of NOT allowing people to send pull-requests to add badges, so while I still think that it is nice to have an ad-hoc space for rendering the badges, it would be also good for the badges information to be in a file in the repository, like .badges.yml or something. That way different mirrors might eventually end up rendering the same badges too

@strk commented on GitHub (Jan 24, 2022): I just experienced that the GitLab way of doing this has the limit of NOT allowing people to send pull-requests to add badges, so while I still think that it is nice to have an ad-hoc space for rendering the badges, it would be also good for the badges information to be in a file in the repository, like .badges.yml or something. That way different mirrors *might* eventually end up rendering the same badges too

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@strk commented on GitHub (Jan 24, 2022):

Or .badges.md if people really do render the markdown-with-images locally.
Or .header.md to be rendered before README.md, to be more generic and less intrusive in the life of text-only console-based reading of README files ?

@strk commented on GitHub (Jan 24, 2022): Or .badges.md if people really do *render* the markdown-with-images locally. Or .header.md to be rendered *before* README.md, to be more generic and less intrusive in the life of text-only console-based reading of README files ?

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@lafriks commented on GitHub (Jan 25, 2022):

.yaml could be better option imho, also would be nice to allow way for badges to pass branch/tag name in image url, so that it would be possible to link to specific version/branch docs/build status etc

@lafriks commented on GitHub (Jan 25, 2022): .yaml could be better option imho, also would be nice to allow way for badges to pass branch/tag name in image url, so that it would be possible to link to specific version/branch docs/build status etc

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@belliash commented on GitHub (Jun 7, 2023):

Gitea gained actions (CI/CD) feature. Can this be implemented now as a part of Gitea Actions?

@belliash commented on GitHub (Jun 7, 2023): Gitea gained actions (CI/CD) feature. Can this be implemented now as a part of Gitea Actions?

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@lunny commented on GitHub (Jun 8, 2023):

Gitea gained actions (CI/CD) feature. Can this be implemented now as a part of Gitea Actions?

I think they are different features.

@lunny commented on GitHub (Jun 8, 2023): > Gitea gained actions (CI/CD) feature. Can this be implemented now as a part of Gitea Actions? I think they are different features.

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@senare commented on GitHub (Sep 25, 2023):

Yes, please don't bundle this with Gitea Actions !

I think use case is bigger and not all of use use Gitea Actions ...

@senare commented on GitHub (Sep 25, 2023): Yes, please don't bundle this with Gitea Actions ! I think use case is bigger and not all of use use Gitea Actions ...

GiteaMirror commented

2025-11-02 04:45:12 -06:00

@robe2 commented on GitHub (Nov 7, 2023):

But you can preview the README badges when you clone it locally.

Do people actually tend to open README.md files with tools capable of rendering the images in them ? Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption!

I do yes. VS Code can preview markdown and see the badges. But to be honest, only reason I preview is when I edit.

@robe2 commented on GitHub (Nov 7, 2023): > > But you can preview the README badges when you clone it locally. > > Do people actually tend to open README.md files with tools capable of rendering the images in them ? Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption! > I do yes. VS Code can preview markdown and see the badges. But to be honest, only reason I preview is when I edit.

GiteaMirror referenced this issue

2025-11-02 12:13:12 -06:00

[PR #2708] [MERGED] fix .netrc authentication (#2700) #16549

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2708