Hi,
as stated in the topic, all commit messages that are started with hash character (#) are aborted.
Steps to reproduce:
- Stage some changes.
- Type following commit message:
#123456 - test.
- Press Commit button.
Hi,
as stated in the topic, all commit messages that are started with hash character (#) are aborted.
Steps to reproduce:
#123456 - test.
I encountered the same issue.
When using git from the CLI, it worked well because I went with the git config core.commentChar “@” approach.
Seems like Sublime Merge does not take that into account!
After some more testing I indeed see that the comment character seems to be ignored by Sublime Merge