[Quality of Life]: Use codeowners and leverage teams through CODEOWNERS file.
Open
Nobody has claimed this yet.
backlog
quality of life
- Dominant language
- JavaScript
- Stars
- 232
- Forks
- 77
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 17
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
N/A
Describe the feature request
A good use for scoping issues and triaging is to make use of github teams and an CODEOWNERS file for each of your projects (say OpenMCT/MMGIS).
Check out how we do it at webpack. This will make your admin/maintainance tasking better.
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 webpack CODEOWNERS example linked in the issue and review how GitHub teams are used for ownership. Define the relevant teams and add CODEOWNERS files for the OpenMCT/MMGIS projects; done means GitHub can assign the named teams as reviewers for the owned paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100