Repository navigation
Clarify GHA installation and first use - #32
Merged
Merged
Conversation
Raithlin
force-pushed
the
feature/readme-setup
branch
from
October 28, 2026 11:57
caad427 to
9baa322
Compare
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.
Summary
Make the README easier to follow from installation to a first PR review, using the Plasma Shortcut Explorer documentation structure. Expand the setup guide with release downloads, checksum verification, PATH, authentication, updates and removal.
Clarify that GitHub CLI is optional: GHA prefers GHA_GITHUB_TOKEN, otherwise tries gh auth token, and continues unauthenticated when neither supplies credentials. Explain that gha update refreshes agent guidance rather than the executable. Preserve the Homebrew and native Linux package instructions added by #31.
Validation