Explore >> Select a destination
|
You are here 
|
kewah.com | ||
| | | | |
pboyd.io
|
|
| | | | | Small Git commits are great when working, but they aren't so great when looking at the history. This post examines the commands to make a clean Git history. | |
| | | | |
8yd.no
|
|
| | | | | Git squash takes your commits and squashes them together, usually into one commit. Useful for creating one commit if you've got a lot of smaller commits that creates a messy Git history. Git rebase ... | |
| | | | |
www.cheehow.dev
|
|
| | | | | Simple Git branching strategy for small teams. | |
| | | | |
citizen428.net
|
|
| | | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: | ||
