From f191c3c51a7646fb299b6cbbf5dc7ce5c7412114 Mon Sep 17 00:00:00 2001 From: GeertJohan Date: Thu, 30 Jul 2026 14:34:00 +0200 Subject: [PATCH] In the contribution guidelines, change the Generated-By label to Assisted-By --- community/02-contribution-guideline.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/community/02-contribution-guideline.md b/community/02-contribution-guideline.md index bac10607..07df873a 100644 --- a/community/02-contribution-guideline.md +++ b/community/02-contribution-guideline.md @@ -30,8 +30,8 @@ The metal-stack project generally accepts contributions that make use of generat - **Compliance**: The contributor is responsible for the disclosed sources and ensures that it complies with the Open Source definition, copyright and license regulations of the metal-stack project. - **Communication**: Comments, motivations and issues are genuinely written by humans. - **Transparency**: Commits where substantial parts were generated by AI must include: - - Commit labels for the review process, like: `Generated-By: [tool name] `. - - The names of the tools that were used with AI should be included in the pull request description. For this, there is a dedicated section in the pull request template. As we usually squash commits when we merge, the `Generated-By` labels should be kept in the final commit description. + - Commit labels for the review process, like: `Assisted-By: [tool name] `. + - The names of the tools that were used with AI should be included in the pull request description. For this, there is a dedicated section in the pull request template. As we usually squash commits when we merge, the `Assisted-By` labels should be kept in the final commit description. - **Code Understanding**: We expect full understanding of the contributed code. The code must have been executed and tested in some way by the contributor. The contribution guideline's overall style and design choices must be followed. - **Quality over Quantity**: It is very easy to generate a lot of code with the help of AI in a very short amount of time. By contrast, reviewing large pull requests takes exponentially longer as they grow in size. Therefore, contributions are expected to be minimal. Large changes must be discussed in issues as usual and discussed in the community.