Edwin, what would be the best way to filter this account from reviewer suggestions?

We don't have support for excluding a specific account from the reviewer suggestion.

The reviewer suggestion excludes existing reviewers. Would if be feasible to automatically add the commit bot as reviewer when the change is created, so that it's then not suggested as reviewer?

Reviewer suggestion also filters out accounts that are not visible. So depending on the setting for 'accounts.visibility' on the host the commit bot may be placed into an own group that is not visible to other users.

If support for excluding a specific account from the reviewer suggestion should be implemented this could be project setting (list of accounts that should not be suggested as reviewer). Alternatively adding a special property on the account would be possible.

Option #1: Make account invisible

The accounts.visibility setting would potentially be viable if all the human users on chromium-review are automatically members of a visible group. The requirement is that every account that should be suggestible as reviewer or CC must always be a member of an explicitly visible group.

It appears to me that the chromegroupbackend plugin doesn't populate that field. Perhaps that would be a reasonable change to make? Not sure if there are users who would not be members of any group served by chromebackend that ought to be suggested as reviewers or CCs.

Option #2: Auto-add bot as reviewer on every change

Auto-adding the bot to every change (as either reviewer or CC) would be easy to add to git cl upload. The downside is that it adds visual noise.

Option #3: Use chromium_behavior plugin to hide account

I'm not sure how this would work exactly, but we could use a plugin in some fashion to filter this suggestion.

Option #4: New Gerrit feature to offer a way to blacklist reviewer accounts without depending on group visibility.

This would need to be specced out further, and there's a risk that it wouldn't fit on our near-term roadmap.

Moved issue gerrit:6936 to now be  issue chromium:753411 .

Removing Milestone-Afterglow, as it has ceased to have meaning. More refined milestones may be added back in the near future.

The solution for this is not to special-case the CQ bot, but to make intelligent suggestions based on OWNERS files and review history. Duping into bug tracking that work.