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.
Related
I want to know if there is a way to give access to a private repository to people who don't have a GitHub account. Like a link, app or integrating the GH account to some platform like Teams or Slack. The people I intend to share code with share a Microsoft Teams team with me and a corporation mail name#comapny.com. Secure an official suggestions only please.
If your goal is to give them access to clone a repository but not otherwise interact with it, then you can use read-only deploy keys to allow them to clone and fetch the repository via SSH.
Otherwise, if you need more access, then each user will need to have their own GitHub account. It's intentional that users need their own accounts to properly enforce access controls and 2FA policies and to permit users to block and report bad actors. GitHub does not permit accounts to be shared.
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.
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?
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'm part of a GitHub organization developing a FOSS project. I'd like to run CI tests on Windows using AppVeyor. Currently I see my own fork of the project, and some other forks from people who have named me collaborator in GitHub. I don't see the upstream of the project, though. Apparently me being an administrator of the GitHub organization isn't enough to offer access to it in AppVeyor. But probably setting this up under my account would be the wrong approach anyway. Probably this should be under the name of the organization.
Towards that end, I'd like to have an AppVeyor account for this organization, with suitable permissions for its members. Reading http://www.appveyor.com/docs/team-setup it sounds as if AppVeyor could distinguish between users (with unique email and password) and accounts (to which projects belong), and a single user apparently can belong to multiple accounts while one account can have multiple users with different roles. In that sense, I'd like to create a new account without creating a user for it. Instead I as an existing user, identified by GitHub login, would like to become the first administrator of this new account, and ready to change settings and add more users. How do I do this?
You can't create a new account without a user. Just use some your email/password to create an account, then add existing user as collaborator.