> > Ooh, thank you Dawid! And it's now merged, so we now have a decent timeout > protection, so if a bad actor tries to crypto mine or run some distributed > LLM or whatever, at least the wasted resources are bounded by how long a > "typical" legitimate run takes, plus generous buffer. So given this > protection, why require the added manual approval step :) > > Net/net I don't think we have to do anything more here ... for now I'll try > to make a periodic effort myself to approve & run these blocked jobs. Maybe > that's enough to create a smoother first-contributor experience.
We can write a bot to do this. Why do it manually? https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#approve-a-workflow-run-for-a-fork-pull-request --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
