anchor.diff:  
   ### Pipeline.yml file
   
  -To use a pipeline.yml file, click the ➕ to add a step and select “Read steps from repository”:
  +Before getting started with a pipeline.yml file, you'll need to tell Buildkite where to find your steps.
  +
  +In your Buildkite pipeline settings, add a new step using the ➕ button and choose 'read steps from repository'.
   
   <%= image "pipeline-upload-step.png", width: 612/2, height: 484/2, alt: "Screenshot of the 'Read steps from repository' menu item" %>
   
  
positive.code: 
  <%= image "pipeline-upload.png", width: 1174/2, height: 452/2, alt: "Screenshot of the pipeline upload step" %>
  
  When this step runs on an agent, it adds the steps you defined in `.buildkite/pipeline.yml` to your pipeline. For example, here is a pipeline file with a single step:
  
  ```yml
  steps:
  
negative.code:     command: echo "Hello!"
  ```
  
  With the above example code in a `pipeline.yml` file, commit and push the file up to your repository. If you have set up webhooks, this will automatically create a new build. You can also create a new build using the 'New Build' button on the pipeline page.
  
  <%= image "show-example-test.png", width: 968/2, height: 698/2, alt: "Screenshot of the build passing with pipeline upload step first, and then the example step" %>
  
  For more example steps and detailed configuration options, see the example `pipeline.yml` below, or the step type specific documentation: [command steps](/docs/pipelines/command-step), [wait steps](/docs/pipelines/wait-step), [block steps](/docs/pipelines/block-step), and [trigger steps](/docs/pipelines/trigger-step).
  
  If your pipeline has a lot of steps and you have multiple agents available to run them, they will automatically run at the same time. If your steps rely on running in sequence, you can separate them with [wait steps](/docs/pipelines/wait-step) to ensure that the steps before the 'wait' are completed before subsequent steps are run.  
  
  When each step is run by an agent, it will be run with a clean checkout of the pipeline's repository. If your commands or scripts rely on the output from previous steps, you will need to either combine them into a single script or use [artifacts](docs/pipelines/artifacts) to pass data between steps. This enables any step to be picked up by any agent and run steps concurrently to speed up your build.
  
  ## Example pipeline
  
  