From 2b42b3fe3da249ff89a9dd3498a8f06d5de28fab Mon Sep 17 00:00:00 2001 From: Richard Levasseur Date: Sat, 22 Aug 2026 12:08:17 -0700 Subject: [PATCH] agents: specify docs and build(release) commit types Ambiguity in commit type selection can cause issue templates or release scripts to be mislabeled under generic types like chore. Updates the agent pull request rules to specify that issue template changes use docs: and release tooling uses build(release):. --- .agents/rules/pr.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.agents/rules/pr.md b/.agents/rules/pr.md index 9e5fa9df88..ae75aa34fe 100644 --- a/.agents/rules/pr.md +++ b/.agents/rules/pr.md @@ -16,9 +16,10 @@ Before drafting any pull request description, strictly adhere to the rules in ## Commit & PR Types * `fix:` / `feat:`: User-visible changes ONLY. -* `build:` / `build(release):`: Internal release tooling, developer workflows, - and build scripts (prefer `build(release):` over `chore:` or `tools:`, since - `tools:` could be ambiguous with production tools). +* `build:` / `build(release):`: Internal release tooling + (`tools/private/release/`), developer workflows, and build scripts. Always + prefer `build(release):` over `chore:` or `chore(release):`. +* `docs:`: Documentation and issue templates (`.github/ISSUE_TEMPLATE/`). * `ci:`: `.bazelci` and Buildkite CI configurations. * `workflow:` / `workflows:`: GitHub Actions workflow configurations (`.github/workflows/`).