anchor.diff:    - name: my-app-name
       env:
         GOVERSION: go1.8
  +      ```
  +
  +### <a id='with_dep'></a>Push an App with dep ###
  +If you use [dep](https://github.com/golang/dep) to specify or package your dependencies,
  +make sure that you have created a valid `Gopkg.toml` file in the root directory of your app by running `dep init`.
  +
  +To vendor your dependencies before pushing, run `dep ensure`.
  +This will generate a `vendor` directory and a `Gopkg.lock` file specifying the latest compatible versions of your dependencies.
  +You must have a `Gopkg.lock` file when pushing a vendored app. You do not need a `Gopkg.lock` file when deploying a non-vendored app.
  +
  +####<a id='dep_app'></a>dep####
  +* [Sample Go app with dep](https://github.com/cloudfoundry/go-buildpack/tree/master/fixtures/go18_dep)
  +
  +An example `Gopkg.toml` file:
  +
  +```toml
  +[[constraint]]
  +  branch = "master"
  +  name = "github.com/ZiCog/shiny-thing"
  +```
  +
  +You can specify Go version in the `manifest.yml` file:
  +
  +```yaml
  +---
  +applications:
  +  - name: my-app-name
  +    env:
  +      GOVERSION: go1.8
   ```
   
   ### <a id='pushing_Apps_with_native_Go_vendoring'></a>Push an App with Native Go Vendoring ###
  -If you use 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. 
  +If you use 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`:
   
  
positive.code: - Your app has a `vendor/` directory and has any files ending with `.go`.
  - Your app has a `GOPACKAGENAME` environment variable specified and has any files ending with `.go`.
  - Your app has a `glide.yml` file and is using [glide](https://github.com/Masterminds/glide), starting in buildpack version <a href="https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.7.9">1.7.9</a>.
  
  If your Cloud Foundry deployment does not have the Go Buildpack installed, or the installed version is out of date, you can use the latest version with the command:
  
  
negative.code: 
  ## <a id='passing_symbol_linker'></a>Pass a Symbol and String to the Linker ##
  
  The Go buildpack supports the Go [linker's](https://golang.org/cmd/link/) ability, `-X symbol value`,
  to set the value of a string at link time.
  Set the `GO_LINKER_SYMBOL` and `GO_LINKER_VALUE` in the application's configuration  before pushing code.
  
  This can be used to embed the commit SHA or other build-specific data directly
  