|
11 | 11 | ## PR Checklist |
12 | 12 |
|
13 | 13 | - [ ] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) |
14 | | - - Use the present tense and imperative mood when describing your changes |
| 14 | + - Use the present tense and imperative mood when describing your changes |
15 | 15 | - [ ] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) |
16 | 16 | - [ ] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) |
17 | 17 | - [ ] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress). |
18 | | - - If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready. |
| 18 | + - If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready. |
19 | 19 | - **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)** |
20 | | - - [ ] None |
21 | | - - **OR** |
22 | | - - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/7.3/Microsoft.PowerShell.Core/About/about_Experimental_Features.md) |
23 | | - - [ ] Experimental feature name(s): <!-- Experimental feature name(s) here --> |
| 20 | + - [ ] None |
| 21 | + - **OR** |
| 22 | + - [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/main/reference/7.5/Microsoft.PowerShell.Core/About/about_Experimental_Features.md) |
| 23 | + - [ ] Experimental feature name(s): <!-- Experimental feature name(s) here --> |
24 | 24 | - **User-facing changes** |
25 | | - - [ ] Not Applicable |
26 | | - - **OR** |
27 | | - - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) |
| 25 | + - [ ] Not Applicable |
| 26 | + - **OR** |
| 27 | + - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission) |
28 | 28 | - [ ] Issue filed: <!-- Number/link of that issue here --> |
29 | 29 | - **Testing - New and feature** |
30 | | - - [ ] N/A or can only be tested interactively |
31 | | - - **OR** |
32 | | - - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting) |
| 30 | + - [ ] N/A or can only be tested interactively |
| 31 | + - **OR** |
| 32 | + - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting) |
33 | 33 | - **Tooling** |
34 | | - - [ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted. |
35 | | - - **OR** |
36 | | - - [ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include: |
37 | | - - [ ] Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode |
| 34 | + - [ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted. |
| 35 | + - **OR** |
| 36 | + - [ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include: |
| 37 | + - [ ] Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode |
38 | 38 | (which runs in a different PS Host). |
39 | | - - [ ] Issue filed: <!-- Number/link of that issue here --> |
40 | | - - [ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features. |
41 | | - - [ ] Issue filed: <!-- Number/link of that issue here --> |
42 | | - - [ ] Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions). |
43 | | - - [ ] Issue filed: <!-- Number/link of that issue here --> |
44 | | - - [ ] Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors). |
45 | | - - [ ] Issue filed: <!-- Number/link of that issue here --> |
| 39 | + - [ ] Issue filed: <!-- Number/link of that issue here --> |
| 40 | + - [ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features. |
| 41 | + - [ ] Issue filed: <!-- Number/link of that issue here --> |
| 42 | + - [ ] Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions). |
| 43 | + - [ ] Issue filed: <!-- Number/link of that issue here --> |
| 44 | + - [ ] Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors). |
| 45 | + - [ ] Issue filed: <!-- Number/link of that issue here --> |
0 commit comments