choo121600 commented on code in PR #60158: URL: https://github.com/apache/airflow/pull/60158#discussion_r2664772599
########## contributing-docs/05_pull_requests.rst: ########## @@ -100,6 +100,31 @@ these guidelines: - Adhere to guidelines for commit messages described in this `article <https://cbea.ms/git-commit/>`__. This makes the lives of those who come after you (and your future self) a lot easier. +Gen-AI Assisted contributions +----------------------------- + +Generally, it's fine to use Gen-AI tools to help you create Pull Requests for Apache Airflow as long as you +adhere to the following guidelines: + +* Follow the `Apache Software Foundation (ASF) Generative Tooling guideliens <https://www.apache.org/legal/generative-tooling.html>`__. +* Ensure that you review and understand all code generated by Gen-AI tools before including it in your PR - + do not blindly trust the generated code. +* Make sure that the generated code adheres to the project's coding standards and best practices described + above +* Make sure to run all relevant static checks and tests locally to verify that the generated code works as + intended and does not introduce any issues. +* State in your PR description that you have used Gen-AI tools to assist in creating the PR. +* Be prepared to explain and justify the use of Gen-AI tools if asked by project maintainers or reviewers. +* Remember that the final responsibility for the code in your PR lies with you, regardless of whether + it was generated by a tool or written by you. +* By contributing code generated by Gen-AI tools, you agree to comply with the project's licensing terms + and any applicable laws and regulations. +* Remember that when you blindly copy & paste hallucinated code from Gen-AI tools, you are not improving your + skills as a developer and you might be introducing security and stability risks to the project and maintainers + when spot such repeated behaviours will close all such PRs and might block the contributor from further + contributions. Your personal reputation goes south with such behaviour, so if your goal is to increase + your value as a developer, avoid such practices. Review Comment: I feel this paragraph doesn’t blend well with the rest of the guidelines, but I think it’s important to keep. Would it make sense to restructure the Gen-AI contribution guidelines into two sections? * Mandatory Requirements: rules that contributors must follow (e.g., ASF guidelines, code review, tests, responsibility for code). * Recommended Cautions: advice and warnings for safe and responsible use (e.g., avoiding blind copy-paste, understanding potential risks). Just a suggestion :) -- 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]
