-
Notifications
You must be signed in to change notification settings - Fork 113
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
feat(ncu-ci)!: require --certify-safe
flag
#798
Conversation
Or ensure the PR has received at least one approving review since last time it was pushed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
--certify-safe
flag--certify-safe
flag
This is currently a bit too restrictive - it should add an exceptions to collaborators otherwise even a collaborator cannot use the label to run the CI wihout an approving review (or after they've pushed a new commit), see nodejs/node#52692 |
@aduh95 do you intend to make a patch based on what @joyeecheung mentioned? 👀 |
Or ensure the PR has received at least one approving review since last time it was pushed.