Branches and branching
An impressive feature of Git is branching. There are times during development when your project enters a state that you're happy with. The work may not be completed or final, but you've reached an important milestone that should be committed and saved to the history. At this point, your project can take multiple directions, and you'd like to experiment a little, trying out new ideas or developing clever solutions for new features. On reaching this point, you effectively need to Branch your work. This instructs Git to make a duplicate of your work and its history to this point (a new Branch), and then you can make further commits on the new branch, without affecting the history of the original branch. That way, if you ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access