Skip to content

Remove committed venv/ from repository #4

@DaaanielTV

Description

@DaaanielTV

Problem

The repository currently contains a committed Python virtual environment (venv/).
This introduces several issues:

Extremely large repository size
Massive diffs when modifying or deleting files
Platform-specific binaries (breaks cross-platform compatibility)
Slower cloning and CI operations
Redundant files (dependencies should come from requirements.txt)
Why this matters

Virtual environments are generated artifacts and should never be tracked in version control.
Keeping them in the repo makes maintenance harder and causes tooling issues (e.g., diff size limits).

Proposed Solution

Remove venv/ from version control (without deleting it locally):

git rm -r --cached venv

Ensure .gitignore contains:

venv/
.venv/
env/

Commit the change:

git commit -m "Remove venv from repository and update .gitignore"
(Optional but recommended) Clean repository history if size is a concern:
Use tools like git filter-repo or BFG Repo-Cleaner
Acceptance Criteria
venv/ is no longer tracked by Git
.gitignore prevents future commits of virtual environments
Repository size is reduced
No impact on application functionality
Notes

Each developer should create their own local environment:

python -m venv venv
pip install -r requirements.txt
This change should not affect runtime behavior
Priority

Medium (should be done before public/open-source release)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions