Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
tools: fix skip PR if CI is still running#42377
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
meixg commented Mar 17, 2022 • edited by aduh95
Loading Uh oh!
There was an error while loading. Please reload this page.
edited by aduh95
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot commented Mar 17, 2022
Review requested:
|
Uh oh!
There was an error while loading. Please reload this page.
aduh95 commented Mar 17, 2022
|
Uh oh!
There was an error while loading. Please reload this page.
change according to review
mhdawson left a comment
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
nodejs-github-bot commented Mar 21, 2022
nodejs-github-bot commented Mar 21, 2022
Landed in 8f07452 |
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: nodejs#40330 PR-URL: nodejs#42377Fixes: nodejs#40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: nodejs#40330 PR-URL: nodejs#42377Fixes: nodejs#40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: #40330 PR-URL: #42377Fixes: #40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
resolve: nodejs/node#40330 PR-URL: nodejs/node#42377Fixes: nodejs/node#40330 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Mestery <[email protected]>
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 checksshould be just fine I guess.Fixes: #40330