Ability to specify no variant (#2)

Since Python 3.10 has been released the docker image has been bumped.
Bumped version to 1.1.0
Adds PR template and issue templates
Removes pylint config

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Stacktrace/Code**
+If applicable, add stacktrace or code segments to help explain your problem.
+
+**Environment:**
+
++ OS: (e.g. Linux)
++ Python version: (e.g. 3.8.5)
++ pytest-variant version: (e.g. 0.2.1)
+
+```text
+Optionally include the output of 'pipdeptree --warn silence -p pytest-variant'
+```
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'enhancement'
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**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,36 @@
+## Brief
+
+- Please provide brief information, what this pull request provides or fixes, possibly in a list format
+
+### Checklist
+
+<!-- Use the checklist below to ensure the changes are correct and consistent
+     with the rest of the codebase.
+ -->
+
+- [ ] Add relevant labels to the Pull Request
+- [ ] Review test results and code coverage
+- [ ] Review code changes
+  - [ ] Create relevant test scenarios
+  - [ ] Update examples
+- [ ] Update documentation
+- [ ] Update version number
+
+## Resolves
+
+<!--
+     Use the syntax: "Fixes #42" or "Resolves #42" to automatically link to issues.
+ -->
+
++ Describe the bug or feature and link to relevant issues
+
+## Evidence
+
+<!-- This section is meant to provide proof that the PR is correct.
+     Here you should note if a change will possibly break existing usage of the library
+     or how new features are tested.
+ -->
+
++ Analyze how the change might impact existing code
+
++ Provide evidence that the feature is tested and covered properly

.github/workflows/build.yml

@@ -8,7 +8,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ['3.6', '3.9', '3.10.0b1']
+        python-version: ['3.6', '3.9', '3.10']
     container:
       image: python:${{ matrix.python-version }}
     steps:
@@ -32,7 +32,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ['3.6', '3.9', '3.10.0b1']
+        python-version: ['3.6', '3.9', '3.10']
     container:
       image: python:${{ matrix.python-version }}
     steps: