Skip to content

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Apr 24, 2024

Or ensure the PR has received at least one approving review since last time it was pushed.

Or ensure the PR has received at least one approving review since last
time it was pushed.
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Member

@BridgeAR BridgeAR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@aduh95 aduh95 changed the title feat(ncu-ci): require --certify-safe flag feat(ncu-ci)!: require --certify-safe flag Apr 24, 2024
@aduh95 aduh95 merged commit a5213cd into nodejs:main Apr 24, 2024
@aduh95 aduh95 deleted the run-ci-certify-safe branch April 24, 2024 18:45
@joyeecheung
Copy link
Member

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

@ovflowd
Copy link
Member

ovflowd commented May 2, 2024

@aduh95 do you intend to make a patch based on what @joyeecheung mentioned? 👀

mcollina added a commit that referenced this pull request May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants