Deploy to GitHub Pages

Before you start

• A GitHub account
• A repository you want to publish from Swebsy

• A GitHub personal access token with repo scope, or a fine-grained token with read/write access to the target repository

If you are using Private repositories

GitHub Pages is available for public repositories on GitHub Free. Publishing from a private repository requires GitHub Pro for personal accounts, or GitHub Team/Enterprise for organization repositories.

One-time setup

1. Click Settings in the topbar, then open the Deployment tab.
2. Under GitHub Pages, paste your personal access token.
3. Click Test connection to confirm the token can access GitHub.

4. Pick a Repository from the list. If it is not listed, create it on GitHub first, then refresh the repository list in Swebsy.

5. Optionally enter a custom domain (e.g. www.example.com). Swebsy writes a CNAME file for you.

6. Click Save.

GitHub Pages configuration lives in Settings → Deployment.

Deploy

1. Click the Deploy menu in the topbar.
2. Select GitHub Pages.

3. The Deploy review modal opens, showing the target repository, live URL, pages, upload size, and any warnings.

4. Review the plan, then click Deploy now.

5. A progress indicator shows while Swebsy builds and publishes your site to GitHub.

Choose GitHub Pages from the Deploy menu.

Review the generated deployment plan before clicking Deploy now.

Expected result

Your site is live at https://<owner>.github.io/<repo>/ (or your custom domain if configured). The first deploy may take a minute for GitHub to activate Pages.

Custom domain

After deploying with a custom domain configured:

1. In your DNS provider, add a CNAME record pointing www.example.com → <owner>.github.io.
2. In your GitHub repository settings, go to Pages and verify the custom domain.

GitHub automatically sets up a secure https:// connection for your domain (takes a few minutes).

Common issues

“Permission denied” error — your token needs repo scope (classic), or fine-grained permissions that let Swebsy write repository contents and configure Pages for the selected repository. Check the token’s permissions on GitHub.

Repository not listed — confirm the token can access that repository, then refresh the repository list. For fine-grained tokens, make sure the repository is included in the token’s repository access list.

Blank page after deploy — GitHub Pages may need a few minutes to activate on first deploy. Also check Settings → Pages in the repository to confirm it is publishing from the gh-pages branch.

Custom domain shows a certificate error — DNS changes take time to propagate. Wait 15–30 minutes and try again.

Assets load with wrong paths — if your repository is at owner/repo, assets should be relative-path referenced. Check that you haven’t hardcoded absolute paths starting with /.