Ask HN: Large code repository in Git?

Re:Ask HN: Large code repository in Git? by ansible on Thursday March 12, 2015 @02:44PM (#9192870)

The other option for you (since our dependency list is fairly flat and uncomplicated, and yours may not be) would be to create a yaml/xml/json file to specify the directory structure and which packages go where, and then have the tool automatically update them appropriately. Alternately, store a .config.yml file in each repo telling what other repos should be cloned where, and let your tool recurse through it.

The nice thing about a tool like that is you can add functionality like e.g. doing a batch-commit (commit all changes in all/specified repositories, with the same commit message, create the same tag name for all of them in all repos, etc), batch-rollback, and so on.

I think you've basically re-invented Google's repo application. :-)

[ Parent | on HN ]

Re:Ask HN: Large code repository in Git? by stevekemp on Friday March 13, 2015 @04:24AM (#9196124)

Or even the "mr" tool which allows you to work with multiple-repositories easily.

I have a few locations where I have a config-file listing repositories, their target destinations, and some arbitrary shell commands (read: making symlinks) that I distribute to people. Users just run "mr -c config.cfg checkout" to get all the code in the right place.

http://myrepos.branchable.com/

[ Parent | on HN ]