Skip to content

ci: declare explicit GITHUB_TOKEN permissions in workflows - #15

Draft
son-oz wants to merge 1 commit into
mainfrom
chore/explicit-workflow-permissions
Draft

ci: declare explicit GITHUB_TOKEN permissions in workflows#15
son-oz wants to merge 1 commit into
mainfrom
chore/explicit-workflow-permissions

Conversation

@son-oz

@son-oz son-oz commented Aug 29, 2026

Copy link
Copy Markdown

The product-security baseline rollout will set the repository default GITHUB_TOKEN permissions to read-only (with PR-approval by the token disabled). Workflows that rely on the current implicit write default would start failing at their next write operation. This PR makes each workflow's required permissions explicit so the downgrade is a no-op for this repo.

Workflow Declared permissions
.github/workflows/pr-title.yaml contents: read

Scopes were inferred from the actions and commands each workflow uses; read-only workflows get contents: read. Draft on purpose — please review before marking ready.

🤖 Generated with Claude Code

Prepares for the org-wide default GITHUB_TOKEN permission downgrade to read-only by declaring each workflow's required permissions explicitly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant