anchor.diff:  
   When specifying versions, specify only major/minor versions, eg. go1.6, rather than go1.6.0. This will ensure you receive the most recent patches.
   
  -### <a id='start_command'></a>Start command ###
  +### <a id='start_command'></a>Start Command ###
   
   When pushing go apps, you can specify a start command for the app. The start command can be placed in the file `Procfile` in your app's root directory. For example, if the binary generated by your go project is `my-go-server`, your `Procfile` could be:
   
  
positive.code:   - foo
  ```
  
  ### <a id='pushing_Apps_with_native_Go_vendoring'></a>Pushing Apps with native Go vendoring ###
  If you are using the native Go vendoring system, which packages all local dependencies in the `vendor/` directory, you must specify your app's package name in the `GOPACKAGENAME` environment variable. An example `manifest.yml`:
  
  ```yaml
  
negative.code:       GO15VENDOREXPERIMENT: 0
  ```
  
  ### <a id='with_glide'></a>Pushing Apps with Glide ###
  If you are using [glide](https://github.com/Masterminds/glide) to specify and/or package your dependencies, make sure that you have created a valid `glide.yaml` file in the root directory of your app by running `glide init`.
  
  To vendor your dependencies before pushing, run `glide install`. This will generate a `vendor` directory and a `glide.lock` file specifying the latest compatible versions of your dependencies. A `glide.lock` is not required when deploying a non-vendored app. A `glide.lock` is required when pushing a vendored app.
  