Skip to content

Commit bbaa69e

Browse files
author
choco-sync
committed
(maint) synced local '.github/PULL_REQUEST_TEMPLATE.md' with remote '.github/PULL_REQUEST_TEMPLATE.md'
1 parent 3e3898c commit bbaa69e

File tree

1 file changed

+60
-24
lines changed

1 file changed

+60
-24
lines changed

.github/PULL_REQUEST_TEMPLATE.md

+60-24
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,67 @@
1-
<!-- DO NOT MODIFY OR DELETE THIS TEMPLATE. IT IS USED IN AUTOMATION. -->
2-
## Bug
1+
<!--
2+
BEFORE YOU CREATE A PULL REQUEST:
33
4-
<!-- Search https://github.com/NuGet/Home/issues, and create one if you can't find a suitable issue. -->
5-
<!-- Paste the full link, like https://github.com/nuget/home/issues/1000. GitHub will render is neatly. -->
6-
Fixes:
4+
Ensure you have read over [CONTRIBUTING.md](./CONTRIBUTING.md). We provide VERY defined guidance (as such, we strongly adhere to it).
75
8-
Regression? Last working version:
6+
A summary of our expectations:
7+
- You are not submitting a pull request from your MASTER / MAIN branch.
8+
- You are able to sign the Contributor License Agreement (CLA).
9+
- YOUR GIT COMMIT MESSAGE FORMAT IS EXTREMELY IMPORTANT. We have a very defined expectation for this format and are sticklers about it. Really, READ the entire Contributing document. It will save you and us pain.
10+
- Do not reformat code, it makes it hard to see what has changed. Leave the formatting to us.
911
10-
## Description
11-
<!-- Add details about the fix. Include any information that would help the maintainer review this change effective. -->
12+
THANKS! We appreciate you reading the entire Contributing document and not just scanning through it.
1213
13-
## PR Checklist
14+
Name your pull request appropriately: give it a sentence that reads well enough for anyone seeing this.
1415
15-
- [ ] PR has a meaningful title
16-
- [ ] PR has a linked issue.
17-
- [ ] Described changes
16+
if you were explaining it to somebody else. This helps others to understand the reasons for the pull request and for it to be searchable in future.
1817
19-
- **Tests**
20-
- [ ] Automated tests added
21-
- **OR**
22-
<!-- Describe why you haven't added automation. -->
23-
- [ ] Test exception
24-
- **OR**
25-
- [ ] N/A <!-- Infrastructure, documentation etc. -->
18+
Please do not remove any of the headings.
19+
If a heading is not applicable then enter N/A: Why it's not applicable
2620
27-
- **Documentation**
28-
<!-- Please link the PR/issue if appropriate -->
29-
- [ ] Documentation PR or issue filled
30-
- **OR**
31-
- [ ] N/A
21+
Make sure you have raised an issue for this pull request before continuing.
22+
23+
Please remove all comments before submitting.
24+
-->
25+
26+
## Description Of Changes
27+
<!-- Enter a description of the pull request changes -->
28+
29+
## Motivation and Context
30+
<!-- Why is this change necessary and under what context is it being done -->
31+
32+
## Testing
33+
<!-- How has this change been tested? If multiple different tests have been done please list them.
34+
1. Tested this way
35+
1. Tested that way
36+
-->
37+
### Operating Systems Testing
38+
<!-- If this is a code change, list the operating systems this has been tested on
39+
- Windows Server 2008R2
40+
- Windows 8.1
41+
...
42+
-->
43+
44+
## Change Types Made
45+
<!-- Tick the boxes for the type of changes that have been made -->
46+
47+
* [ ] Bug fix (non-breaking change).
48+
* [ ] Feature / Enhancement (non-breaking change).
49+
* [ ] Breaking change (fix or feature that could cause existing functionality to change).
50+
* [ ] Documentation changes.
51+
* [ ] PowerShell code changes.
52+
53+
## Change Checklist
54+
55+
* [ ] Requires a change to the documentation.
56+
* [ ] Documentation has been updated.
57+
* [ ] Tests to cover my changes, have been added.
58+
* [ ] All new and existing tests passed?
59+
* [ ] PowerShell code changes: PowerShell v2 compatibility checked?
60+
61+
## Related Issue
62+
<!-- Make sure you have raised an issue for this pull request before
63+
continuing. -->
64+
65+
Fixes #
66+
67+
<!-- PLEASE REMOVE ALL COMMENTS BEFORE SUBMITTING -->

0 commit comments

Comments
 (0)