Skip to content
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

Add a check to verify mkdocs builds #357

Closed
wants to merge 1 commit into from

Conversation

Javagedes
Copy link
Contributor

Adds a check to the pipeline that verifies mkdocs builds with no errors or warnings.

It was chosen to also force users to fix warnings, as the additional pydocstyle linting requirements for mkdocs only show up as warnings if incorrect.

@Javagedes Javagedes self-assigned this Dec 7, 2022
@Javagedes Javagedes added documentation Improvements or additions to documentation enhancement New feature or request labels Dec 7, 2022
@Javagedes Javagedes added this to the 0.20.1 milestone Dec 7, 2022
@codecov
Copy link

codecov bot commented Dec 7, 2022

Codecov Report

Merging #357 (10e7049) into master (efa3d60) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #357   +/-   ##
=======================================
  Coverage   71.63%   71.63%           
=======================================
  Files          48       48           
  Lines        4813     4813           
=======================================
  Hits         3448     3448           
  Misses       1365     1365           
Flag Coverage Δ
Linux 70.80% <ø> (ø)
Windows_NT 71.57% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Adds a check to the pipeline that verifies mkdocs builds with no errors
or warnings.

It was chosen to also force users to fix warnings, as the additional
pydocstyle linting requirements for mkdocs only show up as warnings if
incorrect.

Signed-off-by: Joey Vagedes <joeyvagedes@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant