Your GitHub Pages site is currently being built from the main branch (hangs)

[kuato]

Select Topic Area

Question

Body

Hi, I tried to make a simple change to my simple HTML website but GitHub Pages Actions got locked in some weird loop where the job just hung in a Queued state. I couldn't resolve the blockage so blew away the repo and started again with a new repo with the same name as the previous repo, but I keep getting the same message (Your GitHub Pages site is currently being built from the main branch.).. and that's it, it just hangs. So I blew away that repo and started yet another with a different name. Same problem. Is my account blocked? Internal error? Thanks.

[kuato]

Got it unstuck, not sure if all my button mashing helped. thx.

[Nayil97]

Try these quick fixes:

1. Check if GitHub is having issues: https://www.githubstatus.com/

2. Force rebuild:

   • Make a small commit (add a space to README.md), or
   • Settings → Pages → Change source to "None", save, then back to "main"

3. Check repository Actions tab for failed builds

4. Verify your repository is under 1GB and files are under 100MB

If still stuck, contact GitHub Support with your repo URL. They can investigate build issues.

[jequearabe]

Hi Kuato,

What you’re experiencing is a relatively common GitHub Pages build issue, and it’s usually not a permanent block on your account. Here’s a step-by-step approach to resolve it:

1. Check GitHub’s status first
   Sometimes Pages or Actions have outages that cause builds to hang. Verify at: https://www.githubstatus.com/.

2. Force a rebuild in your repository

   • Make a tiny commit (even just adding a space to README.md) and push to main.
   • Alternatively, go to Settings - Pages - Source, temporarily set the branch to None, save, then set it back to main and save again. This often clears stuck builds.

3. Inspect Actions workflows
   Check the Actions tab for any queued or failed jobs. Sometimes an older workflow from a deleted repo can interfere, so manually cancelling any lingering jobs can help.

4. Repository size limits
   Make sure your repo is under 1GB and individual files are under 100MB, as exceeding these can silently block builds.

5. Clear cache (optional but effective)
   If you’re comfortable using Git, you can delete the .github/workflows folder, push, then recreate a minimal workflow or just let GitHub Pages rebuild without a workflow.

6. Contact GitHub Support
   If the problem persists after the above steps, it’s best to open a support ticket with the repository URL(s). They can investigate whether your account or repository state has lingering build artifacts causing the loop.

tip: Using a new repository name sometimes helps temporarily, but if the underlying build queue has cached your previous site, it can propagate the same stuck state. The most reliable fix is usually forcing a rebuild or having GitHub Support clear any lingering Jobs for your account.

Following these steps usually resolves the “site is currently being built” loop without waiting for the queue to resolve itself.

---

[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! 💬