.gitignore for Elixir
Elixir/Erlang build artifacts, Mix dependencies, and compiled BEAM files.
Quick presets
Selected (1)
Elixir
Your selections never leave your browser. Generation happens entirely client-side.
10 patterns · 241 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: Elixir # 2026-04-20 # ---- Elixir ---- # Elixir /_build/ /cover/ /deps/ /doc/ /.fetch erl_crash.dump *.ez *.beam /config/*.secret.exs .elixir_ls/
What this template ignores
Ignores Mix build output (_build/), dependencies (deps/), compiled BEAM files, crash dumps, and secret configuration files.
Common additions
- +
.env — if using dotenv for secrets
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 mix.lock?
- Yes — mix.lock pins exact dependency versions and should always be committed.
Looking for something else? Browse all templates →