Repository navigation
Conversation
Adds a no-secrets build check for PRs, which the drafts opened by the fil-one docs sync workflow rely on, and tells reviewers and agents how those drafts are handled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
bajtos
reviewed
Oct 22, 2026
bajtos
left a comment
Contributor
There was a problem hiding this comment.
It's a great idea to add a CI!
A few more suggestions to consider as follow-ups:
- Configure Dependabot to automatically update the pinned actions and also npm dependencies. See https://github.com/fil-one/fil-one/blob/main/.github/dependabot.yml for inspiration.
- Change the branch protection ruleset to require passing CI checks before a PR can be merged.
This branch was successfully deployed
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.
This is the docs-repo half of the docs sync system in fil-one/fil-one#881. That workflow drafts docs.fil.one updates from product PRs and opens them here as draft PRs on
docs-sync/fil-one-<PR#>branches..github/workflows/build.yamlrunsnpm ci --ignore-scripts && npm run buildon every PR and on pushes tomain. It has a read-only token and no secrets, because a PR's MDX runs during the build. Actions are pinned by SHA.AGENTS.mdgets a section on drafted PRs. The bot may edit onlydocs/**and the two llms mirrors. It lists other changes under "Manual follow-ups" and claims it couldn't confirm under "Needs verification". The drafts stay as drafts until the product PR merges. Pushing a commit to the branch takes it over from the bot.No docs content changes, so
llms.txtandllms-full.txtare unchanged.npm run buildpasses locally.Manual setup still needed in this repo (details in
docs/DocsSync.mdin fil-one/fil-one#881):mainruleset's bypass list.docs-synclabel.🤖 Generated with Claude Code