From 79dcba1431fc21b7e0686fd3a12f938b2a679346 Mon Sep 17 00:00:00 2001 From: Renn F Date: Wed, 17 Jun 2026 01:15:43 +0200 Subject: [PATCH] feat(deploy): enable external-PR review in the registry compose too MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The build compose got ROBOCO_EXTERNAL_PR_ENABLED (default true) but the registry compose's orchestrator env was missed, so a pull-based deploy would have defaulted it off — inconsistent. Add the same external-PR block so both deploy paths behave identically. --- docker-compose.registry.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docker-compose.registry.yml b/docker-compose.registry.yml index d3982852..780f7a91 100644 --- a/docker-compose.registry.yml +++ b/docker-compose.registry.yml @@ -201,6 +201,13 @@ services: ROBOCO_ENVIRONMENT: production ROBOCO_CLAIM_STALE_SECONDS: "1800" ROBOCO_STALE_CLAIM_REAP_SECONDS: "1800" + # External-PR review (read-only: discover inbound external/fork PRs, post + # one change-request; never runs contributor code — the supersede stays + # CEO-triggered + human-confirm gated). Matches the build compose. + ROBOCO_EXTERNAL_PR_ENABLED: ${ROBOCO_EXTERNAL_PR_ENABLED:-true} + ROBOCO_EXTERNAL_PR_REQUIRE_HUMAN_CONFIRM: ${ROBOCO_EXTERNAL_PR_REQUIRE_HUMAN_CONFIRM:-true} + # ROBOCO_EXTERNAL_PR_POLL_INTERVAL_SECONDS: "300" + # ROBOCO_EXTERNAL_PR_AUTHOR_ALLOWLIST: '["corey"]' # empty = every external PR volumes: - /var/run/docker.sock:/var/run/docker.sock - ${CLAUDE_AUTH_DIR:-${HOME}/.claude}:/root/.claude