Skip to content

ci: route member builds to private Linux runners - #13

Merged
Quick104 merged 1 commit into
mainfrom
ci/private-linux-routing
Sep 30, 2026
Merged

Quick104 merged 1 commit into
mainfrom
ci/private-linux-routing

Conversation

@Quick104

@Quick104 Quick104 commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Problem

Related issue: Silo-Server/siloserver.org#55

Member PRs and main builds should use the private Linux runner pool.

Approach

Call the trusted reusable workflow on main. SILO_CI_MEMBERS selects member PRs for private routing; the controller independently verifies current organization membership and PR state before creating a disposable runner. Main builds use the same pool.

Validation

GOWORK=off go test ./..., GOWORK=off go vet ./..., GOWORK=off go build ./..., and actionlint passed. gofmt -l . produced no output. Reviewed run/attempt labels and the event/repository conditions against the controller admission rules.

Risks

Refresh SILO_CI_MEMBERS when organization membership changes. Private PR run 36660286463 passed in runner group 3; the runner registration and disposable VM were removed. Removed members fail live admission even if their routing entry is stale.

Checklist

  • I read and can explain the complete diff.
  • This pull request addresses one concern.

AI Disclosure

  • Harness: Codex desktop.
  • Tool(s): functions.exec with exec_command and apply_patch; unified-computer-use cua_repl.
  • Model(s): GPT-6, as reported by the harness; a more specific deployment identifier is unavailable.
  • Involvement: AI-assisted.
  • Adversarial review: examined caller-controlled inputs, stale PR commits, organization membership, workflow references and credentials. The controller checks live membership and binds runners to individual runs and attempts. Seventeen admission tests passed; the current PR passed on the private runner with live admission.

@kody-ai

kody-ai Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

  • Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
  • Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
  • Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
  • Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
  • API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
  • Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
  • Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
  • Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
  • Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
  • Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).
Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ❌

Access your configuration settings here.

@coderabbitai

coderabbitai Bot commented Sep 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 15 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 0c5cd2da-e787-4070-ab9c-76f2f784ed62

📥 Commits

Reviewing files that changed from the base of the PR and between 7c2c60b and f96fce4.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-30T02:33:39.631988Z f96fce4 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Quick104
Quick104 merged commit 5ba3ae3 into main Sep 30, 2026
3 checks passed
@Quick104
Quick104 deleted the ci/private-linux-routing branch September 30, 2026 02:35
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