`sparse` `clone` with sensible defaults
Open
Nobody has claimed this yet.
subcommand request
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
Essentially, this:
git clone --filter=blob:none --sparse
# cd repo-path
git config set merge.stat false
I explain everything here: jesseduffield/lazygit#4907
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 with the requested git clone command sequence: --filter=blob:none, --sparse, and git config set merge.stat false. Read the linked jesseduffield/lazygit#4907 discussion for the stated rationale and expected behavior. Done means the relevant git-extras functionality provides these sensible defaults and has coverage for the resulting clone behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100