Initial commit

Author: kylejb

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: "🐛 Bug Report"
+about: Report a reproducible bug or regression.
+title: 'Bug: '
+labels: 'Status: Unconfirmed'
+
+---
+
+<!--
+  Please provide a clear and concise description of what the bug is. Include screenshots if needed.
+-->
+## Steps To Reproduce
+
+1.
+2.
+
+<!--
+  Your bug will get fixed much faster if we can run your code. Issues without reproduction steps or code examples may be immediately closed as not actionable.
+-->
+
+Link to code example:
+
+<!--
+  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve.
+-->
+
+## The current behavior
+
+
+## The expected behavior

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## What
+
+**Is your feature request related to a problem? Please describe.**
+- Clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## How
+
+**Describe the solution you'd like**
+- Clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+- Clear and concise description of any alternative solutions or features you've considered.
+
+
+## {Subtitle} (e.g., Why)
+
+**Additional context**
+- Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -0,0 +1,39 @@
+<!--
+
+Note: Remember to add the 'in progress' label, if this PR is still a work-in-progress and create a draft PR. Once it's ready, please remove the label and mark the PR as ready for review!
+-->
+
+## Description
+
+<!-- Write a brief description of the changes introduced by this PR -->
+
+### Documentation
+
+<!--
+  If this is a feature PR, then where is it documented?
+
+  - If docs exist:
+    - Update any references, if relevant.
+  - If no docs exist:
+    - Create a stub for documentation including bullet points for how to use the feature, code snippets (including from happy path tests), etc.
+-->
+
+<!-- Important: Did you make any backward incompatible changes? If yes, then you must write a migration guide! -->
+
+## TODOs
+
+Please ensure all of these TODOs are completed before asking for a review.
+
+- [ ] Ensure the branch is named correctly with the issue number. e.g: `feat/310-new-endpoint` or `bug/322-fix-missing-param`.
+- [ ] Update the docs.
+- [ ] Keep the changes backward compatible where possible.
+- [ ] Run the pre-commit checks successfully.
+
+## Related Issues
+
+<!--
+  Link to related issues, and issues fixed or partially addressed by this PR.
+  e.g. Fixes #1234
+  e.g. Closes #1234
+  e.g. Related to #1234
+-->

.gitignore

@@ -0,0 +1,50 @@
+## Testing
+/coverage
+
+## Misc
+.DS_Store
+.vscode
+.idea
+
+## Logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+## Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+## IPython
+profile_default/
+ipython_config.py
+
+## pyenv
+.python-version
+
+## Environment
+*.env
+.env.*
+.venv
+
+## mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json

.pre-commit-hooks.yaml

@@ -0,0 +1,5 @@
+- id: branch-validate
+  name: branch-validate
+  description: Enforce git branch naming conventions in repository
+  entry: githooks/branch_validate.sh
+  language: script