Ideal team workflow?

We've just switched one of our accounts over to a team account
and are wondering what you're recommended workflow is for private
repositories. I found this comment on the blog post announcing teams that
is very close to the workflow we'd like to use:
http://blog.bitbucket.org/2012/05/30/bitbucket-teams/#comment-584674368

Basically, what we want is for users to be able to fork into their own
accounts and have the team permissions added to those forks so that other
members of the team can view those repositories. We see that forks can be
created within the team account, but this becomes a bit of a problem with a
large number of repositories; if everyone creates a fork, that's another
5-15 repositories per master repository. Considering that we're starting
with ~60 repositories, that can get out of hand really quickly and can
create a lot of chaff to sift through when looking for a specific
repository.

The other thing that gets a little messy is code reviews. If I fork a
private repository into my personal account and make a pull request, either
no one can view the pull request or I go over my plan limit. If I fork
into the team account, that means we need a separate mechanism for pull
requests/code reviews, which is a bit of an inconvenience.

2 answers

1 accepted

Accepted Answer
1 vote

The best plan in the case where you have a large team, but want less complicated permissioning, is to fork into the team account. There will be changes to the site in the future that will improve the way repos are shown on team and user accounts that should reduce or eliminate the need to "sift" through the list.

You may want to comment on and follow https://bitbucket.org/site/master/issue/2323/create-folders-to-organize-the-repository and https://bitbucket.org/site/master/issue/894/mark-repo-as-archived-or-inactive-bb-720 to contribute ideas or anything else as to how we can make the teams repo list easier for large teams.

Like many issues on https://bitbucket.org/site/master/

These 2 entries are open for YEARS.

I'm quite concerned about Bitbucket roadmap and ability to support our needs.

So it sounds like the solution is to just deal with it until something better comes along?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

2,406 views 9 12
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