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.

Should I commit the Makefile?

Yes — the Makefile defines your build steps and should always be committed.

.gitignore for Make

Make build artifacts and generated dependency files.

Quick presets

Selected (1)

Make

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

Raw

5 patterns · 161 B

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

# ---- Make ----
# Make
*.o
*.d
*.a
*.so
build/

What this template ignores

Ignores compiled object files (.o), dependency files (.d), static/shared libraries, and build output.

Commonly paired with

c cpp cmake Combine →

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 the Makefile?: Yes — the Makefile defines your build steps and should always be committed.

Looking for something else? Browse all templates →