.gitignore for FastAPI

FastAPI Python environment, compiled files, and local configuration.

Quick presets

Selected (1)
FastAPI
Your selections never leave your browser. Generation happens entirely client-side.
Raw

11 patterns · 244 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: FastAPI
# 2026-04-20

# ---- FastAPI ----
# FastAPI
__pycache__/
*.py[cod]
.env
.venv
venv/
ENV/
*.egg-info/
dist/
build/
.pytest_cache/
.mypy_cache/

What this template ignores

Ignores Python bytecode, virtual environments, distribution artifacts, .env secrets, and type/test checker caches.

Common additions

  • +alembic/versions/*.py — if auto-generating migration names (keep manually written ones)

Commonly paired with

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.
Should I commit alembic migrations?
Yes — alembic migration scripts define schema changes and must be committed and applied in order.

Looking for something else? Browse all templates →