Mike McCready
Mike McCready
I have resubmitted an enhancement request to GitHub in a different place. In the community board, which is where enhancement requests for the GitHub runners are supposed to go, there...
The GitHub runner team have written in https://github.com/actions/runner/issues/2812#issuecomment-1708710610 that there are no plans to make changes in this area in the short- or medium-term which would ensure that containers in...
@jebarjonet I suggest to close this issue now as all possible steps have now been addressed by `github-action`. The best advice to avoid the issue is to use a Docker...
@medmoe You are using an old version of the action which is not compatible with Cypress `10` and later versions: ``` - name: Run Cypress tests uses: cypress-io/github-action@v2 ``` Your...
Hi @alxndr I looked at your https://github.com/alxndr/almost-dead-net/blob/main/.github/workflows/main.yml and you are using `cypress-io/[email protected]` so although the issue here is solved, your workflow will soon fail. There is a note in the...
@huy-nguyen It looks like you ran into an issue which was not previously documented. If you use the `command` parameter it overrides many other functions. See [README > Custom test...
Closing, since this is a stale inactive issue and a probable cause has been identified.
This issue hasn't been addressed. It is not covered in the [README documentation](https://github.com/cypress-io/github-action#node-versions) and the workflow [.github/workflows/example-node-versions.yml](https://github.com/cypress-io/github-action/blob/master/.github/workflows/example-node-versions.yml) doesn't notice the problem even though the only version of Node.js used is...
@ricardo-dematos If you want to log your cucumber issue separately, we could take a look to see if there is some workaround which may be used. Edit: We would need...
@ricardo-dematos Using the github-action [command](https://github.com/cypress-io/github-action#custom-test-command) option, Cypress can be run using the Node.js version set up in the runner instead of `node16` specified by the JavaScript Action definition. Please note...