Issue #4304 new

Forking team-owned repository and permissions inheritance for non-member groups (BB-4783)

Ryan Djurovich
created an issue

Hello,

Currently, if a developer forks a repository which is owned by our team account, and checks the "Inherit repository user/group permissions" box, the repository will be created with the tam account assigned as user with Admin permissions, and:

  • Group permissions assigned to the team account repository, excluding those groups which the developer is not assigned to.

We would like this to changed to:

  • Group permissions assigned to the team account repository, including those groups which the developer is not assigned to.

The reason being that we have two groups setup:

  • Developers, with read-only access to mainline team repositories, who create forks under their own account and perform work here

  • Lead Developers, handling writes to mainline team repositories e.g. pull requests from developers

And with the current functionality, this requires all memebers of the Lead Developers group to be assigned to the Developers group also, otherwise they cannot perform pull requests as they will not have read access to the source (developers) repository.

Regards,

Ryan Djurovich

Evolution 7

Comments (0)

  1. Log in to comment