Type of change:
- Bug fix
- New feature
- Code refactor
- Breaking change
- Documentation update
- Other (please describe)
- Description of the feature What it does, why was it created, how does it work and so on...
- Links to screenshots, design docs, user docs, etc.
- Links to Jira/Fogbugz cases
- Halo effect What areas do you know/expect this feature to affect? Do you have any worries about possible breaking points? Write them down here.
- Performance Impact Could this PR affect performance? If so, what has been done to measure time taken per frame, memory used, etc.?
- Package requirements What Unity Editor version is required/supported? Any other dependancy packages needed?
- Have you added a backport label? (if needed)
- Have you updated the Changelog? Each package has a
CHANGELOG.mdfile - Have you added or updated the Documentation to your PR? When you add a new feature, change a property name, or change the behaviour of a feature, it's best practice to include related documentation changes in the same PR
- Existing or new automation tests - what automation was added, changed Put any relevant Yamato links here
- Detailed description of what testing was done, what projects were run Tell the reviewers what did you already test, so that they may have a better understanding when reviewing/testing this PR themselves
- What environment did you test on? Your Operating System, Platforms you ran on, Graphics APIs and any other relevant info you can think of
- Projects Any existing projects ready for testing should be noted here
- Testing checklist
- Built and run editor Locally or Katana
- Built a player Android/iOS (if applicable)
- Run on device Android/iOS (if applicable)
- If new feature has UI, does it match Unity style? (Unity HIG?)
- Tested Undo/Redo + Prefab overrides + Alignment in Preset
- All items have tooltips?
Changeset to use, if extra changesets on top. Any other notes to pass along
Notes for the reviewers you have assigned