Describe the big picture of your changes here to communicate to the maintainers. If it fixes a bug or resolves a feature request, please provide a link to that issue.
What types of changes does your code introduce to dbldatagen?
Put an x in the boxes that apply
- 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)
- Change to tutorials, tests or examples
- Non code change (readme, images or other non-code assets)
- Documentation Update (if none of the other choices apply)
Put an x in the boxes that apply. You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
- Lint and unit tests pass locally with my changes
- I have added tests that prove my fix is effective or that my feature works
- I have added necessary documentation (if appropriate)
- Any dependent changes have been merged and published in downstream modules
- Submission does not reduce code coverage numbers
- Submission does not increase alerts or messages from prospector / lint
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...