馃悰 Fix commit message escaping #164
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the fix @alvarezfr! |
|
馃帀 This PR is included in version 1.17.1 馃帀 The release is available on GitHub release Your semantic-release bot 馃摝馃殌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #125
Hi @BetaHuhn,
The source of the issue is related to the bash command substitution.
Replaced the execution of the git commit from using double quotes to single quotes. Also, replaced the escaped sequence to escape the single quotes instead of doubles. The escape is a bit funny but all the elements are required. In the git commit message (when inside of single quotes), the
'must be escaped with'\''.After the change, the command substitution is not executed, and also the single quotes and double quotes inside the commit message are processed just fine.