Skip to content

Sanitized history and clone transition

The publication cleanup preserves the development sequence while transforming private deployment examples, identifiers and evidence. Historical commits no longer have their original object IDs or valid original signatures. Newly signed cleanup commits attest the cleanup; they do not impersonate historical signers.

Historical qualification dates, source revisions and recorded integrity digests still describe the original execution. A transformed report or artifact is identified as a derivative, not a qualification of rewritten source. Some historical commit links and retired internal-tracker references may become unavailable when original retained copies are retired. Original evidence and old-to-new mappings are held privately. Use current documentation for operation.

Replace old clones

Only maintainers replacing a checkout from before the privacy rewrite need these steps. Use a fresh clone in a new directory:

# Supply the existing repository URL using your normal authenticated Git setup.
git clone --no-tags --single-branch --branch main REPOSITORY_URL rfsentry-clean
git -C rfsentry-clean config remote.origin.tagOpt --no-tags
git -C rfsentry-clean config push.followTags false

Compare its main tip with the sanitized revision supplied in the cleanup handoff. Do not pull, merge or rebase old history into this clone. Do not use --allow-unrelated-histories, mirror pushes or all-ref/tag pushes to recover old work. Old clones and backups remain private and must not be pushed.

Before retiring an old checkout, preserve any useful local changes privately. Port only reviewed file changes onto the fresh branch, then run public and trusted private checks, including the actual staged index. Do not copy .git, unreviewed patches, private configuration, raw diagnostics or old build outputs. Avoid blindly cherry-picking original commits, which may reintroduce identifying content or metadata. Preserve intentional attribution and the approved public identity.

Recreate CI workspaces and review mirrors/scheduled writers before enabling writes. Keep private recovery backups isolated from publication remotes. A push lease protects one update; it does not prevent a later old clone from restoring history if someone explicitly forces it.