diff options
| author |   memdmp <memdmpestrogenzone> | 2025-01-28 21:06:58 +0100 |
|---|---|---|
| committer | memdmp <memdmpestrogenzone> | 2025-01-28 21:07:08 +0100 |
| commit | 927e7e66d065d38bb8a891171945e6ecdb6a6abe (patch) | |
| tree | cf4e52caedff3a1eba2578819d31b57cf08aa8f6 /CODE-OF-CONDUCT.md | |
| parent | a1afe603a056e25966ea072b031c7b837c900f6f (diff) | |
| download | zuwu-927e7e66d065d38bb8a891171945e6ecdb6a6abe.tar.gz zuwu-927e7e66d065d38bb8a891171945e6ecdb6a6abe.tar.bz2 zuwu-927e7e66d065d38bb8a891171945e6ecdb6a6abe.tar.lz zuwu-927e7e66d065d38bb8a891171945e6ecdb6a6abe.zip | |
fix(code-of-conduct): i was wrong
Diffstat (limited to 'CODE-OF-CONDUCT.md')
| -rw-r--r-- | CODE-OF-CONDUCT.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CODE-OF-CONDUCT.md b/CODE-OF-CONDUCT.md index d40c14e..f6ad993 100644 --- a/CODE-OF-CONDUCT.md +++ b/CODE-OF-CONDUCT.md @@ -98,6 +98,6 @@ You are receiving this because you are subscribed to this thread. Message ID: <dmpmem/zuwu/pull/1@github.com> ``` -This PR, made by an unknown (due to github marking them as spam :3) account, is obviously AI generated in it's entirety, does not address anything serious, includes a reference to the existing code without describing a change, does idiotic things like "INSTALL_DIR" being prioritized over a perfectly fine "TARGET". This both used my code as an input to an LLM (and likely added it to the training data being used by whatever company runs said LLM), and gave garbage out. +This PR, ~~made by an unknown (due to github marking them as spam :3) account~~ (nvm, github was just randomly 404ing the link works now?), is obviously AI generated in it's entirety, does not address anything serious, includes a reference to the existing code without describing a change, does idiotic things like "INSTALL_DIR" being prioritized over a perfectly fine "TARGET". This both used my code as an input to an LLM (and likely added it to the training data being used by whatever company runs said LLM), and gave garbage out. The only usable change was the `set -euo pipefail` being used over `set -e`. This is theoretically [bad practice](https://bbs.archlinux.org/viewtopic.php?id=240984), however is a theoretically ok addition as I had forgotten to run shellcheck (which outputted nothing useful) and shellharden on the scripts in this repo to this point, and it's more or less "standard industry practice" in some capacity. |