Improve provider target workflow reruns#1112
Merged
Merged
Conversation
This was referenced Jun 2, 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
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.
Summary
GITHUB_RUN_IDandGITHUB_RUN_ATTEMPTin provider-target operation idempotency keys so intentional reruns with different reasons do not collideContext
During Phase Two provider-target backfill, the grouped apply rerun hit an idempotency-key collision on the already-seeded
discord-blue/prodproof lane because the request reason differed. Rapid single-lane dispatches also showed that unrelated routes should not share a global workflow concurrency group.Verification
actionlint -config-file .github/actionlint.yaml .github/workflows/provider-target-operations.ymlyamllint .github/workflows/provider-target-operations.ymlprettier --check .github/workflows/provider-target-operations.yml