docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst by JohnVillalovos · Pull Request #3406 · python-gitlab/python-gitlab · GitHub

Require AI generated contributions to indicate so in commit messages.

Pull request overview

This PR updates the contributor guidelines to require attribution in commit messages when an AI coding assistant meaningfully contributed to a commit, by adding an Assisted-by: trailer convention.

Changes:

Add an “AI Attribution” section describing when/how to include an Assisted-by: commit trailer.
Provide an example commit message showing Closes: alongside Assisted-by:.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Require AI generated contributions to indicate so in commit messages. Also add the CONTRIBUTING.rst file to the generated documentation.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.78%. Comparing base (a4cbecb) to head (66007d3).
⚠️ Report is 33 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3406      +/-   ##
==========================================
+ Coverage   92.23%   95.78%   +3.54%     
==========================================
  Files         100      100              
  Lines        6172     6172              
==========================================
+ Hits         5693     5912     +219     
+ Misses        479      260     -219

Flag	Coverage Δ
api_func_v4	83.86% <ø> (?)
cli_func_v4	78.74% <ø> (ø)
unit	90.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 23 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@JohnVillalovos Nice, now you just need to add it to this commit as well ;-)

@JohnVillalovos Nice, now you just need to add it to this commit as well ;-)

If you look at all my failures along the way it kind of gives away that I didn't use AI this time 😄

But we do use this policy over at LibreBooking https://github.com/LibreBooking/librebooking and I also do use AI quite often to help. If I had been smarter I would have used AI but I was lazy and thought it can't be that hard. My knowledge of RST was not as good as I thought it was. I should have just started up Claude...

I'm not a big fan of this. All code is now written by LLMs and humans are just nudging it in the right direction. I would have agreed with adding this in 2025, but our work fundamentally changed in 2026 so I'm not sure this makes sense.

The model should not matter, but the quality of the code does.

Thanks @JohnVillalovos, I agree it'd be good to have something now that they've started, but would like something lightweight/generic to future-proof it. WDYT?

I think this will pretty quickly get outdated, as agents are now autonomous enough that they're essentially doing the whole implementation. Likewise with models and harnesses, they change every month now and can be extended with MCPs, skills, plugins and other tools that I think muddy the water further.

WDYT about asking for the initial prompt that created the contribution, instead? As discussed offline as well, I think what's becoming more important now is the author's initial intent for a change, as that way we can better reason about whether something is well-intentioned or just slop to fill a GitHub punch card.

Though in that case, it might make more sense to include it in the original PR description as it could pollute the commit log much more than a simple trailer. We could even include it in the PR template, and have agents pick it up automatically.

Thanks @nejch

@nejch I'm not sure. As I know in my work I don't often do an initial prompt and the result of that is what I submit. For me there is usually a lot of iterating. But it could be useful to get the plan of what they were trying to do.

I still like would to have people declare if they used an AI or not. And adding the footer seems like an initial minimal ask of people.

One of my favorite quotes is, "Don't let perfect be the enemy of good". So my thought is get a start and then keep iterating on it as time goes by and we learn more and more.

Copilot AI review requested due to automatic review settings June 10, 2026 04:20

Copilot started reviewing on behalf of JohnVillalovos June 10, 2026 04:21 View session

Copilot AI reviewed Jun 10, 2026

View reviewed changes

Comment thread CONTRIBUTING.rst Outdated

Comment thread CONTRIBUTING.rst Outdated

Comment thread CONTRIBUTING.rst

JohnVillalovos force-pushed the jlvillal/ai_attribution branch 2 times, most recently from bf0e5f0 to f2ad992 Compare June 10, 2026 04:25

JohnVillalovos requested review from Copilot and nejch June 10, 2026 04:26

Copilot started reviewing on behalf of JohnVillalovos June 10, 2026 04:26 View session

Copilot AI reviewed Jun 10, 2026

View reviewed changes

JohnVillalovos force-pushed the jlvillal/ai_attribution branch 3 times, most recently from aa92932 to 8106ca0 Compare June 10, 2026 04:41

JohnVillalovos requested a review from Copilot June 10, 2026 04:41

Copilot started reviewing on behalf of JohnVillalovos June 10, 2026 04:41 View session

Copilot AI reviewed Jun 10, 2026

View reviewed changes

Comment thread docs/index.rst

Comment thread CONTRIBUTING.rst Outdated

JohnVillalovos force-pushed the jlvillal/ai_attribution branch 4 times, most recently from a8ae5d6 to 40ddaba Compare June 10, 2026 04:56

docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst

66007d3

Require AI generated contributions to indicate so in commit messages. Also add the CONTRIBUTING.rst file to the generated documentation.

JohnVillalovos force-pushed the jlvillal/ai_attribution branch from 40ddaba to 66007d3 Compare June 10, 2026 04:59

bufferoverflow approved these changes Jun 10, 2026

View reviewed changes

nejch reviewed Jun 11, 2026

View reviewed changes

+              When an AI coding assistant contributed meaningfully to a commit (writing or
+              significantly modifying code, suggesting the fix, generating tests, etc.),
+              add an ``Assisted-by`` trailer to the commit footer::

docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst by JohnVillalovos · Pull Request #3406 · python-gitlab/python-gitlab · GitHub

Repository navigation

docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst - #3406

docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst#3406JohnVillalovos wants to merge 1 commit intomainpython-gitlab/python-gitlab:mainfrom jlvillal/ai_attributionpython-gitlab/python-gitlab:jlvillal/ai_attributionCopy head branch name to clipboard

Conversation

JohnVillalovos commented Jun 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

codecov Bot commented Jun 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

bufferoverflow left a comment

Choose a reason for hiding this comment

Uh oh!

JohnVillalovos commented Jun 10, 2026

Uh oh!

JohnVillalovos commented Jun 10, 2026

Uh oh!

max-wittig commented Jun 10, 2026

Uh oh!

nejch left a comment

Choose a reason for hiding this comment

Uh oh!

nejch Jun 11, 2026

Choose a reason for hiding this comment

Uh oh!

JohnVillalovos Jun 14, 2026

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

docs(ai_policy): add an AI attribution policy to CONTRIBUTING.rst#3406
JohnVillalovos wants to merge 1 commit into
mainfrom
jlvillal/ai_attribution

codecov Bot commented Jun 10, 2026 •
edited
Loading