The linter was recently turned on (#61875), and it seems to be running on entire files, any time those files are touched. See for example this failure, which is on a line that the PR doesn't touch. Having these linter 'land mines' in files adds friction to PRs, and encourages mixing of linter fixes with functional changes.

Can we either run the linter only on changed lines (not sure if that's possible) or not enable the linter where the codebase isn't already clean?

@gaaclarke