GitSync
unlistedby Vishal Sharma
Sync your vault to GitHub. Works on mobile and desktop without Git installed.
MAGNETO β Markdown And Git Notes Export, Track Origin
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: Works with private repositories (auto-create is possible when your token allows it)
- π 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 "MAGNETO"
- Click Install, then Enable
Manual Installation
- Download
main.js,manifest.json, andstyles.cssfrom the latest release - Create folder:
<YourVault>/.obsidian/plugins/magneto/ - Copy the downloaded files into the folder
- Reload Obsidian and enable the plugin
Note: the folder name stays magneto because the plugin id is still magneto.
Setup
MAGNETO works with either:
- Recommended (most secure): a private repo + a fine-grained PAT restricted to that single repo
- Alternative (easiest / auto-create repo): a classic PAT with broad
reposcope
Recommended setup (private repo + restricted token)
1) Create a private GitHub repository
You must create the repo first (fine-grained tokens can only be restricted to repos that already exist).
- Go to https://github.com/new
- Create a Private repository (example:
obsidian-vault) - Optional (recommended): check Add a README so GitHub initializes the default branch (usually
main)
2) Generate a fine-grained token (restricted to that repo)
- GitHub β Settings β Developer settings
- Personal access tokens β Fine-grained tokens
- Click Generate new token
- Configure:
- Token name:
Obsidian MAGNETO (restricted) - Expiration: set a reasonable expiry
- Resource owner: the account/org that owns the repo
- Under Repository access:
- Select Only select repositories
- Choose your repo (example:
obsidian-vault)
- Under Repository permissions, set:
- Contents: Read and write
- Metadata: Read-only
- Click Generate token and copy it immediately
3) Configure MAGNETO in Obsidian
- Obsidian β Settings β Community plugins β MAGNETO
- Set:
- GitHub username: your GitHub username
- Personal access token: paste the fine-grained token
- Repository name: repo name only (example:
obsidian-vault, notowner/obsidian-vault) - Branch: usually
main
- Click Test connection
Alternative setup (classic PAT with repo scope)
Use this if you want MAGNETO to potentially auto-create the repo during Push/Sync, or if fine-grained tokens arenβt an option.
- Go to https://github.com/settings/tokens
- Tokens (classic) β Generate new token (classic)
- Select scope:
repo - Copy the token immediately
Then configure MAGNETO the same way in Obsidian settings.
Start syncing
- Use the ribbon icon (git-branch icon) for quick sync
- Or use the Command Palette (Ctrl/Cmd + P):
MAGNETO: Push to GitHubMAGNETO: Pull from GitHubMAGNETO: Sync with GitHub
- Or use the buttons in the settings tab
Settings
| Setting | Description |
|---|---|
| GitHub Username | Your GitHub username |
| Personal Access Token | Recommended: fine-grained token restricted to your repo (Contents RW + Metadata RO). Classic PAT with repo scope also works. |
| Repository Name | Repo name only (fine-grained tokens require the repo to exist already) |
| 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, MAGNETO:
- 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 right permissions:
- Fine-grained PAT: Contents RW + Metadata RO (and restricted to the correct repo)
- Classic PAT:
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
- π Report a bug
- π‘ Request a feature
- π Documentation
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.