microsoft / microsoft/vscode-remote-release
'Clone Repository in Container Volume' should use partial clones
Open
Nobody has claimed this yet.
containers
feature-request
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
For large repositories, it'd save time to clone with --filter=blob:none. (https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/)
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 locating the implementation and tests for “Clone Repository in Container Volume,” then trace how the repository clone command is assembled. Confirm how the existing behavior handles large repositories and define done as using Git’s blobless partial-clone option while preserving the current container-volume workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100