> > If push status is visible in the PR, I don't see the need for such a > workflow. > > From my experience, when submitting a PR from a fork, this status sometimes > shows along with the latest commit, sometimes in the CI status section, and > sometimes not at all.
You are right. It seems to work only within the same repo, so the PR in my own repo was a wrong example for this. Then ideally we need this workflow together with the main change. I have looked at the workflows Hadoop and Spark have for this purpose, and they seem to be very fragile and hard to test. I would rather wait for for Airflow's implementation, for which they plan to publish reusable bits. In the meantime let's look for other alternatives. -Attila --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
