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

Merged
jwilger merged 2 commits from issue-43-forgejo-ci-review-action into main 2026-05-03 22:34:16 -07:00
Owner

Summary

  • Replace the legacy local-review Forgejo action with a gateway dispatcher for POST /reviews/ci.
  • Default PR metadata from Forgejo/GitHub-compatible Actions context while keeping explicit overrides.
  • Document gated workflow usage and add a static action contract test.

Verification

  • nix develop -c cargo fmt --all -- --check
  • nix develop -c cargo nextest run -p ar-gateway --no-tests=pass

Closes #43

## Summary - Replace the legacy local-review Forgejo action with a gateway dispatcher for `POST /reviews/ci`. - Default PR metadata from Forgejo/GitHub-compatible Actions context while keeping explicit overrides. - Document gated workflow usage and add a static action contract test. ## Verification - `nix develop -c cargo fmt --all -- --check` - `nix develop -c cargo nextest run -p ar-gateway --no-tests=pass` Closes #43
feat(actions): add CI review gateway action
Some checks failed
auto_review auto_review: no findings
CI / Nix flake check (pull_request) Failing after 48s
3a052dfca0
auto-review approved these changes 2026-05-03 22:20:26 -07:00
Dismissed
auto-review left a comment

This PR replaces the legacy local-review Forgejo action with a new gateway dispatcher for CI reviews, updating documentation and adding a static action contract test. The changes appear well-structured and safe to merge, but ensure users are informed about the new gateway requirements.

Walkthrough

  • New Rule File: A new rule file .kilo/rules/branch-first.md was added, which advises creating a dedicated PR branch before starting implementation work. This should be documented for clarity.
  • Changelog Update: The changelog was updated to reflect the new CI review endpoint feature, closing issue #43.
  • Test Addition: A comprehensive test forgejo_action_posts_ci_review_to_gateway was added to ensure the action contract is met, checking for required inputs and correct endpoint usage.
  • Documentation Update: The README and operations documentation were updated to reflect the new action usage, emphasizing the need for a running ar-gateway.
  • Action Configuration: The action.yml file was simplified to remove legacy inputs and focus on the new gateway-based review process.
This PR replaces the legacy local-review Forgejo action with a new gateway dispatcher for CI reviews, updating documentation and adding a static action contract test. The changes appear well-structured and safe to merge, but ensure users are informed about the new gateway requirements. ## Walkthrough - **New Rule File**: A new rule file `.kilo/rules/branch-first.md` was added, which advises creating a dedicated PR branch before starting implementation work. This should be documented for clarity. - **Changelog Update**: The changelog was updated to reflect the new CI review endpoint feature, closing issue #43. - **Test Addition**: A comprehensive test `forgejo_action_posts_ci_review_to_gateway` was added to ensure the action contract is met, checking for required inputs and correct endpoint usage. - **Documentation Update**: The README and operations documentation were updated to reflect the new action usage, emphasizing the need for a running `ar-gateway`. - **Action Configuration**: The `action.yml` file was simplified to remove legacy inputs and focus on the new gateway-based review process.
fix(ci): include Forgejo action contract asset
All checks were successful
auto_review auto_review: no findings
CI / Nix flake check (pull_request) Successful in 2m31s
a75bb150c5
jwilger dismissed auto-review's review 2026-05-03 22:29:36 -07:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

auto-review left a comment

This PR replaces the legacy local-review Forgejo action with a new gateway dispatcher for CI reviews, updating documentation and adding a contract test. The changes appear well-structured and safe to merge, with clear documentation and test coverage.

Walkthrough

  • .kilo/rules/branch-first.md: A new rule file is added, but it's not clear how it's integrated into the existing system.
  • CHANGELOG.md: Updated to reflect the new feature, providing clear context for the changes.
  • crates/ar-gateway/tests/forgejo_action_contract.rs: A comprehensive test is added to ensure the action.yml file meets the expected contract.
  • deploy/forgejo-action/README.md: Updated to describe the new action usage, emphasizing the need for a gateway setup.
  • deploy/forgejo-action/action.yml: Simplified to focus on dispatching to the gateway, removing legacy inputs.
  • docs/OPERATIONS.md: Updated to reflect the new action usage, ensuring users understand the new workflow.
  • flake.nix: Includes the action.yml in the deploy assets, ensuring it's part of the build process.
This PR replaces the legacy local-review Forgejo action with a new gateway dispatcher for CI reviews, updating documentation and adding a contract test. The changes appear well-structured and safe to merge, with clear documentation and test coverage. ## Walkthrough - **.kilo/rules/branch-first.md**: A new rule file is added, but it's not clear how it's integrated into the existing system. - **CHANGELOG.md**: Updated to reflect the new feature, providing clear context for the changes. - **crates/ar-gateway/tests/forgejo_action_contract.rs**: A comprehensive test is added to ensure the action.yml file meets the expected contract. - **deploy/forgejo-action/README.md**: Updated to describe the new action usage, emphasizing the need for a gateway setup. - **deploy/forgejo-action/action.yml**: Simplified to focus on dispatching to the gateway, removing legacy inputs. - **docs/OPERATIONS.md**: Updated to reflect the new action usage, ensuring users understand the new workflow. - **flake.nix**: Includes the action.yml in the deploy assets, ensuring it's part of the build process.
jwilger referenced this pull request from a commit 2026-05-05 12:18:07 -07:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Slipstream/auto_review!68
No description provided.