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: CHANGELOG.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,13 @@
2
2
3
3
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
Copy file name to clipboardExpand all lines: README.md
+31-12Lines changed: 31 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,28 +65,47 @@ sf plugins
65
65
66
66
## `sf project:deploy`
67
67
68
-
deploy a Salesforce project
68
+
The command first analyzes your project, active or logged-into environments, and local defaults to determine what to deploy and where. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.
69
69
70
70
```
71
+
The command first analyzes your project, active or logged-into environments, and local defaults to determine what to deploy and where. The command then prompts you for information about this particular deployment and provides intelligent choices based on its analysis.
72
+
73
+
For example, if your local project contains a package directory with metadata source files, the command asks if you want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to deploy to. If the command finds Apex tests, it asks if you want to run them and at which level.
74
+
75
+
Similarly, if the command finds a local functions directory, the command prompts if you want to deploy it and to which compute environment. The command prompts and connects you to a compute environment of your choice if you’re not currently connected to any.
76
+
77
+
This command must be run from within a project.
78
+
79
+
The command stores your responses in a local file and uses them as defaults when you rerun the command. Specify --interactive to force the command to reprompt.
80
+
81
+
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific commands, such as "sf project deploy org", that provide additional flags.
82
+
71
83
USAGE
72
84
$ sf project:deploy
73
85
74
86
OPTIONS
75
-
--directory=directory directory to deploy
76
-
--interactive TBD
77
-
--target-env=target-env TBD
87
+
--interactive
78
88
79
89
DESCRIPTION
80
-
Deploy a project, including org metadata and functions. Be default, the deploy analyze your project and assume
81
-
sensible defaults when possible, otherwise it will prompt. To always prompt and not assume defaults, use
82
-
"--interctive".
83
-
To run specialized deploys, especially when interactivity isn't an option like continuous deployment, used the scoped
84
-
deploy commands like "sf project deploy org" or "sf project deploy functions"
90
+
For example, if your local project contains a package directory with metadata source files, the command asks if you
91
+
want to deploy that Salesforce app to an org. The command lists your connected orgs and asks which one you want to
92
+
deploy to. If the command finds Apex tests, it asks if you want to run them and at which level.
93
+
94
+
Similarly, if the command finds a local functions directory, the command prompts if you want to deploy it and to which
95
+
compute environment. The command prompts and connects you to a compute environment of your choice if you’re not
96
+
currently connected to any.
97
+
98
+
This command must be run from within a project.
99
+
100
+
The command stores your responses in a local file and uses them as defaults when you rerun the command. Specify
101
+
--interactive to force the command to reprompt.
102
+
103
+
Use this command for quick and simple deploys. For more complicated deployments, use the environment-specific
104
+
commands, such as "sf project deploy org", that provide additional flags.
0 commit comments