> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/review-workflow/summary-checks.md).

# Summary checks

Configure Argos summary checks to combine commit statuses into one required status check before merging.

A **summary check** is a single commit status — `argos/summary` — that combines the result of all Argos builds on a commit. When your CI produces several builds (for example, one per app in a monorepo), the summary check gives you one status to glance at, and one status to require.

By default, Argos adds the summary check **only when a commit has more than one build** — a single build keeps its individual status (`argos`, or `argos/<build-name>` for a named build) with no summary added. See [Commit status names](/docs/learn/integrations/github-integration.md#commit-status-names) for the exact context of each status Argos posts.

![Summary status check in GitHub](https://content.gitbook.com/content/0slCNmeVzY3qdh0I85HX/blobs/FNRkxoePm6BADbJLuvYW/summary%20check%20d7953362698c802ff3f81de23bfb83cc.png)

Summary checks are particularly useful as a [required status check before merging](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging): require the summary check instead of each individual build check, and the requirement keeps working as you add or rename builds.

![Required Argos status check in GitHub](https://content.gitbook.com/content/0slCNmeVzY3qdh0I85HX/blobs/ZMNlRIuPWRHhQbcGFY7b/required%20status%20check%200c8c4bf869c27334b7e13f5decd2ff08.png)

### Options

Argos offers three settings for summary checks:

* **Add a summary check only if there is more than one build** — The default, recommended for most projects. The summary check appears when there are multiple builds to combine, and stays out of the way otherwise.
* **Always add a summary check** — The summary check is posted even for a single build. Choose this if you require the summary check in your branch protection and some commits produce only one build — the required check is then always present.
* **Never add a summary check** — Disable summary checks entirely if they don't add value to your workflow.

Summary checks are an additional layer of status reporting — they never replace the individual build statuses.

### Configure summary checks

1. Go to your project **Settings** in Argos.
2. Locate the **Summary Checks** section.
3. Choose the option that fits your project.
4. Select **Save** to apply the changes.

![Configure summary checks in Argos](https://content.gitbook.com/content/0slCNmeVzY3qdh0I85HX/blobs/jCQDBAiCXLBeNQQnCZIH/configure%20summary%20checks%20db8f96ec82fc779a58d5e273c492cf02.png)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://argos-ci.com/docs/learn/review-workflow/summary-checks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.