cypress-io / cypress-io/github-action

Not possible to run Cypress tests without exposing record key

Open
#796 17 comments 0 reactions 1 assignee Claimed by @rockhold View on GitHub
Cypress Cloud triaged type: feature
Dominant language
JavaScript
Stars
1.5k
Forks
353
Avg merge
1d 22h
Merged PRs (30d)
27

Description

Hi. We're using the Cypress Dashboard for our product and we're having a hard time running the tests without exposing the record key. Currently we have hard-coded it in our workflow, which makes it publicly available (less than ideal for obvious reasons).

We're following the recommendation as outlined in [the documentation](https://github.com/cypress-io/github-action#record-test-results-on-cypress-cloud) to use the `push` event to trigger runs of Cypress. This is problematic for a couple of reasons when opening a **PR** from a fork:

1. The workflow is now triggered only on the repository of the forked repository.
2. Because the workflow on the forked repository does not have access to this secret all jobs fail.

What is the recommend way to resolve this?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.