This question is related to my problem in understanding rebase, branch and merge, and to the problem
How can you commit to your github account as you have a teamMate in your remote list?
I found out that other people have had the same problem. The problem seems to be related to /etc/xinet.d/.
Problem: unable to push my local branch to my master branch at Github
I run
git push origin master
I get
fatal: 'origin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
The error message suggests me that the branch 'origin' is not in my local git repository. This way, Git stops connecting to Github.
This is strange, since I have not removed the branch 'origin'.
My git tree is
dev
* master
ticgit
remotes/Math/Math
remotes/Math/master
remotes/origin/master
remotes/Masi/master
How can you push your local branch to Github, while you have a teamMate's branch in your local Git?
VonC's answer solves the main problem. I put a passphares to my ssh keys.
I run
$git push github master
I get
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
It seems that I need to give the passphrase for Git somehow.
How can you make Github ask for your passphrase rather than relying on the ssh key?
They key thing to remember is 'origin' is not the value you may need to be using... it worked for me when I replaced 'origin' with repo's name.
I had this problem and tried various solutions to solve it including many of those listed above (config file, debug ssh etc). In the end, I resolved it by including the -u switch in the git push, per the github instructions when creating a new repository onsite - Github new Repository
I think that's another case of git error messages being misleading. Usually when I've seen that error it's due to ssh problems. Did you add your public ssh key to your github account?
Edit: Also, the xinet.d forum post is referring to running the git-daemon as a service so that people could pull from your system. It's not necessary to run git-daemon to push to github.