Configuring your GitHub OAuth2 token
SourceLevel requires a GitHub® OAuth2 token with the
scopes enabled so we can interact with your repositories and install some
webhooks to fetch your code when we review it.
📣 The GitHub® account you use to create the token will be the one commenting on your Pull Requests
We highly recommend you to use the OAuth2 token from a GitHub® account that represents a bot or an automation for your organization (like an acme-sourcelevel-bot account) instead of a token from your personal account or from some of your team members.
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 SourceLevel.
Creating your token on GitHub
To create your GitHub® OAuth2 token, follow the step by step below:
- Visit your GitHub’s personal access tokens page.
- Give a description for your token so you can easily know it was created for SourceLevel.
- Check the
write:repo_hookscope (as shown in the image below) and click on Generate token.
- Make sure to copy your token after that. You won’t be able to see it again later.
Adding your token to your SourceLevel account
After creating your token, you must set it to your SourceLevel account. To do so, follow the steps below:
- From your Dashboard page, click on the Account integrations link below the name of the account for which you want set the token.
- On the GitHub OAuth2 Token section, Paste your token into the input field.
- If your token has the right scopes, you will see which GitHub user owns the token.
- 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 →