diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-07-12 16:33:28 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-07-12 16:33:33 +0200 |
| commit | 58a3001a3a1220882a95dd97f8d4032270c33a3f (patch) | |
| tree | 58af7da5fec71e7062d759cc93f63872ca61ae16 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 7d5dcd00b884edfc95187a7f10409b1275e376bc (diff) | |
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.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions