This is an automated email from the ASF dual-hosted git repository.

guanmingchiu pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v3-1-test by this push:
     new 62c6affafe5 [v3-1-test] Clarify ExternalTaskSensor path in dags.rst 
(#61555) (#61617)
62c6affafe5 is described below

commit 62c6affafe5142dcece781ffcb221164097e3bca
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Feb 9 20:51:10 2026 +0800

    [v3-1-test] Clarify ExternalTaskSensor path in dags.rst (#61555) (#61617)
    
    (cherry picked from commit 82b345f573b51a2b53c1d23b3d2cd011b971ca65)
    
    Co-authored-by: Thejana Weththasinghe 
<[email protected]>
---
 airflow-core/docs/core-concepts/dags.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/airflow-core/docs/core-concepts/dags.rst 
b/airflow-core/docs/core-concepts/dags.rst
index b1bb0c8bec2..ef16238a000 100644
--- a/airflow-core/docs/core-concepts/dags.rst
+++ b/airflow-core/docs/core-concepts/dags.rst
@@ -771,7 +771,7 @@ relationships, dependencies between Dags are a bit more 
complex. In general, the
 in which one Dag can depend on another:
 
 - triggering - 
:class:`~airflow.providers.standard.operators.trigger_dagrun.TriggerDagRunOperator`
-- waiting - 
:class:`~airflow.providers.standard.sensors.external_task_sensor.ExternalTaskSensor`
+- waiting - 
:class:`~airflow.providers.standard.sensors.external_task.ExternalTaskSensor`
 
 Additional difficulty is that one Dag could wait for or trigger several runs 
of the other Dag
 with different data intervals. The **Dag Dependencies** view

Reply via email to