anchor.diff:     JSON or YAML configuration file. If no configuration file is provided,
      we look for the file in the following locations:
   
  -   - buildkite.yml
  -   - buildkite.json
      - .buildkite/pipeline.yml
      - .buildkite/pipeline.json
  -   - .buildkite/steps.json (deprecated, will be removed in 2.2)
   
      You can also pipe build pipelines to the command, allowing you to create scripts
      that generate dynamic pipelines.
  
positive.code: You can use either [YAML](http://yaml.org) or [JSON](http://json.org) to configure your build pipelines. Below is an example of how the YAML configuration would look.
  
  ```
  # buildkite.yml
  
  steps:
    -
      name: "\:bundler\:"
      command: "bundle install -j8"
      concurrency: 1
      concurrency_group: bundler
    -
      type: "waiter"
    -
      name: "\:rubocop\:"
      command: "script/buildkite/rubocop"
    -
      name: "\:brakeman\:"
      command: "script/buildkite/brakeman"
    -
      name: "\:eslint\:"
      command: "script/buildkite/eslint"
    -
      name: "\:rspec\:"
      command: "script/buildkite/rspec"
      artifact_paths: "tmp/capybara/**/*;coverage/**/*"
      parallelism: 6
    -
      type: "waiter"
    -
      name: "\:shipit\:"
      command: "script/buildkite/deploy"
      branches: "master"
      env:
        DEPLOY_KEY: "xxx"
      agents:
        - "queue=deploy"
      concurrency: 1
      concurrency_group: deploy
  ```
  
negative.code: ```bash
  #!/bin/bash
  
  if [ -f ".buildkite/pipeline.yml" ];
  then
    echo ".buildkite/pipeline.yml found, will replace current pipeline with steps from it"
    buildkite-agent pipeline upload --replace
  else
    echo "No .buildkite/pipeline.yml file, using existing steps"
  fi
  ```
  
  