workflows/backport: fix concurrent jobs cancelling each other

When a PR is merged and labeled afterwards - with a non-backport label -
the following will happen:
- The first backport job is triggered on the merge.
- The second backport job is triggered on the label event.
- The second job will cancel the first one due to the concurrency group.
- The second job will cancel itself because the label event didn't
contain a backport label.

Both jobs end up cancelled and no backport happens.

We made the backport action idempotent upstream a while ago, so we don't
need to cancel those actions. Instead, we'll run all of them -
subsequent actions running through will just stay silent anyway.
This commit is contained in:
Wolfgang Walther 2025-07-12 16:33:28 +02:00
parent 7d5dcd00b8
commit 58a3001a3a
No known key found for this signature in database
GPG Key ID: B39893FA5F65CAE1

View File

@ -9,10 +9,6 @@ on:
pull_request_target:
types: [closed, labeled]
concurrency:
group: backport-${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || github.run_id }}
cancel-in-progress: true
permissions:
contents: read
issues: write