Skip to content

feat(but): add sign-on-push functionality to but CLI#13000

Draft
slarse wants to merge 2 commits intomasterfrom
GB-1121/sign-on-push-continued
Draft

feat(but): add sign-on-push functionality to but CLI#13000
slarse wants to merge 2 commits intomasterfrom
GB-1121/sign-on-push-continued

Conversation

@slarse
Copy link
Contributor

@slarse slarse commented Mar 23, 2026

Adds in sign-on-push functionality, along with a new Git config setting to enable it. This is all backwards compatible with gitbutler.signCommits and will be invisible to end users for the time being, one has manually set signMode=OnPush in the config to enable the new behavior.

The UX here is still a bit rough. The push command is overall a bit rough to work with and I think this needs some major refactor. Perhaps not in this PR but soon.

TODO

  • Improve UX
  • ...

This is part 1 of 1 in a stack made with GitButler:

@vercel
Copy link

vercel bot commented Mar 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
gitbutler-web Ignored Ignored Preview Mar 23, 2026 9:29pm

Request Review

@github-actions github-actions bot added rust Pull requests that update Rust code CLI The command-line program `but` labels Mar 23, 2026
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch from 2ebe52b to 1af2176 Compare March 23, 2026 20:34
@slarse slarse force-pushed the GB-1121/sign-on-push-continued branch from 10d98b8 to d384ab9 Compare March 23, 2026 20:34
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch from 1af2176 to 60ffe7c Compare March 23, 2026 20:43
@slarse slarse force-pushed the GB-1121/sign-on-push-continued branch from d384ab9 to 4118849 Compare March 23, 2026 20:43
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch from 60ffe7c to e3a1aaa Compare March 23, 2026 20:52
@slarse slarse force-pushed the GB-1121/sign-on-push-continued branch from 4118849 to 518c952 Compare March 23, 2026 20:52
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch from e3a1aaa to 58dc1c0 Compare March 23, 2026 20:58
@slarse slarse force-pushed the GB-1121/sign-on-push-continued branch from 518c952 to 3e09e7a Compare March 23, 2026 20:58
slarse added 2 commits March 23, 2026 22:29
This commit puts down the groundwork for enabling sign-on-push
functionality. Importantly, it contributes but-workspace abstractions
to list unsigned commits and forcibly sign commits, as well as the
underlying graph rebase engine work to actually accomplish the
signing.

Note that there is still full backwards compatibility with the current
sign-all-the-flippin-time functionality.
Adds in sign-on-push functionality, along with a new Git config setting
to enable it. This is all backwards compatible with
gitbutler.signCommits and will be invisible to end users for the time
being, one has manually set signMode=OnPush in the config to
enable the new behavior.
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch from 58dc1c0 to d905572 Compare March 23, 2026 21:29
@slarse slarse force-pushed the GB-1121/sign-on-push-continued branch from 3e09e7a to 2aaaf84 Compare March 23, 2026 21:29
@slarse slarse changed the base branch from GB-1121/sign-on-push-groundwork to master March 24, 2026 08:45
@slarse slarse changed the base branch from master to GB-1121/sign-on-push-groundwork March 24, 2026 08:45
@slarse slarse force-pushed the GB-1121/sign-on-push-groundwork branch 10 times, most recently from cdf1046 to 3dfc22e Compare March 26, 2026 07:55
Base automatically changed from GB-1121/sign-on-push-groundwork to master March 26, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLI The command-line program `but` rust Pull requests that update Rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant