I'm regretting not just putting everything in one repo, so that it looks like:
SurePulse
SurePulseDataProccessor
SurePulseViewer
SPLibraries
...etc
The only reason to have separate repos is if they are being used independently. This is not the case, and the codebases are tiny, so they should be in one repo.
Benefits:
Less commands when developing. A lot of mental overhead goes into maintaining 7 different repos while developing, and potential for sync errors between repos
We often have multiple PR's for the same feature/fix. This would mean we only have one PR.
All issues go into one repo.
Easier for new contributors. If you look at our developer guide, you can see the hassle of cloning 7 repos.
markhalonen
commented
6 years ago
I'm regretting not just putting everything in one repo, so that it looks like:
SurePulseSurePulseDataProccessorSurePulseViewerSPLibraries...etcThe only reason to have separate repos is if they are being used independently. This is not the case, and the codebases are tiny, so they should be in one repo.
Benefits:
Google has one repo, surely SurePulse can be.