Managing Poly Repo
Multiple GIT
- git remote add all https://github.com/McK-Playground/EV-Playbook.git
Re-register the remote as a push URL.β
- git remote set-url --add --push all https://github.com/McK-Playground/EV-Playbook.git
- git remote set-url --add --push all git@github.mdl.cloud:ev/ev-playbook.git
- git push all
Re-register the remote as a push URL.β
- git remote add all <current_github_repo>
- git remote set-url --add --push all <current_github_repo>
- git remote set-url --add --push all <current_github_repo_2>
- git push all
CLEANUP UNRELATED GIT HISTORIES
- git pull https://github.com/McK-Private/leapx-olympus.git <branch_name> --allow-unrelated-histories -X theirs
Poly repo versus Mono Repo
Polyβ
- Needs Bounded Context
- Needs clear seperation of ownership
- Faster CI/CD
- Easier to understand
- GraphQL how to manage (?)
Consβ
- Unable to spin up the whole thing e2e
Monoβ
Notes:
- Google uses, but using trunk based development
- Conway's Law
- Able to spin up everything (if you have a powerful machine)
Consβ
- Slow
- Anti pattern on commons
- Anti pattern on microservices