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

Option to reorder repositories in Source Control Repositories view #146359

Closed
ruxpendp opened this issue Mar 30, 2022 · 1 comment
Closed

Option to reorder repositories in Source Control Repositories view #146359

ruxpendp opened this issue Mar 30, 2022 · 1 comment
Assignees
Labels
feature-request Request for new features or functionality on-testplan scm General SCM compound issues
Milestone

Comments

@ruxpendp
Copy link

With the 1.66.0 release, the SCR view was changed to always sort repositories by name. Previously they would appear in the order they were discovered by vscode.

The old behavior was billed as a feature (e.g. comment), and I preferred that behavior because my multi-folder workspaces usually contain a primary git repo (that I put at the top) and a few ancillary ones.

So the minimum viable feature request would be to:

  • have a vscode setting that allows switching between the new and old behaviors

But the "best QoL" feature request would be to:

  • have repos initially sorted by name
  • be able to drag to reorder repos in the SCR view (and the multi-folder workspace would remember the order)
@lszomoru
Copy link
Member

Today's Insiders release (2022-04-14), contains two changes related to repository sorting:

  • The default sorting was reverted to be by discovery time, which was the original behaviour
  • A new setting scm.repositories.sortOrder was added that can be used to control the repository sorting (discovery time, name, path)

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-testplan scm General SCM compound issues
Projects
None yet
Development

No branches or pull requests

2 participants