Skip to content

Conversation

@VisruthSK
Copy link
Member

@VisruthSK VisruthSK commented Dec 5, 2025

Clean up the pages branch before deploying the site.

Waiting for https://github.com/stan-dev/loo/actions/runs/19970666932 to finish and ensure the website is still up after.

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.78%. Comparing base (30d6677) to head (181db28).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #318   +/-   ##
=======================================
  Coverage   92.78%   92.78%           
=======================================
  Files          31       31           
  Lines        2992     2992           
=======================================
  Hits         2776     2776           
  Misses        216      216           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jgabry
Copy link
Member

jgabry commented Dec 5, 2025

Looks like mc-stan.org/loo is down now but the dev site is still up

@VisruthSK
Copy link
Member Author

I think clean: true will always wipe the main site whenever a dev site is rebuilt because it wipes the entire branch before copying over the (dev site) files. For hygeine, we could manually wipe the pages branch, build the release site, then build the dev site but that will accumulate cruft which may not be cleaned by pkgdown builds (which only clean pkgdown managed files. I'm going to close the PR and try to think about how to maintain the dev site and release site files only.

@VisruthSK VisruthSK closed this Dec 5, 2025
@jgabry jgabry deleted the clean-pages-branch-before-build branch December 8, 2025 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants