From 5a2d24bac751247af22f7bc2fc91cb56bdddb8d7 Mon Sep 17 00:00:00 2001 From: Cliff Hall Date: Tue, 28 Apr 2026 15:59:26 -0400 Subject: [PATCH] docs(agents): require version label on new issues and PRs (#1257) * docs(agents): require version label on new issues and PRs (#1256) Recent v2 PRs (#1247, #1249, #1250, #1252, #1255) all landed without a v2 label, making version-filtered queries unreliable. Codify the expectation directly in the issue-driven workflow: each branch / board gets a fixed label, and the label is set at create time via the gh create flag rather than backfilled. Co-Authored-By: Claude Opus 4.7 (1M context) * Also fix stale "PR against main" line The PR-target line still said "Open a PR against main", which is correct only for v1 work. Mirror the version-label mapping above so the PR base matches the board. Co-Authored-By: Claude Opus 4.7 (1M context) --------- Co-authored-by: Claude Opus 4.7 (1M context) --- AGENTS.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index e96f6b24..d8bdf97a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -48,10 +48,16 @@ All work should be driven by items on the project board. - Before starting work, check the board for the relevant item. - **Draft items vs. issues**: Board items may be draft items (no issue number) or full GitHub issues. Before creating a new issue, always check if a matching draft item already exists on the board. If it does, convert it to an issue using `gh project item-edit` or create the issue and link it — **never create a duplicate**. +- **Label by version.** New issues and PRs must carry the label matching the target board / branch: + - `main` → `v1` + - `v1.5/main` → `v1.5` + - `v2/main` → `v2` + + Set the label at create time (`gh issue create --label v2 ...`, `gh pr create --label v2 ...`) — don't rely on backfilling later, since unlabeled PRs are easy to miss when filtering by version. - When work begins, create a feature branch and move the item to "In Progress". - When work is complete: - Run format, lint, typecheck, build, and test — ensure all checks pass - - Open a PR against `main` and move the item to "In Review" + - Open a PR against the matching base branch (`main` for v1, `v1.5/main` for v1.5, `v2/main` for v2) and move the item to "In Review" - If new tasks are discovered or requested during development, create issues and add them to the board. ### Always test new or modified code