MultiGitRepository

From APIDesign

Using single Git repository is certainly more comfortable than working with multiple Git repositories. On the other hand, distributed development can hardly be performed in a single repository (unless you believe in a single Blockchain for the whole sourcecode on the planet). How to orchestrate multiple Git repositories to work together? That is the thousands dollar question various teams seek answer to! For example there was a talk at GeeCON 2017 in Prague about that by Robert Munteanu. Let's assume we have a project split into multiple Git repositories. What are the options?

Contents 1 Remember non-Distributed Version Control Systems? 2 Gates for Correctness 3 Single Integration Repository 4 Always Correct vs. Ultimately Correct 5 Single vs. Multi: Where's the difference?

Remember non-Distributed Version Control Systems?

TBD There used to be times when people were afraid of distributed version control systems like Mercurial or Git. All the users of CVS or Subversion couldn't understand how one can develop and commit in parallel without integrating into the tip of the development branch!

Gates for Correctness

TBD

Single Integration Repository

TBD

Always Correct vs. Ultimately Correct

TBD

Single vs. Multi: Where's the difference?

TBD