git-meta
git-meta copied to clipboard
twosigma
Repository for the git-meta project -- build your own monorepo using Git submodules
Our typical workflow very much depends on branches across multiple repos. The meta repo state that should be recorded for every commit should not only record the hash of the...
Well, I didn't get everything I wanted done, but at least I got this.
``` git init foo git init bar cd foo touch .gitmodules git add .gitmodules git commit -m 'first commit' git meta push ../bar HEAD:refs/heads/tmp ``` Expected: (try running with "meta"...
git meta status does not respect the `color.status` config. Apparently it is hard coded in the `colors/safe` npm module. Apparently `FORCE_COLOR=0 git meta status` works
Command: `git meta log --stat` Observed: The output lists the changed submodules in the meta repo. Expected: The output lists the files changed in each submodule, for each meta commit
Command: ``` git meta merge otherbranch ``` Output: ``` Submodule ts/foo/bar is conflicted. ``` Expected: ``` Merge conflict in ts/foo/bar/file1. Merge conflict in ts/foo/bar/file2. ```
``` git meta remote remove origin git meta fetch $URL # OR git meta push $URL ``` Expected: * Resolves submodule's relpath (../../foo/bar) to $URL Actual: * Fails since it...
The `-p` option to `git meta log` should list the changes to the files committed. However, instead it shows you the changes to the submodule SHAs, eg. ``` @@ -1...
Repro steps: ``` git init emptyrepo cd emptyrepo git fetch https://github.com/twosigma/git-meta git meta checkout FETCH_HEAD ``` Expected: * Checks out FETCH_HEAD Actual: ``` TypeError: Cannot read property 'id' of null...
If the stash-pop command fails from a conflict in one submodule, changes from that stash in other submodules don't get applied. They're also gone from the list of stashes.
