Git Codebase Management Cheat Sheet

Now that you know how to use branches, you can be more organized in your coding projects, especially those with more people on them where lots of different work is being done independently.

The branching and merging workflow, while useful, can be quite complicated, even for a Git veteran. Here is a cheat-sheet summarizing everything we have covered so that you can reference it when you need to remember how it all works:

Use Branches To:

Code independently on a team, with the same codebase
Store experimental features/buggy code somewhere for testing purposes without causing problems where the working/production code is
Group independent changes by feature to keep things organized, and selectively merge them into a production codebase (usually on master branch)
Communicate and organize with others

The Best Practices Are:

Group commits for features into new branches to keep things organized.
Make sure source branches are up to date and don’t have issues/bugs of their own
Maintain a branch with only working/production code
Delete old and merged branches unless there is a good reason not to
Prefer to use branching/merging features through GitHub's interface; it's easier and more organized

Command Reference:

git checkout <branch name> (switch to branch)
git checkout -b <branch name>(switch to branch, create beforehand if it does not exist. Current uncommitted changes are transferred)
git merge <source branch name> (merge branch into current branch)
git merge --continue (after resolving conflicts manually; recommended to do so on GitHub if possible)
git merge --abort(abort resolving a merge conflict manually)

Additional Resources:

PreviousBest Practices For Branching NextConclusion

Last updated 4 years ago

Was this helpful?