-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double backticks escaping is no longer required #67
Closed
RomanMinkin opened this issue
Mar 13, 2019
· 2 comments
· May be fixed by satoshinakamoto007/bitcore#1119
Closed
Double backticks escaping is no longer required #67
RomanMinkin opened this issue
Mar 13, 2019
· 2 comments
· May be fixed by satoshinakamoto007/bitcore#1119
Comments
RomanMinkin
pushed a commit
to RomanMinkin/cz-customizable
that referenced
this issue
Mar 13, 2019
ISSUES CLOSED: leoforfree#67
RomanMinkin
added a commit
to RomanMinkin/cz-customizable
that referenced
this issue
Mar 14, 2019
ISSUES CLOSED: leoforfree#67
RomanMinkin
added a commit
to RomanMinkin/cz-customizable
that referenced
this issue
Mar 14, 2019
ISSUES CLOSED: leoforfree#67
🎉 This issue has been resolved in version 5.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This issue is present again in version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Double backticks escaping was introduced in 99aa05b to fix #23 , but it's no longer required since
[email protected]
has fixed it commitizen/cz-cli@5f7737fCurrent code produces extra escaping for non
win32
architectures:Do you guys want me to open up a PR?
The text was updated successfully, but these errors were encountered: