Disable GitHub actions for draft PRs

[jackwener]

Which issue does this PR close?

Closes #2086.

What changes are included in this PR?

Are there any user-facing changes?

[jackwener]

It's from CI of node

[jackwener]

We can see the result of those change in this PR.

[yjshen]

I suppose draft is a way to tag PRs that are not ready for review? Are we experiencing insufficient resources or similar problems currently?

[jackwener]

I suppose draft is a way to tag PRs that are not ready for review? Are we experiencing insufficient resources or similar problems currently?

Yes, I'm write a draft PR #2084. It's just want to ask for help, I don't want to trigger CI.
So is #2054.

[matthewmturner]

In my case I find value in seeing CI run even when in draft state. I would think it's ok to keep as long as it isn't draining some limited resource (I'm unsure how that works with Apache projects).

[jackwener]

In my case I find value in seeing CI run even when in draft state. I would think it's ok to keep as long as it isn't draining some limited resource (I'm unsure how that works with Apache projects).

This can save CI resource, I think it's valuable. Because run CI for not ready PR is not meaningful.

[jychen7]

In my case I find value in seeing CI run even when in draft state

I also agree on that. Because running full test case locally is time consuming. In my case, I always run related test cases locally for my change and if it looks good, draft a PR to trigger a full run. If all checks have passed in Draft, then convert to "Ready for review"