Conversation
|
A better way to test if docs would succeed is There are still some possible edge cases, especially around system dependencies, but |
5bffb24 to
60da003
Compare
Collaborator
Author
|
Thanks for the suggestion. However, it fails for me locally on (there are two more similar errors) I can also see that bevy ended up doing this manually too because of lack of |
Member
|
Any reason this is still a draft? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The failed docs.rs build of 0.8.5 was not caught in CI though it probably should have been.
Solution
Add
--cfg docsrsto the rustdoc invocations. This makes the docs build process more like what's going to happen in the docs.rs build and can check for similar kinds of failures that are gated behind this cfg option.