anchor.diff:  
       <pre class="terminal">$ git commit -m "YOUR-COMMIT-MESSAGE[#STORY_NUMBER]"</pre>
   
  -1. Push your changes to the remote origin. 
  +1. Push your changes to the remote origin.
   
       <pre class="terminal">$ git push</pre>
   
   1. Pushing your changes triggers the binary building process, which you can  monitor at the [binary-builder pipeline](https://buildpacks.ci.cf-app.com/pipelines/binary-builder)
  -of your own `buildpacks-ci` Concourse deployment. When the build completes, it adds a link to the Concourse build run to the Tracker story for the new release. 
  +of your own `buildpacks-ci` Concourse deployment. When the build completes, it adds a link to the Concourse build run to the Tracker story for the new release.
   
       <p class="note"><strong>Note</strong>: Binary builds are executed by the CF <a href="https://github.com/cloudfoundry/binary-builder">Binary Builder</a> and the <a href="https://github.com/cloudfoundry/buildpacks-ci/blob/master/pipelines/binary-builder.yml">binary-builder pipeline</a>.</p>
   
  
positive.code: 
  To build the binary for a dependency, perform the following steps:
  
  1. Change into the `buildpacks-ci` directory and check that there are no uncommitted changes.
  	<pre class='terminal'>
  	$ cd ~/workspace/buildpacks-ci
  	$ git status
  	</pre>
  1. Check out the `binary-builds` branch. This is an orphan branch of `buildpacks-ci` that the CF buildpacks team uses as a separate resource on Concourse to trigger the binary building process.
  	<pre class="terminal">
  	$ git checkout binary-builds
  	</pre>
  1. Pull the branch to make sure it is up to date.
  	<pre class="terminal">
  	$ git pull -r
  	</pre>
  1. Locate the YAML file for the buildpack you want to build a binary for. The directory contains YAML files for all the packages and dependencies tracked by the CF buildpacks team. Each YAML file correlates to the build queue for one dependency or package and the naming format is `DEPENDENCY-NAME.yml`. For example, the YAML file tracking the build queue for Ruby is called `ruby-builds.yml` and contains the following contents:
  
      ```yaml
  
negative.code: 
  ###<a id="build-go-buildpack"></a>Go Buildpack
  
  __Go__:
  
  * Built from: a tarred binary (`GO-VERSION.linux-amd64.tar.gz`) provided by Google on the Go [Downloads](https://golang.org/dl/) page
  * Verified with: the MD5 of the tarred binary
  * Example usage: [Using the Google Tarred Binary for Go 1.6.2](https://github.com/cloudfoundry/go-buildpack/blob/v1.7.8/manifest.yml#L33-L34)
  
  __Godep__:
  
  * Built from: a source code `.tar.gz` file from the [Godep Github releases](https://github.com/tools/godep/releases) page
  * Verified with: the SHA256 of the source
  Example: [Automated enqueuing of binary build for Godep 72](https://github.com/cloudfoundry/buildpacks-ci/commit/42a361193ea9a4c77a93451228c93bf96f78d50a)
  
  