don't fail production builds because of eslint errors

we still need to check eslint somewhere in this process though. so I'm
creating the build-test-lint workflow.

ref: https://nextjs.org/docs/pages/api-reference/next-config-js/eslint

.github/workflows/build-test-lint.yml

@@ -0,0 +1,34 @@
+name: "Build Test Lint"
+run-name: Build Test Lint of ${{ github.ref_name }} by @${{ github.actor }}
+on:
+  push:
+    branches:
+    - main
+  pull_request:
+    branches:
+    - main
+  workflow_dispatch:
+    inputs:
+      debug_enabled:
+        type: boolean
+        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
+        required: false
+        default: false
+
+jobs:
+  build:
+    uses: scientist-softserv/actions/.github/workflows/[email protected]
+    secrets: inherit
+    with:
+      platforms: 'linux/amd64'
+      webTarget: web
+  test:
+    needs: build
+    uses: scientist-softserv/actions/.github/workflows/[email protected]
+    with:
+      cypress-container-name: cypress-tests
+  lint:
+    needs: build
+    uses: scientist-softserv/actions/.github/workflows/[email protected]
+    with:
+      rubocop_cmd: docker-compose run web -- bash -c 'yarn && yarn lint:all'

next.config.js

@@ -13,7 +13,10 @@ const nextConfig = {
   reactStrictMode: true,
   swcMinify: true,
   eslint: {
-    dirs: ['pages', 'utils'], // Only run ESLint on the 'pages' and 'utils' directories during production builds
+    // Warning: This allows production builds to successfully complete even if
+    // your project has ESLint errors.
+    // ref: https://nextjs.org/docs/pages/api-reference/next-config-js/eslint
+    ignoreDuringBuilds: true,
   },
   sentry: {
     // Use `hidden-source-map` rather than `source-map` as the Webpack `devtool`