I've found myself saying, "please run all tests before pushing" on at least a few GitHub PRs. The whole "push a button to run CI" thing is more annoying than I thought it would be. I'll be looking to switch CI systems very soon if it isn't fixed.
10
1
2
66
I'm sitting here looking at PRs going like, "should I run CI now that they pushed an update?" Or should I like, give them a few minutes in case they are going to push another commit? This is madness.
4
1
38
Yeah, they’re going to have to expand their definition of β€œtrusted” pretty quickly I think. It’s not like they don’t have a lot of data; I a GH user for 11 years, with dozens of source repos (some even popular!) am extremely unlikely to attempt to abuse the platform for mining.
1
5
Indeed. Even something like, "has contributed to my repo before" allowing CI to be automatic would be a big improvement. I'm sure GitHub is working on something along these lines to fix it, but oh man, I hope it comes soon.
2
4
Replying to @burntsushi5 @urschrei
I thought that was what it was meant to be. i.e. only first-time contributors get caught with this.

May 8, 2021 Β· 5:06 PM UTC

1
2
Replying to @dsilverstone @burntsushi5 @urschrei
I'm pretty sure that is the case on a per-repo basis. If they did a site wide "trust" level, that would create a black market for accounts pretty quickly which I think they want to avoid