| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
In addition, two examples are edited to not use "DeprecationWarning" and reflect the current status. |
Sorry, something went wrong.
|
🎉 This is a very big win at a very small cost! |
Sorry, something went wrong.
|
It should be quite easy to get those results out and comment in the PR as well. Given that one knows how to do the GitHub-part... |
Sorry, something went wrong.
|
Great! 🚀 This addresses my issue #22176. Posting a comment is easy https://stackoverflow.com/a/64126737. |
Sorry, something went wrong.
…868-on-v3.6.2-doc Backport PR #23868 on branch v3.6.2-doc (Show errors and warnings in doc CI after build.)
…868-on-v3.6.x Backport PR #23868 on branch v3.6.x (Show errors and warnings in doc CI after build.)
| Back | FazBrowse Home | New Git URL |
PR Summary
Adds a separate step that summarized the warnings and errors during documentation build.
Adds a step which checks for deprecation warnings in examples and tutorials.
I'm quite sure that there is an issue for that which I cannot find, but ideally this should be fed back to GitHub as a comment so it will still not be closed.
Anyway, this should help a bit as it is easier than scrolling back in the very long log (and some messages may have disappeared...).
Helps with #23866
PR Checklist
Tests and Styling
Documentation