GitHub Issue/Pull request template

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,68 @@
+<!-- 
+
+- Before submitting an issue please refer to https://lava-nc.org/developer_guide.html#how-to-contribute-to-lava
+
+- Please make sure you are posting an issue pertaining to the github.com/lava-nc/lava, for issues with lava libraries please file in appropriate library repository, for example github.com/lava-nc/lava-dl/issues
+
+- Please do not submit support requests or "How to" questions here, use discussions Q&A https://github.com/lava-nc/lava/discussions/categories/q-a 
+
+- ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION. 
+
+-->
+
+<!-- Insert one sentence issue objective here, can be copied to PR. -->
+Objective of issue:
+
+<!-- Lava Version bug found in or Lava Version feature is targeting-->
+
+**Lava version:**
+- [ ] **0.3.0** (feature release)
+- [ ] **0.2.1** (bug fixes)
+- [x] **0.2.0** (current version)
+- [ ] **0.1.2**
+
+**I'm submitting a ...** 
+<!--  (check one with "x") -->
+- [ ] bug report
+- [ ] feature request
+- [ ] documentation request
+
+<!-- Please do not submit support requests or "How to" questions here, use discussions Q&A https://github.com/lava-nc/lava/discussions/categories/q-a -->
+
+**Current behavior:**
+<!-- Describe the bug or why a new feature is needed, can be copied to PR -->
+- 
+
+**Expected behavior:**
+<!-- Describe how the bug or new feature should work, can be copied to PR -->
+- 
+
+**Steps to reproduce:**
+<!--  If a bug, explain the steps to reproduce the issue -->
+- 
+
+**Related code:**
+
+<!-- If you are able to illustrate the bug or feature request with a code example, please provide a sample application via one of the following means:
+
+A sample application via GitHub
+
+StackBlitz (https://stackblitz.com)
+
+Plunker (http://plnkr.co/edit/cpeRJs?p=preview)
+
+Replit (https://replit.com/languages/python3)
+
+-->
+
+```
+insert short code snippets here
+```
+
+**Other information:**
+<!-- List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, etc. -->
+
+
+```
+insert the output from lava debug here
+```

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,58 @@
+<!-- For questions please refer to https://lava-nc.org/developer_guide.html#how-to-contribute-to-lava or ask in a comment below -->
+
+
+<!-- All pull requests require an issue https://github.com/lava-nc/lava/issues -->
+
+<!-- Insert issue here as "Issue Number: #XXXX", example "Issue Number: #19" -->
+Issue Number: 
+
+<!-- Insert one sentence pr objective here, can be copied from relevant issue. -->
+Objective of pull request:
+
+## Pull request checklist
+
+Your PR fulfills the following requirements:
+- [ ] [Issue](https://github.com/lava-nc/lava/issues) created that explains the change and why it's needed
+- [ ] Tests are part of the PR (for bug fixes / features)
+- [ ] [Docs](https://github.com/lava-nc/docs) reviewed and added / updated if needed (for bug fixes / features)
+- [ ] PR conforms to [Coding Conventions](https://lava-nc.org/developer_guide.html#coding-conventions)
+- [ ] [PR applys BSD 3-clause or LGPL2.1+ Licenses](https://lava-nc.org/developer_guide.html#add-a-license) to all code files
+- [ ] Lint (`pyb`) passes locally
+- [ ] Build tests (`pyb -E unit`) or (`python -m unittest`) passes locally
+
+
+## Pull request type
+
+<!-- Please do not submit updates to dependencies unless it fixes an issue. --> 
+
+<!-- Please limit your pull request to one type, submit multiple pull requests if needed. --> 
+
+Please check your PR type:
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Code style update (formatting, renaming)
+- [ ] Refactoring (no functional changes, no api changes)
+- [ ] Build related changes
+- [ ] Documentation changes
+- [ ] Other (please describe): 
+
+
+## What is the current behavior?
+<!-- Please describe the current behavior that you are modifying, can be copied from relevant issue. -->
+-
+
+## What is the new behavior?
+<!-- Please describe the new behavior, can be copied from relevant issue. -->
+-
+
+## Does this introduce a breaking change?
+
+- [ ] Yes
+- [ ] No
+
+<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
+
+
+## Supplemental information
+
+<!-- Any other information that is important to this PR. -->