Skip to content

docs: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field#3701

Open
FBruzzesi wants to merge 9 commits into
mainfrom
chore/add-ai-policy
Open

docs: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field#3701
FBruzzesi wants to merge 9 commits into
mainfrom
chore/add-ai-policy

Conversation

@FBruzzesi

@FBruzzesi FBruzzesi commented Jun 21, 2026

Copy link
Copy Markdown
Member

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)

  • 💾 Refactor
  • ✨ Feature
  • 🐛 Bug Fix
  • 🔧 Optimization
  • 📝 Documentation
  • ✅ Test
  • 🐳 Other

@FBruzzesi FBruzzesi added documentation Improvements or additions to documentation needs discussion labels Jun 21, 2026
@FBruzzesi FBruzzesi marked this pull request as ready for review June 21, 2026 16:37
@dangotbanned dangotbanned added the high priority Your PR will be reviewed very quickly if you address this label Jun 22, 2026
@dangotbanned dangotbanned changed the title RFC, chore: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field docs: Add 'AI-assisted contributions' section in CONTRIBUTING.md and PR field Jun 22, 2026

@dangotbanned dangotbanned left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

spinny hands narwhal

Comment thread .github/pull_request_template.md Outdated
Comment thread .github/pull_request_template.md Outdated
- [ ] 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)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😍

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we clarify what constructors should be considered here (e.g. whatever is default at the time of opening the PR)? I wouldn't expect first time contributors to set up spark and run the spark constructor tests.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added suggested command in 49a22a8

Comment thread CONTRIBUTING.md
Comment on lines +400 to +401
## AI-assisted contributions

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are 2 other points I agree with from pip-tools

1

https://github.com/jazzband/pip-tools/blob/24f4230b0fc9c964100b73f81599b0cc4eaff79a/CONTRIBUTING.md?plain=1#L67-L70

Pull Request Templates

Please do not replace the pull request template, which is part of the
maintainers' process.

2

https://github.com/jazzband/pip-tools/blob/24f4230b0fc9c964100b73f81599b0cc4eaff79a/CONTRIBUTING.md?plain=1#L42-L45

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's very valid! Thanks for pointing it out

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the second. Not sure where to place the first one

Comment thread CONTRIBUTING.md Outdated
@dangotbanned

dangotbanned commented Jun 22, 2026

Copy link
Copy Markdown
Member

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 😅

@FBruzzesi FBruzzesi mentioned this pull request Jun 23, 2026
6 tasks

@EdAbati EdAbati left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with everything! thanks for putting this together :) just a minor comment but it's ok to merge if everyone else agrees

Comment thread .github/pull_request_template.md Outdated

@camriddell camriddell left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this up! No new points from me, once you wrap up any lingering feedback from @dangotbanned and @EdAbati this should be in a good spot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation high priority Your PR will be reviewed very quickly if you address this

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants