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

Run linting in continuous integration #906

Closed
excitement-engineer opened this issue Oct 15, 2016 · 8 comments
Closed

Run linting in continuous integration #906

excitement-engineer opened this issue Oct 15, 2016 · 8 comments

Comments

@excitement-engineer
Copy link
Contributor

I am wondering if it is possible to perform an eslint check during continuous integration to ensure that the coding guidelines are maintained by developers.

Does anyone know of a way to do this?

@excitement-engineer
Copy link
Contributor Author

Specifically for the javascript code. I want CI to be able to catch the warnings in the linter such as the following example:

screen shot 2016-10-15 at 13 52 38

Do you know if this is currently possible?

@mxstbr
Copy link
Contributor

mxstbr commented Oct 15, 2016

Sorry, deleted my comment, my brain was still in the wrong project so it didn't make any sense. 😊

I haven't done that so I'm not sure, sorry!

@excitement-engineer
Copy link
Contributor Author

hahaha no worries!

@gaearon
Copy link
Contributor

gaearon commented Oct 15, 2016

I think linting should be a part of npm run build on CI environments.
There is an issue for this: #440.

Would you like to send a PR?
Let's enable this only if process.env.CI is "true".
Otherwise local builds will be annoyingly slow.

It's fine to totally abort the build on CI if there are any lint warnings, but not locally.

@excitement-engineer
Copy link
Contributor Author

Yes I will send a PR, I will try to find some time to fix this next week:) Thanks a lot for your help and quick response!

@karlhorky
Copy link

Can this be closed now that #944 is merged?

@mxstbr
Copy link
Contributor

mxstbr commented Dec 4, 2016

Yes! Thanks @karlhorky

@mxstbr mxstbr closed this as completed Dec 4, 2016
@karlhorky
Copy link

Np, thanks for all the work on this!

@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants