version control - Does git have any built in repository management strategy? -
i'm trying come version control strategy moving our company’s code , document files centralized scm (perforce) git. content in perforce 1 large depot projects stored, want break multiple smaller git repositories number of reasons.
the issue have how can index of these repositories can found. far can tell, git doesn't have built in tools managing multiple repositories.
i did find git-submodule, sounds that's making repository content of other repositories, , don't want manage content of various repositories repositories themselves.
originally thinking flat file system on our sever:
/repos -repo1.git -repo2.git -... -repon.git
and git command query directory repository names , comment content (sort of logging server, going /repos
directory , running git log
). thinking make /repo
git
repository (a repository of repositories) , said, seems so... un-git-y.
so questions are:
- am missing built
git
tools/features made manage multiple repositories this? - am correct in thinking
git-submodule
not i'm looking manage this? - are there strategies you've seen type of set up?
if want pure git solution, looking git-submodule
.
especially when say:
i thinking make /repo git repository (a repository of repositories)
this submodules are.
the parent repo keep track of single file - .gitmodules
, connects paths revisions of other repos.
however in experience i've come conclusion git submodules not ideal, when deal inexperienced git users. cause problems when switching branches or making changes in submodules. gui git clients not have full support submodules.
but if want track these folders, ok submodules.
another way ignore such folders in main repo , have separate git repos in these folders. git works in these folders, no matter under git repo.
this solution works vendor libraries within application project. , use package/dependency manager update them or cd
, git pull
.
Comments
Post a Comment