+10
-27
.github/workflows/check.yml
+10
-27
.github/workflows/check.yml
···-`\n_Hint: The full diffs are also available in the [runner logs](${job_url}) with slightly better highlighting._`
ci/check-cherry-picks.md
ci/github-script/check-cherry-picks.md
ci/check-cherry-picks.md
ci/github-script/check-cherry-picks.md
-152
ci/check-cherry-picks.sh
-152
ci/check-cherry-picks.sh
···-PICKABLE_BRANCHES="master staging release-??.?? staging-??.?? haskell-updates python-updates staging-next staging-next-??.??"-log warning "Difference between $new_commit_sha and original $original_commit_sha may warrant inspection."-# Also limit the output to 10k bytes (and remove the last, potentially incomplete line), because-# GitHub comments are limited in length. The value of 10k is arbitrary with the assumption, that-# after the range-diff becomes a certain size, a reviewer is better off reviewing the regular diff-# Note: This could still lead to a too lengthy comment with multiple commits touching the limit. We-printf -v diff "%s\n>\n> [...truncated...]" "$(echo "$diff" | head -c $max_length | head -n-1)"
+4
ci/github-script/README.md
+4
ci/github-script/README.md
···+Run `./run commits OWNER REPO PR`, where OWNER is your username or "NixOS", REPO is the name of your fork or "nixpkgs" and PR is the number of the pull request to check.
+199
ci/github-script/commits.js
+199
ci/github-script/commits.js
···+url: `https://github.com/${context.repo.owner}/${context.repo.repo}/branch_commits/${original_sha}`,+// For some unknown reason a 404 error comes back as 500 without any more details in a GitHub Actions runner.+// # The output of `git range-diff` is indented with 4 spaces, but we'll control indentation manually.+// The docs for markdown alerts only show examples with markdown blockquote syntax, like this:+// However, our testing shows that this also works with a `<blockquote>` html tag, as long as there+// Limit the output to 10k bytes and remove the last, potentially incomplete line, because GitHub+// comments are limited in length. The value of 10k is arbitrary with the assumption, that after+// the range-diff becomes a certain size, a reviewer is better off reviewing the regular diff in+// Note: if multiple commits are close to the limit, this approach could still lead to a comment+// that's too long. We think this is unlikely to happen, and so don't deal with it explicitly.+`\n\n_Hint: The full diffs are also available in the [runner logs](${job_url}) with slightly better highlighting._`,
+36
-22
ci/github-script/run
+36
-22
ci/github-script/run
·········
+2
ci/github-script/withRateLimit.js
+2
ci/github-script/withRateLimit.js
···