Move WP refresh concurrency group to workflow level#3380
Merged
brandonpayton merged 2 commits intotrunkfrom Mar 12, 2026
Merged
Move WP refresh concurrency group to workflow level#3380brandonpayton merged 2 commits intotrunkfrom
brandonpayton merged 2 commits intotrunkfrom
Conversation
The job-level concurrency guard was not preventing concurrent runs. Evidence: run 23010346814 started at 11:39am and ran for 40 minutes, while run 23011564322 started 27 minutes later at 12:06pm and ran concurrently. Moving the concurrency group to the workflow level ensures GitHub Actions queues workflow runs before any jobs start. Also adds a 2-hour timeout to prevent indefinitely stuck runs.
Contributor
There was a problem hiding this comment.
Pull request overview
Moves GitHub Actions concurrency control for the “Refresh WordPress Major&Beta” workflow from a single job to the workflow level, and adds a job timeout to avoid stuck runs.
Changes:
- Add workflow-level
concurrencyto serialize entire workflow runs - Remove job-level
concurrency - Add
timeout-minutes: 120to the workflow job
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bgrgicak
pushed a commit
that referenced
this pull request
Mar 27, 2026
## Summary - Moves the `concurrency` group from job-level to workflow-level in the "Refresh WordPress Major&Beta" workflow - Adds a `timeout-minutes: 120` to prevent indefinitely stuck runs ## Motivation The job-level concurrency guard was not preventing concurrent workflow runs. Evidence: - [Run 23010346814](https://github.com/WordPress/wordpress-playground/actions/runs/23010346814) started at 11:39am and ran for ~40 minutes - [Run 23011564322](https://github.com/WordPress/wordpress-playground/actions/runs/23011564322) started 27 minutes later at 12:06pm and ran concurrently By moving the concurrency group to the workflow level, GitHub Actions will queue pending runs before any jobs start, ensuring only one instance runs at a time. ## Test plan - [x] Verify the workflow YAML is valid - [ ] Confirm only one workflow run executes at a time after merging (observable via next scheduled trigger)
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 from job-level to workflow-level in the "Refresh WordPress Major&Beta" workflowtimeout-minutes: 120to prevent indefinitely stuck runsMotivation
The job-level concurrency guard was not preventing concurrent workflow runs. Evidence:
By moving the concurrency group to the workflow level, GitHub Actions will queue pending runs before any jobs start, ensuring only one instance runs at a time.
Test plan