Repository navigation
docs: clarify where to persist the CLI PATH setting - #102
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the documentation-only clarification that persistent PATH settings belong in the shell profile.
No open issues 🎉
What changed in this PR
Clarifies the CLI setup documentation by specifying that persistent PATH settings belong in the shell profile.
Changes:
- Replaces “shell” with “shell profile” in the PATH guidance.
- Documentation only; no runtime code, commands, dependencies, or CI/CD changes.
| File | Description |
|---|---|
| README.md | Clarifies where to persist the CLI PATH setting. |
Review effort: Balanced
This branch was successfully 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.
Clarify that a persistent PATH setting belongs in the shell profile. Documentation only; no runtime code, commands, dependencies or CI/CD changes.
This small source change exercises the existing main CI and image-publishing flow after merge. The PR stays unmerged until its checks pass and the release owner confirms the merge window.