.gitignore for Erlang

Erlang compiled BEAM files, crash dumps, and rebar3 build artifacts.

Quick presets

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

9 patterns · 215 B

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

# ---- Erlang ----
# Erlang
.eunit
deps/
*.o
*.beam
*.plt
erl_crash.dump
.rebar/
_build/
rebar.lock

What this template ignores

Ignores compiled BEAM files, Erlang crash dumps, rebar3 build output (_build/), and PLT files used by Dialyzer.

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.
What is erl_crash.dump?
When the Erlang VM crashes it writes a crash dump to erl_crash.dump. This is diagnostic output and should never be committed.

Looking for something else? Browse all templates →