ci/request-reviews: limit to 10 review requests #371115
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This mirrors old ofborg for now and avoids pinging a huge number of reviewers, for example like in #370749 or even worse in #371100. The latter is similar to the old code-owners behavior after changing from master to staging. Both happened after #370857.
I'm thinking about alternatives based on my ideas in #366046 (comment), but to make those work well, we'd need to avoiding pinging maintainers in draft mode first as discussed in #370857 (comment). However, that's not trivial, because we don't want to run all of eval again on each "pull request edited" event.
This change here technically limits review requests to 10 reviewers max for code owners, too - not only maintainers. That's because both now used the same code path since #370857. I'm OK with this for now.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.