ci: skip scenario-parity on dependabot PRs - #183
Merged
Conversation
Dependabot-triggered workflow runs don't receive repository secrets, so the create-github-app-token step fails with an empty private-key before the parity check can run — every dependabot PR fails this required-looking check. Dependency bumps can't change scenario parity, so skip the job.
eddietejeda
force-pushed
the
ci/skip-scenario-parity-for-dependabot
branch
from
September 3, 2026 00:09
984a865 to
df04c91
Compare
| # Dependabot-triggered runs don't receive repository secrets, so the App | ||
| # token mint below fails before the check can run. Dependency bumps can't | ||
| # change scenario parity, so skip instead. | ||
| if: github.actor != 'dependabot[bot]' |
There was a problem hiding this comment.
nit: Fork PRs also run without repository secrets, so scenario-parity still fails on them. (not blocking)
Widen the condition to cover forks:
Suggested change
| if: github.actor != 'dependabot[bot]' | |
| if: github.actor != 'dependabot[bot]' && github.event.pull_request.head.repo.fork != true |
On push events github.event.pull_request is null, so the added clause stays true there. The integration job comment at line 85 already records that fork PRs get no secrets.
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
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.
Dependabot-triggered runs don't get repository secrets, so the
create-github-app-tokenstep inscenario-parityfails ("The 'private-key' input must be set") on every dependabot PR — this is why #163, #164, #165, and #182 are stuck. Dependency bumps can't affect scenario parity, so skip the job for the dependabot actor.Note: sdk-rust has the same pattern in its workflow and will hit the same issue on its next dependabot PR.