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.

Sign up for GitHub

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

Jump to bottom

No way to identify the source control provider when only one git repo is shown in a multi root workspace #39688

Closed
sandy081 opened this issue Dec 5, 2017 · 1 comment
Closed

No way to identify the source control provider when only one git repo is shown in a multi root workspace #39688

sandy081 opened this issue Dec 5, 2017 · 1 comment
Assignees
@joaomoreno
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues *out-of-scope Posted issue is not in scope of VS Code scm General SCM compound issues
Milestone
Backlog

Comments

@sandy081
Copy link
Member

sandy081 commented Dec 5, 2017

  • Open a MR workspace with at least two folders
  • Disable git in one of the folders

In SCM view, you cannot determine for which folder the active source control provider is for.
@sandy081 sandy081 added git GIT issues scm General SCM compound issues labels Dec 5, 2017
@joaomoreno joaomoreno added this to the Backlog milestone Dec 5, 2017
@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Dec 5, 2017
@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joaomoreno joaomoreno

Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues *out-of-scope Posted issue is not in scope of VS Code scm General SCM compound issues
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@joaomoreno @sandy081