Skip to content
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

Source control providers are not automatically removed when file closed #47495

Closed
Wehrdo opened this issue Apr 9, 2018 · 3 comments
Closed
Assignees
Labels
feature-request Request for new features or functionality git GIT issues *out-of-scope Posted issue is not in scope of VS Code scm General SCM compound issues
Milestone

Comments

@Wehrdo
Copy link

Wehrdo commented Apr 9, 2018

  • VSCode Version: 1.22.1
  • OS Version: Windows 10 Pro, Version 1709

Steps to Reproduce:

  1. Open a workspace that is a git repository (repository A). As expected, repository A shows up in the "Source Control Providers" list.
  2. Open a file from a different git repository (repository B), either through the "File > Open File..." menu, or by dragging onto the window. Now both repository A and repository B are listed as source control providers.
  3. Close the newly opened file.
    Expected behavior: Repository B will be removed from the source control providers list, since no folders/files from that repository are open.
    Actual behavior: Both repositories remain listed, until a restart of Visual Studio Code.

Does this issue occur when all extensions are disabled?: Yes

@vscodebot
Copy link

vscodebot bot commented Apr 9, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@vscodebot vscodebot bot added the git GIT issues label Apr 9, 2018
@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Apr 10, 2018
@joaomoreno joaomoreno added this to the Backlog milestone Apr 10, 2018
@joaomoreno joaomoreno added the scm General SCM compound issues label Apr 10, 2018
@joaomoreno joaomoreno added the *out-of-scope Posted issue is not in scope of VS Code label Sep 14, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 14, 2018

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 14, 2018
@pedzed
Copy link

pedzed commented Apr 14, 2019

I find this very annoying. Have you found a solution?

Actually, I do not want another repository to open at all. When I CTRL + O (open file), I expect to open a single file. Not the entire repository it is associated with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality git GIT issues *out-of-scope Posted issue is not in scope of VS Code scm General SCM compound issues
Projects
None yet
Development

No branches or pull requests

3 participants