Formalizing code owners
Open
keep
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 233
- PR merge metrics
- No merged PRs in 30d
Description
Our team is oriented with ppl in some knowledge in an area, and less in others, so it might be worth formalizing this under the form of codeowners. Codeowners would allow us to ping the right person automatically on code reviews, and make it easier for community members to know what they own or what are the areas that deserve more love.
WDYT?
Contributor guide
Research direction
No files or tests are named. Start by reviewing GitHub CODEOWNERS behavior and the repository's major ownership areas, then determine which team members should own each area. Done means the ownership model is agreed and documented in the appropriate repository configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100