Rules to Better GitHub
- Do you enable pull requests to ensure code is reviewed?
- Do you know how to name a GitHub Repository?
- Do you add a description to your GitHub repositories?
- Do you know how to structure a project for GitHub?
- Do you know how to use labels for GitHub Issues?
- Do you know how to completely remove confidential information from a GitHub Issue?
- GitHub Issues - Do you use Issue Templates?
- Do you know how to make content changes on GitHub?
- Do you know how to write a great Pull Request (PR)?
- Pull Requests - Do you use and indicate Draft Pull Requests?
- Do you know when to branch in git?
- Do your branches have a naming convention?
- Do you include a useful description of your changes?
- Do you have a "rubber stamp" approval method for PRs?
- Do you know when to add your changes to an existing PR?
- Do you use indentation for readability?
- Do you know to the requirements to create a new repository?
- GitHub Repos - Do you write nice commit messages?
- GitHub Issues - Do you turn emails into Issues before starting work?
- Do you know to mention someone with a @mention when you make a pull request or comment on GitHub?
- Do you require 2FA to join your GitHub organisation?
- Do you restrict repository deletion?
- Do you use branch protection?
- Do you know when to override branch protection rules?
- Do you use GitHub Discussions?
- Do you use GitHub Topics?
- Do you know why reacting to GitHub Issues/Discussions is important?
- GitHub - Do you use GitHub teams for collaborator permissions?
- Do you have GitHub on your phone?
- Do you know how to view a project’s activity, traffic and contributions?
- Do you limit who gets admin access to repositories?
- Do you set default permissions for all new repositories?
- Do you know how to setup GitHub notifications?
- Do you know to set up GitHub Scrum workflow?
- Do you configure your GitHub Notifications?
- GitHub Actions - Do you know why Job Summaries are awesome?
- Do you know how to handle special characters in GitHub Secrets and Variables?
- Do you store your GitHub secrets in Azure KeyVault?
- Git - Do you know when to create a fork vs a branch?
- Pull Request - Do you do over the shoulder reviews?
- GitHub Environments - Do you use gated deployments?
- Do you use tasklists in your PBIs?
- Do you close PBIs and tasks with context?
- Do you avoid linking issues to PRs in GitHub?
- Do you use enterprise secrets in your DevOps pipelines?
- Do you use Pull Request templates to specify the expectations and requirements for each PR?
- Do you merge open source pull requests using the "Squash and merge" option?
- Do you to keep a PBI's current status visible?
- Do you use Co-Authored Commits?
- Do you know the best license for your project?
- Do you know the best way to suggest changes on a Pull Request?
- Do you know how to view changes made to a file in GitHub?