GitHub Community
Old checks still appearing in PR checks after being removed #139960
-
Select Topic AreaQuestion BodyI am experiencing an issue with one of my repositories where checks that were previously removed are still showing up in the Pull Request (PR) discussions. This is preventing the merge process from completing, as the old checks remain listed as required even though they should no longer be relevant. Here are the steps I followed:
Despite these changes, the removed checks still appear in the PR discussions and are marked as failing, blocking the merge. Thank you for your assistance and guidance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
cool, thanks @lovrozagar. its as you said, the check is still listed as required in the branch protection settings. |
Beta Was this translation helpful? Give feedback.
-
|
is there any way to forcibly remove specific status checks or just reset the cache, we had a lambda function incorrectly publishing a timestamp into the status check so one of our repos has 100s of status checks that are in pending state and never complete... just looks botched. |
Beta Was this translation helpful? Give feedback.
Hi @pararang,
It sounds like GitHub is still referencing the old checks you’ve removed. This can happen occasionally, but there are a few things you can try to fix it.
First, head to your repository settings and check the Branch Protection Rules. Sometimes, even after removing a check from your workflow files, it might still be listed as required in the branch protection settings. If you see the old checks there, you’ll need to remove them.
If that doesn’t help, you could try re-running the workflows on the pull request. There’s usually a button in the PR checks section that says "Re-run jobs." That can sometimes force GitHub to refresh the status checks.
Another thing to try is pushing a…