You can limit the depth of the history while cloning:
--depth <depth>
Create a shallow clone with a history truncated to the specified
number of revisions.
Use this if you want limited history, but still some.
More Related Contents:
- How do I update or sync a forked repository on GitHub?
- How to do a GitHub pull request
- Are Git forks actually Git clones?
- How can I fork my own GitHub repository?
- How do you fork your own repository on GitHub?
- Creating a GitHub repository with only a subset of a local repository’s history
- Error when pushing amended commit to remote [duplicate]
- Git, fatal: The remote end hung up unexpectedly
- Download a single folder or directory from a GitHub repo
- Git keeps prompting me for a password
- Is it possible to create a remote repo on GitHub from the CLI without opening browser?
- Configure Git clients, like GitHub for Windows, to not ask for authentication
- Git SSH error: “Connect to host: Bad file number”
- Git push results in “Authentication Failed”
- How to recover from a git push -force?
- ‘git diff’ doesn’t show enough
- Trying To Understand/Determine A Basic Git Workflow
- Github file size limit changed 6/18/13. Can’t push now
- Trying to understand `git diff` and `git mv` rename detection mechanism
- How to merge remote changes at GitHub?
- Push to origin from GitHub action
- Git push doesnt do anything over HTTPS
- fatal: The current branch master has no upstream branch
- Create new pull request from fork without having commits of the previous fork
- How to delete the last n commits on Github and locally?
- How to merge the remote branch and ignore the config setting?
- Git: Set local user.name and user.email different for each repo
- github: server certificate verification failed
- git export from github remote repository
- Do GitHub and GitLab support git clone’s –filter parameter?