potiuk commented on issue #25088: URL: https://github.com/apache/datafusion/issues/25088#issuecomment-6384691569
Our version in Airflow (and one that will hopefully turn into reusable action set) - is way more sophisticated. We aim for practically **no** change in the workflow from the maintainer point of view: * we will post instructions for the contributors who have their fork workflow's disabled (which is the default) - when they do not have tehme * we automatically will approve workflow for external contributors that are **safe** - but those workflow will do **nothing** for them - they will just quit after first check and succeed * however we have a scheduled workflow that will monitor the remotely run "push" actions and will mirror their statuses to the PR - so the PR will **look** as if the PR is running - also links from those status messages will link to the jobs running in the contributor's workflows. * We will be able to control who can and who cannot use the runners in ASF - by default, Airflow maintainers, but we will also enable our stakeholders who use their own "organisation" forks to use them + we will be able to selectively give access to specific users. The PR's status will be also set depending on the status of the fork run. This all will be done via scheduled workflow that will check and update status for such open PRs. Generally we aim for practically 0 change in how you interact with GH PRs via UI. This all **shoudl** work - no need (such as in rust workflow) for contributors to post their workflow run links - and even know that something changed. Once they enable the workflows in their fork - things will work for them "as usual" (with little delay on refreshing status of their jobs to the PR). Once I get it into reusable action, maybe you could try to switch to it. I will post it here once I have it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
