One additional perspective on this:

Restore the flake8 error code suffx

In D17552#210700, @epriestley wrote:

Ideally, the "name" would be a short human-readable title for the error that's as specific as possible ("Undefined Variable") while the "description" provides more details ("The variable $x is not defined in this context. Define variables prior to use.") but they're both human-readable text so any reasonable behavior should be fine.

This is also a duplicate of T4954, which was fixed by the addition of per-linter version support in D14298.

For reference, the Chromium project has a formal definition of their OWNERS files, including parsing code (in Python).

Simplify regular expression. No need to capture the code character.

In D15472#182717, @epriestley wrote:

Despite the status, owners.search is probably more stable than owners.query at this point. Is there any technical reason you can't switch to owners.search?

Fix silly errors.

@epriestley, I've acted on those two suggested action items.

Prefer '=' to '==' for user-facing equality.

Introduce getUpgradeInstructions() for upgrade-specific instruction text.

I had considered a getUpgradeInstructions() method and got stalled on the idea that some cases might call for a "downgrade". I suppose that's really not a good reason to forego the actual functionality, though. :)

Fix the version requirement regular expression.

I just signed the CLA. Sorry, I thought I had already done that a while back.

A partial solution is to (ab)use the List-ID header, which Gmail does understand. GitHub took this approach.

I see this error about once a week. Repeatedly clicking the "Close" button in the error pop up will eventually dismiss it. I don't know what the number of required clicks correlates to, but it's consistent per problematic diff.

I've been enjoying the combination of the "Done" flag and inherited comments, but one thing that I've found bothersome is that I need to click "Done" for each comment in a "thread" to "close out" that line of conversation (once I've actually done the requested thing).

This appears to break cassowary which [uses getCommitHookMode()](https://github.com/imobile3/cassowary/blob/master/libcassowary/src/lint/engine/MobileLintEngine.php#L52).

Perhaps a reviewer could flag a comment as "Changes Requested" or similar to indicate whether the comment should be inherited by future revisions (until it is marked "Done" by the owner).