Haris Amjed

<p>The Version Control Your Content plugin provides an alternative to the native WP <a href="https://wordpress.org/documentation/article/revisions/" rel="ugc">Revisions</a> feature using Git services.</p>
<h4>Requirements</h4>
<ul>
<li>A GitHub account. If you don’t have one, you can create one <a href="https://github.com/join" rel="nofollow ugc">here</a>.</li>
<li>A GitHub private repository. If you don’t have one, you can create one <a href="https://github.com/new" rel="nofollow ugc">here</a>.</li>
<li>(Optional but highly recommended) A GitHub fine-grained personal access token. If you don’t have one, you can create one <a href="https://github.com/settings/tokens/new" rel="nofollow ugc">here</a>.</li>
</ul>
<p>This plugin provides an option for version control in the following places for now:</p>
<ol>
<li>Block Editor (Gutenberg)</li>
<li>Classic Editor</li>
<li>Additional CSS in the Customizer</li>
<li>Default Settings pages in WP Admin</li>
</ol>
<p>On all supported pages, you will see a “Version Control” box, and you can activate or deactivate it for that page. It will also show you the real-time GitHub API usage in the top admin bar.</p>
<p>This solution will put minimal load on your server because there will be no database entries, no complex SQL operations, and only simple JavaScript-based API calls to external Git services.</p>
<h4>How it works behind the scenes?</h4>
<ol>
<li>When you submit any HTML form, such as saving a post, it captures the form data via JavaScript before sending it to the server backend.</li>
<li>It sanitizes the data and converts it to JSON format (if needed).</li>
<li>It sends that JSON or HTML data to your Git repository via a commit.</li>
<li>In this way, all your changes will be new commits in your Git repo in related JSON or HTML files.</li>
<li>In the commits box, a list of all commits will be shown. It will also provide an option to view the changes or revert to that version.</li>
</ol>
<h4>Planned Upcoming Features</h4>
<p>Currently, I have developed it for three views as described above, and the following features will be added in the future:</p>
<ul>
<li>Integration with page builders like Elementor, Divi, Beaver Builder, WPBakery, etc.</li>
<li>Integration with WooCommerce</li>
<li>Integration with BuddyPress</li>
<li>Integration with bbPress</li>
<li>Integration with WPML, etc.</li>
</ul>


Version Control Your Content

Provides an alternative to the native WP Revisions feature using Git services. Also works for Additional CSS and wp-admin Settings pages.

RobertGillmer

<p>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.</p>
<p>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.</p>
<p>The modal title and modal content are admin-configurable through the options page.</p>
<p>Please understand, we’re not advocating <em>not</em> 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.</p>


Protect Version Controlled Updates

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

Version Control Your Content vs Protect Version Controlled Updates