Make 'no public fork' checked as default for private repository (BB-4571)

Issue #4261 resolved
Starqle Indonesia
created an issue

To my understanding private repository is only completely secured from accidental public fork creation by checking the 'no public fork' option within the admin area.

For that purpose, can bitbucket make the 'no public fork' checked as default or perhaps the ability to mass-assign it, because private repositories can contains some sensitive codes and its quite a hassle to check whether the option was already checked one-by-one.

Comments (5)

  1. Log in to comment