Skip to content
Plinger.Docs
Dashboard
Getting started / GitHub PAT

CONNECT YOUR WORK

Create your GitHub PAT

Give Plinger access to track your issues and support approved developer and agent work.

What is a PAT?

A Personal Access Token is a secret credential that tools can use to access GitHub as you. Plinger uses yours to find assigned issues, pull requests, and their connections. Authorized Plinger admins can retrieve it for approved work by developers and agents.

This guide uses a classic token for the GitHub CLI workflow across repositories. GitHub generally recommends fine-grained tokens, but documents limitations for contributions across organizations and public repositories you don’t own. Compare token types.

Generate your token

  1. 1

    Open token settings

    Sign in to your scouter GitHub account. Go to Settings → Developer settings → Personal access tokens → Tokens (classic).

  2. 2

    Choose a classic token

    Select Generate new token → Generate new token (classic). Complete any authentication prompt.

  3. 3

    Name it and set expiration

    Enter any Note you like, such as “Plinger”. For this setup, choose No expiration. This means no scheduled expiry; GitHub recommends expiring tokens, and organization policies may require one.

  4. 4

    Select your scopes

    Use the checklist below, then select Generate token.

  5. 5

    Copy the PAT immediately

    Copy the complete token and keep it securely for the next step. You won’t be able to reveal that same value again after leaving the page.

Based on GitHub’s token-creation guide. Checked 14 October 2026.

Open GitHub token settingsOpens in a new tab so you can follow this guide

Which scopes should you select?

For the classic-token GitHub CLI setup, select repo, read:org, and gist. These are the minimum scopes documented for GitHub CLI’s token login; they aren’t all needed just to display public issues in Plinger.

repoSELECT

Repository access for work such as pushing code and managing pull requests. This is broad: it covers public and private repositories your account can access.

read:orgSELECT

Read organization and team membership. Find read:org under admin:org and tick only read:org, leaving admin:org and write:org unchecked.

gistSELECT

Allows writing GitHub gists, which are shared snippets. Included here for GitHub CLI token-login compatibility.

workflowSELECT

Add this when the developer or agent needs to create or update GitHub Actions workflow files, such as automated tests in .github/workflows.

Leave other scopes unchecked unless a specific task requires them. Broad admin scopes and delete_repo aren’t needed for routine issue and pull-request work. GitHub’s scope reference.

Watch the walkthrough

Follow the video here. Use the scope checklist above for Plinger’s setup if the video selects different permissions.

If the embedded player is unavailable, open the video on YouTube (new tab).

Ready to continue?

Make sure the token belongs to the same GitHub account you use to sign in to Plinger. Keep the complete value copied, then open your dashboard and choose GitHub PAT to save it.

NextCreate your Plinger accountInstall the App, sign in, and save your details
PreviousCreate a Drips Wave account