[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
π Background
Provide a brief explanation of why this pull request is needed. Include the problem you are solving or the functionality you are adding. Reference any related issues.
Issue Link: ENG-2630
Context Link (if applicable):
π Changes
Enumerate the changes made in this pull request, detailing what has been modified, added, or removed. Include technical details and implications if necessary.
Impact:
Explain the broader impact of these changes.
How it improves performance, fixes bugs, adds functionality, etc.
πΌ Screenshot / πΉ Video
Include screenshots or a video demonstrating the changes. This is especially helpful for UI changes.
β Review checklist
Please ensure the following are true before merging:
[x] Code Style is consistent with the project guidelines.
[x] Code is readable and well-commented.
[x] No unnecessary or debugging code has been added.
[x] Security considerations have been taken into account.
[x] The change has been manually tested and works as expected.
[x] Breaking changes and their impacts have been considered and documented.
[x] Code does not introduce new technical debt or issues.
π PR Type
What kind of change does this PR introduce?
π Background
Provide a brief explanation of why this pull request is needed. Include the problem you are solving or the functionality you are adding. Reference any related issues.
Issue Link: ENG-2630 Context Link (if applicable):
π Changes
Enumerate the changes made in this pull request, detailing what has been modified, added, or removed. Include technical details and implications if necessary.
Impact:
πΌ Screenshot / πΉ Video
Include screenshots or a video demonstrating the changes. This is especially helpful for UI changes.
β Review checklist
Please ensure the following are true before merging: