Skip to content

ci: move onto the seidroid review workflow, retire ai-review - #89

Closed
bdchatham wants to merge 1 commit into
mainfrom
chore/remove-old-ai-review
Closed

bdchatham wants to merge 1 commit into
mainfrom
chore/remove-old-ai-review

Conversation

@bdchatham

Copy link
Copy Markdown

Summary

This PR replaces the old AI review with seidroid. That is the same move sei-chain (#4372), sei-load (#92), sei-internal-skills (#416) and platform (#1652) made.

  • Removed: .github/workflows/ai-review.yml, the caller of the old three-pass review in uci (ai-review.yml).

  • Added: .github/workflows/seidroid.yml. It calls uci seidroid-review.yml at v0.0.26 (0dc48cf) with the same triggers and jobs as sei-chain: review, close (anchored) and reclaim on close.

  • Why both cannot stay: uci says seidroid-review replaces ai-review. If both run, every PR gets two reviews. A comment with @seidroid review and more text also starts the old review path.

  • What stays: ai-assist.yml (the @seidroid assistant) and every other workflow.

  • Not set: approve-on-success. The repo owners can turn on bot approval on a clean review if they want it.

Before merge: a repo admin must add the repository secret OMNIGENT_MACHINE_CLIENT_SECRET (the seidroid machine credential, the same as in sei-chain). This repo does not have it, so without it every seidroid review fails. The GitHub App secrets PLATFORM_CODE_AGENT_APP_ID and PLATFORM_CODE_AGENT_APP_PK are already available.

How to use it

To ask for a review, post a comment whose whole body is @seidroid review. The assistant answers any other comment that mentions @seidroid.

Verification

  • actionlint passes on seidroid.yml.
  • No branch protection rule or ruleset on the default branch requires the AI Review check. seidroid also publishes an AI Review check run by default.

🤖 Generated with Claude Code

Replace the uci ai-review.yml caller with a seidroid.yml caller of uci
seidroid-review.yml at v0.0.26, the same wiring sei-chain uses. uci says
seidroid-review replaces ai-review and the two must not run side by side.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Oct 1, 2026, 8:25 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@cursor

cursor Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
CI workflow swap only; no application code changes, though reviews fail until OMNIGENT_MACHINE_CLIENT_SECRET is configured.

Overview
Retires automatic uci ai-review and wires PR reviews through seidroid instead, matching the pattern used in other sei-protocol repos so PRs are not double-reviewed.

The deleted ai-review.yml was the reusable caller for uci’s old three-pass review (with Cursor disabled). The new seidroid.yml delegates to uci seidroid-review.yml @ v0.0.26 with three jobs: run review on PR lifecycle events or an exact @seidroid review mention (excluding close), tear down via a top-level @seidroid review close comment (startsWith so quoted commands do not misfire), and reclaim the session when the PR closes.

Reviews are gated to sei-protocol/sei-core and need OMNIGENT_MACHINE_CLIENT_SECRET plus the existing platform GitHub App secrets; approve-on-success is not enabled here.

Reviewed by Cursor Bugbot for commit 420deac. Bugbot is set up for automated code reviews on this repo. Configure here.

@bdchatham

Copy link
Copy Markdown
Author

Closing this: it is out of scope. We remove the old AI review only from the core packages that already run seidroid, and those have no ai-review.yml left. This repository does not run seidroid, so it keeps its current review.

@bdchatham bdchatham closed this Oct 1, 2026
@bdchatham
bdchatham deleted the chore/remove-old-ai-review branch October 1, 2026 21:13

This branch was successfully deployed

1 active deployment
staging — 420deacd Deployed Oct 1, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant