Files
MeshTerm/.gitignore
T
Jean-Pierre MartineauandClaude Opus 5 caac83c64a The developer environment hides where dotfiles hide
dev.env and dev.env.example become .dev.env and .dev.env.example, and the five
skills that name them follow. The .gitignore rule takes the dot too; it matches
the exact name, so the example stays tracked while the real one stays out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-06 02:09:59 -04:00

32 lines
828 B
Plaintext

# Python
__pycache__/
*.py[cod]
*.egg-info/
build/
dist/
# Ignore all dot-directories (.venv, .pytest_cache, .ruff_cache, .vscode, ...)
.*/
# ...except the project's tracked Claude config. Private working notes stay out:
# settings.local.json is per-machine, and plans/ + housekeeping.md are internal
# planning that names hardware and unshipped ideas.
!.claude/
.claude/settings.local.json
.claude/plans/
.claude/housekeeping.md
# Other virtual environments
venv/
# MeshTerm runtime data
*.db
output/
# Developer environment: the machine-specific half of the .claude/ skills (device
# addresses, logins, the local venv path). .dev.env.example is tracked and shows the shape.
.dev.env
# Built radio firmware (scripts/xiao-radio/build-firmware.sh writes it here)
scripts/xiao-radio/*.uf2
scripts/xiao-radio/_meshcore-build/