anchor.diff:  
   ## <a id='pushing_apps'></a> Push an App ##
   
  -The Go buildpack will be automatically detected if:
  -
  -- Your app has been packaged with [godep](https://github.com/tools/godep) using `godep save`
  +The Go buildpack will be automatically detected in the following circumstances:
  +
  +- Your app has been packaged with [godep](https://github.com/tools/godep) using `godep save`.
   - 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.yaml` file and is using [glide](https://github.com/Masterminds/glide) <span style="font-size:1rem">(starting in buildpack version <a href="https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.7.9">1.7.9</a>)</span>.
  +- 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:
   
  
positive.code: 
  ## <a id='passing_symbol_linker'></a>Pass a Symbol and String to the Linker ##
  
  This 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. This can be done by setting
  `GO_LINKER_SYMBOL` and `GO_LINKER_VALUE` in the application's config before
  pushing code.
  
  This can be used to embed the commit SHA, or other build specific data directly
  into the compiled executable.
  
  For an example usage, see the relevant [fixture app](https://github.com/cloudfoundry/go-buildpack/tree/develop/cf_spec/fixtures/go1.6_app_using_ldflags/src/go_app).
  
  ## <a id='c_dependencies'></a>C Dependencies ##
  
  This buildpack supports building with C dependencies via
  [cgo](https://golang.org/cmd/cgo/). You can set config vars to specify CGO flags
  to, e.g., specify paths for vendored dependencies. E.g., to build
  [gopgsqldriver](https://github.com/jbarham/gopgsqldriver), add the config var
  `CGO_CFLAGS` with the value `-I/app/code/vendor/include/postgresql` and include
  the relevant Postgres header files in `vendor/include/postgresql/` in your app.
  
  ## <a id='proxy_support'></a> Proxy Support ##
  
  If you need to use a proxy to download dependencies during staging, you can set
  the `http_proxy` and/or `https_proxy` environment variables. For more information, see
  the [Proxy Usage Docs](http://docs.cloudfoundry.org/buildpacks/proxy-usage.html).
  
  ## <a id='bosh_trusted_cert'></a>BOSH Configured Custom Trusted Certificate Support ##
  
  Go uses certificates stored in `/etc/ssl/certs` and supports [BOSH configured custom trusted certificates](http://bosh.io/docs/trusted-certs.html) out of the box. 
  
  ## <a id='help_support'></a>Help and Support ##
  
  
negative.code: $ cf push my_app -b https://github.com/cloudfoundry/go-buildpack.git
  </pre>
  
  When specifying versions, specify only major/minor versions, such as Go 1.6, rather than Go 1.6.0. This ensures you receive the most recent patches.
  
  ### <a id='start_command'></a>Start Command ###
  
  When pushing Go goapps, you can specify a start command for the app. You can place the start command in the `Procfile` file in root directory of your app. For example, if the binary generated by your Go project is `my-go-server`, your `Procfile` could contain the following:
  
  ```
  web: my-go-server
  