Skip to content

MINOR: Use per-PR concurrency group in Dev PR workflow - #1320

Open
jbonofre wants to merge 1 commit into
apache:mainfrom
jbonofre:dev-pr-concurrency-per-pr
Open

jbonofre wants to merge 1 commit into
apache:mainfrom
jbonofre:dev-pr-concurrency-per-pr

Conversation

@jbonofre

@jbonofre jbonofre commented Oct 3, 2026

Copy link
Copy Markdown
Member

What's Changed

The Dev PR workflow runs on pull_request_target, where github.ref is the base branch (refs/heads/main), not the PR ref. Its concurrency group therefore resolved to apache/arrow-java-refs/heads/main-Dev PR for every PR, and with cancel-in-progress: true a new run on one PR cancelled the run in progress on another.

This leaves a cancelled "Ensure PR format" check on the losing PR, which shows up as a failure. For example on #1295 the job was cancelled with:

Canceling since a higher priority waiting request for apache/arrow-java-refs/heads/main-Dev PR exists

This change keys the concurrency group on the PR number, so runs are only cancelled by newer runs of the same PR.

Note that pull_request_target uses the workflow from the base branch, so this only takes effect once merged.

The Dev PR workflow runs on pull_request_target, where github.ref is the
base branch rather than the PR ref. All PRs therefore shared a single
concurrency group, and with cancel-in-progress any new run cancelled the
run in progress on another PR, leaving a cancelled "Ensure PR format"
check behind. Key the group on the PR number instead.
@jbonofre jbonofre added the chore PRs that make misc changes. label Oct 3, 2026
@jbonofre
jbonofre requested a review from kou as a code owner October 3, 2026 13:02
@github-actions github-actions Bot added this to the 20.0.0 milestone Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore PRs that make misc changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant