I need to have multiple people work on a private repository and was wondering why anyone would pay 9$/user as an organization if one can just have a single paid user with a private repository who adds other users as collaborators?
Related
I have connected my personal GitHub account to the company I am working at. if I change anything in the organization related repositories, my colleagues will receive a notification about that but what if I change my own repositories which belong my account? is there anyway that my colleagues receive notification about my own repositories?
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.
When you remove a user from an organization, GitHub warns you that all their forks of the organisation's private repos will be deleted
Removing people from the XX organization will also delete their forks of any private XX-owned repositories.
And GitHub tells you how many private forks the user has but it does not tell you the repo names (even though I have permission to see them!)
It would be useful to see the repos so that I can check that they really have no outstanding, potentially useful, work left on branches (that they have not opened pull-request for).
To do it from the Web U:
Go to the people tab of the organization (https://github.com/orgs/myorg/people).
Filter/find the person.
Click their name; this will take you to https://github.com/orgs/myorg/people/theirusername, which lists all repos they have access to, including repos in the organization and forks the user has made of them.
Filter the list by their username; this will show just the forks.
This requires owner permissions for the organization.
There's a GitHub API to list all the forks. I haven't tested the API but I assume that you will get ONLY the public forks for other users and all the forks if you're the authenticated user.
If you wanted to query this on behalf of other users you can work on a GitHub Integration that would get users' permissions via OAuth and then you could store that information on your side for a whole group of people.
I don't think this is what you were asking for but additionally there's a WEB UI filter for forked repositories, e.g., https://github.com/defunkt?utf8=%E2%9C%93&tab=repositories&q=&type=fork.
My personal GitHub account is a member of an organization account which can create private repositories, and of which I am also an owner (but with a different username). I am trying to create a private repo while logged in from GitHub Desktop while logged in to my personal account. However, the private repository option is disabled, even after I choose the organization as the owner, as shown below.
So I have to log in to the organization account before the private option is enabled.
I can create a private repo normally from a browser, however.
Other following operations (e.g. commits) seem to be fine once I get the write permission.
So do I miss a step here? Or is this intentionally disabled in GitHub desktop?
Considering organizations only proposes private repos under a paid plan, maybe your personal account is not associated with a private account, while your other account owner of the organization is.
The web interface might have (on GitHub side) all the information to link the two accounts, but GitHub Desktop might not (locally) have that same information and might lack the API to query it.
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.