-
Notifications
You must be signed in to change notification settings - Fork 10
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
git: Fix git message parsing #329
base: main
Are you sure you want to change the base?
git: Fix git message parsing #329
Conversation
Warning Rate limit exceeded@Donach has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 58 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe recent changes enhance the functionality of commit message retrieval and processing in the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- src/git.rs (3 hunks)
Additional comments not posted (3)
src/git.rs (3)
35-35
: LGTM! The updated format string enhances the information retrieved from the git log.The new format string includes additional commit details, which improves the functionality.
51-61
: LGTM! The changes improve the handling of commits without body messages.The regular expression modification and the conditional check ensure that only non-empty message lines are included, improving the quality of the output.
94-94
: LGTM! The changes broaden the criteria for recognizing the end of the message body.Considering lines that contain only a pipe character (
|
) improves the functionality by accommodating different formatting styles in commit messages.
@@ -89,7 +91,7 @@ pub fn parse_commit_message( | |||
|
|||
for line in lines_iter { | |||
if line.trim().is_empty() { | |||
if in_body { | |||
if in_body || line.trim() == "|" { |
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.
In case there is no body, this is necessary as we will skip the body and the "|" will help us switch to footers.
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.
Thank you!
I would like to have a unit test for no body test case 🙏
95c2ee0
to
0bb0a17
Compare
- Add data of Author and Date to footer
0bb0a17
to
4cc9dcb
Compare
.arg("--no-merges") | ||
.arg("--no-decorate") | ||
.arg("--reverse") | ||
.arg(range) | ||
.arg(opt_target) |
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 also quite handy - in case no range is specified, this will ensure we compare only current branch - IMO quite major use-case for regular every day development.
You don't care for commit linting on master, since you cannot usually just rebase it as you want. -> also if all commits that are merged to master are already valid by commitlint, no need to run it there at all...
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.
Thank you for your PR! I'll check this not later than this weekend!
Sorry for the delay, thank you for your PR! |
I'll try to take a look within the next few weeks if there are some sensible tests to be added... |
Why
I've tested the tool and decided to implement it in our company.
However, there are some logical flaws which prevent us from using it.
We have a policy that if a commit change is small enough, there is no need to fill in the body - the tool itself also allows to set for empty body of commit message.
However parsing of git commits with no body message creates problems.
At the same time, it seems like the tool doesn't even properly split the messages, since when you use "--pretty=%B", it will return only subject+body of the commit message, so the
fn extract_commit_messages
will not work to separate commits properly.By applying this fix, I was able to fix this major flaw, it also breaks no tests and no other changes are necessary.
One minor bug -> if somebody would "abuse" my usage of "|" as artificial separator, it might break the logic a bit, but IMO that is very rare case to happen.
I'm open for discussion on how to improve it further, as we don't wanna overhaul the whole tool just to fit our "few special needs".
Summary by CodeRabbit
New Features
Bug Fixes