-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
feat(changelog): add merge-prerelease flag #703
Conversation
ebf3f73
to
d5f6722
Compare
7ef678c
to
23fa1b8
Compare
23fa1b8
to
45113d0
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v3 #703 +/- ##
==========================================
+ Coverage 97.98% 98.11% +0.12%
==========================================
Files 41 41
Lines 1835 1855 +20
==========================================
+ Hits 1798 1820 +22
+ Misses 37 35 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
cfbbfb5
to
ab957a4
Compare
It seems the pre-commit hook |
ab957a4
to
a42531b
Compare
Found out another reason why test would randomly fail. It's caused by concurrent tests all accessing the same temporary file for the backup of the commit message. Changing the test script to run test independently seems to solve the issue. |
16aacf5
to
0e0a012
Compare
@woile could you perhaps have a look at the pr? Do you maybe have some idea on how to keep |
tests/test_changelog.py
Outdated
gitcommits, tags, parser, changelog_pattern, merge_prerelease=True | ||
) | ||
|
||
assert tuple(tree) == COMMITS_TREE_MERGED_PRERELEASES |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should COMMITS_TREE_MERGED_PRERELEASES
be renamed to COMMITS_TREE_AFTER_MERGED_PRERELEASES
?
How is this test different than just test_generate_tree_from_commits
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that name is better. It's different in the sense, that COMMITS_TREE_AFTER_MERGED_PRERELEASES
does not contain pre-releases (there were 2) and the changes of them are now part of the next non-prerelease.
How does this feature affect existing changelogs? |
Can you point this PR to |
Existing changelogs will be changed when run with this flag. This is unless you also add the
Will do! |
bde4bdc
to
44ace73
Compare
Running tests concurrently can cause temporary files, such as the file used to backup the commit message, to be deleted by one test but accessed by another test later on.
44ace73
to
e34de55
Compare
… issue with freeze_time Signed-off-by: apkawa <[email protected]> commitizen-tools#703
Description
Added a
--merge-prerelease
flag and config option as described in #687.Checklist
./scripts/format
and./scripts/test
locally to ensure this change passes linter check and testExpected behavior
Steps to Test This Pull Request
Additional context
The dependency
codecov
seems to be no longer available.I can try to fix it in this pull request, but could also create a new one, depending on what is preferred.I have now to my own frustration fixed the
codecov
action in the second commit. This also closes #685