Sub-actions are additional verbs that qualify the primary action. Sub-actions are optional and used only when necessary. For example, in the command sf project deploy start, the sub-action start qualifies what the command project deploy does.
A sub-action can also be a followup action related to a previous asynchronous action. For example, sf data query with the --async flag starts a bulk query. You can then use sf data query resume --use-most-recent to “resume” that query at a later time.
sf project deploy start (start is the sub-action)sf project deploy preview (preview is the sub-action)sf project deploy report (report is the sub-action)sf data import resume (resume is the sub-action)
j