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:
- Always Work on a Branch
- Avoid Merge Commits with Rebase
- Merge and Squash
- Delete the Branch (Locally and Remotely)
Have an amazing project to share? Join the SHOW-AND-TELL every Wednesday night at 7:30pm ET on Google+ Hangouts.
Join us every Wednesday night at 8pm ET for Ask an Engineer!
Learn resistor values with Mho’s Resistance or get the best electronics calculator for engineers “Circuit Playground” – Adafruit’s Apps!
Maker Business — Transforming Today’s Bad Jobs into Tomorrow’s Good Jobs
Wearables — Make it snow
Electronics — Pseudodifferential Measurement
Biohacking — Soft Artificial Human Heart #3DThursday #3DPrinting
No comments yet.
Sorry, the comment form is closed at this time.