{ "doc": { "id": "app/continuous-integration/github-actions", "title": "Run Cypress tests in GitHub Actions: A Step-by-Step Guide", "description": "Set up GitHub Actions to run Cypress tests, cache dependencies and build artifacts, and parallelize Cypress tests.", "section": "app", "source_path": "/llm/markdown/app/continuous-integration/github-actions.md", "version": "3cf5b86b3403f604bdf7f3e35025c3bc3865e02c", "updated_at": "2026-05-07T17:44:31.931Z", "headings": [ { "id": "app/continuous-integration/github-actions#run-cypress-in-github-actions", "text": "Run Cypress in GitHub Actions", "level": 1 }, { "id": "app/continuous-integration/github-actions#what-youll-learn", "text": "What you'll learn", "level": 5 }, { "id": "app/continuous-integration/github-actions#github-actions-cypress-screencasts", "text": "GitHub Actions + Cypress Screencasts", "level": 2 }, { "id": "app/continuous-integration/github-actions#cypress-github-action", "text": "Cypress GitHub Action", "level": 2 }, { "id": "app/continuous-integration/github-actions#version-number-selection", "text": "Version Number Selection", "level": 3 }, { "id": "app/continuous-integration/github-actions#basic-setup", "text": "Basic Setup", "level": 2 }, { "id": "app/continuous-integration/github-actions#testing-on-github-with-installed-browsers", "text": "Testing on GitHub with Installed Browsers", "level": 2 }, { "id": "app/continuous-integration/github-actions#testing-with-cypress-docker-images", "text": "Testing with Cypress Docker Images", "level": 2 }, { "id": "app/continuous-integration/github-actions#caching-dependencies-and-build-artifacts", "text": "Caching Dependencies and Build Artifacts", "level": 2 }, { "id": "app/continuous-integration/github-actions#parallelization", "text": "Parallelization", "level": 2 }, { "id": "app/continuous-integration/github-actions#install-job", "text": "Install Job", "level": 3 }, { "id": "app/continuous-integration/github-actions#worker-jobs", "text": "Worker Jobs", "level": 3 }, { "id": "app/continuous-integration/github-actions#setting-up-parallelization", "text": "Setting up Parallelization", "level": 4 }, { "id": "app/continuous-integration/github-actions#specifying-browsers-in-parallel-builds", "text": "Specifying Browsers in Parallel Builds", "level": 3 }, { "id": "app/continuous-integration/github-actions#using-cypress-cloud-with-github-actions", "text": "Using Cypress Cloud with GitHub Actions", "level": 2 }, { "id": "app/continuous-integration/github-actions#cypress-real-world-example-with-github-actions", "text": "Cypress Real World Example with GitHub Actions", "level": 2 }, { "id": "app/continuous-integration/github-actions#common-problems-and-solutions", "text": "Common Problems and Solutions", "level": 2 }, { "id": "app/continuous-integration/github-actions#re-run-jobs-passing-with-empty-tests", "text": "Re-run jobs passing with empty tests", "level": 3 }, { "id": "app/continuous-integration/github-actions#pull-requests-commit-message-is-merge-sha-into-sha", "text": "Pull requests commit message is merge SHA into SHA", "level": 3 }, { "id": "app/continuous-integration/github-actions#see-also", "text": "See also", "level": 2 } ] }, "chunks": [ { "id": "app/continuous-integration/github-actions#what-youll-learn", "doc_id": "app/continuous-integration/github-actions", "heading": "What you'll learn", "heading_level": 5, "content_markdown": "##### What you'll learn\n\n* How to set up Cypress tests in GitHub Actions\n* How to cache dependencies and build artifacts\n* How to parallelize Cypress tests in GitHub Actions\n* How to use Cypress Cloud with GitHub Actions\n\nGitHub offers developers [Actions](https://github.com/features/actions) that provide a way to **automate, customize, and execute your software development workflows** within your GitHub repository. Detailed documentation is available in the [GitHub Action Documentation](https://docs.github.com/en/actions).\n", "section": "app", "anchors": [ "what-youll-learn" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 93 }, { "id": "app/continuous-integration/github-actions#github-actions-cypress-screencasts", "doc_id": "app/continuous-integration/github-actions", "heading": "GitHub Actions + Cypress Screencasts", "heading_level": 2, "content_markdown": "## GitHub Actions + Cypress Screencasts\n\n1. [What is Continuous Integration?](https://youtu.be/USX6AntcPyg)\n2. [Actions & Workflows](https://youtu.be/N0TOFWy1Xvg)\n3. [Understanding how to configure a workflow](https://youtu.be/vVr7DXDdUks)\n4. [Running Tests in GitHub Actions CI/CD Workflow](https://youtu.be/23ZGSrmbV_4)\n5. [Debugging Test Failures in CI](https://youtu.be/Oqq-_QZWzhg)\n6. [Running Tests in Parallel](https://youtu.be/96Yn_IiQUJI)\n", "section": "app", "anchors": [ "github-actions-cypress-screencasts" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 55 }, { "id": "app/continuous-integration/github-actions#cypress-github-action", "doc_id": "app/continuous-integration/github-actions", "heading": "Cypress GitHub Action", "heading_level": 2, "content_markdown": "## Cypress GitHub Action\n\nWorkflows can be packaged and shared as [GitHub Actions](https://github.com/features/actions). GitHub maintains many, such as the [checkout](https://github.com/marketplace/actions/checkout) and [Upload/Download Artifact Actions](https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts) actions used below.\n\nThe official [Cypress GitHub Action](https://github.com/marketplace/actions/cypress-io) is maintained by Cypress and our community to help ease the setup of Cypress in a GitHub Action. The action provides dependency installation (via npm, yarn, or pnpm), built-in caching of Node dependencies, and additional configuration options for advanced workflows.\n\n### Version Number Selection\n\n**GitHub Action Version Number**\n\nWe recommend binding to the action's latest major version by specifying `v7` when using the action.\n\nFor Example:\n\n```\njobs: cypress-run: steps: - uses: cypress-io/github-action@v7\n```\n\nAlternatively, as a mitigation strategy for unforeseen breaks, bind to a specific [release version tag](https://github.com/cypress-io/github-action/releases), for example `cypress-io/github-action@v7.1.0`. Read the [Cypress GitHub Action documentation](https://github.com/cypress-io/github-action#action-version) for more information.\n", "section": "app", "anchors": [ "cypress-github-action" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 177 }, { "id": "app/continuous-integration/github-actions#version-number-selection", "doc_id": "app/continuous-integration/github-actions", "heading": "Version Number Selection", "heading_level": 3, "content_markdown": "### Version Number Selection\n\n**GitHub Action Version Number**\n\nWe recommend binding to the action's latest major version by specifying `v7` when using the action.\n\nFor Example:\n\n```\njobs: cypress-run: steps: - uses: cypress-io/github-action@v7\n```\n\nAlternatively, as a mitigation strategy for unforeseen breaks, bind to a specific [release version tag](https://github.com/cypress-io/github-action/releases), for example `cypress-io/github-action@v7.1.0`. Read the [Cypress GitHub Action documentation](https://github.com/cypress-io/github-action#action-version) for more information.\n", "section": "app", "anchors": [ "version-number-selection" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 81 }, { "id": "app/continuous-integration/github-actions#basic-setup", "doc_id": "app/continuous-integration/github-actions", "heading": "Basic Setup", "heading_level": 2, "content_markdown": "## Basic Setup\n\nThe example below is a basic CI setup and job using the [Cypress GitHub Action](https://github.com/marketplace/actions/cypress-io) to run Cypress tests within the Electron browser. This GitHub Action configuration is placed within `.github/workflows/main.yml`.\n\n```\nname: Cypress Testson: pushjobs: cypress-run: runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 # Install npm dependencies, cache them correctly # and run all Cypress tests - name: Cypress run uses: cypress-io/github-action@v7 with: build: npm run build start: npm start\n```\n\n**How this action works:**\n\n* On _push_ to this repository, this job will provision and start a GitHub-hosted Ubuntu Linux instance to run the outlined `steps` for the declared `cypress-run` job within the `jobs` section of the configuration.\n* The [GitHub checkout Action](https://github.com/marketplace/actions/checkout) is used to check out our code from our GitHub repository.\n* Finally, our Cypress GitHub Action will:\n * Install npm dependencies\n * Build the project (`npm run build`)\n * Start the project web server (`npm start`)\n * Run the Cypress tests within our GitHub repository within Electron.\n", "section": "app", "anchors": [ "basic-setup" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 223 }, { "id": "app/continuous-integration/github-actions#testing-on-github-with-installed-browsers", "doc_id": "app/continuous-integration/github-actions", "heading": "Testing on GitHub with Installed Browsers", "heading_level": 2, "content_markdown": "## Testing on GitHub with Installed Browsers\n\n[GitHub-hosted runners](https://github.com/actions/runner-images) offer images with pre-installed browsers to use for testing. The `ubuntu` and `windows` runners each include Google Chrome, Mozilla Firefox, and Microsoft Edge pre-installed. The `macos` runners additionally include Apple Safari. Refer to [GitHub Actions Runner Images](https://github.com/actions/runner-images/blob/main/README.md) for current details.\n\nUse the action's `browser` parameter to select the desired browser. To change the above example to select Chrome instead of the default browser Electron, add `browser: chrome` as follows.\n\n```\n- name: Cypress run uses: cypress-io/github-action@v7 with: build: npm run build start: npm start browser: chrome\n```\n\nFor more examples, see the action's [Browser](https://github.com/cypress-io/github-action#browser) section.\n\nIf you are specifying a browser in a parallel job, see [Specifying Browsers in Parallel Builds](#Specifying-Browsers-in-Parallel-Builds) for more info on how to avoid errors during runs due to GitHub runner images being updated with the latest browsers.\n", "section": "app", "anchors": [ "testing-on-github-with-installed-browsers" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 188 }, { "id": "app/continuous-integration/github-actions#testing-with-cypress-docker-images", "doc_id": "app/continuous-integration/github-actions", "heading": "Testing with Cypress Docker Images", "heading_level": 2, "content_markdown": "## Testing with Cypress Docker Images\n\nGitHub Actions provides the option to specify a container image for the job. Cypress offers various [Docker Images](https://github.com/cypress-io/cypress-docker-images) for running Cypress locally and in CI.\n\nNote that GitHub Actions [requires using a Linux runner](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idcontainer) when specifying a container image. It does not support running Docker images on Windows or macOS runners.\n\nBelow, we extend the previous example by adding the `container` attribute using a [cypress/browsers](https://github.com/cypress-io/cypress-docker-images/tree/master/browsers) Docker image which also includes Google Chrome. We are using the Node.js short-form tag to select a `cypress/browsers` image built with the corresponding Node.js version. To specify instead an exact set of browser versions, visit the [Docker Hub cypress/browsers](https://hub.docker.com/r/cypress/browsers) page and view the available long-form tags, for example `cypress/browsers:node-22.15.0-chrome-136.0.7103.92-1-ff-138.0.1-edge-136.0.3240.50-1`. Using a Cypress Docker image allows our tests to execute without any influence from browser version changes in the GitHub runner image.\n\n```\nname: Cypress Tests using Cypress Docker Imageon: pushjobs: cypress-run: runs-on: ubuntu-24.04 container: image: cypress/browsers:22.15.0 options: --user 1001 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress run uses: cypress-io/github-action@v7 with: build: npm run build start: npm start browser: chrome\n```\n\nIf you are testing with Firefox, you must specify the non-root user `1001` as above. Refer to [Firefox not found](https://github.com/cypress-io/cypress-docker-images#firefox-not-found) for more information.\n", "section": "app", "anchors": [ "testing-with-cypress-docker-images" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 275 }, { "id": "app/continuous-integration/github-actions#caching-dependencies-and-build-artifacts", "doc_id": "app/continuous-integration/github-actions", "heading": "Caching Dependencies and Build Artifacts", "heading_level": 2, "content_markdown": "## Caching Dependencies and Build Artifacts\n\nWhen working with actions that have multiple jobs, it is recommended to have an initial \"install\" job that will download any dependencies and build your app, and then cache these assets for use later by subsequent jobs.\n\nThe Cypress GitHub Action will automatically cache and restore your Node dependencies for you.\n\nFor build assets, you will need to cache and restore them manually.\n\nThe `install` job below uses the [upload-artifact](https://github.com/marketplace/actions/upload-a-build-artifact) action and saves the state of the `build` directory for the `cypress-run` worker job.\n\nThe [download-artifact](https://github.com/marketplace/actions/download-a-build-artifact) action retrieves the `build` directory saved in the `install` job, as seen below in the `cypress-run` worker job.\n\n```\nname: Cypress Tests with Dependency and Artifact Cachingon: pushjobs: install: runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress install uses: cypress-io/github-action@v7 with: # Disable running of tests within install job runTests: false build: npm run build - name: Save build folder uses: actions/upload-artifact@v6 with: name: build if-no-files-found: error path: build cypress-run: runs-on: ubuntu-24.04 needs: install steps: - name: Checkout uses: actions/checkout@v6 - name: Download the build folder uses: actions/download-artifact@v7 with: name: build path: build - name: Cypress run uses: cypress-io/github-action@v7 with: start: npm start browser: chrome\n```\n\nView GitHub's guide on [Storing workflow data as artifacts](https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts) for more info.\n", "section": "app", "anchors": [ "caching-dependencies-and-build-artifacts" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 284 }, { "id": "app/continuous-integration/github-actions#parallelization", "doc_id": "app/continuous-integration/github-actions", "heading": "Parallelization", "heading_level": 2, "content_markdown": "## Parallelization\n\n[Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md) offers the ability to [parallelize and group test runs](/llm/markdown/cloud/features/smart-orchestration/parallelization.md) along with additional insights and [analytics](/llm/markdown/cloud/features/analytics/overview.md) for Cypress tests.\n\nUsing parallelization with the Cypress GitHub Action requires setting up recording to [Cypress Cloud](https://on.cypress.io/cloud).\n\nGitHub Actions offers a [matrix strategy](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) for declaring different job configurations for a single job definition. Jobs declared within a matrix strategy can run in parallel, which enables us to run multiples instances of Cypress at the same time, as we will see later in this section.\n\nBefore diving into an example of a parallelization setup, it is important to understand the two different types of GitHub Action jobs that we will declare:\n\n* **Install Job**: A job that installs and caches dependencies that will be used by subsequent jobs later in the GitHub Action workflow.\n* **Worker Job**: A job that handles the execution of Cypress tests and depends on the _install job_.\n\n### Install Job\n\nThe separation of installation from test running is necessary when running parallel jobs. It allows for the reuse of various build steps aided by caching.\n\nFirst, we'll define the `install` step that will be used by the worker jobs defined in the matrix strategy.\n\nFor the `steps`, notice that we pass `runTests: false` to the Cypress GitHub Action to instruct it only to install and cache Cypress and npm dependencies _without running the tests_.\n\nThe [upload-artifact](https://github.com/marketplace/actions/upload-a-build-artifact) action will save the state of the `build` directory for the worker jobs.\n\n```\nname: Cypress Testson: pushjobs: install: runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress install uses: cypress-io/github-action@v7 with: # Disable running of tests within install job runTests: false build: npm run build - name: Save build folder uses: actions/upload-artifact@v6 with: name: build if-no-files-found: error path: dist\n```\n\n### Worker Jobs\n\nNext, we define the worker job named \"cypress-run\" that will run Cypress tests as part of a parallelized matrix strategy.\n\nThe `download-artifact` action will retrieve the **dist** directory saved in the install job.\n\n```\nname: Cypress Testson: pushjobs: install: # ... omitted install job from above cypress-run: runs-on: ubuntu-24.04 needs: install strategy: # don't fail the entire matrix on failure fail-fast: false matrix: # run copies of the current job in parallel containers: [1, 2, 3, 4, 5] steps: - name: Checkout uses: actions/checkout@v6 - name: Download the build folder uses: actions/download-artifact@v7 with: name: build - name: Cypress run uses: cypress-io/github-action@v7 with: record: true parallel: true group: 'UI-Chrome' start: npm start\n```\n\n**Ensure Correct Container**\n\nIf a Docker container was used in the install job, the same Docker container must also be used in the worker jobs.\n\n#### Setting up Parallelization\n\nTo set up multiple containers to run in parallel, the matrix option of the strategy configuration can be set to containers: \\[1, 2, 3, 4, 5\\], where the number of items defined in the containers array will be how many instances of the job will start up.\n\nFor instance, `containers: [1, 2, 3, 4, 5]` will provision five worker instances to run in parallel. For our purposes, the array's values are arbitrary and aren't used in the steps.\n\n### Specifying Browsers in Parallel Builds\n\nWhen GitHub deploys new runner image versions containing updated browser versions, and the deployment is still in progress, the workflow \"Set up job\" phase randomly uses either an old or a new runner image version. Your test run might fail if Cypress Cloud detects differences in the browser versions between parallel jobs.\n\nTo work around this issue, and if you specify a browser other than the default Electron browser in parallel mode, we recommend using a [cypress/browsers](#Testing-with-Cypress-Docker-Images) Docker image which then uses one consistent browser version. This shields the workflow from browser version changes due to possible incomplete GitHub runner image deployments.\n\nAs mentioned in [Testing with Cypress Docker Images](#Testing-with-Cypress-Docker-Images), this option is only available with GitHub Actions Linux runners.\n", "section": "app", "anchors": [ "parallelization" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 853 }, { "id": "app/continuous-integration/github-actions#install-job", "doc_id": "app/continuous-integration/github-actions", "heading": "Install Job", "heading_level": 3, "content_markdown": "### Install Job\n\nThe separation of installation from test running is necessary when running parallel jobs. It allows for the reuse of various build steps aided by caching.\n\nFirst, we'll define the `install` step that will be used by the worker jobs defined in the matrix strategy.\n\nFor the `steps`, notice that we pass `runTests: false` to the Cypress GitHub Action to instruct it only to install and cache Cypress and npm dependencies _without running the tests_.\n\nThe [upload-artifact](https://github.com/marketplace/actions/upload-a-build-artifact) action will save the state of the `build` directory for the worker jobs.\n\n```\nname: Cypress Testson: pushjobs: install: runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress install uses: cypress-io/github-action@v7 with: # Disable running of tests within install job runTests: false build: npm run build - name: Save build folder uses: actions/upload-artifact@v6 with: name: build if-no-files-found: error path: dist\n```\n", "section": "app", "anchors": [ "install-job" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 189 }, { "id": "app/continuous-integration/github-actions#worker-jobs", "doc_id": "app/continuous-integration/github-actions", "heading": "Worker Jobs", "heading_level": 3, "content_markdown": "### Worker Jobs\n\nNext, we define the worker job named \"cypress-run\" that will run Cypress tests as part of a parallelized matrix strategy.\n\nThe `download-artifact` action will retrieve the **dist** directory saved in the install job.\n\n```\nname: Cypress Testson: pushjobs: install: # ... omitted install job from above cypress-run: runs-on: ubuntu-24.04 needs: install strategy: # don't fail the entire matrix on failure fail-fast: false matrix: # run copies of the current job in parallel containers: [1, 2, 3, 4, 5] steps: - name: Checkout uses: actions/checkout@v6 - name: Download the build folder uses: actions/download-artifact@v7 with: name: build - name: Cypress run uses: cypress-io/github-action@v7 with: record: true parallel: true group: 'UI-Chrome' start: npm start\n```\n\n**Ensure Correct Container**\n\nIf a Docker container was used in the install job, the same Docker container must also be used in the worker jobs.\n\n#### Setting up Parallelization\n\nTo set up multiple containers to run in parallel, the matrix option of the strategy configuration can be set to containers: \\[1, 2, 3, 4, 5\\], where the number of items defined in the containers array will be how many instances of the job will start up.\n\nFor instance, `containers: [1, 2, 3, 4, 5]` will provision five worker instances to run in parallel. For our purposes, the array's values are arbitrary and aren't used in the steps.\n", "section": "app", "anchors": [ "worker-jobs" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 296 }, { "id": "app/continuous-integration/github-actions#setting-up-parallelization", "doc_id": "app/continuous-integration/github-actions", "heading": "Setting up Parallelization", "heading_level": 4, "content_markdown": "#### Setting up Parallelization\n\nTo set up multiple containers to run in parallel, the matrix option of the strategy configuration can be set to containers: \\[1, 2, 3, 4, 5\\], where the number of items defined in the containers array will be how many instances of the job will start up.\n\nFor instance, `containers: [1, 2, 3, 4, 5]` will provision five worker instances to run in parallel. For our purposes, the array's values are arbitrary and aren't used in the steps.\n", "section": "app", "anchors": [ "setting-up-parallelization" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 109 }, { "id": "app/continuous-integration/github-actions#specifying-browsers-in-parallel-builds", "doc_id": "app/continuous-integration/github-actions", "heading": "Specifying Browsers in Parallel Builds", "heading_level": 3, "content_markdown": "### Specifying Browsers in Parallel Builds\n\nWhen GitHub deploys new runner image versions containing updated browser versions, and the deployment is still in progress, the workflow \"Set up job\" phase randomly uses either an old or a new runner image version. Your test run might fail if Cypress Cloud detects differences in the browser versions between parallel jobs.\n\nTo work around this issue, and if you specify a browser other than the default Electron browser in parallel mode, we recommend using a [cypress/browsers](#Testing-with-Cypress-Docker-Images) Docker image which then uses one consistent browser version. This shields the workflow from browser version changes due to possible incomplete GitHub runner image deployments.\n\nAs mentioned in [Testing with Cypress Docker Images](#Testing-with-Cypress-Docker-Images), this option is only available with GitHub Actions Linux runners.\n", "section": "app", "anchors": [ "specifying-browsers-in-parallel-builds" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 168 }, { "id": "app/continuous-integration/github-actions#using-cypress-cloud-with-github-actions", "doc_id": "app/continuous-integration/github-actions", "heading": "Using Cypress Cloud with GitHub Actions", "heading_level": 2, "content_markdown": "## Using Cypress Cloud with GitHub Actions\n\nIn the GitHub Actions configuration, we have defined in the previous section, we are leveraging three useful features of [Cypress Cloud](/llm/markdown/cloud/get-started/introduction.md):\n\n1. [Recording test results with the `record: true` option](/llm/markdown/cloud/get-started/setup.md) to [Cypress Cloud](https://on.cypress.io/cloud):\n \n * In-depth and shareable [test reports](/llm/markdown/cloud/features/recorded-runs.md#Latest-Runs).\n * Visibility into test failures via quick access to [Test Replay](/llm/markdown/cloud/features/test-replay.md), error messages, stack traces, screenshots, videos, and contextual details.\n * [Integrating testing with the pull-request (PR) process](/llm/markdown/cloud/integrations/github.md) via [commit status check guards](/llm/markdown/cloud/integrations/github.md#Status-checks) and convenient [test report comments](/llm/markdown/cloud/integrations/github.md#Pull-request-comments).\n * [Detecting flaky tests](/llm/markdown/cloud/features/flaky-test-management.md) and surfacing them via [Slack alerts](/llm/markdown/cloud/features/flaky-test-management.md#Slack) or [GitHub PR status checks](/llm/markdown/cloud/features/flaky-test-management.md#GitHub).\n2. [Parallelizing test runs](/llm/markdown/cloud/features/smart-orchestration/parallelization.md) and optimizing their execution via [intelligent load-balancing](/llm/markdown/cloud/features/smart-orchestration/load-balancing.md#Balance-strategy) of test specs across CI machines with the `parallel: true` option.\n \n3. Organizing and consolidating multiple `cypress run` calls by labeled groups into a single report within [Cypress Cloud](https://on.cypress.io/cloud). In the example above, we use the `group: \"UI-Chrome\"` option to organize all UI tests for the Chrome browser into a group labeled \"UI - Chrome\" in the [Cypress Cloud](https://on.cypress.io/cloud) report.\n", "section": "app", "anchors": [ "using-cypress-cloud-with-github-actions" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 227 }, { "id": "app/continuous-integration/github-actions#cypress-real-world-example-with-github-actions", "doc_id": "app/continuous-integration/github-actions", "heading": "Cypress Real World Example with GitHub Actions", "heading_level": 2, "content_markdown": "## Cypress Real World Example with GitHub Actions\n\nA complete CI workflow against multiple browsers, viewports, and operating systems is available in the **Cypress Real World App**.\n\nClone the [Real World App (RWA)](https://github.com/cypress-io/cypress-realworld-app) and refer to the [.github/workflows/main.yml](https://github.com/cypress-io/cypress-realworld-app/blob/develop/.github/workflows/main.yml) file.\n\nTo see additional how-to examples, you can also refer to our [Cypress GitHub Action repo](https://github.com/cypress-io/github-action).\n", "section": "app", "anchors": [ "cypress-real-world-example-with-github-actions" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 72 }, { "id": "app/continuous-integration/github-actions#common-problems-and-solutions", "doc_id": "app/continuous-integration/github-actions", "heading": "Common Problems and Solutions", "heading_level": 2, "content_markdown": "## Common Problems and Solutions\n\n### Re-run jobs passing with empty tests\n\nWe recommend passing the `GITHUB_TOKEN` secret (created by the GH Action automatically) as a system environment variable in CI/CD. This will allow the accurate identification of each build to avoid confusion when re-running a build.\n\n```\nname: Cypress testson: pushjobs: cypress-run: name: Cypress run runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress run uses: cypress-io/github-action@v7 with: record: true env: # pass GitHub token to detect new build vs re-run build GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}\n```\n\n### Pull requests commit message is `merge SHA into SHA`\n\nYou can overwrite the commit message sent to Cypress Cloud by setting a system environment variable in CI/CD. See [Issue #124](https://github.com/cypress-io/github-action/issues/124) for more details.\n\n```\nname: Cypress testson: pushjobs: cypress-run: name: Cypress run runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress run uses: cypress-io/github-action@v7 with: record: true env: # overwrite commit message sent to Cypress Cloud COMMIT_INFO_MESSAGE: ${{github.event.pull_request.title}} # re-enable PR comment bot COMMIT_INFO_SHA: ${{github.event.pull_request.head.sha}}\n```\n\nWe also recommend adding `COMMIT_INFO_SHA` to re-enable [Cypress bot PR comments](/llm/markdown/cloud/integrations/github.md#Pull-request-comments). See [this comment](https://github.com/cypress-io/github-action/issues/124#issuecomment-716584972) for more details.\n", "section": "app", "anchors": [ "common-problems-and-solutions" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 245 }, { "id": "app/continuous-integration/github-actions#re-run-jobs-passing-with-empty-tests", "doc_id": "app/continuous-integration/github-actions", "heading": "Re-run jobs passing with empty tests", "heading_level": 3, "content_markdown": "### Re-run jobs passing with empty tests\n\nWe recommend passing the `GITHUB_TOKEN` secret (created by the GH Action automatically) as a system environment variable in CI/CD. This will allow the accurate identification of each build to avoid confusion when re-running a build.\n\n```\nname: Cypress testson: pushjobs: cypress-run: name: Cypress run runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress run uses: cypress-io/github-action@v7 with: record: true env: # pass GitHub token to detect new build vs re-run build GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}\n```\n", "section": "app", "anchors": [ "re-run-jobs-passing-with-empty-tests" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 111 }, { "id": "app/continuous-integration/github-actions#pull-requests-commit-message-is-merge-sha-into-sha", "doc_id": "app/continuous-integration/github-actions", "heading": "Pull requests commit message is merge SHA into SHA", "heading_level": 3, "content_markdown": "### Pull requests commit message is `merge SHA into SHA`\n\nYou can overwrite the commit message sent to Cypress Cloud by setting a system environment variable in CI/CD. See [Issue #124](https://github.com/cypress-io/github-action/issues/124) for more details.\n\n```\nname: Cypress testson: pushjobs: cypress-run: name: Cypress run runs-on: ubuntu-24.04 steps: - name: Checkout uses: actions/checkout@v6 - name: Cypress run uses: cypress-io/github-action@v7 with: record: true env: # overwrite commit message sent to Cypress Cloud COMMIT_INFO_MESSAGE: ${{github.event.pull_request.title}} # re-enable PR comment bot COMMIT_INFO_SHA: ${{github.event.pull_request.head.sha}}\n```\n\nWe also recommend adding `COMMIT_INFO_SHA` to re-enable [Cypress bot PR comments](/llm/markdown/cloud/integrations/github.md#Pull-request-comments). See [this comment](https://github.com/cypress-io/github-action/issues/124#issuecomment-716584972) for more details.\n", "section": "app", "anchors": [ "pull-requests-commit-message-is-merge-sha-into-sha" ], "path": "/llm/json/chunked/app/continuous-integration/github-actions.json", "token_estimate": 128 } ] }