Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Big Bang Move to Monorepo
See original GitHub issueBefore doing the bing bang, the following point needs to be checked:
- Can we keep the Git History ? Especially useful for
git annotateto find the author of some code. - What about issues ? Can the easily moved in bulk or needs this to be done manually isssue-by-issue ? How to label them ? (see also #9)
- PR: Each PR author should rebase and resolve conflicts and then move the PR over via a patch.
- What are the consequences for productisation ? // @cunningt
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Migrating to the monorepo. How you can take your existing git…
1. Decide on the directory structure. Are you going to move all of the repos into src or services or leave them at...
Read more >Monorepo vs Polyrepo: 5 Things You Should Consider
In this article, I will introduce Monorepo and Polyrepo and help you differentiate them with detailed insight for better decision-making.
Read more >My team just switched to a monorepo. It's been only a few ...
My team just switched to a monorepo. It's been only a few weeks, so I can't claim any results yet, but we've lived...
Read more >Consolidating multiple repositories into a Monorepo
Using submodules absolutely subtracts the benefits of visibility as new changes are often only seen as an updated hash in the parent repo,...
Read more >Monolith, meet mono-repo - Shortcut
We could not simply discard this functionality, and trying to reimplement it could have quickly turned into the “big bang” rewrite we wanted ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We can keep history. I created a https://github.com/chirino/syndesis/blob/merge-modules branch which does not have the git submodules thing going and has a fresh history. It contains the following script:
https://github.com/chirino/syndesis/blob/merge-modules/merge-modules.sh
Which when run, will merge all the project modules master branches into the merge-modules branch with history.
When we are ready for the big bang, run the script then push rename the merge-modules branch to master and push to origin with --force.
For folks that have open PRs, you can re-apply them as a patch. For example, say you have PR https://github.com/syndesisio/syndesis-rest/pull/773 open. You could re-apply it in the monorepo by running: