In Stash, should I setup one project with many repositories or use a one-project-to-one repository model?

I have three different projects.... firmware, iOS and Android. When setting up my Stash instance, should I have one Project with many repositories, or have a project for each (firmware, iOS and Android,) with their corresponding repositories? What are the positives and negatives of each?

1 answer

Projects allow you to group related repositories together so if the three repos are related because the same folks work on all of them, then it makes sense to put them in the same project. If completely different people work on them then it would make more sense to put them in individual projects.

From the (git) client perspective it doesn't make a difference.

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

708 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot