Mike McCready

@fbiville - PR #785 is merged and you now have `Contributor` showing against your name 💪🏻 as recognition for your submission.

@far11ven > Was it fixed somehow in some newer versions? It seems to be working fine in `cypress-io/github-action@v5`. Check out job [7838187516](https://github.com/cypress-io/github-action/actions/runs/4463161679/jobs/7838187516) which shows:  This is a log of...

@far11ven You can also try this out for yourself if you have a fork of this repository. Follow the instructions in - [example-recording.yml](https://github.com/cypress-io/github-action/blob/master/.github/workflows/example-recording.yml) - [examples/recording](https://github.com/cypress-io/github-action/tree/master/examples/recording)

@far11ven Are you setting the `record` parameter of `cypress-io/github-action` to `true` or are you recording by hand? Could you expand the arrow in the log to the left of "Run...

@Erenndriel > What is NOT OBVIOUS in the docs (at least to me and 2 other devs trying to setup the workflow) is that the action by default executes cypress...

@far11ven If you are using `command:` , then the `record:` parameter is not used and there is no `dashboardUrl` saved. > At the end of the step log "Cypress tests"...

@Erenndriel > I don't think that it'd be the right direction to assume that --record is meant for Cypress when passed to command input. You are right. It would not...

- I have made a suggestion to update the README documentation in PR #846. - ~~Whilst the pull request is still in review mode you can read the suggestion under...

@jazanne Could you let us know if this is still an issue for you? We found one root cause, but I don't know if it covers your case.

@jazanne It's good to hear that we finally worked out what the problem is! Thanks for closing the loop! Would you like to close your issue now?