Allow id-token: write permission in strict mode #11307
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
id-token: writepermission enables OIDC token generation for cloud provider authentication (AWS, GCP, Azure) and doesn't modify repository content, making it safe for strict mode.Changes
id-tokenfrom dangerous permissions validator infindWritePermissions()- it now skipsPermissionIdTokenwhen checking for write permissions that require the feature flagid-token: writebehavior in both general and strict modesExample
Workflows can now use
id-token: writein strict mode for OIDC authentication:This continues to block repository-modifying permissions like
contents: write,issues: write, andpull-requests: writein strict mode.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.