Keep tracking origin

.dockerignore

@@ -0,0 +1,10 @@
+venv/
+documentation/
+rego_clone/
+.github/
+docker/
+Makefile
+Dockerfile
+.dockerignore
+.gitignore
+.pre-commit-config.yaml

.editorconfig

@@ -13,4 +13,4 @@ indent_size=4
 
 [Makefile]
 indent_size=2
-indent_style=tab
+indent_style=tab

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Submit a bug report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Please include steps to reproduce the bug: i.e: run OPAL, submit a realtime update through the API, etc.
+
+Please also include:
+- Full logs of opal server and opal client
+- Your configuration for OPAL server and OPAL client
+  - i.e: docker compose, Kubernetes YAMLs, environment variables, etc.
+  - you should redact any secrets/tokens/api keys in your config
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**OPAL version**
+ - Version: [e.g. 0.1.18]

.github/ISSUE_TEMPLATE/documentation_template.md

@@ -0,0 +1,3 @@
+We welcome any suggestions to improve the documentation.
+
+Please let us know what is not clear / missing from the docs.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+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,37 @@
+<!-- If your PR fixes an open issue, use `Closes #999` to link your PR with the issue. #999 stands for the issue number you are fixing -->
+
+## Fixes Issue
+
+<!-- Remove this section if not applicable -->
+
+<!-- Example: Closes #31 -->
+
+## Changes proposed
+
+<!-- List all the proposed changes in your PR -->
+
+<!-- Mark all the applicable boxes. To mark the box as done follow the following conventions -->
+<!--
+[x] - Correct; marked as done
+[X] - Correct; marked as done
+
+[ ] - Not correct; marked as **not** done
+-->
+
+## Check List (Check all the applicable boxes) <!-- Follow the above conventions to check the box -->
+
+- [x] I sign off on contributing this submission to open-source
+- [ ] My code follows the code style of this project.
+- [ ] My change requires changes to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] All new and existing tests passed.
+- [ ] This PR does not contain plagiarized content.
+- [ ] The title of my pull request is a short description of the requested changes.
+
+## Screenshots
+
+<!-- Add all the screenshots which support your changes -->
+
+## Note to reviewers
+
+<!-- Add notes to reviewers if applicable -->