Display multiple commit statuses #3880

New Issue

GiteaMirror · 2025-11-02T05:29:23-06:00

GiteaMirror commented

2025-11-02 05:29:23 -06:00

Originally created by @trinity-1686a on GitHub (Sep 2, 2019).

Gitea version (or commit ref): 1.10.0+dev-232-gf1c414882
Operating system: linux (docker)
Database (use [x]):
- PostgreSQL (other untested)
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (https://try.gitea.io/fdb-hiroshima/test)
- No
- Not relevant

Description

On the web interface, Gitea try to show the most relevant status for a given commit, prioritizing failed check over successful ones. But it only shows one check, there is no easy way to see other status in case of multiple failure. Having some menu showing on hover/click as Github is doing would be nice to see more about statuses.

Screenshot

how Github handle multiple statuses :

Originally created by @trinity-1686a on GitHub (Sep 2, 2019). - Gitea version (or commit ref): 1.10.0+dev-232-gf1c414882 - Operating system: linux (docker) - Database (use `[x]`): - [x] PostgreSQL (other untested) - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/fdb-hiroshima/test) - [ ] No - [ ] Not relevant ## Description On the web interface, Gitea try to show the most relevant status for a given commit, prioritizing failed check over successful ones. But it only shows one check, there is no easy way to see other status in case of multiple failure. Having some menu showing on hover/click as Github is doing would be nice to see more about statuses. ## Screenshot how Github handle multiple statuses : <img width="946" alt="how Github shows multiple statuses" src="https://user-images.githubusercontent.com/35889323/64107032-d16f9b00-cd79-11e9-96e9-7dc82419a618.png">

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 05:29:23 -06:00

GiteaMirror closed this issue

2025-11-02 05:29:23 -06:00

GiteaMirror commented

2025-11-02 05:29:24 -06:00

@stale[bot] commented on GitHub (Nov 1, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 1, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:29:24 -06:00

@PenguinOwl commented on GitHub (May 19, 2020):

Hate to necro, but this would be nice.
In addition to this, IMO the commit statuses in the commit list should be displayed to the right of the sha instead of at the end of the commit message. Putting it after the text causes variable placement and makes it hard to get a good idea of the build success trend.

@PenguinOwl commented on GitHub (May 19, 2020): Hate to necro, but this would be nice. In addition to this, IMO the commit statuses in the commit list should be displayed to the right of the sha instead of at the end of the commit message. Putting it after the text causes variable placement and makes it hard to get a good idea of the build success trend.

GiteaMirror commented

2025-11-02 05:29:24 -06:00

@Ibmurai commented on GitHub (Jul 13, 2020):

This is even more needed now that we can attach different kinds of statuses to the commits.
As an example I am linking to the build artifacts using a status. This works fine when there's a PR involved since that will show all the different commit statuses. But if there is no PR the link is never shown :(

@Ibmurai commented on GitHub (Jul 13, 2020): This is even more needed now that we can attach different kinds of statuses to the commits. As an example I am linking to the build artifacts using a status. This works fine when there's a PR involved since that will show all the different commit statuses. But if there is no PR the link is never shown :(

GiteaMirror commented

2025-11-02 05:29:25 -06:00

@cal101 commented on GitHub (Jan 5, 2021):

+1
I came here by searching for a way to link build artifacts.

@cal101 commented on GitHub (Jan 5, 2021): +1 I came here by searching for a way to link build artifacts.

GiteaMirror commented

2025-11-02 05:29:25 -06:00

@jpraet commented on GitHub (Jan 13, 2021):

I think this is fixed by #13977?

@jpraet commented on GitHub (Jan 13, 2021): I think this is fixed by #13977?

GiteaMirror referenced this issue

2025-11-02 05:46:19 -06:00