teahubxyz/time
1
0 Fork 0
Code Issues 56 Pull Requests 22 Actions Packages Projects Releases Wiki Activity

Sync: the GitHub copy over SSH with a deploy key (host keys pinned) #178

Merged
teahubxyz merged 3 commits from sync-deploy-key into main 2026-10-19 03:33:59 +00:00
Conversation 0 Commits 3 Files Changed 4
+84 -11
3 Commits
Author SHA1 Message Date
teahubxyzandClaude Opus 5.5 0275e30d42 sync: the GitHub copy over SSH with a deploy key (GITHUB_MIRROR_KEY); the job installs ssh if missing
ci / test (pull_request) Successful in 37s
Details 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
 2026-10-19 03:32:46 +00:00
teahubxyzandClaude Opus 5.5 e2fb17e532 test: 83 a copy over SSH with a deploy key 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
 2026-10-19 03:32:06 +00:00
teahubxyzandClaude Opus 5.5 7cb95e9472 sync: a copy over SSH with a deploy key, host keys pinned 
A GitHub deploy key writes to one repo and nothing else, and GitHub's API can make one (a fine-grained token needs a
person in the browser). The key is written 0600 in the run's temp folder; github.com's published host keys are built
in and other hosts need theirs in known_hosts, so nothing is trusted on first use.

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