chore: fleet automation moves to bitbaum/fleet; this repo is the environment again - #56
Merged
Merged
Conversation
…ronment again A repo holding a .bashrc was the wrong place for the machinery gating thirty other repos: three sessions and the owner collided here in one week, and every fleet change looked like an environment change. The audits, templates, registry and sweep now live in bitbaum/fleet (layout unchanged, all six test suites green there, secrets set, CI green). Nothing breaks for callers: - auto-merge-sweep.yml stays as a FORWARDING SHIM — the 16 repos calling it as a reusable workflow keep working; the shim maps the historic ref 'master' to fleet's 'main' and holds no logic. - SHARED.md stays as a pointer, because a decade of docs and habits say to check it here. The registry is maintained only in fleet. - This repo's own auto-merge now calls fleet's sweep like every other repo. CI slims to what this repo now is: shell syntax plus an install.sh dangling-symlink check. CLAUDE.md and README describe the environment repo; the global standards' pointers now name fleet/SHARED.md and fleet/templates/ci. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AZCNYHwjEeqxNpYCUk6Yna
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Answers "why is the registry in dotfiles?" the only correct way: it shouldn't be, and now it isn't.
What moved (to bitbaum/fleet)
SHARED.md,scripts/{ci,fleet,audit},templates/ci, and the five fleet workflows (the reusable auto-merge sweep + the four scheduled audits). Layout unchanged, so every script's relative paths hold. Already verified over there: all six test suites green (shared-inventory 7, verify-predicates 29, auto-merge-sweep 17, stranded-work 24, worktree-gc 9, model-pin-audit 102), CI green,GROQ_API_KEY/OPENROUTER_API_KEYsecrets set.Why nothing breaks
auto-merge-sweep.ymlstays as a forwarding shim. The 16 repos callingbitbaum/dotfiles/.github/workflows/auto-merge-sweep.yml@masterkeep working — the shim forwards all inputs/secrets tobitbaum/fleet/...@mainand maps the historicref: masterdefault to fleet'smain. No logic in the shim, so no drift.SHARED.mdstays as a pointer — a decade of docs, memories and habits say to check it here. The registry is maintained only in fleet..claude/CLAUDE.md) now point atfleet/SHARED.mdandfleet/templates/ci.What this repo is now
The environment:
.bashrc,.ssh/config,.config/,install.sh, and the thin per-session Claude hooks. CI slims to match: shell syntax + an install.sh dangling-symlink check.Follow-up (not this PR)
Consumers can migrate their
uses:line tobitbaum/fleet/...@mainopportunistically — zero urgency, the shim holds. orangecat notably still points atmaonakamoto/dotfiles(two renames ago) and works only via redirects; it should be first.🤖 Generated with Claude Code
https://claude.ai/code/session_01AZCNYHwjEeqxNpYCUk6Yna