diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-10-18 00:20:49 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-10-18 11:29:36 +0200 |
| commit | 402b41c1257ffc7cb88f2876b5fa20ab3ffe4f95 (patch) | |
| tree | cfb4e96e51f9d71bcbf7e6688758805588b29440 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | a1a04c3d3239d2aa0e113e7285fab76b25f286c2 (diff) | |
ci/github-script/labels: close empty PRs
If the change of a PR has already been merged to the target branch
elsewhere, the PR will not be auto-closed by GitHub - and will still
show the same original diff. Still, the temporary merge commit is
actually empty. This causes all kinds of strange CI behavior, from not
showing rebuilds to not pinging maintainers.
We check the merge commit during labeling anyway, to see whether a merge
conflict is present. It's easy to just look a the number of affected
files in this merge commit - and if there are none, we can just
automatically close the PR as no longer relevant.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions