feat(version): add --skip-bump-only-release to avoid empty gh releases#555
feat(version): add --skip-bump-only-release to avoid empty gh releases#555ghiscoding merged 2 commits intonextfrom
--skip-bump-only-release to avoid empty gh releases#555Conversation
Codecov Report
@@ Coverage Diff @@
## next #555 +/- ##
=======================================
Coverage ? 97.93%
=======================================
Files ? 160
Lines ? 12433
Branches ? 2030
=======================================
Hits ? 12175
Misses ? 257
Partials ? 1 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
@StarpTech I believe this PR and feature could be useful to your project and it could be nice to have a review if you get a chance. I'm not using the |
ghiscoding
changed the title
--skip-bump-only-release to avoid empty gh releases--skip-bump-only-release to avoid empty gh releases
ghiscoding
changed the title
--skip-bump-only-release to avoid empty gh releases--skip-bump-only-release to avoid empty gh releases
ghiscoding
force-pushed
the
feat/skip-bump-only-release
branch
from
72503e5 to
378c33a
Compare
ghiscoding
force-pushed
the
feat/skip-bump-only-release
branch
from
f71006d to
f230af3
Compare
packages/version/README.md
Outdated
|
|
||
| ### `--skip-bump-only-release` | ||
|
|
||
| When this option is enabled and a package version is only being bumped without any conventional commits detected, the GitHub/GitLab release will be skipped. This will avoid creating releases with only "Version bump only for package x" in the release notes, however please note that each changelog will still be updated the version bump only text. |
There was a problem hiding this comment.
typo, it should be "are still going to be updated with the "version bump only" text."
|
Hi @ghiscoding, thank you for the update. Unfortunately, I had no time to test it. |
|
@StarpTech no problem, it should be ok and it's now released under v2.0.0 |
2 participants
Description
When using
independentmode, a GitHub/GitLab release is created for each package and very often some of the package will only have a"Version bump only for package x"added to the changelog and a release is created even for these simple bump only package. However these kind of release are not very useful and could be skipped, this is what this option flag will provide to the user when the package is detected to be a version bump only, with this flag enabled, it will not create a release for that packageNote this will be available only under the new
majorv2.0.0 version and higher of Lerna-LiteMotivation and Context
Avoid creating too many releases with info that are not that useful, most users are interested in "what changed?" and not so much in "nothing changed in package x"
How Has This Been Tested?
unit tests only
Types of changes
Checklist: