This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 3ad66157755 Swap contributing links to absolute links (#48085)
3ad66157755 is described below
commit 3ad66157755140423ab87d7da168cbead9f33fc2
Author: Jed Cunningham <[email protected]>
AuthorDate: Fri Mar 21 20:38:32 2025 -0600
Swap contributing links to absolute links (#48085)
Most of these work as a relative link, but they are fragile - if you get
the level of nesting wrong they break. Absolute is more resilient.
---
airflow-core/src/airflow/ui/CONTRIBUTING.md | 2 +-
dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md | 2 +-
dev/breeze/doc/01_installation.rst | 2 +-
dev/breeze/doc/02_customizing.rst | 2 +-
dev/breeze/doc/03_developer_tasks.rst | 2 +-
dev/breeze/doc/05_test_commands.rst | 4 ++--
dev/breeze/doc/09_release_management_tasks.rst | 2 +-
dev/breeze/doc/README.rst | 2 +-
dev/breeze/doc/ci/07_running_ci_locally.md | 2 +-
generated/README.md | 2 +-
providers/MANAGING_PROVIDERS_LIFECYCLE.rst | 6 +++---
11 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/airflow-core/src/airflow/ui/CONTRIBUTING.md
b/airflow-core/src/airflow/ui/CONTRIBUTING.md
index 73ff3ee00df..83d734bafdf 100644
--- a/airflow-core/src/airflow/ui/CONTRIBUTING.md
+++ b/airflow-core/src/airflow/ui/CONTRIBUTING.md
@@ -32,4 +32,4 @@ Manually:
## More
-See [node environment setup
docs](../../contributing-docs/14_node_environment_setup.rst)
+See [node environment setup
docs](/contributing-docs/14_node_environment_setup.rst)
diff --git a/dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md
b/dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md
index 324a35bcd66..23112e55de5 100644
--- a/dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md
+++ b/dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md
@@ -69,7 +69,7 @@ merges to `main` branch builds (also known as `canary`
builds) have separate mai
take care about refreshing the cache that is used to speed up our builds and
to speed up
rebuilding of [Breeze](./breeze/doc/README.rst) images for development
purpose. This is all happening automatically, usually:
-* The latest
[constraints](../contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files)
are pushed to appropriate branch after all tests succeed in the
+* The latest
[constraints](/contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files)
are pushed to appropriate branch after all tests succeed in the
`canary` build.
* The [images](breeze/doc/ci/02_images.md) in `ghcr.io` registry are refreshed
early at the beginning of the
diff --git a/dev/breeze/doc/01_installation.rst
b/dev/breeze/doc/01_installation.rst
index 9c053bf280b..cea7f5cdd55 100644
--- a/dev/breeze/doc/01_installation.rst
+++ b/dev/breeze/doc/01_installation.rst
@@ -84,7 +84,7 @@ Here is an example configuration with more than 200GB disk
space for Docker:
</div>
Note: If you use Colima, please follow instructions at:
-`Contributors Quick Start Guide
<../../../contributing-docs/03_contributors_quick_start.rst>`__
+`Contributors Quick Start Guide
</contributing-docs/03_contributors_quick_start.rst>`__
Docker Compose
--------------
diff --git a/dev/breeze/doc/02_customizing.rst
b/dev/breeze/doc/02_customizing.rst
index a6cf3905aeb..60932015472 100644
--- a/dev/breeze/doc/02_customizing.rst
+++ b/dev/breeze/doc/02_customizing.rst
@@ -141,7 +141,7 @@ Launching Breeze integrations
When Breeze starts, it can start additional integrations. Those are additional
docker containers
that are started in the same docker-compose command. Those are required by
some of the tests
-as described in `<../../../contributing-docs/testing/integration_tests.rst>`_.
+as described in `</contributing-docs/testing/integration_tests.rst>`_.
By default Breeze starts only airflow container without any integration
enabled. If you selected
``postgres`` or ``mysql`` backend, the container for the selected backend is
also started (but only the one
diff --git a/dev/breeze/doc/03_developer_tasks.rst
b/dev/breeze/doc/03_developer_tasks.rst
index d3fd1f01629..2bab6b5d74d 100644
--- a/dev/breeze/doc/03_developer_tasks.rst
+++ b/dev/breeze/doc/03_developer_tasks.rst
@@ -616,7 +616,7 @@ Note that you can also use the local virtualenv for Airflow
development without
This is a lightweight solution that has its own limitations.
More details on using the local virtualenv are available in the
-`Local Virtualenv <../../../contributing-docs/07_local_virtualenv.rst>`_.
+`Local Virtualenv </contributing-docs/07_local_virtualenv.rst>`_.
Auto-generating migration files
-------------------------------
diff --git a/dev/breeze/doc/05_test_commands.rst
b/dev/breeze/doc/05_test_commands.rst
index 8ebc77a4579..5719e028719 100644
--- a/dev/breeze/doc/05_test_commands.rst
+++ b/dev/breeze/doc/05_test_commands.rst
@@ -68,7 +68,7 @@ To run the whole test class:
You can re-run the tests interactively, add extra parameters to pytest and
modify the files before
re-running the test to iterate over the tests. You can also add more flags
when starting the
``breeze shell`` command when you run integration tests or system tests. Read
more details about it
-in the `testing doc <../../../contributing-docs/testing.rst>`_ where all the
test types and information on how to run them are explained.
+in the `testing doc </contributing-docs/testing.rst>`_ where all the test
types and information on how to run them are explained.
This applies to all kind of tests - all our tests can be run using pytest.
@@ -319,7 +319,7 @@ You can:
``breeze k8s delete-all-clusters`` commands as well as running complete
tests in parallel
via ``breeze k8s dump-logs`` command
-This is described in detail in `Testing Kubernetes
<../../../contributing-docs/testing/k8s_tests.rst>`_.
+This is described in detail in `Testing Kubernetes
</contributing-docs/testing/k8s_tests.rst>`_.
You can read more about KinD that we use in `The documentation
<https://kind.sigs.k8s.io/>`_
diff --git a/dev/breeze/doc/09_release_management_tasks.rst
b/dev/breeze/doc/09_release_management_tasks.rst
index 60632a4ef52..fd1320ffd03 100644
--- a/dev/breeze/doc/09_release_management_tasks.rst
+++ b/dev/breeze/doc/09_release_management_tasks.rst
@@ -428,7 +428,7 @@ Whenever ``pyproject.toml`` gets modified, the CI main job
will re-generate cons
files are stored in separated orphan branches: ``constraints-main``,
``constraints-2-0``.
Those are constraint files as described in detail in the
-`<../../../contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files>`_
contributing documentation.
+`</contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files>`_
contributing documentation.
You can use ``breeze release-management generate-constraints`` command to
manually generate constraints for
diff --git a/dev/breeze/doc/README.rst b/dev/breeze/doc/README.rst
index 570ca8b75da..9f5d0b9ad8e 100644
--- a/dev/breeze/doc/README.rst
+++ b/dev/breeze/doc/README.rst
@@ -33,7 +33,7 @@ We call it *Airflow Breeze* as **It's a Breeze to contribute
to Airflow**.
The advantages and disadvantages of using the Breeze environment vs. other
ways of testing Airflow
are described in
-`Integration test development environments
<../../../contributing-docs/06_development_environments.rst>`_.
+`Integration test development environments
</contributing-docs/06_development_environments.rst>`_.
You can use the Breeze environment to run Airflow's tests locally and
reproduce CI failures.
diff --git a/dev/breeze/doc/ci/07_running_ci_locally.md
b/dev/breeze/doc/ci/07_running_ci_locally.md
index 5f414667b01..878969ac7c9 100644
--- a/dev/breeze/doc/ci/07_running_ci_locally.md
+++ b/dev/breeze/doc/ci/07_running_ci_locally.md
@@ -124,7 +124,7 @@ of the options can be passed by `--flags` and some via
environment variables, fo
take a look at both if you want to be sure to reproduce the exact job
configuration. See the next chapter
for summary of the most important environment variables and options used in
the CI jobs.
-You can read more about it in [Breeze](../README.rst) and
[Testing](../../../../contributing-docs/09_testing.rst)
+You can read more about it in [Breeze](../README.rst) and
[Testing](/contributing-docs/09_testing.rst)
# Options and environment variables used
diff --git a/generated/README.md b/generated/README.md
index a52ac1934d0..490c6f81eaf 100644
--- a/generated/README.md
+++ b/generated/README.md
@@ -20,7 +20,7 @@
NOTE! The files in this folder are generated by pre-commit based on airflow
sources. They are not
supposed to be manually modified.
-You can read more about pre-commit hooks
[here](../contributing-docs/08_static_code_checks.rst#pre-commit-hooks).
+You can read more about pre-commit hooks
[here](/contributing-docs/08_static_code_checks.rst#pre-commit-hooks).
* `provider_dependencies.json` - is generated based on `provider.yaml` files
in `airflow/providers` and
based on the imports in the provider code. If you want to add new dependency
to a provider, you
diff --git a/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
b/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
index da88cc9b67f..d84a06eeaf2 100644
--- a/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
+++ b/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
@@ -30,7 +30,7 @@ Another recommendation that will help you is to look for a
provider that works s
help you to set up tests and other dependencies.
First, you need to set up your local development environment. See
-`Contributors Quick Start
<../../contributing-docs/03_contributors_quick_start.rst>`_
+`Contributors Quick Start
</contributing-docs/03_contributors_quick_start.rst>`_
if you did not set up your local environment yet. We recommend using
``breeze`` to develop locally. This way you
easily be able to have an environment more similar to the one executed by
GitHub CI workflow.
@@ -201,7 +201,7 @@ by ``pip``).
Integration tests
-----------------
-See `Airflow Integration Tests
<../../contributing-docs/testing/integration-tests.rst>`_
+See `Airflow Integration Tests
</contributing-docs/testing/integration-tests.rst>`_
Documentation
@@ -209,7 +209,7 @@ Documentation
An important part of building a new provider is the documentation.
Some steps for documentation occurs automatically by ``pre-commit`` see
-`Installing pre-commit guide
<../../contributing-docs/03_contributors_quick_start.rst#pre-commit>`_
+`Installing pre-commit guide
</contributing-docs/03_contributors_quick_start.rst#pre-commit>`_
Those are important files in the airflow source tree that affect providers.
The ``pyproject.toml`` in root
Airflow folder is automatically generated based on content of
``provider.yaml`` file in each provider
