parse-commit-message
parse-commit-message copied to clipboard
(!! moved to tunnckoCore/opensource !! try `parse-commit-message@canary`) Parse, stringify or validate a commit messages that follows Conventional Commits Specification
I can't use parse-commit-message library because our project DX Scanner (which scans your repo to recommend you the best practices) uses a newer node. 
See https://github.com/tunnckoCoreLabs/parse-commit-message/issues/71
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@tunnckocore/config](https://togithub.com/tunnckocorehq/config) | devDependencies | major | [`^1.0.0` -> `^5.0.0`](https://renovatebot.com/diffs/npm/@tunnckocore%2fconfig/1.0.3/5.0.8) | --- ### Release...
i'm new to this typescript and decorators thing, but watching a few videos on TypeGraphQL it's totally cool.
https://circleci.com/gh/intuit/auto/6454?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link also the code on github is pretty out of date
Just couldn't pass by these typos :) ----- [View rendered README.md](https://github.com/kutyepov/parse-commit-message/blob/docs/fix-typo-in-plugins-example/README.md)
Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README. Below are docs for integrating FOSSA license checks...
What I'm thinking is to have a simple convention. Just list of changed packages inside the commit body, like so ``` feat: foo bar baz The changed packages will be...