One of the developers in my team is having the following issues. They have the ability to pull a remote branch which says it is all up to date, but they cannot push to that remote branch. The following is what they are getting in the Windows git command prompt
MY@MY-PC ~/documents/workspace/my-repository (workflowNewCOBRequest1)
$ git remote show origin workflowNewCOBRequest1
Enter passphrase for key '/c/Users/MY/.ssh/id_rsa':
* remote origin
Fetch URL: git@github.com:myorg/my-repository.git
Push URL: git@github.com:myorg/my-repository.git
HEAD branch: master
Remote branches:
2_Initial_COB_Submission tracked
COB_VF_email_template new (next fetch will store in remotes/origin)
Team-approval tracked
develop tracked
master tracked
testing tracked
workflowNewCOBRequest1 tracked
Local branches configured for 'git pull':
develop merges with remote develop
master merges with remote master
workflowNewCOBRequest1 merges with remote workflowNewCOBRequest1
Local refs configured for 'git push':
Team-approval pushes to Team-approval (up to date)
develop pushes to develop (local out of date)
master pushes to master (up to date)
MY@MY-PC ~/documents/workspace/my-repository (workflowNewCOBRequest1)
$ git push origin workflowNewCOBRequest1
Enter passphrase for key '/c/Users/MY/.ssh/id_rsa':
fatal: workflowNewCOBRequest1 cannot be resolved to branch.
fatal: The remote end hung up unexpectedly
I have searched the internet and cannot find anything resembling this. Any ideas?
Thanks
Paul