Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect status is shown on commit detail #5103

Closed
2 of 7 tasks
filipnavara opened this issue Oct 18, 2018 · 6 comments
Closed
2 of 7 tasks

Incorrect status is shown on commit detail #5103

filipnavara opened this issue Oct 18, 2018 · 6 comments
Labels

Comments

@filipnavara
Copy link
Contributor

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

image

@lunny lunny added the type/bug label Oct 18, 2018
@ollien
Copy link

ollien commented 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.

@filipnavara
Copy link
Contributor Author

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.

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 6, 2019
@filipnavara
Copy link
Contributor Author

It is not stale issue, still a very real bug.

@filipnavara
Copy link
Contributor Author

Looks like similar issue as #5649, a PR was submitted for that one.

@stale stale bot removed the issue/stale label Jan 6, 2019
@filipnavara
Copy link
Contributor Author

Fixed via #5650

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants