chore(org-migration): baseline snapshot of the 31 move-list repos - #82
Merged
twistedmelonman merged 2 commits intoSep 4, 2026
Merged
Conversation
added 2 commits
September 4, 2026 06:50
…ts as null The first real baseline run failed all three private repos on the move list (scripts, cleanroom, claude-config-backup): GitHub answers the branch-protection and rulesets endpoints of a private repo under a free plan with a 403 "Upgrade to GitHub Pro or make this repository public", not a 404. That is an absence — the feature does not exist there — and the same absence after the transfer, so snapshot.sh now records null for exactly that sentence on exactly those two endpoints. Any other 403, and the same sentence on any other endpoint (secrets), still fails the repo. Test: private repo with both 403s snapshots with protection==null and rulesets==null (fails on the previous snapshot.sh); the same sentence on the secrets endpoint is still a failure with no file written. Claude-Session: https://claude.ai/code/session_01B7KFdvsQq7eLUGEi4pRQmX
…26-09-04) Owner, default branch, visibility, archived, topics, pages, secret NAMES (no values), branch protection, and rulesets, taken before the rename. verify.sh diffs the post-transfer snapshot against this (with jq, so the prettier formatting the commit hook applied carries no meaning). Claude-Session: https://claude.ai/code/session_01B7KFdvsQq7eLUGEi4pRQmX
twistedmelonman
deleted the
claude/data-org-migration-baseline-01B7KFdv
branch
September 4, 2026 14:55
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.
Step 1 of docs/superpowers/specs/2026-09-03-org-migration-design.md. Advances #54.
What
docs/data/org-migration/2026-09-04-baseline/— one JSON per move-list repo (31 files, incl..github.json): owner, default branch, visibility, archived, topics, pages, secret names (no values), branch protection, rulesets.verify.shdiffs the post-transfer snapshot against these with jq.snapshot.sh: on a private repo under the free plan GitHub answers the branch-protection and rulesets endpoints with a 403 ("Upgrade to GitHub Pro or make this repository public…"), not a 404. That is an absence, so those two endpoints now recordnull. Any other 403, and the same sentence on any other endpoint (e.g. secrets), still fails the repo. Measured onscripts,cleanroom,claude-config-backup.privrepo(must snapshot withnullprotection/rulesets) andproplan(Pro sentence on secrets must still fail) stubs; suite 36/36.Verification
bash scripts/org-migration/tests/run-tests.sh— 36 pass, 0 failshellcheck -S info scripts/org-migration/snapshot.shcleanhttps://claude.ai/code/session_01B7KFdvsQq7eLUGEi4pRQmX