fix the git sparse checkout handling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
The old versions of the path-specific pull/clone's using sparse checkouts were buggy, I changed them with clone/pull that pulls the entire repo, which isn't really desired.
Contributor guide
No contributing guide indexed for this repository
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
Read the implementation of the path-specific pull and clone commands and trace their sparse-checkout handling. Reproduce a path-limited operation and compare it with the current behavior that pulls the entire repository. Done means path-specific operations use sparse checkouts correctly without downloading the full repository, with relevant test coverage if tests exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100