Updates your files to the branch’s latest changeset, or to the changeset given with -c. Run it from the root of a checkout (the folder that contains .mmt). File names are relative to that folder; on Windows use backslashes (templates\sfnt.mvt), because a path with forward slashes doesn’t match and is silently ignored.
Usage#
mmt pull [-c CHANGESET] [--force] [filepaths ...]
Arguments#
| Argument | Short | Required | Description |
|---|---|---|---|
-c CHANGESET |
No | Update to specified changeset. | |
--force |
-f |
No | Overwrite any locally modified files. |
filepaths ... |
No | The list of local files to update. If blank, all files within the checked out changeset / the specified changeset will be updated. |
Examples#
Update everything:
mmt pull
Update one file, replacing your local changes to it:
mmt pull --force templates/sfnt.mvt
How pull treats your local changes#
| Your file | Server version | Without --force |
With --force |
|---|---|---|---|
| Unchanged | Changed | Updated | Updated |
| Changed | Unchanged | Kept as you left it | Replaced with the server version |
| Changed | Also changed | Pull stops with MMT-COMMAND-PULL-00004 and lists the files |
Replaced with the server version |
| Any | Object deleted on the server | Deleted | Deleted |
If you name files that you’ve changed locally, pull stops with MMT-COMMAND-PULL-00001 unless you add --force.
Pull prints Added:, Updated: and Deleted: lines for each file, or No files updated. It then records the changeset it pulled, even when you named only some files.