sudo npm install git-seed -g
Current version 0.0.6 (unstable)
git-seed
Todo
- Follow symlinks
- Switch to notice-0.0.11
- Inform when switching submodule from git clone to subsequently published npm install (npm wont write into a node_modules folder already populated by git repo clone and vice-versa, best to leave the delete up to the user)
- Inform on multiple nested same submodule on different revision. (This happens when the same unreleased node_module is a doublenested dependency in more than one nested submodule) or see tip
Usage
git seed --help
git seed init
Make/Update the .git-seed
file
> git seed init info - recurse
git seed clone
Clone all repos according to the .git-seed
file
- The
.git-seed
control file specifies the branch that each repo should be on. - Running a clone will checkout that branch
> git seed clone info -
git seed status
Report status across all repos in the .git-seed
file
> git seed status info -
git seed commit
Commit with a common message across all repos with staged changes
> git seed commit -m 'commit uses pipeline' info -
git seed pull
Pull across all repos
- Pull first pulls the root repo to get the latest seed file
- Pull only pulls other repos if their local version differs from that in the seed file
> git seed pull info -
Tip
Got the same module nested again deeper inside another?
cd node_modules/rm -fr notice/ln -s phrase/node_modules/noticecd ../git seed status info -