Search Results for "repository"

Run linters against staged git files and don't let anything slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary shell tasks with a list of staged files as an argument, filtered by a specified glob pattern. ...

This repository is for the GitHub Action to run a Super-Linter. It is a simple combination of various linters, written in bash, to help validate your source code. The super-linter finds issues and reports them to the console output. Fixes are suggested in the console output but not automatically fixed, and a status check will show up as failed on the pull request.

...You don't have to fix any whitespace errors and waste time configuring eslint presets. Prettier-standard is best used with the prettier-standard --lint command which formats and lints all non-ignored files in the repository.

Luna Code Checker An advanced web-based tool for checking JavaScript code using ESLint. How to Use Clone the repository. Run npm install to install the dependencies. Run npm start to start the server. Open http://localhost:3000 in your web browser. Write or paste your JavaScript code in the textarea. Click the "Check Code" button to see linting results. Features Comprehensive syntax and style checking using ESLint. Detailed error messages including line numbers and descriptions. ...