diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-05-23 13:47:14 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-05-23 23:06:20 +0200 |
| commit | e48d9d6174e77293235dd2f4e878f7214d0d8612 (patch) | |
| tree | 66d62b2ed7f7572db923731b90d3968ef5b602f9 /pkgs/development/python-modules/python-openstackclient | |
| parent | c77cfb9239e1aad89f668e0599f076761d7771ad (diff) | |
workflows/get-merge-commit: move to composite action
We don't need a separate workflow anymore, because we don't need to skip
dependent jobs on failures anymore. The biggest failure mode was
"conflict" previously, but we resolved that on the last commit. The
remaining failure modes are so rare, that it's OK to just fail the jobs
in this case instead of marking them as "skipped". Especially, because
the resolve-merge-commit job would have previously failed anyway.
By moving this to an action we avoid running separate jobs each time we
need the merge commit. This also makes the check list in PRs much
cleaner.
Diffstat (limited to 'pkgs/development/python-modules/python-openstackclient')
0 files changed, 0 insertions, 0 deletions