-
Notifications
You must be signed in to change notification settings - Fork 326
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
chore: generate release notes with git-cliff #3650
Conversation
Signed-off-by: tison <wander4096@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3650 +/- ##
==========================================
- Coverage 85.14% 84.81% -0.33%
==========================================
Files 943 943
Lines 157092 157092
==========================================
- Hits 133754 133244 -510
- Misses 23338 23848 +510 |
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.
LGTM
Signed-off-by: tison <wander4096@gmail.com>
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.
LGTM
Merging ... So far, we always generate changelog with neighboring tags. I'll investigate #3650 (comment) if we later make multi-branches releases. That is:
Then, to generate the changelog for 1.3, we'd better select a range v1.2.0..v.1.3.0 |
If we use the multi-branch flavor for git management, |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
This refers to #3609
Checklist
Result
Install
cargo install git-cliff
Running
GITHUB_TOKEN=*** git cliff v0.6.0..v0.7.0
gives:(We can then manually add highlights and/or fine-tuning the notes)