Remote rejected (shallow update not allowed) after changing Git remote URL

Question

I have a project under Git version control that I worked on both a server and my local computer. I originally had the remote origin set as my local computer but I would now like to change that to BitBucket.

On the server I used the command

git remote set-url origin bitbucket_address

But now when I try to push my project I get the error

 ! [remote rejected] master -> master (shallow update not allowed)

What is causing this and how do I fix it?

It was a while ago and I can't remember. Is there a way to find out? — rwolst
– rwolst, Commented Mar 11, 2015 at 11:01
There should be a file named shallow in you .git folder. — Alex Wolf
– Alex Wolf, Commented Mar 11, 2015 at 11:05
See stackoverflow.com/a/50996201 for a solution that just discards (or rewrites) the missing history — caw
– caw, Commented Mar 30, 2019 at 17:16

Alex Wolf · Accepted Answer · 2022-10-20 14:25:54Z

501

As it seems you have used git clone --depth <number> to clone your local version. This results in a shallow clone. One limitation of such a clone is that you can't push from it into a new repository.

You now have two options:

if you don't care about your missing history, take a look at this question
if you want to keep your full history, then continue reading:

So, you want to keep your history, eh? This means that you have to unshallow your repository. If you already removed or replaced your old remote then you'll need to add it again:

git remote add old <path-to-old-remote>

After that we use git fetch to fetch the remaining history from the old remote (as suggested in this answer).

git fetch --unshallow old

And now you should be able to push into your new remote repository.

Note: After unshallowing your clone you can remove the old remote.

edited Oct 20, 2022 at 14:25

answered Mar 11, 2015 at 11:23

Alex Wolf

20.6k4 gold badges56 silver badges73 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

clacke Over a year ago

Note that git fetch --unshallow can take a refspec to only unshallow a certain branch rather than the whole repo. E.g.: git fetch --unshallow origin refs/heads/mydeepbranch:refs/remotes/origin/mydeepbranch

clacke Over a year ago

If you are pushing to a repo that is a bit behind whatever repo you cloned from, not creating an all-new repo, it is enough that your local reference is deep enough to contain the remote reference. So if your origin/master was 20 commits ahead of your oldrepo/master when you clone --depth 1'ed it, and you have made 17 local commits since, it is enough for you to do git fetch --depth 37 origin refs/heads/master:refs/remotes/origin/master (apologies for any off-by-one error), and then you can do git push oldrepo master without incident (may require git 1.9.0 or newer).

user36388 Over a year ago

@itamar delete /.git/ (& reference in package.json) and git init

user2679290 Over a year ago

Usually you won't need to add old rep, so just use the git fetch command

Dorian · Accepted Answer · 2017-04-04 21:31:37Z

57

In case your repo is origin, and the original repo is upstream:

git fetch --unshallow upstream

answered Apr 4, 2017 at 21:31

Dorian

24.2k9 gold badges130 silver badges116 bronze badges

Comments

Jayen · Accepted Answer · 2019-08-03 11:35:57Z

33

Another option if you want to keep the repo as is with the new commits you have added since the shallow, initial commit is this: Amend this commit with an interactive rebase.

Start an interactive rebase including the first (root) commit with
```
git rebase --interactive --root
```
Change the pick of the initial commit(s) to edit and save & close the file.

If you've cloned the repo with greater depth than 1, you may need to do the same for all of those commits. Or, alternatively, execute fixup for all of these during the interactive rebase.
Convert this commit to a regular, unshallow commit with
```
git commit --amend --no-edit
```
This will also change the commit ID and add you as co-author to this initial commit.
Don't forget to finish your rebase
```
git rebase --continue
```

edited Aug 3, 2019 at 11:35

Jayen

6,1173 gold badges53 silver badges69 bronze badges

answered Aug 30, 2018 at 22:54

Rene Hamburger

2,29321 silver badges19 bronze badges

2 Comments

CS QGB Over a year ago

fatal: No rebase in progress?

CS QGB Over a year ago

error: src refspec main does not match any

Benjamin Loison · Accepted Answer · 2024-04-15 14:28:31Z

17

If you want to push the new repo as it is, you can try this:

First remove the old git folder from your current repo, sudo rm -rf .git
Then initialize the git again git init
Then add the new remote repo git remote add origin your-new-repo
Then Push it.

edited Apr 15, 2024 at 14:28

Benjamin Loison

5,7804 gold badges20 silver badges37 bronze badges

answered May 14, 2018 at 3:51

Akhter-uz-zaman

3673 silver badges8 bronze badges

3 Comments

rnpd Over a year ago

I found this a better solution, since it doesn't require a push to the old. Sometimes this could happen with boilerplates.

