Push

USAGE
  $ sfp push -o <value> [--json] [-i |  | [-p <value> |  | -d <value>] | ] [-s <value> |  | ]
    [--no-replacements] [--replacementsoverride <value>] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -d, --domain=<value>                Push all metadata for a specific domain.
                                      The domain has to be set by the command sfp config:set (-g).
  -i, --ignore-conflicts              This flag applies only to orgs that allow source tracking. It has no effect on
                                      orgs that don't allow it, such as production orgs.
  -o, --targetusername=<value>        (required) Username or alias of the target org.
  -p, --package=<value>               Push a specific package. Metadata packages deploy via the metadata API; data
                                      packages deploy their records (records/ or CSV) to the org via sfdmu.
  -s, --source-path=<value>           Push all metadata for a specific path.
      --loglevel=<option>             [default: info] logging level for this command invocation
                                      <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --no-replacements               Skip applying text replacements during push
      --replacementsoverride=<value>  Path to a YAML file containing replacement overrides

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push metadata to a target org.

  Metadata packages deploy through the org's metadata API. Data packages (type: data) deploy their records to the org
  via sfdmu — the symmetric inverse of sfp pull. Per-record packages are flattened to CSV first, and sfdmu byproducts
  are cleaned up afterwards so nothing temporary lands in git.

ALIASES
  $ sfp source push
  $ sfp project push

EXAMPLES
  $ sfp project:push --path src/core -o myTargetOrg

  $ sfp project:push -p my-data-package -o myTargetOrg