Menu
I'm confused about github machine users. I want to add an ssh key with read only rights to my repo to use for automation and have it tied to my repository/organization. But it seems like I need to create an actual github user that is not scoped to anything. I'm referring to where you add a collaborator by "Search by username, full name or email address". This seems like a poor match for what I'm trying to do. Is there a way to create a machine user that can be managed by the organization without creating a github user?
834
Method 1: Machine user To set up a GitHub machine user: On your agent machine, generate a key as per the agent SSH keys documentation. Sign up to GitHub as a new user (using a valid email address), and add the SSH key to the user's settings.
Signing up for a new accountGo to GitHub's Pricing page. Read the information about the different products and subscriptions that GitHub offers, then click the upgrade button under the subscription you'd like to choose. Follow the prompts to create your personal account or organization.
A machine user is a GitHub user that you create for running automated tasks. By using the SSH key of a machine user, you allow anyone with repository access to build, test, and deploy the project. Creating a machine user also reduces the risk of losing credentials linked to a single user.
You need a GitHub account, which you can create for free at GitHub.com. I advise to install GitHub Desktop. This is a graphical user interface that makes working with Git much easier. If you use GitHub Desktop, you don't need to do any command-line operations.
It's a sine qua non that an ssh key is associated with a user, so you must create a user. See https://developer.github.com/v3/guides/managing-deploy-keys/#machine-users
GitHub says it's "totally cool" to create a single machine user for automation.
178
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
