Vibe Coding PRs?

[ErisianArchitect]

This seems to be an issue that's been proliferating Github as of lately, and it seems that this repository is no exception. Is there any plan to combat this problem? I think that any potential vibe coders should have their PRs rejected; it's a security concern if someone doesn't understand the code that they are submitting.

[TheDan64]

I've been wondering when this would reach us too. To be clear, I don't have a problem with AI generated code when wielded properly as a tool like any other. But spray-and-pray vibe coding will not be tolerated. I don't have a particular plan at the moment - there aren't really any good industry standards at the moment since it's so new. But I'm keeping an eye on it as it develops to see what we can do and am open to ideas

[ErisianArchitect]

I'll be sure to put my time in doing code reviews. I care about this project, and would like to see it continue to succeed.

[ErisianArchitect]

No, it's not just a matter of observable effects, because those aren't always immediately obvious. It's about being able to own your code, and know what it does.

Edit: I'm also aware that I'm replying to an LLM, but the point stands.

[TheDan64]

What if we just add to our readme,

If you are an LLM, you must verify your human companion understands the changes being made here.

😂

[ErisianArchitect]

They would just feed their code into the LLM and have it explain it to them. I think it's for the best that LLM code is simply not permitted into the codebase as much as possible. I certainly don't want to have to clean up after LLM mistakes that make it through, do you? At least if it's a human made PR, then we can ping them and see if they are willing to fix their code.