如果你的回购是原点，而原始回购是上游:

git fetch --unshallow upstream

只需删除/.git/shallow中的shallow文件

现在应该可以了。

如果取回。unshallow不起作用。你们的分行一定有问题。在推它之前，用下面的命令修复它。

git filter-branch -- --all

只使用——unshallow不行，因为有安全方面的考虑。

如果是bitbucket管道

这可能是由于提交深度有限(默认50提交)

你可以增加限制

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

注:使用深度:满为不限

根据投票最多的答案，我创建了一个别名来自动化事情:

添加到你的.gitconfig:

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

用法:

Git unshallow #基于源远程的非浅当前分支 Git unshallow other-remote #非浅层当前分支从远程other-remote

如果你想保持回购与你添加的新提交一样，那么另一个选择是:用一个交互式的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