Git: Close Repository reopens right after
See original GitHub issueVersion: 1.49.2
Commit: e5e9e69aed6e1984f7499b7af85b3d05f9a6883a
Date: 2020-09-24T16:23:52.277Z (8 hrs ago)
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 18.7.0
Steps to Reproduce:
Help > Report
didn’t work 😕
Steps to Reproduce:
- I’m connecting to a Remote-SSH vagrant host
- I’m closing a repository from
Source Control
->Close Repository
Does this issue occur when all extensions are disabled?: Yes/No
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:17 (2 by maintainers)
Top Results From Across the Web
How to continue in Git after closing terminal?
Closing the terminal (when no git command is currently running!) and reopening it has no effect on git, even if you reboot in...
Read more >Git changes window closes automatically
If I dock the Github changes window to the document tab well then the it closes when I do one of the following:...
Read more >Introducing new Git features to Visual Studio 2022
To checkout a previous commit in Visual Studio, open the Git Repository window View > Git Repository, right click on the commit you...
Read more >Open, reopen, and close projects | PyCharm Documentation
Specify the path to the repository and select the directory to which a project will be cloned. Alternatively, you can select GitHub on...
Read more >Working with GitHub
Reopen closed PR ; -1 · # Checkout the latest state of the PR (commit hash xxxxxxxxxxx) git checkout ; # Delete old...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm, still having this issue with VS code 1.66.0.
Is there any workaround?
Running into this problem in 2022. Was this fixed? I noticed there’s an unmerged PR.