feat: accept --hub <url> on muse push; document push vs hub flag split
muse push now accepts --hub <url> as a convenience: it resolves the URL to the matching configured remote name so agents that mistakenly apply the muse hub --hub pattern to push get correct behaviour instead of an argparse crash. If no remote matches the URL a clear error lists configured remotes and shows the correct remote-name syntax.
Also re-interprets the <remote> positional as a branch when --hub is given and only one positional was supplied (e.g. muse push --hub URL main).
agent-guide.md: add explicit callout that muse push uses remote names not --hub URLs, with correct/incorrect examples and a note about the new --hub convenience flag.
sha256:1fba819a24de82fecb5d395019d29021982f129fb62b96a67605916f711be41b
sha
sha256:02d81bd5359bd5bfbe83f2312430cd9d2c1b04022c42f7602577abb53578c55b
snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:1fba819a24de82fecb5d395019d29021982f129fb62b96a67605916f711be41b --body "your comment"
No comments yet. Be the first to start the discussion.