I have 10+ teams and 50+ repos in an organization account. The goal is to group selected repos into a management unit so I can grant access to teams with fine permission.
The members of the teams will keep changing roughly monthly.
Question
Is this possible?
If not, what's the best practice?
An organization is itself a group of repositories.
You can manage team access to an organization repository or to all repositories, not to a group of repositories inside that organization.
You would need to define one organization per group of repositories in order to grant access for said groups.
Related
Is there a way to list all repositories within an organization, created or contributed to by a specific user?
For concreteness, I am a member of the organization and I am the user in question.
The organization page has a ton of repos listed and I just want to see the ones that I made.
I can see that it's possible to change the owner of an organization, and I can also add users to the Project Collection Administrators group so that they get most administrative rights, but cannot find how to add multiple owners to the organization.
You cannot have multiple owners for the Azure Devops Organization.
According to Create and configure organization FAQs:
Q: How many organization Owners can I have?
A: Your organization can have only one owner. Only organization Owners can do certain actions, so make sure you keep your organization Owner updated.
On GitHub, a user can belong to multiple organizations. Is it possible for a repository to be part of multiple organizations as well?
According to this blog post by GitHub, a repository can only belong to one organization.
Creating an organization helps you centralize your organization’s code. All repositories live under the organization, and billing goes through a central organization account.
You can fork one organization's repository into another organization's space, but the original belongs to just a single organization.
As GitHub user I can create an organization. What i don't understand -- Is an organisation independent?
Is it a repositories container, that needs a (user) account it belongs to or
is it for itself an (organization) account GitHub user (and doesn't need any personal user account)? Is it then correct to say, that an organization is a "featured user" account -- an account with all the features of a personal user account (especially code management, commenting etc.) and some additional functionality?
The biggest difference between user accounts and organizations is team-based permissions for the repositories owned by the organization.
This means you can have team members under your organization and let them interact more aggressively with your repositories compared to plain contributors.
I'd say the concept of a GitHub organization is pretty independent from a plain GitHub user - they aren't the same thing. See for example how you can convert a user to an organization https://help.github.com/articles/converting-a-user-into-an-organization/
With that being said, organizations have what they call owners.
You can have multiple owners (i.e you can invite people to be owner of your organization along with you) but an organization cannot have zero owner.
For example, when you create an organization while logged under your account, the default first owner of the organization you just created is yourself.
Here's a more detailed list about the differences between a user and an organization
https://help.github.com/articles/what-s-the-difference-between-user-and-organization-accounts/
An organization is not a user, it doesn't have a password and you cannot log into an organization like you can to a personal/user account. But an organization can own repositories, which can be made accessible to actual persons/users who have passwords and can login.
I have a main repo that students are forking to do their homework. From the student's view of the repo, the list of collaborating teams is small (their individual team and my teacher team). However, from my view (as admin), there is a long list of teams with access. As a result, students are able to see within other students' private repos.
What is the correct way to manage this so that teams can fork a main repo, and limit access to that repo among teams.