fix(ci): force code reviews to run as pi-reviewer #6
No reviewers
Labels
No labels
code-review
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
norobo/webstream!6
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/code-review-pi-reviewer-identity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Code reviews triggered by this workflow were still posting as
pi-agent, not the dedicatedpi-revieweraccount. Root cause:paseo run --provider pi-reviewdoes not reliably apply the provider's configured command, so the launched agent falls back to the default Forgejo identity (FORGEJO_ACCESS_TOKEN->pi-agent). Api-agentreview onpi-agent's own PRs is limited toCOMMENT(Forgejo forbids approve/reject on your own PR), so blocking reviews never landed withREQUEST_CHANGES.Fix
Resolve the
FORGEJO_REVIEW_TOKENfrom the paseo container (the runner shell does not have it) and pass it as--env FORGEJO_ACCESS_TOKEN=...topaseo run. The launched agent's forgejo MCP server then authenticates aspi-reviewer.Verified: a
pi-review-provider agent launched with that env override has itsforgejo-mcpchild authenticate with the pi-reviewer token (confirmed via/api/v1/useridentity check).