aboutsummaryrefslogtreecommitdiff
path: root/inbox
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-30 14:18:44 -0500
committerCraig Jennings <c@cjennings.net>2026-05-30 14:18:44 -0500
commit968a39bb3978e6ad499447ce173e2265dee772a2 (patch)
tree65632f3b0e6baaf5b4d65ee3aea67b1c8b2125f5 /inbox
parent9c9af9002d2d3b4f21c9a55480b9e5f1aa0f0acd (diff)
downloadrulesets-968a39bb3978e6ad499447ce173e2265dee772a2.tar.gz
rulesets-968a39bb3978e6ad499447ce173e2265dee772a2.zip
fix(startup): exclude Python cache from script sync and restore script exec bits
From health's handoff: the startup =.ai/scripts/= sync was dragging pytest build artifacts into every consuming project. =rsync -a= copies by disk presence, not git status, so the =__pycache__/= and =.pytest_cache/= that rulesets' own pytest leaves in =claude-templates/.ai/scripts/tests/= rode along to each project's tree even though the root =.gitignore= already keeps them out of rulesets' commits. Phase A's scripts rsync now excludes =__pycache__=, =.pytest_cache=, and =*.pyc=. A project that already received the cache has to remove it once by hand, since =--delete= leaves excluded paths in place. I noted that in the startup doc. Health also flagged that =inbox-send.py= kept needing a manual chmod. The cause wasn't rsync dropping the bit. Four shebang scripts (=inbox-send.py=, =cj-scan.py=, =cj-remove-block.py=, =eml-view-and-extract-attachments.py=) were committed mode 100644, so rsync faithfully copied the wrong mode. I set the exec bit on all four so the synced copies are runnable.
Diffstat (limited to 'inbox')
0 files changed, 0 insertions, 0 deletions