Configuring your GitHub OAuth2 token

Ebert requires a GitHub® OAuth2 token with the repo and write:repo_hook scopes enabled so we can interact with your repositories and install some webhooks to fetch your code when we review it.

It’s only required that the account you use to create the token have admin permissions on the repositories you want to review with Eber and, although allowed, there is no need to create your token with the same GitHub® account you’ve used to log in to Ebert.

Creating your token on GitHub

To create your GitHub® OAuth2 token, follow the step by step below:

1. Visit your GitHub’s personal access tokens page.
2. Give a description for your token so you can easily know it was created for Ebert.
3. Check the repo and the write:repo_hook scope (as shown in the image below) and click on Generate token.
4. Make sure to copy your token after that. You won’t be able to see it again later.

Adding your token to your Ebert account

After creating your token, you must set it to your Ebert account. To do so, follow the steps below:

1. From your Dashboard page, click on the Account integrations link below the name of the account for which you want set the token.
2. On the GitHub OAuth2 Token section, Paste your token into the input field.
3. If your token has the right scopes, you will see which GitHub user owns the token.
4. Click on Add GitHub token and you will be all set.

As well as you can’t see previously created tokens on GitHub, you won’t be able to see them here. You can, however, update it anytime you need.

Next, review your first repository →