feat(context): add release commit range#1138
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1138 +/- ##
==========================================
- Coverage 40.16% 40.04% -0.12%
==========================================
Files 21 21
Lines 1900 1911 +11
==========================================
+ Hits 763 765 +2
- Misses 1137 1146 +9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
ah interesting. i just updated my toolchain under windows so the clippy errors (and the linting error here) are probably explained by that. |
orhun
left a comment
There was a problem hiding this comment.
Looking pretty good, thanks for reopening the PR!
Only got one question
b384e40 to
945a05a
Compare
Co-authored-by: Orhun Parmaksız <[email protected]>
945a05a to
9030e40
Compare
orhun
left a comment
There was a problem hiding this comment.
Awesome, thanks for bearing with me!
|
Congrats on merging your first pull request! ⛰️ |
Same to you :D |
Description
Adds the used
commit_rangefor each release.commit_rangeincludes the full length commit ids (commit_range.fromandcommit_range.to)Also added related docs (and documentation for the sort_commits default)
Motivation and Context
See #1041
How Has This Been Tested?
Via integration_test and three new fixtures.
Types of Changes
Checklist:
random sideinfo:
repo::test::propagate_error_if_no_repo_foundfails under windows.clippy also reports errors under windows.