Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorMartin Hořeňovský2026-06-14 20:25:57 +0200
committerMartin Hořeňovský2026-06-14 20:25:57 +0200
commit675f9eaeb191c51b9d2ffb2bb198009533895051 (patch)
treefd0880cb5298d76e5429c5a495b5542cc9fdfc2e /docs
parentbcfb10e498df3e2ed8f814b3e4b689b9a85608ab (diff)
downloadcatch3-675f9eaeb191c51b9d2ffb2bb198009533895051.tar.gz
Add LLM policy to contributing.md
Diffstat (limited to 'docs')
-rw-r--r--docs/contributing.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/contributing.md b/docs/contributing.md
index d21323d9..ff6e545b 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -7,6 +7,8 @@
[Writing documentation](#writing-documentation)<br>
[Writing code](#writing-code)<br>
[CoC](#coc)<br>
+[Using LLMs when contributing](#using-llms-when-contributing)<br>
+
So you want to contribute something to Catch2? That's great! Whether it's
a bug fix, a new feature, support for additional compilers - or just
@@ -332,6 +334,19 @@ When adding new `CATCH_CONFIG` option, there are multiple places to edit:
This project has a [CoC](../CODE_OF_CONDUCT.md). Please adhere to it
while contributing to Catch2.
+
+## Using LLMs when contributing
+
+I do not care whether you used LLM for your contribution. What I care
+about is the quality of the contribution, not whether you made it through
+prompting LLM, letting GAs run wild, dictated it into the computer, wrote
+it using your nose or used butterflies to flip the correct bits.
+
+The flipside of this is that I am also not going to iterate your LLM for
+you. If a PR looks LLM generated and does not pass the muster to be merged
+as-is, I am going to close it.
+
+
-----------
_This documentation will always be in-progress as new information comes