GitHub Copilot Token

This guide walks you through creating an organization-scoped, fine-grained personal access token (PAT) for use by Milestone when use of Milestone App is not permitted.

Create GitHub Copilot access token

Before you start:


Step-by-step: Create the token

  1. Open the fine-grained token page GitHub → Your profile (top-right) → Settings → Developer settings (last option on the side menu) → Personal access tokens → Fine-grained tokens → Generate new token. https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens

  2. Name & description

  • Token name: Milestone’s Copilot Token (read-only)

  • Description: Token to be used by Milestone integration to gather metadata and generate analytics.

  1. Expiration

  • Choose 1 year.

  • If your org allows longer, you may choose “No expiration”; if your org enforces a shorter maximum, coordinate with an org owner to adjust the maximum lifetime policy. (GitHub Docs)

  1. Resource owner

  • Select your organization as Resource owner (the token will only access resources owned by that org).

  • If your org doesn’t appear, it may have blocked fine-grained PATs — ask an org owner to allow them. (GitHub Docs)

  1. Repository access

  1. Permissions

  • In Permissions, set the following to Read. These map to GitHub’s fine-grained permission model for API and Git read access. (GitHub Docs)

  1. Organization permissions (Read):

  • Members: Read (lets Milestone read the org’s members list when needed). (GitHub Docs)

  • GitHub Copilot Business: Read (lets Milestone query Copilot business seats and metrics).

  1. Generate

  • Click Generate token and store it on the machine where Milestone will be setting up their services. If your org requires approvals, the token will show as pending and will only access public resources until approved by an org owner. (GitHub Docs)


Last updated