Cypress dashboard isn't recording test runs about streamlit HOT 1 CLOSED

@tvst Did you see the email I forwarded you with the conversation with Cypress Support?

Many CI providers (Circle being one of them) do not pass private environment variables along to forked PRs for security reasons. You can read more about their decision here: https://circleci.com/docs/2.0/oss/#pass-secrets-to-builds-from-forked-pull-requests

We face this problem in our own project.We have many open source projects running Cypress tests with contributions from forked PRs. You can see some of our setup in our circle.yml file. Basically, we don't record the test runs if the env var is not present and fallback to just running the tests without the --record flag.

You should also understand a bit about the consequences of exposing the Cypress record key, so you can assess the risks of exposing it.

Anyone that has access to both the projectId and the record key of your project will be able to record runs to your organization in the Dashboard. Typically, you would not want anyone running tests because this could drive up the number of tests you've run. Since Cypress bills based on the number of tests - this would mean they could use up all allotted tests and there would be consequences to that.

And

If the build is triggered from a forked pull request, the environment variables will be inaccessible. It doesn't matter where the pull request originally was forked from - it's all about what triggers the build.

from streamlit.