This is an automated email from the ASF dual-hosted git repository. twice pushed a commit to branch twice/generative-tools in repository https://gitbox.apache.org/repos/asf/kvrocks-website.git
commit 7dacf9c2b509beec4df7c20bfa48fd6a86b87b3e Author: Twice <[email protected]> AuthorDate: Thu Dec 25 16:16:17 2025 +0800 Update contributing guidelines with ASF link --- community/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/contributing.md b/community/contributing.md index 87cfb931..0968303f 100644 --- a/community/contributing.md +++ b/community/contributing.md @@ -54,7 +54,7 @@ AI tools are welcome as helpers, not authors. Keep these practices in mind: - Keep humans in the loop: discuss non-trivial ideas early via Issues, Discussions, or Mailing Lists, especially when you are unsure about design or impact. - Use AI for acceleration, then verify: treat AI output as a draft for code, tests, or docs; run linters/tests and review the logic yourself. - Be transparent in PRs: note briefly if AI was used and for what (e.g., initial draft, test scaffolding), and call out any parts where you want extra review. -- Respect ASF policy: ensure generated content does not introduce incompatible licenses or undisclosed third-party code; review the ASF Generative Tooling Guidance and licensing rules when in doubt. +- Respect ASF policy: ensure generated content does not introduce incompatible licenses or undisclosed third-party code; review the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) and licensing rules when in doubt. - Prefer focused patches over large dumps; if you cannot confidently explain an AI-produced change, open a well-described issue instead. ## Submit patches to document or project website
