Copilot CLI no longer needs a PAT in GitHub Actions

GitHub simplified running Copilot CLI in CI: workflows no longer need to create and store long-lived personal access tokens (PATs).

Key points

• Copilot CLI can now run in GitHub Actions using the built-in GITHUB_TOKEN, removing the need for a PAT.
• Workflows only need the copilot-requests: write permission and can authenticate with the built-in token — no extra secrets.
• When run with the Actions token in an org-owned repo, AI credits are billed directly to the organization (requires the "Allow use of Copilot CLI billed to the organization" policy, on by default if the Copilot CLI policy is enabled).
• Spend can be controlled via cost centers, billing/usage dashboards, and per-workflow session limits.