.gitignore for Linux
Linux system files including backup files, NFS artifacts, and KDE/GNOME metadata.
Quick presets
Selected (1)
Linux
Your selections never leave your browser. Generation happens entirely client-side.
5 patterns · 183 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: Linux # 2026-04-20 # ---- Linux ---- # Linux *~ .fuse_hidden* .directory .Trash-* .nfs*
What this template ignores
Ignores Linux editor backup files (files ending with ~), FUSE hidden mounts, KDE .directory files, Trash directories, and NFS temporary files.
Common additions
- +
.env — local environment files - +
*.log — application log files
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 are the *~ files on Linux?
- Many Linux editors (vim, emacs, gedit) create backup files by appending a tilde (~) to the filename. These are local backup copies and should not be committed.
Looking for something else? Browse all templates →