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. | |
| | | | |
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. | |
| | | | |
initialcommit.com
|
|
| | | | | The practical guide to everything you've ever wanted to know about working with Git commit messages. | |
| | | | |
www.cesarsotovalero.net
|
|
| | | Git is the go-to version control system in software development, created by Linus Torvalds in 2005 for Linux kernel development. It's now an indispensable tool for tracking project history and managing versions. This post covers the key Git commands you need to streamline your development workflow. | ||
