An epic is a Goal used as a parent, and Future is where the next milestones come from - #1482
Merged
Merged
Conversation
…stones come from The milestone section still described the scheme #1384 replaced: epics on an `Epics` milestone, and a missing milestone as the mark of an untriaged issue. The maintainer retired that milestone when the issue types came in -- #718, #1409 and #746 were taken off it on 2026-09-22 -- and the section on types already says an issue with no *type* is untriaged, so the two parts of the file disagreed. An epic is a Goal used as a parent and carries no milestone; untriaged is the absence of a type. And the maintainer's rule from #1468: once every other milestone is done, the next milestones are planned by pulling issues from `Future`. The milestone's description now says the same. Part of #1468. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura
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
1 participant
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.
Two corrections to the milestone section of
AGENTS.md, both from #1468.The epics. The section still described the scheme #1384 replaced: epics sitting on an
Epicsmilestone, and a missing milestone as the mark of an untriaged issue. The milestone was retired when the issue types came in — #718, #1409 and #746 were taken off it on 2026-09-22 — and the section on types already says an issue with no type is untriaged, so the two parts of the file contradicted each other. It now says an epic is a Goal used as a parent and carries no milestone, and that untriaged is the absence of a type. The opening line ("every open issue is on a milestone or is visibly untriaged") gains the epic, which is neither.Future. Your rule from #1468 — once every other milestone is done, the next milestones are planned by pulling issues from
Future— is recorded beside the rest of what the milestone means. The milestone's own description now says it too, with the wording you approved there: "Deferred: ideas that are not relevant yet. An issue waits here rather than being closed as not planned, and once every other milestone is done, the next milestones are planned by pulling issues from here." Today the condition is far off —2.6.0has 25 open,2.7.017,2.85,3.028 and3.18.Part of #1468.
🤖 Generated with Claude Code
https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura