Is it possible to decline the creation of a public repository for a certain team? Right now, when you create a new repository, you have the ability to specifically create a public repository, even though it is private by default.
I'll add another vote for this feature request. Our organization is currently evaluating different source control technologies, and we consider the lack of this feature a deal breaker. We want to make sure a mistake in a single configuration option makes our internal IP public, and we would prefer a cloud hosted solution instead of a self-hosted solution.
Can you report back on the request for this feature?
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events