I have many projects with shared components that are in independent repositories, so I would love to have them "packaged" as part of all of the projects that make use of them.
That would be difficult with the repository permissions. The repository can have it's own distinguished permissions - but it also inherits the permissions of the project it belongs to. What if one project is very restrictive with permissions and the other project very liberal? What policy should be inherited from the projects for the given repsoitory?
Bitbucket projects are not projects to organize repositories according their functional structure (as you would like to) - Bitbucket projects are meant to group repositories with the same superordinate permissions on the first hand.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs