maksonlee

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:
<ul>
<li>Automatic Git versions for normal post and page saves.</li>
<li>Side-by-side content diffs and field diffs.</li>
<li>Full restore and content-only restore modes.</li>
<li>Deleted Resources view for posts, pages, and tracked media.</li>
<li>Restore deleted posts/pages as new drafts and deleted media as new attachments.</li>
<li>Optional media metadata and file tracking.</li>
<li>Manual import of existing posts, pages, and media.</li>
<li>Version store dashboard with branch, latest commit, tracked file count, and GitHub version store status.</li>
<li>Direct GitHub API commits without a local Git worktree.</li>
</ul>
<h3>External Services</h3>
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.
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:
<ul>
<li>https://docs.github.com/en/site-policy/github-terms/github-terms-of-service</li>
<li>https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</li>
</ul>

Content Version for Git

GitHub-backed version history for WordPress posts, pages, and media.

RobertGillmer

This plugin is built to be used on production servers which are version-controlled with Git. If plugins are updated directly on production, they can get out of sync with the repo, and later pushes to the server might “roll back” plugin updates which weren’t committed to the repo.
Users who try to update a plugin via the Plugins screen will get a modal window asking for confirmation. Admins can also block updates entirely, so users will still get the modal window but will only have a cancel button.
The modal title and modal content are admin-configurable through the options page.
Please understand, we’re not advocating not updating plugins. You should still update all the things with the quickness. Just do it in the repo and push the changes to the server.

Protect Version Controlled Updates

This plugin warns or prevents users from updating plugins on a Git version-controlled server.

Content Version for Git vs Protect Version Controlled Updates