4 Quick Tips for Cleaner Git History

Thanks to Ryan Abel from Atomic Object for these Four Steps to Maintaining a Clean Git History – the rebase tip is especially useful, and while I’m *always* a little hesitant to press ‘delete’ on most things, there are times when it’s a-ok!

Git is a very important tool. Not only does it keep a history of a project, but Git also makes it easy for a team to collaborate in a codebase. Although it’s such an important tool, it’s often under-utilized and on occasion, even neglected.

A clean Git history is easy to understand and tells a story about the project. It’s evident when features were added and how they were implemented. I’ve come to cherish a clean Git history on a project. The good news is, it’s not very difficult to keep this history clean.

The tips headings are:

1. Always Work on a Branch
2. Avoid Merge Commits with Rebase
3. Merge and Squash
4. Delete the Branch (Locally and Remotely)

Read more here.

from Adafruit Industries – Makers, hackers, artists, designers and engineers! http://ift.tt/2tltZcg
via IFTTT