Repository navigation
ci: Disallow AI attribution in commits and PR descriptions - #130
Merged
Merged
Conversation
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
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.
Using AI tools to contribute is still allowed, this PR does not change that. It stops AI attribution from ending up in the git history, which happens when pull requests are squash merged.
This adds a workflow that runs bluefireteam/no-ai-attribution-action on every pull request, also when the description is edited. It checks the description, the commit messages and the commit authors, and flags co-author trailers with the addresses that AI tools use, footers such as "Generated with" followed by a tool name, and
claude.ai/code/sessionlinks. Prose that only mentions a tool is allowed, and existing history on the default branch is not checked.