chore: prevent GitHub Actions recording examples running in fork

[MikeMcC399]

• closes GHA recording workflows fail in fork on push event #810

Issue

The set of example CI workflows includes three GitHub Actions workflows that record to Cypress Cloud using a projectId owned by Cypress.io with a secret Record Key.

These workflows fail if they are executed unchanged in a user fork of the parent repo. The fork has no access to the necessary Record Key.

Workflow file	Workflow name
.github/workflows/parallel.yml	Cypress parallel tests
.github/workflows/single.yml	Cypress single tests
.github/workflows/using-action.yml	Using Cypress GH Action

Change

• Prevent the above workflows running in a fork. Only run if: github.repository_owner == 'cypress-io'.

• The exception is the single-run job of .github/workflows/using-action.yml which does not record, and so does not fail if a matching Record Key is missing. This job is not blocked from running.

Verification

Attempt to manually run each of the above workflows in a fork, and confirm that they are skipped without error.

---

Note

Low Risk
CI-only guard conditions with no application, auth, or data-path changes; risk is limited to workflow skip behavior in forks versus the parent repo.

Overview
Forks of this repo were failing CI because example workflows record to Cypress Cloud using a Record Key secret that only exists on the parent cypress-io repository.

This PR adds if: github.repository_owner == 'cypress-io' to jobs that record to Cypress Cloud: the install job in parallel.yml, the test job in single.yml, and the parallel-runs and parallel-runs-across-platforms jobs in using-action.yml. Comments note that forks need their own project ID and Record Key to run those examples.

The single-run job in using-action.yml is intentionally unchanged (no if) because it does not record, so it can still run in forks. That workflow also gets clearer job names and documentation; a stale top-of-file comment about pinning cypress-io/github-action versions was removed.

^{Reviewed by Cursor Bugbot for commit c3732c2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.