Ability to clone repos with `git clone --depth 1`

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, go
Domain
cli, performance

Research direction

The issue names no files, tests, or entry points; start by locating the repository-cloning path in this Go CLI and reviewing how git clone options are assembled. Check the expected shallow-clone behavior for the optional deadline/latest-commit cases, then verify that depth 1 works without breaking existing modes.

Written by the indexing model from the issue text.

Description

I only need the latest commit state at the deadline (optionally - #16 ), or the latest commit (optionally). With 100s of repos, a shallow clone will likely increase performance for many users of this tool.

Dominant language
Go
Stars
126
Forks
21
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-classroom

All issues in github/gh-classroom

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.