Repository navigation
Explain setup requirements and skip actions - #829
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
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.
Setup now explains why navigation is unavailable, gives remote-only users an explicit path onward, and distinguishes skipping switch configuration from exiting setup. Existing capture and unsaved-draft navigation guards remain intact.
Validation: Node 24 lint/build, 165 frontend tests plus 5 update-feed tests, Rust formatting/Clippy, 508 Rust unit tests and 7 integration tests passed; one existing test ignored. Independent review passed at a8f030f. GitHub CI is green, including macOS and Windows native packaging.
Closes #824.