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 prek-hooks 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: [email protected]
  Slack: https://s.apache.org/airflow-slack

Nice!. I will review soon

And if you include the issue in the PR description, it will make it easier for reviewers to review 😉
closes: #<issue-number> or related: #<issue-number>

And if you include the issue in the PR description, it will make it easier for reviewers to review 😉 closes: #<issue-number> or related: #<issue-number>

For some reason the PR is not getting linked to the issue even after adding closes and related issue number

And if you include the issue in the PR description, it will make it easier for reviewers to review 😉 closes: #<issue-number> or related: #<issue-number>

For some reason the PR is not getting linked to the issue even after adding closes and related issue number

@iharsh02 I have updated the description with closing and related issue its fine now

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

Cooool🎉🎉🎉