Runs on every pull request:
- ESLint and vue-tsc typecheck
- gitleaks secret scan over full history
- pnpm dependency audit (advisory)
- droast Dockerfile lint (skips until a Dockerfile exists)
- Snyk dependency and base image scan
- opencode AI code review posted as PR comment
The Gitea repo CV_Website/CV_Site_Nuxt checks out to a workspace that
already is the app root, so working-directory CV_Site_Nuxt resolved to
a doubled, non-existent path.
pnpm 9 treats the config-only pnpm-workspace.yaml (allowBuilds, no
packages field) as a workspace definition and fails with 'packages
field missing or empty'. Pin the same major version as local dev.
gitleaks is not published on Docker Hub, so the container image pull
failed with 'pull access denied'. Use ghcr.io/gitleaks/gitleaks and
pin v8.28.0 for reproducible scans.
The gitleaks container image ships no node binary, so node-based
actions like actions/checkout fail with exit code 127. Install the
gitleaks v8.28.0 binary in the standard node:22-bookworm image
instead.
Replace anthropic/claude-sonnet-4-5 with opencode/deepseek-v4-pro for
a large cost reduction while keeping thorough, high-effort reviews.
Documented cheaper fallback: deepseek-v4.1-flash(-free).
The snyk/snyk:node image is amd64-only and cannot start on an arm64
runner. Install the Snyk CLI through npm (supports linux/arm64) in
the multi-arch node:22-bookworm image instead.
The pnpm-workspace.yaml makes Snyk treat the project as a package
workspace; without --all-projects it aborts with SNYK-CLI-0000
(422 Unprocessable Entity).
Dockerfile linting is already covered by the droast job; the second
Snyk step now scans our own source for code vulnerabilities (XSS,
injection, unsafe patterns) instead of the base image.
- Snyk job disabled via 'if: false': free plan only has ~100 test
credits/month and the job runs 2 tests per PR push
- PR comment step no longer fails silently: curl prints the HTTP
status and response body, making token/URL errors visible
- model: opencode/deepseek-v4-pro#max (requires funds on the opencode
account; flash fallback documented in a comment)
- review prompt rewritten: SSR/hydration/reactivity pitfalls, Nuxt
server-route security, runtime config leaks, Go error handling,
concurrency and resource hygiene, frontend/backend contract checks
- strict output format with [BLOCKER]/[WARN]/[NIT] severities mapped
to the approve/request-changes verdict
Passing the PR diff as a command-line argument exceeded
MAX_ARG_STRLEN (128KiB per single argument; the diff was 190KB,
mostly pnpm-lock.yaml). The shell failed with E2BIG ('Argument list
too long') and the tee pipeline masked the failure, so the raw error
log got posted as a 'review' comment.
- exclude pnpm-lock.yaml from the review diff (pnpm audit covers deps)
- write the diff to .pr-review-diff.patch in the workspace; the agent
reads it with file tools
- redirect output instead of piping through tee and fail the job when
opencode fails, so errors are never posted as review comments
Noel
merged commit 34c9995939 into main2026-10-18 14:31:27 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
/var/run/act/workflow/3.sh: 4: opencode: Argument list too long
/var/run/act/workflow/3.sh: 5: opencode: Argument list too long
Passing the PR diff as a command-line argument exceeded MAX_ARG_STRLEN (128KiB per single argument; the diff was 190KB, mostly pnpm-lock.yaml). The shell failed with E2BIG ('Argument list too long') and the tee pipeline masked the failure, so the raw error log got posted as a 'review' comment. - exclude pnpm-lock.yaml from the review diff (pnpm audit covers deps) - write the diff to .pr-review-diff.patch in the workspace; the agent reads it with file tools - redirect output instead of piping through tee and fail the job when opencode fails, so errors are never posted as review comments