My git push is hanging after appearing to complete the push. I am going git push
Counting objects: 51, done.
Delta compression using up to 2 threads.
C
Permissions can also be cause of this in the case of a bare repo on a remote machine.
I ran into this same problem while pushing to GitHub. I found that a subset of the files being pushed wasn't being accepted.
I found this out by breaking my large commit into smaller commits (as described in this SO question: Break a previous commit into multiple commits), and then finding success with most of the smaller pieces.
The problem piece contains image files and I'm still sorting out which particular file (or files) triggers the problem.
This issue can be caused by issues with your SSH agent.
I recently ran into this issue because I changed my default shell from zsh
to bash
. I'd originally set up my ssh keys using zsh
, and so they were not available by default to bash
, using chsh -s /bin/bash
.
To fix, you'll need to add your ssh key(s) to the SSH authentication agent using the same shell script (bash
, sh
, zsh
, etc) you're using to perform your git commands:
eval `ssh-agent`
ssh-add ~/.ssh/some_key_rsa
You'll need to enter the passphrase for the key in order to add it. To store the passphrase to your user keychain so you don't need to enter it every time the key is used, add the key with the -K
option to the ssh-add
command.
ssh-add -K ~/.ssh/some_key_rsa
Note the uppercase K
as using a lowercase is a different command option.
This turned out to be no problem at all. I simply had to wait until the upload was complete. I had added several large files and there is not a progress indicator. Maybe someone else will find this helpful.
It only worked for me in the case when I did
git push -u origin master
, when I just simply used git push
for bit bucket, it did not push through.
Just wanted to add this in case it helps anyone. I had the same problem, and the issue was that the git user didn't have permission to write to the files, only to read from them.