How to solve git error: Server does not allow request for unadvertised object 3a2ceef391af73994dfeb0d8ef57ed6a52ef4238?

前端 未结 8 2686
攒了一身酷
攒了一身酷 2021-02-19 09:18

I wanted to pull commit \"3a2ceef391af73994dfeb0d8ef57ed6a52ef4238\" from branch android. I used the command:

$ git fetch origin 3a2ceef391af73994dfeb0d8ef57ed6a         


        
相关标签:
8条回答
  • 2021-02-19 09:39

    I got the same error and none of these resolved it. It turned out that I hadn't pushed submodule changes from my other computer (this would give 404 error when you click on submodule folder on GitHub). So pushing submodule, committing parent and pushing that as well resolved the error.

    Other solutions are git submodule update --recursive and this.

    0 讨论(0)
  • 2021-02-19 09:45

    You can follow the below steps to solve the above error .

    > git init 
    > git pull <reponame> branchname(optional) 
    > git reset --hard <commit_id>
    

    Note:make sure that You have committed and pushed your changes from local to remote already as reset --hard will leave any unsaved changes from local and it moves completely and get the files and folders of the commit which is irreversible with any changes not pushed. You may have a look in to these as well.

    https://www.pylabz.com/2019/08/using-python-to-pull-files-of-git-hub.html#more

    https://medium.com/@deepakr6242/using-python-to-extract-files-from-git-hub-repo-through-commits-id-2bdf76b2e0fd

    0 讨论(0)
  • 2021-02-19 09:49

    I got the same error when use git submodule update --init,quickly fix it by using git submodule update --force --recursive --init --remote

    0 讨论(0)
  • 2021-02-19 09:50

    git submodule sync as pointed in https://github.com/AppImage/AppImageKit/issues/511 works for me.

    0 讨论(0)
  • 2021-02-19 09:54

    I was facing such an error while doing a git pull. Doing below helped fix the issue for me.

    git remote prune origin
    git pull
    
    0 讨论(0)
  • 2021-02-19 09:54

    I got the same problem and unsuccessfully tried some of the above solutions. What worked for me is:

    git fetch --unshallow && git fetch origin && git reset --hard origin/master
    
    0 讨论(0)
提交回复
热议问题