Add CODEOWNERS file #4764
Merged
Add CODEOWNERS file #4764
Conversation
This file contains 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
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 PR suggests a CODEOWNERS file, which is a GitHub convention for specifying individual ownership/interest in parts of a repository.
The proposed file uses freshly-added DDEV organization teams (Development and Documentation) rather than individual usernames, so those teams can be modified as necessary and referenced by a handle. This should encourage tidy team organization and serve as a useful shorthand particularly if CODEOWNERS are designated in additional repositories.
Ultimately the file designates Randy (
@ddev/development) as the global owner of everything (*), and Matt (@ddev/documentation) as the owner ofREADME.mdand the contents of the/docs/folder. With this file in place, PR reviews will be suggested accordingly.I strictly designated myself over here until that project gets settled since it really is me, and not an imaginary documentation team, that best knows that project having created it recently.