Posts to GitHub
Export published WordPress posts as Markdown files (with YAML front matter) to a GitHub repository.
Use with caution
Posts to GitHub works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Posts to GitHub stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| backup | >100 |
| corpus | #9 |
| export | >100 |
| Github | >100 |
| markdown | >100 |
About Posts to GitHub
From the official readme · v1.5.15Description
Posts to GitHub exports your published posts as Markdown files, with YAML front matter, to an existing GitHub repository (public or private). The goal is to build, over time, a text corpus of your writing that’s useful for training or guiding a consistent writing style in tools like Claude.
Features:
* Export a single post from its edit screen, with live status and trace log
* Bulk export from a dedicated Posts screen: filters, pagination, multi-page selection, stoppable progress
* Single commit and push for the whole bulk export batch by default (opt out for one commit per post), with automatic retry on GitHub rate limits either way
* Optional automatic export of newly published posts and automatic re-export of updated posts, both in the background via WP-Cron
* Read-only view of posts that were exported but are no longer published (draft, private, scheduled or trashed)
* Connection test and automatic branch detection against the configured GitHub repository
* WP-CLI commands for scripted single or bulk exports
* English by default, with an included Italian translation
* Git Updater compatible for seamless updates from GitHub
The plugin never creates the repository, never uploads binary images (they stay as absolute links to the source site), and only works on published post content.
External services
This plugin connects to GitHub’s REST API (api.github.com) to write your exported posts to a repository you own and configure. It is a core, opt-in part of the plugin’s function: nothing is sent until you set a Personal Access Token and target repository in Settings and trigger an export (manually, in bulk, or via the optional automatic-export setting).
On each export, the plugin sends the post title, content converted to Markdown, and basic metadata (date, categories, tags, slug) as the file content of a commit to the repository and branch you configured. It also calls the API to test the connection, detect the default branch, and read/create the file/commit needed for the export. No data is sent to any third party other than GitHub, and no data is sent unless you have explicitly configured the plugin.
This service is provided by GitHub, Inc.: GitHub Terms of Service and GitHub Privacy Statement.
Installation
- Copy the whole plugin folder to
wp-content/plugins/post-to-github-md/(thevendor/folder with dependencies is already included: no need to run Composer). - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Go to Settings → Posts to GitHub and configure a GitHub Personal Access Token and target repository.
- Export posts individually from the post edit screen, in bulk from Posts → Export to GitHub, or automatically on publish via the “Automatic export” setting.
Frequently asked questions
Does this create the GitHub repository for me?
No, the target repository must already exist before configuring the plugin.
Does it upload images?
No. Images in the post content remain absolute links to your site; nothing binary is uploaded to GitHub.
What post types are supported?
Only the post post type, with “published” status.
Changelog
Bulk export now uses one commit for the whole batch by default; uncheck "Bulk export method" in Settings to keep one commit per post.
1.5.15
- Taxonomy backup section: fixed intro paragraph layout and added direct links to
wp-categories.json/wp-tags.jsonon GitHub. - Added a “back to top” floating button to the Export posts screen.
1.5.14
- Added a taxonomy backup section on the Export posts screen: pushes
wp-categories.jsonandwp-tags.jsonto the repository root on demand, keeping a versioned snapshot of your categories and tags alongside your exported posts. WordPress stays the source of truth; nothing is ever read back from GitHub.
1.5.13
- First release published to the WordPress.org SVN repository.
- Fixed the bundled
POTOGH_VERSIONconstant, which was out of sync with the plugin header. - Release packaging now strips
vendor/*/bindirectories, addressing a WordPress.org review note about non-plugin files in the distributed zip.
1.5.12
- Aligned the text domain with the plugin slug (
posts-to-github-md) across all files and the plugin header. - Sanitized the
branchandbase_foldersettings withsanitize_text_field()instead of trimming only. - Removed bundled translation files (
.po/.mo/.pot); translations are now handled via translate.wordpress.org.
1.5.11
- The export status text (“Exported on …”) in the bulk export table is now a direct link to the file on GitHub, opening in a new tab.
- Added the
Release Asset: trueplugin header so Git Updater installs the clean production zip instead of the rawmainbranch zip.
1.5.10
- Silenced the remaining informational
meta_queryslow-query warnings from the WordPress Plugin Check tool with justifiedphpcs:ignoreannotations: the plugin’s export-status filters query its own_potogh_exported_at/_potogh_pathpost meta and have no WP_Query alternative.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Posts to GitHub alternatives
All backup plugins →
FAQ
Posts to GitHub: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 6, 2026
Is Posts to GitHub free?
Yes. Posts to GitHub is free to download and use from the official WordPress.org plugin directory.
Is Posts to GitHub safe to use in 2026?
Posts to GitHub works, but test it on a staging site before relying on it in 2026. Was last updated 2 months ago, and scores 55/100 on our health check.
How many websites use Posts to GitHub?
Posts to GitHub is active on <10 WordPress websites and has been downloaded 217 times since it launched in July 2026. It was downloaded 58 times in the last 30 days.
Does Posts to GitHub work with WordPress 7.1?
Posts to GitHub is officially tested up to WordPress 7.0.7, while the latest release is 7.1.3. It may still work, but try it on a staging site first.
What PHP version does Posts to GitHub need?
Posts to GitHub requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Posts to GitHub last updated?
The latest version, 1.5.15, was released on July 29, 2026 (2 months ago).
Who makes Posts to GitHub?
Posts to GitHub is developed and maintained by gioxx.
What are the best alternatives to Posts to GitHub?
The most popular alternatives to Posts to GitHub are All-in-One WP Migration and… (5M+ installs), UpdraftPlus: WP Backup & Mi… (4M+ installs) and Jetpack (3M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
