+6
-19
.github/workflows/check.yml
+6
-19
.github/workflows/check.yml
···-(fromJSON(inputs.baseBranch).stable && !contains(fromJSON(inputs.headBranch).type, 'development'))···+TARGETS_STABLE: ${{ fromJSON(inputs.baseBranch).stable && !contains(fromJSON(inputs.headBranch).type, 'development') }}
+4
.github/workflows/pr.yml
+4
.github/workflows/pr.yml
······
-1
.github/workflows/push.yml
-1
.github/workflows/push.yml
+18
-77
ci/github-script/commits.js
+18
-77
ci/github-script/commits.js
···············
+157
-14
ci/github-script/prepare.js
+157
-14
ci/github-script/prepare.js
······+'The `nixos-*` and `nixpkgs-*` branches are pushed to by the channel release script and should not be merged into directly.',+// when the number of commits exceeds it in reality. The difference between two stable releases+`The PR's base branch is set to \`${current.branch}\`, but ${current.commits === 10000 ? 'at least 10000' : current.commits - best.commits} commits from the \`${best.branch}\` branch are included. Make sure you know the [right base branch for your changes](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#branch-conventions), then:`,+`- If the changes should go to the \`${best.branch}\` branch, [change the base branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request).`,+`- If the changes should go to the \`${current.branch}\` branch, rebase your PR onto the correct merge-base:`,+` # git rebase --onto $(git merge-base upstream/${current.branch} HEAD) $(git merge-base upstream/${best.branch} HEAD)`,······
+85
ci/github-script/reviews.js
+85
ci/github-script/reviews.js
···
+10
-7
ci/github-script/run
+10
-7
ci/github-script/run
···············
-3
ci/request-reviews/default.nix
-3
ci/request-reviews/default.nix
···
-8
ci/request-reviews/dev-branches.txt
-8
ci/request-reviews/dev-branches.txt
+1
-23
ci/request-reviews/request-code-owner-reviews.sh
+1
-23
ci/request-reviews/request-code-owner-reviews.sh
·········-if ! "$SCRIPT_DIR"/verify-base-branch.sh "$tmp/nixpkgs.git" "$headRef" "$baseRepo" "$baseBranch" "$prRepo" "$prBranch" | tee "$tmp/invalid-base-error" >&2; then
-104
ci/request-reviews/verify-base-branch.sh
-104
ci/request-reviews/verify-base-branch.sh
···-git -C "$localRepo" branch --list --format "%(refname:short)" "${devBranchPatterns[@]}" > "$tmp/dev-branches"-echo "The PR's base branch is set to $baseBranch, but $extraCommits commits from the $testBranch branch are included. Make sure you know the [right base branch for your changes](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#branch-conventions), then:"-echo "- If the changes should go to the $testBranch branch, [change the base branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request) to $testBranch"-echo "- If the changes should go to the $baseBranch branch, rebase your PR onto the merge base with the $baseBranch branch:"-echo " # git rebase --onto \$(git merge-base upstream/$baseBranch HEAD) \$(git merge-base upstream/$testBranch HEAD)"
+15
ci/supportedBranches.js
+15
ci/supportedBranches.js
············