Deferral is the Future milestone, and a closed thread still takes comments - #1471
Merged
Merged
Conversation
…ments Two corrections from #1468. `Not now` went with the issue-type migration and I replaced it with "closed as not planned", which is wrong in the other direction: an idea whose time has not come goes to the **Future** milestone and stays open, where it is searchable and where the planning already lives. CONTRIBUTING says that, and the working practice in AGENTS.md says it beside the assignee rule, which is where an agent looks when it is deciding what to do with an issue it is not taking. And the sweep: a comment arrives on a merged pull request and on a closed issue as readily as on an open one, while a sweep that lists what is open misses it -- which is how a correction sat unanswered until the maintainer opened an issue asking whether closed threads are read at all. The comment endpoints are not filtered by state, so the rule is to sweep them by time, from the last sweep rather than from the session's start, and to read what comes back before picking up the next piece of work. Part of #1468. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura
Happypig375
reviewed
Sep 22, 2026
| as that: an assignment is a priority, never a lock, and an assigned issue with no open | ||
| pull request is free to whoever opens one -- a note on the issue is polite, and enough. | ||
| - **Deferral is the `Future` milestone.** An issue nobody is taking up yet stays open and | ||
| goes there; closing it as not planned loses it, and there is no `Not now` label any more. |
Member
There was a problem hiding this comment.
Suggested change
| goes there; closing it as not planned loses it, and there is no `Not now` label any more. | |
| goes there; closing it as not planned loses it. |
This label has no relevance to the future
…m the sentence Happypig375 on #1468: an untriaged issue is typed, milestoned and labelled by the reply that engages with it, not by a later pass -- a separate pass is one more thing to forget, and leaves the tracker wrong until it runs. A pull request is not triaged, since it carries the issue it is `Part of` and a type on it would be that issue's type written twice; a discussion is triaged by its category, and what it needs is an answer, with an issue only if work came of it. And the review's suggestion: the `Not now` label has no relevance to the Future milestone, so the sentence no longer mentions it. Part of #1468. Co-Authored-By: Claude Opus 5 (1M context) <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
2 participants
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 from #1468.
Deferral.
Not nowwent with the issue-type migration and I replaced it in #1384 with "closed as not planned", which is wrong in the other direction: an idea whose time has not come goes to the Future milestone ("All ideas that aren't just yet relevant, but maybe at time point will") and stays open, where it is searchable and where the planning already lives.CONTRIBUTING.mdsays that now, and the working practice inAGENTS.mdsays it beside the assignee rule — which is where an agent looks when deciding what to do with an issue it is not taking.Closed is not finished. A comment arrives on a merged pull request and on a closed issue as readily as on an open one, and a sweep that lists what is open misses it. The comment endpoints are not filtered by state, so the rule is now to sweep them by time (
issues/commentsandpulls/commentswithsince=<last sweep>), from the last sweep rather than from the session's start, and to read what comes back before picking up the next piece of work — a reply that waits for the end of a measurement is a reply you have already had to chase.The other two items of #1468 — the label review and whether the four issue templates should exist at all — are answered on that issue, since one of them is destructive and the other is a judgement I would rather put to you than make silently.
Part of #1468.
🤖 Generated with Claude Code
https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura