Mike McCready

> Would still love to see this changed/supported in the future. I'm guessing that this would need to be an enhancement to Cypress in order to expose / export the...

Closing, since a workaround was found.

@DjNaGuRo Can we assume that your issue is now resolved? Your original post didn't include your workflow, so it is difficult to evaluate what may have caused your issue. The...

@commonpike Is this just a documentation issue for you or do you have an example workflow using the current version of the action (`v5`) where it is causing you a...

Probably if there was a need to start a server a second time, then I would put it into a separate job rather than a step in the same job....

I haven't looked at this too closely, but I think in the original example I would have just deleted the second `start: npm start`, unless there is some special reason...

- I submitted PR https://github.com/cypress-io/github-action/pull/915 to modify the documentation.

@kgartland-rstudio > FYI, I came across this as well and found that if you're running Cypress within a Docker Container, the proper exit code may not be sent to GH...

@kgartland-rstudio Thanks very much for adding your environment / steps. That makes it a lot clearer!

This is a stale issue. GitHub runners include Google Chrome and [.github/workflows/example-chrome.yml](https://github.com/cypress-io/github-action/blob/master/.github/workflows/example-chrome.yml) demonstrates that Cypress finds the browser. https://github.com/cypress-io/cypress-docker-images also offers Cypress Docker images with Chrome pre-installed. For browsers installed...