-
Notifications
You must be signed in to change notification settings - Fork 2
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
No longer publishing to custom url #84
Comments
There isn't a CNAME file in the root of the repo, which according to the docs there should be. The CNAME file exists in the repo used as a template for this one, so maybe we should try add it. |
Above PR fixes the issue for uclhal.org, but not www.uclhal.org. I think the DNS is misconfigured but we can't fix that here. |
Fab - thanks Dan! Even if it does not work for www.uclhal.org, when you google "UCL HAL" the address that pops up is uclhal.org (same as it used to) -> so it still works ok for people trying to find us |
Yesterday I updated the Data Clinic.qmds on the UCL HAL github (only changed wording of the qmd files, nil else). Pull request preview looked fine. This morning I re-ran the “Quarto Publish” and “pages-build-deployment” workflows to update the website with the changes. These seemed to work and the website has been updated.
However, the website now only seems to be visible at https://uclhal.github.io/uclhal/ rather than our custom url https://uclhal.org/?
I’ve checked the “_quarto.yml” script (the CNAME script) on the main branch of the repo. It is unchanged and still contains the correct site-url option - but some some reason now doesn’t seem to be publishing to the custom URL?
Only possibility I can see is that in Settings/Pages/Build & Deployment and “publish.yml” file in main/.github/workflows, the target seems to be the gh-pages branch rather than the main branch. The gh-pages branch does not have the “_quarto.yml”.
Has anyone got any ideas of why this may be happening? I was tempted to try changing the target of the Settings and the publish.yml file to the main branch - but I don't want to mess it up any further!
The text was updated successfully, but these errors were encountered: