-
Notifications
You must be signed in to change notification settings - Fork 7
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
extremely basic rtd impl #102
Conversation
…ng sphinx documentation strings
Codecov Report
@@ Coverage Diff @@
## master #102 +/- ##
==========================================
- Coverage 13.40% 13.02% -0.38%
==========================================
Files 40 40
Lines 873 898 +25
Branches 14 14
==========================================
Hits 117 117
- Misses 756 781 +25
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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 few comments, mostly just observations and some nits before I gave up on doing that before the PR is out of draft. Structurally it seems fine, docs could use some editing for consistency with punctuation/capitalisation but I can do a full pass later with suggestions you can just hit or dismiss.
One Q tho, is Make the best idea here? I know we spoke about Taskfiles before and Make isn't super approachable beyond basics.
Purpose
This is the start of a transition from pydoc to sphinx for readthedocs (so we're more in line with what the general community does for python projects)
New Features
s/pydoc/sphinx/
Bug Fixes
No bug fixes, but we're severely lacking on documentation now. Also the workflows will need to change.
Before/After
s/pydoc/sphinx/
Additional Context
Restructured text is... far from my favorite.