I cannot deploy my github pages. The repository size is approximately 100Kb.

[thanakornbua]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

Repository is located at www.github.com/thanakornbua/thanakornbua.github.io
Failed action is: https://github.com/thanakornbua/thanakornbua.github.io/actions/runs/20929168089

[DavitEgoian]

Check that Pages is enabled in the repo settings and that the publishing branch matches what Pages is set to (user sites usually use main). Make sure your workflow uses current actions (upload-pages-artifact@v3 and deploy-pages@v4) and includes permissions: contents: read, pages: write, id-token: write. If you don’t need Jekyll, add a blank .nojekyll file at the repo root. Cancel any stuck/queued runs and push again. If you want, paste your workflow YAML and I’ll look for specific issues.

[realsunil]

Hi @thanakornbua 👋

Repo size (100KB) is not the issue — GitHub Pages deployments usually fail because of config/branch settings or a build error in the Pages workflow.

Here are the most common things to check/fix:

---

✅ 1) Check GitHub Pages settings

Go to:
Repo → Settings → Pages

Make sure:

• Source is set correctly:
  • If you're using Actions: it should show GitHub Actions
  • If you're using branch deployment: set Deploy from a branch
    • Branch: main
    • Folder: / (root) or /docs

---

✅ 2) Confirm your site files exist in the correct place

For normal Pages (no framework):
You must have at least one of these in the deployed folder:

• index.html ✅ (required)

If index.html is missing, Pages will fail or show nothing.

---

✅ 3) Check the Action error logs

Open the failed workflow run:
Actions → latest failed run → click the failing job → expand logs

Common errors:

• No such file or directory
• Build failed
• Permission denied
• wrong Node version / package install error (if using Jekyll/React/Vite)

---

✅ 4) If you are using a framework (React/Vite/Next)

Your Pages workflow must build and upload the dist/build output, not the source code.

Examples:

• Vite → output folder = dist
• React CRA → output folder = build
• Jekyll → output folder = _site

Make sure your workflow uploads the correct folder.

---

✅ 5) Fix by re-creating Pages workflow (easy)

Go to:
Actions → New workflow → Pages → Static HTML
(or Jekyll if you're using it)

This regenerates a correct workflow for GitHub Pages.

---

✅ 6) Rename default branch if needed

If your default branch is not main (ex: master), update Pages settings and workflows to match.

---

✅ Quick checklist (most common)

✅ index.html exists in root
✅ Pages source set properly
✅ workflow uploads correct folder (/, dist, build)
✅ no build errors in logs

---

If you paste the exact error lines from the failed action log, I can tell you the 1 exact fix in 1 reply.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[Jaiminkansagara1327]

Hey @thanakornbua, the repo size isn’t the problem here.
​

A few quick things you can check:

In Settings → Pages, make sure the source is set correctly (GitHub Actions or the right branch/folder) and that your default branch matches what Pages expects.
​

Confirm you have an index.html (or build output like dist / build) in the folder that’s being deployed.
​

Open the failed run you linked, go to Actions → that run → the failing job, and look at the last error lines in the logs — that message usually tells you exactly what’s wrong (missing file, wrong folder, permissions, etc.).
​

If you can paste the exact error line from the log, someone can point out the exact fix more easily in one go.
​