GitHub Community
-
|
I’ve set up a repo using vue and vue styleguidist. I’ve also set up an action that will build a new version of the styleguidist documentation every time there is a merge to master. The action appears to be working. It’s building the proper files and saving them to the gh_pages branch. Under settings, I have verified that gh_pages branch is the one I want to use and I get this message: Your site is ready to be published at http://mullaney.github.io/benchprep-components/. However, when I go to that page I get a 404 error. Is there a step that I’m missing? It’s been over an hour since I last published it. And I have tried multiple browsers in case it’s a caching issue. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
For reference here is the gh_pages branch: |
Beta Was this translation helpful? Give feedback.
-
|
A message from github support: Hi Kevin, In order to be built and published for the very first time, a GitHub Pages repository must have a commit pushed to it by a user with admin permissions for the repository, such as the repository owner. In this case, it looks like the only commits pushed to the Once a commit has been pushed to the repository by a user with admin permissions, you should find the site live and available shortly thereafter. Subsequent commits pushed by accounts with write access such as Sorry for the inconvenience; this issue is something that’s currently being looked at by our engineers as more and more Pages sites are using Actions. I hope that helps to explain! Let us know if there’s anything else we can do. Thanks, Tammy |
Beta Was this translation helpful? Give feedback.
-
|
I checked your page , it could display now. |
Beta Was this translation helpful? Give feedback.
A message from github support:
Hi Kevin,
In order to be built and published for the very first time, a GitHub Pages repository must have a commit pushed to it by a user with admin permissions for the repository, such as the repository owner.
In this case, it looks like the only commits pushed to the
gh-pagesbranch were fromgithub-actions.Once a commit has been pushed to the repository by a user with admin permissions, you should find the site live and available shortly thereafter. Subsequent commits pushed by accounts with write access such as
github-actionswill then also trigger a build.Sorry for the inconvenience; this issue is something that’s currently being looked at by our eng…