docs(agents): require PR metadata (assignee, type label, milestone) — ADR-0040#92
Merged
Merged
Conversation
… ADR-0040 Agent-opened PRs carried only a title and body; GitHub's structured metadata (reviewers, assignees, labels, projects, milestone) was unset, so the PR list and release view had no type/ownership/release signal. Codify a PR-metadata rule in AGENTS.md §6.4: every PR sets a maintainer assignee (--assignee @me), exactly one type label (Conventional-Commit type -> like-named label; docs reuses the built-in `documentation`), and the current open release milestone (per-release scheme, e.g. v1.1.1; the SemVer level is decided by maintenance.md). Reviewers are deferred — the sole collaborator is the PR author and GitHub forbids self-review — and Projects are deferred until the gh token carries the `project` scope; the rule names how each switches on. Rationale and the rejected alternatives (area labels, rolling milestone, CI auto-labeler) in ADR-0040. The eight type labels and the v1.1.1 milestone were created on the repo, and PRs #89-#91 were backfilled (assignee + type label + milestone), out of band from this commit. Process/repository-metadata only; no API change. Recorded under CHANGELOG Unreleased. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Codifies a PR-metadata policy so every agent-opened PR also sets a maintainer assignee, exactly one type label (Conventional-Commit type → label), and the current open release milestone. Process/repository-metadata only — no code/API change.
Motivation
PRs carried only a title and body; GitHub's structured metadata (reviewers, assignees, labels, projects, milestone) was unset, leaving the PR list and release view without a type/ownership/release signal. Requested by the maintainer; recorded as ADR-0040.
Changes
AGENTS.md§6.4 — the PR-metadata rule + the Conventional-Committype→ label map + the canonicalgh pr createinvocation; a metadata checkbox added to the PR body template.docs/adr/0040-pull-request-metadata-policy.md— decision + rejected alternatives (area labels, rolling milestone, CI auto-labeler, forced reviewer), indexed.CHANGELOG.md—UnreleasedAddedentry.feat/fix/refactor/perf/test/build/chore/ci;docsreusesdocumentation) and thev1.1.1milestone, and backfilled PRs docs(bugs): add in-repo bug ledger and agent triage protocol (ADR-0039) #89–docs(journal): add 2026-06-15 bug-ledger session checkpoint #91 with assignee + type label + milestone.Design Patterns
Verification
python tools/consistency_lint.py— OKmarkdownlint-cli2clean on the four changed files@me, labeldocumentationfordocs, milestonev1.1.1)Documentation Impact
Unreleasedupdateddocumentationlabel,v1.1.1milestone (§6.4 / ADR-0040)Known gaps (documented, not oversights)
danielPoloWork) is the PR author and GitHub forbids self-review. Switches on (--reviewer …) when a second collaborator/team exists.ghtoken lacks theprojectscope. Switches on (--project …) aftergh auth refresh -s read:project,project+ a board.🤖 Generated with Claude Code