Direct Git Sync

Private source reviewed

Sync your Obsidian vault directly with a GitHub repository on desktop and mobile.

End to end: open Settings, add your repository URL and token, save, and sync.

Direct Git Sync is built for people who want simple Git-based vault sync without installing Git on every device. It uses isomorphic-git for repository operations and Obsidian-friendly HTTP requests so the same flow can work inside desktop and mobile Obsidian.

Why

Direct Git Sync is for the case where you want your vault backed by a GitHub repository:

• private notes backed up to GitHub
• a vault shared across desktop and mobile
• version history through Git commits
• a portable setup that does not require the Git CLI inside Obsidian

The plugin keeps the workflow intentionally small:

• enter a repository URL
• enter a personal access token
• sync from the ribbon button or on an interval

What it does

• Complete sync flow in one action: stage, commit, fetch, merge, and push.
• Works on desktop and mobile.
• No separate Git installation required.
• Verifies your repository and token before sync starts.
• Supports automatic interval-based sync.
• Shows the last successful sync time and recent sync history in a dedicated modal.
• Handles merge conflicts by keeping the local file and saving the remote version as a separate conflict copy.

Install

From inside Obsidian

1. Open Settings -> Community plugins -> Browse.
2. Search for Direct Git Sync.
3. Click Install, then Enable.
4. Or visit website : https://community.obsidian.md/plugins/direct-git-sync to download.

From BRAT

1. Install the BRAT plugin enable it.
2. Add this github repo's link to 'Add Beta Plugin'
3. Select Latest Version
4. Click 'Add Plugin'

Manual install

Download these files from the latest GitHub release into .obsidian folder: Files required:

• main.js
• manifest.json
• styles.css

Then enable the plugin in Settings -> Community plugins.

Caption: The GitHub release should include main.js, manifest.json, and styles.css for manual installation.

Setup

1. Create a repository

Create a public/private GitHub repository for your vault. A typical URL looks like:

https://github.com/your-username/your-repo.git

Caption: Copy your repository URL from GitHub. This is the value you will paste into the plugin settings.

2. Create a personal access token

Create a GitHub token that can read and write the repository. Steps:

1. Open Settings

2. Open Credentials under Access

   

3. Click on Personal access tokens (classic)

4. Click on Generate new token (classic).

5. Write any title under note.

6. Under Expiration select no expiration

7. In Select scope section check the repo checkbox

8. Then click generate token at the end of the page

9. Copy the token somewhere face as you will not be able to see it again

For a classic token, the repo scope is enough.

Caption: Copy the token and store it somewhere safe

3. Configure the plugin

Open Settings -> Direct Git Sync and fill in:

• GitHub repository URL
• Personal access token
• Author name (Any name will work)
• Author email (Any email will work)

You can also enable auto-sync and add extra ignore rules there.

Caption: Paste your repository URL and token into Direct Git Sync settings, then save your author details and optional sync preferences.

How sync works

Each sync run follows the same sequence:

1. Verify repository access and credentials.
2. Initialize the local Git state if needed.
3. Stage all local changes that are not ignored.
4. Create a commit if there is anything new to save.
5. Fetch the latest remote changes.
6. Merge remote changes into the local vault.
7. Push the final result back to GitHub.

On first-time setup, if the remote already contains files that would overwrite local files, the plugin creates local backup copies before checkout.

Caption: A sync run verifies the repository, stages local changes, fetches remote updates, merges them, and pushes the final result.

Conflicts

If the same file changed locally and remotely, the plugin does not discard your local work.

Instead it:

• keeps your local version in place
• writes the remote version as a separate file
• commits the conflict result so the vault stays in a usable state

This is a local-first conflict strategy designed to avoid silent data loss.

History

The plugin includes a sync history modal with:

• the last successful sync time
• recent sync commit messages
• short commit hashes for quick reference

Open it from the command palette:

Direct Git Sync: Show sync history

Auto sync

You can enable automatic sync in settings and choose an interval in minutes. When enabled, the plugin periodically runs the same sync flow in the background. Caption: Auto Sync Feature

Ignored files

The plugin automatically ignores a few vault-local paths such as workspace state and its own data.json.

You can add your own ignore rules in plugin settings, one path per line. These are written into the vault .gitignore.

Caption: Add extra ignored paths here when you do not want certain vault files or plugin folders committed to Git.

Security and storage

• Authentication currently uses GitHub personal access tokens over HTTP.
• The token is stored in the plugin data file inside your vault.
• The plugin automatically ignores its own data.json so the token is not supposed to be committed by the plugin itself.

Because the token is stored locally, keep your vault and backups private.

License

MIT