Feature request: but log & but revert

[jeyj0]

My use-case was this:

• Target branch (dev) had commit abc
• I wanted to revert that commit
• I didn't know the commit-hash
• I wanted to revert that commit as a new revert commit on one of my active branches

How I'd like to have done it:

• but log (to show not just commits on active branches, but also target branch's history)
• copy commit-hash (abc)
• but revert abc, either interactively choosing correct branch, or providing it as another argument

How I worked around it (this could've been more efficient, but I figured it out step-by-step):

• git log → find commit-hash (not nice to find though)
• copy commit-hash (abc)
• git revert abc → created on gitbutler/workspace 🤮
• git log → copy revert-commit's hash (cba)
• git reset --soft 1234 (copied command from gitbutler ui to get back to previous state)
• discarded changes from revert commit
• but pick cba (cherry-pick revert commit to correct branch)

[Byron]

Thanks a lot for sharing!

As this involves a workflow proposition, I thought it would be better to start it out as discussion from which an issue can be created once it's clear what it's going to be.

Let me also reel in @schacon who probably also has some ideas about this.

PS: Now I realise that in future, I might just leave these as issues and label them as discussion, as this semi-threaded format always looked strange unless it's Q&A.