I need to setup group access right to repositories. I would like to set permissions for groups as I do not want to set rights per user. I only way I see to so this is by Bitbucket team.
So I have two approaches :
1. Approach one is to create a team and create a repository for the team. This repository will be shown when you go to the team homepage.
2. Second approach is to create a repository and a team separately. Then, we do not create a repository for the team. We only go to the repository settings and then give access to the team ( usually some groups of the team) to the repository. If you go to the team page in this case, there are no repositories shown for the team.
Both of the above can work for me, but I was wondering if any of the approaches has any advantages over the other ?
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 ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot