ci: push bot-generated docs straight to main instead of opening PRs#12
Conversation
regenerate-llms and sync-default-configs now commit their generated output (llms.txt / llms-full.txt and node/node-operators.mdx) directly to main when something changes, instead of opening a fresh bot PR each run. Keeps the PR list uncluttered. Permissions narrowed to contents: write since no PR is created. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PR SummaryMedium Risk Overview Reviewed by Cursor Bugbot for commit d6e6967. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
What
regenerate-llms.ymlandsync-default-configs.ymlnow commit their generated output directly tomainwhen something changes, instead of opening a fresh bot PR on every run.regenerate-llms→llms.txt/llms-full.txtsync-default-configs→node/node-operators.mdxEach replaces the
peter-evans/create-pull-request@v6step with a guarded commit-and-push: it no-ops if nothing changed, commits asgithub-actions[bot], rebases onorigin/mainto absorb any concurrent push, then pushes tomain. Permissions narrowed fromcontents: write+pull-requests: writedown to justcontents: write.Why
These bot PRs (e.g. #10) were piling up requiring a manual merge and inflating the PR count. The content is fully machine-generated (plaintext
llms.txt, marker-bounded TOML blocks), so a per-PR review gate added noise without much safety. Mintlify still redeploys on every push tomain, andlink-checkstill sweepsmaindaily via its cron, so nothing material is lost.🤖 Generated with Claude Code