Please keep the title short, but expressive enough to signal what the reviewer can expect.
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue here in this description (not in the title of the PR). Be sure to provide detail on the "Why" of the change; this will help reviewers not familiar with the codebase to provide better reviews.
Before creating a PR, run through this checklist and mark each as complete.
- I have written my commit messages in the Conventional Commits format.
- I have read the CONTRIBUTING doc
- I have added tests (when possible) that prove my fix is effective or that my feature works
- I have checked that all unit tests pass after adding my changes
- I have updated necessary documentation
- I have rebased my branch onto main
- I will ensure my PR is targeting the master branch and pulling from my branch from my own fork