Repository navigation
ci: reject commit messages with co-author or tool attribution lines - #16
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
1 participant
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.
Rebase merges keep each commit's message as written, so a
Co-Authored-By:trailer or a "Generated with Claude…" line in a PR commit would land on main.A new step in the
checkjob scans every non-merge commit in the PR and fails when a message has such a line. The match is case-insensitive;Co-Authored-By:counts only at the start of a line, so a message that mentions it inline passes.Tried in a throwaway repo: of four commits, the two with a trailer or attribution line failed, the clean one and the inline mention passed. The README's Develop section lists the new check.