-
Notifications
You must be signed in to change notification settings - Fork 6
Closed
Milestone
Description
It would be helpful to introduce a template for PRs with a checklist of things to consider/include. This would help avoiding some common mistakes developers make (including myself). For example in about half of the merged PRs, we forget to update the changelog with relevant info for the user, which then has to be added later.
Things to include in the the checklist/definition of done:
- Link to issue
- Description of changes broadly made and how they are going to fix the issue
- Update changelog, if changes are relevant to the users (e.g. bugfix, API changes, changes in behaviour)
- PR title starts with issue number, like
#737
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
✅ Done