Overview
How to create a GitHub Personal Access Tokens (classic) for bulk onboarding and SCM monitoring features via SCM Integrations. Monitoring includes Synchronizing Polaris with your SCM Provider and Event-Based Test Automation in Polaris for SCM Integrations.
Note: Available only for GitHub and GitHub Enterprise Cloud.
Creating a personal access token
Authentication between GitHub and Polaris is managed with a personal access token that you create in GitHub. If you haven't done so already, create an access token. For additional information: GitHub > Managing your personal access tokens.
Important: Token must be created by a GitHub Organization Owner or users with the "Manage organization webhooks" permission, who are authorized to manage organization webhooks. Although other GitHub users may be able to select the admin scope requirements when creating a token, the token will not work due to permission requirements in GitHub to manage organization webhooks.
Next Steps
Use this token to connect to Polaris:
After the connection is established:
You can also scan on demand (see How to test from the web UI) or schedule automatic testing on a daily or weekly basis (see Test scheduling policies).
Note: From the Tests screen, before beginning a test manually, make sure to test the connection.