Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Fix heading for Mocking section in best-practices.rst #13658

Merged
merged 1 commit into from Jan 13, 2021

Conversation

kaxil
Copy link
Member

@kaxil kaxil commented Jan 13, 2021

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

image
image


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

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
@kaxil kaxil merged commit 21446d6 into apache:master Jan 13, 2021
@kaxil kaxil deleted the fix-heading branch January 13, 2021 19:26
kaxil added a commit that referenced this pull request Jan 21, 2021
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

(cherry picked from commit 21446d6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants