Vendor dependencies

notes-service/vendor/email_address/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+A clear and concise description of what you expected to happen.
+
+## Minimal Reproducible Examples (MRE)
+
+Please try to provide information which will help us to fix the issue faster. MREs with few dependencies are especially lovely <3.
+
+If applicable, add logs/screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - Platform: [e.g.`uname -a`]
+ - Rust [e.g.`rustic -vV`]
+ - Cargo [e.g.`cargo -vV`]
+
+## Additional context
+
+Add any other context about the problem here. For example, environment variables like `CARGO`, `RUSTUP_HOME` or `CARGO_HOME`.

notes-service/vendor/email_address/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,28 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+## Problem
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+Include Issue links if they exist.
+
+Minimal Reproducible Examples (MRE) with few dependencies are useful.
+
+## Solution
+
+A clear and concise description of what you want to happen.
+
+## Alternatives
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

notes-service/vendor/email_address/.github/ISSUE_TEMPLATE/spec_bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Specification Non-conformance report
+about: Report an error in our implementation
+title: ''
+labels: specification
+assignees: ''
+
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+Please include references to the relevant specification; for example:
+
+> RFC 2616, section 4.3.2:
+> 
+> > The HEAD method is identical to GET except that the server MUST NOT
+> > send a message body in the response
+
+## Minimal Reproducible Examples (MRE)
+
+Please try to provide information which will help us to fix the issue faster. MREs with few dependencies are especially lovely <3.
+
+## Additional context
+
+Add any other context about the problem here. For example, any other specifications that provide additional information, or other implementations that show common behavior.