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

#46316 Issue: Update start.rst #46335

Merged
merged 7 commits into from
Feb 5, 2025
Merged

#46316 Issue: Update start.rst #46335

merged 7 commits into from
Feb 5, 2025

Conversation

SaumilPatel03
Copy link
Contributor

@SaumilPatel03 SaumilPatel03 commented Jan 31, 2025


^ 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 newsfragments.

Copy link

boring-cyborg bot commented Jan 31, 2025

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

@SaumilPatel03 SaumilPatel03 requested a review from RNHTTR February 1, 2025 05:40
@SaumilPatel03
Copy link
Contributor Author

@RNHTTR @potiuk Can you please review my changes.

@SaumilPatel03 SaumilPatel03 requested a review from eladkal February 3, 2025 17:53
@potiuk
Copy link
Member

potiuk commented Feb 5, 2025

Soem static checks are failing

@SaumilPatel03 SaumilPatel03 requested a review from potiuk February 5, 2025 16:47
@potiuk potiuk merged commit 0a3eb17 into apache:main Feb 5, 2025
42 checks passed
Copy link

boring-cyborg bot commented Feb 5, 2025

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

insomnes pushed a commit to insomnes/airflow that referenced this pull request Feb 6, 2025
* apache#46316 Issue: Update start.rst

* Update start.rst

Added the link for detailed error

* Removed single ticks
niklasr22 pushed a commit to niklasr22/airflow that referenced this pull request Feb 8, 2025
* apache#46316 Issue: Update start.rst

* Update start.rst

Added the link for detailed error

* Removed single ticks
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 17, 2025
* apache#46316 Issue: Update start.rst

* Update start.rst

Added the link for detailed error

* Removed single ticks
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

5 participants