Release / release (push) Successful in 1m25s
On the Gitea runner, pnpm's content-addressable store ends up inside the workspace (.pnpm-store/) instead of the global cache location - format:check was scanning its content-addressable blobs as if they were source files, some of which happen to parse as JS/TS-like text and crash prettier's parser outright rather than just wasting time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
51 lines
685 B
Plaintext
51 lines
685 B
Plaintext
# dependencies
|
|
/node_modules
|
|
/.pnpm-store
|
|
/.pnp
|
|
.pnp.*
|
|
.yarn/*
|
|
!.yarn/patches
|
|
!.yarn/plugins
|
|
!.yarn/releases
|
|
!.yarn/versions
|
|
|
|
# testing
|
|
/coverage
|
|
|
|
# next.js
|
|
/.next/
|
|
/out/
|
|
|
|
# production
|
|
/build
|
|
|
|
# typescript
|
|
*.tsbuildinfo
|
|
next-env.d.ts
|
|
|
|
# debug
|
|
npm-debug.log*
|
|
yarn-debug.log*
|
|
yarn-error.log*
|
|
.pnpm-debug.log*
|
|
|
|
# vercel
|
|
.vercel
|
|
|
|
# Runtime data (created by `triggershell start` in whatever directory the config lives in)
|
|
.triggershell/
|
|
|
|
# Secrets loaded by `triggershell` via ${VAR} interpolation - never commit these
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
|
|
# Local config files a developer might create while testing against this repo
|
|
/triggershell.yml
|
|
|
|
# Editors / OS
|
|
.DS_Store
|
|
*.pem
|
|
.idea/
|
|
.vscode/
|