nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Matt Evered1

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?

Accepted answers

All comments

Rich Duncan

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.

unknown

Tim Crall1

RIch nailed it

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bitbucket-administration