|
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 (*) |
| 1 | +### Description |
10 | 2 | <!---
|
11 | 3 | 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. |
| 4 | + Make sure your commit messages have meaningful information. |
| 5 | + To help us link commits and PRs to JIRA work items, please include the JIRA ticket ID in the PR title or at least of your commit messages. |
13 | 6 | -->
|
14 |
| -### Related Pull Requests |
15 |
| -<!-- related pull request placeholder --> |
16 |
| -### Issue Number(s) (*) |
| 7 | + |
| 8 | +### Issue Number(s) |
17 | 9 | <!---
|
18 | 10 | Provide a list of fixed issues from Jira (GOMPS-ticketnumber) or GitHub (#issuenumber).
|
19 | 11 | This helps us understand the reasoning behind this change, what it fixes, feature being added, etc.
|
20 | 12 | -->
|
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 |
| ---> |
| 13 | + |
35 | 14 | ### Contribution checklist
|
36 | 15 | - [ ] Pull request has a meaningful description of its purpose
|
37 | 16 | - [ ] 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) |
| 17 | + - [ ] JIRA ticket ID is in the PR title or at least one commit message |
| 18 | + - [ ] Include the ticket ID number within the body message of the PR to create a hyperlink |
0 commit comments