anchor.diff:  
   When using godep, you can fix your Go version in `GoVersion` key of the `Godeps/Godeps.json` file.
   
  -The following is an example `Godeps/Godeps.json` file:
  +#### <a id='godeps_1.6'></a>Go Sample App
  +
  +* [Sample Go app](https://github.com/cloudfoundry/go-buildpack/tree/master/fixtures/godep)
  +
  +An example `Godeps/Godeps.json`:
   
   ```json
   {
  
positive.code: If you do not specify a start command in a `Procfile`, in the manifest, or with the `-c` flag for `cf push`, the generated binary will be used as the start command. Example: `my-go-server`
  
  ### <a id='with_godep'></a>Push an App with Go Modules ###
  
  In Go v1.11 and later, you can use the `go mod` vendoring tool that comes with Go.
  If you are using [go mod](https://github.com/golang/go/wiki/Modules) to package your dependencies, make sure that you have created a valid `go.mod` file in the root directory of your app by running `go mod init`.
  
  The following is an example `go.mod` file:
  
  ```
  module go-online
  
negative.code: This will generate a `vendor` directory and a `glide.lock` file specifying the latest compatible versions of your dependencies.
  You must have a `glide.lock` file when pushing a vendored app. You do not need a `glide.lock` file when deploying a non-vendored app.
  
  ####<a id='glide_app'></a>Glide
  
  * [Sample Go app with Glide](https://github.com/cloudfoundry/go-buildpack/tree/master/fixtures/glide)
  
  An example `glide.yml` file:
  
  ```yaml
  package: go_app_with_glide
  