Concurrency for community-label.yml causing failed workflow runs #47179
Labels
focus: monorepo infrastructure
Issues and PRs related to monorepo tooling.
priority: high
The issue/PR is high priority—it affects lots of customers substantially, but not critically.
team: Vortex
WooCommerce monorepo tools and test suite.
type: bug
The issue is a confirmed bug.
Prerequisites
Describe the bug
Some of the workflow runs for community-label.yml are failing.
https://github.com/woocommerce/woocommerce/actions/workflows/community-label.yml?query=is%3Acancelled
They fail with error
Canceling since a higher priority waiting request for 'Add Community Label, Assign Reviewers-refs/heads/trunk' exists
The workflow currently has this concurrency step
The
github.ref
is always returningtrunk
instead of the branch name so it appears like the workflow is already running when multiple are triggered at the same time. Perhaps usegithub.head_ref
instead https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-pull_request_target-workflow-based-on-the-head-or-base-branch-of-a-pull-requestExpected behavior
All runs pass
Actual behavior
Some runs fail if there is another run in progress at the same time.
https://github.com/woocommerce/woocommerce/actions/workflows/community-label.yml?query=is%3Acancelled
Steps to reproduce
Go to https://github.com/woocommerce/woocommerce/actions/workflows/community-label.yml
See some runs are cancelled due to error
WordPress Environment
n/a
Isolating the problem
The text was updated successfully, but these errors were encountered: