Auto Release Posts for GitHub vs Code Engine – PHP Snippets, AI Functions & Automation for WordPress

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: Monitor — Add any GitHub repository and the plugin checks for new releases daily via WP-Cron. Generate — When a new release is detected, the AI researches the release and writes a blog post tailored to your audience. Publish — Posts are created as drafts for review, or published automatically based on your per-repository settings. You can also generate a post on demand at any time from the Repositories tab. Features: Monitor multiple GitHub repositories for new releases AI-powered post generation via WordPress Connectors — works with Anthropic, OpenAI, Google, and any other configured connector Significance-aware content — patch, minor, major, and security releases get tailored tone and structure 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 SEO-friendly post slugs and excerpts generated automatically by AI Configurable publish/draft workflow with per-repository overrides Per-repository post defaults (categories, tags, post status) 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) 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 Custom prompt instructions to guide AI writing style, tone, and voice Regenerate posts with feedback — refine AI output directly from the block editor sidebar Email notifications on draft creation, publication, or both Source attribution in the block editor — see which GitHub release generated each post Idempotency — the same release never creates duplicate posts Optional project link support — enter a URL or WordPress.org slug for download CTAs Optional pre-release tracking per repository — track stable releases by default, or opt in to include betas, release candidates, and other pre-release versions Monorepo support — per-repository tag patterns limit posts to selected packages (e.g. @headstartwp/core@*, @headstartwp/next@*) when one repository releases many packages For developers: Extensible via filter hooks at every stage of the pipeline Customize preferred AI models via the ghrp_wp_ai_client_model_preferences filter Override significance classification, prompt content, post terms, and post status per-release All prompt templates defined in code, versioned with the plugin Requirements: WordPress 7.0 or later PHP 8.2 or later At least one AI connector configured under Settings → Connectors (Anthropic, OpenAI, or Google recommended) 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. External Services 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 What it is: GitHub’s REST API (https://api.github.com) is used to read release data and repository metadata, and — when a Personal Access Token is configured — to list repositories the token can access. What is sent: HTTP requests to api.github.com containing the repository owner and name. If a GitHub Personal Access Token is configured (in the Settings tab, or via the GHRP_PAT constant or environment variable), the token is sent in the Authorization header. When it is sent: Daily via WP-Cron (configurable via the ghrp_check_frequency filter), and on demand when generating, regenerating, or refreshing posts from the plugin’s admin screens. Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement Image sideloading from GitHub-hosted domains What it is: When AI-generated post content references images hosted on github.com, githubusercontent.com, or github.io, the plugin downloads those images to the WordPress Media Library so posts render without external image dependencies. What is sent: HTTP GET requests to the specific image URLs referenced by the AI output. No data beyond a standard HTTP request. 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 ghrp_sideload_allowed_domains, ghrp_max_sideload_images, ghrp_sideload_time_budget, and related filters. Terms of Service and Privacy Policy: same as GitHub above. AI providers (via WordPress Connectors) 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. 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. 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. Privacy and terms for the AI provider depend on which connector is configured. Common providers: Anthropic — Terms — Privacy OpenAI — Terms — Privacy Google AI — Terms — Privacy Source Code 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 dist/js/ are built from the source files under assets/js/ using the @10up/scripts toolkit (which wraps Webpack). To rebuild: npm install && npm run build Source-to-build mapping: dist/js/admin.js is built from assets/js/admin/index.js dist/js/editor.js is built from assets/js/editor/index.js dist/css/admin-style.css is built from assets/css/admin/style.css 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 vendor/ 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 composer.json require block requires only php: >=8.2. 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): @10up/scripts (which itself bundles Webpack, ESLint, Babel, and the build-time-only wp-prettier and eslint-plugin-jsdoc overrides). All declared in package.json and package-lock.json. None of these end up in the distributed plugin.

Code Engine is a snippets manager that doesn’t stop at snippets. Yes, it runs your PHP and JavaScript exactly where and when you want: frontend, backend, on a schedule, or inside your content. But its real magic is what happens after you write a function: the same little piece of code instantly becomes a tool your AI chatbots can call, a step you can drag into a visual workflow, and an endpoint the outside world can trigger. One function, three superpowers. Most “code snippets” plugins stop at a textarea and a toggle. Code Engine treats your functions as first-class building blocks for the whole Meow Apps ecosystem, and for anything that can speak REST. Think out of the box, let your creativity flow, because the possibilities really are endless! ✨ For more, check the official website and come say hi on the Discord. Quick Intro Hello! ☀️ I built Code Engine because I was tired of pasting mystery snippets into functions.php and praying. I wanted a place where small bits of code are organized, safe, AI-assisted, and reusable everywhere. Here’s the idea. You write a function (or let the AI write it for you from a plain-English description). That function immediately shows up in three places: AI Engine: your chatbots and MCP clients (Claude, ChatGPT, Claude Code) can call it as a tool, with real arguments. Ask “how many orders shipped today?” and your chatbot runs your function to answer. Workflow Engine: your function appears in the step picker as its very own block. Drag it onto the canvas, wire it between an AI step and a Slack step, done. No glue code. REST / External tools: give it a secure endpoint and a token, then trigger it from Make.com, n8n, Zapier, a cron job, or a webhook. You never wrote an “integration.” You just wrote a function. Code Engine did the rest. 🤝 Core Modules 🧩 Snippets Manager Backend, Frontend, Persistent, Scheduled, Functions, and in-content (PHP/JS) snippets, all in one clean dashboard with tags, search, scope filters, and priorities. 🪄 AI-Assisted Coding Describe what you want in plain English and let AI Engine write the snippet: code, name, arguments, and scope included. Refine existing code or implement it straight from your comments. 🤖 Functions as AI Tools Every Function snippet becomes a function-calling tool and an MCP tool, so your AI Engine chatbots (and external AI agents) can actually do things on your site, not just talk. 🔀 Functions as Workflow Steps Workflow Engine surfaces each of your functions as its own draggable step. Your custom logic becomes a first-class citizen on the automation canvas. 🌐 External Access (REST) Expose any runnable snippet through a secured REST endpoint with a bearer token. Perfect for Make.com, n8n, webhooks, and scheduled external jobs. 🛡️ Safe Mode A snippet that throws a fatal error is automatically caught and disabled before it can take your site down. Code with confidence. ⏰ Scheduling Run a snippet daily at a chosen time via WP-Cron (reports, cleanups, syncs) without touching the server crontab. 🧱 Code Blocks & Shortcodes (Pro) Drop PHP or JS straight into a post or page with a Gutenberg block or the [code-engine] shortcode, with safety guards. 🧩 Snippets, the way they should be Code Engine organizes your code by scope, so each snippet runs exactly where it belongs: Persistent: runs everywhere (frontend and backend). Your everyday “add this to functions.php” code, but managed. Frontend: runs only on the public site. Backend: runs only in the admin. Function: a named, callable function with typed arguments and defaults. This is the reusable building block (see below). Scheduled: runs on a WP-Cron schedule, at the hour and minute you pick. Content (PHP / JS): runs inside a specific post or page, via a Gutenberg Code Block or the [code-engine] shortcode (Pro). Everything is searchable, taggable, sortable by priority, and importable/exportable. The CodeMirror editor gives you proper syntax highlighting and keyboard shortcuts (Cmd+S to save, Cmd+Enter to run). A nikic/php-parser pass validates your PHP before it ever runs. 🪄 Let AI write it for you Don’t feel like writing the boilerplate? Describe the snippet in plain language and Code Engine, powered by AI Engine, generates the whole thing: the code, a sensible name, a description, the right scope, and, for functions, the argument list with names, types, and defaults. Already have code? Ask the AI to modify it from a prompt, or write a few comments describing what you want and let it fill in the implementation. It’s pair programming, right inside your dashboard. ✨ The big idea: write once, use everywhere This is what makes Code Engine different. A Function snippet is not just code you call from other code. It’s a reusable capability that the rest of your stack can plug into. The moment you save it, the same function is available in three places at once: 1. As an AI tool, for chatbots and AI agents With AI Engine active, your functions are exposed through function calling and over MCP (Model Context Protocol). Your on-site chatbot can run them mid-conversation, and external AI agents (Claude, Claude Code, ChatGPT, OpenClaw) can call them too. Want a chatbot that checks stock, looks up a booking, or kicks off a process? Write the function; the chatbot gains the skill. 2. As a workflow step, for automation With Workflow Engine, every active function shows up in the Add-step picker as its own block, named after your snippet, with one input per argument. Drag it onto the canvas and wire it between other steps: an AI step that summarizes, your function that saves, a Social Engine step that posts. There’s also a generic “Execute snippet (by ID / by name)” step when you want to call one dynamically. You never write integration code; your function is the integration. 3. As a REST endpoint, for the outside world Give a snippet a custom endpoint name and a bearer token, and it’s instantly callable from anywhere: POST /wp-json/code-engine/v1/snippets-endpoint/your-endpoint Pass arguments as JSON in the body, secure it with a token, and trigger it from Make.com, n8n, Zapier, GitHub Actions, or a humble cron job. Automation without a middleware bill. 🛡️ Safe by default Running arbitrary code is powerful, so Code Engine takes safety seriously: Safe Mode catches fatal errors and auto-disables the offending snippet, so a typo never white-screens your site. REST whitelisting means global snippets only run on trusted REST routes by default, so you choose what to open up. Per-snippet tokens secure your external endpoints. Validation with a real PHP parser before code is saved. For developers who want fewer guardrails, there’s a “Bypass REST Security” option and filters (mwcode_rest_authorized, mwcode_rest_whitelist) to tailor exactly what’s allowed. Works beautifully with the Meow Apps family Code Engine is one engine in a connected set, each one useful alone, magical together: AI Engine: chatbots, content generation, and MCP. Turns your functions into AI tools. Workflow Engine: visual automation. Turns your functions into draggable steps. SEO Engine: smart, lightweight AI SEO. Social Engine: schedule and automate social posts. Why Code Engine? Reusable, not throwaway Other snippet plugins give you a place to paste code. Code Engine gives you a place to build capabilities that your AI, your workflows, and your external tools can all use. Native to WordPress Clean, fast, and built the WordPress way. No clunky external dashboards, no bloat. AI-native Write snippets with AI, expose them to AI. The whole loop lives in your wp-admin. Developer friendly REST API, MCP tools, function calling, scheduling, import/export, and plenty of filters to hook into. Cared for Part of the Meow Apps family, with regular updates and a real human behind it. 💕