-
Notifications
You must be signed in to change notification settings - Fork 255
Inconsistent carriage returns in generated changelogs #955
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
Labels
bug
Something isn't working properly
Comments
wyardley
added a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 15, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). Fixes python-semantic-release#955
wyardley
added a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 15, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). Fixes python-semantic-release#955
https://bugs.python.org/issue40863
|
wyardley
added a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 15, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). This is only needed in the case when we are _not_ byte decoding. Fixes python-semantic-release#955
wyardley
added a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 15, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). This is only needed in the case when we are _not_ byte decoding. Fixes python-semantic-release#955
codejedi365
pushed a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 17, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). This is only needed in the case when we are _not_ byte decoding. Fixes python-semantic-release#955
wyardley
added a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 17, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). This is only needed in the case when we are _not_ byte decoding. Fixes python-semantic-release#955
codejedi365
pushed a commit
to wyardley/python-semantic-release
that referenced
this issue
Jun 17, 2024
The default template can result in mixed (UNIX / DOS style) carriage returns in the generated changelog. Use a string replace in the commit parser to strip the DOS CRs ("\r"). This is only needed in the case when we are _not_ byte decoding. Fixes python-semantic-release#955
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
The commit object returned from GitPython seems to sometimes contain DOS CRs (
^M
)s (even when the original commit message does not contain them). This results in inconsistent carriage return style in generated changelogs with the default templateExpected behavior
Consistent CRs in generated changelog
Environment
I can make a PR to fix this, though may need some help with figuring out the best way(s) to test if applicable.
The text was updated successfully, but these errors were encountered: