4 Commits

Include renames

Author	SHA1	Message	Date
Claude	7cc654c987	ci: scheduled workflows run on the cron lane runner ... astra, heartbeat, housekeeping, sync, update and venture move to runs-on: cron (green-tea-runner-cron), so they never queue ahead of deploys on the main runner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VVFi3wvLWKaEkpDw6eLnQC	2026-10-25 16:55:40 -07:00
teahubxyzandClaude Opus 5.5	745231844f	sync: secret names Gitea accepts (SYNC_GITHUB_KEY, SYNC_GITHUB_TOKEN) (#179) ... sync: secret names Gitea accepts (SYNC_GITHUB_KEY, SYNC_GITHUB_TOKEN) (#179) Gitea refuses secret names starting GITHUB_ or GITEA_, so the GitHub copy's deploy key is in SYNC_GITHUB_KEY. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD	2026-10-19 04:03:20 +00:00
teahubxyzandClaude Opus 5.5	e34994bbc6	Sync: the GitHub copy over SSH with a deploy key (host keys pinned) (#178) ... Sync: the GitHub copy over SSH with a deploy key, host keys pinned (#178) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD	2026-10-19 03:33:59 +00:00
teahubxyzandClaude Opus 5.5	ab3c5f5200	Sync: a repo's copies on other forges follow its home (GitHub first, for cloud sessions) (#177) ... Sync: a repo's copies on other forges follow its home (#177) sync.py + time/sync.json + the sync workflow. One home per repo, one writer per branch: main goes out to every copy fast-forward only (a diverged copy is a needs-human issue, never overwritten, unless forced once); a copy's claude/* branches come home as PRs for the council. First copy: github.com/teahubxyz/time, skipped until GITHUB_MIRROR_TOKEN. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD	2026-10-19 03:18:50 +00:00