This is an automated email from the ASF dual-hosted git repository. amoghdesai pushed a commit to branch amoghrajesh-patch-2 in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 97456a284c7b594e52ccb848bcc6a07fcc6e44fc Author: Amogh Desai <[email protected]> AuthorDate: Fri Jan 12 10:49:12 2024 +0530 Fixing minor grammatical nits in dags.rst --- docs/apache-airflow/core-concepts/dags.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/core-concepts/dags.rst b/docs/apache-airflow/core-concepts/dags.rst index 2a7829971e..5965a6aa40 100644 --- a/docs/apache-airflow/core-concepts/dags.rst +++ b/docs/apache-airflow/core-concepts/dags.rst @@ -165,8 +165,8 @@ While both DAG constructors get called when the file is accessed, only ``dag_1`` You can also provide an ``.airflowignore`` file inside your ``DAG_FOLDER``, or any of its subfolders, which describes patterns of files for the loader to ignore. It covers the directory it's in plus all subfolders underneath it. See :ref:`.airflowignore <concepts:airflowignore>` below for details of the file syntax. -In the case where the ``.airflowignore`` does not meet your needs and you want a more flexible way to control if a python file needs to be parsed by Airflow. You can plug your callable by setting ``might_contain_dag_callable`` in the config file. -Note, this callable will replace the default Airflow heuristic, i.e. checking if the strings ``airflow`` and ``dag`` (case-insensitively) in the file. +In the case where the ``.airflowignore`` does not meet your needs and you want a more flexible way to control if a python file needs to be parsed by airflow, you can plug your callable by setting ``might_contain_dag_callable`` in the config file. +Note, this callable will replace the default Airflow heuristic, i.e. checking if the strings ``airflow`` and ``dag`` (case-insensitively) are present in the python file. .. code-block::
