Currently the readme advises using a PAT to allow Copilot to be used: https://github.com/github/copilot-release-notes#authentication
However, for most use cases when using workflows it's a better practice to have the workflow run under the repo's budget rather than as an invidiual user (which would use their AI credits and would break if they left / lost their copilot license / etc).
Is it worth updating the root README.md with a note on using the job's permissions to enable copilot-requests: write for this, per guidance: https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli-in-actions#recommended-approach-github-agentic-workflows
Currently the readme advises using a PAT to allow Copilot to be used: https://github.com/github/copilot-release-notes#authentication
However, for most use cases when using workflows it's a better practice to have the workflow run under the repo's budget rather than as an invidiual user (which would use their AI credits and would break if they left / lost their copilot license / etc).
Is it worth updating the root README.md with a note on using the job's permissions to enable
copilot-requests: writefor this, per guidance: https://docs.github.com/en/copilot/how-tos/copilot-cli/use-copilot-cli-in-actions#recommended-approach-github-agentic-workflows