You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/delete.source.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Delete source from your project and from a non-source-tracked org.
4
4
5
5
# description
6
6
7
-
Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, "sf project deploy start".
7
+
Use this command to delete components from orgs that don’t have source tracking. To remove deleted items from orgs that have source tracking enabled, "<%= config.bin %> project deploy start".
8
8
9
9
When you run this command, both the local source file and the metadata component in the org are deleted.
Copy file name to clipboardExpand all lines: messages/deploy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ For example, if your local project contains a source directory with metadata fil
12
12
13
13
The command stores your responses in the "deploy-options.json" file in your local project directory and uses them as defaults when you rerun the command. Specify --interactive to force the command to reprompt.
14
14
15
-
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as "sf project deploy start", that provide additional flags.
15
+
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as "<%= config.bin %> project deploy start", that provide additional flags.
Copy file name to clipboardExpand all lines: messages/deploy.metadata.cancel.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,15 +47,15 @@ Number of minutes to wait for the command to complete and display results.
47
47
48
48
# flags.wait.description
49
49
50
-
If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
50
+
If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the cancellation, run "<%= config.bin %> project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
51
51
52
52
# flags.async.summary
53
53
54
54
Run the command asynchronously.
55
55
56
56
# flags.async.description
57
57
58
-
The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run "sf project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
58
+
The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the cancellation, run "<%= config.bin %> project deploy resume". To check the status of the cancellation, run "<%= config.bin %> project deploy report".
Copy file name to clipboardExpand all lines: messages/deploy.metadata.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ Number of minutes to wait for command to complete and display results.
110
110
111
111
# flags.wait.description
112
112
113
-
If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf project deploy report".
113
+
If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To resume the deployment, run "<%= config.bin %> project deploy resume". To check the status of the deployment, run "<%= config.bin %> project deploy report".
114
114
115
115
# flags.manifest.summary
116
116
@@ -178,7 +178,7 @@ Run the command asynchronously.
178
178
179
179
# flags.async.description
180
180
181
-
The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run "sf project deploy resume". To check the status of the deployment, run "sf project deploy report".
181
+
The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run "<%= config.bin %> project deploy resume". To check the status of the deployment, run "<%= config.bin %> project deploy report".
182
182
183
183
# flags.metadata-dir.summary
184
184
@@ -203,7 +203,7 @@ You must specify tests using the --tests flag if the --test-level flag is set to
203
203
204
204
# error.ClientTimeout
205
205
206
-
The command has timed out, although the deployment is still running. Use "sf project deploy resume" to resume watching the deployment.
206
+
The command has timed out, although the deployment is still running. Use "%s project deploy resume" to resume watching the deployment.
207
207
208
208
# error.Conflicts
209
209
@@ -213,15 +213,15 @@ There are changes in the org that conflict with the local changes you're trying
213
213
214
214
- To overwrite the remote changes, rerun this command with the --ignore-conflicts flag.
215
215
216
-
- To overwrite the local changes, run the "sf project retrieve start" command with the --ignore-conflicts flag.
216
+
- To overwrite the local changes, run the "%s project retrieve start" command with the --ignore-conflicts flag.
217
217
218
218
# error.nothingToDeploy
219
219
220
220
No local changes to deploy.
221
221
222
222
# error.nothingToDeploy.Actions
223
223
224
-
- To see conflicts and ignored files, run "sf project deploy preview" with any of the manifest, directory, or metadata flags.
224
+
- To see conflicts and ignored files, run "%s project deploy preview" with any of the manifest, directory, or metadata flags.
0 commit comments