PowerShell/.github/PULL_REQUEST_TEMPLATE.md

<!-- Anything that looks like this is a comment and can't be seen after the Pull Request is created. -->

# PR Summary

<!-- Summarize your PR between here and the checklist. -->

## PR Context

<!-- Provide a little reasoning as to why this Pull Request helps and why you have opened it. -->

## PR Checklist

- [ ] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
    - Use the present tense and imperative mood when describing your changes
- [ ] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [ ] [Change is not breaking](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)
- [ ] [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)
- [ ] 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).
    - 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.
- **User-facing changes**
    - [ ] Not Applicable
    - **OR**
    - [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
        - [ ] Issue filed: <!-- Number/link of that issue here -->
- **Testing - New and feature**
    - [ ] N/A or can only be tested interactively
    - **OR**
    - [ ] [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)
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			`<!-- Anything that looks like this is a comment and can't be seen after the Pull Request is created. -->`
Update the pull request template (#8624) Some cleanup/enhancements to make it easier to understand. 2019-01-11 20:30:28 +01:00
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			`# PR Summary`
Fix a typo and a Markdonw linting error in the Pull Request Template (#5807) 2018-01-08 21:14:48 +01:00
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			`<!-- Summarize your PR between here and the checklist. -->`
Update the pull request template (#8624) Some cleanup/enhancements to make it easier to understand. 2019-01-11 20:30:28 +01:00
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			`## PR Context`
Update the pull request template (#8624) Some cleanup/enhancements to make it easier to understand. 2019-01-11 20:30:28 +01:00
			`<!-- Provide a little reasoning as to why this Pull Request helps and why you have opened it. -->`
contribution guidelines: Remove requirement for updating changelog update in pr (#5644) 2017-12-07 02:22:46 +01:00
contribution guidelines: change to say updating changelog is required (#5586) - Update contribution guidelines to make updating the changelog required - add a checklist to PR template Comment by @SteveL-MSFT : > Everyone should understand that we are always open to feedback and nothing is set in stone. Based on a team discussion, one of the biggest costs for a release is creating the ChangeLog hence updating this document to push it to the contributor most aware of why the changes are being made and ideally how it's useful to end users. 2017-12-04 23:32:02 +01:00			`## PR Checklist`
Define roles and their responsibilities in a PR (#3168) 2017-02-23 22:13:06 +01:00
contribution guidelines: change to say updating changelog is required (#5586) - Update contribution guidelines to make updating the changelog required - add a checklist to PR template Comment by @SteveL-MSFT : > Everyone should understand that we are always open to feedback and nothing is set in stone. Based on a team discussion, one of the biggest costs for a release is creating the ChangeLog hence updating this document to push it to the contributor most aware of why the changes are being made and ideally how it's useful to end users. 2017-12-04 23:32:02 +01:00			`- [ ] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)`
Make it clearer how and what to mark as "not applicable" in PR template (#6209) 2018-02-24 00:25:44 +01:00			`- Use the present tense and imperative mood when describing your changes`
contribution guidelines: change to say updating changelog is required (#5586) - Update contribution guidelines to make updating the changelog required - add a checklist to PR template Comment by @SteveL-MSFT : > Everyone should understand that we are always open to feedback and nothing is set in stone. Based on a team discussion, one of the biggest costs for a release is creating the ChangeLog hence updating this document to push it to the contributor most aware of why the changes are being made and ideally how it's useful to end users. 2017-12-04 23:32:02 +01:00			`- [ ] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)`
			`- [ ] [Change is not breaking](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)`
Make it clearer how and what to mark as "not applicable" in PR template (#6209) 2018-02-24 00:25:44 +01:00			- [ ] [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)
contribution guidelines: Add work in progress guidance (#5655) Add guidance for submitting PR which are not ready to merge, or work in progress (WIP) 2017-12-08 21:14:00 +01:00			`- [ ] 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).`
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			- 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.
Make it clearer how and what to mark as "not applicable" in PR template (#6209) 2018-02-24 00:25:44 +01:00			`- User-facing changes`
			`- [ ] Not Applicable`
Fix Markdown lint issues (#8929) #8896 Broke the static analysis CI. Fixing so CI passes 2019-02-20 22:24:26 +01:00			`- OR`
Update the pull request template (#8624) Some cleanup/enhancements to make it easier to understand. 2019-01-11 20:30:28 +01:00			`- [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)`
			`- [ ] Issue filed: <!-- Number/link of that issue here -->`
Make it clearer how and what to mark as "not applicable" in PR template (#6209) 2018-02-24 00:25:44 +01:00			`- Testing - New and feature`
Update the pull request template (#8624) Some cleanup/enhancements to make it easier to understand. 2019-01-11 20:30:28 +01:00			`- [ ] N/A or can only be tested interactively`
Make it clearer how and what to mark as "not applicable" in PR template (#6209) 2018-02-24 00:25:44 +01:00			`- OR`
			`- [ ] [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)`