Re: [PR] Fix PR number on 3.0.2 release note entry [airflow]
kaxil commented on code in PR #51637: URL: https://github.com/apache/airflow/pull/51637#discussion_r2143053115 ## RELEASE_NOTES.rst: ## @@ -71,7 +71,7 @@ Bug Fixes - Restored backward compatibility for the ``/run`` API endpoint for older Task SDK clients - Fixed dropdown overflow and error text styling in ``FlexibleForm`` component (#50845) - Corrected DAG tag rendering to display ``+1 more`` when tags exceed the display limit by one (#50669) -- Fix permission check on the ui config endpoint (#50608) +- Fix permission check on the ui config endpoint (#50564) Review Comment: huh no clue -- 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]
Re: [PR] Fix PR number on 3.0.2 release note entry [airflow]
github-actions[bot] commented on PR #51637: URL: https://github.com/apache/airflow/pull/51637#issuecomment-2965660940 ### Backport failed to create: v3-0-test. View the failure log Run details Status Branch Result ❌ v3-0-test https://github.com/apache/airflow/commit/61e9b08604ed6017421e59bea148820328bb9c3b";> You can attempt to backport this manually by running: ```bash cherry_picker 61e9b08 v3-0-test ``` This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking the files that need manual conflict resolution. After you have resolved the conflicts, you can continue the backport process by running: ```bash cherry_picker --continue ``` -- 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]
Re: [PR] Fix PR number on 3.0.2 release note entry [airflow]
potiuk merged PR #51637: URL: https://github.com/apache/airflow/pull/51637 -- 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]
Re: [PR] Fix PR number on 3.0.2 release note entry [airflow]
boring-cyborg[bot] commented on PR #51637: URL: https://github.com/apache/airflow/pull/51637#issuecomment-2965661130 Awesome work, congrats on your first merged pull request! You are invited to check our [Issue Tracker](https://github.com/apache/airflow/issues) for additional contributions. -- 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]
Re: [PR] Fix PR number on 3.0.2 release note entry [airflow]
boring-cyborg[bot] commented on PR #51637: URL: https://github.com/apache/airflow/pull/51637#issuecomment-2964466799 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]( https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst#prerequisites-for-pre-commit-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: [email protected] Slack: https://s.apache.org/airflow-slack -- 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]
