Repository navigation
task: pre-detach snapshot of every repo-scoped setting, runner, variable and link #160
Description
Parent: #158.
Capture, as data in this issue, everything repo-scoped that must still exist and work after the detach. This is the baseline the post-detach verification compares against, so it has to be captured before the owner clicks.
Capture list
Driven by the enumeration in the DIAGNOSE child. At minimum:
| what | how |
|---|---|
| repo settings | gh api repos/OKI-Mesh/CoreScope — visibility, default branch, merge methods, delete-on-merge, features |
| rulesets | gh api repos/OKI-Mesh/CoreScope/rulesets plus each ruleset by id, full JSON including bypass_actors |
| self-hosted runners | gh api repos/OKI-Mesh/CoreScope/actions/runners — names, labels, status |
| Actions variables | gh api repos/OKI-Mesh/CoreScope/actions/variables (ENABLE_STAGING_DEPLOY=true is live) |
| Actions secrets | names only, never values |
| labels | gh label list full set |
| project board links | repository.projectsV2 |
| open issues and PRs | counts and numbers |
| webhooks | gh api repos/OKI-Mesh/CoreScope/hooks |
| GHCR packages | the ghcr.io/oki-mesh/corescope tags CI publishes to |
| master tip | SHA, so we can prove history is unchanged |
Secrets are recorded by name only. No values in this issue.
Done when
The snapshot is posted as a comment on this issue with a UTC timestamp, and the master tip SHA is recorded so the post-detach check can prove history survived byte for byte.
Activity
diffwireauto commentedon Oct 3, 2026
Pre-detach snapshot:
OKI-Mesh/CoreScopeCaptured 2026-10-03T03:01:07Z by AzureSparrow, before the owner leaves the fork network (#161).
This is the baseline #162 diffs against. Secrets appear by name only.
Repository settings
full nameOKI-Mesh/CoreScopevisibilitypublicforktrueparentKpa-clawbot/CoreScopesourceKpa-clawbot/CoreScopenetwork_count67child forks0default branchmastersize (KB)112602squash mergetruemerge committruerebase mergetruedelete branch on mergefalseissuestruewikitrueprojectstruestars5watchers2open issues + PRs82Git state
mastertip:ff5e338f8c2bb612477e2a1bbb75040d0a9c567bRulesets
18667552Protect Main �active, targetbranch, conditions~DEFAULT_BRANCHdeletionnon_fast_forwardpull_request{"allowed_merge_methods": ["squash"], "dismiss_stale_reviews_on_push": false, "dismissal_restriction": {"allowed_actors": [], "enabled": false}, "require_code_owner_review": false, "require_extra_approval_for_unattributed_changes": true, "require_last_push_approval": false, "required_approving_review_count": 1, "required_review_thread_resolution": false, "required_reviewers": []}required_status_checks{"do_not_enforce_on_create": false, "required_status_checks": [{"context": "\u00e2\u0153\u2026 Go Build & Test"}], "strict_required_status_checks_policy": true}bypass actors:
OrganizationAdminid=Nonemode=alwaysRepositoryRoleid=5mode=alwaysSelf-hosted runners
corescope-dev-offbandonlinefalseself-hosted, Linux, ARM64, corescope-dev-offbanddeadbeef-prodonlinefalseself-hosted, Linux, X64, corescope-prodActions variables
ENABLE_STAGING_DEPLOY=trueActions secrets (names only)
PROJECT_PATLabels
board:backlog,board:deferred,board:done,board:in-progress,board:ready,board:testing,board:todo,bug,documentation,duplicate,enhancement,good first issue,help wanted,high-risk,invalid,priority:P0,priority:P1,priority:P2,priority:P3,question,sql-backend,status:void,type:bug,type:chore,type:documentation,type:epic,type:feature,type:incident,type:initiative,type:problem,type:refactor,type:story,type:task,wontfixcount: 34
Project board links
Webhooks, environments, deploy keys
Issues and pull requests at risk (verified not at risk, recorded anyway)
GHCR packages
corescopevisibility=publicdiffwireauto commentedon Oct 3, 2026
Three notes on the snapshot above
1. One value is mangled by my console, not by GitHub. The ruleset's required status check prints as:
That is a double-encoding artifact of how the snapshot was generated. The real value is
✅ Go Build & Test— U+2705 followed by a space. It matters because #162 compares this string, and because the ruleset is joined todeploy.yml:102by exact string match including the emoji. Compare against the real value, not the printed one.2. The repo allows merge methods the ruleset forbids. Repository settings say
squash merge: true,merge commit: true,rebase merge: true, whileProtect Mainrestricts the default branch toallowed_merge_methods: ["squash"]. Not a defect and not caused by anything here — the ruleset is doing the work. Recorded so the post-detach diff does not read it as drift. Same fordelete branch on merge: false, which is the current state and should stayfalseafter.3.
network_count: 67andparent/sourceare the two fields expected to change. Everything else in the snapshot should be byte-identical afterwards.masteratff5e338f8c2bb612477e2a1bbb75040d0a9c567bis the proof that history survived.Snapshot is complete — #161 is unblocked
Preconditions for the Settings option, all met
[verified: api 2026-10-03]:visibility: public112602 KB= 109 MBforks_count: 0And from the #159 experiment
[verified: api 2026-10-03]: issues, PRs, comments, stars and watchers survive the Settings path. The 124 issues and 33 PRs recorded above are not at risk.Nothing further is needed before the owner detaches.