From b5dda29add51051f6cd26fadbc0855ffd7f304d5 Mon Sep 17 00:00:00 2001 From: Owen McGirr Date: Sun, 13 Sep 2026 21:03:17 +0100 Subject: [PATCH] docs: require milestones when creating issues --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 2f05929f..8dd5f4f5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -9,6 +9,7 @@ The frozen C# application is not maintained in this repository. Do not reintrodu ## Workflow - Start every change with a GitHub issue and a scoped branch from current `main`. +- Never create a GitHub issue without a milestone. Select or create the appropriate milestone first and include it in the issue creation request; assigning it afterward is not allowed. This applies to every issue, including bugs, chores, release preparation, and follow-up work. Verify the milestone on the created issue before continuing. - Keep commits and pull requests focused on that issue. - Open a draft pull request with the issue-closing reference and validation evidence. - Before handoff, deploy an independent agent that did not implement the change to review the pull request's latest head, and address all actionable findings. If review fixes change the head, repeat the independent review on the new latest head.