Project Hygiene for Git and GitHubs
Project hygiene is the set of GitHub practices that keep a repository healthy. Issues and Projects track work and bugs, while repository settings such as branch protection, required reviews, CODEOWNERS and a .gitignore file enforce quality and prevent accidents like committing secrets.
Stage: GitHub Collaboration · Part of the Git and GitHub roadmap · Last reviewed 19 November 2026
What to learn in Project Hygiene
- Write an issue with steps to reproduce and expected behaviour
- Organise work on a GitHub Projects board
- Enable branch protection with required reviews and checks
- Assign reviewers automatically with a CODEOWNERS file
- Keep build output and secrets out with .gitignore
Project Hygiene interview questions
What does branch protection do?
Branch protection rules stop direct pushes or force pushes to important branches such as main, and can require pull requests, approvals and passing status checks before merging. They enforce review and testing.
What should you do if you commit a secret to Git?
Treat the secret as compromised and rotate it immediately, because removing it from the latest commit leaves it in history. Then purge it from history with a tool like git filter-repo if needed, and add the file to .gitignore.
Where Project Hygiene fits in the Git and GitHub roadmap
Project Hygiene belongs to the GitHub Collaboration stage (beginner level), which takes about 9 hours. Work with a team.
Other units in this stage
Back to the full Git and GitHub roadmap