docs: propose auto-approve conditions for docs PRs - #1186
Draft
teallarson wants to merge 1 commit into
Draft
Conversation
Records the risk tiers we want to sort docs PRs into, ahead of building the workflow that enforces them. Sits under .github/auto-approve/ so the policy lands next to the mechanism once that mechanism exists. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
teallarson
marked this pull request as ready for review
September 9, 2026 17:22
teallarson
marked this pull request as draft
September 9, 2026 17:24
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
1 participant
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.
Records the risk tiers we want to sort docs PRs into, ahead of building the workflow that enforces them.
Nothing is enforced by this PR — it's a proposal to react to. The tiers:
package.jsonMerging stays a human action either way, as in the monorepo and www.
Placed at
.github/auto-approve/README.mdrather thanCONTRIBUTING.mdso the policy sits next to the mechanism once the mechanism exists — the same layout the monorepo uses for.github/autoapprove/. Happy to move it if you'd rather it be more visible to contributors.Fuller writeup with risks, tradeoffs, and the alternatives we considered: Google Doc
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only policy proposal with no workflow or runtime behavior changes.
Overview
Adds
.github/auto-approve/README.mdto document a proposed risk tiering policy for docs PRs, ahead of any automation.Low risk (future auto-approve): human-authored changes under 300 lines with no new routes. Medium: bot PRs or human PRs that add a page or exceed 300 lines (any teammate review). Higher: toolkit gen pipeline, GitHub Actions, or
package.json(codeowner review). The doc states merging stays manual and aligns with practices in other Arcade repos; this PR does not add workflows or enforce anything.Reviewed by Cursor Bugbot for commit c23fc6c. Bugbot is set up for automated code reviews on this repo. Configure here.