Skip to content

Add guidelines for AI usage, in PR and issue templates - #391

Open
Priyankasaggu11929 wants to merge 3 commits into
mainfrom
add-guidelines-for-ai-usage
Open

Add guidelines for AI usage, in PR and issue templates#391
Priyankasaggu11929 wants to merge 3 commits into
mainfrom
add-guidelines-for-ai-usage

Conversation

@Priyankasaggu11929

Copy link
Copy Markdown
Member

@kubernetes-prow kubernetes-prow Bot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 11, 2026
@netlify

netlify Bot commented Aug 11, 2026

Copy link
Copy Markdown

Deploy Preview for node-readiness-controller canceled.

Name Link
🔨 Latest commit 4302a00
🔍 Latest deploy log https://app.netlify.com/projects/node-readiness-controller/deploys/6a86a5ca2e27040008ace588

@kubernetes-prow kubernetes-prow Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 11, 2026
@ajaysundark

Copy link
Copy Markdown
Contributor

@Priyankasaggu11929 Thank you for sending this out. I'll go through this soon

@Priyankasaggu11929
Priyankasaggu11929 force-pushed the add-guidelines-for-ai-usage branch from ab29421 to 8d5e8ae Compare August 13, 2026 12:12
@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Priyankasaggu11929
Once this PR has been reviewed and has the lgtm label, please ask for approval from ajaysundark. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Priyankasaggu11929
Priyankasaggu11929 force-pushed the add-guidelines-for-ai-usage branch 2 times, most recently from a746602 to b070fb0 Compare August 13, 2026 12:23
@ajaysundark

ajaysundark commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

I cannot decide what's better, having these in the issue/PR templates or contributing.md? The latter feels like the right shape for these guidelines.

Maybe add the guidelines to contributing.md and refer it here with a checkbox?

It'd also be a good idea to update the AGENTS.md with this context, so if someone is using AI tools, this could help establish the responsibility split as well!?

@Priyankasaggu11929

Priyankasaggu11929 commented Aug 14, 2026

Copy link
Copy Markdown
Member Author

I cannot decide what's better, having these in the issue/PR templates or contributing.md? The latter feels like the right shape for these guidelines.

Maybe add the guidelines to contributing.md and refer it here with a checkbox?

It'd also be a good idea to update the AGENTS.md with this context, so if someone is using AI tools, this could help establish the responsibility split as well!?

+1. Adding it to CONTRIBUTING.md and AGENTS.md makes sense. (k/k also adopted a snippet yesterday).

But I still think - atleast in 2 places where our most AI spam contributions are coming from (PR template and bug issue template), it makes sense to keep it as a upfront text.
Because, chances are people wont open the contributing doc unless called out.
@ajaysundark, wdyt about ^?

I will send an update later during the day.

@ajaysundark

Copy link
Copy Markdown
Contributor

I cannot decide what's better, having these in the issue/PR templates or contributing.md? The latter feels like the right shape for these guidelines.
Maybe add the guidelines to contributing.md and refer it here with a checkbox?
It'd also be a good idea to update the AGENTS.md with this context, so if someone is using AI tools, this could help establish the responsibility split as well!?

+1. Adding it to CONTRIBUTING.md and AGENTS.md makes sense. (k/k also adopted a snippet yesterday).

But I still think - atleast in 2 places where our most AI spam contributions are coming from (PR template and bug issue template), it makes sense to keep it as a upfront text. Because, chances are people wont open the contributing doc unless called out. @ajaysundark, wdyt about ^?

I will send an update later during the day.

Thanks @Priyankasaggu11929! My only concerns were that if we overly put text into the templates, people wont read it, or start asking AI to do it. So felt keeping brief references may be better (That's with hoping people would follow redirections!).

May be we could try it and see how it goes.

/lgtm

@kubernetes-prow kubernetes-prow Bot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 18, 2026
@Priyankasaggu11929

Copy link
Copy Markdown
Member Author

+1. Adding it to CONTRIBUTING.md and AGENTS.md makes sense. (k/k also adopted a snippet yesterday).

sorry, I forgot to add this ^. will address it.

Thanks @Priyankasaggu11929! My only concerns were that if we overly put text into the templates, people wont read it, or start asking AI to do it. So felt keeping brief references may be better (That's with hoping people would follow redirections!).

In that case, I'll just keep the PR template text, and move all issues template ones to a link redirecting to CONTRIBUTING.md

will send updates!

@Priyankasaggu11929
Priyankasaggu11929 force-pushed the add-guidelines-for-ai-usage branch from b070fb0 to 4302a00 Compare August 20, 2026 06:59
@kubernetes-prow

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@kubernetes-prow kubernetes-prow Bot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants