44 lines
906 B
Markdown
44 lines
906 B
Markdown
# Bug Fix PR Template
|
|
|
|
## Summary
|
|
|
|
Provide a concise description of the bug and the fix.
|
|
|
|
## Issue Link
|
|
|
|
Link to the issue being addressed.
|
|
|
|
## Root Cause Analysis
|
|
|
|
Detail the root cause of the bug and how it was identified.
|
|
|
|
## Changes
|
|
|
|
Outline the changes made to fix the bug.
|
|
|
|
## Impact
|
|
|
|
Describe any implications this fix may have on other parts of the application.
|
|
|
|
## Testing Strategy
|
|
|
|
Explain how the fix has been tested to ensure the bug is resolved without introducing new issues.
|
|
|
|
## Regression Risk
|
|
|
|
Assess the risk of regression caused by this fix and steps taken to mitigate it.
|
|
|
|
## Checklist
|
|
|
|
- [ ] The fix has been locally tested
|
|
|
|
- [ ] The fix meets the codestyle requirements
|
|
|
|
- [ ] New unit tests have been added to prevent future regressions
|
|
|
|
- [ ] The documentation has been updated if necessary
|
|
|
|
## Additional Notes
|
|
|
|
Any further information needed to understand the fix or its impact.
|