The commit lint is breaking git reviewing flow by forcing contributors rebasing alot

[tesuji]

The commit lint makes me rebasing a lot, which hurts github reviewing workflow.
For example, I had to force-push in #5547 more than 3 times to please that lint.
I think this lint is useful, but not when the PR is in reviewing state.
Maybe you could make this lint run only on merge queue.

[epage]

Note that the lint is optional. The job is not a blocker for merge and the included message says just as much.

I also do not mind a lot of rebases during review. In fact, I generally recommend it.

I'm also not running merge queues and having a "frequently broken" lint that only fails on merge would be even more frustrating for people.

[tesuji]

The job is not a blocker for merge and the included message says just as much.

Seeing the CI fails for first time contributor (like myself) is driving me to fix it.
Now I know about how the reviewer feel about this problem. So it's not a problem for me anymore.