Wolfgang Walther 856792f93e 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.		2025-06-01 09:35:51 +02:00
..
actions/get-merge-commit	workflows: checkout nixpkgs in get-merge-commit action	2025-05-25 15:14:23 +02:00
ISSUE_TEMPLATE	ISSUE_TEMPLATES: update releases following 25.11's branch-off	2025-05-16 20:27:35 -03:00
workflows	workflows/check-cherry-picks: truncate long diffs after 10k characters	2025-06-01 09:35:51 +02:00
dependabot.yml	.github/dependabot.yml: disable default labels	2025-05-05 17:15:19 +02:00
ISSUE_TEMPLATE.md	ISSUE_TEMPLATE.md: clear the blank issue template	2025-01-12 16:01:56 -03:00
labeler-development-branches.yml	workflows/labeler: fix repo owner condition	2025-05-04 18:52:43 +02:00
labeler-no-sync.yml	labels: Automatically label CI changes for backport to 25.05	2025-05-16 20:53:25 +02:00
labeler.yml	nixos/gnome & nixos/gdm: move out of x11	2025-05-28 13:27:36 +02:00
PULL_REQUEST_TEMPLATE.md	25.11 is Xantusia	2025-05-16 19:21:55 +02:00
STALE-BOT.md
stale.yml