docs(pr-agent): record the first successful review
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m10s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 8s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s

The key is wired into the live server .env; glm-5.3-flash returned OK and /review on PR #28 posted a PR Reviewer Guide.
This commit is contained in:
Noel Sabia committed 2026-10-30 21:28:05 +01:00
1 parent a43134ad83
commit 636a65dd05
3 files changed
+15 -16

No files matched your search

+9 -8
View File
@@ -89,21 +89,22 @@ provider rejects the request before it reaches the model.
`server0`. The repository contains the compose file and an example env
file, never the token or webhook secret.
# Evidence
* 2026-10-30: a direct `glm-5.3-flash` call through the handler returned
`OK`, and `/review` on PR #28 posted a PR Reviewer Guide through the Gitea
comment API. The key is set only in the server-side `.env`.
# Not verified
* The OpenCode Go API key was not present when this was committed, so no
model call has completed. A dummy-key call now reaches the provider's
authentication check instead of failing on the missing session header,
so the remaining blocker is the credential. The first PR after the key is
set is the real verification.
* Whether `glm-5.3-flash` handles PR-Agent's structured review output well
enough. `glm-5.3` is configured as the fallback.
* Whether the model finds the same class of issues as the opencode prompt on
larger diffs. The first review found none; `glm-5.3` remains the fallback.
* Whether two gunicorn workers and the 1 GB memory limit hold under
concurrent reviews. The host has roughly 2.5 GB available with Gitea and
its runner idle.
* Whether the default review prompt is specific enough for this repository.
A `.pr_agent.toml` with project instructions is deliberately absent until
the first real review shows what it misses.
a real review shows what it misses.
# Revisit when
+2 -1
View File
@@ -5,7 +5,8 @@
* **Fix**: `pnpm-lock.yaml` - merging `main` left the lockfile at `@nuxt/icon` 2.6.0 while `package.json` asked for 2.6.2, so `pnpm install --frozen-lockfile` aborted in CI. The lockfile now resolves 2.6.2.
* **Fix**: `pnpm-workspace.yaml` - `seroval` 1.6.9 was the two moderate audit findings (GHSA-f86p-h4j2-7qgj, GHSA-9wx9-5pv9-3349). The patched 1.6.11 is forced through `overrides`; the blocking audit now reports only two low-severity advisories and passes the moderate gate.
* **Fix**: PR-Agent model routing - OpenCode Go rejects requests without `x-opencode-session`; `LITELLM__EXTRA_HEADERS` now supplies it, and the fallback keeps the `openai/` prefix. Auto commands are `/describe` and `/review`; `/improve` is on demand. A dummy-key call reaches the provider's auth check instead of failing on the missing header.
* **State**: the OpenCode Go API key is still unset, so no real review has run. The next step is the credential, then a `/review` comment on PR #28.
* **Evidence**: the key was wired into the live `.env`; a direct `glm-5.3-flash` call returned `OK`, and `/review` on PR #28 posted a PR Reviewer Guide (no findings). The failed-review comment was removed.
* **State**: the key is set only in the server-side `.env`; the first `/review` posted on PR #28 with no findings.
## 2026-10-30 (PR-Agent replaces the opencode review job)