Policy on accepting PRs that include LLM generated code?

[astatide]

Hello!

I've just been checking out Helix recently, and I quite enjoy what I've seen so far! It's fast, intuitive, ships a lot of nice defaults, and works well with what I've used it for thus far!

I apologize if this has been asked before (I was unable to find anything discussing it previously); I was curious if the project had any specific guidelines on whether it would be utilizing LLMs as part of the development process, or whether the project would accept PRs that had involved Claude, CoPilot, ChatGPT, etc, in some fashion?

(My own personal interest in asking is that I am actively disinterested in using software stacks that incorporate the usage of LLMs anymore than I am forced to).

Thank you!

[the-mikedavis]

We don't currently have a policy but there have been more and more PRs and other interaction (comments, issues, etc.) that seem LLM-generated so I think it's getting time to adopt one. @archseer and I were discussing this the other day and we like Ghostty's policy: https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md.

I think LLMs are good at certain tasks like building timelines or helping you dig into unfamiliar code. But it's very easy to abuse them to waste peoples' time. And I find the output quality pretty questionable most of the time.

[codecat]

I am a big fan of Helix, and an opponent of anything related to generative AI for many different reasons. Even when people claim they "use it responsibly", I don't have much trust in it, because people's trust in generative AI is often misplaced. As a casual user, I would ask for you to consider having an AI policy to reject AI contributions.