For the repositories of my team, I would like to make it possible for my developers to see which projects their repositories are assigned to. However, it seems that the ability to see projects is coupled with the ability to create new repositories, which seems to a global right. I.e. if a developer has access to even one of my repositories and is allowed to create new repositories, he/she is able to see all of the company's projects.
Since we organize our resources on a need-to-know basis, this isn't ideal. So far, the only solution I have found, is to not give anyone the right to create new repositories. This, however, leads to a situation in which only our administrators can see any projects at all.
I would like to establish the following situation: Developers can not create new repositories, but they can see projects (i.e Project names), if they have access to repositories within these projects. Is this possible?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.