Run a cleaner plugin delivery channel from GitHub.
Git Repos Manager lets WordPress admins discover repositories tagged with wp-plugin, install release ZIP assets through the native upgrader, and selectively track active plugins for update checks.
Example admin view for Available Plugins.
The interface works better as a standalone product preview than as a cramped hero aside. This gives the repository list, install actions, and source-profile controls enough horizontal room to read cleanly.
A WordPress-native admin screen for browsing eligible repositories, resolving release assets, and deciding which plugins should participate in ongoing update checks.
wp-plugin topic so discovery stays intentional.
.zip release asset with the expected content type.
A repo-backed plugin workflow that stays native to WordPress.
This product keeps GitHub as the source of truth without forcing admins into a foreign interface. Discovery, installation, release metadata, authenticated downloads, and update checks all stay inside WordPress conventions.
Discovery by topic
Repositories only appear when they are explicitly tagged with wp-plugin, which keeps the plugin list intentional instead of dumping every repo in an org.
Native install flow
Release ZIP assets are installed through the WordPress upgrader stack, so the experience stays familiar to admins and compatible with core plugin handling.
Active repo tracking
Admins can mark repositories active for update checks, so only approved plugins participate in the GitHub-backed update lifecycle.
Private repo support
Per-source PATs unlock private repositories and authenticated asset downloads, with token resolution matched by repository owner instead of one global credential.
Cache and lockout controls
Repository and release payloads are cached, a rate-limit lockout prevents thrashing the API, and the settings page exposes a force-check utility when you need fresh data now.
Operational clarity
Auth failures, missing releases, bad ZIP assets, and not-found responses are surfaced with explicit admin-facing error messages instead of silent failure modes.
Connect sources first. Distribute plugins second.
The setup flow is straightforward, but the product stays opinionated where it matters: source-level credentials, topic filtering, release asset validation, and explicit active-repo selection.
Add one or more GitHub user or organization targets. Each source can carry its own optional PAT.
Use the wp-plugin topic, create a release, and attach a real .zip asset.
The plugin builds a clean list of eligible repositories, latest versions, install actions, and active toggles.
Flush caches and trigger update checks from the settings page when a release just shipped and you need the admin to reflect it immediately.
Repeatable source rows
Each source stores a target name and optional PAT. That makes public orgs, private client repos, and mixed environments manageable without awkward credential reuse.
Release asset discipline
The installer prefers ZIP assets from the latest published release and falls back carefully, which means your release process stays explicit and auditable.
Admin-native install actions
Install, uninstall, active-state saving, settings notices, and update integration all sit inside WordPress conventions instead of bolted-on custom flows.
Owner-matched token lookup
The plugin resolves a token per repository owner, which is the right mental model when one admin instance needs to talk to multiple GitHub accounts or orgs.
From GitHub release to WordPress update notice.
The product story here is operational confidence: discover repos, install from release assets, keep selected plugins active for checks, and let WordPress core surface version changes in a familiar way.
Query configured users or orgs and filter down to repos that explicitly declare themselves as WordPress plugins.
Pull the newest published release, fall back to release lists when needed, and reject incomplete release metadata.
Use the native upgrader and inject GitHub auth headers only for approved GitHub asset hosts when private downloads are involved.
Only repositories marked active are included in ongoing update checks, which keeps governance explicit for site owners.
Built for admins who need predictable behavior, not magic.
The strongest part of the product is restraint. It narrows discovery, validates releases, scopes credentials by source, and handles bad API states explicitly.
One-hour lockout
When GitHub rate limiting is detected, requests pause instead of hammering the API. That protects both reliability and operator sanity.
Host-restricted auth injection
Authorization headers are only injected for allowed GitHub hosts and asset endpoints, which reduces accidental credential leakage paths.
Useful admin notices
Missing releases, invalid repo names, auth failures, and transport problems surface as actionable WordPress notices instead of vague silent breakage.
Turn GitHub releases into a real plugin channel.
Git Repos Manager is for teams that want WordPress-native installs and updates without giving up GitHub as the source of truth for plugin distribution.