add github templates (#48)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug Report
+about: Report a bug in molecule-kubevirt
+title: ''
+labels: bug
+assignees: ''
+
+---
+<!-- Make sure that you read carefully README.md and KubeVirt install.
+-->
+
+**What happened**:
+A clear and concise description of what the bug is.
+
+**What you expected to happen**:
+A clear and concise description of what you expected to happen.
+
+**How to reproduce it (as minimally and precisely as possible)**:
+Steps to reproduce the behavior.
+
+**Additional context**:
+Add any other context about the problem here.
+
+**Environment**:
+- ansible --vesion: N/A
+- molecule --version: N/A
+- KubeVirt version (use `virtctl version`): N/A
+- Kubernetes version (use `kubectl version`): N/A
+- OS (e.g. from /etc/os-release): N/A
+- Kernel (e.g. `uname -a`): N/A
+- Install tools: N/A
+- Others: N/A

.github/ISSUE_TEMPLATE/docs_report.md

@@ -0,0 +1,22 @@
+---
+name: Docs Report
+about: Report an issue in molecule-kubevirt's documentation
+title: ''
+labels: documentation
+assignees: ''
+
+---
+<!-- Make sure that you read carefully README.md and KubeVirt install.
+-->
+
+**Description**:
+A clear and concise description of what the issue is.
+
+**What you expected**:
+A clear and concise description of what you expected.
+
+**URL**:
+Provide a link to the documentation.
+
+**Additional context**:
+Add any other context about the issue here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature Request
+about: Suggest an idea for molecule-kubevirt
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+<!-- Make sure that you read carefully README.md and KubeVirt install.
+-->
+
+**Is your feature request related to a problem? Please describe**:
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like**:
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**:
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**:
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+1. Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md
+-->
+
+**What this PR does / why we need it**:
+
+**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
+Fixes #
+
+**Special notes for your reviewer**:
+
+**Release note**:
+<!--  Write your release note:
+1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
+2. If no release note is required, just write "NONE".
+-->
+```release-note
+
+```