This article is a continuation of my git workflow. As your teams grow or shrink, there are practices that you can do with git that can make knowledge transfer more comfortable. Here is a list of things that you can do to make that process easier. Branch from master Only keep branches that are actively worked on Branches should be relatively short-lived Merge master to your branch regularly if it exists longer than a few days.

Working on a large team of developers can be difficult when trying to keep code, branches, and repositories in sync. Here are a few things that I have found helpful. Branch from master If you are using a ticketing/bug-tracking system, use the ticket/bug identifier in the branch name git checkout -b ticket-1234 Keep your branch up-to-date by syncing master to it frequently git fetch && git merge master Commit to your branch frequently.