Repository navigation
fix: isolate CLI rustdoc output from workspace docs - #216
Merged
Merged
Conversation
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
1 participant
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.
The core library and CLI binary are both named
warble, causing rustdoc to write to the same directory and intermittently fail with missing output files. Build the CLI package and the remaining workspace documentation in separate fresh target directories, preserving Cargo’s default target selection, warning-as-error checks, and cleanup.Validation: two clean workspace documentation builds passed without collisions. Recorded rustdoc invocations confirm all six libraries and the CLI binary remain checked. Disposable fixtures verify that broken links in the core library, CLI library, and CLI binary still fail the build and clean up temporary output.