[plan] Add 'Why a separate token?' explanation for COPILOT_GITHUB_TOKEN in Quick Start Step 2

[github-actions]

Objective

Add a brief 1–2 sentence "Why a separate token?" explainer before the COPILOT_GITHUB_TOKEN PAT creation steps in Quick Start Step 2.

Context

Discussion #43686 (Documentation Noob Tester report, issue #3) flagged that the note currently says "a separate GitHub token with Copilot access — distinct from the default GITHUB_TOKEN" with no further explanation. For a beginner, the existence of two different GitHub tokens is confusing without context for why they are different.

File to Modify

docs/src/content/docs/setup/quick-start.mdx

Implementation Plan

Approach

1. Open quick-start.mdx and find the COPILOT_GITHUB_TOKEN Note block.
2. Before the PAT creation steps, add a short callout or sentence such as:

   Why a separate token? The default GITHUB_TOKEN provided by Actions has limited scopes and cannot call the GitHub Copilot API. A Personal Access Token (PAT) with Copilot access lets the workflow authenticate to the AI engine on your behalf.

3. Keep it brief — 2 sentences maximum — to avoid adding too much prose to an already dense step.

Files to Modify

• docs/src/content/docs/setup/quick-start.mdx

Acceptance Criteria

• A 1–2 sentence "Why a separate token?" explanation is present before the COPILOT_GITHUB_TOKEN PAT creation steps
• The explanation clearly distinguishes GITHUB_TOKEN from a PAT
• No other content is changed in the file

Generated by 📋 Plan Command · 27.1 AIC · ⌖ 10.7 AIC · ⊞ 4.9K · ◷
_{Comment /plan to run again}

• expires on Jul 7, 2026, 9:34 PM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 4.32 AIC · ⌖ 3.94 AIC · ⊞ 3.6K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-07-08T05:34:55.614Z.

Closed by Workflow