Repository navigation
fix: update token for bot_updater - #244
Merged
Merged
Conversation
The workflow referenced steps.generate-token.outputs.token, but no step with that id exists (introduced in #178). create-pull-request fails with "Input 'token' not supplied", so the excluded rules table and deprecated rules were never updated automatically.
erickzanardo
approved these changes
Oct 9, 2026
4 tasks
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.
Status
READY
Description
The
bot_update_exclusionsworkflow has failed on 199 of its last 200 runs (the only success, on 2026-08-17, was a run with nothing to change):Both
create-pull-requeststeps use${{ steps.generate-token.outputs.token }}, but no step hasid: generate-token(the reference came in with #178). The expression evaluates to an empty string. So whenever the bot found drift, it never opened a PR, and the README excluded-rules table went stale (fixed in #243). The deprecated-rules step comes after the failing step, so it never ran either.This switches both steps to the org's
VGV_BOT_PATsecret, which is whatvery_good_cli's bot workflows use.Type of Change