Hmmm…
> Remove warnings as Git repo is immutable and cannot lose data
Ok this is a great response!
There's also this wishlist/proposals for git log[0], which are extremely exciting to think about; it's from 2012, so even older than the article…
Hmmm…
> Remove warnings as Git repo is immutable and cannot lose data
Ok this is a great response!
There's also this wishlist/proposals for git log[0], which are extremely exciting to think about; it's from 2012, so even older than the article…
Something like this happened to me, breaking the whole Chromium repo for half an hour. Definitely not fun.
So during an interactive rebase you drop one commit, and pick the other, then are upset at git for dropping your commit? It did exactly what you asked of it.
This would have easily been avoided if you had branched off your feature branch into a new one and did the interactive rebase there. Your old feature branch is still present, which you could rebase interactively, or drop HEAD so you only have the other commit, or whatever other thing to meet its needs.