fruivita/corporate

View on GitHub
docs/PULL_REQUEST_TEMPLATE.md

Summary

Maintainability
Test Coverage
# Proposed changes (mandatory)

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

1. What is the current behavior? (if appropriate)

    Fixes Issue Number: N/A

2. What is the new behavior? (if appropriate)

    - Something

    - Else

## Pull Request Types (mandatory)

> *What types of changes does your code introduce? Put an x in the boxes that apply*

- [] Doc update (non-breaking change which fixes typos or improve readability)

- [] 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)

- [] Other (please describe):

## Before you submit a pull request, please make sure you have to following (mandatory)

> *Go over all the following points, and put an **x** in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!*

- [] My code follows the code style of this project.

- [] I have commented my code, particularly in hard-to-understand areas.

- [] I have made corresponding changes to the documentation.

- [] I have read the **[CONTRIBUTING](CONTRIBUTING.md)** document.

- [] I have added tests that prove my fix is effective or that my feature works.

- [] All new and existing tests and lint passed.

## Any relevant logs, error output, etc (if appropriate)

## Screenshots (if appropriate)

## Further comments (if appropriate)

> If this is a relatively large or complex change, kick off the [discussion](https://github.com/orgs/fruivita/discussions/new?category=ideas&title=[Corporate]) by explaining why you chose the solution you did and what alternatives you considered, etc...

💔Thank you!