> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/getting-started/ci-setup/github-actions.md).

# GitHub Actions

Start with [Quick Start](/getting-started/ci-setup/github-actions/playwright-github-actions.md) for a workflow that records to Currents, then add what your setup needs from the articles below.

## Setup

* [Quick Start](/getting-started/ci-setup/github-actions/playwright-github-actions.md) — a workflow that records tests to Currents, and how to parallelize it.
* [Commit data for GitHub Actions](/getting-started/ci-setup/github-actions/commit-data-for-github-actions.md) — get the correct commit, branch and pull request on a run.
* [Custom Docker runners](/getting-started/ci-setup/github-actions/custom-docker-runners.md) — the environment variables to pass when the job runs in your own container.
* [Named Runners](/getting-started/ci-setup/github-actions/named-runners.md) — show which runner executed each spec file.

## Reruns

* [Re-run Only Failed Tests](/getting-started/ci-setup/github-actions/re-run-failed-only-tests.md) — re-run only the tests that failed, for [sharded](/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-sharded.md) and [orchestrated](/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-orchestrated-v2.md) runs.
* [Custom CI Build ID for Reruns](/getting-started/ci-setup/github-actions/re-run-failed-only-tests/custom-ci-build-id-for-reruns.md) — when your workflow sets its own CI build ID.

## Cancellation

* [Cancel Runs on Workflow Cancellation](/getting-started/ci-setup/github-actions/cancel-runs.md) — cancel the Currents run when the workflow is cancelled, so it does not sit in progress until the run timeout.

## Examples

The [currents-examples](https://github.com/currents-dev/currents-examples/tree/main/playwright/ci/github-actions) repository has complete workflows for sharding, orchestration, reruns and visual testing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.currents.dev/getting-started/ci-setup/github-actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.