April 11, 2026

## Pipelines

### Consolidated Comments for Pipelines and Terragrunt Scale

Pipelines version [v4.12.0](https://github.com/gruntwork-io/pipelines-workflows/releases/tag/v4.12.0) (GitHub) / [v2.9.0](https://gitlab.com/gruntwork-io/pipelines-workflows/-/releases/v2.9.0) (GitLab) now supports consolidating status update comments into a single comment on your pull requests and merge requests, instead of creating a new comment on every push.

By default, Pipelines creates a fresh status comment each time you push (`new_comment_per_push = true`). To switch to consolidated comments, add this to your `gruntwork.hcl` or `.gruntwork/repository.hcl` file:

```hcl
repository {
  # ...
  status_update {
    new_comment_per_push = false
  }
}
```

You can find the full documentation for this feature and all of Pipelines HCL [here](https://docs.gruntwork.io/2.0/reference/pipelines/configurations-as-code/api#new_comment_per_push).

GitHub retains the history of all edits made to a comment, which means you can still easily access results from previous plans right from the pull request. Here’s what you’ll see:

GitLab comments are overwritten silently. If you choose to enable this feature, you can still view the output of previous runs in your GitLab CI pipeline history.