Add AI usage policy and disclosure requirements to contribution guidelines#13520
Merged
Add AI usage policy and disclosure requirements to contribution guidelines#13520
Conversation
Add guidance for contributors using AI tools in their submissions, including: - Disclosure requirements for meaningful AI assistance - Examples of good disclosure (ChatGPT, Claude, Gemini) - Expectations for code understanding and quality - Clear communication about maintainer time and review process Inspired by Ghostty's approach to AI disclosure in contributions: https://github.com/ghostty-org/ghostty/blob/main/CONTRIBUTING.md Collaborated with Claude to draft this policy, comparing approaches and refining the language to match Oh My Zsh's community voice. Co-Authored-By: Claude <noreply@anthropic.com>
Add checkbox to encourage contributors to disclose AI tool usage (ChatGPT, Claude, Gemini, etc.) in their pull requests, complementing the new AI usage policy in CONTRIBUTING.md. Co-Authored-By: Claude <noreply@anthropic.com>
Member
Author
|
For anyone who wants a bit more context, I wrote a blog post to capture my current thinking on the topic. Like all things, my thinking could change on this in the future. 🙃 https://robbyonrails.com/articles/2026/01/20/humans-in-the-loop/ |
lesterchan
added a commit
to lesterchan/oh-my-zsh
that referenced
this pull request
Jan 26, 2026
* upstream/master: (32 commits) chore(deps): bump github/codeql-action from 4.31.10 to 4.31.11 (ohmyzsh#13539) chore(deps): bump actions/checkout from 6.0.1 to 6.0.2 (ohmyzsh#13541) chore(deps): bump actions/setup-python from 6.1.0 to 6.2.0 (ohmyzsh#13540) feat(gitignore): use cdn as endpoint (ohmyzsh#13497) feat(command-not-found): support void linux (ohmyzsh#13531) chore: add AI guidelines (ohmyzsh#13520) chore(deps): bump github/codeql-action from 4.31.9 to 4.31.10 (ohmyzsh#13524) feat(hcloud): add plugin for Hetzner Cloud CLI (ohmyzsh#13473) feat(brew): add aliases for reinstall and HEAD install (ohmyzsh#13446) chore: update LICENSE (ohmyzsh#13509) feat(jj): add alias for `jj abandon` (ohmyzsh#13510) fix(1password)!: remove v1 support (ohmyzsh#13507) fix(mise)!: remove unneeded hook-env call (ohmyzsh#13491) chore(deps): bump urllib3 in /.github/workflows/dependencies (ohmyzsh#13506) chore(kube-ps1): update to 0b0e6daf (ohmyzsh#13503) ci(deps): add GH_TOKEN to GitHub API requests (ohmyzsh#13502) ci(deps): add kube-ps1 to dependencies (ohmyzsh#13283) chore(deps): bump certifi in /.github/workflows/dependencies (ohmyzsh#13499) Revert "fix(kubectl)!: change alias from `kl` to `klog` (ohmyzsh#13204)" feat(tmux): add 'to' alias for session attachment (ohmyzsh#13479) ...
jhannah
pushed a commit
to jhannah/oh-my-zsh
that referenced
this pull request
Apr 26, 2026
Co-authored-by: Claude <noreply@anthropic.com>
adam-mccoy
pushed a commit
to adam-mccoy/ohmyzsh
that referenced
this pull request
Apr 30, 2026
Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This policy emerges from recent maintainer team discussions about the uptick in AI-generated contributions we've been observing. We wanted to take a thoughtful approach to how we consider these contributions moving forward.
While we each have our own perspectives about AI's impact on our industry, as a project we're focused on not creating unnecessary barriers for contributions while remaining mindful of our role as stewards of reliability, security, and quality control over what gets merged and shared with the community.
We recognize this decision might be controversial, but we're being pragmatic—we can't entirely predict or prevent AI contributions from coming our way. What we can do is remain committed to being great stewards and curators of the project by asking our community to be upfront and transparent about their process, ensuring we maintain end-to-end transparency.
Changes
CONTRIBUTING.md: Added "A note on AI-assisted contributions" section with:
PR Template: Added checkbox for AI tool disclosure to encourage transparency in pull requests
Rationale
As a small team of volunteers managing hundreds of pending PRs, we want to:
Standards checklist:
AI Disclosure
Collaborated with Claude to draft the AI usage policy language, comparing approaches from other projects (particularly Ghostty's CONTRIBUTING.md) and refining the tone to match Oh My Zsh's friendly, community-focused voice.
Other comments
Inspired by Ghostty's thoughtful approach to AI disclosure: https://github.com/ghostty-org/ghostty/blob/main/CONTRIBUTING.md
This policy aims to be practical rather than restrictive - we're not anti-AI, but want transparency to help us provide appropriate support and maintain project quality.