The GitHub Actions job "Tests" on airflow.git has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 4d6be32d350fcdad71b14cbdda2b1466ab83d27c / Jarek Potiuk <ja...@potiuk.com> Breeze installation is separated into composite action We've been long waiting for an opportunity to simplify our workflows by extracting some steps of the workflow and waiting for something like yaml anchor supoprt... But the solution was under our noses for quite some time. No idea how I missed that - since August 2021 we should be able to use composite actions to simplify our GitHub Actions. The only explanation I have is that I have not connected two facts: * you can have composite actions defined as separate workflows you can use as step in your Job * the documentation for composite actions does not mention the case that your action can be INSIDE your repository. All the examples refer to an action defined in ANOTHER repository. That made it confusing to understand that you can actually do it all as an action inside your repo. Let me rectify the mistake and extract some of the common yaml entries one-by-one - first is Installing Breeze which is pretty common and most of the jobs use it. This one will be followed up with some other jobs simplified in the same matter. Report URL: https://github.com/apache/airflow/actions/runs/3353854376 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: jobs-unsubscr...@airflow.apache.org For additional commands, e-mail: jobs-h...@airflow.apache.org
