pull_request_template.md

Description

Related issue(s)

Fixed #

✅ Checklist for your Pull Request

Related changes (conditional)

• Tests
  • If I added new functionality, I added tests covering it.
  • If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

• Documentation
  • I checked whether I should update the docs and did so if necessary:
    • README
    • Haddock

• Public contracts
  • Any modifications of public contracts comply with the Evolution of Public Contracts policy.
  • I added an entry to the changelog if my changes are visible to the users and
  • provided a migration guide for breaking changes if possible

Stylistic guide (mandatory)

• My commits comply with the policy used in Serokell.
• My code complies with the style guide.

✓ Release Checklist

• I updated the version number in package.yaml.
• If any definitions (functions, type classes, instances, etc) were added, I added @since haddock annotations.
• (After merging) I created a new entry on the releases page, with a summary of all user-facing changes.
  • I made sure a tag was created using the format vX.Y.Z
• (After merging) I uploaded the package to hackage.