anchor.diff:  
   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.
  +1. Change into the `public-buildpacks-ci-robots` directory and check that there are no uncommitted changes.
   	<pre class='terminal'>
  -	$ cd ~/workspace/buildpacks-ci
  +	$ cd ~/workspace/public-buildpacks-ci-robots
   	$ 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. Change to the `binary-builds` directory.
  +	<pre class="terminal">
  +	$ cd binary-builds
  +	</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
  
positive.code: 
  <p class="note"><strong>Note</strong>: The steps below assume you are using a Concourse deployment of the <code>buildpacks-ci</code> pipelines and Pivotal Tracker.</p>
  
  1. Change into the directory of the buildpack for which you want to update dependencies and check out the `develop` branch. 
      <pre class="terminal">
      $ cd ~/workspace/ruby-buildpack
      $ git checkout develop
  
negative.code: The CF buildpacks team uses the following tools to update dependencies:
  
  * A [Concourse](https://concourse.ci) deployment of the [buildpacks-ci](https://github.com/cloudfoundry/buildpacks-ci) pipelines
  * [public-buildpacks-ci-robots](https://github.com/cloudfoundry/public-buildpacks-ci-robots) repo
  * [Pivotal Tracker](https://www.pivotaltracker.com) for workflow management
  
  <p class="note"><strong>Note</strong>: The procedures in this topic refer to the tools used by the CF buildpacks team. However, the procedures do not require the specific tools mentioned above. You can use any CI and workflow management tool to update dependencies in custom buildpacks.</p>
  
  When the [New Releases](https://buildpacks.ci.cf-app.com/pipelines/notifications/jobs/New%20Releases) job in the [notifications pipeline](https://buildpacks.ci.cf-app.com/pipelines/notifications)
  detects a new version of a tracked dependency in a buildpack, it creates a [Tracker](https://www.pivotaltracker.com) story about building and including the new version of the dependency in the buildpack manifests. It also posts a message as the `dependency-notifier` to the [#buildpacks channel](https://cloudfoundry.slack.com/messages/buildpacks/) in the Cloud Foundry Slack.
  