Stack rebase needs GPG signing support to be truly usable #338
Closed
aleksei-averchenko-wise
started this conversation in
Feedback
Replies: 2 comments
|
This behavior is noted in the documentation, so I assume it is intentional at the moment. However, I think commit signing in server-side rebasing is a must. I've been using stacked PRs with other tools such as Graphite for a while, and server-side rebasing was able to properly sign the commits by using a key configured in their settings. I'm missing that in GitHub's native stacks. |
0 replies
|
We have released an update that will now create signed commits as part of stack rebases. The rebased commits will have a GitHub bot user as a committer while maintaining the original author. This affects both the "Rebase Stack" button in the merge box as well as the automated rebase that occurs after a partial merge of a stack. Screen.Recording.2026-08-13.at.6.43.21.PM.mov |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Right now, GitHub's rebase button results in the rewritten commits having no GPG signatures, which makes it inconvenient to use. Please consider adding commit signing support via GitHub
All reactions