From 148b33c1e39b0d6f34450172bfc4733eba9e9414 Mon Sep 17 00:00:00 2001
From: Wes Carroll <wcarroll@oceanbeachlife.com>
Date: Wed, 19 Jun 2019 17:03:23 -0400
Subject: [PATCH] Add Issue and PR Templates

---
 .github/CONTRIBUTING.md          | 62 ++++++++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE.md        | 31 ++++++++++++++++
 .github/PULL_REQUEST_TEMPLATE.md | 37 +++++++++++++++++++
 3 files changed, 130 insertions(+)
 create mode 100644 .github/CONTRIBUTING.md
 create mode 100644 .github/ISSUE_TEMPLATE.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
new file mode 100644
index 0000000..4006efc
--- /dev/null
+++ b/.github/CONTRIBUTING.md
@@ -0,0 +1,62 @@
+# How to contribute
+
+Contributions to ZertoApiWrapper are highly encouraged and desired.
+Below are some guidelines that will help make the process as smooth as possible.
+
+## Getting Started
+
+- Make sure you have a [GitHub account](https://github.com/signup/free)
+- Submit a new issue, assuming one does not already exist.
+  - Clearly describe the issue including steps to reproduce when it is a bug.
+  - Make sure you fill in the earliest version that you know has the issue.
+- Fork the repository on GitHub
+
+## Suggesting Enhancements
+
+I want to know what you think is missing from ZertoApiWrapper and how it can be made better.
+
+- When submitting an issue for an enhancement, please be as clear as possible about why you think the enhancement is needed and what the benefit of it would be.
+
+## Making Changes
+
+- From your fork of the repository, create a topic branch where work on your change will take place.
+- To quickly create a topic branch based on master; `git checkout -b my_contribution master`.
+  Please avoid working directly on the `master` branch.
+- Make commits of logical units.
+- Check for unnecessary whitespace with `git diff --check` before committing.
+- Please follow the prevailing code conventions in the repository.
+  Differences in style make the code harder to understand for everyone.
+- Make sure your commit messages are in the proper format.
+
+```
+    Add more cowbell to Get-Something.ps1
+
+    The functionality of Get-Something would be greatly improved if there was a little
+    more 'pizzazz' added to it. I propose a cowbell. Adding more cowbell has been
+    shown in studies to both increase one's mojo, and cement one's status
+    as a rock legend.
+```
+
+- Make sure you have added all the necessary Pester tests for your changes.
+- Run _all_ Pester tests in the module to assure nothing else was accidentally broken.
+
+## Documentation
+
+I am infallible and as such my documenation needs no corectoin.
+In the highly unlikely event that that is _not_ the case, commits to update or add documentation are highly apprecaited.
+
+## Submitting Changes
+
+- Push your changes to a topic branch in your fork of the repository.
+- Submit a pull request to the main repository.
+- Once the pull request has been reviewed and accepted, it will be merged with the master branch.
+- Celebrate
+
+## Additional Resources
+
+- [General GitHub documentation](https://help.github.com/)
+- [GitHub forking documentation](https://guides.github.com/activities/forking/)
+- [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
+- [GitHub Flow guide](https://guides.github.com/introduction/flow/)
+- [GitHub's guide to contributing to open source projects](https://guides.github.com/activities/contributing-to-open-source/)
+
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000..28202e0
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,31 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Module version used:
+* Operating System and PowerShell version:
+* Zerto Virtual Manager Version:
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..52edb2a
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,37 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+<!--- Describe your changes 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 read the **CONTRIBUTING** document.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.
+