feat: label session branches by first message - #449
Open
111-test-111 wants to merge 1 commit into
Open
Conversation
Extract the session-tree projection into lib/project-tree.ts and keep the first message entry of each diverging arm, so BranchNavigator can label each branch with the message it diverged with. BranchNavigator renders those first-message labels and supports multi-root trees.
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.
What
Makes in-session branches recognizable in
BranchNavigator:app/api/sessions/[id]/route.tsintolib/project-tree.ts(identical iterative algorithm — no behavior change)messageentry of each diverging arm, so the UI can label a branch with the message it diverged withBranchNavigatorrenders those labels and supports multi-root treesNotes
tsc --noEmitand eslint clean.app/api/sessions/[id]/route.ts, and the companion context-usage PR touches the same file's imports/response — the second one to land may need a trivial rebase.