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
Currently GitLens falls back to terminal execution for certain git commands. It was mainly done out of convenience to avoid needing to handle many error cases, but also so that the user could easily tweak the command and execute it again themselves.
We should replace those terminal-run command with custom command like all our other Git commands, though it could still be really nice to offer to open the terminal with the command as an option/button on an error dialog/notification if the user chooses.
This sounds really nice!
I assume this was prompted by the VSCode August 2024 release by the filing date, so please disregard this if so, but if not, I'd really love it if the fallback used VSCode's new Terminal shell integration API, as my shell starts up slowly and GitLens's not waiting for the prompt always messes with me :)
Thanks for GitLens! I use it everyday, the commit graph is amazing.
Currently GitLens falls back to terminal execution for certain git commands. It was mainly done out of convenience to avoid needing to handle many error cases, but also so that the user could easily tweak the command and execute it again themselves.
We should replace those terminal-run command with custom command like all our other Git commands, though it could still be really nice to offer to open the terminal with the command as an option/button on an error dialog/notification if the user chooses.
Can find all the commands that call this:
vscode-gitlens/src/env/node/git/git.ts
Line 2192 in d9a9718
Which really boils down to callers of:
vscode-gitlens/src/git/models/repository.ts
Lines 1289 to 1293 in ac7c727
Tasks
branch
terminal-run commands into normal commands w/ proper error handling #3528tag
terminal-run commands into normal commands w/ proper error handling #3529reset
terminal-run commands into normal commands w/ proper error handling #3533revert
terminal-run commands into normal commands w/ proper error handling #3530cherry-pick
terminal-run commands into normal commands w/ proper error handling #3531merge
terminal-run commands into normal commands w/ proper error handling #3532rebase
terminal-run commands into normal commands w/ proper error handling #3534This will ultimately resolve: #3364, #2889, #2664, #2607, #2541, #2444, #2312, #2057, #1901, #1450, #732, #3364, #1767
The text was updated successfully, but these errors were encountered: