Affected Version:
What steps will reproduce the problem?
1. Clone repository via HTTP.
2. Push changes to non-existing branch.
What is the expected output? What do you see instead?
Current:
git-over-HTTP response doesn't contain errors:
$ git push origin-http HEAD:refs/for/none
Password:
Counting objects: 7, done.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 364 bytes, done.
Total 4 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 0% (0/2)
$ git push origin-ssh HEAD:refs/for/none
Enter passphrase for key '/home/user/.ssh/id_rsa':
Counting objects: 7, done.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 364 bytes, done.
Total 4 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 0% (0/2)
To ssh://user@review.example.com:29418/project
! [remote rejected] HEAD -> refs/for/none (branch none not found)
error: failed to push some refs to 'ssh://user@review.example.com:29418/project'
Expected: both responses should be the same (contain errors).
Please provide any additional information below.
Successful responses for git-over-HTTP and SSH are the same, only rejections are different.