-
Notifications
You must be signed in to change notification settings - Fork 0
1-ci-config #2
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
1-ci-config #2
Conversation
Conditionally install cc-test-reporter by os. Still might not work, since the test reports probably need to be merged. 🤞 #1
CodeClimate does not support eslint-plugin-unicorn. CodeClimate does, however, support eslint-config-xo, which includes eslint-plugin-unicorn. Replaced plugin with eslint-config-xo, and disabled rules that do not comply with JavaScript Standard Style. #1
Moved statements with common behaviors into helper functions in order to comply with max-nested max-line rules. #1
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.
The PR diff size of 8805 lines exceeds the maximum allowed for the inline comments feature.
There are too many results to compare The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 100.0%. View more on Code Climate. |
Marked as "approved" on the CodeClimate site. |
I didn't mean to close the PR! (I was thinking in terms of GitLab Discussion Resolution 🤦♂️ .) |
- Install to the TRAVIS_BUILD_DIR - Run from the TRAVIS_BUILD_DIR - Try to exit 0 on failure. This is my last attempt to use cc-test-reporter before I uninstall it. #1
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.
The PR diff size of 9958 lines exceeds the maximum allowed for the inline comments feature.
Associated issue(s)
Closes #1
completed, tested, and validated.
require updates.
Code quality summary
Code quality, vulnerability, and standards compliance tools
How to format, lint, and test your changes
Open a Terminal, go to the root directory for parse-numeric,
and run:
$ npm test