anchor.diff:  
   ## Step 4: Test with Manual Build
   
  -Click "Run Plan Manually" on the next screen. Provide a revision ID for the repository inside Phabricator.
  +Click "Run Plan Manually" on the next screen. Provide a revision ID from the repository inside Phabricator.
   
   <%= image "phabricator_manual_build_trigger.png", alt: "Run a manual build in Phabricator" %>
   
  -Next, your Buildkite Pipeline should run then report back to Phabricator.
  +Your Buildkite Pipeline should run then report back to Phabricator.
   
   <%= image "phabricator_build_status.png", alt: "Build status in Phabricator" %>
   <%= image "buildkite_pipeline.png", alt: "Build status in Phabricator" %>
  
positive.code: 
  ## Step 2: Configure Buildkite Notification Webhook
  
  Phabricator and Buildkite integrate via webhooks. Phabricator triggers events
  in Buildkite, then Buildkite reports the status. You need to create an API
  Access Token in Buildkite to configure Phabricator.
  
  Open the [New API Access
  Token](https://buildkite.com/user/api-access-tokens/new) page in Buildkite.
  Provide a description, then select the relevant organization. Check
  `read_builds` and `write_builds`. Create the token then save a copy on the next screen.
  
  <%= image "buildkite_new_api_access_token.png", alt: "Creating a new Buildkite API Access Token" %>
  
  Next, configure the "Webhook Notification" for your Buildkite organization.
  
  From Phabrictor use the "Webhook URL" under "Webhook Configuration" (it should
  end in `/harbormaster/hook/buildkite/`) for "Webhook URL" in Buildkite.  Make a
  note of the autogenerated value in the "Token" field in Buildkite.  Check
  `build.finished` under Events, then save the notification settings.
  
  <%= image "buildkite_notification_webhook_settings.png", alt: "Buildkite Notification Webhook settings" %>
  
  Now back to Phabricator.
  
  ## Step 3: Complete Phabricator Build Step
  
  Press "Add New Credential" for "API Token". Provide a name and use the
  Buildkite API Access Token generated in earlier for the "Token" field.
  
  <%= image "phabricator_new_credential.png", alt: "Creating a new Credential in Phabricator" %>
  
  
negative.code: # Phabricator
  
  [Phabricator][] can trigger Buildkite on new revisions through Habormaster.
  
  <%= toc %>
  
  ## Prerequisites
  
  Check that your repository is activated in your Phabricator instance and
  Habormaster is installed. Configure a pipeline for that repository in Buildkite.
  You also need admin accces in your Phabricator and your Buildkite organization.
  
  ## Step 1: New Phabricator Build Step
  
  Create a new Build Plan in Harbormaster. Inside Habormaster open "Manage
  Build Plans". Press "Create Build Plan" located in the upper right.
  
  <%= image "phabricator_create_build_plan.png", alt: "Creating a new Build Plan in Phabricator" %>
  
  Provide a name then press "Create Build Plan".
  
  Now, add a step to the Build Plan. A "Build Step" calls one BuildKite
  "pipeline". If you need to call multiple pipelines then create multiple Build
  Steps.
  
  