************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! *****
************************************************************
Affected Version:2.9
What steps will reproduce the problem?
1.I would like to be able to create a branch remotely using the push command to refs/for/... Currently I am allowing my developers to create references based on a pattern /PROJ-(.)*. each feature branch will have the PROJ-(.)* expression in it. I am forcing that everyone who creates those feature branches must initiate a code review.
2.I create a branch locally and do updates
3.push to origin HEAD:refs/for/<branch name> to initiate a code review I get an error that the branch does not exist.
What is the expected output? What do you see instead?
I would have to create the branch remotely and then pull then push. I would like to be able to remotely create the branch using the push command when I initiate a code review. I believe the direct push works, but I am afraid that if I allow them to do a direct push to create the branch, then they will always do a direct push and bypass the code review.
Please provide any additional information below.