Copilot CLI in GitHub Actions: No PATs Needed

The Copilot CLI no longer requires a personal access token when used in GitHub Actions. Now, you can run it with the built-in GITHUB_TOKEN. This change removes the need to create and store personal access tokens, which helps reduce security risks. When you use the Copilot CLI with the Actions token in an organization's repository, AI credits are billed directly to that organization. To enable this, you must activate the "Allow use of Copilot CLI billed to the organization" Copilot policy. This policy is enabled by default if the "Copilot CLI" policy is already active. Workflows then only need "copilot-requests: write" permission and can authenticate with the workflow’s GITHUB_TOKEN. To manage costs when billing to your organization, you can configure cost centers or monitor Copilot usage from your organization's billing dashboards. You can also set a session limit to control the maximum AI credits a workflow will use. This update simplifies security and billing for automated Copilot CLI operations.