Say what actually restarts the checks after a refresh - #77
Merged
Conversation
The workflow told you to re-run the pull request's checks. There is nothing to re-run: a push made with GITHUB_TOKEN does not create a workflow run at all, so the required checks simply have no result against the new head and the PR sits BLOCKED with everything apparently green. Found by using it. Healthie.NET#62 stayed blocked with `build` and `End-to-end (browser)` absent rather than failing, and only an empty commit from a human identity started them. LakeWright.NET#75 behaved the same way, except there the held run could be approved instead. The message now gives both commands that work, and says why the obvious one does not.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The workflow told you to re-run the pull request's checks. There is nothing to re-run.
A push made with
GITHUB_TOKENdoes not create a workflow run at all, so after the refresh the required checks have no result against the new head — the PR sitsBLOCKEDwith everything that did run showing green, which reads like a mystery rather than a missing step.Found by using it on a real bump:
buildandEnd-to-end (browser)absent rather than failing. Only an empty commit from a human identity started them.action_requiredand could be approved instead.The closing message now gives both commands that work, and says why the obvious one does not.