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

SCM: Bring back SCM Providers view #104151

Closed
joaomoreno opened this issue Aug 6, 2020 · 7 comments
Closed

SCM: Bring back SCM Providers view #104151

joaomoreno opened this issue Aug 6, 2020 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality on-release-notes Issue/pull request mentioned in release notes scm General SCM compound issues verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@joaomoreno
Copy link
Member

From #102118

Let's bring back the SCM Providers view:

  • It should look and feel the same as before
  • Its selection should reflect the visibility of the repositories in the SCM View, instead of messing around with view panes

This will make it easier to manage many repositories.

@joaomoreno joaomoreno added feature-request Request for new features or functionality scm General SCM compound issues labels Aug 6, 2020
@joaomoreno joaomoreno added this to the August 2020 milestone Aug 6, 2020
@joaomoreno joaomoreno self-assigned this Aug 6, 2020
@joaomoreno
Copy link
Member Author

joaomoreno commented Aug 11, 2020

Pushed: 4cd3ec3

Good news

recording (18)

  • The Source Control Repositories view is now back (it used to be called Source Control Providers. It lets you control visibility of multiple repos in the Source Control view.
  • The setting scm.repositories.visible is now back (it used to be called scm.providers.visible).
  • I've sprinkled visibility actions both in the context menu of the Source Control view as well as the ... menu, to make it easier to control the visibility without using the Source Control Repositories view.
  • This will all be available in the next Insiders, hopefully this week.

Bad news

I'm out on vacation until the end of the month so no more work will happen this month here apart from critical bugfixing. Here's the state for now:

  • The workbench opens the exact same way as today. On any given workspace, one must make the Source Control Repositories view visible manually. Once visible in a workspace, it will remain visible. I expect this to change and make the view visible depending on (1) the stored visibility state or (2) the number of repositories.
  • No repository visibility state is stored yet. On reload, they will all be loaded once again. I expect this to change to simply remember which repositories were visible since the last session, per workspace.

@bpasero
Copy link
Member

bpasero commented Aug 14, 2020

Very cool, I think this solution is elegant, will selfhost on it and report back if I find issues.

@michaelhays
Copy link

michaelhays commented Aug 21, 2020

Thank you for this!

There were a lot of (understandably) critical comments on #102118, so I just wanted to reiterate our appreciation for listening and bringing this functionality back.

@joaomoreno
Copy link
Member Author

@michaelhays Thanks for the kind words 🙏

@joaomoreno joaomoreno added the verification-needed Verification of issue is requested label Aug 31, 2020
@bpasero bpasero added the verified Verification succeeded label Sep 1, 2020
@joaomoreno joaomoreno added the on-release-notes Issue/pull request mentioned in release notes label Sep 7, 2020
@raschan
Copy link

raschan commented Sep 18, 2020

Thank you, for more or less bringing back the old View of the SCM panel, I really appreciate it 🙏

I still have one detail, that is bothering me a lot: in the old view, all the options and extensions were only visible on the "Changes" pane, leaving the different repos looking clean. My major problem with new look was this clean space got cluttered, and sadly this change doesn't really solve that.

I'm not sure if it is doable, but if it is, could we please have it back that all the various options are:
a) selectable (so I can turn it off, if I don't need it)
b) only appear on the selected Source Controls and not in the Source Control Repositories section.

Until this can happen (or confirmed that it is impossible), I'm gonna go back to 1.46, hopefully temporary.

for reference, this is how it looks like for me:
Screenshot 2020-09-18 at 16 26 38

and how it looked like in 1.46
Screenshot 2020-09-18 at 16 39 50

@pd93
Copy link

pd93 commented Sep 18, 2020

My thanks to you too for allowing us to choose which view we use. I much prefer the old UI.

However, I agree with everything @raschan said. The Source Control Provider list is way too cluttered with all those icons. Combined with a long branch name this results in it hiding the name of repo which makes it even more confusing. It also stops me from being able to easily select the repos I want to see. I just end up clicking the branch name by accident every time which brings up the branch selection drop-down.

@astrowonk
Copy link

My thanks to you too for allowing us to choose which view we use. I much prefer the old UI.

However, I agree with everything @raschan said. The Source Control Provider list is way too cluttered with all those icons. Combined with a long branch name this results in it hiding the name of repo which makes it even more confusing. It also stops me from being able to easily select the repos I want to see. I just end up clicking the branch name by accident every time which brings up the branch selection drop-down.

I also agree but this probably would be better to open as its own issue, @raschan, than to post here in this closed one.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality on-release-notes Issue/pull request mentioned in release notes scm General SCM compound issues verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants