GitSync
pendingby Vishal Sharma
Sync your vault to GitHub. Works on mobile and desktop without Git installed.
GitSync - Obsidian GitHub Sync Plugin
Sync your Obsidian vault to a GitHub repository. Works on both mobile and desktop without requiring Git to be installed locally.
Features
- 🔄 Full Sync: Push local changes and pull remote changes
- ⬆️ Push to GitHub: Upload all local vault files to your repository
- ⬇️ Pull from GitHub: Download all files from your repository
- ⏰ Auto Sync: Optionally sync at regular intervals (5-120 minutes)
- 📱 Mobile Compatible: Uses GitHub REST API, no Git installation needed
- 🔒 Private Repos: Automatically creates a private repository if it doesn't exist
- 📁 Exclusions: Configure folders and files to exclude from sync
- 🖼️ Binary Files: Supports images, PDFs, and other binary files
Installation
From Community Plugins (Recommended)
- Open Settings → Community plugins
- Disable Restricted mode
- Click Browse and search for "GitSync"
- Click Install, then Enable
Manual Installation
- Download
main.js,manifest.json, andstyles.cssfrom the latest release - Create folder:
<YourVault>/.obsidian/plugins/gitsync/ - Copy the downloaded files into the folder
- Reload Obsidian and enable the plugin
Setup
1. Create a GitHub Personal Access Token
- Go to GitHub Settings → Developer Settings → Personal Access Tokens
- Click Generate new token (classic)
- Give it a descriptive name (e.g., "Obsidian GitSync")
- Select the
reposcope (full control of private repositories) - Click Generate token
- Copy the token immediately - you won't be able to see it again!
2. Configure the Plugin
- Open Obsidian Settings
- Go to Community plugins → GitSync
- Enter your GitHub username
- Paste your Personal Access Token
- Enter a repository name (e.g.,
obsidian-vault) - Click Test Connection to verify your credentials
3. Start Syncing
- Use the ribbon icon (git branch icon) for quick sync
- Or use the Command Palette (Ctrl/Cmd + P):
GitSync: Push to GitHubGitSync: Pull from GitHubGitSync: Sync with GitHub
- Or use the buttons in the settings tab
Settings
| Setting | Description |
|---|---|
| GitHub Username | Your GitHub username |
| Personal Access Token | GitHub token with repo scope |
| Repository Name | Name of the repo (created if doesn't exist) |
| Branch | Git branch to use (default: main) |
| Auto Sync | Enable automatic syncing |
| Auto Sync Interval | How often to auto-sync (5-120 minutes) |
| Commit Message | Template with {{date}} placeholder |
| Excluded Folders | Folders to skip (one per line) |
| Excluded Files | Files to skip (one per line) |
Default Exclusions
By default, these folders are excluded:
.obsidian/plugins- Plugin files (too large, use plugin manager).obsidian/themes- Theme files.trash- Deleted files
How It Works
This plugin uses the GitHub REST API to sync files. Unlike traditional Git sync plugins that require Git to be installed, GitSync:
- Reads all files in your vault
- Uploads them to GitHub using the Git Data API (efficient batch uploads)
- Downloads any remote-only files to your vault
This makes it perfect for Obsidian Mobile where Git isn't available.
Commands
| Command | Description |
|---|---|
Push to GitHub | Upload all local files to GitHub |
Pull from GitHub | Download all files from GitHub |
Sync with GitHub | Push first, then pull (full sync) |
Troubleshooting
"Connection failed"
- Verify your GitHub username is correct
- Ensure your token has the
reposcope - Check that the token hasn't expired
Files not syncing
- Check the Excluded Folders and Excluded Files settings
- Make sure the file isn't in
.obsidian/plugins(excluded by default)
Large vaults
- The plugin uses batch uploads for efficiency
- Very large vaults (10,000+ files) may take a few minutes for the first sync
Development
# Install dependencies
npm install
# Build for development (watch mode)
npm run dev
# Build for production
npm run build
# Run linter
npm run lint
See CONTRIBUTING.md for detailed development guidelines.
Support
Author
Vishal Sharma
- GitHub: @vishal-go
- Email: sharma39vishal@gmail.com
License
MIT License - see LICENSE for details.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.