This is an automated email from the ASF dual-hosted git repository.
Lee-W 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 40a10b46add fix oudated img links in `dags.rst` (#67357)
40a10b46add is described below
commit 40a10b46add7a3a1393f057e4583a0842fcbd5cc
Author: Aaron Chen <[email protected]>
AuthorDate: Tue May 26 18:50:59 2026 -0700
fix oudated img links in `dags.rst` (#67357)
---
airflow-core/docs/core-concepts/dags.rst | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/airflow-core/docs/core-concepts/dags.rst
b/airflow-core/docs/core-concepts/dags.rst
index 8b19ba07e41..0cc8fbfa9d0 100644
--- a/airflow-core/docs/core-concepts/dags.rst
+++ b/airflow-core/docs/core-concepts/dags.rst
@@ -26,7 +26,7 @@ Dags
Here's a basic example Dag:
-.. image:: /img/ui-light/basic_dag.png
+.. image:: ../img/ui-light/basic_dag.png
It defines four Tasks - A, B, C, and D - and dictates the order in which they
have to run, and which tasks depend on what others. It will also say how often
to run the Dag - maybe "every 5 minutes starting tomorrow", or "every day since
January 1st, 2020".
@@ -331,7 +331,7 @@ The task_id returned by the Python function has to
reference a task directly dow
.. note::
When a Task is downstream of both the branching operator *and* downstream
of one or more of the selected tasks, it will not be skipped:
- .. image:: /img/ui-light/branch_note.png
+ .. image:: ../img/ui-light/branch_note.png
The paths of the branching task are ``branch_a``, ``join`` and
``branch_b``. Since ``join`` is a downstream task of ``branch_a``, it will
still be run, even though it was not returned as part of the branch decision.
@@ -411,7 +411,7 @@ In the case of this Dag:
* ``task3`` is downstream of ``task1`` and ``task2`` and because of the
default :ref:`trigger rule <concepts:trigger-rules>` being ``all_success`` will
receive a cascaded skip from ``task1``.
* ``task4`` is downstream of ``task1`` and ``task2``, but it will not be
skipped, since its ``trigger_rule`` is set to ``all_done``.
-.. image:: /img/latest_only_with_trigger.png
+.. image:: ../img/latest_only_with_trigger.png
.. _concepts:depends-on-past:
@@ -492,11 +492,11 @@ You can also combine this with the
:ref:`concepts:depends-on-past` functionality
``join`` is downstream of ``follow_branch_a`` and ``branch_false``. The
``join`` task will show up as skipped because its ``trigger_rule`` is set to
``all_success`` by default, and the skip caused by the branching operation
cascades down to skip a task marked as ``all_success``.
- .. image:: /img/ui-light/branch_without_trigger.png
+ .. image:: ../img/ui-light/branch_without_trigger.png
By setting ``trigger_rule`` to ``none_failed_min_one_success`` in the
``join`` task, we can instead get the intended behaviour:
- .. image:: /img/ui-light/branch_with_trigger.png
+ .. image:: ../img/ui-light/branch_with_trigger.png
Setup and teardown
@@ -554,7 +554,7 @@ Tasks in TaskGroups live on the same original Dag, and
honor all the Dag setting
.. seealso::
API reference for :class:`~airflow.sdk.TaskGroup` and
:class:`~airflow.sdk.task_group`
-.. image:: /img/ui-light/task_group.gif
+.. image:: ../img/ui-light/task_group.gif
Dependency relationships can be applied across all tasks in a TaskGroup with
the ``>>`` and ``<<`` operators. For example, the following code puts ``task1``
and ``task2`` in TaskGroup ``group1`` and then puts both tasks upstream of
``task3``:
@@ -638,7 +638,7 @@ Or, you can pass a Label object to
``set_upstream``/``set_downstream``:
Here's an example Dag which illustrates labeling different branches:
-.. image:: /img/ui-light/edge_label_example.png
+.. image:: ../img/ui-light/edge_label_example.png
.. exampleinclude:: /../src/airflow/example_dags/example_branch_labels.py
:language: python
