You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can tell, the Delete Branch option does not show up for branch A if you start on branch A, switch to branch B, and then try to use the Delete Branch option.
This may be related to using the built-in source control feature to switch branches instead of using the GitLens Branches view. Once I used the Refresh button on the Branches view, the "Delete Branch" option appeared on the inactive branch A.
In the Branches view after performing a Refresh of the view, GitLens seems to not realize that the current branch is active after performing a switch.
E.g. Switch from "initial-release" to "main", Git reports "main" as the current branch, but the Branches view still allows me to attempt to switch to the "main" branch (note that the switch branch button is enabled for both branches):
When I use the button to switch to the "main" (current) branch, it asks which branch I want to switch to (not the normal behavior for this button). When I use the button to switch to the "initial-release" (inactive) branch, it switches to that branch right away (as expected), but then the Branches view disables the switch button for the "main" (now inactive) branch, and the switch button for the "initial-release" (now current) branch remains enabled. Refreshing the Branches view returns the button states to the example image (both enabled; not expected behavior).
Description
Might be a regression of #3582
From what I can tell, the Delete Branch option does not show up for branch A if you start on branch A, switch to branch B, and then try to use the Delete Branch option.
This may be related to using the built-in source control feature to switch branches instead of using the GitLens Branches view. Once I used the Refresh button on the Branches view, the "Delete Branch" option appeared on the inactive branch A.
In the Branches view after performing a Refresh of the view, GitLens seems to not realize that the current branch is active after performing a switch.
E.g. Switch from "initial-release" to "main", Git reports "main" as the current branch, but the Branches view still allows me to attempt to switch to the "main" branch (note that the switch branch button is enabled for both branches):
When I use the button to switch to the "main" (current) branch, it asks which branch I want to switch to (not the normal behavior for this button). When I use the button to switch to the "initial-release" (inactive) branch, it switches to that branch right away (as expected), but then the Branches view disables the switch button for the "main" (now inactive) branch, and the switch button for the "initial-release" (now current) branch remains enabled. Refreshing the Branches view returns the button states to the example image (both enabled; not expected behavior).
GitLens Version
15.6.2
VS Code Version
Version: 1.94.2 (system setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045
Git Version
git version 2.39.2.windows.1
Logs, Screenshots, Screen Captures, etc
No response
The text was updated successfully, but these errors were encountered: