Sync: a repo's copies on other forges follow its home (GitHub first, for cloud sessions) #177

Merged
teahubxyz merged 3 commits from sync-copies into main 2026-10-19 03:18:50 +00:00
3 Commits
Author SHA1 Message Date
teahubxyzandClaude Opus 5.5 4af8c5dcdc changelog: sync
ci / test (pull_request) Successful in 36s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
2026-10-19 03:17:46 +00:00
teahubxyzandClaude Opus 5.5 4547115cbc test: 83 sync.py against real local git repos
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
2026-10-19 03:17:40 +00:00
teahubxyzandClaude Opus 5.5 16fec75a43 sync: keep a repo's copies on other forges in step with its home (sync.py, time/sync.json, sync workflow)
One home per repo, one writer per branch: main goes out to every copy fast-forward only (a copy with commits of its
own is reported as a needs-human issue, never overwritten, unless forced once from the dispatch); a copy's branches
matching its import patterns (claude/* from cloud sessions on GitHub) come back to the home as PRs for the council.
The first copy is github.com/teahubxyz/time, skipped until GITHUB_MIRROR_TOKEN is set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
2026-10-19 03:17:10 +00:00