This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 39b5871e16f Fix grammar, casing, and typo across testing docs and prek
scripts (#72252)
39b5871e16f is described below
commit 39b5871e16f8b89e6c1a4b7fdabd39220bef22bf
Author: Chareonwit Kunna <[email protected]>
AuthorDate: Sat Aug 29 20:44:52 2026 +0700
Fix grammar, casing, and typo across testing docs and prek scripts (#72252)
- Follow Dag naming conventions in dag_testing.rst and
airflow_e2e_tests.rst.
- Fix missing preposition and casing in airflow_e2e_tests.rst.
- Fix typo 'consolidte' -> 'consolidate' in
check_supervisor_schemas_versions.py.
---
contributing-docs/testing/airflow_e2e_tests.rst | 8 ++++----
contributing-docs/testing/dag_testing.rst | 6 +++---
scripts/ci/prek/check_supervisor_schemas_versions.py | 2 +-
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/contributing-docs/testing/airflow_e2e_tests.rst
b/contributing-docs/testing/airflow_e2e_tests.rst
index 792465788dc..c4efb70e1e7 100644
--- a/contributing-docs/testing/airflow_e2e_tests.rst
+++ b/contributing-docs/testing/airflow_e2e_tests.rst
@@ -49,11 +49,11 @@ Running E2E Tests
Adding new E2E Tests
--------------------
-1. To Add new Dags for E2E tests, you can add them to the dags folder in
``./airflow-e2e-tests/tests/dags`` and update
-the DAG_IDS constant in
``./airflow-e2e-tests/tests/basic_tests/test_example_dags.py`` file to include
the new Dags ids.
-This will trigger Dag execution and validate the Dag run successfully.
+1. To add new Dags for E2E tests, you can add them to the dags folder in
``./airflow-e2e-tests/tests/dags`` and update
+the DAG_IDS constant in
``./airflow-e2e-tests/tests/basic_tests/test_example_dags.py`` file to include
the new Dag IDs.
+This will trigger Dag execution and validate that the Dag runs successfully.
-2. To add new test cases, create a new test file or add it any existing files
in the ``./airflow-e2e-tests/tests/*``
+2. To add new test cases, create a new test file or add it to any existing
files in ``./airflow-e2e-tests/tests/*``.
Airflow E2E tests in CI
diff --git a/contributing-docs/testing/dag_testing.rst
b/contributing-docs/testing/dag_testing.rst
index ca75e506dbf..d39e22a73f3 100644
--- a/contributing-docs/testing/dag_testing.rst
+++ b/contributing-docs/testing/dag_testing.rst
@@ -20,7 +20,7 @@ Dag Testing
===========
To ease and speed up the process of developing Dags, you can use
-py:meth:`~airflow.models.dag.DAG.test`, which will run a dag in a single
process.
+py:meth:`~airflow.models.dag.DAG.test`, which will run a Dag in a single
process.
To set up the IDE:
@@ -35,7 +35,7 @@ To set up the IDE:
2. Run and debug the Dag file.
-You can also run the dag in the same manner with the Airflow CLI command
``airflow dags test``:
+You can also run the Dag in the same manner with the Airflow CLI command
``airflow dags test``:
.. code-block:: bash
@@ -43,7 +43,7 @@ You can also run the dag in the same manner with the Airflow
CLI command ``airfl
airflow dags test example_branch_operator 2018-01-01
By default ``/files/dags`` folder is mounted from your local
``<AIRFLOW_SOURCES>/files/dags`` and this is
-the directory used by Airflow scheduler and webserver to scan dags for. You
can place your dags there
+the directory used by Airflow scheduler and webserver to scan Dags for. You
can place your Dags there
to test them.
The Dags can be run in the main version of Airflow but they also work
diff --git a/scripts/ci/prek/check_supervisor_schemas_versions.py
b/scripts/ci/prek/check_supervisor_schemas_versions.py
index 348382a3e67..5e011e8f43f 100755
--- a/scripts/ci/prek/check_supervisor_schemas_versions.py
+++ b/scripts/ci/prek/check_supervisor_schemas_versions.py
@@ -57,7 +57,7 @@ CORE_PROCESSOR_PATH =
"airflow-core/src/airflow/dag_processing/processor.py"
DUMP_SCRIPT = Path(__file__).parent / "dump_supervisor_schemas.py"
-# TODO: We should consolidte the common logic with
check_execution_api_versions.py into common_prek_utils
+# TODO: We should consolidate the common logic with
check_execution_api_versions.py into common_prek_utils
def get_target_branch() -> str:
"""Branch to compare against. GITHUB_BASE_REF for PRs, DEFAULT_BRANCH in
CI, else main."""
return os.environ.get("GITHUB_BASE_REF") or
os.environ.get("DEFAULT_BRANCH") or "main"
