Document kosli_github_token secret and its required permission#19
Merged
Conversation
The Secrets table did not list `kosli_github_token`, and the example caller workflow did not show passing the token or granting the `pull-requests: read` permission. As a result, anyone copy-pasting the example and later wiring up the PR attestation step hits a confusing `Resource not accessible by integration` failure. Add `kosli_github_token` to the Secrets table, add the secret and the permission to the example caller workflow, and explain why both sides of a reusable workflow must grant the permission. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ToreMerkely
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
kosli_github_tokento the Secrets table in the README — previously it was only documented in the workflow file itself.pull-requests: readpermission, so anyone copy-pasting it doesn't later hitResource not accessible by integrationwhen wiring up the PR attestation step.pull-requests: read, since GitHub computes the token's permissions in a reusable workflow as the intersection of the two.Companion to #18 (which restores the permission on the called side).
Test plan
kosli attest pr githubsucceeds.🤖 Generated with Claude Code