-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
tools: fix skip PR if CI is still running #42377
Conversation
Review requested:
|
|
change according to review
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
Landed in 8f07452 |
resolve: nodejs#40330 PR-URL: nodejs#42377 Fixes: nodejs#40330 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Mestery <mestery@protonmail.com>
resolve: nodejs#40330 PR-URL: nodejs#42377 Fixes: nodejs#40330 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Mestery <mestery@protonmail.com>
resolve: nodejs/node#40330 PR-URL: nodejs/node#42377 Fixes: nodejs/node#40330 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Mestery <mestery@protonmail.com>
The original "Skip PR if CI is still running" seems not working, I find it is because
ncu-ci url
's output can't be greped (not totally sure because I don't have access to jenkins).Using
gh pr checks
should be just fine I guess.Fixes: #40330