Adaverse opened a new pull request, #29338: URL: https://github.com/apache/airflow/pull/29338
Background: While going through the Dynamic DAG Generation doc -> https://airflow.apache.org/docs/apache-airflow/stable/howto/dynamic-dag-generation.html, found out one of the links to best practices while using airflow variable didn't work with error 404 not found. Have made changes and fixed the reference that points to the correct link now which is -> https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html#airflow-variables. Changes done: replaced ```Airflow Variables <_best_practices/airflow_variables>`_``` with ```:ref:`best_practices/airflow_variables``` <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
