saivarmaakireddy270-star commented on PR #64850: URL: https://github.com/apache/airflow/pull/64850#issuecomment-4201322564
i am logging out of apache server at the time of 23:57 pm and login hours are 5 hours On Tue, Apr 7, 2026 at 9:22 PM boring-cyborg[bot] ***@***.***> wrote: > *boring-cyborg[bot]* left a comment (apache/airflow#64850) > <https://github.com/apache/airflow/pull/64850#issuecomment-4200364254> > > 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 > <https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst#prerequisites-for-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 > <https://github.com/apache/airflow/blob/main/airflow-core/docs/howto/custom-operator.rst> > Consider adding an example DAG that shows how users should use it. > - Consider using Breeze environment > <https://github.com/apache/airflow/blob/main/dev/breeze/doc/README.rst> > 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 > <https://www.apache.org/foundation/policies/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 > <https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#coding-style-and-best-practices> > . > - 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: ***@***.*** > Slack: https://s.apache.org/airflow-slack > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/airflow/pull/64850#issuecomment-4200364254>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/CAVXSMYYSWWCQHSMQFU24WL4UUP4LAVCNFSM6AAAAACXPUDJH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBQGM3DIMRVGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- 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]
