Skip to content

docs(#6243): broaden doc-update rule to cover behavior and format changes - #6245

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/6243-broaden-doc-update-rule
Open

docs(#6243): broaden doc-update rule to cover behavior and format changes#6245
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/6243-broaden-doc-update-rule

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Broadens the AGENTS.md doc-update rule to trigger when a code agent changes the behavior or output format of a CLI command, public API, or user-facing feature — not just when removing or renaming one. This prevents stale documentation from reaching review, as happened in PR #6239 where the REF column format changed but docs/cli/repos.md was not updated.

Changes

  • Amended the doc-update bullet in AGENTS.md from "removing or renaming" to "removing, renaming, or changing the behavior or output format"
  • Updated the action clause from "references to the old name and update or remove them" to "references and update them to reflect the current behavior" to match the broader trigger
  • Trimmed "that walk through the removed workflow" since the rule now covers more than just removals

Testing

  • Verified new phrasing "changing the behavior or output format" is present in AGENTS.md
  • Verified old narrow phrasing "When removing or renaming a CLI command" is no longer present
  • Gitlint passes on commit message

Checklist

  • PR title follows Conventional Commits (correct type, ! for breaking changes)
  • Single-line edit — no behavioral code changes

Closes #6243

Post-script verification

  • Branch is not main/master (agent/6243-broaden-doc-update-rule)
  • Secret scan passed (gitleaks — f7b794dca167e312fda418b0fd92aa60db00987a..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

…nges

Amend the existing AGENTS.md doc-update rule to trigger on behavior
and output format changes, not just removals and renames. The prior
wording ("removing or renaming") missed cases where a code agent
changed CLI output format (e.g., PR #6239 changed the repos status
REF column format without updating docs/cli/repos.md). The review
agent caught the stale doc, but the code agent should have grepped
docs proactively.

The updated rule now reads: "When removing, renaming, or changing
the behavior or output format of a CLI command, public API, or
user-facing feature, grep all documentation files under docs/ for
references and update them to reflect the current behavior."

Closes #6243
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner August 14, 2026 23:22
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Agent PR ready for human review label Aug 14, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 14, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 11:24 PM UTC · Completed 11:36 PM UTC

Commit: 418aaaa · View workflow run →

@codecov

codecov Bot commented Aug 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium


Labels: PR is a pure documentation change to AGENTS.md governance file

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

Comment thread AGENTS.md
- Never commit secrets (tokens, API keys, PEM keys, gcloud credentials) or sensitive data (GCP project names, service account identifiers, Model Armor template names, internal hostnames). Use environment variables with no defaults for sensitive values.
- When adding a new doc under `docs/`, check `docs/.vitepress/config.ts` sidebar config. Sections using `getMarkdownFiles()` are auto-discovered. All other sections need a manual `{ text, link }` entry. Also add the new folder's prefix to `search.options.scopes` in the same file so the folder's pages are reachable when search scope pills are active.
- When removing or renaming a CLI command, public API, or user-facing feature, grep all documentation files under `docs/` for references to the old name and update or remove them. Pay special attention to `docs/cli/`, `docs/guides/`, and any getting-started or operations guides that walk through the removed workflow.
- When removing, renaming, or changing the behavior or output format of a CLI command, public API, or user-facing feature, grep all documentation files under `docs/` for references and update them to reflect the current behavior. Pay special attention to `docs/cli/`, `docs/guides/`, and any getting-started or operations guides.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[medium] protected-path

This PR modifies AGENTS.md, which is a protected governance file. The change is well-justified by issue #6243 (broadening the doc-update rule to also cover behavior and output format changes, motivated by a concrete gap identified in PR #6239). Human approval is always required for protected-path changes, regardless of justification.

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment documentation labels Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation ready-for-review Agent PR ready for human review requires-manual-review Review requires human judgment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broaden AGENTS.md doc-update rule to cover behavior and output format changes

0 participants