A GitHub Action to automatically build and deploy Ghost themes to any Ghost installation via the Admin API.
TryGhost/action-deploy-theme is a GitHub Action that automates the deployment of Ghost themes from a GitHub repository to any Ghost installation. It builds and uploads themes via the Ghost Admin API, enabling continuous deployment for theme developers. This eliminates manual uploads and streamlines the theme update process.
Ghost theme developers and teams who manage Ghost themes in GitHub repositories and want to automate deployment to Ghost instances. It's ideal for those using continuous integration workflows.
Developers choose this action because it provides a seamless, automated way to deploy Ghost themes directly from GitHub, reducing manual effort and ensuring consistent deployments. It's officially maintained by the Ghost team, ensuring reliability and compatibility with Ghost's API.
:octocat: Deploy your Ghost theme with Github Actions
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Deploys themes on every commit to specified branches, enabling continuous integration workflows as shown in the example YAML configuration in the README.
Uses Ghost's Admin API for secure uploads to any Ghost instance, including self-hosted setups, ensuring compatibility and reliability as it's maintained by the Ghost team.
Allows customizing theme names, excluding files, specifying working directories, and using pre-built zip files, detailed in the configuration table for tailored deployments.
Requires only API credentials and a simple YAML file to get started, making it easy to integrate into existing GitHub workflows with clear setup steps.
Only works within GitHub Actions, so teams using other CI/CD tools like Jenkins or GitLab CI cannot leverage this action, limiting its applicability.
Designed solely for Ghost CMS, making it useless for projects using WordPress, Jekyll, or other platforms that require theme deployment automation.
Users must manually specify the Ghost API version, which can lead to deployment failures if mismatched, adding complexity compared to auto-detection features.