Investigate code owners to better suggest PR reviewers
Open
Nobody has claimed this yet.
bugfix day
- Dominant language
- C++
- Stars
- 245
- Forks
- 36
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 4
Description
This github feature may help better suggest who should be reviewing sections of the code.
For example:
- default: jamiebramwell, white238
- src/serac/infrastructure : white238, chapman39
- src/numerics/functional: samuelpmishLLNL
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked GitHub CODEOWNERS documentation, then inspect the repository's current pull-request review workflow. Determine whether code-owner-based reviewer suggestions fit the project and define what behavior would count as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100