Christian Byrne 5cba1e3f88 fix: prevent duplicate backport workflow runs for same PR (#7335) ...

## Summary

When multiple labels are added to a PR in quick succession (e.g.,
`needs-backport` and `core/1.33`), each label triggers a separate
workflow run. Both runs would proceed independently, causing duplicate
failure comments or redundant work. This adds a concurrency group keyed
by PR number with `cancel-in-progress: false`, ensuring runs for the
same PR are serialized rather than racing.

┆Issue is synchronized with this [Notion
page](https://www.notion.so/PR-7335-fix-prevent-duplicate-backport-workflow-runs-for-same-PR-2c66d73d36508140a603cd7110c42442)
by [Unito](https://www.unito.io)

2025-12-11 03:01:54 -07:00

..

actions

fix: npm link in release notification comment (#6683)

2025-11-13 11:25:23 -07:00

ISSUE_TEMPLATE

ci: add yamllint (#6682)

2025-11-13 11:10:48 -07:00

workflows

fix: prevent duplicate backport workflow runs for same PR (#7335)

2025-12-11 03:01:54 -07:00

CLAUDE.md

[feat] Add GitHub Action for automated Claude PR reviews (#4452)

2025-07-14 16:44:51 -07:00

copilot-instructions.md

[refactor] Replace lodash with es-toolkit (#4935)

2025-08-12 12:22:09 -07:00

pull_request_template.md

[feat] Add PR creation automation command (#4892)

2025-08-10 19:53:35 -04:00