nixos/nixpkgs/ci/github-script, branch origin/python-updatesUnnamed repository; edit this file 'description' to name the repository.
http://cgit.wugi.info/nixos/nixpkgs/atom?h=origin%2Fpython-updates2025-07-21T06:13:11Zci/github-script/labels: limit cutoff to max 1 day (#426946)2025-07-21T06:13:11ZWolfgang Waltherwalther@technowledgy.de2025-07-21T06:13:11Zurn:sha1:0d6945991c344da87a7932cc670071700e8e233eci/github-script/labels: limit cutoff to max 1 day2025-07-20T19:53:21ZWolfgang Waltherwalther@technowledgy.de2025-07-20T14:20:41Zurn:sha1:7f9f7a20b0434f9acb96b05e5f121a9ef29f53d6
It has only happened once, but the GitHub API suddenly returned a
workflow run from a few weeks back. This lead to quickly hitting the
rate limit for search requests.
Prevent this from happening by going back a day max for the "recently
updated" case. After roughly a day, every PR will have been touched by
the regular batch processing anyway.
Also save a few API requests, by taking bigger chunks of the search
result.
ci/github-script/commits: harden code block rendering2025-07-20T14:06:25ZWolfgang Waltherwalther@technowledgy.de2025-07-20T14:06:25Zurn:sha1:524a47b2b4e82ca0086c997de303b404f7cba51e
To avoid rendering issues when diffing a markdown file with these
markers in context, just increase the markers length.
Revert "ci/github-script/commits: keep formatting for diffs of markdown blocks"2025-07-20T14:04:23ZWolfgang Waltherwalther@technowledgy.de2025-07-20T14:04:23Zurn:sha1:4a0c2c58a2f3270b36ba6d2a334511b7f5b161ca
This reverts commit b19798c8b03cc378373aac1a9e01cfdbb5f12305.
It lead to messed up formatting of the diff.
ci/github-script/commits: shorten and clarify review comment2025-07-16T13:47:19ZWolfgang Waltherwalther@technowledgy.de2025-07-16T13:15:23Zurn:sha1:486756d85c20db90003cac6136380e5c1aa36a8e
Also following the one-sentence-per-line rule now.
ci/github-script/commits: fix job_url2025-07-16T13:47:18ZWolfgang Waltherwalther@technowledgy.de2025-07-16T10:53:41Zurn:sha1:c4496912fdeaa0255c13250ad0ab7996e9498b7a
This broke when we moved the check-cherry-picks workflow into the bigger
PR workflow. At this time, the "workflow run" became the whole PR
workflow, which includes many more than just 1 job, thus the assumption
in `jobs[0]` doesn't hold anymore.
ci/github-script/commits: block on errors2025-07-16T13:47:17ZWolfgang Waltherwalther@technowledgy.de2025-07-16T10:28:29Zurn:sha1:1fbcad04345d37eb50aadac2d8eaf876a9a7fa15
Most of the checks we do for cherry-picks are dismissable warnings, with
one exception: When a commit hash has been found, but this hash is not
available in any of the pickable branches, we raise this with
severity=error. This should also *block* the merge and not be
dismissable. That's because this is a fixable issue in every case.
ci/github-script/commits: keep formatting for diffs of markdown blocks2025-07-16T10:15:07ZWolfgang Waltherwalther@technowledgy.de2025-07-16T10:15:07Zurn:sha1:b19798c8b03cc378373aac1a9e01cfdbb5f12305
Previously, when the diff contained a context line with ```, this would
end the code block and entirely break the markdown rendering.
Now we use the html code blocks provided by `core.summary` and properly
escape the content, so that it never escapes via html tags.
ci/github-script/commits: ignore whitespace on diff2025-07-16T09:59:28ZWolfgang Waltherwalther@technowledgy.de2025-07-16T09:59:28Zurn:sha1:40dcbb1483f527d919430386efb08401be8be55a
This reduces noise that the cherry-pick reviews produce when formatting
related conflicts had to be resolved. We only do this in the
length-limited review comment, though. All changes, including
whitespace, can still be double-checked in the job log if needed.
ci/github-script/commits: add comment about --creation-factor2025-07-16T09:58:08ZWolfgang Waltherwalther@technowledgy.de2025-07-16T09:58:08Zurn:sha1:84925b35c4c394ab244e8ef89874cc850de237a9