IvanRF

<a href="https://ivanrf.com/en/github-release-downloads/" rel="nofollow ugc">GitHub Release Downloads</a> allows you to get the download count, links and more information for releases of GitHub repositories.
<h4>Download count</h4>
The shortcode is <code>[grd_count]</code>. It returns a number corresponding to the sum of all download count values for the selected releases. For instance, you can get the number of total downloads for one GitHub repository.
Attributes
<ul>
<li><code>user</code>: the GitHub username.</li>
<li><code>repo</code>: the GitHub repository name.</li>
<li><code>latest</code>: only gets information about the latest published release for the repository.</li>
<li><code>tag</code>: only gets information about the release with the specified tag name.</li>
<li><code>prereleases</code>: includes draft releases and prereleases. Default value is <code>false</code>.</li>
</ul>
Examples
<ul>
<li>All repository downloads: <code>[grd_count user="IvanRF" repo="MassiveFileRenamer"]</code></li>
<li>Latest release downloads: <code>[grd_count user="IvanRF" repo="MassiveFileRenamer" latest="true"]</code></li>
<li>Specific release downloads: <code>[grd_count user="IvanRF" repo="MassiveFileRenamer" tag="v1.6.0"]</code></li>
</ul>
Note: <code>user</code> and/or <code>repo</code> can be omitted if default values are set.
<h4>Release downloads list</h4>
The shortcode is <code>[grd_list]</code>. It returns an HTML list for the selected releases including the release tag name, the release description and the list of files that can be downloaded, like release assets or the source code. 
For styling, class selectors are provided (e.g.: <code>release-downloads-header</code>, <code>release-name</code>, etc.).
Attributes
<ul>
<li><code>user</code>, <code>repo</code>, <code>latest</code>, <code>tag</code>, <code>prereleases</code>: same as above.</li>
<li><code>hide_description</code>: hides the release description.</li>
<li><code>hide_size</code>: hides information about the file size.</li>
<li><code>hide_downloads</code>: hides information about the download count.</li>
<li><code>downloads_suffix</code>: use it for internationalization. Default value is <code>" downloads"</code>.</li>
<li><code>hide_source_code</code>: hides the download link for the source code.</li>
</ul>
Examples
<ul>
<li>All repository downloads: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer"]</code></li>
<li>Latest release downloads: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer" latest="true"]</code></li>
<li>Specific release downloads: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer" tag="v1.5.6"]</code></li>
<li>Hide file size: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer" hide_size="true"]</code></li>
<li>Hide downloads count: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer" hide_downloads="true"]</code></li>
<li>Downloads suffix change: <code>[grd_list user="IvanRF" repo="MassiveFileRenamer" downloads_suffix="descargas"]</code></li>
</ul>
Boolean attributes can take any of this values: “1”, “true”, “on” and “yes”; or “0”, “false”, “off” and “no”.
<h4>Latest version</h4>
The shortcode is <code>[grd_latest_version]</code>. It returns the tag name of the latest published full release. 
For tag names like “v1.6.0”, it returns “1.6.0” as the version number.
Attributes
<ul>
<li><code>user</code>, <code>repo</code>, <code>prereleases</code>: same as above.</li>
</ul>
<h4>Settings</h4>
Under WordPress Settings menu you will find the GitHub Release Downloads options page. In this page you can set values for the GitHub username and the repository name to use by default in the shortcodes.
If both values are set, the shortcodes can be used without attributes (e.g.: <code>[grd_count]</code>) since default values for <code>user</code> and <code>repo</code> will be used. 
Attribute values take precedence over default values. For example, <code>[grd_count repo="MyRepo"]</code> will use the username default value and the repository specified in the shortcode.

GitHub Release Downloads

Get the download count, links and more information for releases of GitHub repositories.

10up

Thorsten Ott

Jake Goldman

Ben Word

