Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: add generative ai contribution guidelines#19427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
Emyrk merged 9 commits intomainfromstevenmasley/ai_contrib
Aug 20, 2025

Conversation

Emyrk
Copy link
Member

@EmyrkEmyrk commentedAug 19, 2025
edited
Loading

Initial language that gives us something to point to if needed.

I did not include language around the size of a PR. I think we should have normal contribution guidelines about very large PRs, include tests, etc, etc.

Copy link
Contributor

@dannykoppingdannykopping left a comment

Choose a reason for hiding this comment

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

Great start@Emyrk, thanks! A few minor points, appreciate your putting this together


##Disclosure

Contributors must**disclose AI involvement** in the pull request description whenever these guidelines apply.
Copy link
Contributor

Choose a reason for hiding this comment

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

We should pair this with aPULL_REQUEST_TEMPLATE.md file to elicit this disclosure and link to this page. I'm not sure many folks will find this doc organically. I don't think we can customize the links under the PR description box, can we?

Image

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I'm not 100% sure. I know we can make issue templates, never tried for PRs

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

It'd be nice to have a standard way to represent AI contributors. We could either have a separate AI PR template or put the AI splash in the template inside<!-- /--> so it can be surfaced with relative ease. In the past we had a PR template and it was a bit of an inconvenience IIRC, hopefully that has improved.

Copy link
Contributor

Choose a reason for hiding this comment

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

@Emyrk can we please include this? Right now folks won't know to look at your new doc; let's increase discoverability.

Emyrkand others added2 commitsAugust 19, 2025 15:10
Copy link
Member

@johnstcnjohnstcn left a comment

Choose a reason for hiding this comment

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

Thanks for working on this@Emyrk !

@@ -0,0 +1,32 @@
#Guidelines for Using Generative AI in Contributions

This document defines rules for contributions where an AI system is the primary author of the code (i.e., most of the pull request was generated by AI).
Copy link
Member

Choose a reason for hiding this comment

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

most of the pull request was generated by AI)

This decision is very much "vibes based" from the reviewer's perspective. As such, I anticipate that this may be the source of a number of arguments. Unfortunately, I don't have any suggestion for a better delineation.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I do agree, but I kept it subjective because I know we all use AI day to day in our coding. I did not want to encompass our usual PRs.

I do not like the idea of saying like "50% of lines" or something.

Copy link
Member

@mafredrimafredri left a comment

Choose a reason for hiding this comment

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

Short and clear, I think this is a good starting point 👍🏻. I feel this guide is mostly for humans, would it make sense to have one targeting AI's as well? Or alternatively, having a hidden section act as clear instructions for the AI. Either way, that can come later.

Emyrk reacted with thumbs up emoji

##Disclosure

Contributors must**disclose AI involvement** in the pull request description whenever these guidelines apply.
Copy link
Member

Choose a reason for hiding this comment

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

It'd be nice to have a standard way to represent AI contributors. We could either have a separate AI PR template or put the AI splash in the template inside<!-- /--> so it can be surfaced with relative ease. In the past we had a PR template and it was a bit of an inconvenience IIRC, hopefully that has improved.

Emyrkand others added2 commitsAugust 20, 2025 07:42
Co-authored-by: Cian Johnston <cian@coder.com>
Co-authored-by: Cian Johnston <cian@coder.com>
@Emyrk
Copy link
MemberAuthor

Or alternatively, having a hidden section act as clear instructions for the AI. Either way, that can come later.

Very interesting idea

@EmyrkEmyrk merged commita19dfa9 intomainAug 20, 2025
26 checks passed
@EmyrkEmyrk deleted the stevenmasley/ai_contrib branchAugust 20, 2025 14:13
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsAug 20, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@dannykoppingdannykoppingdannykopping approved these changes

@mafredrimafredrimafredri approved these changes

@johnstcnjohnstcnjohnstcn approved these changes

@spikecurtisspikecurtisAwaiting requested review from spikecurtis

Assignees

@EmyrkEmyrk

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@Emyrk@mafredri@dannykopping@johnstcn

[8]ページ先頭

©2009-2025 Movatter.jp