|
| 1 | +## Proposed changes |
| 2 | +Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. |
| 3 | +If it fixes a bug or resolves a feature request, be sure to link to that issue. |
| 4 | + |
| 5 | +## Types of changes |
| 6 | +What types of changes does your code introduce to Lowcoder? |
| 7 | +_Put an `x` in the boxes that apply._ |
| 8 | + |
| 9 | +- [ ] Bugfix (non-breaking change which fixes an issue) |
| 10 | +- [ ] New feature (non-breaking change which adds functionality) |
| 11 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) |
| 12 | +- [ ] Documentation Update (if none of the other choices apply) |
| 13 | + |
| 14 | +## Checklist |
| 15 | +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! |
| 16 | +This is simply a reminder of what we are going to look for before merging your code. |
| 17 | +_Put an `x` in the boxes that apply._ |
| 18 | + |
| 19 | +- [ ] Lint and unit tests pass locally with my changes |
| 20 | +- [ ] I have added tests that prove my fix is effective or that my feature works |
| 21 | +- [ ] I have added necessary documentation (if appropriate) |
| 22 | +- [ ] Any dependent changes have been merged and published in downstream modules |
| 23 | + |
| 24 | +## Further comments |
| 25 | +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. |
0 commit comments