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

Handle empty commit list in --commits (#22) #25

Merged
merged 1 commit into from
Mar 16, 2017

Conversation

tommyip
Copy link
Contributor

@tommyip tommyip commented Mar 15, 2017

This fixes a "index out of range" exception when the specified git range for --commits is empty.

Fixes #22.

This fixes a "index out of range" exception when the specified git
range for --commits is empty.

Fixes jorisroovers#22.
@tommyip
Copy link
Contributor Author

tommyip commented Mar 15, 2017

The OSX test doesn't seem to be starting.

@jorisroovers jorisroovers merged commit 90979db into jorisroovers:master Mar 16, 2017
@jorisroovers
Copy link
Owner

jorisroovers commented Mar 16, 2017

Thanks :)

The OSX test doesn't seem to be starting.

Yeah, there is an issue with the OSX tests on Travis that I don't think has anything to do with gitlint. I've reached out to Travis but haven't heard back yet.

With this merge, I'm going to release v0.8.1. I would've liked to have more tests and fixes for some of the other issues (#23 and #24), but I likely won't have time for those in the remainder of the week. Since I want to unblock you on zulip/zulip#1131, I'll just note that the --commits feature is still experimental in the v0.8.1 release notes.

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.

--commits option does not handle 0 commits case.
2 participants