After this is merged, some trivial Travis CI setup is necessary to complete the process (I'll handle that).
dangerfile.js is where the actual linting logic is performed (this can be used for lots of things besides linting). Updates to .travis.yml are necessary to actually run Danger as part of CI. It was necessary to make .eslintrc into a JSON file so it could be imported and parsed in the Dangerfile. Also, I disabled auto-fixing in the default npm run lint script.
This PR enables automatic linting of the files that were changed in any given PR. On success, a message like this one is added by a bot:
On failure/warning, it looks like this:
After this is merged, some trivial Travis CI setup is necessary to complete the process (I'll handle that).
dangerfile.jsis where the actual linting logic is performed (this can be used for lots of things besides linting). Updates to.travis.ymlare necessary to actually run Danger as part of CI. It was necessary to make.eslintrcinto a JSON file so it could be imported and parsed in the Dangerfile. Also, I disabled auto-fixing in the defaultnpm run lintscript.