chore: retire the maonakamoto handle - #11
Merged
Merged
Conversation
The account was renamed to `catomean` and the repos then moved to the `bitbaum` org, so `maonakamoto` now names nothing: github.com/maonakamoto and maonakamoto.github.io both return 404, and @maonakamoto no longer resolves as a user. Three different targets, because these are not the same reference: repo links -> bitbaum/<repo> (the repos live in the org) the person -> catomean (profile links, @mentions, CODEOWNERS) pages site -> bitbaum.github.io Deliberately NOT changed: .mailmap keeps the old noreply address as an ALIAS. It is what maps historical commits onto the current identity; deleting it would silently unmap them. Only the canonical side moved to catomean. Files that explain the outage by naming the old account keep it, since the name is the content. Files: package.json Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P
github-actions Bot
pushed a commit
that referenced
this pull request
Sep 7, 2026
GITHUB_TOKEN cannot merge a PR that touches .github/workflows. The sweep tries, the merge API refuses, it logs "leaving for the next sweep", and repeats — while still exiting 0. So the failure is invisible: every run reports success and the PR simply never merges. That is not hypothetical. ai-kit #11 (bump actions/checkout) sat green, CLEAN and MERGEABLE for nine days; aoz-housing #122 (bump actions/upload-artifact) for nine more. Both had to be merged by hand today. Every Dependabot `github_actions` bump in the fleet is in this class, permanently. A PAT fixes a second thing that costs more: THROUGHPUT. A dispatch made with GITHUB_TOKEN emits no workflow_run, so after each merge nothing wakes the sweep to take the next PR — it waits for the cron, and GitHub throttles scheduled workflows to roughly hourly regardless of what the cron says. Observed in fleetcrown: sweeps ~50-65 minutes apart against a */10 schedule. A PAT-created dispatch does emit workflow_run, so the queue drains at CI speed instead. The reusable workflow has always supported this — GH_TOKEN is `secrets.token || github.token`. This just passes it. SAFE BEFORE THE SECRET EXISTS: an undefined secret resolves to empty, and the fallback picks github.token. So this changes nothing until FLEET_PAT is created as an organisation secret, and needs no second pass afterwards. Claude-Session: https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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.
maonakamotono longer names anything. The account was renamed tocatomean, and the repos then moved to thebitbaumorg.Verified rather than assumed:
github.com/maonakamotomaonakamoto.github.io/hire/gh api users/maonakamotogithub.com/maonakamoto/<repo>bitbaum/<repo>So the references split into three groups, and treating them as one string would produce new broken links:
bitbaum/<repo>— the repos live in the org nowcatomean— profile links,@mentions, CODEOWNERSbitbaum.github.io— the old host 404s; this one is liveWhat was actually broken, not merely stale
petvity/.github/workflows/deploy.ymlcalledmaonakamoto/fleetcrown/...selfhost-deploy.yml@main. Actions does not follow the redirect that everything else follows, so this repo's deploy was dead — and it has noauto-merge.yml, which is why the earlier sweep-focused pass never saw it.fleetcrown/.github/CODEOWNERSwas* @maonakamoto— a user that returns 404, so the file assigned no owner at all while looking populated.hire/index.html— the live hire page — linked twice to a 404 profile.GH_OWNERdefaults indotfilesandcrewlessaudit tooling defaulted tomaonakamoto, so those tools enumerated a nonexistent owner and would report an empty fleet as a clean one.package.jsonrepository URLs in four packages, one of which (bip-kit) is published to npm with that URL on its listing.Deliberately left alone
.mailmapkeeps the old noreply address as an alias. That line is what maps historical commits onto the current identity; deleting it would silently unmap every commit ever authored under it. Only the canonical side moved tocatomean.orangecat.ch/profiles/maonakamotois untouched: thecatomeanslug 404s too, so rewriting it would swap one dead link for another and hide a real problem instead of fixing it.🤖 Generated with Claude Code
https://claude.ai/code/session_01UvjGNAS9CMfEGNW26tUR4P