Incorrect status is shown on commit detail #2414

New Issue

2025-11-02T04:35:12-06:00

GiteaMirror commented

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

Originally created by @filipnavara on GitHub (Oct 18, 2018).

Gitea version (or commit ref): dd62ca7
Git version: 2.8
Operating system: Windows
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (https://try.gitea.io/filipnavara/test/pulls/1/commits)
- No
- Not relevant
Log gist:

Description

The commit status displayed on the Commits tab on Pull Request is correctly the status reported for the particular commit. When the commit detail is open though the status displayed is taken for the HEAD or master branch, not for the correct commit.

Screenshots

Originally created by @filipnavara on GitHub (Oct 18, 2018).  - Gitea version (or commit ref): dd62ca7 - Git version: 2.8 - Operating system: Windows - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/filipnavara/test/pulls/1/commits) - [ ] No - [ ] Not relevant - Log gist: ## Description The commit status displayed on the Commits tab on Pull Request is correctly the status reported for the particular commit. When the commit detail is open though the status displayed is taken for the HEAD or master branch, not for the correct commit. ## Screenshots ![image](https://user-images.githubusercontent.com/1764393/47148803-03971c00-d2d2-11e8-8215-05ef6f0f8c2e.png) ![image](https://user-images.githubusercontent.com/1764393/47148821-13166500-d2d2-11e8-878a-4cea7a8f1939.png)

GiteaMirror added the type/bug label 2025-11-02 04:35:12 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

2025-11-02 04:35:13 -06:00

@ollien commented on GitHub (Oct 23, 2018):

Hi,

I'm interested in taking a crack at fixing this. I know this sounds silly, but how are you enabling commit status to begin with? I've scoured for the answer and having a bit of trouble.

@ollien commented on GitHub (Oct 23, 2018): Hi, I'm interested in taking a crack at fixing this. I know this sounds silly, but how are you enabling commit status to begin with? I've scoured for the answer and having a bit of trouble.

GiteaMirror commented

2025-11-02 04:35:13 -06:00

@filipnavara commented on GitHub (Oct 23, 2018):

Gitea implements the same API for statuses as GitHub: https://developer.github.com/v3/repos/statuses/

I created the example above by manually calling the API endpoint through Fiddler. There's a Golong API binding for the statuses at https://github.com/go-gitea/go-sdk.

@filipnavara commented on GitHub (Oct 23, 2018): Gitea implements the same API for statuses as GitHub: https://developer.github.com/v3/repos/statuses/ I created the example above by manually calling the API endpoint through Fiddler. There's a Golong API binding for the statuses at https://github.com/go-gitea/go-sdk.

GiteaMirror commented

2025-11-02 04:35:13 -06:00

@stale[bot] commented on GitHub (Jan 6, 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 (Jan 6, 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 04:35:13 -06:00