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

Requires CNAME to be listed somewhere #48

Closed
Lextuga007 opened this issue Jun 30, 2023 · 6 comments · Fixed by #65, #66, #74, #72 or #71
Closed

Requires CNAME to be listed somewhere #48

Lextuga007 opened this issue Jun 30, 2023 · 6 comments · Fixed by #65, #66, #74, #72 or #71
Labels
bug Something isn't working

Comments

@Lextuga007
Copy link
Member

GitHub Action is removing the domain name.

@Lextuga007 Lextuga007 added the bug Something isn't working label Jun 30, 2023
@Lextuga007 Lextuga007 linked a pull request Nov 27, 2023 that will close this issue
@Lextuga007
Copy link
Member Author

Adding to _quarto.yml hasn't resolved

@Lextuga007 Lextuga007 reopened this Nov 27, 2023
@Lextuga007 Lextuga007 linked a pull request Nov 27, 2023 that will close this issue
@Lextuga007
Copy link
Member Author

Fixed by ensuring code in yaml is formatted to:

project:
  type: book
resources:
  - CNAME

And setting GitHub in Settings > Pages to GitHub Actions from Deploy from Branch

@Lextuga007
Copy link
Member Author

Now this is publishing from the gh-action it now needs to have something in the gh-action for rendering as it is not using the gh-pages branch https://github.com/quarto-dev/quarto-actions/tree/main/render

@Lextuga007 Lextuga007 reopened this Nov 29, 2023
@Lextuga007
Copy link
Member Author

Now I remember why I went back to the the usual way for publishing through GitHub because the quarto book doesn't render new content.

@Lextuga007
Copy link
Member Author

Two issues, firstly gh-pages isn't updating and secondly isn't publishing (changes don't appear even after running quarto render gh-pages from the terminal).

@Lextuga007
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment