Repository navigation
Separate milestones from triage in the contributing guide - #19
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
dansabin
approved these changes
Oct 13, 2026
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.
Why
Triage step 5 required a milestone for every kept issue, which forced inventing a milestone before there was a clear goal. Today's triage of eight issues showed that triage and planning are different activities on different cadences.
What
Triage now ends with keep or close; a kept issue takes a milestone only when a goal already has one, and otherwise waits in the backlog. Milestones are made in a separate planning pass.
Changes
.github/CONTRIBUTING.mdand add two sentences to "Labels and milestones" saying milestones come from a planning pass that pulls issues from the backlog. Triage is the rigour, done often and quickly; milestones are a separate planning process at its own cadence, and an issue does not need one to be triaged..claude/specs/contributing-guide/to match, so the spec and the guide do not disagree.Testing
make validate: 9 unit tests OK, both validators passed. Read the changed guide section back.Risk and rollout
None.
🤖 Generated with Claude Code