This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-9-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit dff4a1283cf20a56f7b05ae3e003e8887c0329fc Author: Andrey Anshin <[email protected]> AuthorDate: Sat May 4 15:08:46 2024 +0400 Add whitespace after inline literal in docs (#39401) (cherry picked from commit a1c873cfb82b7b4b57dfddd14f4d5624957983b9) --- docs/apache-airflow/core-concepts/dag-run.rst | 2 +- docs/apache-airflow/templates-ref.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/core-concepts/dag-run.rst b/docs/apache-airflow/core-concepts/dag-run.rst index 343e50cadd..02fd30c156 100644 --- a/docs/apache-airflow/core-concepts/dag-run.rst +++ b/docs/apache-airflow/core-concepts/dag-run.rst @@ -255,7 +255,7 @@ Using UI In the UI the parameters to trigger a DAG can be better represented via ``params`` definition as described in :ref:`concepts:params` documentation. Via defined params a proper form for value entry is rendered. -If the DAG does not define ``params``the form is usually skipped, via the configuration option ``show_trigger_form_if_no_params`` +If the DAG does not define ``params`` the form is usually skipped, via the configuration option ``show_trigger_form_if_no_params`` it is possible to force the display the classic form of a dict-only entry to pass configuration options. .. image:: ../img/example_passing_conf.png diff --git a/docs/apache-airflow/templates-ref.rst b/docs/apache-airflow/templates-ref.rst index 8f5e3ff070..8a03575b46 100644 --- a/docs/apache-airflow/templates-ref.rst +++ b/docs/apache-airflow/templates-ref.rst @@ -127,7 +127,7 @@ Deprecated Variable Description ``{{ tomorrow_ds }}`` the day after the execution date as ``YYYY-MM-DD`` ``{{ tomorrow_ds_nodash }}`` the day after the execution date as ``YYYYMMDD`` ``{{ prev_execution_date_success }}`` execution date from prior successful DAG run; - you may be able to use ``prev_data_interval_start_success``instead if + you may be able to use ``prev_data_interval_start_success`` instead if the timetable/schedule you use for the DAG defines ``data_interval_start`` compatible with the legacy ``execution_date``. ===================================== ==========================================================================
