Being a developer most times means working with git.
There are many different ways to use git and every project, every developer has their preferences.
For my own projects I work a lot with GitHub and I love using the
git rebase -i feature to clean up commits.
Lately I ran into the problem that rebasing a Commitizen commit message with a linked GitHub issue leads to problems.
The problem is that the rebase UI treats the
# hash sign as an escape character for comments.
In the message below the reference to the GitHub issue #53 would be removed from the commit message as
# is the leading character in line 3.
This could be fixed by prepending some text to make sure the line does not start with a hash.
However the Commitizen style I use creates commit messages that include the issue ID on a new line and I did not want to break this pattern during rebases.
But luckily you can configure the escape character that git uses in the rebase UI.
By setting the
core.commentChar = ";" (or any other single character) in your git config.
On my MacOS device my
~/.gitconfig has the following entries after including the
The next time you
git rebase -i you will see that all comments are escaped using
; instead of the hash sign.
This also means that my original commit message with a
# leading in line 3 will now be taken over as it is no longer treated as a comment.
You can pick any character you want to escape comments in the rebase UI, just make sure it fits your workflow and does not conflict with any rules you have for git messages.
Hope this little trick can help you too 👋