private project forks are expected to have same level of accessibility as group projects
- Say there is a group X and uder this group Y private project.
- In group X, two members are having developer role access.
- Both developers had forked project Y in their namespace
Issue: Developer 1 can not access the forked repo of Developer 2. Ideally private project forks are expected to have the same level of accessibility as group membership.
Currently, Developer 2 has to provide the access to Developer 1 to see the forked repo.