Skip to content

Conversation

stewartpark
Copy link

@stewartpark stewartpark commented Jul 5, 2018

The rubocop-git command exits with exit code 1, but the console output says no offenses.

This is because it doesn't display disabled offenses, and if all offenses are disabled under a violation, it just says there are no offenses. But when it determines whether it should exit(1), it just sees if there are any violations.

@stewartpark stewartpark force-pushed the invisible-offenses branch from 8ab66a1 to e01a226 Compare July 5, 2018 21:06
@stewartpark stewartpark force-pushed the invisible-offenses branch from e01a226 to d1a53b6 Compare July 7, 2018 00:30
@seanbjornsson
Copy link

seanbjornsson commented Apr 16, 2019

I'll go ahead and second this PR. We use rubocop-git for CI build checks, on only changed code. This issue causes it to fail on seemingly no offenses.

And can confirm this change fixes our issue. @m4i any chances this will make it in?

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