Preserve cached PR pane links on completed labels#312
Merged
Conversation
Owner
Author
Pull Request Review
The code change itself is narrowly scoped and the relevant pane-link test passes; Unplaced findings
|
Owner
Author
[Agent] Updated the PR description with root-cause context: |
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
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.
Summary
Preserve cached PR links when repo cleanup keeps a completed tmux window label.
Why
Brian noticed Pi/tmux sessions could keep the completed PR label but lose the clickable PR URL from the footer after cleanup. The root cause was that repo-end preserved the completed window label while unconditionally clearing the pane PR link state.
Approach
Capture the cached pane link before clearing worktree state and restore it only for the completed-window-label path when it came from the PR-status cache.
Related PRs
Verification
Reviewer Notes: Review found no actionable correctness issues.