Disable eslint in codeclimate #221
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm, the build succeeded at https://codeclimate.com/github/zendesk/radar/builds/115. I think we need to remove and re-add the codeclimate integration in this repo's settings. |
|
👍 |
junosuarez
added a commit
that referenced
this pull request
Feb 12, 2016
Disable eslint in codeclimate
|
landed in 0.21.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use standard rather than eslint.
Currently we run it in a pretest step, so linting errors would be caught in a travisci build failure.
In the future, we may be able to move this linting step back into codeclimate.
References
standardcodeclimate engineRequired
Risks