'hyve git'
What changed
hyve git add/list/use/remove/status/path/branch/pull/push/sync/credentials are all gone. None of them ever ran real git operations beyond a thin credentials-store wrapper — the actual clone/pull/push was always your own git CLI, called by hand or from CI. What they did do — register a local directory as the one hyve reconcile/hyve cluster/etc. operate against — is now hyve context create [--path]/hyve context use/hyve context list/hyve context remove.
What still works
If you want your state directory backed by git, that’s exactly the same as before: git clone, git add, git commit, git push — your own tooling, your own remote, your own credentials. Hyve reads and writes plain files in whatever directory hyve context has registered as active; it has no opinion about whether that directory happens to be a git working tree. See Version Control for the full picture.
Related
- Contexts — the concept
hyve contextreplaces “git repositories” with - CLI Reference — context
- Version Control