This is an automated email from the ASF dual-hosted git repository. potiuk pushed a commit to branch v2-2-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 1b1bfc5b4a1a3bb843e4912ac750bdb038ce2881 Author: aabhaschopra <[email protected]> AuthorDate: Fri Jan 21 19:59:26 2022 +0530 Fix grammar in ``dags.rst`` (#20988) grammar correction (cherry picked from commit 754d8bcb5a2d461b71bebfa261a0c41a995d79e4) --- docs/apache-airflow/concepts/dags.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/dags.rst b/docs/apache-airflow/concepts/dags.rst index 8d9b387..3edaf35 100644 --- a/docs/apache-airflow/concepts/dags.rst +++ b/docs/apache-airflow/concepts/dags.rst @@ -260,7 +260,7 @@ The task_id returned by the Python function has to reference a task directly dow .. image:: /img/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 be still be run, even though it was not returned as part of the branch decision. + 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. The ``BranchPythonOperator`` can also be used with XComs allowing branching context to dynamically decide what branch to follow based on upstream tasks. For example:
