Migrate Dependabot reviewers to codeowners - #2032
Open
HonkingGoose wants to merge 4 commits into
Open
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
HonkingGoose
commented
May 12, 2025
Comment thread
.github/CODEOWNERS
| # GitHub recommends listing the code owner in the CODEOWNER file. | ||
| # This means changes to the CODEOWNERS file must be reviewed by the code owner. | ||
|
|
||
| /.github/CODEOWNERS @ben |
Copy link
Copy Markdown
Contributor
Author
There was a problem hiding this comment.
Maybe you should add a "backup codeowner", so the organization can unblock itself when you're not around?
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes
Context
GitHub is going to stop listening to the reviewers field in the Dependabot config file soon (Tuesday 27 May). GitHub recommends using a CODEOWNERS file to control who must review incoming PRs.
The CODEOWNERS config pings @ben for all incoming PRs, and requires their approval before merge.
GitHub recommends explictly listing the code owner for the CODEOWNERS file. I'm following that recommendation in this PR.
I think you (@ben) will need to set up branch protection rules to make sure the CODEOWNERS need to review the changes before merge? Quote from the GitHub Docs:
References