Merge #320

320: Add categories to release-drafter r=alallema a=curquiza

This PR is an example of what I'm going to add to every repository.
I am inspired by what is already done in the Gatsby integration (based on our meeting discussion I guess 😇)


This PR is a final validation before implementation! (and a check it will work as expected).

⚠️ If no label is put, the PR will be put at the top of the changelog, but I don't recommend letting it. It means you will have to put a label on every PR from now. We discussed it during our weekly meeting and you say you are ok with this addition in your process, **do you still agree with this**?
In the future, we might want to add tool to enforce a label to be present as requirement to merge a PR.

Co-authored-by: Clémentine Urquizar <[email protected]>

Author: bors[bot]

.github/release-draft-template.yml

@@ -8,11 +8,15 @@ version-resolver:
       - 'breaking-change'
   default: patch
 categories:
-  - title: 'Breaking changes ⚠️'
+  - title: '⚠️ Breaking changes'
     label: 'breaking-change'
+  - title: '🚀 Enhancements'
+    label: 'enhancement'
+  - title: '🐛 Bug Fixes'
+    label: 'bug'
+  - title: '🔒 Security'
+    label: 'security'
 template: |
-  ## Changes
-
   $CHANGES
 
   Thanks again to $CONTRIBUTORS! 🎉