Repository navigation
Conversation
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
concurrency groups instead of head_ref.concurrency groups instead of head_ref.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
…head_ref`. The current standard across all GitHub Actions workflows is to configure `concurrency` to use the `github.head_ref` value in the `group` name for a given PR. Because `head_ref` only includes the branch name, workflow runs can be inadvertantly cancelled when two PRs are open from different forks with identical branch names. This switches to using the `github.event.pull_request.number` instead of `github.head_ref` to ensure that runs are properly grouped only with runs from the same pull request. A similar change has been made to `props-bot.yml`, which can be triggered by an `issue_comment` event. In this case, the `github.event.issue.number` will be used. In the context of GitHub, `issues == pull_requests` for the data returned by a number of request types. Merges [65249] to the 6.9 branch. Props lancewillett. See #65845.
833250f to
aab66f1
Compare
Backports r65249 to the
6.9branch.Switches GitHub Actions
concurrencygroups fromgithub.head_ref(branch name only) togithub.event.pull_request.number, so workflow runs from PRs opened from different forks with identical branch names no longer cancel each other.props-bot.ymlusesgithub.event.pull_request.number || github.event.issue.numberto also coverissue_commentevents.All files in this branch that use
head_refin aconcurrencygroup were updated. Some of them (such ascheck-built-files.yml) do not exist intrunk.Trac ticket: https://core.trac.wordpress.org/ticket/65845
Use of AI Tools
Claude Code (Claude Opus 5.5) applied the trunk change to each branch with scripted substitutions and opened this PR. Each diff was checked to contain only the expected concurrency group and comment changes.
🤖 Generated with Claude Code