@artsy/lint-changed

This package is inspired heavily by lint-staged. Also checkout pull-lock.

We waste a lot of time of CI time doing unnecessary tasks. Why lint all your files when git already tells you which files have changed? @artsy/lint-changed helps by only running lint tags for the files that have changed since master (when not on master) or since the last tag (if you are on master).

Basic Configuration

Add a lint-changed key to your package.json with a pattern of files to match and the command or commands you'd like to run for each changed file. Each command will be ran for every changed file that matches it's pattern.

{
  "lint-changed": {
    "*.js": ["eslint", "prettier -c"],
    "*.ts": "tslint"
  }
}

For the given configuration above if the following three files were changed...

foo.js
bar.ts
baz.json

You could expect the following commands to be ran

eslint foo.js
prettier -c foo.js
tslint bar.ts

Note that baz.json would be skipped because it doesn't match with any patterns in the configuration.

Configuring base branch

By default Artsy will use master as the base branch for detecting changes. In case your default branch is not master you can let Artsy know what branch to use as a base branch.

{
  "lint-changed-base-branch": "development",
  "lint-changed": {
    "*.js": ["eslint", "prettier -c"],
    "*.ts": "tslint"
  }
}

About Artsy

This project is the work of engineers at Artsy, the world's leading and largest online art marketplace and platform for discovering art. One of our core Engineering Principles is being Open Source by Default which means we strive to share as many details of our work as possible.

You can learn more about this work from our blog and by following @ArtsyOpenSource or explore our public data by checking out our API. If you're interested in a career at Artsy, read through our job postings!