diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-05-23 23:43:42 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-05-23 23:43:42 +0200 |
| commit | 039a954892ac43ebe2d8b2f8b977122db710c969 (patch) | |
| tree | f41585cc50d1de37e5278cec90368d2f8077b365 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | e48d9d6174e77293235dd2f4e878f7214d0d8612 (diff) | |
workflows/{check-shell,manual-nixos,manual-nixpkgs}: use get-mege-commit action
This makes a difference for the case of a merge conflict: In that case,
the magic `.../merge` branch actually points to the *last test merge
commit* that was successful, which might not contain the latest head
commit in any way. Running the tests on that commit is heavily
misleading. By using the get-merge-commit action, we run on the PR's
head commit in this case, which is much better.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions