Yeah, this was more of an ad-hoc thing so that we could cherry-pick things to go in our next release. I wouldn't recommend trying this to model pull requests, since, like you said, it would require submitting another patch to merge your "PR" branch. On Tue, Jun 9, 2015 at 6:51 AM, Joaquin Oltra Hernandez < jhernandez(a)wikimedia.org&gt; wrote: > Yo can you expand on how to use this to do branch-driven development? > Seems like you could get something similar to PRs by doing this. > > I guess you have to do a merge patch later to master? > > On Tue, Jun 9, 2015 at 12:21 AM, Gergo Tisza &lt;gtisza(a)wikimedia.org&gt; > wrote: > >> On Mon, Jun 8, 2015 at 3:10 PM, Brian Gerstle &lt;bgerstle(a)wikimedia.org&gt; >> wrote: >> >>> For anyone iOS or gerrit inclined I just created a "4.1.5" release >>> branch and submitted a patch >>> <https://gerrit.wikimedia.org/r/#/c/216861/> using "git review 4.1.5". >>> >>> This was done by: >>> >>> 1. Pushing a new branch to gerrit >>> 1. git push -u origin HEAD:4.1.5 >>> 2. Submitting the patch to the newly created branch >>> 1. commit some changes... >>> 2. git review 4.1.5 >>> >>> Step #1 requires push permissions for your target repo. >>> >> >> If there is future work to be done on the branch (backports etc.) it's a >> good idea to change defaultbranch in .gitreview to avoid accidents (that >> branch will be used if you run git review without a branch name). >> >