chore: pull request and issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: 🐛 Bug Report
+about: If something isn't working as expected 🤔.
+---
+
+<!--
+Thank you for reporting an issue.
+
+Please fill in as much of the template below as you're able.
+-->
+
+## Bug Report
+
+### Version
+
+<!--
+List the versions of all `axum` crates you are using. The easiest way to get
+this information is using `cargo tree`:
+
+`cargo tree | grep axum`
+-->
+
+### Platform
+
+<!---
+Output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
+-->
+
+### Description
+
+<!--
+Enter your issue details below this comment.
+
+One way to structure the description:
+
+<short summary of the bug>
+
+I expected to see this happen: <explanation>
+
+Instead, this happened: <explanation>
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,34 @@
+---
+name: 💡 Feature Request
+about: I have a suggestion (and may want to implement it 🙂)!
+---
+
+<!--
+This is a template to help you request your feature, feel free to skip
+anything you are unsure of how to describe or fill
+-->
+
+- [ ] I have looked for existing issues (including closed) about this
+
+## Feature Request
+
+### Motivation
+
+<!--
+Please describe the use case(s) or other motivation for the new feature.
+-->
+
+### Proposal
+
+<!--
+How should the new feature be implemented, and why? Add any considered
+drawbacks.
+-->
+
+### Alternatives
+
+<!--
+Are there other ways to solve this problem that you've considered? What are
+their potential drawbacks? Why was the proposed solution chosen over these
+alternatives?
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+<!--
+Thank you for your Pull Request. Please provide a description above and review
+the requirements below.
+
+Bug fixes and new features should include tests.
+
+Contributors guide: https://github.com/wllfaria/reqtui/blob/main/CONTRIBUTING.md
+-->
+
+## Motivation
+
+<!--
+Explain the context and why you're making that change. What is the problem
+you're trying to solve? If a new feature is being added, describe the intended
+use case that feature fulfills.
+-->
+
+## Solution
+
+<!--
+Summarize the solution and provide any necessary context needed to understand
+the code change.
+-->