vscode-gitlens
vscode-gitlens copied to clipboard
Commit Composer view doesn't switch when recomposing different branches
When attempting to recompose commits from different branches in sequence, the Commit Composer view doesn't refresh to show the correct branch content.
Preconditions:
- Two branches with multiple commits exist
- AI feature enabled in the system
Steps to Reproduce:
- Navigate to the commit graph
- Select branch 1 and right-click
- Choose "Recompose Commits" from context menu
- Expected: Commit Composer view for branch 1 opens
- Actual: Commit Composer view for branch 1 opens ✓
- Select branch 2 and right-click
- Choose "Recompose commits" from context menu
- Expected: Commit Composer view for branch 2 opens with auto-refresh
- Actual: Commit Composer view for branch 1 is still displayed ✗
Actual Result:
The Commit Composer view remains stuck showing the content from the first selected branch (branch 1) instead of refreshing to show the second branch (branch 2).
Expected Result:
When selecting "Recompose commits" on a different branch, the Commit Composer view should automatically refresh and display the commits from the newly selected branch.
Additional Context:
- This prevents users from efficiently working with multiple branches in the Commit Composer
- The issue suggests either a view caching problem or missing refresh trigger when switching between branches