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

[Insiders] Broken Submodule Source Control view order #145886

Closed
dchennaraidu opened this issue Mar 23, 2022 · 4 comments
Closed

[Insiders] Broken Submodule Source Control view order #145886

dchennaraidu opened this issue Mar 23, 2022 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality scm General SCM compound issues
Milestone

Comments

@dchennaraidu
Copy link

dchennaraidu commented Mar 23, 2022

Issue Type: Bug

  1. Create a repo with name B
  2. Create another repo with name A (Any repo name lexically smaller than first repo)
  3. Add second repo (A) as submodule in B repo

Actual: In Source Control Side bar repo A is shown at the top

Desired: Repo B should be at the top followed by repo A

VS Code version: Code - Insiders 1.66.0-insider (2eebd2a, 2022-03-23T05:27:08.615Z)
OS version: Darwin arm64 21.4.0
Restricted Mode: No

System Info
Item Value
CPUs Apple M1 Pro (8 x 24)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 6, 5, 4
Memory (System) 16.00GB (0.07GB free)
Process Argv --crash-reporter-id 31040e07-41d1-42ee-ad16-eae0b78a5016
Screen Reader no
VM 0%
Extensions (20)
Extension Author (truncated) Version
pgformatter bra 1.18.0
npm-intellisense chr 1.4.1
vscode-sql-beautify cla 0.3.5
vscode-markdownlint Dav 0.46.0
vscode-eslint dba 2.2.2
gitlens eam 12.0.5
vscode-npm-script eg2 0.3.24
prettier-vscode esb 9.3.0
copilot Git 1.9.5350
vscode-pull-request-github Git 0.38.1
vscode-nuget-package-manager jmr 1.1.6
vscode-oracle-format mp 0.1.5
csharp ms- 1.24.1
vscode-postgresql ms- 0.3.0
azure-account ms- 0.10.1
test-adapter-converter ms- 0.1.5
polacode pnp 0.3.4
vscode-xml red 0.19.1
synthwave-vscode Rob 0.1.11
markdown-preview-enhanced shd 0.6.2

(1 theme extensions excluded)

@lszomoru lszomoru added the scm General SCM compound issues label Mar 24, 2022
@dchennaraidu
Copy link
Author

dchennaraidu commented Mar 26, 2022

Kindly observe the repositories order

1.65.2: c722ca6
image

1.66.0-insider: c63ed49
image

Change Log: c722ca6...c63ed49

@dchennaraidu
Copy link
Author

Seems because of this change #145264

@lszomoru
Copy link
Member

@dchennaraidu, we did indeed recently adjusted the order in which source control repositories are being displayed in the "Source Control Repositories" and "Source Control" views. To give you a little context, historically repositories were being showing in the order in which they were discovered. This worked well for folders/workspaces with a small number of repositories, but it certainly looked random (as discovery order can vary) for folders/workspaces with a large number of repositories and it was a real pain point.

We are considering providing more control over sorting the list of repositories other than by their name.

@lszomoru lszomoru added the feature-request Request for new features or functionality label Mar 30, 2022
@lszomoru lszomoru added this to the Backlog milestone Mar 30, 2022
@lszomoru
Copy link
Member

Closing this issue as duplicate of #146359

@lszomoru lszomoru added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 31, 2022
@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality scm General SCM compound issues
Projects
None yet
Development

No branches or pull requests

2 participants