Get Your GitHub Credentials
How to get your GitHub organization slug and create a GitHub Personal Access Token.
Last updated
Was this helpful?
How to get your GitHub organization slug and create a GitHub Personal Access Token.
Last updated
Was this helpful?
For Warp to be able to migrate your repositories to GitHub, it needs two key pieces of information:
The destination organization slug, which is the part of the organization’s webpage’s URL that uniquely identifies the organization.
A Personal Access Token (PAT) for your GitHub user account, which grants the bearer the necessary privileges to migrate repositories to the organization.
At the end of this section, you will have the slug for your GitHub organization and a Personal Access Token for your GitHub account.
🛠️ Switch to the browser tab or window containing Migration HQ.
Make a note of the URL in your browser’s address bar. The URL contains the organization slug, which is the part of the URL that uniquely identifies the organization. It’s the part of the URL after github.com/ and before /Migration-HQ:
In this example, the URL for the organization’s page is:
The organization slug is the part that comes after github.com/ and before /Migration-HQ, which means that this example’s organization slug is:
🛠️ Copy the organization slug from your browser’s address bar and paste it someplace safe — you’ll use it when you create the vault file.
🛠️ Switch to the browser tab or window containing Migration HQ and click on your profile picture (located near the top right of the page) so that this menu appears:
🛠️ Select Settings from the menu.
You will be taken to the Settings page for your GitHub account:
🛠️ Scroll down the page until you see the Developer settings item appear in the list on the left side:
🛠️ Click on Developer settings.
This will take you to the Developer Settings page:
🛠️ In the menu on the left side of the page, expand the Personal access tokens item:
🛠️ Select Tokens (classic) from the menu.
You will end up at the Personal access tokens (classic) page:
Towards the top right of the page, you’ll see the Generate new token button.
🛠️ Click the Generate new token button to make its menu appear:
🛠️ ...then select Generate new token (classic) from the menu.
You will arrive at the New personal access token (classic) page, where you’ll need to provide enough information to create a new personal access token:
🛠️ Enter a name or some other text to help you identify the token in the Note field. To make it easier to identify, we suggest you include “Warp” in the name:
For the purposes of this Quickstart, we’ll leave the Expiration field at the default value of 30 days.
🛠️ Under Select scopes, check the following boxes. Checking these boxes will automatically check their sub-boxes:
repo
workflow
write:packages
delete:packages
admin:org
🛠️ Then scroll down the page and check these boxes. Once again, checking these boxes will automatically check their sub-boxes:
admin:repo_hook
admin:org_hook
delete_repo
Feel free to use the checklist below to double-check that you’ve checked all the necessary checkboxes. It’s important to make sure you’ve checked all of them!
🛠️ Scroll to the bottom of the page and click the Generate token button:
You should now see this page, which will display the personal access token you just created:
🛠️ Copy the token and save it in a safe place — preferably a password manager.
You now have the information needed to connect Warp to GitHub.
You should confirm that you have all the credentials you need for migration.
Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow.
This will be the only time that this Personal Access Token will be presented to you.
Make sure you’ve copied it someplace safe before clicking the Close button!
