Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dismissed review not respected #62

Closed
Mariatta opened this issue Feb 20, 2018 · 0 comments
Closed

Dismissed review not respected #62

Mariatta opened this issue Feb 20, 2018 · 0 comments
Assignees
Labels

Comments

@Mariatta
Copy link
Member

In python/cpython#5746, two core devs approved the PR initially, but later both reviews were dismissed.
miss-islington still went ahead and merged the PR.

The PR shouldn't have been merged in this case.

@Mariatta Mariatta added the bug label Feb 20, 2018
@Mariatta Mariatta self-assigned this Jun 27, 2018
Mariatta added a commit that referenced this issue Jun 29, 2018
Change the behavior for when deciding when miss-islington
should merge the PR.

Previously it checks if the PR has one core dev who approved the PR.
But that is unreliable because the review may be dismissed later,
or another core dev might decide not to backport the PR anymore.

The "awaiting merge" label is a better indicator that the PR
is ready for merge.

Adjust tests.

Fixes #62
Mariatta added a commit that referenced this issue Jun 29, 2018
Change the behavior for when deciding when miss-islington
should merge the PR.

Previously it checks if the PR has one core dev who approved the PR.
But that is unreliable because the review may be dismissed later,
or another core dev might decide not to backport the PR anymore.

The "awaiting merge" label is a better indicator that the PR
is ready for merge.

Adjust tests.

Fixes #62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant