Lint

[Checkout] Cloning into '/var/lib/open-git/runner-work/7e1f08d9-6f0a-407a-993a-d8967cf8956d'...
[Checkout] Note: switching to '078edbb92a344d9e22adeed12bef323856e4c363'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 078edbb Update webhooks
[Install deps and run eslint] Preparing pnpm@9.15.9 for immediate activation...
[Install deps and run eslint] Scope: all 23 workspace projects
[Install deps and run eslint] Lockfile is up to date, resolution step is skipped
[Install deps and run eslint] Progress: resolved 1, reused 0, downloaded 0, added 0
[Install deps and run eslint] Packages: +1006
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 35, added 23
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 52, added 40
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 161, added 148
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 293, added 280
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 373, added 362
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 412, added 404
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 423, added 410
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 434, added 420
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 453, added 440
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 466, added 452
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 513, added 498
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 654, added 643
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 775, added 762
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 795, added 783
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 861, added 851
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 902, added 892
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 956, added 941
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 1006, added 1005
[Install deps and run eslint] Progress: resolved 1006, reused 0, downloaded 1006, added 1006, done
[Install deps and run eslint] .../node_modules/msw postinstall$ node -e "import('./config/scripts/postinstall.js').catch(() => void 0)"
.../sharp@0.34.5/node_modules/sharp install$ node install/check.js || npm run build
.../esbuild@0.27.3/node_modules/esbuild postinstall$ node install.js
.../esbuild@0.25.12/node_modules/esbuild postinstall$ node install.js
.../esbuild@0.18.20/node_modules/esbuild postinstall$ node install.js
[Install deps and run eslint] .../node_modules/msw postinstall: Done
[Install deps and run eslint] .../sharp@0.34.5/node_modules/sharp install: Done
[Install deps and run eslint] .../node_modules/core-js-pure postinstall$ node -e "try{require('./postinstall')}catch(e){}"
[Install deps and run eslint] .../esbuild@0.25.12/node_modules/esbuild postinstall: Done
.../esbuild@0.27.3/node_modules/esbuild postinstall: Done
[Install deps and run eslint] .../esbuild@0.18.20/node_modules/esbuild postinstall: Done
.../node_modules/core-js-pure postinstall: Done
[Install deps and run eslint] 
devDependencies:
+ @workspace/eslint-config 0.0.0 <- packages/eslint-config
+ @workspace/typescript-config 0.0.0 <- packages/typescript-config
+ prettier 3.8.1
+ prettier-plugin-tailwindcss 0.7.4
+ turbo 2.9.6
+ typescript 5.9.3
+ vitest 4.1.5

[Install deps and run eslint] Done in 20.7s using pnpm v9.15.9
[Install deps and run eslint] 
> open-git@0.0.1 lint /workspace
> turbo lint

[Install deps and run eslint] 
Attention:
Turborepo now collects completely anonymous telemetry regarding usage.
This information is used to shape the Turborepo roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://turborepo.dev/docs/telemetry

[Install deps and run eslint] 
   • Packages in scope: @opengit/cli, @opengit/runner, @opengit/sdk, @workspace/ci-runner-executor, @workspace/code-storage, @workspace/eslint-config, @workspace/git-graph, @workspace/git-indexing, @workspace/github-sync, @workspace/marketing, @workspace/typescript-config, @workspace/ui, @workspace/workflows, bot-example, campfire-gateway, community, git-gateway, git-worker, github-sync-worker, managed-runner, playground, web
   • Running lint in 22 packages
   • Remote caching disabled

[Install deps and run eslint] @workspace/code-storage:lint: cache miss, executing a76f76f4f843ebec
@workspace/git-graph:lint: cache miss, executing 787862d4ff705382
@workspace/ui:lint: cache miss, executing 5a9aeece04d44d3e
[Install deps and run eslint] @workspace/code-storage:lint: 
@workspace/code-storage:lint: > @workspace/code-storage@0.0.0 lint /workspace/packages/code-storage
@workspace/code-storage:lint: > eslint
@workspace/code-storage:lint: 
[Install deps and run eslint] @workspace/ui:lint: 
@workspace/ui:lint: > @workspace/ui@0.0.0 lint /workspace/packages/ui
@workspace/ui:lint: > eslint
@workspace/ui:lint: 
[Install deps and run eslint] @workspace/git-graph:lint: 
@workspace/git-graph:lint: > @workspace/git-graph@0.0.0 lint /workspace/packages/git-graph
@workspace/git-graph:lint: > eslint
@workspace/git-graph:lint: 
[Install deps and run eslint] @workspace/code-storage:lint: 
@workspace/code-storage:lint: /workspace/packages/code-storage/src/storage.ts
[Install deps and run eslint] @workspace/code-storage:lint:   121:50  warning  GIT_CACHE_MAX_BYTES is not listed as a dependency in turbo.json          turbo/no-undeclared-env-vars
@workspace/code-storage:lint:   123:46  warning  GIT_CACHE_IDLE_MS is not listed as a dependency in turbo.json            turbo/no-undeclared-env-vars
@workspace/code-storage:lint:   126:30  warning  GIT_CACHE_MIN_FREE_BYTES is not listed as a dependency in turbo.json     turbo/no-undeclared-env-vars
@workspace/code-storage:lint:   129:33  warning  GIT_CACHE_PRUNE_INTERVAL_MS is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
@workspace/code-storage:lint: 
@workspace/code-storage:lint: ✖ 4 problems (0 errors, 4 warnings)
@workspace/code-storage:lint: 
[Install deps and run eslint] @workspace/ui:lint: 
@workspace/ui:lint: /workspace/packages/ui/src/components/appearance-menu-section.tsx
@workspace/ui:lint:   44:19  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint: 
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint: 
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint: 
[Install deps and run eslint] @workspace/ui:lint: /workspace/packages/ui/src/components/appearance-menu-section.tsx:44:19
@workspace/ui:lint:   42 |   // next-themes resolves the active value only on the client; defer reading it
@workspace/ui:lint:   43 |   // until mounted to avoid a hydration mismatch on the highlighted cell.
@workspace/ui:lint: > 44 |   useEffect(() => setMounted(true), [])
@workspace/ui:lint:      |                   ^^^^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint:   45 |
@workspace/ui:lint:   46 |   const active = mounted ? theme : undefined
@workspace/ui:lint:   47 |   const activeIndex = THEME_OPTIONS.findIndex((option) => option.value === active)  react-hooks/set-state-in-effect
@workspace/ui:lint: 
@workspace/ui:lint: /workspace/packages/ui/src/components/nucleo-icons.tsx
@workspace/ui:lint:   120:14  warning  '_state' is defined but never used  @typescript-eslint/no-unused-vars
@workspace/ui:lint: 
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts
@workspace/ui:lint:    39:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint: 
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint: 
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint: 
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts:39:7
@workspace/ui:lint:   37 |   useEffect(() => {
@workspace/ui:lint:   38 |     if (!active) {
@workspace/ui:lint: > 39 |       setPhase(0);
@workspace/ui:lint:      |       ^^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint:   40 |       return;
@workspace/ui:lint:   41 |     }
@workspace/ui:lint:   42 |                                                  react-hooks/set-state-in-effect
@workspace/ui:lint:   127:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
@workspace/ui:lint: 
@workspace/ui:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
@workspace/ui:lint: * Update external systems with the latest state from React.
@workspace/ui:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
@workspace/ui:lint: 
@workspace/ui:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
@workspace/ui:lint: 
@workspace/ui:lint: /workspace/packages/ui/src/hooks/dotmatrix-hooks.ts:127:7
@workspace/ui:lint:   125 |       activeRef.current = false;
@workspace/ui:lint:   126 |       currentStepRef.current = idleStep;
@workspace/ui:lint: > 127 |       setStep(idleStep);
@workspace/ui:lint:       |       ^^^^^^^ Avoid calling setState() directly within an effect
@workspace/ui:lint:   128 |       return;
@workspace/ui:lint:   129 |     }
@workspace/ui:lint:   130 |  react-hooks/set-state-in-effect
@workspace/ui:lint: 
@workspace/ui:lint: ✖ 4 problems (0 errors, 4 warnings)
@workspace/ui:lint: 
[Install deps and run eslint] playground:lint: cache miss, executing 67c46cdb1a1f3e7f
[Install deps and run eslint] @workspace/marketing:lint: cache miss, executing 15b75b39c2ad4357
[Install deps and run eslint] @workspace/marketing:lint: 
@workspace/marketing:lint: > @workspace/marketing@0.0.0 lint /workspace/packages/marketing
@workspace/marketing:lint: > eslint
@workspace/marketing:lint: 
[Install deps and run eslint] playground:lint: 
playground:lint: > playground@0.0.1 lint /workspace/apps/playground
playground:lint: > eslint
playground:lint: 
[Install deps and run eslint] playground:lint: 
playground:lint: /workspace/apps/playground/components/theme-toggle.tsx
playground:lint:   11:19  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
playground:lint: 
playground:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
playground:lint: * Update external systems with the latest state from React.
playground:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
playground:lint: 
playground:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
playground:lint: 
playground:lint: /workspace/apps/playground/components/theme-toggle.tsx:11:19
playground:lint:    9 |   const { resolvedTheme, setTheme } = useTheme()
playground:lint:   10 |   const [mounted, setMounted] = useState(false)
playground:lint: > 11 |   useEffect(() => setMounted(true), [])
playground:lint:      |                   ^^^^^^^^^^ Avoid calling setState() directly within an effect
playground:lint:   12 |
playground:lint:   13 |   const isDark = mounted ? resolvedTheme === "dark" : true
playground:lint:   14 |  react-hooks/set-state-in-effect
playground:lint: 
playground:lint: ✖ 1 problem (0 errors, 1 warning)
playground:lint: 
[Install deps and run eslint] @workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx
@workspace/marketing:lint:   23:7  warning  'DEFAULT_CONFIG' is assigned a value but never used                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    @typescript-eslint/no-unused-vars
@workspace/marketing:lint:   92:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:92:3
@workspace/marketing:lint:   90 |   const logoAnchorXRef = useRef(logoAnchorX)
@workspace/marketing:lint:   91 |
@workspace/marketing:lint: > 92 |   configRef.current = config
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   93 |   themeRef.current = theme
@workspace/marketing:lint:   94 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:   95 |                             react-hooks/refs
@workspace/marketing:lint:   93:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:93:3
@workspace/marketing:lint:   91 |
@workspace/marketing:lint:   92 |   configRef.current = config
@workspace/marketing:lint: > 93 |   themeRef.current = theme
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   94 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:   95 |
@workspace/marketing:lint:   96 |   const packKey = (col: number, row: number) => col * 100000 + row        react-hooks/refs
@workspace/marketing:lint:   94:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/ascii-shader.tsx:94:3
@workspace/marketing:lint:   92 |   configRef.current = config
@workspace/marketing:lint:   93 |   themeRef.current = theme
@workspace/marketing:lint: > 94 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   95 |
@workspace/marketing:lint:   96 |   const packKey = (col: number, row: number) => col * 100000 + row
@workspace/marketing:lint:   97 |  react-hooks/refs
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx
@workspace/marketing:lint:   70:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:70:3
@workspace/marketing:lint:   68 |   const clipToLogoBoundsRef = useRef(clipToLogoBounds)
@workspace/marketing:lint:   69 |
@workspace/marketing:lint: > 70 |   configRef.current = config
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   71 |   svgScaleRef.current = svgScale
@workspace/marketing:lint:   72 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:   73 |   clipToLogoBoundsRef.current = clipToLogoBounds                   react-hooks/refs
@workspace/marketing:lint:   71:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:71:3
@workspace/marketing:lint:   69 |
@workspace/marketing:lint:   70 |   configRef.current = config
@workspace/marketing:lint: > 71 |   svgScaleRef.current = svgScale
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   72 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:   73 |   clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint:   74 |   themeRef.current = theme                                             react-hooks/refs
@workspace/marketing:lint:   72:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:72:3
@workspace/marketing:lint:   70 |   configRef.current = config
@workspace/marketing:lint:   71 |   svgScaleRef.current = svgScale
@workspace/marketing:lint: > 72 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   73 |   clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint:   74 |   themeRef.current = theme
@workspace/marketing:lint:   75 |   svgPathRef.current = svgPath           react-hooks/refs
@workspace/marketing:lint:   73:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:73:3
@workspace/marketing:lint:   71 |   svgScaleRef.current = svgScale
@workspace/marketing:lint:   72 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint: > 73 |   clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   74 |   themeRef.current = theme
@workspace/marketing:lint:   75 |   svgPathRef.current = svgPath
@workspace/marketing:lint:   76 |   svgWidthRef.current = svgWidth  react-hooks/refs
@workspace/marketing:lint:   74:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:74:3
@workspace/marketing:lint:   72 |   logoAnchorXRef.current = logoAnchorX
@workspace/marketing:lint:   73 |   clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint: > 74 |   themeRef.current = theme
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   75 |   svgPathRef.current = svgPath
@workspace/marketing:lint:   76 |   svgWidthRef.current = svgWidth
@workspace/marketing:lint:   77 |   svgHeightRef.current = svgHeight           react-hooks/refs
@workspace/marketing:lint:   75:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:75:3
@workspace/marketing:lint:   73 |   clipToLogoBoundsRef.current = clipToLogoBounds
@workspace/marketing:lint:   74 |   themeRef.current = theme
[Install deps and run eslint] @workspace/marketing:lint: > 75 |   svgPathRef.current = svgPath
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   76 |   svgWidthRef.current = svgWidth
@workspace/marketing:lint:   77 |   svgHeightRef.current = svgHeight
@workspace/marketing:lint:   78 |                                                react-hooks/refs
@workspace/marketing:lint:   76:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:76:3
@workspace/marketing:lint:   74 |   themeRef.current = theme
@workspace/marketing:lint:   75 |   svgPathRef.current = svgPath
@workspace/marketing:lint: > 76 |   svgWidthRef.current = svgWidth
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   77 |   svgHeightRef.current = svgHeight
@workspace/marketing:lint:   78 |
@workspace/marketing:lint:   79 |   const mouseXRef = useRef(-1000)                                                              react-hooks/refs
@workspace/marketing:lint:   77:3  warning  Error: Cannot access refs during render
@workspace/marketing:lint: 
@workspace/marketing:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
@workspace/marketing:lint: 
@workspace/marketing:lint: /workspace/packages/marketing/src/logo-shaders/lines-shader.tsx:77:3
@workspace/marketing:lint:   75 |   svgPathRef.current = svgPath
@workspace/marketing:lint:   76 |   svgWidthRef.current = svgWidth
@workspace/marketing:lint: > 77 |   svgHeightRef.current = svgHeight
@workspace/marketing:lint:      |   ^^^^^^^^^^^^^^^^^^^^ Cannot update ref during render
@workspace/marketing:lint:   78 |
@workspace/marketing:lint:   79 |   const mouseXRef = useRef(-1000)
@workspace/marketing:lint:   80 |   const mouseYRef = useRef(-1000)                                                      react-hooks/refs
@workspace/marketing:lint: 
@workspace/marketing:lint: ✖ 12 problems (0 errors, 12 warnings)
@workspace/marketing:lint: 
[Install deps and run eslint] community:lint: cache miss, executing 7130b721ac0d39ae
web:lint: cache miss, executing 1bdbef7ba9f821a7
[Install deps and run eslint] community:lint: 
community:lint: > community@0.0.1 lint /workspace/apps/community
community:lint: > eslint
community:lint: 
[Install deps and run eslint] web:lint: 
web:lint: > web@0.0.1 lint /workspace/apps/web
web:lint: > eslint
web:lint: 
[Install deps and run eslint] community:lint: 
community:lint: /workspace/apps/community/components/post-header.tsx
community:lint:   10:11  warning  Error: Cannot create components during render
community:lint: 
community:lint: Components created during render will reset their state each time they are created. Declare components outside of render.
community:lint: 
community:lint: /workspace/apps/community/components/post-header.tsx:10:11
community:lint:    8 |   }
community:lint:    9 |
community:lint: > 10 |   return <Skeleton />
community:lint:      |           ^^^^^^^^ This component is created during render
community:lint:   11 | }
community:lint:   12 |
community:lint: 
community:lint: /workspace/apps/community/components/post-header.tsx:4:20
community:lint:   2 |
community:lint:   3 | export function PostHeader({ header }: { header?: string }) {
community:lint: > 4 |   const Skeleton = getPostHeaderSkeleton(header)
community:lint:     |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The component is created during render here
community:lint:   5 |
community:lint:   6 |   if (!Skeleton) {
community:lint:   7 |     return null  react-hooks/static-components
community:lint: 
community:lint: /workspace/apps/community/lib/posts.ts
community:lint:   82:24  warning  '_content' is assigned a value but never used  @typescript-eslint/no-unused-vars
community:lint:   82:39  warning  '_toc' is assigned a value but never used      @typescript-eslint/no-unused-vars
community:lint: 
community:lint: ✖ 3 problems (0 errors, 3 warnings)
community:lint: 
[Install deps and run eslint] web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/pulls/new/create-pull-request-form.tsx
web:lint:   197:9  warning  The 'allSourceBranches' logical expression could make the dependencies of useMemo Hook (at line 203) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'allSourceBranches' in its own useMemo() Hook                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          react-hooks/exhaustive-deps
web:lint:   221:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/pulls/new/create-pull-request-form.tsx:221:7
web:lint:   219 |   useEffect(() => {
web:lint:   220 |     if (sourceBranches.length === 0) {
web:lint: > 221 |       setSelectedSourceBranch("")
web:lint:       |       ^^^^^^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   222 |       return
web:lint:   223 |     }
web:lint:   224 |     setSelectedSourceBranch((current) =>  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/pulls/new/new-pull-request-modal.tsx
web:lint:   42:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/pulls/new/new-pull-request-modal.tsx:42:7
web:lint:   40 |   useEffect(() => {
web:lint:   41 |     if (!isNewPrRoute) {
web:lint: > 42 |       setOpen(false)
web:lint:      |       ^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   43 |     }
web:lint:   44 |   }, [isNewPrRoute])
web:lint:   45 |  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/repository-file.tsx
web:lint:   174:9  warning  Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
web:lint: 
web:lint: /workspace/apps/web/app/[username]/[repository]/settings/integrations/page.tsx
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint:   57:13  warning  Do not use an `<a>` element to navigate to `/integrations/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages  @next/next/no-html-link-for-pages
web:lint: 
web:lint: /workspace/apps/web/app/home/autopilot-trigger-demo.tsx
web:lint:   330:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/home/autopilot-trigger-demo.tsx:330:7
web:lint:   328 |   useEffect(() => {
web:lint:   329 |     if (reduced) {
web:lint: > 330 |       setCiTick(4)
web:lint:       |       ^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   331 |       setManualTick(0)
web:lint:   332 |       return
web:lint:   333 |     }  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/connections.tsx
web:lint:    82:10  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/connections.tsx:82:10
web:lint:   80 |
web:lint:   81 |   useEffect(() => {
web:lint: > 82 |     void refreshAccounts().catch((error) => {
web:lint:      |          ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   83 |       setLoaded(true)
web:lint:   84 |       setStatus({ kind: "error", message: getErrorMessage(error) })
web:lint:   85 |     })  react-hooks/set-state-in-effect
web:lint:   208:10  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/connections.tsx:208:10
web:lint:   206 |
web:lint:   207 |   useEffect(() => {
web:lint: > 208 |     void refresh().catch(() => {
web:lint:       |          ^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   209 |       setLoaded(true)
web:lint:   210 |     })
web:lint:   211 |   }, [])                                                                          react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/installed-bots.tsx
web:lint:   21:5  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/installed-bots.tsx:21:5
web:lint:   19 |
web:lint:   20 |   useEffect(() => {
web:lint: > 21 |     setLoaded(false)
web:lint:      |     ^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   22 |     void listMyInstallationsAction()
web:lint:   23 |       .then(setInstalls)
web:lint:   24 |       .finally(() => setLoaded(true))  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/payments.tsx
web:lint:   82:5  warning  Error: This value cannot be modified
web:lint: 
web:lint: Modifying a variable defined outside a component or hook is not allowed. Consider using an effect.
web:lint: 
web:lint: /workspace/apps/web/app/settings/account/account-settings-sections/payments.tsx:82:5
web:lint:   80 |       throw new Error("No checkout URL returned.")
web:lint:   81 |     }
web:lint: > 82 |     window.location.href = result.url
web:lint:      |     ^^^^^^^^^^^^^^^ value cannot be modified
web:lint:   83 |   }
web:lint:   84 |
web:lint:   85 |   const topUp = (amountCents: number) =>  react-hooks/immutability
web:lint: 
web:lint: /workspace/apps/web/app/settings/organizations/[slug]/developer/bot-forms.tsx
web:lint:   515:5  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/app/settings/organizations/[slug]/developer/bot-forms.tsx:515:5
web:lint:   513 |   useEffect(() => {
web:lint:   514 |     const app = oauthApps.find((item) => item.id === attachedId)
web:lint: > 515 |     setAttachedRedirects((app?.redirectUris ?? []).join("\n"))
web:lint:       |     ^^^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   516 |   }, [attachedId, oauthApps])
web:lint:   517 |
web:lint:   518 |   return (  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/app/settings/organizations/[slug]/developer/oauth-forms.tsx
web:lint:   166:17  warning  `'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`  react/no-unescaped-entities
web:lint: 
web:lint: /workspace/apps/web/components/github-import-modal.tsx
web:lint:   36:15  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/components/github-import-modal.tsx:36:15
web:lint:   34 |   const [mounted, setMounted] = useState(open)
web:lint:   35 |   useEffect(() => {
web:lint: > 36 |     if (open) setMounted(true)
web:lint:      |               ^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   37 |   }, [open])
web:lint:   38 |
web:lint:   39 |   const close = () => {  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/components/new-repository-modal.tsx
web:lint:   59:15  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/components/new-repository-modal.tsx:59:15
web:lint:   57 |   const [mounted, setMounted] = useState(open)
web:lint:   58 |   useEffect(() => {
web:lint: > 59 |     if (open) setMounted(true)
web:lint:      |               ^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   60 |   }, [open])
web:lint:   61 |
web:lint:   62 |   const close = () => {  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/components/sidebar-app-frame.tsx
web:lint:   83:5  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/components/sidebar-app-frame.tsx:83:5
web:lint:   81 |       return
web:lint:   82 |     }
web:lint: > 83 |     setPanelOverride((current) =>
web:lint:      |     ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   84 |       current?.isOpen ? { ...current, isOpen: false } : current
web:lint:   85 |     )
web:lint:   86 |   }, [pathname])  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/components/viewer-context.tsx
web:lint:   70:7  warning  Error: Calling setState synchronously within an effect can trigger cascading renders
web:lint: 
web:lint: Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
web:lint: * Update external systems with the latest state from React.
web:lint: * Subscribe for updates from some external system, calling setState in a callback function when external state changes.
web:lint: 
web:lint: Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
web:lint: 
web:lint: /workspace/apps/web/components/viewer-context.tsx:70:7
web:lint:   68 |   useEffect(() => {
web:lint:   69 |     if (!userId) {
web:lint: > 70 |       setProfileState(null)
web:lint:      |       ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
web:lint:   71 |       return
web:lint:   72 |     }
web:lint:   73 |  react-hooks/set-state-in-effect
web:lint: 
web:lint: /workspace/apps/web/components/workbench-tabs/workbench-tab-bar.tsx
web:lint:   307:21  warning  Error: Cannot access refs during render
web:lint: 
web:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
web:lint: 
web:lint: /workspace/apps/web/components/workbench-tabs/workbench-tab-bar.tsx:307:21
web:lint:   305 |   const loading = !hydrated
web:lint:   306 |
web:lint: > 307 |   const newTabIds = tabsInitialized.current
web:lint:       |                     ^^^^^^^^^^^^^^^^^^^^^^^ Cannot access ref value during render
web:lint:   308 |     ? new Set(
web:lint:   309 |         tabs.filter((tab) => !seenTabIds.current.has(tab.id)).map((t) => t.id)
web:lint:   310 |       )                                      react-hooks/refs
web:lint:   309:21  warning  Error: Cannot access refs during render
web:lint: 
web:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
web:lint: 
web:lint: /workspace/apps/web/components/workbench-tabs/workbench-tab-bar.tsx:309:21
web:lint:   307 |   const newTabIds = tabsInitialized.current
web:lint:   308 |     ? new Set(
web:lint: > 309 |         tabs.filter((tab) => !seenTabIds.current.has(tab.id)).map((t) => t.id)
web:lint:       |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Passing a ref to a function may read its value during render
web:lint:   310 |       )
web:lint:   311 |     : new Set<string>()
web:lint:   312 |  react-hooks/refs
web:lint:   469:3   warning  Error: Cannot access refs during render
web:lint: 
web:lint: React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).
web:lint: 
web:lint: /workspace/apps/web/components/workbench-tabs/workbench-tab-bar.tsx:469:3
web:lint:   467 |   const [closing, setClosing] = useState(false)
web:lint:   468 |   const onCloseRef = useRef(onClose)
web:lint: > 469 |   onCloseRef.current = onClose
web:lint:       |   ^^^^^^^^^^^^^^^^^^ Cannot update ref during render
web:lint:   470 |   useEffect(() => {
web:lint:   471 |     if (!closing) return
web:lint:   472 |     const timer = setTimeout(() => onCloseRef.current(), 160)                   react-hooks/refs
web:lint: 
web:lint: /workspace/apps/web/db/bots.ts
web:lint:   5:3  warning  'botInstallationRepositories' is defined but never used  @typescript-eslint/no-unused-vars
web:lint: 
web:lint: /workspace/apps/web/db/pr-autopilot.ts
web:lint:   622:5  warning  AUTOPILOT_CHECK_SETTLE_TIMEOUT_MS is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
web:lint: 
web:lint: /workspace/apps/web/db/repositories.ts
web:lint:   305:3  warning  'targetRepository' is defined but never used  @typescript-eslint/no-unused-vars
web:lint: 
web:lint: /workspace/apps/web/db/repository-index-fork.test.ts
web:lint:   4:25  warning  '_query' is defined but never used  @typescript-eslint/no-unused-vars
web:lint: 
web:lint: /workspace/apps/web/db/repository-index.ts
web:lint:   1:25  warning  'inArray' is defined but never used  @typescript-eslint/no-unused-vars
web:lint: 
web:lint: /workspace/apps/web/lib/bots/verification-shared.ts
web:lint:   10:20  warning  OPEN_GIT_STAFF_EMAILS is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
web:lint: 
web:lint: /workspace/apps/web/scripts/freestyle-ci-smoke.ts
web:lint:   48:24  warning  Unnecessary escape character: \$                                    no-useless-escape
web:lint:   48:44  warning  Unnecessary escape character: \$                                    no-useless-escape
web:lint:   91:26  warning  CI_SMOKE_SLEEP_SECONDS is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
web:lint: 
web:lint: /workspace/apps/web/scripts/seed-commit-graph.ts
web:lint:   69:31  warning  COMMIT_GRAPH_OWNER is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
web:lint: 
web:lint: /workspace/apps/web/scripts/seed-oauth-staff.ts
web:lint:   11:21  warning  OPEN_GIT_TRIPWIRE_REDIRECT_URI is not listed as a dependency in turbo.json  turbo/no-undeclared-env-vars
web:lint:   12:14  warning  OPEN_GIT_TRIPWIRE_CLIENT_NAME is not listed as a dependency in turbo.json   turbo/no-undeclared-env-vars
web:lint: 
web:lint: ✖ 41 problems (0 errors, 41 warnings)
web:lint: 
[Install deps and run eslint] 
 Tasks:    7 successful, 7 total
Cached:    0 cached, 7 total
  Time:    55.396s