Skip to content

docs: add explicit token permissions to all caller templates - #10

Merged
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01
Aug 12, 2026
Merged

docs: add explicit token permissions to all caller templates#10
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01

Conversation

@00o-sh

@00o-sh 00o-sh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

What & why

Follow-up to the CodeQL/Scorecard template fix. The ci, commitlint, and release caller
templates now also show explicit least-privilege permissions, matching what each reusable
workflow declares:

  • ci.yml, commitlint.ymlcontents: read
  • release-please.yml, release-cut.yml, release-security.ymlcontents: write, pull-requests: write

(publish.yml already showed contents: read + id-token: write.)

With this, a fork scaffolded from these templates is fully independent of the org's default
GITHUB_TOKEN setting — the whole pipeline keeps working even if the default is tightened to
read-only. The live forks are getting the same change in their own PRs.


Generated by Claude Code

Show least-privilege GITHUB_TOKEN permissions on the ci, commitlint, and
release caller templates, matching what the reusable workflows declare, so
new forks are independent of the org default token setting.
@00o-sh
00o-sh force-pushed the claude/new-session-zrgq01 branch from d6ca915 to ca8a3b5 Compare August 12, 2026 13:17
@00o-sh
00o-sh merged commit 5a06bdf into main Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants