Review requested:

• @nodejs/actions

It counts the approvals of the head of the PR, meaning that if the PR has many approval, but a commit gets pushed and it receives a single approval, the CQ will wait for the 7 days (even though the PR could technically land sooner according to our governance rules).

Can we aleviate this drawback? Often times a PR that's ready to land in the 2-7 period would get an approval with a nit, or just requests a small change before approving, you want to fix that nit but now can't land it with CQ even if the one who requested a small change re-approves because now it needs one more existing reviewer to either come back and approve or someone else entirely.

#62498 OTOH just allowed to add the CQ label with one approval and it'd stay in the queue until a 2nd review comes or 7 days pass. No brain teasers.

@panva you can add the Approvals: 2+ PRs that have anough approvals to land before the 7 days mark label manually
Note that there’s no reliable way for the bot to detect a small change, so IMO it makes sense to defer to a more defensive behavior

@panva you can add the label manually

Which label would that be? Can you explain this automation proposal here better?

The automation runs every time a review is submitted or dismissed. It will count how many approvals from the team (TSC for semver-major PRs, collaborators for other PRs) on the HEAD (i.e. since the last non-empty commit), if that's more that 2 and there are no changes requested, it adds Approvals: 2+ PRs that have anough approvals to land before the 7 days mark , otherwise it removes it.
What I'm saying is that for the case you present in #64340 (comment), it would IMO makes sense for a human to manually add the label, if it's indeed just a nit it doesn't invalidate the previous reviews.

Can we aleviate this drawback?

To answer this specifically, the answer is: definitely yes, I had to add some logic to check if the review was on the last commit.

Superseded by #64343