docs(ci): the sweep lives in bitbaum/fleet, not dotfiles - #425
Merged
Conversation
The `uses:` line is already correct. What was stale is the prose next to it, which told the reader the policy lives in bitbaum/dotfiles and to go change it THERE. That file no longer exists in dotfiles — the sweep moved to bitbaum/fleet on 2026-08-28, because a repo holding someone's .bashrc is not where a fleet's deploy policy belongs. A comment that misroutes a fix is worse than a missing one: it sends the next person to edit a repo where the change would reach nobody, which is the precise failure the shared sweep exists to prevent. Files: .github/workflows/auto-merge.yml, CLAUDE.md Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
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.
The
uses:line here is already correct. What was stale is the prose beside it.It told the reader that the sweep policy lives in
bitbaum/dotfiles, atscripts/ci/auto-merge-sweep.sh, and to "change it THERE". That file no longer exists in dotfiles — the sweep moved tobitbaum/fleeton 2026-08-28, because a repo holding someone's.bashrcand editor config is not where a fleet's deploy policy belongs.A comment that misroutes a fix is worse than a missing one. It sends the next person — or the next agent, since
CLAUDE.mdcarried the same sentence — to edit a repo where the change would reach nobody. That is precisely the failure the shared sweep was built to prevent, reintroduced through documentation instead of code.Three flavours of the same staleness are corrected across the fleet:
auto-merge.ymlcallers — the "ONE place for the whole fleet" commentfleetcrown/CLAUDE.md— the shipping section, which is the instruction file agents read before touching CIci.ymlgolden-floor pointers (printcraft,solon,limitkit) — the templates moved tobitbaum/fleetas well, andlimitkitstill named the retiredcatomeanowner on top of thatNo behaviour changes: not one
uses:, input, or permission is touched. This is the documentation catching up with a migration that already happened, verified across all 38 org repos — 156 workflow files read, 0 unreadable, 0 remaining liveuses:references to dotfiles.🤖 Generated with Claude Code
https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P