simple-commit-message
simple-commit-message copied to clipboard
Simple commit message wizard and validator; works with commitizen and pre-git
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [semver](https://redirect.github.com/npm/node-semver) | [`5.7.1` -> `5.7.2`](https://renovatebot.com/diffs/npm/semver/5.7.1/5.7.2) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release...
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/checkout](https://togithub.com/actions/checkout) | action | major | `v2` -> `v3` | ---...
For example see https://github.com/bahmutov/generator-node-bahmutov/commit/8eb48addc834294f6248d163e69c37ef3ca38e12 The subject is just `Immutable (#57)` but the body has titles from 3 commits that were squashed from the pull request. One of them is semantic...
More specifically said, it does, but that adding of `BREAKING CHANGE` to body and title seems almost useless. Or at least not make sense to output that prompt every time...
As like we have `subject` and `type`, so we should have `body` too. ;)
Just like #3
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [debug](https://redirect.github.com/debug-js/debug) | [`4.3.4` -> `4.4.3`](https://renovatebot.com/diffs/npm/debug/4.3.4/4.4.3) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ubuntu](https://redirect.github.com/actions/runner-images) | github-runner | major | `20.04` -> `24.04` | --- ### Configuration...
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/checkout](https://redirect.github.com/actions/checkout) | action | major | `v2` -> `v4` | --- ### Release...