Continuous merging of develop to keep master up to date
Linked Issues
Include any linked issues here by writing "Closes #No."
Description
Please include a summary of the change and which issue is fixed. Include the context and motivations behind your changes. If needed, add screenshots or videos.
How to test
Describe how the PR should be tested (ideally with an enumerated list)
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
Checklist:
[x] My PR is concise and addresses only one bug/feature (otherwise split PR into two)
[x] My PR has a concise and descriptive title
[x] My code follows the code style of this project.
[x] I have performed a self-review of my own code and PR and have added comments in the PR code to help the reviewer.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
TL;DR
Continuous merging of develop to keep master up to date
Linked Issues
Include any linked issues here by writing "Closes #No."
Description
Please include a summary of the change and which issue is fixed. Include the context and motivations behind your changes. If needed, add screenshots or videos.
How to test
Describe how the PR should be tested (ideally with an enumerated list)
Type of change
Checklist:
Additional Notes
Add any other notes or comments here.
How to make a good PR (Video)