Skip to content

GitHub Personal Access Token (PAT)

This guide explains how to try CloudAEye using a GitHub personal access token when you do not have permission to install the CloudAEye GitHub App for your organization.

Overview

A personal access token (PAT) lets CloudAEye access the repositories you authorize through your GitHub account, without requiring you to install the GitHub App. This can be useful for evaluating CloudAEye while waiting for an organization administrator to approve app installation.

Use a fine-grained personal access token. PAT access is a alternative with limitations, not a replacement for the full GitHub App integration.

Prerequisites

  • Register with CloudAEye and sign in to the console.
  • Have access to the GitHub repositories you want to evaluate.

Your organization may restrict PAT access or require approval.

Connect with a PAT

Create a fine-grained token first, then follow the steps for either initial onboarding or the Code Review Integrations page.

Create a Fine-Grained Token

  1. In GitHub, open Settings > Developer settings > Personal access tokens > Fine-grained tokens, then select Generate new token.
  2. Give the token a descriptive name, such as CloudAEye Trial.
  3. Select an Expiration appropriate for your evaluation. Choose the maximum expiration allowed by your organization.
  4. Select the Resource owner that owns the repositories, then allow access to repositories you want to evaluate.
  5. Under Repository permissions, grant the following permissions:
Permission Access
Contents Read-only
Metadata Read-only (included automatically)
Administration Read and write
Commit statuses Read and write
Pull requests Read and write
Webhooks (repository hooks) Read and write

During Initial Onboarding

Use this flow when setting up Code Review for the first time.

Step 1: Select GitHub Token

In Setup Code Review, select GitHub Token and click Next.

Select GitHub Token

Step 2: Connect the GitHub Token

Paste the token and click Save Token.

Connect GitHub Token

Step 3: Select GitHub Repositories

Select the repositories you want to integrate with CloudAEye Code Review.

Select GitHub Repositories

Follow GitHub Repository Integration to select branches and App Names, then save the mapping.

From the Code Review Integrations Page

Use this flow to connect GitHub after initial onboarding. You must have permission to manage GitHub connections.

Step 1: Open GitHub Connect

Open Code Review > Integrations. On the GitHub card, click Connect.

GitHub card with Connect and Docs buttons on the Integrations page

Step 2: Choose Personal Access Token

In the Connect GitHub modal, select Personal access token and click Continue. The other option, GitHub App, starts the GitHub App installation flow.

Connect GitHub modal with Personal access token selected

Step 3: Add the GitHub Token

In the Add GitHub Token dialog, paste your token into Fine-grained personal access token and click Add Token. The dialog lists the required repository permissions for Code Review.

Add GitHub Token dialog with the token field and required repository permissions

Step 4: Select GitHub Repositories

After the token is added, the GitHub Repositories page shows the token connection and its available repositories.

GitHub Repositories page showing a token connection and available repositories

Follow GitHub Repository Integration to select repositories, branches, and App Names, then save the mapping.

If GitHub is already connected, click Repos on the GitHub card, then Add Token to add another token connection.

Limitations

  • Personal access: The token cannot grant more access than its owner has. Access can stop if the owner loses access to a repository.
  • Organization approval: PAT restrictions and approval requirements still apply.