anchor.diff:        <em>Example:</em> <code>"My reason"</code>
       </td>
     </tr>
  +
  +  <tr>
  +    <td><code>agents</code></td>
  +    <td>
  +      A map of <a href="/docs/agent/v3/cli-start#setting-tags">agent tag</a> keys to values to <a href="/docs/agent/v3/cli-start#agent-targeting">target specific agents</a> for this step. <br>
  +      <em>Example:</em> <code>npm: "true"</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>artifact_paths</code></td>
  +    <td>
  +      The <a href="/docs/agent/v3/cli-artifact#uploading-artifacts">glob path</a> or paths of <a href="/docs/agent/v3/cli-artifact">artifacts</a> to upload from this step. This can be a single line of paths separated by semicolons, or a list.<br>
  +      <em>Example:</em> <code>"logs/**/*;coverage/**/*"</code><br>
  +      <em>Example:</em><br><code>- "logs/**/*"</code><br><code>- "coverage/**/*"</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>branches</code></td>
  +    <td>
  +      The <a href="/docs/pipelines/branch-configuration#branch-pattern-examples">branch pattern</a> defining which branches will include this step in their builds.<br>
  +      <em>Example:</em> <code>"master stable/*"</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>concurrency</code></td>
  +    <td>
  +      The <a href="/docs/pipelines/controlling-concurrency#concurrency-limits">maximum number of jobs</a> created from this step that are allowed to run at the same time. If you use this attribute, you must also define a label for it with the <code>concurrency_group</code> attribute.<br>
  +      <em>Example:</em> <code>3</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>concurrency_group</code></td>
  +    <td>
  +      A unique name for the concurrency group that you are creating with the <code>concurrency</code> attribute.<br>
  +      <em>Example:</em> <code>"my-app/deploy"</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>env</code></td>
  +    <td>
  +      A map of <a href="/docs/pipelines/environment-variables">environment variables</a> for this step.<br>
  +      <em>Example:</em> <code>RAILS_ENV: "test"</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>id</code></td>
  +    <td>
  +      A string to identify the step. The value is available in the <code>BUILDKITE_STEP_IDENTIFIER</code> <a href="/docs/pipelines/environment-variables">environment variable</a>.<br>
  +      <em>Example:</em> <code>"linter"</code>
  +      <em>Alias:</em> <code>identifier</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>label</code></td>
  +    <td>
  +      The label that will be displayed in the pipeline visualisation in Buildkite. Supports emoji.<br>
  +      <em>Example:</em> <code>"\:hammer\: Tests"</code><br>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>parallelism</code></td>
  +    <td>
  +      The number of <a href="/docs/tutorials/parallel-builds#parallel-jobs">parallel jobs</a> that will be created based on this step. <br>
  +      <em>Example:</em> <code>3</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>plugins</code></td>
  +    <td>
  +      An array of <a href="/docs/pipelines/plugins">plugins</a> for this step.<br>
  +      <em>Example:</em><br>
  +      <code>- docker-compose#v1.0.0:<br>
  +&nbsp;&nbsp;&nbsp;&nbsp;run: app</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>retry</code></td>
  +    <td>
  +      The conditions for retrying this step.<br>
  +      Available retry types: <code>automatic</code>,<code>manual</code>
  +    </td>
  +  </tr>
  +  <tr>
  +    <td><code>skip</code></td>
  +    <td>
  +      Whether to skip this step or not. Passing a string provides a reason for skipping this command. Passing an empty string is equivalent to <code>false</code>.
  +      Note: Skipped steps will be hidden in the pipeline view by default, but can be made visible by toggling the 'Skipped jobs' icon.<br>
  +      <em>Example:</em> <code>true</code><br>
  +      <em>Example:</em> <code>false</code><br>
  +      <em>Example:</em> <code>"My reason"</code>
  +    </td>
  +  </tr>
  +
  +  <tr>
  +    <td><code>soft_fail</code></td>
  +    <td>
  +      Should this step cause the build to fail if it exits with a non-zero status.
  +      Can be either an array of soft failure exit statuses or <code>true</code> to make all exit statuses soft-fail.
  +
  +      An array of failure conditions that when matched indicate that the step should soft-fail.<br>
  +      <em>Example:</em> <code>true</code><br>
  +      <em>Example:</em><br>
  +      <code>- exit_status: 1</code><br>
  +      <code>- exit_status: "*"</code><br>
  +    </td>
  +  </tr>
  +
  +
     <tr>
       <td><code>timeout_in_minutes</code></td>
       <td>
  
positive.code:       manual:
          allowed: false
          reason: "Sorry, you can't retry a deployment"
  ```
  
negative.code: _Optional attributes:_
  
  <table>
    <tr>
      <td><code>skip</code></td>
      <td>
  