Deployment
Trigger automated GitHub Actions workflows, push to WP.org SVN, or release premium builds directly to the Freemius API — all from the build result screen.
Three Deployment Channels
After a successful build, Step 4 gives you direct access to all three release paths — from a single screen, without switching tools or opening a terminal.
↗ GitHub → FREE
Pushes the FREE ZIP to the free branch of your GitHub repository. Available in all editions. Use this as your starting point before triggering any further deployment.
↗ GitHub → WP.org PRO
Pushes the FREE ZIP to GitHub and triggers a GitHub Actions workflow that deploys to WordPress.org via SVN. Requires WPORG_USERNAME and WPORG_PASSWORD stored as GitHub Secrets.
↗ GitHub → Freemius PRO
Transfers the PRO ZIP directly to the Freemius API and releases the version automatically. Requires FREEMIUS_BEARER_TOKEN stored as a GitHub Secret in your repository.
GitHub as the Deployment Hub
Every deployment channel routes through GitHub. This keeps your release history version-controlled, auditable, and recoverable — and lets GitHub Actions do the heavy lifting for SVN and Freemius.
Repository Setup
On the first deployment to a new repository, use the ⚙️ Initialize GitHub Repo button. It creates the required branch structure and installs the necessary GitHub Actions workflow files automatically.
Branch Convention
The FREE build is pushed to the free branch. The PRO build is handled by a separate workflow triggered by the Freemius push. Both share the same repository, clearly separated by branch.
Per-Dataset Credentials
GitHub Repo and Personal Access Token are stored in your active dataset. Switching between plugins in the workspace also switches the deployment target — no manual reconfiguration needed.
Prerequisites
Deployment requires a few one-time setup steps. Once configured, every subsequent release is a single click.
GitHub PAT
Create a Personal Access Token on GitHub with repo scope. Save it in your BuildHub dataset under GitHub PAT. This token is used to authenticate the ZIP push from BuildHub to your repository.
WP.org GitHub Secrets
In your GitHub repository, add two Secrets: WPORG_USERNAME (your WordPress.org username) and WPORG_PASSWORD (your WordPress.org application password). The GitHub Action reads these during the SVN push.
Freemius Bearer Token
In your GitHub repository, add the Secret FREEMIUS_BEARER_TOKEN from your Freemius developer dashboard. Also save your Freemius product ID in your BuildHub dataset. The workflow uses both to authenticate the API release.
Downloads
All three build archives are available for direct download from Step 4 — independently of any deployment channel.
🟠 DEV ZIP
Your working copy with injected headers. Use it for local testing and as the source for your next build cycle.
🟢 FREE ZIP
Your wp.org-ready version with all PRO blocks, Freemius stubs, and SDK references removed. Submit directly to WordPress.org or distribute freely.
🔵 PRO ZIP PRO
Your premium build with the full codebase intact. Distribute via Freemius or any other premium channel.
Build once. Deploy everywhere.
From a single DEV ZIP to GitHub, WP.org SVN, and Freemius — in one workflow, without leaving the workspace.