diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-01-08 21:16:34 +0100 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-01-10 18:36:22 +0100 |
| commit | 3e9f5c05eacaa83dab454c97b55c852f5337225e (patch) | |
| tree | 164f0b592dbd102f812fcbfc756028ba0ec4c2c9 /pkgs/development/python-modules/rangehttpserver | |
| parent | ba09688dc88ac88a46a75412a1b72affcca16471 (diff) | |
workflows: rename baseSha to targetSha
We currently use two different "base" commits, but the same name. One of
them is the commit in which context the pull_request_target runs. The
other is the parent of the merge commit. Those are **not** necessarily
the same - see README introduced in the next commit for details.
Renaming one of them for clarity. Since the pull_request_target related
base commit is also called like that in GitHub Actions terminology, we
rename the other. The best I could come up with is "target".
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions