Repository navigation
README: a caller's required job must never skip on a draft - #252
Merged
Merged
Conversation
… required check counts as passed)
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
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.
One paragraph under Draft PRs. pacc-trac's own
fastjob skips on drafts withif:. On 2026-11-16 a push to a draft and ready for review landed in the same second: the push's run (its payload still said draft) cancelled the ready run in the same concurrency group, so only the skip remained. GitHub counts a skipped required job as passed, so the PR showed mergeable with nothing run. The callables here already report a failure on drafts and read the live draft state (#243); this states the rule for callers' own jobs. Docs only.