chore: 🤖 add github templates

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,27 @@
+---
+Before filing an issue we'd appreciate it if you could take a moment to ensure
+there isn't already an open issue or pull-request.
+---
+
+If there's an existing issue, please add a :+1: reaction to the description of
+the issue. One way we prioritize issues is by the number of :+1: reactions on
+their descriptions. Please DO NOT add `+1` or :+1: comments.
+
+### Feature requests and proposals
+
+We're excited to hear how we can make Svelte better. Please add as much detail
+as you can on your use case.
+
+### Bugs
+
+If you're filing an issue about a bug please include as much information
+as you can including the following.
+
+- Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10)
+- Your operating system: (e.x. OS X 10, Windows XP, etc)
+- `svelte-i18n` version (Please check you can reproduce the issue with the latest release!)
+- Whether your project uses Webpack or Rollup
+
+- _Repeatable steps to reproduce the issue_
+
+## Thanks for being part of Svelte!

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,47 @@
+---
+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.
+
+**Logs**
+Please include browser console and server logs around the time this bug occurred.
+
+**To Reproduce**
+To help us help you, if you've found a bug please consider the following:
+
+- Please create a small repo that illustrates the problem.
+- Reproductions should be small, self-contained, correct examples – http://sscce.org.
+
+Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that `svelte-preprocess` is run by unpaid volunteers in their free time, and issues that follow these instructions will get fixed faster.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Stacktraces**
+If you have a stack trace to include, we recommend putting inside a `<details>` block for the sake of the thread's readability:
+
+<details>
+  <summary>Stack trace</summary>
+
+Stack trace goes here...
+
+</details>
+
+**Information about your project:**
+
+- Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10)
+
+- Your operating system: (e.x. OS X 10, Ubuntu Linux 19.10, Windows XP, etc)
+
+- `svelte-i18n` version (Please check you can reproduce the issue with the latest release!)
+
+- Whether your project uses Webpack or Rollup
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'New Feature'
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. For example: 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.
+
+**How important is this feature to you?**
+Note: the more honest and specific you are here the more we will take you seriously.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+### Before submitting the PR, please make sure you do the following
+
+- [ ] It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases features are absent for a reason.
+- [ ] This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
+- [ ] Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to `npm run lint`!)
+
+### Tests
+
+- [ ] Run the tests tests with `npm test` or `yarn test`

.github/workflows/ci.yml

@@ -0,0 +1,30 @@
+name: CI
+
+on: [push, pull_request]
+
+jobs:
+  Lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: actions/setup-node@v1
+      - run: 'npm i && npm run lint'
+
+  Tests:
+    needs: [Lint]
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        node-version: [8, 10, 12]
+        os: [ubuntu-latest, windows-latest, macOS-latest]
+
+    steps:
+      - run: git config --global core.autocrlf false
+      - uses: actions/checkout@v1
+      - uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+      - run: npm install
+      - run: npm run test:ci
+        env:
+          CI: true