Show skipped commit message after rebase conflict?
- From
Cameron Steffen <cam.steffen94@gmail.com>
- Date
- Jul 24, 2025, 14:43 UTC
- Message-ID
- <CAAVFnNkdgXuUk6ziu5FkB=sAHzEOyiynQpQJFox_p_ZL9VGRfg@mail.gmail.com>
Hello Git Community!
Sometimes I run into a conflict in a rebase and I end up resolving the conflict by removing all the changes. Then when I run `git rebase --continue`, the current commit is skipped and the rebase continues normally. Would it be possible to emit a message showing that the commit was skipped in this case? It isn't very obvious to me in my workflow that that is what occurred.
Thanks, Cameron Steffen