Repository navigation
Refuse AI-attribution lines in commit messages - #82
Merged
Merged
Conversation
… pull request check The repository had no .githooks and no commit-message check. This adds tools/ai-trace-commit-check.sh with its pattern list (a self-contained copy, since a public repository cannot depend on a private one), a commit-msg hook that runs it (git config core.hooksPath .githooks), and a ci job that runs it over the commits of a pull request on a hosted runner. The job also runs the checker's self-test, which goes red when the patterns are removed.
Contributor
Author
|
Tracked under umbrella #1609 (going public: AI-attribution refusal). Old parent: no parent. A pull request cannot be a sub-issue, so this comment is the link. |
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.
Part of FreeMixer/openmixer-ops#38.
Adds, as a self-contained copy (a public repository must not depend on a private one):
git config core.hooksPath .githooks.ai-tracejob in ci.yml, on pull requests, on a hosted runner with full history: the self-test, then origin/..HEAD. Commits already on the base are not read.Checked locally: the self-test is green and goes red with the co-author, email and session patterns removed; a commit carrying a trailer makes the range scan exit 1; the hook refuses a message with an attribution line and passes a plain one; the repository's own source and licence checks still pass.