📝 Add Community Guidelines

Author: deraw

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when \[...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+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.

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing
+
+First off, thanks for taking the time to contribute! This is really important to help us improve the library.
+
+## Report bugs
+
+Bugs are reported using [GitHub issues](https://guides.github.com/features/issues/).
+
+Before creating a new issue, [check if your bug hasn't alreaydy been reported](https://github.com/assurance-maladie-digital/vue-cli-plugin-proxy/issues?utf8=%E2%9C%93&q=is%3Aissue). If it's the case and you don't find a solution in the comments, contribute to the issue instead of creating a new one.
+
+### Submit a (good) bug report
+
+Explain the problem and include additional details to help maintainers reproduce the problem:
+
+-   **Use a clear and descriptive title**
+-   **Describe the exact steps which reproduce the problem**
+-   **Provide specific examples to demonstrate the steps.** Include links to files or projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use [Markdown code blocks](https://help.github.com/articles/markdown-basics/#multiple-lines).
+
+<br>
+
+[Go to issues](https://github.com/assurance-maladie-digital/vue-cli-plugin-proxy/issues)
+
+## Suggest changes
+
+Enhancement suggestions are tracked as [GitHub issues](https://guides.github.com/features/issues/).
+
+To create enhancement suggestions, [create a new issue](#submitting-a-good-bug-report).
+
+## Code contribution
+
+You can look for issues labelled with `help-wanted` if you're not sure where to start!
+
+#### Commit guidelines
+
+Look at the previous commits for inspiration! But you need it to be explicit, and it should follow these rules:
+
+-   Write it in English
+-   Start with an emoji from [gitmoji](https://gitmoji.carloscuesta.me/) corresponding to the changes made
+-   Do not end the subject line with a period
+-   Capitalize the subject line
+-   Use the imperative mood
+
+#### Pull requests
+
+When creating a pull request, follow and complete the provided template.