From 5d501f8ef96145b59311d8ec2a9ef4c8779040de Mon Sep 17 00:00:00 2001 From: Ryan Hughes Date: Thu, 27 Aug 2026 01:15:06 -0400 Subject: [PATCH] Stop treating a single shared chat as a misconfiguration MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reporting to BASECAMP_CHATBOT_URL is a working setup — the second variable exists only for those who want release traffic in its own chat. setup now states which chat receives reports instead of warning about the common case, and the README frames the split as optional rather than expected. --- README.md | 15 +++++++++------ bin/setup | 8 +++++--- 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index dcc648e..678d24b 100644 --- a/README.md +++ b/README.md @@ -776,17 +776,20 @@ runs when the version check queued work, so building nothing means the check and the builder disagree about what is out of date. It names the packages that were queued but not built, which is where to start looking. -Release traffic gets its own chat so it does not drown the repository chat -that the AUR/upstream sync workflows post to. Export the destination in -`/root/.omarchy/build-credentials`: +By default everything posts to `BASECAMP_CHATBOT_URL`, the same chat the +AUR/upstream sync workflows use — one variable, nothing extra to configure. + +If release traffic starts drowning that chat, give it its own: create a second +Basecamp chat, add a chatbot integration to it, and export its lines URL +alongside the existing one in `/root/.omarchy/build-credentials`: ```bash export OMARCHY_RELEASE_CHATBOT_URL="https://3.basecamp.com//integrations//buckets//chats//lines" ``` -Without it, release reports fall back to `BASECAMP_CHATBOT_URL`; with neither -set they are silently skipped. `bin/setup` reports which of the three cases -applies. +Release reports then go there while the sync workflows keep posting to +`BASECAMP_CHATBOT_URL`. With neither set, reports are silently skipped. +`bin/setup` reports which of the three cases applies. Check on all of it with `bin/repo timers` — schedule, each unit's last run and whether it succeeded, what is queued, whether a release is running right now, diff --git a/bin/setup b/bin/setup index 83cf5ec..5467be6 100755 --- a/bin/setup +++ b/bin/setup @@ -280,9 +280,11 @@ if [[ -f "$CREDENTIALS" ]]; then if grep -q 'OMARCHY_RELEASE_CHATBOT_URL' "$CREDENTIALS"; then print_success "Release reports go to the dedicated release chat" elif grep -q 'BASECAMP_CHATBOT_URL' "$CREDENTIALS"; then - print_warning "Release reports fall back to BASECAMP_CHATBOT_URL (the repository chat)" - echo " Export OMARCHY_RELEASE_CHATBOT_URL in $CREDENTIALS to send them" - echo " to their own chat instead." + # A working setup, not a problem: one chat receives everything. Splitting + # them is a preference, so this states the fact rather than nagging. + print_success "Release reports go to BASECAMP_CHATBOT_URL (shared with the sync workflows)" + echo " To give releases their own Basecamp chat, create one, add a chatbot" + echo " to it, and export its lines URL as OMARCHY_RELEASE_CHATBOT_URL here." else print_warning "No chatbot URL in $CREDENTIALS — build reports are disabled" echo " Export OMARCHY_RELEASE_CHATBOT_URL to receive start/publish/failure"