Serialize workflow runs per PR#47
Open
Phlogistique wants to merge 2 commits into
Open
Conversation
Two runs can act on the same PR concurrently: the push that finishes a conflict resolution fires a synchronize event while the conflict label is still attached, so the follow-up run races the one that triggered it (the label is its gate and only comes off at the end). A per-PR concurrency group queues the follow-up instead; cancel-in-progress stays off so a running update is never killed mid-mutation. The group is keyed by PR number rather than repo-wide because GitHub keeps only the newest pending run in a group - a repo-wide group could silently drop the update for one merge when several land in quick succession. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01JHvKryT4QUpHYdNq9YEQxX
A run waiting on its concurrency-group slot reports status "pending", which the wait loop treated as fatal instead of sleeping. Surfaced as soon as the per-PR concurrency group queued a merge-triggered run behind a still-running synchronize run. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01JHvKryT4QUpHYdNq9YEQxX
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
2 participants
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.
Two runs can act on the same PR concurrently: the push that finishes a conflict resolution fires a
synchronizeevent while the conflict label is still attached (the label is the gate and only comes off at the end), so the follow-up run races the one that triggered it. A per-PR concurrency group queues the follow-up instead;cancel-in-progress: falseso a running update is never killed mid-mutation.The group is keyed by PR number rather than repo-wide on purpose: GitHub keeps only the newest pending run per group, so a repo-wide group could silently drop the stack update for one merge when several land in quick succession.
Also added to both README example workflows.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JHvKryT4QUpHYdNq9YEQxX
Generated by Claude Code