Repo Bridge Forge

Repo Bridge Forge lets you keep your content in a GitHub repository and have it appear as WordPress posts. Point the plugin at a repo, a branch, and a folder, and every Markdown file there becomes a post. Edit the file in GitHub, and the post updates on your next sync.

It is built for people who like writing in Markdown, want their content under version control, or manage docs and changelogs in a repo and need them mirrored onto a WordPress site.

How it works

• You add a repository owner, name, branch, and an optional sub-folder.
• You provide a fine-grained personal access token with read-only access to that repo.
• Each Markdown file is read, its YAML front matter maps to the post title, slug, status, type, date, categories, and tags, and the body is converted to HTML.
• The plugin tracks each file by its Git blob checksum, so unchanged files are skipped and only real changes trigger an update.

One-directional by design

Your repository is the source of truth. WordPress is the place it gets published. The plugin only reads from GitHub, it never writes back, so there is nothing to reconcile and no risk of the plugin changing your repo.

Example file

---
title: "Getting Started"
slug: getting-started
status: publish
type: post
categories: [Guides]
tags: [setup, intro]
date: 2026-08-14
---

# Getting Started

Your **Markdown** body goes here.

External services

This plugin connects to the GitHub REST API (https://api.github.com) to read files from the repository you configure. It sends requests only after you enter a repository and an access token and only to fetch the repository details, its file tree, and the contents of Markdown files in it. No request is made until you save a configuration, and nothing is sent anywhere else.

• GitHub Terms of Service: https://docs.github.com/site-policy/github-terms/github-terms-of-service
• GitHub Privacy Statement: https://docs.github.com/site-policy/privacy-policies/github-privacy-statement

The plugin does not collect analytics, does not phone home, and stores your token encrypted in your own database.