Skip to content

Require AI usage declaration in PR template - #5334

Merged
peterjc merged 4 commits into
biopython:masterfrom
peterjc:declare-ai
Nov 6, 2026
Merged

peterjc merged 4 commits into
biopython:masterfrom
peterjc:declare-ai

Conversation

@peterjc

@peterjc peterjc commented Sep 29, 2026

Copy link
Copy Markdown
Member
  • I hereby agree to dual licence this and any previous contributions under both
    the Biopython License Agreement AND the BSD 3-Clause License.

  • I have read the CONTRIBUTING.rst file, have run pre-commit
    locally, and understand that continuous integration checks will be used to
    confirm the Biopython unit tests and style checks pass with these changes.

  • I have added my name to the alphabetical contributors listings in the files
    NEWS.rst and CONTRIB.rst as part of this pull request, am listed
    already, or do not wish to be listed. (This acknowledgement is optional.)

This is a partial step based on #5241 to at least ask up front that any AI usage is declared as part of the PR template. With our AI policy yet to be settled, should at least save us having to ask this by hand so often.

(Assuming this is merged, I'll rebase #5241 to incorporate this.)

Additionally this adds an AI agent self declaration instruction to the CONTRIBUTING file, based on https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md where browsing/searching their issues and PRs that seems to be working, and will aid with triage.

Based on https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md

This is done with RST commenting so as not to show up on the human facing
rendering of the RST on GitHub etc. Browsing the Godot repository issues
and PRs, this seems to be working for them.
…laration

Pending agreement on an AI policy, we do at least seem to agree that
any AI tool usage should be openly declared.
@peterjc
peterjc requested a review from mdehoon September 29, 2026 10:09
@codecov

codecov Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.46%. Comparing base (8b4d499) to head (c611cf6).
⚠️ Report is 48 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5334      +/-   ##
==========================================
+ Coverage   85.52%   86.46%   +0.93%     
==========================================
  Files         282      281       -1     
  Lines       59497    59561      +64     
==========================================
+ Hits        50887    51499     +612     
+ Misses       8610     8062     -548     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@peterjc

peterjc commented Sep 29, 2026

Copy link
Copy Markdown
Member Author

I tracked the GoDot change back to via the pull request adding it, and they credit the idea to https://glama.ai/blog/2026-03-19-open-source-has-a-bot-problem

@JoaoRodrigues

Copy link
Copy Markdown
Member

This looks good to me @peterjc !

@peterjc

peterjc commented Nov 3, 2026

Copy link
Copy Markdown
Member Author

Updated to reference both policies, flagging the commonality that either would want human written communicaitions. I've tried to keep this neutral as to what might eventually be agreed - but the motivation of this PR remains to keep new potential contributors aware, and save us maintainers from having to keep asking about AI usage.

Is this PR wording OK with you @idoerg?

@peterjc

peterjc commented Nov 4, 2026

Copy link
Copy Markdown
Member Author

@mdehoon would you be OK with merging this?

@etal

etal commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Looks good to me, with the quibble: linking to the AI/No-AI discussing threads may be mixing concerns for a human contributor. For an initial short step toward settling the policy, the second sentence could just be:

All communications must be written by a human (unless machine-translated to English, accepted if declared).

@peterjc

peterjc commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

Re-ordered as per Eric's suggestion.

@peterjc
peterjc merged commit ba47c4c into biopython:master Nov 6, 2026
44 checks passed
@peterjc
peterjc deleted the declare-ai branch November 6, 2026 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants