I would like to propose that CI should not be run on PRs that are marked as "Drafts" using the Github "Drafts" feature.
Run CI wastes resources and produces lots of noisy messages from rust-highfive bot about failing CI.
mark-i-m
All 5 comments
It should be possible to explicitly ask for them to run through CI, but it makes sense to not run CI on drafts by default.
joshtriplett
on 16 Dec 2019
It might be a bit heavy-weight, but I think we can already use bors try for that.
mark-i-m
on 17 Dec 2019
It looks like Travis, Azure, and Github don't have support for such a feature yet...
mark-i-m
on 17 Dec 2019
Triage: this looks to be possible for Github Actions? https://github.community/t5/GitHub-Actions/Don-t-run-actions-on-draft-pull-requests/m-p/55316#M9508
steveklabnik
on 17 May 2020
We discussed this in the infrastructure team meeting and decided not to go forward with this approach. You can see the context on the decision by reading the contents of the meeting.
pietroalbini
on 9 Sep 2020
Related issues
lambda-fairy
路
3Comments
eddyb
路
3Comments
dwrensha
路
3Comments
pedrohjordao
路
3Comments
modsec
路
3Comments
Most helpful comment
It should be possible to explicitly ask for them to run through CI, but it makes sense to not run CI on drafts by default.