> 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/how-to-guides/ci-pipelines.md).

# CI pipelines

Run Argos in GitHub Actions, GitLab CI, CircleCI, Buildkite, or any other CI, with patterns for monorepos, sharding, preview deployments, and subset builds.

Patterns for running Argos efficiently inside your continuous integration pipeline.

* [Run Argos in CI](/docs/learn/how-to-guides/ci-pipelines/run-argos-in-ci.md) — pipeline examples for GitHub Actions, GitLab CI, CircleCI, and Buildkite, the CI providers Argos detects, and the environment variables for any other CI.
* [Monorepos setup](/docs/learn/how-to-guides/ci-pipelines/monorepos-setup.md) — run Argos for multiple projects in a single repository.
* [Parallel testing (sharding)](/docs/learn/how-to-guides/ci-pipelines/parallel-testing-sharding.md) — collect screenshots from sharded or parallelized test runs into a single build.
* [Cached CI pipelines (Turborepo, Nx)](/docs/learn/how-to-guides/ci-pipelines/cached-pipelines.md) — keep builds, baselines, and required checks reliable when a task cache decides which suites run.
* [Run on preview deployments](/docs/learn/how-to-guides/ci-pipelines/run-on-preview-deployments.md) — trigger Argos against a deployed preview environment.
* [Skipping a build](/docs/learn/how-to-guides/ci-pipelines/skipping-a-build.md) — skip an Argos build when a visual comparison isn't needed.
* [Subset builds](/docs/learn/how-to-guides/ci-pipelines/subset-builds.md) — upload a partial run without affecting the baseline of screenshots it didn't cover.


---

# 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/how-to-guides/ci-pipelines.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.