Skip to content

fix: check-suite-success trigger uses token without actions permission#310

Merged
zbigniewsobiecki merged 1 commit intodevfrom
fix/check-suite-trigger-actions-token
Feb 16, 2026
Merged

fix: check-suite-success trigger uses token without actions permission#310
zbigniewsobiecki merged 1 commit intodevfrom
fix/check-suite-trigger-actions-token

Conversation

@zbigniewsobiecki
Copy link
Copy Markdown
Member

Summary

  • The check-suite-success trigger calls getCheckSuiteStatus() which uses the Actions API (/actions/runs), but the default project GITHUB_TOKEN is a fine-grained PAT without actions permission → 403
  • The trigger already resolves the review agent's credential override (aaight's classic PAT with repo scope) for the review identity check — now also uses it for the actions API call via withGitHubToken
  • Follows up on fix: review agent uses wrong GitHub identity (agent credential override ignored) #308 which fixed the agent-level credential override

Test plan

🤖 Generated with Claude Code

…igger

The check-suite-success trigger calls getCheckSuiteStatus() which hits
the Actions API (workflow runs endpoint). The default project GITHUB_TOKEN
is a fine-grained PAT that lacks the actions permission, causing a 403.

Use the review agent's credential override (classic PAT with repo scope)
for this call, since the trigger already resolves it for the review
identity check.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@zbigniewsobiecki zbigniewsobiecki merged commit f8b4233 into dev Feb 16, 2026
4 checks passed
@zbigniewsobiecki zbigniewsobiecki deleted the fix/check-suite-trigger-actions-token branch February 16, 2026 19:48
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.

1 participant