feat: add concurrency group to prevent parallel deployments#159
Merged
Conversation
Ensures only one deployment runs at a time. If a new push arrives while a deployment is in progress, it queues instead of cancelling the running deployment (cancel-in-progress: false).
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the production deployment GitHub Actions workflow to serialize deployments so only one production deploy can run at a time, preventing overlapping deploys to the same environment.
Changes:
- Add a workflow-level
concurrencygroup for production deployments. - Configure
cancel-in-progress: falseto queue deploys rather than cancel in-flight runs.
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.
Summary
concurrencygroup to the deploy workflow so that only one deployment runs at a timecancel-in-progress: falseso a running deployment finishes before the next one starts (queuing behavior, not cancellation)