- 已装运
- 2026年9月25日 17:05 UTC
- 作者
- Kamo
- 提交
- 3942793
The KamoUniverse marketing site is now edited on GitHub GitHub, and PRs merge there. But the site deploys from Forgejo (kamo/kamouniverse-marketing), whose workflow builds and rolls out on push. git-sync-kamouniverse-marketing bridges the two: every two minutes it fast-forwards Forgejo main to GitHub main. That is an ordinary push, so the normal build and deploy follow. It never forces. If Forgejo has a commit that GitHub lacks, the job fails with a message saying so and leaves both untouched. Credentials are two SSH deploy keys generated on k1m1 straight into the Secret: read-only on the GitHub repo, write on the Forgejo repo only. Host keys are pinned (StrictHostKeyChecking=yes). Applied by hand, not by deploy-services.yml: a new step there is a .forgejo/ change, which forces a full-cluster reconcile. See git-sync/README.md.