Use travis-conditions to give users flexibility for draft PRs?

[MaxThevenet]

There has been some discussion in the TravisCI community as to how GitHub draft pull requests are handled. In my understanding, if a TravisCI build is requested for all open PRs to a given branch, draft PRs are treated as regular PRs for TravisCI and a TravisCI build will be launched.

For some project, it could be a useful feature to disable TravisCI builds for draft PRs in order to take a weight off of TravisCI jobs.

Could travis-conditions give enough flexibility to let the user decide on the behavior for draft PRs? For instance, adding a new option draft_pull_request for type (currently available are push, pull_request, api, cron)?

Thanks!!

[erwanp]

Good feature, any update?

[wischli]

Good feature, any update?

Push 🌚

[vkamenskyi]

It would be really helpful to have this feature!