feat: add auto cancel after failures flag#772
Conversation
|
This is currently marked as a draft as there isn't a published cypress binary to test it with yet. |
Co-authored-by: Paul Jaffre <jaffrepaul@gmail.com>
|
You may have noticed that there is a new check which fails here. You'll need to execute npm run format
npm run buildand commit the change. Edit: Also to be safe, you should rebase on |
awesome thanks @MikeMcC399 |
|
I see it's still failing, so the full set of instructions would be: rebase on current master (It seems to be the |
There was a problem hiding this comment.
The new example Specify auto cancel after failures is missing from the table of contents Examples. It should be added.
Please review the order of examples, currently shown as:
How about modifying this and changing the order to:
- Record results on Cypress Cloud
- Specify auto cancel after failures
- Tag recordings
- Store test artifacts on GitHub
- Quiet output
in both the table of contents and the examples themselves. The "Quiet" example seems to be misplaced, which could be handled here or in a separate PR.
This branch is currently 36 commits behind master. I suggest to rebase it on master before it is merged (and to squash commits during merge).
Please set the status of the resolved review comments to "resolved".
|
Do you consider it necessary / desirable for PRs to be in sync with the base branch ( |
|
|
Is this PR going ahead? It seems like it should, since Cypress 12.6.0 was already released on Feb 15, 2023, but maybe I'm missing part of the big picture. |
|
🎉 This PR is included in version 5.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |

No description provided.