Conversation
Previous sessions from the SDK were not enriched with worktree data (matched by cwd), so they weren't added to coveredWorktreePaths. This caused standalone worktree entries to be added on top of existing SDK sessions for the same branch. Additionally, multiple SDK sessions pointing to the same worktree were all shown as separate entries. Now only the most recent session per worktree path is kept. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Tests cover: - Enriching previous sessions with worktree data prevents standalone duplicates - Multiple SDK sessions for the same worktree are deduplicated (keep most recent) - Sessions with different worktree paths are not deduplicated Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.
No description provided.