Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support --unshallow on fetch

See original GitHub issue

I use IndexedDB backend. Browser storage’s quota is restricted up to 6% of user storage(HDD/SSD). https://developer.chrome.com/apps/offline_storage

I want to reduce cloned data volume so I use { singleBranch: true, depth: 1 } at first to show rapidly. But users need history later by git fetch <ref> --unshallow

# man git-fetch
       --unshallow
           If the source repository is complete, convert a shallow repository to a complete one, removing
           all the limitations imposed by shallow repositories.

           If the source repository is shallow, fetch as much as possible so that the current repository
           has the same history as the source repository.

P.S. git.clone looks unstable yet. It’s one of reason I use singleBranch, depth: 1. Some tree objects are broken after clone (or not implemented format?). Do you plan to improve them after https://github.com/isomorphic-git/isomorphic-git/pull/138 ?

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

jcubiccommented, Sep 2, 2018

Should you add next-editor to list of projects then? @mizchi maybe you should create PR with this file updated with your project https://github.com/isomorphic-git/isomorphic-git.github.io/edit/source/website/users.js

0reactions

wmhiltoncommented, Sep 2, 2018

Added to the FAQ! https://isomorphic-git.org/docs/en/faq

Top Results From Across the Web

git-fetch Documentation - Git

Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. This option can...

Cancel "git fetch --unshallow" - Stack Overflow

So I used git fetch --unshallow upstream (upstream being the boilerplate origin), however, as expected, it loaded all the commits from the ...

git fetch --unshallow no longer working · Issue #4942 - GitHub

The command "if [[ -a .git/shallow ]]; then git fetch --unshallow; fi" failed and exited with 128 during .

depth=1 to git fetch --unshallow. does it do just the diff

Now I tried to unshallow the repo. ~/games/flare-game$ git fetch --unshallow remote: Counting objects: 29729, done. remote: Compressing objects: 100% ...

Push rejected, source repository is a shallow clone ...

I'm getting error Push rejected, source repository is a shallow clone. Unshallow it with git fetch --all --unshallow and try pushing again.