sync: auto-sync from GURU-KALI at 2026-06-18 20:38:36
Author: Mike Swanson Machine: GURU-KALI Timestamp: 2026-06-18 20:38:36
This commit is contained in:
22
.claude/memory/reclone-submodule-creds.md
Normal file
22
.claude/memory/reclone-submodule-creds.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
name: reclone-submodule-creds
|
||||
description: Re-cloning claudetools (now submodule-based) needs credential.helper set GLOBALLY or submodule init fails
|
||||
metadata:
|
||||
type: feedback
|
||||
---
|
||||
|
||||
When re-cloning the restructured `claudetools` (history rewritten 2026-06-18; projects
|
||||
are now git submodules under `projects/`), `git submodule update --init --recursive`
|
||||
fails for every `https://git.azcomputerguru.com` submodule with **"could not read
|
||||
Username ... terminal prompts disabled"** — even though the top-level clone succeeded and
|
||||
`~/.git-credentials` already holds `azcomputerguru` creds.
|
||||
|
||||
**Why:** `credential.helper=store` set *locally on the superproject* does NOT propagate to
|
||||
the child `git clone` processes that submodule recursion spawns (they run in fresh repos).
|
||||
|
||||
**How to apply:** before the recursive submodule init, run
|
||||
`git config --global credential.helper store` (the single `~/.git-credentials` line covers
|
||||
`git.azcomputerguru.com`). Then `git submodule update --init --recursive` populates all 23.
|
||||
Also: a fresh clone has empty git `user.name`/`user.email` — `sync.sh` auto-corrects from
|
||||
`identity.json`, but set them if running git before first sync. Re-clone steps: `RECLONE.md`
|
||||
at repo root; pre-split bundle on Jupiter `\\172.16.3.20\Backups\Gitea-Storage`.
|
||||
Reference in New Issue
Block a user