chore(): gitlab templates

.gitlab/issue_templates/Bug.md

@@ -0,0 +1,33 @@
+<!---
+Please read this!
+
+1. Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "bug" label and verify the issue you're about to submit isn't a duplicate.
+
+2. Make sure you're including the name of the affected component if applicable.
+--->
+
+### Summary
+
+(Summarize the bug encountered concisely)
+
+### Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+### What is the current _bug_ behavior?
+
+(What actually happens)
+
+### What is the expected _correct_ behavior?
+
+(What you should see instead)
+
+### Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output,
+logs, and code as it's tough to read otherwise.)
+
+### Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)

.gitlab/issue_templates/Feature.md

@@ -0,0 +1,24 @@
+<!---
+Please read this!
+
+1. Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "feature" label and verify the issue you're about to submit isn't a duplicate.
+
+2. Make sure you're including the name of the affected component if applicable.
+--->
+
+### Summary
+
+(Summarize the feature concisely)
+
+### What is the expected behavior?
+
+(Describe what the user should see)
+
+### Relevant mockups or screenshots
+
+(Paste or link any relevant mockups or screenshot that describe the feature.)
+
+### Possible approach
+
+(Outline a possible approach for this feature, ex. make an example how the code could look like)