Monorepo support built around git subtree.
pip install git_monorepo
Simply create a mapping file called monorepo.yml in the root of your git directory:
mappings: adhesive: firstname.lastname@example.org:germaniumhq/adhesive.git oaas: oaas: email@example.com:germaniumhq/oaas.git grpc-compiler: firstname.lastname@example.org:germaniumhq/oaas-grpc-compiler.git registry-api: email@example.com:germaniumhq/oaas-registry-api.git registry: firstname.lastname@example.org:germaniumhq/oaas-registry.git grpc: email@example.com:germaniumhq/oaas-grpc.git simple: firstname.lastname@example.org:germaniumhq/oaas-simple.git tools: git-monorepo: email@example.com:bmustiata/git-monorepo.git
If you want to use a different branch name in all the remote repositories instead of the same name as the local branch, specify it as such:
mappings: # ... branch: master **Note** This branch name applies for both pulling *and* pushing.
subtree creates the commits, including merges into the upstream repos. This could severely pollute the history of the upstream repos. Because of this reason, squashing is implicitly enabled.
To disable squash the history into single commits, set the squash property:
mappings: # ... squash: false
To pull the repos (including initial setup), use:
git mono pull
In case upstream changes happened in the remote repos, so a pull is required before the push, use the --no-sync flag, so it won’t automatically merge and mark the changes as already synchronized to the remote repo.
Implicity having a pull should be done on a clean repo, and a pull --no-sync if upstream changes are present.
To push the repos do:
git mono push
This takes into account the current branch name, so pushes can happen also with branches.
At the end of the operation, if something was pushed, a new file to track the status named .monorepo.sync is created and committed automatically. This file holds a list of commits that were pushed, so your merges can also be dealed with correctly, by adding both entries when solving a potential conflict for a project.
This renames the entry in the synchronized commits, and does the equivalent of:
git mv old/path new/path
With a special commit so git-subtree can find it.
You still need to manually update the monorepo.yml manually with the new location.
The feature is currently deemed unstable.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size git_monorepo-1.9.1.tar.gz (8.8 kB)||File type Source||Python version None||Upload date||Hashes View|