From f9fe35ca99b71617694afffcc4e21d902d73da22 Mon Sep 17 00:00:00 2001 From: sohey Date: Tue, 25 Aug 2026 22:04:47 +0200 Subject: [PATCH] fix: use BaseRunnerGroup runner group instead of BaseRunner label MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit runs-on: BaseRunner requests a runner with that literal label, which doesn't exist — the actual self-hosted infra is organized as a runner group named BaseRunnerGroup. This left both jobs stuck in queued indefinitely. Confirmed fixed via a manual workflow_dispatch test run, which was picked up immediately by baserunnergroup. Co-Authored-By: Claude --- .github/workflows/base-std-docs-sync.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/base-std-docs-sync.yml b/.github/workflows/base-std-docs-sync.yml index 1604c5e2c..485da3aa8 100644 --- a/.github/workflows/base-std-docs-sync.yml +++ b/.github/workflows/base-std-docs-sync.yml @@ -35,7 +35,8 @@ jobs: # Keep every job in this workflow on BaseRunnerGroup. Besides providing a # consistent trusted execution environment, the downstream apply job uses # Base's internal LLM Gateway. - runs-on: BaseRunner + runs-on: + group: BaseRunnerGroup permissions: contents: read steps: @@ -122,7 +123,8 @@ jobs: if: github.event.repository.fork == false && vars.DISABLE_BASE_SYNC != 'true' # Run where Base's internal LLM Gateway is available. The corresponding # Base gateway integration documents BaseRunnerGroup as a requirement. - runs-on: BaseRunner + runs-on: + group: BaseRunnerGroup permissions: contents: write pull-requests: write