We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not a bug, but incorrect behavior
lerna-changelog uses ; as a delimiter for git log --pretty and then split by it to get commit info.
lerna-changelog
;
git log --pretty
https://github.com/lerna/lerna-changelog/blob/master/src/git.ts#L36
Our CI uses ; symbol for tags labels and automatically adds it to the commits. For example, RC;.;1.164.0.
RC;.;1.164.0
That's why lerna-changelog can not parse commits properly in out case.
I am going to make PR to fix this.
There are a few options:
I like the way with RegExp.
BTW the same issue will be if use ; in commit messages.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Not a bug, but incorrect behavior
lerna-changelog
uses;
as a delimiter forgit log --pretty
and then split by it to get commit info.https://github.com/lerna/lerna-changelog/blob/master/src/git.ts#L36
Our CI uses
;
symbol for tags labels and automatically adds it to the commits. For example,RC;.;1.164.0
.That's why
lerna-changelog
can not parse commits properly in out case.I am going to make PR to fix this.
There are a few options:
I like the way with RegExp.
BTW the same issue will be if use
;
in commit messages.The text was updated successfully, but these errors were encountered: