Skip to main content
The GitHub control under a Righthand’s Manage area uses a GitHub personal access token (PAT). It does not use the OAuth app policy described in older versions of this guide.

​
Before you begin

  • Use a GitHub account that represents the Righthand if you want a separate audit trail.
  • Invite that account to the organization or repositories it needs.
  • Decide which repositories and actions the Righthand should be allowed to access.
  • Keep the account’s password and recovery methods in a team-controlled password manager.

​
Create and connect the token

1

Create a fine-grained token

While signed in to the intended GitHub account, open GitHub’s token creation page. Choose the appropriate resource owner, select only the required repositories, grant the minimum permissions needed for the Righthand’s work, and set an expiration.GitHub documents the complete flow in Managing your personal access tokens.
2

Complete organization approval

If the resource owner is an organization that requires approval, ask an organization owner to approve the pending fine-grained token request. Until approval, the token cannot access the organization’s private resources.
3

Open GitHub in Righthand

Go to Righthands, select the Righthand, then open Manage → GitHub.
4

Save the token

Paste the token into the masked Token field and select Save. Righthand verifies the token before marking the integration active.
5

Verify access

Confirm that the GitHub pane shows Active and the expected GitHub account. Ask the Righthand to read a known repository before assigning write work.
Treat a PAT like a password. Paste it only into Manage → GitHub. Never send it to the Righthand in a message or store it in a repository.

​
Organization approval

If a fine-grained token is pending, a GitHub organization owner can review it under the organization’s Settings → Personal access tokens → Pending requests. GitHub’s guide is Managing requests for personal access tokens.

​
Replace or disconnect a token

The GitHub pane shows Needs attention when a token has expired or cannot be verified.
  • Select Replace token to paste and verify a fresh token.
  • Select Disconnect to remove GitHub access from the Righthand.
  • Rotate the token before its expiration date to avoid interrupted work.

​
Troubleshooting

Confirm that the GitHub account can access the repository, that the token’s repository selection includes it, and that the token has the permissions required for the attempted action.
Ask a GitHub organization owner to approve the fine-grained token request. A pending token can read public resources but not the organization’s private resources.
Create a fresh token, select Replace token, and verify the connection again. Revoke the old token in GitHub if it is no longer needed.