Files
leetcrypt d1eb4b0bbb chore(git): keep the benchmark harness local, never push to origin
The bench/ native-harness benchmark suite is dev-internal test tooling tightly
coupled to the local tmux + podman test rig, so untrack it and ignore /bench/
entirely (harness code AND result artifacts) — it stays on disk for local use
but no longer ships to origin. Also keep ignoring /docs/plans/ (local planning).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-06-15 08:26:43 -07:00

47 lines
808 B
Plaintext

# Python
__pycache__/
*.pyc
/venv/
.venv/
.pytest_cache/
.benchmarks/
build/
dist/
*.egg-info/
cmd_chat.egg-info/
secured_console_chat.egg-info/
# Secrets / keys
*.pem
# Editor / OS
.idea/
# Logs / runtime scratch
*.log
err.log
# Sandbox save/load snapshots (large runtime tarballs, not source)
/hh/hh-snapshots/
# Out-of-tree experiments (not part of hack-house)
/experiments/
/headroom/
# Heavy / superseded demo-build kit (real demos live in video-toolkit)
/docs/demo/
# Native-harness benchmark harness + results — dev-internal test tooling, kept
# on disk but never pushed to origin (coupled to the local tmux+podman test rig)
/bench/
# Local-only planning/design docs (kept on disk, never pushed to origin)
/docs/plans/
# Project scratch
/i-try/
test_rsa.py
commiter.py
true.txt
/downloads/