Skip to content

Estate: set up multi-forge mirroring (deferred) #168

Description

@hyperpolymath

Deferred estate task: multi-forge mirroring

Tracking issue raised during the 2026-07-01 estate sync/cleanup pass (owner asked to mark, not action, now).

Goal: Mirror the estate (~500+ repos incl. nested grouping-dir repos) to one or more secondary forges (e.g. Codeberg / self-hosted Forgejo / GitLab) for resilience and sovereignty.

Why it needs its own plan:

  • Scale: ~292 top-level + hundreds nested (julia×39, isers×29, awesome-projects×17, a2ml×14, self-validating×12 …).
  • Identity split: personal hyperpolymath (human) vs org metadatastician (machinery) — mirror mapping must respect this.
  • Auth: post-2026-06-30 key rebuild; secondary-forge tokens/SSH keys not yet provisioned.
  • Rulesets/branch-protection/autodelete do not carry across forges — need a policy for what mirrors enforce.
  • LFS / large artifacts / wiki repos / submodules need per-case handling.
  • Push-mirror vs pull-mirror vs periodic bundle sync decision.

Prereqs: finish local↔remote sync + branch cleanup (in progress), choose secondary forge, provision credentials.

Filed by estate sync agent.

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