feat: implement the cheshirecube to GitHub source sync (fast-export/import) #386

New issue

Open

opened 2026-08-17 03:19:11 +00:00 by hexajon · 0 comments

hexajon commented

2026-08-17 03:19:11 +00:00

Owner

Goal

Build the one-way source sync that keeps the GitHub SHA-1 mirror (github.com/sixfold-space/madtea) current, so go get madtea.lol resolves. The mechanism is documented in docs/contributing/github-source-sync.md.

Why

The canonical repo is SHA-256; GitHub is SHA-1 only, so no git push mirror is possible. The go-get source is an independent SHA-1 copy maintained by git fast-export --signed-tags=strip | git fast-import, then push (ADR 0032, amended 2026-08-16). This is not built yet - only documented.

Scope

A sync script implementing the runbook's fast-export/fast-import + push to the GitHub mirror (deterministic SHA-1 output).
Wire it into the release flow so the release tag reaches GitHub before GoReleaser publishes, and/or a cheshirecube CI job on push + tag.
Uses the release GitHub PAT (docs/contributing/release-credentials.md), scoped madtea-release-pat.

Done when

A release tag reaches the GitHub SHA-1 mirror with go.mod = madtea.lol.
go install madtea.lol/cmd/madtea@latest resolves (verify per the runbook).

Related: part of the migration epic #420. The first release also depends on the GitHub-API retooling in #421.

## Goal Build the one-way source sync that keeps the GitHub SHA-1 mirror (`github.com/sixfold-space/madtea`) current, so `go get madtea.lol` resolves. The mechanism is documented in `docs/contributing/github-source-sync.md`. ## Why The canonical repo is SHA-256; GitHub is SHA-1 only, so no git push mirror is possible. The go-get source is an independent SHA-1 copy maintained by `git fast-export --signed-tags=strip | git fast-import`, then push (ADR 0032, amended 2026-08-16). This is not built yet - only documented. ## Scope - A sync script implementing the runbook's `fast-export`/`fast-import` + push to the GitHub mirror (deterministic SHA-1 output). - Wire it into the release flow so the release tag reaches GitHub before GoReleaser publishes, and/or a cheshirecube CI job on push + tag. - Uses the release GitHub PAT (`docs/contributing/release-credentials.md`), scoped `madtea-release-pat`. ## Done when - A release tag reaches the GitHub SHA-1 mirror with `go.mod = madtea.lol`. - `go install madtea.lol/cmd/madtea@latest` resolves (verify per the runbook). Related: part of the migration epic #420. The first release also depends on the GitHub-API retooling in #421.

hexajon added the

enhancement

label

2026-08-17 03:19:11 +00:00

hexajon referenced this issue

2026-08-17 15:50:29 +00:00

feat: adopt madtea.lol vanity import path and route distribution through the GitHub edge #420

hexajon added a new dependency

2026-08-17 15:59:09 +00:00

#420 feat: adopt madtea.lol vanity import path and route distribution through the GitHub edge

hexajon added a new dependency

2026-08-17 15:59:10 +00:00