Bulk export now uses one commit for the whole batch by default; uncheck "Bulk export method" in Settings to keep one commit per post.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.5.13"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[151,273611,1859,1673,4608],"plugin_category":[59],"plugin_contributors":[230503],"plugin_business_model":[],"class_list":["post-343075","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-corpus","plugin_tags-export","plugin_tags-github","plugin_tags-markdown","plugin_category-utilities-and-tools","plugin_contributors-gioxx","plugin_committers-gioxx"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/posts-to-github-md.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
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.<\/p>\n\n
Features:\n* Export a single post from its edit screen, with live status and trace log\n* Bulk export from a dedicated Posts screen: filters, pagination, multi-page selection, stoppable progress\n* 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\n* Optional automatic export of newly published posts and automatic re-export of updated posts, both in the background via WP-Cron\n* Read-only view of posts that were exported but are no longer published (draft, private, scheduled or trashed)\n* Connection test and automatic branch detection against the configured GitHub repository\n* WP-CLI commands for scripted single or bulk exports\n* English by default, with an included Italian translation\n* Git Updater compatible for seamless updates from GitHub<\/p>\n\n
The plugin never creates the repository, never uploads binary images (they stay as absolute links to the source site), and only works on published This plugin connects to GitHub's REST API ( 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.<\/p>\n\n This service is provided by GitHub, Inc.: GitHub Terms of Service<\/a> and GitHub Privacy Statement<\/a>.<\/p>\n\n\n No, the target repository must already exist before configuring the plugin.<\/p><\/dd>\n No. Images in the post content remain absolute links to your site; nothing binary is uploaded to GitHub.<\/p><\/dd>\n Only the post<\/code> content.<\/p>\n\nExternal services<\/h3>\n\n
api.github.com<\/code>) 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).<\/p>\n\n\n
wp-content\/plugins\/post-to-github-md\/<\/code> (the vendor\/<\/code> folder with dependencies is already included: no need to run Composer).<\/li>\n\n
Does this create the GitHub repository for me?<\/h3><\/dt>\n
Does it upload images?<\/h3><\/dt>\n
What post types are supported?<\/h3><\/dt>\n
post<\/code> post type, with \"published\" status.<\/p><\/dd>\n\n<\/dl>\n\n\n1.5.13<\/h4>\n\n
\n
POTOGH_VERSION<\/code> constant, which was out of sync with the plugin header.<\/li>\nvendor\/*\/bin<\/code> directories, addressing a WordPress.org review note about non-plugin files in the distributed zip.<\/li>\n<\/ul>\n\n1.5.12<\/h4>\n\n
\n
posts-to-github-md<\/code>) across all files and the plugin header.<\/li>\nbranch<\/code> and base_folder<\/code> settings with sanitize_text_field()<\/code> instead of trimming only.<\/li>\n.po<\/code>\/.mo<\/code>\/.pot<\/code>); translations are now handled via translate.wordpress.org.<\/li>\n<\/ul>\n\n1.5.11<\/h4>\n\n
\n
Release Asset: true<\/code> plugin header so Git Updater installs the clean production zip instead of the raw main<\/code> branch zip.<\/li>\n<\/ul>\n\n1.5.10<\/h4>\n\n
\n
meta_query<\/code> slow-query warnings from the WordPress Plugin Check tool with justified phpcs:ignore<\/code> annotations: the plugin's export-status filters query its own _potogh_exported_at<\/code>\/_potogh_path<\/code> post meta and have no WP_Query alternative.<\/li>\n<\/ul>\n\n1.5.9<\/h4>\n\n
\n
1.5.8<\/h4>\n\n
\n
1.5.7<\/h4>\n\n
\n
1.5.6<\/h4>\n\n
\n
1.5.5<\/h4>\n\n
\n
1.5.4<\/h4>\n\n
\n
1.5.3<\/h4>\n\n
\n
1.5.2<\/h4>\n\n
\n
1.5.1<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n