Conversation
Include event_name in concurrency group so push-triggered deploys and delete-triggered cleanups run independently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jmarek41
approved these changes
Feb 23, 2026
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.
Summary
The
deploy-docsworkflow uses a single concurrency group based ongithub.ref. When a branch is merged and then deleted, both thepush(deploy) anddelete(cleanup-preview) events resolve torefs/heads/main, causing the deploy job to be cancelled by the cleanup job.Adding
github.event_nameto the concurrency group key ensures both jobs run independently.Changes
github.event_namein the concurrency group:deploy-docs-${{ github.event_name }}-${{ github.ref }}