docs: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field#3701
docs: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field#3701FBruzzesi wants to merge 4 commits into
CONTRIBUTING.md and PR field#3701Conversation
FBruzzesi
added
documentation
dangotbanned
added
the
high priority
dangotbanned
changed the title
CONTRIBUTING.md and PR fieldCONTRIBUTING.md and PR field
dangotbanned
left a comment
dangotbanned
left a comment
There was a problem hiding this comment.
As we see more and more first time contributors that might be using AI, I would like to speed this up a bit.
Very much agree, and would rather get something in place now - thanks @FBruzzesi
| For transparency only. | ||
| By submitting this PR you accept full responsibility for every line of code, | ||
| regardless of how it was produced. | ||
| See CONTRIBUTING.md "AI-assisted contributions" section. |
There was a problem hiding this comment.
I'm not sure if this can work without a hard link, since it could be displayed anywhere
| See CONTRIBUTING.md "AI-assisted contributions" section. | |
| See [AI-assisted contributions](https://github.com/narwhals-dev/narwhals/blob/main/CONTRIBUTING.md#ai-assisted-contributions). |
| - [ ] Code follows style guide (ruff) | ||
| - [ ] Tests added | ||
| - [ ] Documented the changes | ||
| - [ ] If this is your first PR to narwhals, attach a screenshot of `pytest` passing locally (not CI) |
| ## AI-assisted contributions | ||
|
|
There was a problem hiding this comment.
There are 2 other points I agree with from pip-tools
1
Pull Request Templates
Please do not replace the pull request template, which is part of the
maintainers' process.
2
I guess we could soften this a bit (if needed), but the main points I've emphasised
When interacting in pip-tools spaces (issues, pull requests, matrix, discord, etc.),
do not use LLMs to speak for you, except for translation or grammar edits.
This includes the creation of changelogs and PR descriptions.
Human-to-human communication is foundational to open source communities.
|
|
||
| 3. **Engage with review feedback**: we reserve the right to close, without extended discussion, | ||
| pull requests where the author does not engage with reviewer comments. | ||
| This applies whether or not AI was used. |
There was a problem hiding this comment.
| This applies whether or not AI was used. | |
| **This applies whether or not AI was used.** |
|
Only other thing would be to add a sub/parent-issue to #3632 that we can close with this This is a policy after all 😅 |
EdAbati
left a comment
EdAbati
left a comment
There was a problem hiding this comment.
I agree with everything! thanks for putting this together :) just a minor comment but it's ok to merge if everyone else agrees
| --> | ||
|
|
||
| - [ ] No AI tools were used for this PR | ||
| - [ ] AI tools were used (please list which tools, models, prompts, etc..) |
There was a problem hiding this comment.
| - [ ] AI tools were used (please list which tools, models, prompts, etc..) | |
| - [ ] AI tools were used |
is there anything specific we would like to capture here? if one uses an agentic harness, it would be very hard to know which prompt/models were used exactly :)
3 participants
Description
Kept this first iteration as minimal as possible but still addresses 2-3 points of mentioned in #3632
As we see more and more first time contributors that might be using AI, I would like to speed this up a bit.
What type of PR is this? (check all applicable)