PAT for Webhook configuration (Code version control systems)

Modified on Wed, 1 Oct at 6:23 AM

This article provides an overview of the steps required to create a Personal Access Token (PAT) for enabling Webhooks in GitHub, GitLab, and Bitbucket to support near-instant code analysis.

Steps to be performed in the Cubyts platform

Step 1: Sign-in to Cubyts platform and click on the integration trigger as indicated in the image shown below:

Step 2: Click on the “Configure” button in the VCS webhooks section as indicated in the image shown below:

Step 3: Configure the tokens (as per the tool) and click on the connect button as shown in the image below:

If you are using Github then:

Create a fine-grained token with access to the required organization.
Select relevant code repositories and configure the following permissions:
- Read access to code (contents) and metadata.
- Read & Write access to issues, pull requests and repository hooks (web hooks).
- Note: You must be an admin of the selected repositories.

If you are using Gitlab then:

Create a personal access token (or project access token if you are a paid subscriber of Gitlab).
Select relevant code repositories and configure the following permissions:
- Read_api, and api.
Note: You must be a maintainer or admin of the selected repositories.

If you are using Bitbucket then:

Create a new API token with the following scopes:
- Read permission: repository, pull request, webhook.
- Write permission: pull request, webhook.
- Delete permission: webhook.
Note: You must be an admin of the selected repositories.

Step 4: Click on “Add webhooks” for all the configured repositories, this action will automatically configure the webhooks and the Cubyts platform will be ready to perform instant code analysis (as soon as a push from the IDE is done by a developer).

Note: Please note that this action will set up webhooks for the selected repositories across all Cubyts workspaces where the repositories are connected or configured.