Some open source projects are setting guidelines on ai usage https://github.com/kyverno/community/blob/main/AI_USAGE_POLICY.md

Yes, makes sense and not a bad idea. Has GitHub adopted this as a actual community file standard?

Has GitHub adopted this as a actual community file standard?

I don’t believe so. Only a matter of time.

I’ll be honest today we haven’t had much reports of abuse of AI. As a fellow contributor, have you seen problems in our community?

I have not but it’s such a powerful tool. It makes years of programming feel like we’ve been using spears and now we have guns. People are still getting used to the new change and once everyone is used to it, I think more and more open source communities will get a deluge of AI PRs so creating some policy would be a good start. Especially right now, I’m using LLMs to contribute to cloudposse and I don’t know what is expected from the org i.e. rules of engagement. So I’m making it up as I go, but luckily since I have experience as a contributor, I can steer the machine in the “right” direction, but maybe others may not be able to

Awesome 🙂

also, would be very interested to hone some copilot review instructions

One thing that would be nice is to tune mergify. When I run copilot, it will create a PR without any files changed. Mergify will detect the PR and automatically close the PR because there are no files changed which will then kill the copilot task. I then have to manually find the PR, go to the PR branch, add a dummy file that I can later delete, go back to the PR, reopen it, then finally go back to copilot and ask it to try again.

We resolved that end of last week

mergify auto closed one of my PRs today 😞

which org?

cloudposse-terraform-components

hrmmm ok, @Ben Smith (Cloud Posse) maybe the second fix needs to be rolled out there too

on it

Thank you!

Thanks for speaking up!