| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Marking the PR a s ready is not enough to re-run the workflows. |
Sorry, something went wrong.
Sorry, something went wrong.
|
When we mark it as ready, will it trigger github action run ? |
Sorry, something went wrong.
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.... |
Sorry, something went wrong.
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.... |
Sorry, something went wrong.
Hmmm... just in case the not-able-to-run-once-out-of-draft-mode stuff is all due to some daylight-savings-in-North-America weirdness, I'm going to put it into Draft mode again, and then take it out again.... |
Sorry, something went wrong.
|
Maybe pushing (or force-pushing) will be enough to kick off the jobs? |
Sorry, something went wrong.
|
Rebasing against master and force-pushing to see if that kicks off the jobs. |
Sorry, something went wrong.
|
That seems to have worked. I can live with that. |
Sorry, something went wrong.
Works with me too. Can this be integrated with our CI robot ? |
Sorry, something went wrong.
|
Needs a rebase before this can land |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.