Points a checkout at a different remote, so it tracks another branch from now on. Run it from the root of a checkout (the folder that contains .mmt).
Usage#
mmt switch remote-key
Arguments#
| Argument | Short | Required | Description |
|---|---|---|---|
remote-key |
Yes | The key associated with the stored remote resource. |
What switch does#
Switch re-reads the new branch’s latest changeset and compares your files with it. It doesn’t download, change or delete any files.
- Files that differ from the new branch show as modified. Pushing them commits them to the new branch, which is how you move local work from one branch to another.
- Objects that exist on the new branch but not in your folder also show as modified. A plain
mmt pushsends them empty, which blanks them on the branch. Before pushing, restore them withmmt revert(for examplemmt revert templates\dev_only.mvton Windows), or push only the files you mean to.mmt pulldoesn’t restore them. - Files for objects that exist only on the old branch stay in the folder but are no longer tracked: status doesn’t list them and push ignores them.
To start clean on another branch, use mmt checkout into a new folder instead.