Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

combining repos

mathew mathew March 19, 2014

my team currently owns ~20 different maven modules (with a single repo for each). Is there a way in stash to create a single project, with all 20 repos underneath, or is the intent for a 1 to 1 mapping between projects and repositories?

3 answers

1 accepted

1 vote
Answer accepted
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2014

There are two options. Subtree and submodule. Here is a good demo of each (http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/).

1 vote
Balázs Szakmáry
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2014

You can arrange your repos into projects as you please. (They can also be moved from one project to another if things change.) The two main organising factors should be
- The logical grouping of the repos (part of the same product, owned by the same team, etc.)
- Common access control requirements (everybody who can read/write a project can read/write all the repos in it, with the exception of restrictions set by branch permissions)

[As Timothy pointed out, you can arrange your repos as submodules of each other, if necessary/convenient, but this is independent of how you organise them into projects.]

0 votes
Balázs Szakmáry
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2014

You can arrange your repos into projects as you please. (They can also be moved from one project to another if things change.) The two main organising factors should be
- The logical grouping of the repos (part of the same product, owned by the same team, etc.)
- Common access control requirements (everybody who can read/write a project can read/write all the repos in it, with the exception of restrictions set by branch permissions)

[As Timothy pointed out, you can arrange your repos as submodules of each other, if necessary/convenient, but this has nothing to do with organising them into projects.]

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events