From 33d0fc685e09bdeb9bd1c43956886b87b4b9d617 Mon Sep 17 00:00:00 2001 From: John Date: Wed, 14 Jan 2026 08:20:15 +0000 Subject: [PATCH] #451 clarify addBrancherServer usage --- docs/hypernode-platform/tools/hypernode-brancher.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/hypernode-platform/tools/hypernode-brancher.md b/docs/hypernode-platform/tools/hypernode-brancher.md index 52d35bf9..e02f9169 100644 --- a/docs/hypernode-platform/tools/hypernode-brancher.md +++ b/docs/hypernode-platform/tools/hypernode-brancher.md @@ -157,6 +157,7 @@ $testStage = $configuration->addStage('test', 'example.com'); // We use an automatically created Brancher node based on the parent for the 'test' stage. // In your testing pipeline, you can simply use the 'test' stage to push changes to the Brancher server, // and run your tests. Cancel it when your tests fail or after your tests pass to incur minimal costs. +// 'example' is the name of the parent hypernode, which will be cloned to create the brancher, without the '.hypernode.io'. $testStage->addBrancherServer('example') ->setLabels(['stage=test']) ->setSettings(['clear_services' => ['cron', 'supervisor']);