Affected Version: current master (v2.11.1-797-g9a3d7dc)
What steps will reproduce the problem?
1. # Have some point of valid git history such as
touch asdf && git add asdf && git commit -a -m "add file asdf"
2. git push origin HEAD:refs/for/master%submit
3. # create a new branch "newbranch" in the web UI
4. git checkout -b newbranch
5. # advance git history again:
touch fdsa && git add fdsa && git commit -a -m "add file fdsa"
6. git push origin HEAD:refs/for/newbranch%submit
7. # delete the newbranch in the web ui
8. # Recreate the newbranch in the web ui, pointing at HEAD (master)
9. # rerun command in 6
git push origin HEAD:refs/for/newbranch%submit
10. # Observe output:
! [remote rejected] HEAD -> refs/for/nbranch%submit (no new changes)
What is the expected output? What do you see instead?
While the changes are not new, the branch should be advanced to have the
commits included. So I'd expect something like:
remote: advance refs/heads/newbranch ce87ef370..f00cf621
remote: (no new changes, though)