I used git-drover to cherry-pick a CL into a release branch. Both the original CL and the cherry-picked CL went through Gerrit. This didn't trigger a comment or a label change on the associated bug -- see https://crbug.com/733642#c13

However, I later had to revert the cherry-pick and manually merge the original CL, due to dependencies on unmerged code. I followed the workflow at http://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/git-drover.html for the manual merge, but I used "git cl upload --gerrit" instead of "git cl upload". After submitting this CL, the associated bug got updated -- see https://crbug.com/733642#c14

Original CL: http://crrev.com/c/538965
Merged by git-drover: http://crrev.com/c/540103
Manual merge (with changes): http://crrev.com/c/541797

In both cases, I gave myself Code-Review +1 using the UI, clicked the red "Submit" button, and ignored the warning about the project having a CQ. So (I think) I followed the same workflow for submitting the two merge CLs.