Skip to content
HomeWebAppSetDocsAbout
🌐 Auto English 简体中文 繁體中文 Español Français Русский العربية Português Deutsch 日本語 한국어 हिन्दी

Git Sync

Git Sync connects a knowledge base directory to a remote Git repository, bringing version history and team synchronization to your Markdown documents. It’s the foundation for Moraya’s collaboration features — team review and AI review build on top of it.

Requirements

Git Sync calls your system’s git command directly, so you need Git installed on your machine. Most professional environments already have it.

Binding a knowledge base

You can connect a knowledge base to a remote in two directions:

Once bound, Moraya tracks how far your local copy is ahead of or behind the remote and surfaces sync status in the UI.

Everyday operations

ActionWhat it does
PullFetch and merge remote updates
PushSend your local commits to the remote
CommitStage changed files and record a commit with a message
StatusSee which files are modified, added, or deleted
HistoryBrowse the commit log for the repo or a single file
DiffCompare versions of a document

Credentials & security

Access tokens are never stored in plaintext or embedded in the remote URL. Moraya keeps them in the OS keychain and injects them only for the duration of a git command via GIT_ASKPASS:

What gets synced

Your Markdown files sync as normal. Moraya also keeps a .moraya/ directory in the knowledge base for collaboration data — review threads and lock state are shared with your team through the same repository, while machine-local artifacts (search indexes, derived rules) are excluded.