Skip to content

autosubmit blocks merging on stale "request changes" pr #185224

@gaaclarke

Description

@gaaclarke

example

#184984

reproduction steps

  1. X authors PR
  2. Y reviews PR with request changes
  3. X makes changes
  4. Y approves changes
  5. X fixes merge conflicts (which invalidates all previous approvals)
  6. Z approves changes

In this state the PR just has one review that is an approval, but it will fail to merge the PR with the following message:

autosubmit label was removed for flutter/flutter/184984, because This PR has not met approval requirements for merging. Changes were requested by {Y}, please make the needed changes and resubmit this PR.
The PR author is a member of flutter-hackers and needs 1 more review(s) in order to merge this PR.

- Merge guidelines: A PR needs at least one approved review if the author is already part of flutter-hackers or two member reviews if the author is not a member of flutter-hackers before re-applying the autosubmit label. Reviewers: If you left a comment approving, please use the "approve" review action instead.

observed behavior

The PR is blocked from merging, despite the PR having only one active review which is approval.

expected behavior

Since Y's last review was approval, and the PR has an active review from Z, it should be merged.

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions