adjust CODEOWNERS to reduce unnecessary reviews for core-dev team #20587
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.
For discussion: we're currently getting pinged for a lot of reviews which don't seem necessary - indeed, most PRs where core-dev is auto-assigned as a reviewer end up being merged without our review.
I've updated the default assignee for all file changes to the core-yari-content team - this seems more appropriate - and limited the core-dev reviews to only files changed in the immediate root of the repo (excluding markdown files) and in the
.github
folder - even this may be a bit broad, but we can refine more in the future.Is this alright? Are there any files elsewhere we need to review before merging which may break the build?