microsoft / microsoft/winget-cli-restsource
Cloning the Repo in VS 19 and 22
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 317
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Brief description of your issue
when Cloning the repo "Git failed with fatal error. the remote end hung unexpectedly" Clone succeeded, but checkout failed. the remote end hung up unexpectedly
Steps to reproduce
Use clone from Repo on VS 19 or VS 22
Expected behavior
The repo is to be cloned and loaded into a solution within Visual Studio.
Actual behavior
No solution, error message shows when Cloning the repo "Git failed with fatal error. the remote end hung unexpectedly" Clone succeeded, but checkout failed. the remote end hung up unexpectedly
Environment
Windows 10 10.0.19043 build 19043
Windows 11 10.0.22000 build 22000
Visual studio v19 & V22 (tested with)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the clone and checkout failure from Visual Studio 19 or 22 on Windows 10 or 11, using the environment details in the issue. No files or tests are identified; done means the repository clones, checks out successfully, and loads into a solution without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100