Add AI Policy - #2046
Add AI Policy#2046reinecke wants to merge 9 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2046 +/- ##
=======================================
Coverage 83.48% 83.48%
=======================================
Files 182 182
Lines 13517 13517
Branches 1254 1254
=======================================
Hits 11284 11284
Misses 2060 2060
Partials 173 173
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
How about attribution just for the PR? Otherwise every commit will need DCO + LLM attribution, which seems like a lot. |
The DCO auto-enforcement system checks every commit, but |
+1
This seems like a reasonable adjustment to me. |
44fe449 to
6834b8b
Compare
Signed-off-by: Eric Reinecke <ereinecke@netflix.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
…t been merged yet Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
… have 1st party support. Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
Signed-off-by: Eric Reinecke <reinecke.eric@gmail.com>
74473d5 to
8638df4
Compare
apetrynet
left a comment
There was a problem hiding this comment.
One minor suggestion, but this looks good to me
| Even when using a coding assistant to write the code, you are strongly | ||
| encouraged to write your own PR description, in your own words, if for no | ||
| other reason than to force yourself to understand the code well enough to | ||
| describe it to others. |
There was a problem hiding this comment.
Can we highlight this with bold or itallic?
| Even when using a coding assistant to write the code, you are strongly | |
| encouraged to write your own PR description, in your own words, if for no | |
| other reason than to force yourself to understand the code well enough to | |
| describe it to others. | |
| **Even when using a coding assistant to write the code, you are strongly | |
| encouraged to write your own PR description, in your own words, if for no | |
| other reason than to force yourself to understand the code well enough to | |
| describe it to others.** |
Summarize your change.
This PR adds an AI coding policy to provide clarity for contributors using AI coding assistants.
This policy is forked from the thoughtful policy provided by OpenImageIO.