Repository navigation
docs(commit-signing): document how pull requests merge under the rule - #7
Open
estefano-vechietti-azion wants to merge 1 commit into
Open
estefano-vechietti-azion wants to merge 1 commit into
estefano-vechietti-azion wants to merge 1 commit into
Conversation
Tested on a scratch repository with a ruleset that only requires signatures: squash merges pass with unsigned commits (GitHub signs the result), merge commits are refused unless every commit is signed, and rebase merges are always refused because GitHub cannot sign rebased commits. Existing history is not checked again. gh pr merge --squash refuses on its own pre-check while the API merge is allowed. Co-Authored-By: Claude Opus 5.5 <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
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.
What changes
The guide gains a Merging pull requests section and three rows in Common problems, based on a test on a scratch repository whose ruleset only has
required_signaturesand no bypass:mainverified: true,reason: valid, committed by GitHubCommits must have verified signaturesRebase merges cannot be automatically signed by GitHubmainGH013 ... Commits must have verified signaturesIt also notes that
gh pr merge --squashrefuses on its own pre-check (mergeStateStatus: BLOCKED), while the same merge through the API succeeds.Not tested: a merge commit where every commit is signed, which is expected to pass.
🤖 Generated with Claude Code