chore(rfd): Keep triage in the active drafting session - #822
Merged
Conversation
`just rfd-triage` now prefers the session's active conversation over starting a separate `rfd-triage:<id>` conversation. When a session already has an active conversation (typically the agentic session that drafted the RFD), it prompts whether to triage there, keeping the accumulated context, or fall back to a new/continued titled triage conversation. Declining, or running outside a TTY, keeps the previous behavior of resolving or creating `rfd-triage:<id>`. The separate `rfd-apply` recipe is folded into `rfd-triage`, since apply now runs in whichever conversation triage used, rather than requiring a pre-existing `rfd-triage:<id>` conversation to resume. Signed-off-by: Jean Mertz <git@jeanmertz.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
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.
just rfd-triagenow prefers the session's active conversation over starting a separaterfd-triage:<id>conversation. When a session already has an active conversation (typically the agentic session that drafted the RFD), it prompts whether to triage there, keeping the accumulated context, or fall back to a new/continued titled triage conversation. Declining, or running outside a TTY, keeps the previous behavior of resolving or creatingrfd-triage:<id>.The separate
rfd-applyrecipe is folded intorfd-triage, since apply now runs in whichever conversation triage used, rather than requiring a pre-existingrfd-triage:<id>conversation to resume.