add template for PR and bug report

.github/ISSUE_TEMPLATE/bug_report.md/bug_report.md

@@ -0,0 +1,30 @@
+********************************************************************************
+
+name: Bug report about: Report a bug in gomock
+
+********************************************************************************
+
+**Actual behavior** A clear and concise description of what the bug is.
+
+**Expected behavior** A clear and concise description of what you expected to
+happen.
+
+**To Reproduce** Steps to reproduce the behavior
+
+1.  ...
+2.  ...
+
+**Additional Information**
+
+-   gomock mode (reflect or source)
+-   gomock version or git ref
+-   golang version
+
+**Triage Notes for the Maintainers**
+
+<!-- 🎉🎉🎉 Thank you for an opening an issue !!! 🎉🎉🎉 We are doing our best to get to this. Please help us by helping us prioritize your issue by filling the section below -->
+
+**Description**                                      | **Yes/No**
+---------------------------------------------------- | ------------------------
+Please check if this a new feature you are proposing | <ul><li>- [ ] </li></ul>
+Please check if this is an issue with mockgen        | <ul><li>- [ ] </li></ul>

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,31 @@
+<!-- 🎉🎉🎉 Thank you for the PR!!! 🎉🎉🎉 -->
+
+
+Fixes #<issue number>. _in case of a bug fix, this should point to a bug and any other related issue(s)_
+
+**Description**
+
+<!-- Describe your changes here- ideally you can get that description straight from
+your descriptive commit message(s)! -->
+
+**Submitter Checklist**
+
+These are the criteria that every PR should meet, please check them off as you
+review them:
+
+- [ ] Includes tests
+
+**Reviewer Notes**
+
+- [ ] The code flow looks good.
+- [ ] Tests added.
+
+
+**Release Notes**
+
+Describe any changes here so maintainer can include it in the release notes, or delete this block.
+
+```
+Examples of user facing changes:
+- Improved API for custom matchers
+```