[rtrindvg]

Adds section about disappearing DAGs on UI, as discussed on #44495.

I tried to make the new question have the same tone as the rest of the FAQ, so I condensed A LOT of the explanations in shorter descriptions and used links to point to more complete explanations, as directed by @potiuk in the original discussion. If I went to far in this direction, I can try to increment it.

Also I am not proficient with Sphinx internal links syntax, but I tried my best to make sure they are correct.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[potiuk]

Nice!

[potiuk]

You can folow the https://github.com/apache/airflow/blob/main/contributing-docs/11_documentation_building.rst to build the docs locally and check if links render correctly

[potiuk]

Some static checks need fixing :)

[potiuk]

Best - install pre-commit and it will fix them automatically for you

[phanikumv]

@rtrindvg just checking in to see if you need help to resolve the CI failures here

cc @amoghrajesh

[amoghrajesh]

@rtrindvg yeah it should be a simple fix, let me still know if you need help

[amoghrajesh]

@rtrindvg i just pushed a fix to your branch to fix static checks. FYI @phanikumv

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[github-actions]

Backport successfully created: v3-0-test

Status	Branch	Result
✅	v3-0-test

[rtrindvg]

@rtrindvg i just pushed a fix to your branch to fix static checks. FYI @phanikumv

Thank you so much, just really swamped with a career turmoil at the moment and could not spend time on this for now. Thanks for the fix and the subsequent merge.