Skip to content

Conversation

@jobjen02
Copy link

@jobjen02 jobjen02 commented Mar 16, 2022

Description

A few sentences describing the overall goals of the pull request's commits.

Type of change

  • 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)
  • This change requires a documentation update

Checklist

  • My code follows the style guidelines of this project
  • 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
  • I have added tests that prove my fix is effective or that my feature works
  • I updated the changelog with an end-user readable description
  • I assigned this pull request to the correct project board to update the sprint board

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.
These steps will be used during release testing.

  1. Do something here...
  2. Then run this test...
  3. After that, you should see the result here

Link to issue

Closes: #issuenumber

@jobjen02 jobjen02 requested a review from kallepronk March 16, 2022 12:00
@wilrikdeloose
Copy link
Contributor

Why aren't there any tests? Also a lot of other checks are left open. Why is that? Make sure to respect the checklist and take it seriously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants