Skip to content

Add .gitignore for Python build artifacts and local state#4

Open
megative wants to merge 1 commit into
roxy-wi:mainfrom
megative:chore/add-gitignore
Open

Add .gitignore for Python build artifacts and local state#4
megative wants to merge 1 commit into
roxy-wi:mainfrom
megative:chore/add-gitignore

Conversation

@megative
Copy link
Copy Markdown
Contributor

@megative megative commented Jun 6, 2026

Summary

  • The repository currently has no .gitignore, so local __pycache__/, virtualenvs, pytest/coverage caches, log files, SQLite databases under tests/.tmp/ and operator-local incidentrelay.conf (with secrets) all show up in git status and risk being committed or copied into Docker images via COPY . ..
  • Add a minimal .gitignore covering Python bytecode, venvs, pytest/coverage artifacts, runtime logs, local SQLite/config files, common IDE/editor noise and packaging output.
  • Verified that no currently-tracked file matches the new patterns, so nothing disappears silently from git status.

Test plan

  • git ls-files | git check-ignore --stdin returns no tracked files (i.e. the new ignore patterns don't mask anything already in the repo).
  • After running python -m compileall app and pytest --collect-only, git status shows only the .gitignore itself, not dozens of __pycache__/ directories.
  • CI Tests workflow still passes on this PR.

This is an AI-assisted PR.

The repository previously had no .gitignore, which meant local
__pycache__/, virtualenvs, pytest cache, coverage reports, log
files, SQLite databases under tests/.tmp/ and operator-local
incidentrelay.conf with secrets all showed up in git status and
risked being accidentally committed or copied into Docker images
via COPY . .

The ignore list covers:
- Python bytecode and import cache
- venv/, .venv/, env/, .env
- pytest, coverage and tests/.tmp/ artifacts
- runtime logs and SQLite databases
- local config files (incidentrelay.conf, *.local.conf)
- common IDE/editor and OS files
- packaging build/ and dist/ output

No tracked files are matched by the new patterns, so nothing
disappears silently from git status.
@megative megative force-pushed the chore/add-gitignore branch from 1e39034 to 8124ba7 Compare June 6, 2026 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant