Skip to content

Commit 91a6e3d

Browse files
authored
Merge pull request #330 from Unity-Technologies/chrispope-uploading-pull-request-template
Uploading pull-request-template
2 parents 2702f80 + ed59310 commit 91a6e3d

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
<!---
2+
Thank you for contributing to Unity.
3+
To help us process this pull request we recommend that you add the following information:
4+
- Summary and list of changes in the pull request,
5+
- Issue(s) related to the changes made such as GitHub or Jira,
6+
- Manual testing scenarios if available
7+
Fields marked with (*) are required. Please don't remove the template.
8+
-->
9+
### Description (*)
10+
<!---
11+
Please provide a description of the changes proposed in the pull request.
12+
Letting us know what has changed and why it needed changing will help us validate this pull request.
13+
-->
14+
### Related Pull Requests
15+
<!-- related pull request placeholder -->
16+
### Issue Number(s) (*)
17+
<!---
18+
Provide a list of fixed issues from Jira (GOMPS-ticketnumber) or GitHub (#issuenumber).
19+
This helps us understand the reasoning behind this change, what it fixes, feature being added, etc.
20+
-->
21+
Fixes issue(s):
22+
### Manual testing scenarios
23+
<!---
24+
Please provide a set of unambiguous steps to test the proposed code change.
25+
If an error is output to either the player or editor log file, please attach.
26+
Giving us manual testing scenarios will help with the processing and validation process.
27+
-->
28+
1. ...
29+
2. ...
30+
### Questions or comments
31+
<!---
32+
If relevant, here you can ask questions or provide comments on your pull request for the reviewer
33+
For example if you need assistance with writing tests or would like some feedback on one of your development ideas or for the reviewer to focus on a particular area of the code.
34+
-->
35+
### Contribution checklist
36+
- [ ] Pull request has a meaningful description of its purpose
37+
- [ ] All commits are accompanied by meaningful commit messages
38+
- [ ] All new or changed code is covered with unit/integration tests (if applicable)
39+
- [ ] All automated tests passed successfully (all builds are green)

0 commit comments

Comments
 (0)