This question is in reference to Atlassian Documentation: Forking a Repository
We are in a situation where developers are habitual of creating the number of forks, but they never delete un-used forks which result in a very large number of forks.
We need to have an ability to restrict a user to have a certain number of forks only. Is this do-able.
We have one instance of BBS with 5000~ developers and educating them on about forking and some basic R&Rs would work best for us. If you cannot trust them to follow some basic R&R, why trust them at all to develop your code? Moreover, why trust them to use your software? They can even put some malicious code into your system and nuke your company!
Even if Atlassian provides some restriction about this (5 fork repos per account), it would be very hard to justify it's importance along with thousands of other features suggested for BBS. There's no harm in trying though, put your request in https://support.atlassian.com
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