diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-11-02 19:35:27 +0100 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-11-02 19:35:32 +0100 |
| commit | 9a637aa7a439739120b0a9c80435c3dc6b1ddb68 (patch) | |
| tree | f3e18bb0ad30e72d0fcfc5e10f22ac532c917eb2 /pkgs/development/python-modules/rangehttpserver | |
| parent | 37b7773907f5a183489d28123b4cae6329654a46 (diff) | |
ci/github-script/merge: restructure head SHA check
While it was already the case that only merge comments *after* the
latest push were acted on, the logic wasn't easy to understand. This
change should make it more obvious, specially in combination with the
next commit, that all steps (comments, approvals, merge) must happen on
the same SHA - the current head SHA of the PR.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions