A repoo with some branches and some pull requests designed to show how to:
- Make good commits
- Not too much sausage (squash commits)
- Not too little sausage (splitt commits)
- Make good Pull Requests
- Review Pull Requests like a boss
- Use the Fetch & Rebase method of working (rather than pull)
Obviously some of this is very opinionated. I am working to the following principles when making this guide:
This post by Chris Beams delves deep into what makes a good commit message and why.
We don't need to see how the sausage is made. A good commit should be the code needed for a single logical change. Nothing more, nothing less.
Much like the Good commits section above good Pull Requests make everyone's lives easier.