anchor.diff:  # Defining Your Pipeline Steps
   
  -Pipeline steps can be defined visually in Buildkite or, more powerfully, in code using a `pipeline.yml` file.  
  +Pipeline steps can be defined visually in Buildkite or, more powerfully, in code using a `pipeline.yml` file.
   
   Defining your pipeline steps in a `pipeline.yml` file gives you access to more configuration options than the web interface, and allows you to version, audit and review your build pipelines alongside your source code.
   
  
positive.code: 
  When creating a new pipeline, you can take a shortcut if you want to set up the new pipeline with the same steps as an existing pipeline.
  
  Using the `?clone` URL parameter, you can prefill the new pipeline page with the steps from another pipeline. It will not copy any other fields such as environment variables or repository information. 
  
  The below example URL will copy the steps from the 'My Llamas Pipeline' into the New Pipeline page: 
  
  ```
  https://buildkite.com/organizations/acme-inc/pipelines/new?clone=my-llamas-pipeline
  
negative.code: 
  Create a file called `pipeline.yml` in a directory called `.buildkite` in your repository. This file will describe your pipeline steps in YAML, and will be versioned alongside your code.
  
  If you're using any tools that ignore hidden directories, you can store your `pipeline.yml` file either in the top level of your repository, or in a non-hidden directory called `buildkite`.
  
  The following example YAML defines a pipeline with one command step that will echo 'Hello' into your build log:
  
  