Auto Release Posts for GitHub monitors GitHub repositories for new releases and uses AI to research each release and generate a human-readable blog post about it. Posts can be automatically published or held as drafts for review, with email notifications when new posts are ready.
Built on the AI Client API and Connectors introduced in WordPress 7.0 — configure your AI provider (Anthropic, OpenAI, Google, or any other connector) once under Settings → Connectors, and this plugin uses whatever you’ve set up. No AI API keys to manage in the plugin itself.
How it works:
<ol>
<li>Monitor — Add any GitHub repository and the plugin checks for new releases daily via WP-Cron.</li>
<li>Generate — When a new release is detected, the AI researches the release and writes a blog post tailored to your audience.</li>
<li>Publish — Posts are created as drafts for review, or published automatically based on your per-repository settings.</li>
</ol>
You can also generate a post on demand at any time from the Repositories tab.
Features:
<ul>
<li>Monitor multiple GitHub repositories for new releases</li>
<li>AI-powered post generation via WordPress Connectors — works with Anthropic, OpenAI, Google, and any other configured connector</li>
<li>Significance-aware content — patch, minor, major, and security releases get tailored tone and structure</li>
<li>Choose the research depth — Standard reviews release notes, linked issues and PRs, metadata, and the README; Deep adds commit messages and file changes since the last release</li>
<li>SEO-friendly post slugs and excerpts generated automatically by AI</li>
<li>Configurable publish/draft workflow with per-repository overrides</li>
<li>Per-repository post defaults (categories, tags, post status)</li>
<li>Choose your post title format — prefix with project name and version, version only, or no auto-prefix (let the AI write the full title in single-project sites)</li>
<li>Generate posts on demand for any historical release — pick from a version dropdown when a repo has multiple releases; older releases are automatically backdated to keep the archive in chronological order</li>
<li>Custom prompt instructions to guide AI writing style, tone, and voice</li>
<li>Regenerate posts with feedback — refine AI output directly from the block editor sidebar</li>
<li>Email notifications on draft creation, publication, or both</li>
<li>Source attribution in the block editor — see which GitHub release generated each post</li>
<li>Idempotency — the same release never creates duplicate posts</li>
<li>Optional project link support — enter a URL or WordPress.org slug for download CTAs</li>
<li>Optional pre-release tracking per repository — track stable releases by default, or opt in to include betas, release candidates, and other pre-release versions</li>
</ul>
For developers:
<ul>
<li>Extensible via filter hooks at every stage of the pipeline</li>
<li>Customize preferred AI models via the <code>ghrp_wp_ai_client_model_preferences</code> filter</li>
<li>Override significance classification, prompt content, post terms, and post status per-release</li>
<li>All prompt templates defined in code, versioned with the plugin</li>
</ul>
Requirements:
<ul>
<li>WordPress 7.0 or later</li>
<li>PHP 8.2 or later</li>
<li>At least one AI connector configured under Settings → Connectors (Anthropic, OpenAI, or Google recommended)</li>
</ul>
Auto Release Posts for GitHub is an independent project. It is not affiliated with, endorsed by, or sponsored by GitHub, Inc. or the WordPress Foundation. “GitHub” and “WordPress” are used here for descriptive purposes only.
<h3>External Services</h3>
This plugin connects to external services to fetch release data and (via WordPress Connectors) generate post content. Each service is described below.
GitHub REST API
<ul>
<li>What it is: GitHub’s REST API (<code>https://api.github.com</code>) is used to read release data and repository metadata, and — when a Personal Access Token is configured — to list repositories the token can access.</li>
<li>What is sent: HTTP requests to <code>api.github.com</code> containing the repository owner and name. If a GitHub Personal Access Token is configured (in the Settings tab, or via the <code>GHRP_PAT</code> constant or environment variable), the token is sent in the Authorization header.</li>
<li>When it is sent: Daily via WP-Cron (configurable via the <code>ghrp_check_frequency</code> filter), and on demand when generating, regenerating, or refreshing posts from the plugin’s admin screens.</li>
<li>Terms of Service: <a href="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service" rel="nofollow ugc">https://docs.github.com/en/site-policy/github-terms/github-terms-of-service</a></li>
<li>Privacy Policy: <a href="https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement" rel="nofollow ugc">https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</a></li>
</ul>
Image sideloading from GitHub-hosted domains
<ul>
<li>What it is: When AI-generated post content references images hosted on <code>github.com</code>, <code>githubusercontent.com</code>, or <code>github.io</code>, the plugin downloads those images to the WordPress Media Library so posts render without external image dependencies.</li>
<li>What is sent: HTTP GET requests to the specific image URLs referenced by the AI output. No data beyond a standard HTTP request.</li>
<li>When it is sent: At post creation or regeneration time, for image URLs included in the AI-generated content. The allowed domains and limits are configurable via the <code>ghrp_sideload_allowed_domains</code>, <code>ghrp_max_sideload_images</code>, <code>ghrp_sideload_time_budget</code>, and related filters.</li>
<li>Terms of Service and Privacy Policy: same as GitHub above.</li>
</ul>
AI providers (via WordPress Connectors)
<ul>
<li>What it is: AI-generated post content is produced by whichever AI connector you have configured under Settings → Connectors in WordPress 7.0+. The plugin does not call AI provider APIs directly — it dispatches prompts through the WordPress AI Client API.</li>
<li>What is sent: The release title, release notes body, repository metadata (owner/name, language, description), and any custom prompt instructions you have configured are sent to the AI provider selected by your connector. Optional Deep research mode additionally sends recent commit messages and file change summaries between releases.</li>
<li>When it is sent: When a new release is detected by the daily scheduled check, when you click “Generate post” or “Regenerate,” and when regenerating from the block editor sidebar.</li>
</ul>
Privacy and terms for the AI provider depend on which connector is configured. Common providers:
<ul>
<li>Anthropic — <a href="https://www.anthropic.com/legal/consumer-terms" rel="nofollow ugc">Terms</a> — <a href="https://www.anthropic.com/legal/privacy" rel="nofollow ugc">Privacy</a></li>
<li>OpenAI — <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">Terms</a> — <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">Privacy</a></li>
<li>Google AI — <a href="https://policies.google.com/terms" rel="nofollow ugc">Terms</a> — <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy</a></li>
</ul>
<h3>Source Code</h3>
The complete, human-readable source code for this plugin is published at: 
https://github.com/jakemgold/github-release-posts-wordpress
Bundled JavaScript. The minified files under <code>dist/js/</code> are built from the source files under <code>assets/js/</code> using the @10up/scripts toolkit (which wraps Webpack). To rebuild:
<pre><code>npm install && npm run build
</code></pre>
Source-to-build mapping:
<ul>
<li><code>dist/js/admin.js</code> is built from <code>assets/js/admin/index.js</code></li>
<li><code>dist/js/editor.js</code> is built from <code>assets/js/editor/index.js</code></li>
<li><code>dist/css/admin-style.css</code> is built from <code>assets/css/admin/style.css</code></li>
</ul>
Both source and build outputs ship with the plugin, so the source is available locally as well as in the public repository.
Third-party libraries. The plugin has no third-party PHP dependencies. The <code>vendor/</code> directory only contains Composer’s own PSR-4 autoloader scaffolding generated from the plugin’s own classes — it does not include any external libraries. The <code>composer.json</code> <code>require</code> block requires only <code>php: >=8.2</code>. PAT encryption uses libsodium, which has been part of PHP core since 7.2.
Bundled npm packages used at build time (development only — not shipped at runtime): <code>@10up/scripts</code> (which itself bundles Webpack, ESLint, Babel, and the build-time-only <code>wp-prettier</code> and <code>eslint-plugin-jsdoc</code> overrides). All declared in <code>package.json</code> and <code>package-lock.json</code>. None of these end up in the distributed plugin.

Auto Release Posts for GitHub


We have over dozen plugins and providing detailed updates for each release is a real pain.



Auto Release Posts for GitHub does a great job of making this easy. I highly recommend this as a tool for plugin developers.


Excellent, helpful plugin

Automatically generate blog posts from GitHub releases using AI.

GitHub Release Downloads vs Auto Release Posts for GitHub