Adding repos separately clears clone path of other repos when cloning

[MattVon]

Dev Home version

0.601.297.0

Windows build number

10.0.22631.2506

Other software

OS Build Version: 10.0.22631.2506.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.23

Steps to reproduce the bug

Go to Machine configuration > Clone repositories

First part

• Click "+ Add repository"
• Select a single repository to clone (in my testing, I am cloning from my "Account")
• Leave Path as default value
• Click "Add"

Once added you will be redirected back to the Clone repositories page, from here do the following

Second part

• Click the pencil icon against the repo to edit it
• Change the clone path to something different
• Click "Save"

Once changed, repeat the First part and at the point of clicking "Add" the repo is added to the clone repositories list and any previous repos which had an edited clone path, are all reset to the default value when they were saved.

Expected result

Any previous repositories in the list to maintain their clone path without being reset to their default value

Actual result

Any previous repositories in the list are reset to the default value, presumably the value that could have been set from when originally adding the repo.

Included System Information

Physical Memory: 31.92GB (20.92GB free)
Processor Architecture: x64

Included Extensions Information

Extensions:
Microsoft.Windows.DevHome_0.601.297.0_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_0.600.283.0_x64__8wekyb3d8bbwe

[hamnarauf]

This has been fixed in #1766. Hopefully, this PR will be included in the next release and cloning into different locations won't be an issue.

[krschau]

Duplicate of #1387

[microsoft-github-policy-service]

We've identified this as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your report!