chore(ci): run depcheck and lint in CI

.github/workflows/lint.yml

@@ -0,0 +1,22 @@
+name: Linting
+
+on: [push, pull_request]
+
+env:
+  CI: true
+
+jobs:
+  test:
+    runs-on: ubuntu-18.04
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js 14.x
+        uses: actions/setup-node@v1
+        with:
+          node-version: 14.x
+      - run: yarn --frozen-lockfile
+      - run: yarn clean
+      - run: yarn prepack
+      - run: yarn lint
+      - run: yarn lint:deps

README.md

@@ -912,13 +912,11 @@ however, ensure that your action only applies to the shadow database by setting
 the `"shadow": true` property, leaving you free to manage how your more
 permanent databases are initialized.
 
-
 ## Examples
 
 - [Running Graphile Migrate in a Docker container](docs/docker/README.md)
 - [Examples of idempotent migration files including edge cases](docs/idempotent-examples.md)
 
-
 ## TODO:
 
 - [ ] Store pgSettings with committed transactions to protect against user edits

docs/docker/README.md

@@ -1,15 +1,15 @@
 # Running Graphile Migrate from a container
 
 When working in a team it can be useful to package `graphile-migrate` and the
-Postgres tooling into a Docker file so that everyone has easy access to the
-same versions. This is also helpful if you're using Migrate as part of a larger
+Postgres tooling into a Docker file so that everyone has easy access to the same
+versions. This is also helpful if you're using Migrate as part of a larger
 non-Node based project.
 
 For these purposes we provide an [example Dockerfile](./Dockerfile) in the
 `docs/docker` directory in the source tree. This uses the latest released
 version of `graphile-migrate` from `npm` and packages it together with the
-necessary Node and Postgres tools. You can build the Dockerfile from the
-root of the repository using a command like such as:
+necessary Node and Postgres tools. You can build the Dockerfile from the root of
+the repository using a command like such as:
 
 ```bash
 docker build -t graphile-migrate docs/docker \

docs/idempotent-examples.md

@@ -48,9 +48,9 @@ begin
     /* if column `username` exists on users table */
     if exists(
         select 1
-            from information_schema.columns 
+            from information_schema.columns
             where table_schema = 'public'
-            and table_name = 'users' 
+            and table_name = 'users'
             and column_name = 'username'
     ) then
         /* rename the column to `name` */
@@ -60,7 +60,9 @@ begin
 end$$;
 ```
 
-The structure changes a little if we want to rename an enum value, but the idea is the same:
+The structure changes a little if we want to rename an enum value, but the idea
+is the same:
+
 ```sql
 do $$
 begin
@@ -79,4 +81,6 @@ begin
 end$$;
 
 ```
-Because of its compliance with the SQL standard, the `information_schema` does not contain Postgres-only objects, like enums.
+
+Because of its compliance with the SQL standard, the `information_schema` does
+not contain Postgres-only objects, like enums.

package.json

@@ -5,11 +5,12 @@
   "main": "dist/index.js",
   "scripts": {
     "lint": "yarn prettier:check && eslint --ext .js,.jsx,.ts,.tsx,.graphql .",
+    "lint:deps": "depcheck --ignores @types/jest,eslint_d,tslib ",
     "lint:fix": "eslint --ext .js,.jsx,.ts,.tsx,.graphql . --fix; prettier --ignore-path .eslintignore --write '**/*.{js,jsx,ts,tsx,graphql,md,json}'",
     "prettier:check": "prettier --ignore-path .eslintignore --check '**/*.{js,jsx,ts,tsx,graphql,md,json}'",
     "prepack": "tsc && chmod +x dist/cli.js",
     "clean": "rm -Rf dist",
-    "test": "yarn lint && depcheck --ignores @types/jest,eslint_d,tslib && yarn run test:only --ci",
+    "test": "yarn lint && yarn run lint:deps && yarn run test:only --ci",
     "test:only": "jest -i",
     "version": "yarn prepack && ./scripts/update-docs.js && git add README.md",
     "watch": "mkdir -p dist && touch dist/cli.js && chmod +x dist/cli.js && tsc --watch"