potiuk commented on PR #32089: URL: https://github.com/apache/airflow/pull/32089#issuecomment-1612117429
All the other actions you see in CI can also be generally reproduced locally with Breeze - this is a one-stop CLI that allows you to run all kinds of test and steps locally and fix them before the push. For example you can see that docs building fails for you - but when you look at the command that is run, you can run the same breeze command and generally you should be able to reproduce it locally. <img width="1672" alt="Screenshot 2023-06-28 at 23 11 21" src="https://github.com/apache/airflow/assets/595491/1207c3a7-8c42-4785-83b7-0237ea3efdaa";> There are docs for Breeze in https://github.com/apache/airflow/blob/main/BREEZE.rst - explaining installation steps and all commands with help and screenshots. Also it supports auto-completion and `--help` in case you are in doubt what parameters you can use. Also we have a rather comprehensive example on how to run the suite of tests locally (we invested quite a lot of effort so that the contributors can easily locally reproduce all CI jobs. For example runnig all kind of unit/integration/system tests is described in https://github.com/apache/airflow/blob/main/TESTING.rst All those docs are nicely linked from "CONTRIBUTING.rst" which has step-by-step instructions and helpful guidelines on various parts of the development environment (including docs on how to setup tests in the IDEs of your choice). I hope that will be helpful. I'd usually recommend to run those checks locally if we know they are failing, and only pushing next attempt after you fixed them locally - that's what I usually do. -- 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]
