Hello @n1hility -> after GitHub Actions added support for worfklow_run events (https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/ I decided to write my own action that would support it and make it easy to use for pull requests from forks. The previous workaround with the scheduled run was really not a nice one.
I needed it for the Apache Airflow project - where I am one of the committers and a PMC member, and I have just merged a PR (after extensive testing on my own fork) where I used my action. You can see it used here: https://github.com/apache/airflow/blob/master/.github/workflows/build-images-workflow-run.yml
Here is the action (it has a lot of examples and very comprehensive documentation):
And you can see some of the sequence diagrams of how it actually works in the context of Airflow in this PR with the documentation: https://github.com/PolideaInternal/airflow/blob/future-ci-documentation/CI.rst#ci-sequence-diagrams
I think it would be great to somehow point out the action of mine, as the action of yours is already somehow deprecated when it comes to workflow_run. - or alternatively, if you would like to pull in my changes and make me a contributor if you already have a lot of users for your action and you want to keep on maintaining it, this might be another option.
Happy to discuss :)
Hello @n1hility -> after GitHub Actions added support for
worfklow_runevents (https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/ I decided to write my own action that would support it and make it easy to use for pull requests from forks. The previous workaround with the scheduled run was really not a nice one.I needed it for the Apache Airflow project - where I am one of the committers and a PMC member, and I have just merged a PR (after extensive testing on my own fork) where I used my action. You can see it used here: https://github.com/apache/airflow/blob/master/.github/workflows/build-images-workflow-run.yml
Here is the action (it has a lot of examples and very comprehensive documentation):
And you can see some of the sequence diagrams of how it actually works in the context of Airflow in this PR with the documentation: https://github.com/PolideaInternal/airflow/blob/future-ci-documentation/CI.rst#ci-sequence-diagrams
I think it would be great to somehow point out the action of mine, as the action of yours is already somehow deprecated when it comes to
workflow_run. - or alternatively, if you would like to pull in my changes and make me a contributor if you already have a lot of users for your action and you want to keep on maintaining it, this might be another option.Happy to discuss :)