Auto-Deploy WordPress Theme from GitHub to cPanel with GitHub Actions

Manually clicking “Update from Remote” and “Deploy HEAD Commit” in cPanel every time you push gets old fast. In this tutorial we’ll wire up GitHub Actions to do it automatically — push to main, and your live theme updates within seconds.

How it works

Three pieces work together:

• cPanel Git Version Control — clones your GitHub repo directly into the theme directory on the server
• GitHub deploy key — lets the server authenticate with GitHub when pulling
• GitHub Actions + SSH — on every push, Actions SSHs into your server and runs git pull automatically

git push origin main
      ↓
GitHub Actions triggers
      ↓
SSHs into your server
      ↓
git pull in theme directory
      ↓
Live site updated ✅

Prerequisites

• A GitHub repository for your theme
• cPanel hosting with Git Version Control enabled
• SSH access to your server
• Git installed locally

Step 1 — Set up cPanel Git Version Control

In cPanel → Git Version Control → Create:

• Enable Clone a Repository
• Clone URL: your GitHub SSH URL (e.g. git@github.com:username/repo.git)
• Repository Path: the full server path to your theme directory (e.g. /home/username/public_html/site.com/wp-content/themes/your-theme)

Click Create. cPanel will clone the repo into that directory.

Step 2 — Generate an SSH key pair

Run this on your local machine:

ssh-keygen -t ed25519 -C "github-actions-deploy" -f ~/.ssh/github_actions_deploy -N ""

This creates two files:

• ~/.ssh/github_actions_deploy — private key (goes to GitHub Actions)
• ~/.ssh/github_actions_deploy.pub — public key (goes to cPanel)

Step 3 — Add the public key to cPanel

cPanel → SSH Access → Manage SSH Keys → Import Key:

• Name: github-actions-deploy
• Private key: leave empty
• Passphrase: leave empty
• Public key: paste the output of cat ~/.ssh/github_actions_deploy.pub

Click Import, then find the key in the list and click Authorize.

Step 4 — Add GitHub Actions secrets

GitHub → your repo → Settings → Secrets and variables → Actions → New repository secret. Add these three:

Secret name	Value
SSH_HOST	your server domain or IP
SSH_USERNAME	your cPanel username
SSH_PRIVATE_KEY	full contents of ~/.ssh/github_actions_deploy

Step 5 — Add the .cpanel.yml file

Create .cpanel.yml in the root of your theme repository:

---
deployment:
  tasks:
    - echo "Theme deployed successfully"

Since cPanel’s “Clone a Repository” setup places the git working tree directly in the deployment directory, a simple echo is all that’s needed — git pull already updates the files in place. The cp -R approach you’ll see in some tutorials causes “same file” errors in this setup.

Step 6 — Create the GitHub Actions workflow

Create .github/workflows/deploy.yml in your repository:

name: Deploy to cPanel

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      - name: Deploy via SSH
        uses: appleboy/ssh-action@v1.2.0
        with:
          host: ${{ secrets.SSH_HOST }}
          username: ${{ secrets.SSH_USERNAME }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          port: 22
          script: |
            cd /path/to/your/theme
            git pull origin main

Replace /path/to/your/theme with your actual server path.

Step 7 — One-time manual deploy

The .github/workflows/deploy.yml file itself needs to land on the server before auto-deploy can work. Do one final manual deploy:

1. Push everything to GitHub
2. cPanel → Git Version Control → your repo → Pull or Deploy tab
3. Click Update from Remote
4. Click Deploy HEAD Commit

This is the last time you’ll ever need to do this manually.

Test it

Make any small change, push to main, then go to GitHub → Actions tab. You should see the workflow run and complete with a green ✓ within about 10–15 seconds.

Understanding the two SSH keys

A common point of confusion — there are two separate SSH keys doing different jobs:

Key	Private key lives	Public key lives	Purpose
id_rsa (server key)	On your server	GitHub → Deploy keys	Server → GitHub (git pull auth)
github_actions_deploy	GitHub → Actions Secrets	cPanel → SSH Access	GitHub Actions → Server (SSH in)

They work in sequence: Actions uses its key to SSH into the server, then the server uses its own key to authenticate the git pull with GitHub.