Post idea: Creating Sensible Defaults for Development Teams
Closed this issue · 0 comments
SeanKilleen commented
Setting teams up for success with modern software delivery.
It helps to create successful paths of least resistance. Here are some things I've learned.
- Modeling behavior around issues, PRs, merges
- Implementing builds on pull requests
- Setting up a GitHub flow (vs git flow) system where applicable
- Making merges default to squash merges
- Introducing dependabot to keep things up to date
- the readme. Make it nice
- formatting and rule enforcement if it doesn't exist ( no need to be rigid about individual rules in many cases though)