You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, since I'm using signed commits in a repo, I would love to be able to also create signed commits with absorb. This can of course be generalized down to "specify options to be used when running commit".
The text was updated successfully, but these errors were encountered:
hm, this is probably worth supporting, but i'd like to know more about the use case here. absorb commits aren't really intended to be published anywhere (they should disappear as part of rebase --autosquash), so whether they're signed shouldn't be super important?
Well, for a testing environment where I'm pushing the fixups and see if it works, I wouldn't always want to do absorb, rebase, push but rather just absorb + push. I agree that just doing a rebase is a valid workaround for my use case.
Specifically, since I'm using signed commits in a repo, I would love to be able to also create signed commits with absorb. This can of course be generalized down to "specify options to be used when running commit".
The text was updated successfully, but these errors were encountered: