Mike McCready

@CharlieGreenman > Docs specifically for nrwl Nx might be helpful You can leave this issue open for a response from the Cypress.io team. I'm just a community member here, so...

@jonkoops - I have a PR proposed in https://github.com/cypress-io/github-action/pull/751 to solve the issue that you describe. Whilst the PR is still open and not merged you can take a look...

@gk-bbai > Is there a recommended way for us to utilize `nx affected` _with_ the [Cypress GitHub Action](https://github.com/cypress-io/github-action)? This repository does not provide any framework-specific documentation. You should check first...

@jonkoops Was this helpful to you?

@jonkoops We didn't hear any more from you, so hopefully you have managed to resolve your issue. The improved example of recording in a fork has now been merged, so...

@jonkoops > After reading the linked documentation I don't understand how this should resolve this issue. From what I can tell it specifies that forks should have their own secrets?...

@jonkoops > 1. These are all public forks. > 2. My problem is that putting it in a secret makes said secret unavailable to forks (this is just how Github...

@jonkoops Have you considered blocking recording into Cypress Cloud for external contributors working in forks? Would that work for you?

@jonkoops > I have, but our entire team works from forks so that would essentially make the Cypress Cloud useless for our current workflow. Thanks for continuing to explain your...

@jonkoops I would encourage you to file a new [feature request](https://github.com/cypress-io/cypress/issues/new?assignees=&labels=&projects=&template=4-feature.yml) for Cypress so that this need is funnelled in the right direction.