This is a demonstration issue. It is deliberately tiny, so it can be
done start to finish in a couple of minutes. If you are brand new, these are
the ones to start with.
Context
.gitignore covers __pycache__ and node_modules but not Python virtual environments. Anybody who makes a venv inside the project folder will see hundreds of files appear in git status, which is alarming the first time and leads to accidentally committing the lot.
What to change
Files: .gitignore
Requirements:
- Add
.venv/ and env/ under the existing # Python heading
- Keep the existing grouping and comments — do not reorder the file
- One entry per line, matching the style already there
Acceptance criteria
How to verify locally
python3 -m venv .venv
git status # .venv should not be listed
rm -rf .venv
How long this takes
One minute. Two lines. The smallest real contribution on the list.
New here? Comment /claim on this issue and a bot will assign it to you. Then read CONTRIBUTING.md.
Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear.
Context
.gitignorecovers__pycache__andnode_modulesbut not Python virtual environments. Anybody who makes a venv inside the project folder will see hundreds of files appear ingit status, which is alarming the first time and leads to accidentally committing the lot.What to change
Files:
.gitignoreRequirements:
.venv/andenv/under the existing# PythonheadingAcceptance criteria
git statusHow to verify locally
python3 -m venv .venv git status # .venv should not be listed rm -rf .venvHow long this takes
One minute. Two lines. The smallest real contribution on the list.
New here? Comment
/claimon this issue and a bot will assign it to you. Then read CONTRIBUTING.md.Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear.