hermes a63f8f3f9c fix(workflow): treat fork-sync rc=2 as success-with-changes
fork-sync.py exits with code 2 when it has alerts to report (changes
detected) and 1 on real errors. The workflow was treating any non-empty
output as a failure, which made every run where branches were created
show up as failure in CI even though everything worked correctly.

Workflow now distinguishes:
  rc=0: nothing to report
  rc=2: changes reported (success, but worth surfacing in CI summary)
  rc>=3 or other: real failure, mark as such

Assisted-By: hermes-agent:minimax-m3
2026-09-14 17:10:16 +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%