Skip to content
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

GitCommit.raw_log only drop last msg line if blank #42

Merged
merged 3 commits into from
Apr 16, 2015
Merged

GitCommit.raw_log only drop last msg line if blank #42

merged 3 commits into from
Apr 16, 2015

Conversation

scottnonnenberg
Copy link
Contributor

Fixes the message-dropping behavior I saw, potentially the same thing as #38.

@jankeromnes
Copy link
Collaborator

Hi @scottnonnenberg, thanks a lot for fixing this! Do you think we could also add a test that ensures one-line commit messages aren't being dropped in the future?

length -= 1;
}

for(var i = 0; i < length; i++) {
output = output + ' ' + lines[i] + '\n';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Please use output += here.

@scottnonnenberg
Copy link
Contributor Author

Unit tests added. Seems that the couple full repos under /test all have the expected trailing newline, so I couldn't use any existing fixture data.

@jankeromnes
Copy link
Collaborator

Awesome, thanks!

@jankeromnes jankeromnes merged commit c88e44a into christkv:master Apr 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants