sync-github-to-obsidian

To sync GitHub markdown docs to Obsidian, run a shell scan of your local GitHub repositories to collect .md files, filter out node_modules and .git directories, and copy the preserved folder structure into your Obsidian vault.

Yes, exporting markdown documentation from multiple GitHub projects preserves the original folder structure during the copy process to Obsidian, maintaining navigability and allowing cross-referencing across your repositories.

Yes, the markdown sync process explicitly filters out node_modules and .git directories during the shell scan, ensuring only relevant documentation files are exported to your Obsidian vault.

Yes, local filesystem access is required because the tool uses shell commands to scan local GitHub folders, create project directories, and copy markdown files directly into the Obsidian vault structure.

The best way to build a knowledge base from GitHub project docs is to mirror them into a centralized Obsidian vault using a shell scan that skips noisy folders and outputs a per-project summary for easier browsing.

The GitHub to Obsidian sync outputs a per-project summary to provide a clear overview of exported markdown files, helping you track which repositories were successfully scanned and archived into your vault.