Hosting Shared Hosting Managed WordPress Hosting Reseller Hosting Managed VPS
Email Email Sending Email Archiving
Free Tools Mail Tester Email Migration Website Security Scanner Secure File Transfer
Resources Knowledgebase Blog Server Status
About Contact
Region πŸ‡ΏπŸ‡¦ South Africa (R) πŸ‡¬πŸ‡§ United Kingdom (Β£)
Client Login
βš™οΈ Enhance Panel Intermediate

Deploying a Website from GitHub

October 20, 2026 8 min read 0 views

Deploying a website from GitHub

Your control panel can deploy a website straight from a GitHub repository — once by hand, or automatically every time you push. This guide covers connecting GitHub, deploying to a new or existing website, and checking how a deployment went.

Step 1: connect your GitHub account

  1. Log in to your control panel.
  2. Choose GitHub connection in the left-hand menu.
  3. Click Connect GitHub and approve access in GitHub.
The GitHub connection page in the control panel, with the Connect GitHub button.

Once connected, the page shows the GitHub owner and the repositories the panel can see, with a Deploy button beside each one. Both public and private repositories work — private ones appear because you granted access when connecting.

A connected GitHub account in the control panel, listing a repository with its branch, visibility and a Deploy button.

Step 2a: deploy to a new website

When you add a website, choose Deploy from GitHub. Enter the domain, pick the repository and the branch or tag, and decide whether to turn on Auto deploy on push.

The Add website screen with Deploy from GitHub selected, showing domain, repository, branch, auto deploy, build script and publish directory fields.
  • Build script — optional commands run after the repository is cloned, such as installing dependencies or building the site.
  • Publish directory — where your built static files end up, if your project produces them.

Step 2b: connect a repository to an existing website

Open the website and choose the GitHub tab. Pick the repository and branch, set the build options, and choose whether the app needs a worker process (Node.js, Laravel, PHP or a custom command) to keep it running.

The Configure GitHub deploy screen, with repository, branch, auto deploy on push, build script, publish directory and worker process options.

Production or staging

A deployment goes to the website you set it up on. To test changes safely, connect the repository to a staging website — often on a test branch — and to your live website from your main branch.

Deploy manually or automatically

  • Manually: on the website's GitHub page, click Deploy now.
  • Automatically: turn on Auto deploy when pushed to GitHub. Every push to the chosen branch then deploys on its own.

Check deployment status and errors

The Deployments list shows each deployment, the commit it used, how it was triggered and whether it succeeded. Click View logs to see exactly what happened — if a deployment fails, the log usually says why.

The Deployments list for a website, showing a successful manual deployment with its log open.

Change or disconnect the repository

  • To change the branch or repository for a website, use the edit (pencil) icon next to the connected repository on its GitHub page.
  • To remove the link to your GitHub account altogether, use Disconnect account on the GitHub connection page.

Getting help

If a deployment fails because of the hosting environment — for example a missing runtime or a permissions problem on the server — open a support ticket with the website name and the deployment log.

Please note: Go Red Robot supports the hosting environment and deployment tools. Application development, repository configuration and code debugging are not included with hosting support.

Was this helpful?