Skip to content

[CHORE]: Clean up .gitignore redundant patterns and organization #2337

@jonpspri

Description

@jonpspri

Summary

The .gitignore file has accumulated redundant patterns and could benefit from better organization. An analysis identified 16 issues that should be addressed.

Issues to Address

Missing Pattern

  • Add .envrc to support users of direnv for managing private environment variables

Redundant Patterns (Medium Priority)

The following patterns are duplicated or redundant and should be consolidated:

Line Pattern Issue
5 .pylint-cache/ Covered by .pylint-cache
19 .aider* Duplicate
20 .scannerwork Duplicate
35 *.bak Duplicate
40 tmp Covered by tmp/
59 certs/ Duplicate
64 *.log Duplicate
72-74 .venv/, .venv, **/.venv/ Multiple redundant venv patterns
81 public/ Duplicate
90 htmlcov Covered by htmlcov/
93 build/ Duplicate
100 .env Duplicate
137 downloads/ Duplicate

Pattern Simplification

  • Line 273: plugins_rust/**/*.rs.bk has high complexity - consider simplifying

Organization (Low Priority)

Consider grouping related patterns together:

  • General patterns
  • Environment patterns (.env, .envrc, .venv, etc.)
  • Cache patterns (__pycache__, .pytest_cache, etc.)
  • Log patterns (*.log, logs/)
  • Temporary patterns (tmp/, *.tmp)
  • Build patterns (build/, dist/)
  • IDE patterns (.idea/, .vscode/, etc.)

Acceptance Criteria

  • Add .envrc for direnv support
  • Remove all duplicate/redundant patterns
  • Reorganize file with clear section comments
  • Verify no tracked files are affected by changes
  • Test that ignored files remain ignored after cleanup

Metadata

Metadata

Assignees

Labels

COULDP3: Nice-to-have features with minimal impact if left out; included if time permitschoreLinting, formatting, dependency hygiene, or project maintenance choresgood first issueGood for newcomers

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions