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/deploy.metadata.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,17 @@ If your org allows source tracking, then this command tracks the changes in your
12
12
13
13
To deploy multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.
`--quiet` builds on the same streaming-suppression primitive as `--no-progress`. For token-sensitive workflows, `--json --concise` is already a near-minimal machine-readable payload.
25
+
15
26
# examples
16
27
17
28
- Deploy local changes not in the org; uses your default org:
@@ -22,6 +33,14 @@ To deploy multiple metadata components, either set multiple --metadata <name> fl
- Deploy all source files in the "force-app" directory to an org with alias "my-scratch"; emit the trimmed JSON payload instead of the full success table:
- Deploy all source files in the "force-app" directory to an org with alias "my-scratch"; suppress live progress and collapse the final report to one summary line:
- Deploy all the Apex classes and custom objects that are in the "force-app" directory. The list views, layouts, etc, that are associated with the custom objects are also deployed. Both examples are equivalent:
Copy file name to clipboardExpand all lines: messages/retrieve.start.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,20 @@ If your org allows source tracking, then this command tracks the changes in your
12
12
13
13
To retrieve multiple metadata components, either use multiple --metadata <name> flags or use a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --source-dir.
14
14
15
+
## Output modes
16
+
17
+
`--quiet` suppresses the live retrieve progress stream and collapses the final output to a single summary line. `--no-progress` only hides the streaming block; it keeps the normal final output.
18
+
15
19
# examples
16
20
17
21
- Retrieve all remote changes from your default org:
18
22
19
23
<%= config.bin %> <%= command.id %>
20
24
25
+
- Retrieve all remote changes from your default org and keep the output to a single summary line:
26
+
27
+
<%= config.bin %> <%= command.id %> --quiet
28
+
21
29
- Retrieve the source files in the "force-app" directory from an org with alias "my-scratch":
0 commit comments