quarto-dev
docs for list-tables
📝 Preview Deployment
🔍 Full site preview: https://deploy-preview-1801.quarto.org
🔄 Modified Documents
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
(the feature needs to be in quarto-cli before this PR will build correctly.)
📝 Preview Deployment
🔍 Full site preview: https://deploy-preview-1801.quarto.org
🔄 Modified Documents
📝 Preview Deployment
🔍 Full site preview: https://deploy-preview-1801.quarto.org
🔄 Modified Documents
Usually, when this happens, this is a freeze topic:
This file has some computation code cell https://github.com/quarto-dev/quarto-web/blob/3b0bf32466c2f4f04fb4ac822bd893355de1f578/docs/authoring/tables.qmd#L204-L219
So freeze needs to be updated locally and commited. See in _freeze directory _freeze/docs/authoring/tables/execute-results
So locally you need to quarto render docs/authoring/tables.qmd using the venv for quarto-web. If you're not setup locally, I can run it for you (I haven't made the switch to uv here yet, so we are using pipenv (https://github.com/quarto-dev/quarto-web#python-environment-for-jupyter-engine-and-knitr-through-reticulate)
Ahhhhhh you're right, thank you!! 🤦 How much work would it be for the CI to warn when we make .qmd changes to a file that has freeze output?
How much work would it be for the CI to warn when we make .qmd changes to a file that has freeze output?
That's a good question. I'll think about it. If we report in quarto inspect that the document is frozen, then it could be quite easy.
Otherwise, I can find some heuristic.
I'll think about it. If we report in quarto inspect that the document is frozen, then it could be quite easy.
Very good idea. Tracking here: https://github.com/quarto-dev/quarto-cli/issues/13554