-
Notifications
You must be signed in to change notification settings - Fork 334
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
Proactively test Hugo themes #707
Comments
While I was fixing another |
Oh cool. For the final solution, do you want still want it to be as part of R CMD check in package tests/ or is this a workaround and a custom GHA workflow would be better ? Just to know |
What I'm hoping for is that we want to make sure a selected list of themes always work, so a daily action to check them would be nice, and the action should throw an error if any of these themes fail to work. Then I also want a "status page" that shows the full list of themes and indicate which ones work or fail. It's fine if certain themes in the full list fail (i.e. the action doesn't need to throw an error). |
From #704 (comment)
Originally I was thinking of testing only a few themes in a GHA daily workflow:
But it may be a better idea to test all themes: https://github.com/gohugoio/hugoThemesSiteBuilder/blob/main/themes.txt and generate a "status" page that shows which themes work or do not work with blogdown. This page could be a simple (meaning a plain style) HTML page deployed along with https://pkgs.rstudio.com/blogdown/. We can save the results in the artifacts, and make the pkgdown workflow read and deploy the results.
The text was updated successfully, but these errors were encountered: