The CQ plugin (commitqueue.js) is what does this.

I am assuming this is happening for a repo that does not have CQ enabled in chromium-review. IIRC there was an open bug to hide this behavior for non-CQ repos.

Aaron, this is not a Gerrit bug, can you move it to the appropriate Chromium component?

by "CQ", i'm assuming you mean "Chromium CQ".  CrOS has long had a CQ in Gerrit (since the beginning of Gerrit actually).  so if you're binding to "repo has Commit-Queue label", that is incorrect.

Example CL?

I see this in commitqueue.js - https://cs.corp.google.com/piper///depot/google3/devtools/gerritcodereview/plugins/commitqueue/commitqueue.js?l=141
Maybe we need that check in more places.

just search for one of those strings to find plenty of examples:
https://chromium-review.googlesource.com/q/NOPRESUBMIT%253Dtrue

https://chromium-review.googlesource.com/479357
https://chromium-review.googlesource.com/478172
https://chromium-review.googlesource.com/477440
https://chromium-review.googlesource.com/471812
https://chromium-review.googlesource.com/471873

no repo under chromiumos/ should have these Chromium-specific things added imo.

I am assuming continuing to carry over "BUG=.*" to reverts will be useful.
Is there any other string that you want carried over?

extracting BUG= from the commit message and automatically copying it over should be fine.  i'm not seeing any other tags that make sense for us in there.

Moved issue gerrit:6008 to now be  issue chromium:713279 .

This is now live.
Tested by clicking on Revert here: https://chromium-review.googlesource.com/c/500287/

Marking as fixed.

thanks!