Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC: Post warnings as reviews on PRs #24731

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

Merged
merged 3 commits into from
Dec 15, 2022
Merged

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Dec 15, 2022

PR Summary

This posts the warnings and deprecations from the doc builds as artifacts, then fetches them from the GitHub Action for CircleCI posting, and posts them as commit checks.

It also removes the URL check that I added in #24579. While it can be fixed, it would still "error" when the build initially starts (because there are no artifacts) and we've lasted without it so far, so I took it out.

Now, I've found out that the status event only triggers for the workflow on the default branch, so the changes here won't be directly reflected until merged (and is why the URL check thing above wasn't noticed before merging). Therefore, I have pushed this change to my fork's main branch, then opened a PR that breaks a reST target and a deprecation in an example. You can see this posting here: https://github.com/QuLogic/matplotlib/pull/25/files

Fixes #22176

PR Checklist

Documentation and Tests

  • [n/a] Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • [n/a] New plotting related features are documented with examples.

Release Notes

  • [n/a] New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • [n/a] API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • [n/a] Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

echo "No deprecation warnings in gallery")
(grep DeprecationWarning -r -l doc/build/html/tutorials ||
echo "No deprecation warnings in tutorials")
(grep -rl DeprecationWarning doc/build/html/gallery ||
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it worth it to add the plot_types gallery or nah 'cause it's super specific?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just copied the existing warning checks, but I don't see any reason not to check plot_types as well.

@story645 story645 self-requested a review December 15, 2022 05:36
@story645 story645 dismissed their stale review December 15, 2022 05:37

didn't mean to press request changes button

This will fail until the doc build is complete, which causes unwanted
notifications about the job 'failing'.
Copy link
Member

@oscargus oscargus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! (Although I prefer not to have to rewrite the reviewdog call...)

(I'm not sure I'm a big believer in Review Dog doing a better job* than just posting a comment, but this works nicely and fits the current flow.

  • As in new contributors missing what is the actual problem etc.)

@tacaswell tacaswell merged commit a1da538 into matplotlib:main Dec 15, 2022
@QuLogic QuLogic deleted the doc-post-errors branch December 15, 2022 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[MNT]: Write a bot to post doc build issues
4 participants