Summary... What does this pull request accomplish?
If applicable, what is the non-technical or business context around this merge request? e.g., what would a reviewer need to know in order to determine if the behavior is correct?
Let the reviewer know what to look for in your code changes and provide any context they may need in order to understand your code design choices.
If applicable (usually for bugs), let the reviewer know how to reproduce what you are fixing.
Let the reviewer know how to manually verify that your solution works
- Ensure code complies with the style guide
- Devise edge cases to test the bug fix or feature being merged
- Make sure the code is clean and understandable
- Ensure code is not overly inefficient
- There are no conflicting migration leaf nodes
- Ensure code complies with the style guide
- Devise edge cases to test the bug fix or feature being merged
- Make sure the code is clean and understandable
- Ensure code is not overly inefficient
- There are no conflicting migration leaf nodes
- Ensure documentation is understandable and accurate, including:
- Code comments and doc strings
- Technical documentation