[airflow] branch master updated: Docs: Fix heading for Mocking section in best-practices.rst (#13658)

[ka...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kaxilnaik pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/master by this push:
     new 21446d6  Docs: Fix heading for Mocking section in best-practices.rst (#13658)
21446d6 is described below

commit 21446d6f706b9e147e895692fa9d715263787bea
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Wed Jan 13 19:26:53 2021 +0000

    Docs: Fix heading for Mocking section in best-practices.rst (#13658)
    
    Currently 'Mocking variables and connections' section is on same level
    as Best Practices (`h1` heading):
    
    http://apache-airflow-docs.s3-website.eu-central-1.amazonaws.com/docs/apache-airflow/latest/best-practices.html
    
    Because of which this heading shows in TOC
---
 docs/apache-airflow/best-practices.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/apache-airflow/best-practices.rst b/docs/apache-airflow/best-practices.rst
index 56c834c..2289269 100644
--- a/docs/apache-airflow/best-practices.rst
+++ b/docs/apache-airflow/best-practices.rst
@@ -238,7 +238,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 [...]