azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(sync): detect untracked-only changes; reconcile timer-era memories

Browse Source 
sync.sh: replace `git diff-index --quiet HEAD --` with
`[ -n "$(git status --porcelain)" ]` in both the main-repo (Phase 1) and
vault change-detection, so brand-new untracked files are no longer silently
skipped (the bug Howard hit 2026-04-17). Mark project_sync_script_bug.md
RESOLVED.

.gitignore: exclude the datto BSOD dumps (6 MB zip + 48 MB extracted) so the
detection fix doesn't sweep 54 MB of binaries into the repo.

memory: finish the add_line_item reconciliation — drop legacy "time entry" /
timer-billable framing from feedback_syncro_labor_type and
feedback_syncro_warranty_product (and their index lines); the product-selection
rules themselves are unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-05-21 10:19:52 -07:00
parent a201140e92
commit 0897e5e317
6 changed files with 25 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.claude/memory/project_sync_script_bug.md
View File

@@ -1,9 +1,15 @@
---
name: Sync script bug — untracked files
description: Flagged for Mike — .claude/scripts/sync.sh misses untracked-only changes
description: RESOLVED 2026-05-21 — sync.sh now uses git status --porcelain (catches untracked-only changes) in both repo and vault detection.
type: project
---
> **RESOLVED 2026-05-21.** Fixed in `.claude/scripts/sync.sh`: both the main-repo (Phase 1)
> and vault change-detection now use `if [ -n "$(git status --porcelain)" ]` instead of
> `git diff-index --quiet HEAD --`, so untracked-only changes are caught. A `.gitignore` entry
> was added for the datto BSOD dumps (54 MB binary) so the fix doesn't sweep them in. Original
> report retained below.
`.claude/scripts/sync.sh` line 53 uses `git diff-index --quiet HEAD --` to detect local changes. This only flags **tracked** files with modifications. Brand-new untracked files (a new report, new session log, new memory) will NOT be detected on their own — they only get swept up when a tracked file is also dirty (because `git add -A` then runs).
Symptom seen 2026-04-17 by Howard: added a single new report file, ran /sync, script said "No local changes to commit" and did nothing. Workaround was `git add <file>` first, then re-run.