-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(changelog): fix missing commit fields in context (#837) #920
Conversation
Thanks for opening this pull request! Please check out our contributing guidelines! ⛰️ |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #920 +/- ##
==========================================
- Coverage 41.57% 41.49% -0.07%
==========================================
Files 21 21
Lines 1677 1685 +8
==========================================
+ Hits 697 699 +2
- Misses 980 986 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
a693040
to
52712d8
Compare
134d053
to
9dab742
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat!
Left some comments :) Also, can you update the documentation (in /website
) about the existence of the new raw_message
field?
04e064c
to
f24e48d
Compare
I fixed according to your comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last thing :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These test commits should no longer be needed. Can you test with an empty commit.sh
and commit it if it works?
P.S. we should do the same for test-from-context
fixture too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, it didn't work. I got an error, we must at least have one commit. I think this is a bug, but maybe we should fix this in another PR?
ERROR git_cliff > Git error: `reference 'refs/heads/main' not found; class=Reference (4); code=UnbornBranch (-9)`
However, even if we don't use commit.sh
, I think we should just keep it there, as a reference. I find it more difficult to read context.json
compared to commit.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, okay. Yup, we need to fix that bug in another PR.
I find it more difficult to read context.json compared to commit.sh
Fair enough!
367ea95
to
3d96357
Compare
* feat(commit): add `raw_message` to `Commit` * test(fixtures): add test generate all fields in conventional commits * test(fixtures): add test do not discard missing fields in conventional commits when reading from context * docs(website): add `raw_message` fields to `context.md`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks for your contribution!
Congrats on merging your first pull request! ⛰️ |
Hi @orhun, I just encountered this issue. Could you please make a release that includes this fix? |
Yup, I will try to do a release next week. |
Sorry to bother you, but any chance you could release it? |
released now :) |
Description
Add new fields
raw_message
inCommit
to avoid lossy message conversion.Fix #837
Motivation and Context
I implemented according to #837 (comment)
How Has This Been Tested?
Add 2 test fixtures
git cliff --context | git cliff --from-context
should yield identical result withgit cliff
Screenshots / Logs (if applicable)
Types of Changes
Checklist: