fix(ci): use opencode-go plan model for AI review
PR Check / Dockerfile lint (droast) (pull_request) Skipped
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 34s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 5s
PR Check / Dependency audit (pull_request) Successful in 8s
PR Check / AI code review (opencode) (pull_request) Failing after 13s

The 'opencode' provider prefix points at OpenCode Zen (pay-per-call,
no funds), which failed every review run with 'Insufficient account
funds'. The opencode-go $10 plan covers deepseek-v4-pro with high
and max variants - use opencode-go/deepseek-v4-pro#max.
This commit is contained in:
Noel Sabia committed 2026-10-18 16:53:16 +02:00
1 parent 34c9995939
commit 8b6bcb6d70
1 file changed
+6 -4
+6 -4
View File
@@ -204,14 +204,16 @@ jobs:
env: env:
OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }} OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }}
run: | run: |
# deepseek-v4-pro#max: flagship reasoning model at maximum thinking # opencode-go/deepseek-v4-pro#max: flagship reasoning model at
# budget. Requires funds on the opencode account. # maximum thinking budget - included in the opencode-go $10 plan
# Cheaper fallbacks: opencode/deepseek-v4.1-flash, or remove "#max". # (variants: high, max). NOTE the provider prefix must be
# "opencode-go", NOT "opencode" (Zen is a different, pay-per-call
# provider and fails with 'Insufficient account funds').
# Output is redirected (not piped through tee): if opencode fails, # Output is redirected (not piped through tee): if opencode fails,
# the job must fail here so the error log is never posted as a # the job must fail here so the error log is never posted as a
# "review" comment. # "review" comment.
opencode run \ opencode run \
--model opencode/deepseek-v4-pro#max \ --model opencode-go/deepseek-v4-pro#max \
"You are a principal engineer performing a rigorous code review on a "You are a principal engineer performing a rigorous code review on a
pull request. You have tool access: read repo files for context when pull request. You have tool access: read repo files for context when
the diff alone is ambiguous, but review ONLY code changed in this PR. the diff alone is ambiguous, but review ONLY code changed in this PR.