Explore >> Select a destination
|
You are here 
|
cbea.ms | ||
| | | | |
jmatuszewski.com
|
|
| | | | | Learn about the importance of writing a good commit messages. How to use message templates, hooks, aliases and how to navigate Git history like a pro. | |
| | | | |
blog.dnsimple.com
|
|
| | | | | A retrospective of the last two years where we adopted --squash as our default merge strategy for git branches. | |
| | | | |
www.brandonpugh.com
|
|
| | | | | I've reviewed quite a few pull requests in recent years and I've noticed some less-than-ideal practices when it comes to creating merge commits so I thought I'd list some things you can do to make life a little easier for someone reviewing your code. Make the commit message as useful as possible A lot has been written about how to write good commit messages, but I rarely see the advice applied to merge commits. They may not be the most exciting type of commit, but they're still very important. | |
| | | | |
andrew.yurisich.com
|
|
| | | |||
