chore: add issue, bug and PR templates (#28)

.github/ISSUE_TEMPLATE/---bug.md

@@ -0,0 +1,18 @@
+---
+name: "\U0001F41E Bug"
+about: Something is not working as intended.
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Current Behavior
+
+## Expected Behavior
+
+## Steps To Reproduce
+
+## Operator Version
+
+## `kubectl version`

.github/ISSUE_TEMPLATE/--enhancement---feature---task.md

@@ -0,0 +1,23 @@
+---
+name: "✨ Enhancement / Feature / Task"
+about: 'Some feature is missing or incomplete. '
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Problem Statement
+
+...
+
+## Proposed Solution
+
+...
+
+## Additional Information
+
+...
+
+## Acceptance Criteria
+- [ ] Lorem ipsum dolor sit amet

.github/workflows/pull_request_template.md

@@ -0,0 +1,17 @@
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#the-pull-request-submit-process and developer guide https://github.com/kubernetes/community/blob/master/contributors/devel/development.md
+2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
+3. Follow the instructions for writing a release note: https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md and ensure your changes are being reflected in CHANGELOG.md for the next upcoming release
+-->
+
+**What this PR does / why we need it**:
+
+**Which issue this PR fixes**
+
+**Special notes for your reviewer**:
+
+**PR Readiness Checklist**:
+
+Complete these before marking the PR as `ready to review`:
+
+- [ ] the `CHANGELOG.md` release notes have been updated to reflect significant changes