Add Forgejo workflow action for CI-triggered reviews #43

New issue

Closed

opened 2026-05-02 19:41:17 -07:00 by jwilger · 0 comments

jwilger commented

2026-05-02 19:41:17 -07:00

Owner

Problem

After #42 adds a CI-triggered gateway endpoint, repositories need a small workflow-facing wrapper that calls it only after their selected prerequisite CI jobs have passed. The auto_review repository should also wire that wrapper into its own Forgejo CI so the review path is exercised by the project workflow, not just documented as an external example.

Direction

Ship an auto_review Forgejo action or tiny CLI/script suitable for use in a workflow job. The action should not perform the review locally; it should authenticate to the gateway and request review dispatch for the current PR head.

Also add the review job to this repository's Forgejo Actions CI workflow after the prerequisite checks, using the new action/script rather than leaving it as a documentation-only example.

Acceptance

Provide a documented workflow step/action that calls the #42 gateway endpoint.
Inputs/env include gateway URL, action token, owner/repo, PR number, and head SHA, defaulting from Forgejo Actions environment where possible.
The action fails clearly when required PR context is missing, when invoked outside a PR, or when the gateway rejects the request.
Example workflow shows auto_review running after needs: [fmt, clippy, test] or equivalent project checks.
Add an auto_review review job to this repository's Forgejo CI workflow, gated behind the existing prerequisite CI jobs and using the new action/script.
No linter execution is introduced in the action.

Dependencies

Blocked by: #42.

## Problem After #42 adds a CI-triggered gateway endpoint, repositories need a small workflow-facing wrapper that calls it only after their selected prerequisite CI jobs have passed. The auto_review repository should also wire that wrapper into its own Forgejo CI so the review path is exercised by the project workflow, not just documented as an external example. ## Direction Ship an auto_review Forgejo action or tiny CLI/script suitable for use in a workflow job. The action should not perform the review locally; it should authenticate to the gateway and request review dispatch for the current PR head. Also add the review job to this repository's Forgejo Actions CI workflow after the prerequisite checks, using the new action/script rather than leaving it as a documentation-only example. ## Acceptance - Provide a documented workflow step/action that calls the #42 gateway endpoint. - Inputs/env include gateway URL, action token, owner/repo, PR number, and head SHA, defaulting from Forgejo Actions environment where possible. - The action fails clearly when required PR context is missing, when invoked outside a PR, or when the gateway rejects the request. - Example workflow shows `auto_review` running after `needs: [fmt, clippy, test]` or equivalent project checks. - Add an `auto_review` review job to this repository's Forgejo CI workflow, gated behind the existing prerequisite CI jobs and using the new action/script. - No linter execution is introduced in the action. ## Dependencies Blocked by: #42.

jwilger referenced this issue

2026-05-02 19:41:24 -07:00

Stop PR webhooks from automatically dispatching semantic reviews #44

jwilger referenced this issue

2026-05-02 19:41:32 -07:00

Remove bundled linter execution from the review pipeline #45

jwilger referenced this issue from a pull request that will close it,

2026-05-03 22:20:15 -07:00

feat(actions): add CI review gateway action #68

jwilger closed this issue

2026-05-03 22:34:16 -07:00

jwilger referenced this issue from a commit