Status checks don't show up in the pull request overview #10325

New Issue

GiteaMirror · 2025-11-02T09:04:22-06:00

GiteaMirror commented

2025-11-02 09:04:22 -06:00

Originally created by @dcermak on GitHub (Feb 22, 2023).

Description

I am adding status checks to a repository via the API and have managed for these status checks to show up in the commit overview as a green check mark or red cross. I then proceeded to enable branch protection on the repository with status checks being required. Then I opened a pull request against the protected branch, but the status checks don't show up like they for instance do on the Gadgetbridge repository.

Repository without status checks showing up in the PR overview: https://gitea.opensuse.org/rpm/skopeo/pulls

Screenshots

Gitea Version

1.18.3

Can you reproduce the bug on the Gitea demo site?

No

Operating System

No response

Browser Version

Firefox 110, Chromium Version 110.0.5481.100

Originally created by @dcermak on GitHub (Feb 22, 2023). ### Description I am adding status checks to a repository via the API and have managed for these status checks to show up in the commit overview as a green check mark or red cross. I then proceeded to enable branch protection on the repository with status checks being required. Then I opened a pull request against the protected branch, but the status checks don't show up like they for instance do on the [Gadgetbridge](https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls) repository. Repository without status checks showing up in the PR overview: https://gitea.opensuse.org/rpm/skopeo/pulls ### Screenshots ![image](https://user-images.githubusercontent.com/45594031/220662594-dd44a040-5f94-4604-95ee-e4ed5af134e2.png) ### Gitea Version 1.18.3 ### Can you reproduce the bug on the Gitea demo site? No ### Operating System _No response_ ### Browser Version Firefox 110, Chromium Version 110.0.5481.100

GiteaMirror added the type/docs topic/ui labels 2025-11-02 09:04:22 -06:00

GiteaMirror closed this issue

2025-11-02 09:04:22 -06:00

GiteaMirror commented

2025-11-02 09:04:22 -06:00

@oliverpool commented on GitHub (Feb 23, 2023):

Looking at the commits of https://gitea.opensuse.org/rpm/skopeo/pulls/3/commits, they appear to have no status.

I think the PR page shows the status (if any) of the latest commit of the branch.

Can you try adding a commit status to the following commit 9baf124726 ?

@oliverpool commented on GitHub (Feb 23, 2023): Looking at the commits of https://gitea.opensuse.org/rpm/skopeo/pulls/3/commits, they appear to have no status. I think the PR page shows the status (if any) of the latest commit of the branch. Can you try adding a commit status to the following commit https://gitea.opensuse.org/rpm/skopeo/commit/9baf12472696b216f41caf78f5e65851098ed721 ?

GiteaMirror commented

2025-11-02 09:04:23 -06:00

@dcermak commented on GitHub (Feb 23, 2023):

I have added the statuses to the fork: https://gitea.opensuse.org/defolos/skopeo/commits/branch/factory. So they have to be explicitly added to the main repo?

@dcermak commented on GitHub (Feb 23, 2023): I have added the statuses to the fork: https://gitea.opensuse.org/defolos/skopeo/commits/branch/factory. So they have to be explicitly added to the main repo?

GiteaMirror commented

2025-11-02 09:04:23 -06:00

@oliverpool commented on GitHub (Feb 23, 2023):

Ah yes, the commit status must be added to the main repo (they are attached to a commit hash+repo id).

@oliverpool commented on GitHub (Feb 23, 2023): Ah yes, the commit status must be added to the main repo (they are attached to a `commit hash`+`repo id`).

GiteaMirror commented

2025-11-02 09:04:23 -06:00

@dcermak commented on GitHub (Feb 27, 2023):

Ah you're of course correct. Now it works, thanks a lot!

I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend api-usage.en-us.md or create a new document in that folder?

@dcermak commented on GitHub (Feb 27, 2023): Ah you're of course correct. Now it works, thanks a lot! I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend [api-usage.en-us.md](https://github.com/go-gitea/gitea/blob/d27d36f2f4dd389050e613967ad2a5d02d250acc/docs/content/doc/developers/api-usage.en-us.md) or create a new document in that folder?

GiteaMirror commented

2025-11-02 09:04:23 -06:00

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

Ah you're of course correct. Now it works, thanks a lot!

I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend api-usage.en-us.md or create a new document in that folder?

Please send a PR to improve the documentation. Sorry for late reply.

@lunny commented on GitHub (Jun 14, 2023): > Ah you're of course correct. Now it works, thanks a lot! > > I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend [api-usage.en-us.md](https://github.com/go-gitea/gitea/blob/d27d36f2f4dd389050e613967ad2a5d02d250acc/docs/content/doc/developers/api-usage.en-us.md) or create a new document in that folder? Please send a PR to improve the documentation. Sorry for late reply.

GiteaMirror commented

2025-11-02 09:04:23 -06:00

@dcermak commented on GitHub (Jun 14, 2023):

Lunny Xiao @.***> writes:

Ah you're of course correct. Now it works, thanks a lot!

I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend api-usage.en-us.md or create a new document in that folder?

Please send a PR to improve the documentation. Sorry for late reply.

The question was where to send it. I am unsure what the correct place is.

@dcermak commented on GitHub (Jun 14, 2023): Lunny Xiao ***@***.***> writes: >> Ah you're of course correct. Now it works, thanks a lot! >> >> I think this would be worth documenting. Where could/should I submit a short guide about this? I could extend [api-usage.en-us.md](https://github.com/go-gitea/gitea/blob/d27d36f2f4dd389050e613967ad2a5d02d250acc/docs/content/doc/developers/api-usage.en-us.md) or create a new document in that folder? > > Please send a PR to improve the documentation. Sorry for late reply. The question was where to send it. I am unsure what the correct place is.

GiteaMirror commented

2025-11-02 09:04:24 -06:00

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

Maybe here https://github.com/go-gitea/gitea/blob/main/docs/content/doc/development/integrations.en-us.md

@lunny commented on GitHub (Jun 14, 2023): Maybe here https://github.com/go-gitea/gitea/blob/main/docs/content/doc/development/integrations.en-us.md

GiteaMirror commented

2025-11-02 09:04:24 -06:00

@lunny commented on GitHub (Jul 27, 2023):

I think this has been resolved and please feel free to reopen it.

@lunny commented on GitHub (Jul 27, 2023): I think this has been resolved and please feel free to reopen it.

Sign in to join this conversation.