

Content Versions Dashboard showing version store status, settings, import controls, and GitHub version store configuration.
Content Version for Git stores editable WordPress content snapshots in a configured GitHub repository. It versions posts, pages, terms, and optionally media metadata and original media files. Editors can preview, diff, and restore previous versions from the WordPress admin.
The plugin writes and reads Git objects through the GitHub API. It does not keep a local Git repository and does not call the git CLI.
Features include:
This plugin connects to GitHub when the “Enable GitHub version store” setting is enabled and a repository URL, branch, and personal access token are configured.
When enabled, the plugin writes Git commits directly to the configured GitHub repository using the GitHub API. Commit data may include post/page content, metadata, term references, media metadata, and media files if media tracking is enabled.
Create the GitHub repository before configuring the plugin. The repository may be empty, and the plugin can initialize an empty repository on the first write, but it does not create GitHub repositories. Use a dedicated repository or a dedicated branch for this plugin’s version store. Normal version writes preserve unrelated files on the branch, but Reset GitHub Version Store rewrites the configured branch history.
For fine-grained personal access tokens, select only the version-store repository and grant Contents read and write access. Organization repositories may require organization approval for the token before the plugin can use it.
The GitHub version store is disabled by default. No data is sent to GitHub unless a site administrator enables and configures it. Without the GitHub version store, this plugin does not keep durable local Git versions. GitHub’s terms and privacy policy apply: