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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
workflows/eval: Request reviews from changed package maintainers #366046
workflows/eval: Request reviews from changed package maintainers #366046
Changes from all commits
b9d800d
b844cba
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub apps are limited to 15 reviewer requests anyway, and this way treewide changes are handled better. Adding a
head -n15
here should work, but I did not test.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a good idea. Should be the list sorted, so it's always the same 15 reviewers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see two other options to handle treewides / PRs with more than 15 reviewers:
I actually prefer the first option: When you make a treewide change and you get some random 15 reviewers, chances are high that those reviewers:
So why notify many random people?
(Note that for a treewide, we very likely have already requested reviews from a bunch of people via OWNERS!)
For treewide changes it makes much more sense to pick your reviewers individually, specifically for that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is also a limit with posting maintainers in comments. But we probably should avoid mass-pinging so many people and leave it to the pr authors/reviewers to select the right set of people.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, we have now implemented requesting reviewers 1-by-1 to work around failures for some of them.
See #370749 for a run with that. Clearly the limit seems to apply for a single API request - and going 1-by-1 requested reviews from 30 reviewers there.
ofborg had limited itself to 10 per run manually. We'll need to do something about this as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is an extension on top of the current ofborg behavior, but maybe a good time to discuss it:
Can we extend the "relevant file names" for a derivation to include some dependent files like patches or setup hooks?
I remember having to look up maintainers from the derivation manually when changing the
setup-hook.sh
.I think some basic rules could be:
/default.nix
or the path ends in/package.nix
and is in/by-name/
, thenA random example that would benefit from it:
pkgs/by-name/me/meson/package.nix
would include changes to all the patch and.sh
files in the same folder.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@infinisil
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like we can first start with a minimal feature set and make it more complex later. Now since ofborg has been shutdown and will be re-instantiated with only a smaller feature set.