45 lines
1.4 KiB
Markdown
45 lines
1.4 KiB
Markdown
## Links
|
|
- [Ticket Link]
|
|
- [Design Link]
|
|
- [Images / Working Video Ref.]
|
|
|
|
## Describe changes in PR.
|
|
|
|
## PR Checklist
|
|
Please check if your PR fulfills the following requirements:
|
|
- [ ] Tests for the changes have been added (for bug fixes/features)
|
|
- [ ] Docs have been added/updated (for bug fixes/features)
|
|
|
|
## PR Type
|
|
What kind of change does this PR introduce?
|
|
|
|
<!-- Please check the one that applies to this PR using "x". -->
|
|
- [ ] Bugfix
|
|
- [ ] Feature
|
|
- [ ] Code style update (formatting, local variables)
|
|
- [ ] Refactoring (no. functional changes, no. API changes)
|
|
- [ ] Build related changes
|
|
- [ ] Documentation content changes
|
|
- [ ] Other... Please describe:
|
|
|
|
## What is the current behavior?
|
|
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
|
|
Issue Number: N/A
|
|
|
|
## What is the new behavior?
|
|
|
|
## Does this PR introduce a breaking change?
|
|
- [ ] Yes
|
|
- [ ] No
|
|
|
|
## Reviewer(s) Notes
|
|
> **Known Issues/Limitations**
|
|
> > If there are known limitations/issues with the changes can be mentioned here.
|
|
> > Note: These are optional points if the raiser found it good to have then can consider it
|
|
|
|
> **Dependencies**
|
|
> > In such cases we are dividing PR(s) into chunks then it would be good if we add parent / dependent PR so the reviewer would have more idea and also during merging it is known.
|
|
> > Note: These are optional points if the raiser found it good to have then can consider it
|
|
|
|
> **Additional notes for reviewer**
|