This message was deleted.
# how-do-i
s
This message was deleted.
➕ 1
j
checking out the branch should fix this! how did you abort the operation?
e
I aborted by
ctrl+C
, wasn't a smart move haha I ended up deleting everything locally and fetching the remove branch, so disaster avoided! That being said, I'm not sure checking out the branch would do it? I noticed locally that the branch was gone, and everything in the branch seemed to be an uncommitted change.
j
Sorry about that -- we should be catching that and re-checking out the branch
🫡 1
e
Yeah it looks like a bug tbh!
👍 1
j
And interesting that the branch seemed to disappear -- that seems like a bug as we actually dont change anything until the split is finalized. We detach from any branch to create the new commits but checking it back out is meant to work.
e
I aborted by
ctrl+C
, wasn't a smart move haha
I ended up deleting everything locally and fetching the remove branch, so disaster avoided!
Lol, you are not the only one 🙈 Thanks for asking about it!
🫡 1
e
Hmm maybe the branch was still there, but I didn't notice. I look by doing
git tree
, and here's my alias for tree:
tree = log --graph --decorate --pretty=oneline --abbrev-commit
j
ah, the branch wont be in the history of the detached head because we rewind to the parent branch and start creating new commits from there. if you ran git log <branch> you would see it
so i believe the only bug here is just fixing the interrupt handler
👍 1
of course, this state is definitley confusing -- we don't mean to expose any of the details as UX
e
Yeah that sounds about right!
e
we don't mean to expose any of the details as UX
Doing a great job of it so far!