diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-05-31 10:56:29 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-06-01 09:35:51 +0200 |
| commit | 856792f93ef48454c154a728000fe01e2b27f5fd (patch) | |
| tree | 46a5fdbdffa83b45d9efa530d2812188b365b70b /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | 515b174c42ca9f5fa645688d249a00db90c578a0 (diff) | |
workflows/check-cherry-picks: truncate long diffs after 10k characters
GitHub comments have a length limit, so we can't just dump everything.
The 10k limit is arbitrary, but the assumption is that reviewing the
range-diff is not the sensible thing to do once it becomes a certain
size - reviewing the regular diff and treating the commit as "new" is
easier to do in that case. Thus, truncating should work out fine,
especially when the full range-diff is still available in the runner
log.
This could still end up in with an error, if a PR has multiple commits,
which all hit the limit. Let's get there first, before we try to fix
that hypothetical case, too.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions