.gitignore for Sublime Text

Sublime Text project files, workspace state, and package cache.

Quick presets

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

6 patterns · 270 B

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

# ---- Sublime Text ----
# Sublime Text
*.tmlanguage.cache
*.tmPreferences.cache
*.stTheme.cache
*.sublime-workspace
*.sublime-project
.build-system

What this template ignores

Ignores Sublime Text workspace files (.sublime-workspace) containing recent file history and open tabs, plus compiled cache files.

Common additions

  • +!*.sublime-project — if you want to share project settings

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 .sublime-project?
You can commit .sublime-project (build systems, folder settings) but should ignore .sublime-workspace (personal state like open tabs and recent files).

Looking for something else? Browse all templates →