anchor.diff:  # Group Step
  - 
  +
   A *group* step can contain various sub-steps, and display them in a single logical group on the Build page. For example, you can group all of your linting steps or all of your UI test steps to keep the Build page less messy. Sub-groups and nested groups are not supported.
   
   The group step also helps manage dependencies between a collection of steps, for example, "step X" [`depends_on`](/docs/pipelines/group-step#group-step-attributes) everything in "group Y".
   
   {:toc}
  - 
  -A group step can be defined in your pipeline settings or your [pipeline.yml](/docs/pipelines/defining-steps) file.  
  -
  -Here is an example of using the group step:  
  +
  +A group step can be defined in your pipeline settings or your [pipeline.yml](/docs/pipelines/defining-steps) file.
  +
  +Here is an example of using the group step:
   
   ```yml
   - group: "\:lock_with_ink_pen\: Security Audits"
  
positive.code:   </tr>
  </table>
  
  _Optional attributes:_  
  
  <table data-attributes>
    <tr>
  
negative.code:   <tr>
      <td><code>key</code></td>
      <td>
      A unique string to identify the step, block, or group. Alias: `identifier` or `id`.<br>
        <em>Example:</em> <code>"test-suite"</code>
      </td>
    </tr>
    <tr>
      <td><code>label</code></td>
      <td>
  