Add GitHub bug, issue, PR templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,66 @@
+---
+name: Bug report
+about: Create a report to help us repair something that is currently broken.
+title: ''
+labels: 'bug'
+assignees: ''
+---
+
+<!-- Welcome! Thank you for contributing. These HTML comments will not render in the issue.
+Before creating a new issue:
+* Search for relevant issues
+* Follow the JupyterLab issue reporting guidelines:
+https://jupyterlab.readthedocs.io/en/latest/getting_started/issue.html
+-->
+
+## Description
+
+<!--Describe the bug clearly and concisely. Include screenshots if possible-->
+
+## Reproduce
+
+<!--Describe step-by-step instructions to reproduce the behavior-->
+
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error '...'
+
+<!--Describe how you diagnosed the issue. See the JupyterLab guidelines at
+ https://jupyterlab.readthedocs.io/en/latest/getting_started/issue.html -->
+
+## Expected behavior
+
+<!--Describe what you expected to happen-->
+
+## Context
+
+<!--Complete the following for context, and add any other relevant context-->
+
+- Operating System and version: <!-- e.g. Linux Ubuntu 21.04 -->
+- Browser and version: <!-- e.g. Chrome 92 -->
+- JupyterLab version: <!-- e.g. 3.1.7 -->
+- Jupyter Scheduler version: <!-- e.g. 2.7.1 -->
+
+<!--The more content you provide, the more we can help!-->
+
+<details><summary>Troubleshoot Output</summary>
+<pre>
+Paste the output from running `jupyter troubleshoot` from the command line here.
+You may want to sanitize the paths in the output.
+</pre>
+</details>
+
+<details><summary>Command Line Output</summary>
+<pre>
+Paste the output from your command line running `jupyter lab` here, use `--debug` if possible.
+</pre>
+</details>
+
+<details><summary>Browser Output</summary>
+<!--See https://webmasters.stackexchange.com/a/77337 for how to access the JavaScript console-->
+<pre>
+Paste the output from your browser Javascript console here, if applicable.
+
+</pre>
+</details>

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,34 @@
+---
+name: Feature request
+about: Suggest a new feature or a change.
+title: ''
+labels: 'enhancement'
+assignees: ''
+---
+
+<!-- Welcome! Thank you for contributing. These HTML comments will not render in the issue, but you can delete them once you've read them if you prefer! -->
+
+<!--
+Thanks for thinking of a way to improve Jupyter Scheduler. If this solves a problem for you, then it probably solves that problem for lots of people! So the whole community will benefit from this request.
+Before creating a new feature request please search the existing issues for relevant feature requests:
+https://github.com/jupyter-server/jupyter-scheduler/issues
+-->
+
+### Problem
+
+<!-- Provide a clear and concise description of what problem this feature will solve. For example:
+* I'm always frustrated when [...] because [...]
+* I would like it if [...] happened when I [...] because [...]
+-->
+
+### Proposed Solution
+
+<!-- Provide a clear and concise description of a way to accomplish what you want. For example:
+* Add an option so that when [...]  [...] will happen
+ -->
+
+### Additional context
+
+<!-- Add any other context or screenshots about the feature request here. You can also include links to examples of other programs that have something similar to your request. For example:
+* Another project [...] solved this by [...]
+-->

.github/pull_request_template.md

@@ -0,0 +1,26 @@
+<!--
+Thanks for contributing to Jupyter Scheduler!
+Please fill out the following items to submit a pull request.
+Please refer to our contributor's guide for more information on installation and usage:
+https://jupyter-scheduler.readthedocs.io/en/latest/contributors/index.html
+-->
+
+## References
+
+<!-- Note the issue numbers this pull request addresses (should be at least one, see the contributing guidelines above). -->
+
+<!-- Note any other pull requests that address this issue and how this pull request is different. -->
+
+## Code changes
+
+<!-- Describe the code changes and how they address the issue. -->
+
+## User-facing changes
+
+<!-- Describe any visual or user interaction changes and how they address the issue. -->
+
+<!-- For visual changes, include before and after screenshots or GIF/mp4/other video demo here. -->
+
+## Backwards-incompatible changes
+
+<!-- Describe any backwards-incompatible changes to JupyterLab public APIs. -->