Do I need to commit .gitignore?

Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.

How do I add custom patterns?

Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.

How do I ignore a file that is already tracked?

Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached to stop tracking it without deleting the file locally.

.gitignore for Linux + Node + Python

.gitignore for full-stack projects on Linux covering both Node.js and Python toolchains.

Quick presets

Selected (3)

LinuxNodePython

Your selections never leave your browser. Generation happens entirely client-side.

Raw

99 patterns · 1.3 KB

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Linux, Node, Python
# 2026-04-20

# ---- Linux ----
# Linux
*~
.fuse_hidden*
.directory
.Trash-*
.nfs*

# ---- Node ----
# Node
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
.pnpm-debug.log*
.npm
.yarn/cache
.yarn/unplugged
.yarn/build-state.yml
.yarn/install-state.gz
.pnp.*
lerna-debug.log*
.env
.env.local
.env.development.local
.env.test.local
.env.production.local
dist/
build/
.cache/
*.tsbuildinfo

# ---- Python ----
# Python
__pycache__/
*.py[cod]
*$py.class
*.so
.Python
develop-eggs/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST
*.manifest
*.spec
pip-log.txt
pip-delete-this-directory.txt
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
*.mo
*.pot
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
instance/
.webassets-cache
.scrapy
docs/_build/
.pybuilder/
target/
.ipynb_checkpoints
profile_default/
ipython_config.py
.pdm.toml
__pypackages__/
celerybeat-schedule
celerybeat.pid
*.sage.py
.venv
env/
venv/
ENV/
env.bak/
venv.bak/
.spyderproject.db
.spyproject
.ropeproject
/site
.mypy_cache/
.dmypy.json
dmypy.json
.pyre/
.pytype/
cython_debug/

Why use Linux + Node + Python together?

Projects that mix Node.js and Python (common in data science web apps, ML APIs with a JS frontend, or polyglot microservices) need coverage for both ecosystems. Linux patterns protect against editor backup files that accumulate in Linux environments.

Related combinations

docker-node docker-python

Frequently asked questions

Do I need to commit .gitignore?: Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?: Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?: Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Why combine Linux and Node and Python?: Projects that mix Node.js and Python (common in data science web apps, ML APIs with a JS frontend, or polyglot microservices) need coverage for both ecosystems. Linux patterns protect against editor backup files that accumulate in Linux environments.

Looking for something else? Browse all templates →