We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nodejs/node#47769 is a semver-major PR and landed with a single approval as you can see below image:
nodejs/node@b40f0c3 has:
Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
And looking at nodejs/node#47769 they did review and approve the PR at one point in time. But Robert was requested to review again in nodejs/node#47769 (comment) and Matteo was requested to review again in nodejs/node#47769 (comment).
I think there's a bug in git node land that consider the first approval only.
git node land
The text was updated successfully, but these errors were encountered:
It's a duplicate of #677, as I said in #677 (comment) I would argue this is working as expected.
Sorry, something went wrong.
Closing in favor of #677.
No branches or pull requests
nodejs/node#47769 is a semver-major PR and landed with a single approval as you can see below image:
nodejs/node@b40f0c3 has:
And looking at nodejs/node#47769 they did review and approve the PR at one point in time. But Robert was requested to review again in nodejs/node#47769 (comment) and Matteo was requested to review again in nodejs/node#47769 (comment).
I think there's a bug in
git node land
that consider the first approval only.The text was updated successfully, but these errors were encountered: