Error "Invalid GitHub Pages source folder."

[elena-alcaraz]

Select Topic Area

Question

Body

Estoy intentando publicar mi repositorio en GitHub Pages, pero siempre me da el error Invalid GitHub Pages source folder.

Tengo publicada la carpeta docs en la raíz del repositorio, y todo configurado correctamente. ¿Alguien sabe qué puede estar pasando?
Gracias!

[gitstua]

Answering in English - Not sure if this is a public repo but can you check the folder specified in the workflow file? it should be similar to this... (note it is case sensitive so docs isn't the same as Docs) https://github.com/gitstua-labs/pages-demo/blob/7ec39d657d852216bedcb069ff98a6c85b5d13bc/.github/workflows/jekyll-gh-pages.yml#L36

You may also find help in the docs: https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site#creating-a-repository-for-your-site

[legndery]

Happening to me as well. I have created GH pages before many times never something like this happened. I tried using docs folder, tried using different gh-pages branch etc etc.

Mine is public forked repo: https://github.com/legndery/kanakanjiquiz

[elena-alcaraz]

Did you find the error? I cant explain what is happening, I've published several repos without problems, I've tried deleting the folder and creating it again, trying with different methods... Dont know whats happening

[legndery]

I literally have no idea why this is happening. No description or anything about the error. No google search result except for this exact forum post.

[legndery]

But, when I created the docs folder and tried to use it as source folder, somehow the main /root folder got deployed I have no idea how.
So for now, my thing is deployed at x.github.io/repo/docs which is very lame but for now i will use it before more information comes out.

[beethogedeon]

I'm currently facing that issue too

[TyronNIKO]

Hi. Same here... here is deploy settings https://github.com/TyronNIKO/goit-js-hw-12/blob/main/.github/workflows/deploy.yml
Trying to select branch by default '/(root)' - Save btn is disabled - if select '/(root)' or else manualy - SAVE is active but when pressed - you get error Invalid GitHub Pages source folder

[gitstua]

👋🏽 Thanks for the detailed report. I have passed this information on to the team.

[ManuelBerrueta]

I'm getting the same behavior; it sounds like there is an issue here 😕

[ManuelBerrueta]

@gitstua do you guys need to create an incident for this? https://www.githubstatus.com/ still shows all 🟢 green 🤷‍♂️

[bigcat88]

👋🏽 Thanks for the detailed report. I have passed this information on to the team.

any news on this? without it currently we have no option to disable GitHub Pages feature for the repository :(

[pranav-gautam]

I am having the exact same issue!

[pukmajster]

Same issue here. The only time it went through is when i chose a branch without an index.html and it published the readme instead.

[JellyJoe13]

Hi there! Same for me. I have a separate branch for documentation and the content is in /docs with an index.html and .nojekyll file and the same error.

[nicu]

I'm getting the same error when trying to deploy a Docusaurus generated page. The main branch is selected by default and /(root). When I select the gh-pages branch the Save button is disabled, I have to select /docs then /(root) again, press Save and I get the error: Invalid GitHub Pages source folder.

[nnthruslpn]

same error

[philippemiron]

I'm getting the same error. I tried deleting the branch and starting from a single index.html file and got the same error. Note that this is not happening on my "main" page (philippemiron.github.io), but another repo that should show up as a philippemiron.github.io/xyz.

[ManuelBerrueta]

Adding a +1. I am getting the same error as well. It won't let you change the source branch (the "Save" button is disabled) and thus won't deploy, as described by @TyronNIKO

[iCodeWebApps]

I am getting the same error!

I unpublished my site. Then I was trying to getting it republished, it defaulted to main branch for Build and Deployment.

When tried switching it to my gh-pages branch, it returned error: Invalid GitHub Pages source folder.

https://github.com/iCodeWebApps/dev1/settings/pages/source
Request Method:
POST
Status Code:
302 Found
Remote Address:
20.205.243.166:443
Referrer Policy:
strict-origin-when-cross-origin

[foochris]

Same issue as the above posts.

@gitstua Please escalate this issue to the GitHub pages team. The GitHub Status page indicates that Pages is normal, however, with the above comments, there certainly appears to be an issue.

[Samska]

Same issue here, I unpublished a project that I already have the GitHub Pages working fine and tried to publish now I got the same error.

[bkleinen]

Same here. Exact thing that worked yesterday doesn't work today:

fork this repo, enable actions, run gh-pages-fork.yml, publish from gh-pages.
https://github.com/htw-imi-showtime/showtime-website

workflow: https://github.com/htw-imi-showtime/showtime-website/blob/main/.github/workflows/gh-pages-fork.yml

[Mikopet]

same here. cannot change root to docs branch.

[drjzhn]

same here. cannot change root to docs branch.

Same issue

[MariaYminova]

The same problem

[sksksk2024]

this needs to be resolved asap 💀

[jeffreyhsu321]

If it helps anyone, I ended up deploying docusaurus to gh-pages using the same account as the owner of the repository. I was having the same errors as y'all when I was using a collaborator account to deploy.

[lludlow]

I am the owner and still having this issue

[FroZe36]

same problem

[JellyJoe13]

Ok, I found out a possible workaround with workflows/Actions, those still work.
Prerequisites: Have elements to push to pages on main branch (may be possible on other branches but I did not get it to work) and assuming you have a folder of HTML files in your repo

Steps:

• Settings -> Pages
• GitHub Actions in the source dropdown menu
• Choose template "Static HTML" (configure)
• (It opens a config file to add to repo)
• If your HTML content is in a folder, then change in line 40 "." to the path, e.g. "./docs"
• You might also want to change the trigger condition, e.g. by deleting "push: branches: ["main"], or else every time you push something to main it is executed.
• Commit it, in case you left the trigger condition it should deploy
• Else: Go to Actions -> Deploy static content to pages and hit Run workflow with main branch.

Btw. I would appreciate if someone got this to work so that this is also possible on a non-default branch, I am not a fan of merging my docs and main folder in my repo where I wanted to use pages originally.

Example/Proof: https://github.com/JellyJoe13/PagesTest2 (the 'docs' part in the config does not work, so ignore that one)

[grtj1417]

@JellyJoe13 sorry this method is not working for me, I think the only way is to wait until github resolve this problem

[IhsanKhaliq]

Worked for me, thank you!

[sebastian-raubach]

Same issue here.

[Ocece77]

same :c

[tangbojin]

Same issue here.Guys fix it please.

[tangbojin]

I chang my branch to the default branch [main].It works.

[philippemiron]

I created a GitHub ticket, and from their answer, it looks like it's not going to be fixed. The deploy from a branch option is going away in 2 days, as shown at the top of creating-a-github-pages-site.

I'm not sure if there is a workaround because the deploy Github Action is not triggered automatically if you have another Github Action that:

• build website
• copy static files to the gh-pages branch
• create a commit

If you run it manually, it does update correctly. It seems to be related to:

Commits pushed by a GitHub Actions workflow that uses the GITHUB_TOKEN do not trigger a GitHub Pages build.

on publishing-source-for-your-github-pages.

If someone has a solution, that would be helpful 😃

[ManuelBerrueta]

@tcbyrd are you saying then that the way the GitHub pages were being deployed with the ability to switching the branch is now deprecated, and now it requires us to create our own GitHub action to build/deploy?

If so ,that would be a great answer to clarify the issue and close this thread.

Is there somewhere where it is mentioned that this is happening, it apparently is a surprise to many of us.

[tcbyrd]

@tcbyrd are you saying then that the way the GitHub pages were being deployed with the ability to switching the branch is now deprecated, and now it requires us to create our own GitHub action to build/deploy?

No I'm saying the opposite. The deploy from a branch option is NOT going away.

[ManuelBerrueta]

So, then the deployment of GitHub Pages should be working as expected and thus there is an issue?

Maybe I misunderstood from what you replied there that it was only going to work for docs now.

[tcbyrd]

Yeh we found the issue. Working on getting a fix out now.

[ManuelBerrueta]

Got it thanks!

[kscript]

[Kuuuube]

Thank you! This worked.

[sinaatalay]

Hi everyone,

I was having the same issue, but it seems like the way GitHub pages are deployed is changing.

My solution was to give up the Deploy from a branch option and use the GitHub Actions instead.

I have updated my CI deployment workflow from this:

https://github.com/sinaatalay/rendercv/blob/fafa4084cf5ab4153a1830a9fff1fb1ca791e949/.github/workflows/deploy-docs.yaml

to this:

https://github.com/sinaatalay/rendercv/blob/main/.github/workflows/deploy-docs.yaml

Basically, the new workflow builds the website and then pushes the final HTML files as an artifact. Then, actions/deploy-pages@v4 takes that artifact and deploys the website.

[tcbyrd]

My solution was to give up the Deploy from a branch option and use the GitHub Actions instead.

Cross referencing my comment in another thread. To summarize, the deploy from a branch option is not being deprecated. There is a bug we're working on a fix for, but you should not have to move away from using a branch as the source if you don't want to.

[zhoujiayi003]

Hi everyone

a solution may solve the problem: change the default branch from main branch to gh-pages branch.

This solves the problem when I try to use https://github.com/alshedivat/al-folio

[CrazyKamel]

Hi, thank you. I changed my default branch from main to gh-pages, set gh-pages branch for github pages deployment and then, set back main as the default branch.

[tian1327]

Thank you so much for sharing this workaround! It works for me!

[new-AF]

thx for the workaround

[VivekMChawla]

@zhoujiayi003 - You are a lifesaver! Thank you for figuring out this workaround and sharing it with us!

[new-AF]

same

[lavumi]

It seems that changing the branch and folder isn't working. I am currently using GitHub Pages with the master branch pointing to the docs folder. I tried to switch it to the gh-pages branch pointing to the root directory, but it didn't work.

[paichart]

I tried the suggestions above with no success. I guess we are waiting on the bug fix mentioned by Tommy Byrd, right ?

[YiMysty]

👋 A fix has been applied, and the issue should have been resolved. We apologize for any inconvenience caused.

[ManuelBerrueta]

Awesome 👏, thank you for the hard work!
I know that's not how anyone wants to end a Friday but I know all the folks really appreciate it!

[elena-alcaraz]

It's looks to be fixed :) Thanks to all of you!!!

[iCodeWebApps]

I converted over to AWS Static Website hosting as a result of the multi-day outage resulting from this bug.