Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub pages are not refreshed after setup #451

Open
ralienpp opened this issue Oct 16, 2024 · 3 comments
Open

GitHub pages are not refreshed after setup #451

ralienpp opened this issue Oct 16, 2024 · 3 comments

Comments

@ralienpp
Copy link

Hi, I am attempting to use this template for a new draft. After following the instructions I see that the actions are executed successfully, but when attempting to view the generated data - I see an empty page.

I made sure the gh-pages branch was also copied when creating the repository from a template, and that the permissions for the Actions were set to "read and write". Given that there are no errors in the log, what else can I check to understand the root cause of the problem?

@ralienpp
Copy link
Author

After making some trivial edits (add and remove a word) I committed an update to the markdown file, and the pages were built.

The commits were just dummy changes that I hoped would trigger the jobs again. Is that what really did the trick, or is there a natural delay and I just needed to be patient in the first place?

@martinthomson martinthomson changed the title How to troubleshoot an empty page? GitHub pages are not refreshed after setup Oct 16, 2024
@martinthomson
Copy link
Owner

(Changing the title of the issue to reflect this.)

Yeah, the problem here is that while the gh-pages branch is updated by the setup action, the changes that are made do not trigger a refresh of the pages. I don't quite understand why that is the case. As you say, it's the next change that causes the pages to be published. That's mostly OK, but it is a little surprising.

It might be possible to manually publish as a last step of the setup action. I have done that on other repositories, but it's a little fiddly to arrange. If time permits, perhaps.

@martinthomson
Copy link
Owner

I've looked into this more. The default setup of a repo out of the box is to pull from a branch for GitHub Pages. (If gh-pages exists when the repo is created it uses that, otherwise it draws from no branch.)

One effect of this is that it will not allow actions to push to the branch. Nor will the Pages build run when setup runs (for reasons I still don't understand). So I haven't worked out how to make this happen yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants