Git allows us to have multiple repos, unlike centralized version control systems. This is why we call it a "distributed" system. However, Git allows more than one kind of distributed workflow. This way, teams can adopt workflows that work for their projects.
In this Coffee Break Course, you'll look at two of the most important distributed Git workflows: the integration manager workflow and the benevolent dictator model.
Why not check out our Introduction to Git and GitHub or watch the other Coffee Break Courses in this series:
1. Git Basics: Distributed Workflows
GIT is pretty awesome when it comes to sharing code. I think it's fair to say, that next to simple and inexpensive branching, the convenience of distributing code with GIT made it the powerhouse it is today. GIT allows us to have multiple repos, unlike centralized systems. Every repo is a node of equal power. Their permissions can differ, though. Read and write access can be distributed as needed. Being able to easily contribute code offline is another cool aspect we take for granted. There is more than one distributed workflow. The flexibility to adapt work flows to the preferences of teams or to the size of project is quite impressive. Daunting for beginners maybe, but also a very enabling once you face production environments or bigger open source projects for example.