MultiGitRepository
From APIDesign
(Difference between revisions)
(New page: 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 s...) |
|||
| Line 1: | Line 1: | ||
| - | 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 planet) | + | 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 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 [https://2017.geecon.cz/schedule-day2/ Robert Munteanu]. |
Revision as of 12:28, 18 December 2017
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 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.
Follow
