---
name: gururmm-session-logs-submodule-save
description: Saving gururmm session-logs/docs requires committing inside the guru-rmm git submodule and pushing from the new box (.30) — sync.sh doesn't commit submodule contents and GURU-5070 can't push to gururmm Gitea
metadata:
  type: reference
---

`projects/msp-tools/guru-rmm` is a **git submodule** (gururmm repo,
`git@172.16.3.20:azcomputerguru/gururmm.git`, branch main). So gururmm session logs
(`projects/msp-tools/guru-rmm/session-logs/...`) and docs (`docs/HOST_MIGRATION_RUNBOOK.md`,
etc.) are tracked in the **submodule**, not the parent ClaudeTools repo.

`/save` -> `sync.sh` commits/pushes the **parent** ClaudeTools repo only; it leaves submodule
**gitlinks unstaged** (unless `--with-submodules`) and NEVER commits submodule *contents*. So a
session log written under the submodule is left **uncommitted/untracked** by a normal `/save`.

**GURU-5070 cannot push to gururmm Gitea** (`ssh -p 2222 git@172.16.3.20` -> Permission denied;
its key isn't authorized there). The **new box (.30 / .47)** CAN push (its `~/.ssh/id_ed25519` is
authorized as `gururmm-build-server`).

**To persist gururmm session logs/docs from GURU-5070:** scp the file(s) to the new box's
checkout `/home/guru/gururmm/...` (it's on main with push access), `git add` them explicitly
(avoid the build-artifact changelog cruft), commit + `git push origin main` from the new box.
Then on GURU-5070 advance the submodule (`git -C <sub> fetch origin && stash -u && reset --hard
origin/main && stash drop`), `git add` the gitlink in the parent, commit, and `sync.sh`. The
GURU-5070 submodule checkout tends to sit **detached at a stale commit** (it lags the build
host's auto-bump commits) — fetch first. See [[gururmm-physical-server-storage]].