recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ec3e0c35dd5fe1cb237d44cd3d4251255e95e50c
cc-ci-orchestrator/memory/push-commits-to-remote.md
autonomic-bot 542ed0afe3 memory: move agent memory into repo (memory/), note in AGENTS.md 
Persistent agent memories now live in memory/ in this repo; the Claude
auto-memory path is symlinked here so future memories land in the repo
and get committed like any other change.
2026-06-09 19:25:20 +00:00

930 B
Raw Blame History

name, description, metadata
name description metadata
push-commits-to-remote Operator wants every commit pushed to git.autonomic.zone right after it's made
node_type type originSessionId
memory feedback 7b5366a6-263c-421b-be7d-9f888067336b

In the cc-ci orchestrator repo (/srv/cc-ci-orch), push to origin (git.autonomic.zone/recipe-maintainers/cc-ci-orchestrator) immediately after committing — don't leave commits sitting locally waiting to be asked.

Why: the operator treats the remote as the source of truth / backup; local-only commits are a loss risk on this autonomous box.

How to apply: after any git commit here, run git push origin main (or the current branch) in the same turn. The remote is already credentialed in the URL. Mind the orchestrator-host-hetzner git-identity gotcha (commit as autonomic-bot). This standing preference replaces the default "commit/push only when asked" for this repo.