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.<\/p>\n\n
Built on the AI Client API and Connectors introduced in WordPress 7.0 \u2014 configure your AI provider (Anthropic, OpenAI, Google, or any other connector) once under Settings \u2192 Connectors, and this plugin uses whatever you've set up. No AI API keys to manage in the plugin itself.<\/p>\n\n
How it works:<\/strong><\/p>\n\n You can also generate a post on demand at any time from the Repositories tab.<\/p>\n\n Features:<\/strong><\/p>\n\n For developers:<\/strong><\/p>\n\n Requirements:<\/strong><\/p>\n\n 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.<\/em><\/p>\n\n This plugin connects to external services to fetch release data and (via WordPress Connectors) generate post content. Each service is described below.<\/p>\n\n GitHub REST API<\/strong><\/p>\n\n Image sideloading from GitHub-hosted domains<\/strong><\/p>\n\n AI providers (via WordPress Connectors)<\/strong><\/p>\n\n Privacy and terms for the AI provider depend on which connector is configured. Common providers:<\/p>\n\n The complete, human-readable source code for this plugin is published at:\nhttps:\/\/github.com\/jakemgold\/github-release-posts-wordpress<\/p>\n\n Bundled JavaScript.<\/strong> The minified files under Source-to-build mapping:<\/p>\n\n Both source and build outputs ship with the plugin, so the source is available locally as well as in the public repository.<\/p>\n\n Third-party libraries.<\/strong> The plugin has no third-party PHP dependencies. The Bundled npm packages used at build time<\/strong> (development only \u2014 not shipped at runtime): The plugin uses WordPress Connectors (built into WordPress 7.0+) to communicate with AI providers. Any connector installed on your site will work. We recommend Anthropic (Claude Opus 4.7), OpenAI (GPT-5.5), or Google (Gemini 2.5 Pro) for best results. Configure your connector under Settings \u2192 Connectors.<\/p><\/dd>\n No. The plugin uses the public GitHub API for public repositories. Adding an optional Personal Access Token raises the API rate limit from 60 to 5,000 requests per hour and replaces the \"owner\/repo\" text field on the Repositories tab with a dropdown of repos the token can access.<\/p><\/dd>\n Yes. Add a GitHub Personal Access Token in the Settings tab. A fine-grained token scoped to the specific repositories you want to monitor is recommended; a classic token with the By default, the plugin checks daily via WP-Cron. Developers can change this to hourly, twice daily, or weekly using the Yes, in two ways. Site owners can enter custom prompt instructions in the Settings tab to guide the AI's writing style, tone, and voice. Developers can use filter hooks ( Yes. Generated posts are standard WordPress posts and can be edited normally in the block editor. A Release Attribution panel in the editor sidebar lets you regenerate the content with optional feedback \u2014 for example, \"make it shorter\" or \"emphasize the security fix.\"<\/p><\/dd>\n A Release Attribution panel appears in the document sidebar, showing which GitHub release the post was generated from with a link to the release notes. From this panel you can also regenerate the post content with feedback.<\/p><\/dd>\n\n<\/dl>\n\n\n Addresses WordPress.org reviewer feedback on prefix consistency.<\/p>\n\n Pre-publication fixes addressing automated and manual review feedback. Since 1.0.0 was withheld during the WordPress.org review process, this is the first version actually shipping to the directory; Composer-installed sites at 1.0.0 should update to pick up the bug fixes below.<\/p>\n\n Bug fixes<\/strong><\/p>\n\n Compliance with WordPress.org Plugin Directory guidelines<\/strong><\/p>\n\n For developers<\/strong><\/p>\n\n New<\/strong><\/p>\n\n\n
\n
\n
ghrp_wp_ai_client_model_preferences<\/code> filter<\/li>\n\n
External Services<\/h3>\n\n
\n
https:\/\/api.github.com<\/code>) is used to read release data and repository metadata, and \u2014 when a Personal Access Token is configured \u2014 to list repositories the token can access.<\/li>\napi.github.com<\/code> containing the repository owner and name. If a GitHub Personal Access Token is configured (in the Settings tab, or via the GHRP_PAT<\/code> constant or environment variable), the token is sent in the Authorization header.<\/li>\nghrp_check_frequency<\/code> filter), and on demand when generating, regenerating, or refreshing posts from the plugin's admin screens.<\/li>\n\n
github.com<\/code>, githubusercontent.com<\/code>, or github.io<\/code>, the plugin downloads those images to the WordPress Media Library so posts render without external image dependencies.<\/li>\nghrp_sideload_allowed_domains<\/code>, ghrp_max_sideload_images<\/code>, ghrp_sideload_time_budget<\/code>, and related filters.<\/li>\n\n
\n
Source Code<\/h3>\n\n
dist\/js\/<\/code> are built from the source files under assets\/js\/<\/code> using the @10up\/scripts toolkit (which wraps Webpack). To rebuild:<\/p>\n\nnpm install && npm run build\n<\/code><\/pre>\n\n\n
dist\/js\/admin.js<\/code> is built from assets\/js\/admin\/index.js<\/code><\/li>\ndist\/js\/editor.js<\/code> is built from assets\/js\/editor\/index.js<\/code><\/li>\ndist\/css\/admin-style.css<\/code> is built from assets\/css\/admin\/style.css<\/code><\/li>\n<\/ul>\n\nvendor\/<\/code> directory only contains Composer's own PSR-4 autoloader scaffolding generated from the plugin's own classes \u2014 it does not include any external libraries. The composer.json<\/code> require<\/code> block requires only php: >=8.2<\/code>. PAT encryption uses libsodium, which has been part of PHP core since 7.2.<\/p>\n\n@10up\/scripts<\/code> (which itself bundles Webpack, ESLint, Babel, and the build-time-only wp-prettier<\/code> and eslint-plugin-jsdoc<\/code> overrides). All declared in package.json<\/code> and package-lock.json<\/code>. None of these end up in the distributed plugin.<\/p>\n\n\n\n
\/wp-content\/plugins\/auto-release-posts-for-github\/<\/code>, or install via the WordPress Plugins screen.<\/li>\n\n
Which AI providers are supported?<\/h3><\/dt>\n
Do I need a GitHub API key?<\/h3><\/dt>\n
Does it work with private repositories?<\/h3><\/dt>\n
repo<\/code> scope also works.<\/p><\/dd>\nHow often does the plugin check for new releases?<\/h3><\/dt>\n
ghrp_check_frequency<\/code> filter.<\/p><\/dd>\nCan I customize the AI-generated content?<\/h3><\/dt>\n
ghrp_prompt<\/code>, ghrp_prompt_title_guidance<\/code>, ghrp_prompt_content_guidance<\/code>) for full control over the prompt sent to the AI.<\/p><\/dd>\nCan I edit or regenerate a post after it's created?<\/h3><\/dt>\n
What shows up in the block editor for generated posts?<\/h3><\/dt>\n
1.0.2<\/h4>\n\n
\n
GITHUB_RELEASE_POSTS_VERSION<\/code>, _URL<\/code>, _PATH<\/code>, _INC<\/code> to GHRP_VERSION<\/code>, GHRP_URL<\/code>, GHRP_PATH<\/code>, GHRP_INC<\/code> for prefix consistency.<\/li>\nGITHUB_RELEASE_POSTS_PAT<\/code> to GHRP_PAT<\/code>. Sites that supplied the token via wp-config.php<\/code> or an environment variable must update the constant\/var name.<\/li>\nctbpAdmin<\/code> \/ ctbpFetch<\/code> to ghrpAdmin<\/code> \/ ghrpFetch<\/code>, completing the v0.9.0 rebrand. Removed remaining [CTBP]<\/code> debug-log prefixes and internal placeholder markers from the v0.9.0 era.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n
\n
\n
if ( ! defined( 'ABSPATH' ) ) exit;<\/code>) added to every PHP class file.<\/li>\nload_plugin_textdomain()<\/code>; WordPress auto-loads translations for plugins hosted on the directory since version 4.6.<\/li>\n$_SERVER['REQUEST_METHOD']<\/code> and $_GET['page']<\/code> now apply isset()<\/code>, wp_unslash()<\/code>, and sanitize_key()<\/code> per WordPress coding standards.<\/li>\n.DS_Store<\/code> \/ .gitkeep<\/code> files from the distribution zip; included composer.json<\/code> and composer.lock<\/code> so reviewers can verify the (no-third-party-PHP-dependencies) manifest.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n
auto-release-posts-for-github<\/code>. The Composer package name (github-release-posts\/github-release-posts<\/code>), main plugin file, PHP namespace, hook prefix (ghrp_*<\/code>), and REST namespace (ghrp\/v1<\/code>) are unchanged \u2014 existing Composer-installed sites are unaffected.<\/li>\n\n
var<\/code> \u2192 let<\/code>\/const<\/code>, template literals, URL.canParse()<\/code> for URL validation, full wp-prettier<\/code> compliance. Build output is byte-stable; runtime behavior is unchanged.<\/li>\neslint-plugin-jsdoc@^46.10.1<\/code> and prettier@npm:wp-prettier@2.2.1-beta-1<\/code> via package.json<\/code> overrides<\/code> to fix a JSDoc plugin crash on Node 20+ and to honor the codebase's WordPress paren-spacing style.<\/li>\n0.11.1<\/h4>\n\n
\n
composer require github-release-posts\/github-release-posts<\/code>) for Composer-managed WordPress sites such as Roots\/Bedrock. Bootstrap now detects when the plugin is loaded through the consumer's Composer autoloader and skips the local vendor\/autoload.php require \u2014 Composer-installed sites no longer see the spurious \"missing Composer dependencies\" admin notice that 0.11.0 surfaced.<\/li>\n<\/ul>\n\n0.11.0<\/h4>\n\n
\n
owner\/repo<\/code> to track a repository that isn't in the list.<\/li>\nGHRP_PAT<\/code> PHP constant in wp-config.php<\/code> or an environment variable of the same name, for sites that prefer not to store secrets in the database.<\/li>\n