Feature Request (@commitlint/parse): Support parsing information for breaking changes
See original GitHub issueHi,
I just took a quick look at the type definition for Commit
used in @commitlint/parse
, I don’t see information related to breaking changes present. Could we support this?
I think either by seeing BREAKING CHANGE
in the footer
or by spotting the exclamation point !
in the header.
Thank you so much!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Conventional Commits
This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. The commit message should be ...
Read more >@commitlint/config-validator | Yarn - Package Manager
Change Log. All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
Read more >@commitlint/parse - npm
Start using @commitlint/parse in your project by running `npm i @commitlint/parse`. There are 16 other projects in the npm registry using ...
Read more >How To Automatically Generate A Helpful Changelog From ...
This article describes some tools that can help to automate the changelog ... MAJOR: is incremented when you add breaking changes, e.g. an...
Read more >Push rules - GitLab Docs
You can require all commits to your project to comply with the DCO. This push rule requires a Signed-off-by: trailer in every commit...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like for people with my needs, we can just use
conventional-commits-parser
and note this answer https://github.com/conventional-changelog/conventional-changelog/issues/648#issuecomment-704867077@escapedcat As for the typings, I suppose you can just use @types/conventional-commits-parser perhaps.
I’m closing this issue now. Thanks!
@escapedcat oh! I see what you mean now, we call
conventional-commits-parser
anyway. Maybe I should actually file an issue over there. Let me take a look and let you know!