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 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:
- The workflow is now triggered only on the repository of the forked repository.
- 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?
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 to use the
pushevent to trigger runs of Cypress. This is problematic for a couple of reasons when opening a PR from a fork:What is the recommend way to resolve this?