diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-06-18 20:43:03 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-06-20 09:22:48 +0200 |
| commit | 09ddb1a8a0f94409ae121116b5d4b0f9a02915c0 (patch) | |
| tree | c1d9651908a66a3b310d3581e5f0a17e53d483f6 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 9422f30e470dbb9d1925306fc36a674475894ee1 (diff) | |
workflows: sync merge commits
This fixes a problem where each workflow would get their own merge
commit. This happens frequently when the target branch is merged into a
the same time, different workflows in the same run will run
get-merge-commit at different times and thus have different merge
commits.
Since the jobs don't really depend on each other, this doesn't cause
practical problems, yet. But it has already led to strange CI failures
in a still unmerged PR, which can be prevented from happening with this
clean approach.
And yes, this saves a few API calls on every run.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions