Skip to content

Ask GitHub Support to GC unreachable objects - completes the digest removal #52

Description

@adbarc92

The superseded embargo-guard digests were removed from public history on 2026-08-09 via a targeted 9-commit git filter-repo rewrite (see docs/STATUS.md). That removed them from the branch, from history browsing, from code search, and from every future clone.

It did not delete them from GitHub's object store. A force-push leaves unreachable objects in place. Verified still served by the API after the rewrite:

commit 6016495  -> still served
commit eb832bd  -> still served
blob   ee0ed06… -> still served (1656 bytes)

So the current exposure is "an attacker needs the exact 40-char SHA" rather than "gone". The digests are salted SHA-256 of low-entropy tokens; the 10-digit phone digest previously fell to a targeted search in 22.6 seconds on one CPU core, and a phone number cannot be rotated.

Action

Open a GitHub Support ticket asking them to garbage-collect unreachable objects on adbarc92/command-center. This requires the account owner; it cannot be done via the API or CLI.

Repo has 0 forks, so there are no forks retaining the objects — this is the only remaining copy on GitHub's side.

Also

A pre-rewrite backup bundle containing these blobs was written to the session scratchpad (command-center-backup-pre-rewrite.bundle). Delete it once satisfied the rewrite is good.

Closes the last step of the work started in #45 / #47.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions