.gitignore for Notes and Extended Configuration
4 ignore rules for Notes and Extended Configuration, ready to copy into your repository.
Extended notes and configuration
The complete .gitignore for Notes and Extended Configuration
# Generated by LFGitignore - https://lfgitignore.com
# Created: 2026-08-05 02:29:20 UTC
# Technologies: Notes and Extended Configuration
### Notes and Extended Configuration ###
.obsidian/workspace.json
.obsidian/workspace-mobile.json
.obsidian/plugins/*/**
!.obsidian/plugins/*/data.json
What these Notes and Extended Configuration rules actually ignore
Every pattern below, and why it belongs in your .gitignore.
General
| Pattern | What it ignores |
|---|---|
.obsidian/workspace.json |
The current application UI state (DOM layout, recently-opened files, etc.) is stored in these files (separate for desktop and mobile) so you can resume your session seamlessly after a restart. If you want to track UI state, use the Workspaces core plugin instead of relying on these files. |
.obsidian/workspace-mobile.json |
General |
.obsidian/plugins/*/** |
Obsidian plugins are stored under .obsidian/plugins/$plugin_name. They contain metadata (manifest.json), application code (main.js), stylesheets (styles.css), and user-configuration data (data.json). We only want to track data.json, so we: 1. exclude everything that the plugin folders contain, 2. unignore data.json in the plugin folders |
!.obsidian/plugins/*/data.json |
General |
How to use this .gitignore for Notes and Extended Configuration
- Copy the Notes and Extended Configuration rules above, or download the file directly.
- Create a file named .gitignore at the root of your Git repository and paste the rules into it.
- If some of those files are already tracked, run git rm -r --cached . then commit again — Git only applies ignore rules to untracked files.
- Commit the .gitignore so everyone on the team shares the same rules.