Alex Wolf Over a year ago

This is basically the answer from the related question which you can find here.

Alex Wolf Over a year ago

@NachPD I'm not sure what you mean, when you say that the other solution requires "a push to the old". Do you mean a fetch instead of a push? Because it does not require a push.

Chayapol · Accepted Answer · 2020-03-06 13:19:02Z

5

If fetching --unshallow doesn't work. There must be some problems with your branch. Fix it with the following command before pushing it.

git filter-branch -- --all

Do this only with --unshallow doesn't work since there's a SAFETY concern.

answered Mar 6, 2020 at 13:19

Chayapol

3,9841 gold badge24 silver badges12 bronze badges

1 Comment

Ferdinand Prantl Over a year ago

This will help you push a local repo with the history cut by git clone file://<path> <dirname> --depth=<N>. Such shallow clone will not be pushable, because the history will be only hidden by graft. The filter-branch will drop it.

LUAN.YUAN · Accepted Answer · 2022-02-24 05:39:48Z

3

I fixed this issue. but maybe you can not fixed it. the solution as follows.

get the shallow file from the git, like common/.git/shallow
push this file to the .git directory in git server.
push your branch to the git server.

In my company, I need the IT admin to add the file, and I have not permissions.

answered Feb 24, 2022 at 5:39

LUAN.YUAN

311 bronze badge

1 Comment

activedecay Over a year ago

PERFECT! basically, these are my steps: 1. create a repo using git init on the server, 2. cat .git/shallow on a client machine that has a large git history, 3. add .git/shallow on the server with the content from step 2, 4. git push from the client to the server.

Benjamin Loison · Accepted Answer · 2024-04-15 14:32:07Z

1

In case of bitbucket pipeline

It might be due to limited depth of commit (default 50 commit)

You can increase limit

clone:
  depth: 500       # include the last five hundred commits
  
pipelines:
  default:
    - step:
        name: Cloning
        script:
          - echo "Clone all the things!"

Note : Use depth: full for no limit

edited Apr 15, 2024 at 14:32

Benjamin Loison

5,7804 gold badges20 silver badges37 bronze badges

answered Sep 20, 2022 at 13:45

Mihir Bhatt

3,1652 gold badges39 silver badges43 bronze badges

Comments

Tom Hale · Accepted Answer · 2020-09-06 14:41:50Z

0

Based on the most upvoted answer, I created an alias to automate things:

Add to your .gitconfig:

[alias]
    unshallow = !"git fetch --unshallow \"${1:-origin}\" # Unshallow from remote $1 (defaults to origin)"

Usage:

git unshallow # unshallow current branch based on the origin remote
git unshallow other-remote # unshallow current branch from remote other-remote

answered Sep 6, 2020 at 14:41

Tom Hale

48.4k43 gold badges208 silver badges275 bronze badges

Comments

Wai Ha Lee · Accepted Answer · 2021-10-13 14:09:47Z

0

For simply resolving this issue if you don't care about the remote existing changes then do it the following way.

Remove your local .git folder from your repository.
Type git init.
Add your remote again git remote add origin <REMOTE_URL>.
Set main branch by git branch -M main.
Push your changes then git push --set-upstream origin main.

edited Oct 13, 2021 at 14:09

Wai Ha Lee

8,872102 gold badges61 silver badges100 bronze badges

answered Oct 6, 2021 at 5:58

Mohamed Jakkariya

1,7471 gold badge18 silver badges17 bronze badges

1 Comment

CS QGB Over a year ago

fatal: Invalid branch name: 'HEAD'

Mbs Yaswanth · Accepted Answer · 2022-06-06 13:02:15Z

-3

Just delete the shallow file in your /.git/shallow

Now it should work.

answered Jun 6, 2022 at 13:02

Mbs Yaswanth

1502 silver badges7 bronze badges

1 Comment

CS QGB Over a year ago

!git push -f https://{repo} main fatal: unable to get credential storage lock: File exists Counting objects: 347, done. Delta compression using up to 4 threads. Compressing objects: 100% (245/245), done. Writing objects: 100% (347/347), 56.28 MiB | 1.56 MiB/s, done. Total 347 (delta 153), reused 250 (delta 99) remote: Resolving deltas: 100% (153/153), done. remote: fatal: did not receive expected object 2aaa07546a89ead5a106b6ed48beb3ce3a485c8a error: unpack failed: index-pack failed To github.com ! [remote rejected] main -> main (failed) error: failed to push some refs to

Collectives™ on Stack Overflow

Remote rejected (shallow update not allowed) after changing Git remote URL

10 Answers 10

4 Comments

Comments

2 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

4 Comments

Comments

2 Comments

3 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related