-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add ESLint #1
Comments
I'll do this |
@grigori-gru Yes, please! |
I do this but my access is denied |
Adding eslint to package.json
is this issue open? |
@kalpananegi Yes, give it a shot or you may look into a few good first issues which are up for grabs. ✅ Link to the repository |
is this issue still open? I would like to do this. |
@vinitshahdeo I have a branch ready but I need permission to create a branch and open the PR |
@aleoof @arielhad You have to create a fork of this repository, make the commits on your fork, push them up, and then create a pull request. You will not have permission issues anymore because you are the maintainer of the fork. Here is an article with more information: https://opensource.com/article/19/7/create-pull-request-github |
@vinitshahdeo @mvpowers Can you please review my PR: |
Can I work upon this issue under hacktoberfest @vinitshahdeo |
I have added the ESLint .please review my PR @vinitshahdeo |
Adding ESLint will be helpful in identifying some common and uncommon mistakes that are made during coding.
scripts
inpackage.json
i.e.npm run test-lint
should run lint tests.Please refer this.
The text was updated successfully, but these errors were encountered: