All committers have signed the CLA.

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

@tom9744

I would class your PR as a feature not a fix, since it extends the documented functionality, so the commit message would need to start with feat:, for example: feat: apply no-pause rule recursively

You would also need to sign the SLA before the Cypress.io team could consider your PR.

@MikeMcC399 Thank you for your guidance. I was on the fence about which prefix to choose.

@tom9744

The documentation has been reworked since you submitted this PR. Could you rebase your PR? Sorry for the inconvenience!

I rebased my PR and resolved all conflicts!

@tom9744

Many thanks for your contribution! All looks good!

Tested against
https://github.com/cypress-io/cypress-example-kitchensink
using

npm install https://github.com/tom9744/eslint-plugin-cypress#user/tom9744/recursive-no-pause

and additional test-spec cypress/e2e/pause.cy.js

/// <reference types="cypress" />

context('eslinting', () => {
  it('pausing', () => {
    cy.pause()
    cy.visit('https://example.cypress.io').pause()
  })
})

Add "cypress/no-pause": "error" to .eslintrc rules.
(The rule no-pause is not in the set of recommended rules.)

(1) Note: rule cypress/no-pause not yet available in this version
(2) Only cy.pause() detected
(3) All uses of .pause() detected

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