Skip to content

Conversation

apoorvalal
Copy link
Member

@apoorvalal apoorvalal commented Jul 15, 2025

Docs currently only build on Alex's personal laptop (the quarto file points to python.exe) which is not a great state of affairs. I'm going to work on a setup so we have documentation deployment and preview in each branch.

[likely ugly, WIP]

Copy link

codecov bot commented Jul 15, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag Coverage Δ
core-tests 75.94% <ø> (ø)
tests-extended ?
tests-vs-r 16.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
pyfixest/estimation/feiv_.py 87.50% <ø> (ø)
pyfixest/estimation/feols_.py 84.64% <ø> (-6.83%) ⬇️

... and 5 files with indirect coverage changes

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

@apoorvalal
Copy link
Member Author

Drops the comparing with fixest notebook since it is a massive pain in the neck to make rpy2 work on a prod system with github actions. IMO we can link to a notebook that demonstrates equivalent results run on someone's local machine.

Also possibly time to update those comparisons to ryp

@apoorvalal apoorvalal marked this pull request as draft July 15, 2025 05:23
This commit overhauls the Quarto documentation generation and CI process.

- Automates the documentation build and deployment via GitHub Actions.
- Implements Quarto's 'freeze' feature to significantly speed up builds by caching computational results.
- Adds a markdown linting job to the CI to ensure documentation quality.
- Fixes numerous docstrings and cross-reference links in the API documentation.
- Updates the Quarto configuration to correctly build the reference documentation and ignore build artifacts (, ).
@s3alfisc
Copy link
Member

I actually think all the docs are building on the CI, it's just that I think the folder is deleted straight away? Else I couldn't explain why the docs CI step usually takes 20 minutes or so? It's usually painfully slow ...

@apoorvalal
Copy link
Member Author

yeah it takes well over an hour on my local machine; i think the github action is doing some fiddly caching. I'll dig into the logs on a flight tomorrow.

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.

2 participants