From 736579a6eb6f3c5fbbae9d5c20e390fc607f8773 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Wed, 12 Aug 2026 03:58:57 -0700 Subject: [PATCH] Drop the stale note about arming the build trigger The warning dated from when .build-host was the release trigger's own setting and push was a second consumer of it. One setting now names one machine for all three commands, so there is nothing to keep separate -- and the advice was wrong regardless: OMARCHY_REPO_HOST is read by the same resolver, so it arms the trigger exactly as the file does. Only --host is per-invocation. Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 7 ++----- helpers/host-helpers.sh | 3 --- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index e3d0ded..ad2b051 100644 --- a/README.md +++ b/README.md @@ -213,11 +213,8 @@ need no secrets. The host comes from `--host`, `$OMARCHY_REPO_HOST`, then `.repo-host`. One machine both serves pkgs.omarchy.org and runs the scheduled builds, so the setting is named for the repository rather than for building, which happens -wherever you like. - -Note that `.repo-host` also arms the automatic build trigger in -`bin/omarchy-pkgs release`; pass `--host` or set `OMARCHY_REPO_HOST` to keep the -two separate. +wherever you like. The same setting tells `bin/omarchy-pkgs release` which host +to poke after a release push. Split packages are selected by their own names, not their pkgbase — pushing `nvidia-580xx-utils` does not carry `nvidia-580xx-dkms` along. Omit `--package` to diff --git a/helpers/host-helpers.sh b/helpers/host-helpers.sh index 96ce547..1d5fbe8 100644 --- a/helpers/host-helpers.sh +++ b/helpers/host-helpers.sh @@ -39,7 +39,4 @@ print_no_repo_host() { echo "" echo "Pass --host, set OMARCHY_REPO_HOST, or write the destination to:" echo " $BUILD_ROOT/.repo-host" - echo "" - echo "That file also arms the automatic build trigger in 'bin/omarchy-pkgs" - echo "release'. Use --host or OMARCHY_REPO_HOST to keep them separate." }