This is an automated email from the ASF dual-hosted git repository. vatsrahul1001 pushed a commit to branch backport-6bba9b6-v3-3-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 23633108ec9c285ef665a14c19e47ddd9863f7f2 Author: Wei Lee <[email protected]> AuthorDate: Tue Jul 7 16:27:59 2026 +0800 Fix sphinx build error (#69505) (cherry picked from commit 6bba9b65d39d67030a526220253a0c643919ea24) --- airflow-core/docs/best-practices.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/airflow-core/docs/best-practices.rst b/airflow-core/docs/best-practices.rst index 2a3be332d16..724398c9f82 100644 --- a/airflow-core/docs/best-practices.rst +++ b/airflow-core/docs/best-practices.rst @@ -852,7 +852,7 @@ You can use environment variables to parameterize the Dag. Mocking variables and connections ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -When you write tests for code that uses variables or a connection, you must ensure that they exist when you run the tests. The obvious solution is to save these objects to the database so they can be read while your code is executing. However, reading and writing objects to the database are burdened with additional time overhead. In order to speed up the test execution, it is worth simulating the existence of these objects without saving them to the database. For this, you can create env [...] +When you write tests for code that uses variables or a connection, you must ensure that they exist when you run the tests. The obvious solution is to save these objects to the database so they can be read while your code is executing. However, reading and writing objects to the database are burdened with additional time overhead. In order to speed up the test execution, it is worth simulating the existence of these objects without saving them to the database. For this, you can create env [...] For variable, use :envvar:`AIRFLOW_VAR_{KEY}`.
