hermes 9f6ef132f8 fix(fork-sync): actually push to origin after FF
The previous version only updated local clones (the CI workdir) but
never pushed the synced state back to the fork. This means the Gitea
web UI kept showing stale branches even after a green CI run.

Now `git push origin <branch>` runs after each successful fast-forward
and after each created branch. The local CI run can then verify via
the Gitea API that the fork actually moved.

Note: forks whose default_branch differs from upstream default_branch
(e.g. hermes/hermes-voice-gateway uses feat/voice-gateway-mvp while
upstream Org1/hermes-voice-gateway uses main) will still lag on the
default branch. To keep both in sync, run the workflow with a
FORK_BRANCHES env that includes the upstream default_branch name.

Assisted-By: hermes-agent:minimax-m3
2026-09-14 17:38:22 +00:00

hermes/fork-sync

Sync infrastructure for hermes/* forks. Workflow pulls upstream branches into forks every hour.

What it does

For each fork pair hermes/<name>=<upstream-owner>/<name>:

  1. Clones the fork if not present
  2. Adds <upstream-owner>/<name> as upstream remote
  3. Fetches both upstream and origin with --prune
  4. Fast-forwards every local branch with an upstream counterpart (only --ff-only)
  5. Creates local tracking branches for upstream branches we don't have yet
  6. Reports divergences (non-FF-able conflicts) on stdout

Stdout is empty on quiet tick. Non-empty stdout = one Telegram alert.

Trigger

  • Schedule: hourly (0 * * * *) — workflow fork-sync.yml
  • Manual: workflow_dispatch
  • Local cron (fallback for environments without actions): /opt/data/cron/jobs.json → job fork-sync (every 1h)

Fork pairs (default)

hermes/brencher                  = admin/brencher
hermes/ansible                   = admin/ansible
hermes/reverseproxy              = admin/reverseproxy
hermes/mcps                      = admin/mcps
hermes/hermes-voice-gateway      = Org1/hermes-voice-gateway

Override via FORK_PAIRS env (comma-separated fork=upstream).

Secrets

Name Required Used for
HERMES_GITEA_TOKEN yes clone + fetch over HTTPS

Names starting with GITEA_ or GITHUB_ are reserved by Gitea, hence the HERMES_ prefix.

Files

  • .gitea/workflows/fork-sync.yml — workflow definition
  • tools/fork-sync.py — sync script (shared with local cron fallback)

Adding a new fork

Append hermes/<repo>=<upstream-owner>/<repo> to FORK_PAIRS. The next run will clone the fork and pull every upstream branch.

S
Description
Hermes-agent cron-driven fork-sync infrastructure. Workflow syncs upstream branches into hermes/* forks hourly.
Readme
65 KiB
Languages
Python 100%