jedcunningham commented on code in PR #23920: URL: https://github.com/apache/airflow/pull/23920#discussion_r882055531
########## CONTRIBUTING.rst: ########## @@ -503,10 +503,10 @@ Development Environments There are two environments, available on Linux and macOS, that you can use to develop Apache Airflow: -- `Local virtualenv development environment <#local-virtualenv-development-environment>`_ +- `Local virtualenv development environment <https://github.com/apache/airflow/blob/main/LOCAL_VIRTUALENV.rst>`_ Review Comment: ```suggestion - `Local virtualenv development environment <LOCAL_VIRTUALENV.rst>`_ ``` These can be relative. ########## CONTRIBUTING.rst: ########## @@ -503,10 +503,10 @@ Development Environments There are two environments, available on Linux and macOS, that you can use to develop Apache Airflow: -- `Local virtualenv development environment <#local-virtualenv-development-environment>`_ +- `Local virtualenv development environment <https://github.com/apache/airflow/blob/main/LOCAL_VIRTUALENV.rst>`_ that supports running unit tests and can be used in your IDE. -- `Breeze Docker-based development environment <#breeze-development-environment>`_ that provides +- `Breeze Docker-based development environment <https://github.com/apache/airflow/blob/main/BREEZE.rst>`_ that provides Review Comment: ```suggestion - `Breeze Docker-based development environment <BREEZE.rst>`_ that provides ``` ########## CONTRIBUTING.rst: ########## @@ -564,7 +564,7 @@ Limitations: real unit tests. Technically, to run integration tests, you can configure and install the dependencies on your own, but it is usually complex. Instead, you are recommended to use - `Breeze development environment <#breeze-development-environment>`__ with all required packages + `Breeze development environment <https://github.com/apache/airflow/blob/main/BREEZE.rst>`__ with all required packages Review Comment: ```suggestion `Breeze development environment <BREEZE.rst>`__ with all required packages ``` -- 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]
