# GitHub Actions

- [Quick Start](https://docs.currents.dev/getting-started/ci-setup/github-actions/playwright-github-actions.md): Running Playwright tests in Parallel in GitHub Actions using Matrix Workflow
- [Re-run Only Failed Tests](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests.md): How to set up failed test reruns on GitHub Actions
- [Sharded runs](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-sharded.md): How to set up failed test reruns for sharded Playwright runs on GitHub Actions
- [Orchestrated runs](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-orchestrated-v2.md): How to set up failed test reruns for Orchestration on GitHub Actions
- [Custom CI Build ID for Reruns](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/custom-ci-build-id-for-reruns.md): How to configure custom CI build IDs for failed test reruns on GitHub Actions
- [Commit data for GitHub Actions](https://docs.currents.dev/getting-started/ci-setup/github-actions/commit-data-for-github-actions.md): How to get correct git commit information when using GitHub Actions
- [Custom Docker runners](https://docs.currents.dev/getting-started/ci-setup/github-actions/custom-docker-runners.md): Self hosted/managed docker runners
- [Named Runners](https://docs.currents.dev/getting-started/ci-setup/github-actions/named-runners.md): Github Actions provides the ability to use human-readable runner names, and Currents displays these in the dashboard, allowing you to see which runner executed each spec file.


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.