ci: add Forseti advisory review workflow #220
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/forseti-review"
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?
fj was the only repo in the rasterstate org without the Forseti advisory review workflow, so its PRs (e.g. #219) received no automated review, which violates the every-repo-Forseti rule. This adds
.forgejo/workflows/forseti-review.yml, copied verbatim from fjord-platform.The workflow is language-agnostic. It runs the prebuilt
forseti-reviewimage over the PR diff fetched from the Forgejo API as data, with no source checkout and nothing built, so it works unchanged on a Rust repo. Kept identical to the source:pull_request_targettrigger with the same-repo-onlyifguard, so fork PRs never reach the provider keys.rasterstate-ops/forseti-review:stablejob container.FORSETI_ANTHROPIC_MODELcost knob and theANTHROPIC_API_KEY/OPENAI_API_KEYprovider env.Org secrets confirmed:
REGISTRY_USER,REGISTRY_TOKEN,ANTHROPIC_API_KEY, andOPENAI_API_KEYall exist as rasterstate org action secrets and resolve for fj (verified fj is owned byrasterstate; fjord-platform, same org, already runs this workflow with these secrets). fj's own repo secret list is Apple/macOS-only, so the workflow relies on org inheritance, which is in place.After this lands on
main, #219 needs a fresh push to trigger its first Forseti review. Do not close/reopen it (a close would cancel the in-flight Apple validation as collateral).Operator-merge, no self-merge.