-
Notifications
You must be signed in to change notification settings - Fork 115
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
Example for building documentation #1610
Conversation
Please add one of the following labels to add this contribution to the Release Notes 👇 |
Codecov Report
@@ Coverage Diff @@
## main #1610 +/- ##
==========================================
- Coverage 82.82% 82.81% -0.02%
==========================================
Files 44 44
Lines 7151 7151
==========================================
- Hits 5923 5922 -1
- Misses 1228 1229 +1 |
By the way @clatapie - there seems to be a |
Co-authored-by: Roberto Pastor Muela <roberto.pastormuela@ansys.com>
Co-authored-by: Roberto Pastor Muela <roberto.pastormuela@ansys.com>
|
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.
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.
Good job Camile!
I have minor suggestions:
-
Include some text where you recommend one example over the other. After reading this text, people should know that dynamic example should be very short, for everything else, static.
-
You include this text in the toctree
index.rst
which makes sense. However that leave it buried between the API doc. It is ok for now, but I might need to rethink this section. I had some complains about mixing API and contribution. But there are too many things already on our upper bar in the docs:
Any suggestion is welcome!
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.
Looks good to me! Thanks!
By the way, the text looks good, but everybody knows that English it is not my thing so quickly pinging @PipKat for a quick look :) |
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!
PyMAPDL workflow is so much fun... Don't know why the tests are failing honestly, and the logs don't give much info... |
Most of the times, just re-run it until it does not fail 😆 |
Solves #1585