feat: opk update --channel <ref> — switch the tracking ref without editing install.conf - #102
Merged
Merged
Conversation
…iting install.conf Editing /etc/opencode-permissions-kit/install.conf by hand was the only way to move a machine between stable / master / a feature branch / a tag. --channel does it in one command: a pre-scan (before the channel resolution and the self-fetch, so the fetch already uses the new ref) sets KIT_BRANCH, and the existing KIT_CHANNEL re-stamp at the end makes the switch persistent for every future plain 'opk update'. The regular arg loop consumes and validates the flag; KIT_BRANCH env keeps working for the curl-streamed entry points. Docs: cli.md + how-to/update.md.
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.
Editing /etc/opencode-permissions-kit/install.conf by hand was the only way to move a machine between stable / master / a feature branch / a tag. --channel does it in one command: a pre-scan (before the channel resolution and the self-fetch, so the fetch already uses the new ref) sets KIT_BRANCH, and the existing KIT_CHANNEL re-stamp at the end makes the switch persistent for every future plain 'opk update'. The regular arg loop consumes and validates the flag; KIT_BRANCH env keeps working for the curl-streamed entry points. Docs: cli.md + how-to/update.md.