potiuk commented on code in PR #25577:
URL: https://github.com/apache/airflow/pull/25577#discussion_r939640405
##########
docs/apache-airflow/concepts/overview.rst:
##########
@@ -74,12 +74,14 @@ Or, with the ``set_upstream`` and ``set_downstream``
methods::
These dependencies are what make up the "edges" of the graph, and how Airflow
works out which order to run your tasks in. By default, a task will wait for
all of its upstream tasks to succeed before it runs, but this can be customized
using features like :ref:`Branching <concepts:branching>`, :ref:`LatestOnly
<concepts:latest-only>`, and :ref:`Trigger Rules <concepts:trigger-rules>`.
-To pass data between tasks you have two options:
+To pass data between tasks you have three options:
* :doc:`xcoms` ("Cross-communications"), a system where you can have tasks
push and pull small bits of metadata.
* Uploading and downloading large files from a storage service (either one you
run, or part of a public cloud)
+* TaskFlow API automatically passes data between tasks
Review Comment:
```suggestion
* TaskFlow API automatically passes data between tasks via implicit
:doc:`xcoms`
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
