Automate Quarto rendering on code and data updates via GitHub Actions #18
Description
Currently, when CSV data or code changes are pushed, the Quarto site doesn’t update automatically because rendering is done locally before deployment. So when we add new communities in the CSV file they dont show up in the website unless we do quarto render/ quarto preview locally before pushing.
This causes the GitHub Pages site to serve outdated content until someone manually runs quarto render and redeploys.
We need to create a GitHub Actions workflow that triggers quarto render on every push or pull request. This automation will regenerate the site with the latest data and code changes, ensuring the published site stays in sync with the repository without manual intervention.
The workflow should:
- Trigger on pushes and PRs to the main branch
- Install Quarto CLI
- Run quarto render
- Commit and push any generated site files back to the repository