Shallow update not allowed (git > 1.9)

Question

There are a lot of answers stating that git 1.9 removes limitations of shallow clones. Nevertheless, I'm using 2.6.1 and still having the following basic issue:

First, I create an empty repo somewhere:

cd /tmp
mkdir target
cd target
git init

Then, I shallow clone some repo and add the above repo as remote:

cd /tmp
git clone --depth 1 git@github.com:muennich/urxvt-perls.git
cd urxvt-perls
git remote add target /tmp/target

Finally, I push this repo to the remote:

git push target master

But then I get:

! [remote rejected] master -> master (shallow update not allowed)
error: failed to push some refs to '/tmp/target'

What am I missing here?

If you are interested in gitlab allowing this check https://gitlab.com/gitlab-org/gitlab-ce/issues/3033. — memeplex, Dec 31 '15 at 21:13
look at this [remote-rejected-shallow-update-not-allowed-after-changing-git-remote-url](http://stackoverflow.com/a/28985327/2206581) — hisland, Mar 06 '17 at 05:06

memeplex · Accepted Answer · 2015-10-13T00:26:16.980

7

I'm answering my own question.

I tried going the other way around and adding urxvt-perls as a remote for target, then fetching from there. This fails because of the same reason but led me closer to a solution. From the git-fetch man:

  --update-shallow
       By default when fetching from a shallow repository, git fetch
       refuses refs that require updating .git/shallow. This option
       updates .git/shallow and accept such refs.

Now, using this option allows the shallow fetch. So the previous question becomes: Is it possible to specify that --update-shallow behavior while pushing? Well, there is an option for that:

receive.shallowupdate
    If set to true, .git/shallow can be updated when new refs require
    new shallow roots. Otherwise those refs are rejected.

I'm still trying to set this in github and the likes, though.

edited Oct 13 '15 at 00:26

answered Oct 12 '15 at 16:39

memeplex

2,297
27
26

So, Do you success in github or gitlab now ? – Tony Jun 28 '18 at 02:38
No, I opened an issue in gitlab tracker some time ago but nobody really cares. – memeplex Jul 02 '18 at 21:15
I'm also interested if Gerrit supports this – bam Aug 11 '19 at 23:15
FWIW, the GitHub tracker is https://github.community/t/set-receive-shallowupdate-on-to-allow-pushing-from-shallow-clones/2424, and the GitLab tracker is https://gitlab.com/gitlab-org/gitlab-foss/-/issues/3033. – Mingye Wang Jul 29 '20 at 02:03

score 5 · Answer 2 · edited Feb 15 '19 at 13:17

5

git fetch --unshallow

git push target master -f

edited Feb 15 '19 at 13:17

Suraj Rao

29,388
11
94
103

answered Feb 15 '19 at 13:13

Roman Kuntyi

51
1
1

score 2 · Answer 3 · edited May 23 '17 at 12:31

2

Use git merge --squash.

If your remote is shallow and you want to merge from it, compress that merge into a single commit without the need to copy a history of commits (which shallow refs hide).

edited May 23 '17 at 12:31

Community

1
1

answered Apr 16 '16 at 01:34

Enrico Tiongson

400
4
5

score 0 · Answer 4 · answered Jun 23 '17 at 11:48

0

Well on Linux repo server... this

git config --local --add receive.shallowUpdate true

resulted in this being added to the repo config file.

[receive]
    shallowUpdate = true

So maybe if you can add that to the repo config file.

answered Jun 23 '17 at 11:48

NOYB

625
8
14

If I use github Or Gitlab,How To add this config? – Tony Jun 28 '18 at 02:33

Shallow update not allowed (git > 1.9)

4 Answers4

Linked