Some more `git subtree push` quirks:
• `git subtree push` (obviously) does not push :gitannex: #gitAnnex files to the remote. Syncing annexed files there is unergonomic.
• `git subtree push` also strips commit signatures (e.g. GPG and as such #OpenTimeStamps timestamps). The truth lies in the monorepo only. Understandable, but very uncool.
git submodules have neither problem, but without tools like :datalad: #datalad you can't commit at once.
Does anyone have experience with #gitSubRepo? It seems to be a more ergonomic version of #gitSubTree that e.g. remembers remote urls to spare you lengthy syncing commands.
Merging multiple repositories into a monorepo, while preserving history, using git subtree
How to merge multiple repositories, with their history, into a single repository, using the `git subtree add` command.
https://fed.brid.gy/r/https://www.jvt.me/posts/2018/06/01/git-subtree-monorepo/
I have used a git subtree, and while I kinda hate it. I still think it was the right call given the constraints.
This is not a reply because I don’t want to argue with the take that brought it to mind.
If, for some reason, you want to use git subtree, think very carefully about doing so. Reasons follow.
Importing a subdirectory from one repo into another
How to import a subdirectory of a given Git repository into another one, using `git subtree`.
https://fed.brid.gy/r/https://www.jvt.me/posts/2023/10/23/import-subtree-git-repo/
