by maksonlee
0 (0 reviews)
Content Version for Git
GitHub-backed version history for WordPress posts, pages, and media.
Compatible with WP 7.0.2
v0.1.8
Current Version v0.1.8
Updated 6 days ago
Last Update on 12 Jul, 2026
Refreshed 9 hours ago
Last Refreshed on
Rank
#50,254
—
No change
Active Installs
0+
—
No change
KW Avg Position
115.5
—
No change
Downloads
203
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
29,682
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#50,254
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 2 of 2Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.1.8
- Last Updated
- Jul 12, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.0.2
- PHP Version
- 7.4 or higher
- Author
- maksonlee
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowFrequently Asked Questions
Common questions about Content Version for Git
GitHub is the version store. The plugin reads and writes versions through the GitHub API without a local Git repository.
No. It adds a Git-backed version history for selected WordPress resources.
No. The GitHub version store is disabled until an administrator enables it and provides a repository URL, branch, and token. Without GitHub configured, versions are not durably stored and the plugin does not keep a local Git repository.
Create the repository in GitHub before configuring the plugin. The repository can be private or public, but private is strongly recommended because content versions can include unpublished content, metadata, and media files. The repository may be empty. If it is empty, the plugin can initialize the configured branch on the first write.
Yes, but a dedicated repository or dedicated branch is strongly recommended. Normal version writes use the current branch head as the parent commit and preserve unrelated files. If the branch already contains Content Version for Git files under posts/, pages/, or media/, use Rebuild GitHub Index after connecting it to a site that has not indexed it yet.
Reset GitHub Version Store rewrites the configured branch to a new empty history. WordPress content is not deleted, but unrelated files and commits on that branch will no longer be part of the branch history after reset.
Use a token that can read and write contents in the selected repository. For fine-grained personal access tokens, select the version-store repository and grant Contents read and write access.
The version is not stored. Configure GitHub before relying on the plugin for durable version history.
Only when media tracking is enabled. In that mode, referenced media metadata and files are committed directly to GitHub.