-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'git checkout' in quickOpen (Ctrl+P) #24408
Comments
Probably related to the new git SCM provider that is enabled by default. Please see #24141 and Microsoft/vscode-docs#931. The new git SCM provider is not yet final so this should be reintroduced in future updates. |
Yeah this behaviour is now gone since it's unavailable to extensions, which git has now become. |
@joaomoreno Is there a plan to re-introduce it in a future update? |
Needs API advancements. It should be possible in the future. But not a very near one. |
@joaomoreno @borekb I could add a "checkout" or "branch switch" command in GitLens in the mean time -- did the old Git extension do anything special to handle error cases? (like if there were uncommitted changes)? I've been a little hesitant to provide "destructive" operations in GitLens, but since I've already recently added support for stash apply, pop, & delete, this really isn't too different. |
Code comes with a checkout command. What the user asks for is the ability to type |
@joaomoreno oh I see. So no type of extension can provide that, sorry. I completely missed the built-in EDIT: Never mind on the Git not working -- it was my issue, when I was debugging an extension the new Git extension seems to trigger an unhandled exception (that it didn't used to before today's update) when finding Git, and I didn't notice that I had typed into that file when the exception popped up -- which killed things from then on. |
Can you file an issue for that unhandled exception? 👍 |
Filed: #24482 |
To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed. Thanks for your understanding. Happy coding! |
In VSCode 1.10 and earlier, I could do
Ctrl+P
,git checkout
and it would offer me the list of branches. It was a very nice and smooth workflow.In VSCode 1.11, this seems to be gone. The new "Git: Checkout to..." is the replacement.
Is there any chance that the original way would be reintroduced (maybe the current state is just a limitation of the SCM provider infrastructure), or is it going to stay the way it is?
Note: somewhat related is #21439 (Can no longer create branch).
The text was updated successfully, but these errors were encountered: