diff --git a/docs/cli.html b/docs/cli.html index 392c64c39..ef0354646 100644 --- a/docs/cli.html +++ b/docs/cli.html @@ -256,6 +256,7 @@
+Retrieve and update your local integration files with the latest version.
+
Usage: zapier pull
This command updates your local integration files with the latest version. You will be prompted with a confirmation dialog before continuing if there any destructive file changes.
Zapier may release new versions of your integration with bug fixes or new features. In the event this occurs, you will be unable to do the following until your local files are updated by running zapier pull
:
Flags
-d, --debug
| Show extra debugging output.zapier deprecate 1.0.0 2020-06-01
- mark a version as deprecated, but let users continue to use it (we'll email them)zapier env:set 1.0.0 KEY=VALUE
- set an environment variable to some valuezapier delete:version 1.0.0
- delete a version entirely. This is mostly for clearing out old test apps you used personally. It will fail if there are any users. You probably want deprecate
instead.zapier pull
- pull the latest version from Zapier server. This is used in the event that Zapier made an update since your last version.@@ -1143,6 +1146,24 @@Note: To see the changes that were just pushed reflected in the browser, you have to manually refresh the browser each time you push.
Zapier may fix bugs or add new features to your integration and release a new version. If you attempt to use zapier push
and we've released a newer version, you will be prevented from pushing until you run zapier pull
to update your local files with the latest version.
Any destructive file changes will prompt you with a confirmation dialog before continuing.
++Retrieve and update your local integration files with the latest version.
+
Usage: zapier pull
This command updates your local integration files with the latest version. You will be prompted with a confirmation dialog before continuing if there any destructive file changes.
Zapier may release new versions of your integration with bug fixes or new features. In the event this occurs, you will be unable to do the following until your local files are updated by running zapier pull
:
Flags
-d, --debug
| Show extra debugging output.zapier deprecate 1.0.0 2020-06-01
- mark a version as deprecated, but let users continue to use it (we'll email them)zapier env:set 1.0.0 KEY=VALUE
- set an environment variable to some valuezapier delete:version 1.0.0
- delete a version entirely. This is mostly for clearing out old test apps you used personally. It will fail if there are any users. You probably want deprecate
instead.zapier pull
- pull the latest version from Zapier server. This is used in the event that Zapier made an update since your last version.@@ -1143,6 +1146,24 @@Note: To see the changes that were just pushed reflected in the browser, you have to manually refresh the browser each time you push.
Zapier may fix bugs or add new features to your integration and release a new version. If you attempt to use zapier push
and we've released a newer version, you will be prevented from pushing until you run zapier pull
to update your local files with the latest version.
Any destructive file changes will prompt you with a confirmation dialog before continuing.
+