


If your team is using Git, odds are you won’t have to train new hires on your workflow, because they’ll already be familiar with distributed development. In many circles, Git has come to be the expected version control system for new projects. In turn, changes can get pushed down the deployment pipeline faster than the monolithic releases common with centralized version control systems. These capabilities facilitate an agile workflow where developers are encouraged to share smaller changes more frequently. The ultimate result of feature branches, distributed development, pull requests, and a stable community is a faster release cycle. This not only makes it easier for project leads to keep track of changes, but also lets developers initiate discussions around their work before integrating it with the rest of the codebase. A pull request is a way to ask another developer to merge one of your branches into their repository.
