Skip to content

Commit ee8879d

Browse files
authoredOct 23, 2023
linting and spellchecking the markdown files (#711)
1 parent d169f7b commit ee8879d

File tree

3 files changed

+89
-91
lines changed

3 files changed

+89
-91
lines changed
 

‎.github/ISSUE_TEMPLATE/bug_report.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -7,28 +7,28 @@ assignees: ''
77
---
88

99
**Logs and screenshots**
10-
Please provide debug logs by running Cypress from the terminal with `DEBUG=code-coverage` environment variable set, see the [Debugging](https://github.com/cypress-io/code-coverage#debugging) section of the README file.
10+
Please provide debug logs by running Cypress from the terminal with `DEBUG=code-coverage` environment variable set. See the [Debugging](https://github.com/cypress-io/code-coverage#debugging) section of the README file.
1111

1212
**Versions**
1313

14-
- What is this plugin's version? If this is NOT the latest [released version](https://github.com/cypress-io/code-coverage/releases) can you try the latest version, please?
15-
- If the plugin worked before in version X, but stopped after upgrading to version Y, please try the [released versions](https://github.com/cypress-io/code-coverage/releases) between X and Y to see where the breaking change was.
16-
- What is Cypress version?
14+
- What is this plugin's version? If this is NOT the latest [released version](https://github.com/cypress-io/code-coverage/releases), can you try the latest version, please?
15+
- If the plugin worked before in version X but stopped after upgrading to version Y, please try the [released versions](https://github.com/cypress-io/code-coverage/releases) between X and Y to see where the breaking change was.
16+
- What is the Cypress version?
1717
- What is your operating system?
1818
- What is the shell?
1919
- What is the Node version?
2020
- What is the NPM version?
21-
- How do you instrument your application? Cypress [does not instrument web application code](https://github.com/cypress-io/code-coverage#instrument-your-application), so you need to do it yourself.
22-
- When running tests, if you open the web application in regular browser, and open DevTools, do you see `window.__coverage__` object? Can you paste a screenshot?
23-
- Is there `.nyc_output` folder? Is there `.nyc_output/out.json` file. Is it empty? Can you paste at least part of it so we can see the keys and file paths?
24-
- Do you have any custom NYC settings in `package.json` (`nyc` object) or in other [NYC config files](https://github.com/istanbuljs/nyc#configuration-files)
21+
- How do you instrument your application? Cypress [does not instrument web application code](https://github.com/cypress-io/code-coverage#instrument-your-application), so you must do it yourself.
22+
- When running tests, if you open the web application in a regular browser and open DevTools, do you see `window.__coverage__` object? Can you paste a screenshot?
23+
- Is there a `.nyc_output` folder? Is there a `.nyc_output/out.json` file? Is it empty? Can you paste at least part of it so we can see the keys and file paths?
24+
- Do you have any custom NYC settings in `package.json` (`nyc` object) or in other [NYC config files](https://github.com/istanbuljs/nyc#configuration-files)?
2525
- Do you run Cypress tests in a Docker container?
2626

2727
**Describe the bug**
2828
A clear and concise description of what the bug is.
2929

3030
**Link to the repo**
31-
Bugs with a reproducible example, like an open source repo showing the bug, are the most likely to be resolved.
31+
Bugs with a reproducible example, like an open-source repo showing the bug, are the most likely to be resolved.
3232

3333
**Example**
3434
See [#217](https://github.com/cypress-io/code-coverage/issues/217) that is an excellent bug report example

0 commit comments

Comments
 (0)