anchor.diff:  [-n HOST] [-p PATH] [-s STACK] [--no-hostname] [--no-route] [--no-start]
   </pre>
   
  -* `APP` --- the name of the application to push, is the only required argument, and the only argument that has no flag. Even `APP` can be omitted when you provide the application name in a manifest.
  +* `APP` --- The name of the application to push is the only required argument, and the only argument that has no flag. Even `APP` can be omitted when you provide the application name in a manifest.
   
   * `-b` --- Custom buildpack by name (e.g. `my-buildpack`), Git URL (For example, https://github.com/cloudfoundry/java-buildpack.git), or Git URL with a branch or tag: https://github.com/cloudfoundry/java-buildpack.git#v3.3.0 to select `v3.3.0`.
   
  
positive.code: 
  * `-c` --- Start command for the application.
  * `-d` --- Domain, for example, example.com.
  * `-f` --- replaces `--manifest`
  * `-i` --- Number of instances of the application to run.
  * `-m` --- Memory limit, for example, 256, 1G, 1024M, and so on.
  * `-n` --- Hostname, for example, `my-subdomain`.
  
negative.code: 
  ## <a id='return-codes'></a> cf CLI Return Codes ##
  
  The cf CLI uses exit codes, which is helpful for scripting and for confirming that a command has run successfully. For example, run `echo $?` in the terminal. If the return code is `0`, the command was successful. 
  
  ## <a id='help'></a> Run cf help ##
  
  