What did you do before the bug happened? (Steps to reproduce your issue) 1. Create a commit with hash-issueId, eg. '#87 Fix wrong indent' 2. Create a second commit with any commit message. 3. Use interactive rebase and 'f'ixup the second commit to the first one. What did you expect to happen? (Expected behavior) I expect a single commit with message: '#87 Fix wrong indent' What happened instead? (Actual behavior) There is a commit with empty commit message. This happens without any warning and one notices even too late. What's different between what you expected and what actually happened? The commit message disappeared as it was probably treated as a comment. Anything else you want to add: [System Info] git version: git version 2.28.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Darwin 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 compiler info: clang: 11.0.3 (clang-1103.0.32.62) libc info: no libc information available $SHELL (typically, interactive shell): /usr/local/bin/bash [Enabled Hooks] pre-commit
