Add custom depth for git repo cloning
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I'm unable to properly get my projects to build due to using tools that read the git history to version the build - would it possible to allow for custom depth options rather than hardcoding it to 1?
Describe the solution you'd like
I would like for a setting to be added for git cloning to allow cloning deeper than depth 1.
Describe alternatives you've considered
There are no good workarounds for this beyond completely altering how the code is versioned.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
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
The issue names no files or tests. Start by locating the repository-cloning entry point and its current depth-1 option, then trace how clone settings are configured. Done means users can select a deeper clone depth and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100