-
-
Notifications
You must be signed in to change notification settings - Fork 211
Docs/mkdoc #1379
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
Docs/mkdoc #1379
Conversation
order plugin is important: first gen_files needs to generate the virtual files for the jupyter extension to render them
I also tried `no_input: true` but that removed the whole cell.
|
IMO: merge first and focus on user stories/use cases afterward to refactor the documentation. That is, likely move all the old documentation to an "extended example" list and only keep a set of user stories / use cases in the new main documentation. |
SubhadityaMukherjee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merged all the changes, they seem correct and run correctly. Next I will test the notebooks/scripts to verify if everything runs.
…e if everything still runs and is up to date
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1379 +/- ##
========================================
Coverage 53.71% 53.71%
========================================
Files 38 38
Lines 5229 5229
========================================
Hits 2809 2809
Misses 2420 2420 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Seems I forgot to update this. These examples dont work. Im not entirely sure how to fix them. All the other examples seem to run. I modified some slightly to make some of them work. They are from examples/ 20_basic/ 30_extended/ flows_and_runs_tutorial : No reg-eye-state, or dataset 68 seems to be something else. study_tutorial: the flow seems to be wrong. 40_paper/ |
|
Thanks! I can have another look once AIoD calms down a little (i.e., after May 22nd). |
… with new deps- fixed typo
… with new deps-removed incorrect path
|
Removed linkcheck for now since the one I picked apparently is not maintained. |
|
Ah @PGijsbers I think we will also need to point the gh-pages option in settings to a different page. I dont have access to it so I cant check if its the same as sphinx. |
That's already set. Sorry for the slow reply. Next time just ask me directly if I don't respond :) |
.github/workflows/docs.yaml
Outdated
| if: (contains(github.ref, 'develop') || contains(github.ref, 'main')) && github.event_name == 'push' | ||
| run: | | ||
| mkdocs gh-deploy --force | ||
| env: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this take into account the branch? For example, if we publish version 0.16 and its documentation, to me it reads like our develop documentation will overwrite it as soon as we push to develop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know I initially said we didn't need it but.. maybe it might be a good idea to look into mike? https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/
it seems to handle the thing we'd want later and it would also solve this problem.
Then we can simply build docs when:
- push to
develop(asdev) - a release is made, i.e., a tag of format
v*
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some reference for what you might need from mike if you want versioned docs.
https://github.com/automl/amltk/blob/5221d80fb4fec92f2d6f2fc73fce4eb16139c09f/.github/workflows/release.yml#L90-L110
It's also good to be aware that all mike does for you is work on the gh-pages branch and so you can always go nuke it or manually edit it if testing goes wrong. Took me a while before realising that, but it means you can really test out the workflow locally before doing the annoying dance with GH actions to get it to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The root of this branch is pretty instructive for what it's doing, i.e. with the symlink, the index.html pointig to latest and the versions.json it's using to store metadata
https://github.com/automl/amltk/tree/gh-pages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A wild Eddie appears!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can just use regular pokeball, no need for an ultra
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
throws a master ball
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
struggle, struggle, pokémon Eddie breaks free
|
all the tests pass in reality but the added files check fails, maybe mike adds them. Im looking into it |
LennartPurucker
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments
| <<<<<<< docs/mkdoc -- Incoming Change | ||
| # %% | ||
| import openml | ||
| ======= | ||
| >>>>>>> develop -- Current Change | ||
| import pandas as pd | ||
|
|
||
| import openml | ||
| from openml.datasets import edit_dataset, fork_dataset, get_dataset | ||
|
|
||
| ############################################################################ | ||
| # Exercise 0 | ||
| # ********** | ||
| # %% [markdown] | ||
| # ## Exercise 0 | ||
| # | ||
| <<<<<<< docs/mkdoc -- Incoming Change | ||
| # * List datasets | ||
|
|
||
| # %% | ||
| datalist = openml.datasets.list_datasets(output_format="dataframe") | ||
| ======= | ||
| # * List datasets and return a dataframe | ||
| datalist = openml.datasets.list_datasets() | ||
| >>>>>>> develop -- Current Change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this file?
LennartPurucker
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
uv.lock
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file is not needed
Work converting the Python docs to mkdocs. Left to do before it's "functional":
Otherwise, most of the files have been converted.
That said, the documentation really needs a rewrite. I refrained from changing any content as much as I could, with rare exceptions. But the main problems, to me, are:
How should we move forward with this PR? I don't mind rewriting (some of) this documentation, but I think it would be better to merge this at one point so it's easier to collaborate. WDYT? @eddiebergman @LennartPurucker