Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update environments documentation links. #23920

Merged
merged 4 commits into from
May 25, 2022
Merged

Update environments documentation links. #23920

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b186655
Update environments documentation links.
igorborgest May 25, 2022
d7e5d28
Update CONTRIBUTING.rst
igorborgest May 25, 2022
737a62e
Update CONTRIBUTING.rst
igorborgest May 25, 2022
ef0a5a8
Update CONTRIBUTING.rst
igorborgest May 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions CONTRIBUTING.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <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 <BREEZE.rst>`_ that provides
an end-to-end CI solution with all software dependencies covered.

The table below summarizes differences between the environments:
Expand Down Expand Up @@ -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 <BREEZE.rst>`__ with all required packages
pre-installed.

- You need to make sure that your local environment is consistent with other
Expand Down