Add GitHub templates (#25)

Author: johan3141592

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,53 @@
+---
+name: Bug Report
+about: Report a bug encountered while using the Terraform Provider for Rubrik Polaris.
+title: ''
+labels: kind-bug
+assignees: ''
+
+---
+
+<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!-->
+
+
+**Expected Behavior**
+
+Please describe the behavior you are expecting.
+
+**Current Behavior**
+
+What is the current behavior?
+
+**Failure Information (for bugs)**
+
+Please help provide information about the failure if this is a bug.
+
+
+* Use verbose outputs to capture any debug information.
+```
+Paste into a code block.
+```
+
+**Steps to Reproduce**
+
+Please provide detailed steps for reproducing the issue.
+
+* Use numbered list.
+
+**Context**
+
+Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
+
+* Version of project.
+* Version of dependencies.
+* Version of operating system.
+
+**Failure Logs**
+
+Please include any relevant log snippets or files here.
+
+* Use verbose outputs to capture any debug information.
+
+```
+Paste into a code block.
+```

.github/ISSUE_TEMPLATE/enhancement-request.md

@@ -0,0 +1,26 @@
+---
+name: Enhancement Request
+about: Suggest an enhancement to the Terraform Provider for Rubrik Polaris.
+title: ''
+labels: kind-enhancement
+assignees: ''
+
+---
+
+<!-- Please only use this template for submitting enhancement requests -->
+
+**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,40 @@
+# Description
+
+Please describe your pull request in detail.
+
+## Related Issue
+
+This project only accepts pull requests related to open issues.
+
+* If suggesting a new feature or change, please discuss it in an issue first.
+* If fixing a bug, there should be an issue describing it with steps to reproduce
+
+_Please link to the issue here_
+
+## Motivation and Context
+
+Why is this change required? What problem does it solve?
+
+## How Has This Been Tested?
+
+* Please describe in detail how you tested your changes.
+* Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc.
+
+## Screenshots (if appropriate):
+
+## Types of changes
+
+What types of changes does your code introduce? Put an `x` in all the boxes that apply:
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist:
+
+Go over all the following points, and put an `x` in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.
+- [ ] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at build@rubrik.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1 @@
+Contributions via GitHub pull requests are gladly accepted from their original author. Along with any pull requests, please state that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.