ci: don't run the PR-review job on Dependabot PRs - #74
Merged
Conversation
The review job already skips fork PRs because repo secrets aren't exposed to them. Dependabot PRs hit the same wall — GitHub runs them with a restricted token and withholds secrets — but they come from a same-repo branch, so they passed the fork guard and ran anyway, failing every time on the missing CLAUDE_CODE_OAUTH_TOKEN. That painted a red X on otherwise green dependency bumps. Extend the guard to skip dependabot[bot] too (a clean skip, not a failure), and group the weekly CI Action bumps into a single PR so they're easier to review and merge together.
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
1 participant
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 automated PR-review job already skips fork PRs — GitHub doesn't expose repo secrets to them, so
CLAUDE_CODE_OAUTH_TOKENis absent and the job can only fail. Dependabot PRs hit the exact same wall (restricted token, no secret access), but they're raised from a same-repo branch, so they slipped past the fork guard, ran, and failed every time — painting a red ✗ on dependency bumps whose real checks (build & test, CodeQL, govulncheck) all pass.This:
reviewjob's guard to also skipdependabot[bot]— a clean skip, not a failure (dependency PRs are still reviewable on demand via an@claudecomment, which runs in the base-repo context where the secret exists);No effect on human-authored PRs — the review job runs on those exactly as before.