Issue #8428 invalid

Forced private forks count towards private user allotment

mvdkleijn
created an issue

I have a feature of private repositories that I'm not in agreement with. It concerns the following scenario:

  • User A creates a public repository but forces forks to be private
  • User B creates a fork (which is of course private)
  • User A gets admin rights on the private fork

Fine so far... here's the part that I'm not a "fan" of to put it mildly:

  • User B looks at his "Plans and Billing" page and finds that User A counts towards his 5 free users.

That just doesn't seem right to me. Since user B did not explicitly give user A access, your saying this:

  • A fork action can lead to a reduction in available users
  • If you have a free account, you can only fork max. 5 repos that force private forks.

That seems both unfair as well as illogical. No one should be able to influence how much of my free or paid "private user count" allotment is spent but me.

Case in point: my (forced) private fork here https://bitbucket.org/mvdkleijn/social_login

Comments (2)

  1. Marcus Bertrand staff

    When you fork a private repository, you have a choice to not inherit permissions to your fork. The other user does not need access to your fork for your Pull Requests to function.

    In the future, we will be adding a better warning when forking about the potential to inherit and reduce your plan as a result.

    To be clear, there is no situation where we force a private fork to count against your user plan. This is only possible if you choose to allow the owner of the original to have access, which is a valid case as you now have a private repository and you've given someone else access to it.

  2. Log in to comment