Skip to content

Latest commit

 

History

History
45 lines (37 loc) · 1.75 KB

PULL_REQUEST_TEMPLATE.md

File metadata and controls

45 lines (37 loc) · 1.75 KB
name about title labels assignees
Pull Request
Propose changes to the codebase
[PR]

Description

Please provide a detailed description of the pull request and the changes it introduces to the project. Explain the issue it resolves or the feature it adds.

Related Issue(s)

Please link to the existing issue(s) that this pull request addresses, if applicable. Use the syntax Fixes #issue_number or Closes #issue_number to automatically close the issue when the pull request is merged.

Type of Change

What types of changes does your code introduce to the project?

  • Bug fix
  • New feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Proposed Changes

  • Change 1
  • Change 2
  • Change 3

Checklist

Before submitting your pull request, consider the following:

  • I have read the contributing guidelines.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • Any dependent changes have been merged and published in downstream modules.

Additional Information

Any additional information, configuration, or data that might be necessary to reproduce the environment in which the bug exists or the feature works.