-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
build: do not run GitHub actions for draft PRs #35910
Conversation
Marking the PR a s ready is not enough to re-run the workflows. |
When we mark it as ready, will it trigger github action run ? |
No, but I think we can manually run the jobs (and GitHub Actions are advisory in most cases anyway), so I'm OK with this behavior. I'm going to try to manually kick off the jobs to confirm that's possible. Hopefully I'm not messing up @targos's experiment.... |
Argh, nope, it skips them still. I guess we'd have to kick off Jenkins for any PR opened as Draft? I'm still OK with that, although there are jobs in GitHub Actions (ASAN, tarball building, coverage, codeowners assignment, maybe others) that don't get run in Jenkins..... so it's less ideal, for sure.... |
Maybe pushing (or force-pushing) will be enough to kick off the jobs? |
Rebasing against master and force-pushing to see if that kicks off the jobs. |
7c7ec67
to
ac10fb9
Compare
That seems to have worked. I can live with that. |
Works with me too. Can this be integrated with our CI robot ? |
Needs a rebase before this can land |
ac10fb9
to
25b92b0
Compare
25b92b0
to
363d4e4
Compare
Landed in aadb0bd |
Closes: #35899
I also pushed another branch just to verify that this doesn't prevent branch pushes to execute the workflow: https://github.com/nodejs/node/commits/no-draft-workflow-with-branch
Opened as a draft this time.