ci: keep Docs Bot so automation still starts Test - #1192
Merged
cursor[bot] merged 2 commits intoSep 14, 2026
Merged
cursor[bot] merged 2 commits into
cursor[bot] merged 2 commits into
Conversation
GITHUB_TOKEN events do not start other workflows. Restore the Docs Bot GitHub App token so llms.txt commits and automation PRs still run Test. Co-authored-by: Anirudh Kamath <kamath@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
kamath
marked this pull request as ready for review
September 14, 2026 23:51
GITHUB_TOKEN pushes and PRs do not start other workflows. Keep Test running on llms.txt commits and automation PRs by locking those workflows to the Docs Bot GitHub App token.
cursor
Bot
merged commit Sep 14, 2026
22e9c85
into
teallarson/simplify-ci-env-vars
3 of 4 checks passed
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.
Fixes the Bugbot finding on #1190:
GITHUB_TOKENpushes and PRs do not start other workflows.What I verified
GitHub does not start workflows from
GITHUB_TOKENevents (exceptworkflow_dispatch/repository_dispatch).#1190 switched
llmstxt,generate-toolkit-docs, andupdate-design-system-dependencytoGITHUB_TOKEN. The test artifact from that change, #1191, was opened bygithub-actions[bot]and never ran Test. Its checks are only Vercel, Bugbot, and a skipped reindex — so the required check is missing on that SHA.The same gap hits human PRs: an
llms.txtcommit pushed withGITHUB_TOKENcreates a new head SHA with no follow-up Test run.I also ran the new workflow-token tests against #1190's YAML: all three files use
secrets.GITHUB_TOKENand none use./.github/actions/app-token.What changed
Restore the Docs Bot GitHub App token (
.github/actions/app-token) for those three workflows. App-token events are not subject to theGITHUB_TOKENrestriction, so Test still runs on the new SHA.Add contract tests so a later cleanup cannot drop Docs Bot again:
tests/docs-automation-tokens.test.tstoolkit-docs-generator/tests/workflows/generate-toolkit-docs.test.ts#1190's other CI cleanup is unchanged.
How to verify
main).generate-toolkit-docsand confirm the automation PR runs Test, unlike [AUTO] Adding MCP Servers docs update #1191.