Skip to content

6.9 Branch: Build/Test Tools: Use PR number for concurrency groups instead of head_ref. - #15570

Open
desrosj wants to merge 1 commit into
WordPress:6.9from
desrosj:backport/65249-6.9
Open

desrosj wants to merge 1 commit into
WordPress:6.9from
desrosj:backport/65249-6.9

Conversation

@desrosj

@desrosj desrosj commented Nov 5, 2026

Copy link
Copy Markdown
Member

Backports r65249 to the 6.9 branch.

Switches GitHub Actions concurrency groups from github.head_ref (branch name only) to github.event.pull_request.number, so workflow runs from PRs opened from different forks with identical branch names no longer cancel each other. props-bot.yml uses github.event.pull_request.number || github.event.issue.number to also cover issue_comment events.

All files in this branch that use head_ref in a concurrency group were updated. Some of them (such as check-built-files.yml) do not exist in trunk.

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

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The 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

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@desrosj desrosj changed the title [6.9] Build/Test Tools: Use PR number for concurrency groups instead of head_ref. 6.9 Branch: Build/Test Tools: Use PR number for concurrency groups instead of head_ref. Nov 5, 2026
@desrosj
desrosj marked this pull request as ready for review November 5, 2026 22:37
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

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:

Props desrosj.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@desrosj
desrosj requested a review from a team November 6, 2026 00:49
@desrosj desrosj self-assigned this Nov 6, 2026
@desrosj desrosj moved this from Backlog to In review in WordPress Project Build Tooling Nov 6, 2026
…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.
@desrosj
desrosj force-pushed the backport/65249-6.9 branch from 833250f to aab66f1 Compare November 6, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

1 participant