fix: switch to squash+merge for signed commit compatibility - #7
Merged
temper-pulseengine[bot] merged 1 commit intoMar 1, 2026
Merged
Conversation
GitHub rebase merges cannot be signed (known limitation since 2022, no fix as of 2026). Switch to squash+merge commit to ensure all commits on protected branches are signed by GitHub web-flow key. - Enable allow_merge_commit and allow_squash_merge - Disable allow_rebase_merge - Disable required_linear_history (merge commits are non-linear)
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.
GitHub rebase cannot be signed. Switch to squash+merge commit.