Replies: 1 comment 2 replies
|
Disregard this answer, I misread the title and thought we were discussing Commits are unhidden (unabandoned) when:
If you use the op log to find the commit ID you want to be visible again, you can run I probably would have used
|
2 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.
I did a squash and then a push. I then realized that the changes I had squashed were incorrect, and wanted to return to the state from before the squash, without creating bookmark conflicts by undoing the
push.I first tried
jj op undo <squash-op>, without realizing that the "targeted" version ofundoisrevert. The help-string gave the tipa similar subcommand exists: 'abandon', so I thought that abandoning an operation would undo the change created by that operation, the same way that abandoning a commit rebases descendants. However,abandonjust reparents descendants, so the file contents were not changed.After realizing that there's a
revertoperation I should have used, is there a way I could have "undone" theabandonso that I couldrevertthe operation instead?(Also, I think it would be helpful if the tip for
jj op undomentioned bothjj undoandjj op revert, and if the--helpoutput forjj undomentionedjj op revert. I also feel likeundoandredoare intrinsically "op" operations, so I'm kind of surprised that "undo" isn'tjj op undo, withjj undosimply being an alias, and similarly forredo.)All reactions