feat(parser): allow whole commit context to be used in commit parsers#758
Conversation
|
Thanks for opening this pull request! Please check out our contributing guidelines! ⛰️ |
|
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #758 +/- ##
==========================================
+ Coverage 36.71% 36.83% +0.12%
==========================================
Files 19 19
Lines 1501 1499 -2
==========================================
+ Hits 551 552 +1
+ Misses 950 947 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9e39fb5 to
7db25f8
Compare
c3403f8 to
32da6d3
Compare
orhun
left a comment
There was a problem hiding this comment.
This is definitely good to have!
Can you also update the documentation (i.e. add some examples)? Adding your use case to Tips and Tricks would be also pretty nice.
|
Congrats on merging your first pull request! ⛰️ |
Description
Allow grouping of commit by arbitray context fields instead of just a limited set
Motivation and Context
Outlined in #757
How Has This Been Tested?
Tested with this config
on this repository.
Command ran:
GITHUB_TOKEN="" git-cliff --github-repo=bakdata/kpops -o CHANGELOG.mdScreenshots / Logs (if applicable)
Excerpt from generated changelog:
Changelog
All notable changes to this project will be documented in this file.
6.1.0 - 2024-07-09
What's changed
🚀 Features
🏭 Refactor
Full Changelog: bakdata/kpops@6.0.2...6.1.0
6.0.2 - 2024-07-04
What's changed
📝 Documentation
🌀 Miscellaneous
Full Changelog: bakdata/kpops@6.0.1...6.0.2
6.0.1 - 2024-06-12
What's changed
🐛 Fixes
Full Changelog: bakdata/kpops@6.0.0...6.0.1
Types of Changes
I have reordered execution here to make sure the context object is populated when the commits are parsed.
Checklist: