Consider Adding A Codeowners File
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
People with write permissions for the repository can create or edit the CODEOWNERS file and be listed as code owners. People with admin or owner permissions can require that pull requests have to be approved by code owners before they can be merged.
For more information, see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.
Example CODEOWNERS file in CFA: https://github.com/CDCgov/hubhelpr/blob/main/.github/CODEOWNERS
Contributor guide
No contributing guide indexed for this repository
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
Read the linked GitHub CODEOWNERS documentation and compare the example .github/CODEOWNERS file in CDCgov/hubhelpr. Determine the appropriate CODEOWNERS location and ownership entries for DynODE; the work is done when the repository has the agreed CODEOWNERS configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100