[2026-05-23] vault-git-sync: mark Taiga script as fixed
This commit is contained in:
@@ -34,11 +34,11 @@ on 2026-05-23 (two incidents: 3a44a55, c9020c4).
|
||||
|--------|------------------------------------|----------------|
|
||||
| Eagle | `~/scripts/sync-vault.sh` | ✅ Correct |
|
||||
| Kraken | `~/scripts/sync-vault-partial.sh` | ✅ Correct |
|
||||
| Taiga | `/opt/data/sync-vault.sh` | ❌ **BROKEN** — see below |
|
||||
| Taiga | `/opt/data/sync-vault.sh` | ✅ Fixed 2026-05-23 |
|
||||
|
||||
The correct script for Taiga/Kraken is at `~/scripts/sync-vault-partial.sh` on Eagle.
|
||||
It uses sparse checkout (only `personal/` and `family/`), which is an additional safeguard:
|
||||
if Taiga never checks out `wiki/`, it can never delete wiki/ files even if the script has bugs.
|
||||
All scripts now use scoped `git add personal/ family/ .obsidian/` (not `git add -A`) before stash.
|
||||
Taiga additionally uses sparse checkout (only `personal/` and `family/`) — double safeguard:
|
||||
even if a bug reintroduces `git add -A`, sparse checkout means wiki/ is never checked out locally.
|
||||
|
||||
## Taiga Architecture
|
||||
|
||||
|
||||
Reference in New Issue
Block a user