Repository navigation
docs: fix migration commands and broken reader navigation - #382
Open
dajiaohuang wants to merge 1 commit into
Open
dajiaohuang wants to merge 1 commit into
dajiaohuang wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Problem and minimal correction
Fix the reader-contract errors described in #381: close the migration shell fence; point VanillaGAN navigation and CWGAN-GP snippets to their existing tracked targets; use the renamed distribution in FAQ/UI/GX installation instructions; restore the UI example link; align the FAQ Python bound with setup.py.
No feature additions, stylistic cleanup, model changes or replacement links based on transient availability. The installation-guide file is deliberately untouched because #365 already edits it. The independent package-initializer failure is handled separately in #380.
Validation
Fixes #381.