GitHub actions (#32)

* chore: fixes snapshots test

* chore: adds github actions, issue and feat templates

* chore: fixes eslint

* chore: remvoes circle ci and adds publish action

* chore: adds github-release automation using actions

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,37 @@
+---
+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.
+
+**Docker || Kubernetes (please complete the following information):**
+ - Docker verdaccio tag: [e.g. verdaccio:beta]
+ - Docker commands [e.g. docker pull ...]
+ - Docker Version [e.g. v18.05.0-ce-rc1]
+
+**Configuration File (cat ~/.config/verdaccio/config.yaml)** 
+
+**Debugging output**
+ - `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
+ - `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
+ - `$ npm -ddd` prints:
+ - `$ npm config get registry` prints:
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,17 @@
+---
+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.

.github/issue_template.md

@@ -0,0 +1,32 @@
+<!--
+First of all, please read this section
+
+https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#reporting-a-bug
+
+Some advices before file an issue
+  * Give a brief explanation of the issue, suggestion or feature to request.
+  * If the issue is a question, provide as much information you have available.
+  * How can I do in order to reproduce it? What environment?
+  * Define which version the issue happens and whether previous version the behavior is correct.
+  * Provide your config file is really helpful. Please be aware to hide sensitive data (passwords, server IP, etc) before post.
+-->
+
+#### My reason:
+#### Steps to reproduce:
+#### App Version:
+#### Config file:
+#### Additional information:
+
+ - `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
+ - `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
+ - `$ npm -ddd` prints:
+ - `$ npm config get registry` prints:
+ - Verdaccio terminal output
+ - Which (Windows, OS X/macOS, or Linux) environment are you running verdaccio?:
+ - Verdaccio configuration file, eg: `cat ~/.config/verdaccio/config.yaml`
+  - Container Options:
+   - Docker?:
+   - Kubernetes?:
+
+#### Additional verbose log:
+

.github/main.workflow

@@ -0,0 +1,71 @@
+workflow "build and test" {
+  resolves = [
+    "lint",
+    "test",
+    "branch-filter",
+  ]
+  on = "push"
+}
+
+action "branch-filter" {
+  uses = "actions/bin/filter@master"
+  args = "branch"
+}
+
+action "install" {
+  uses = "docker://node:10"
+  args = "yarn install"
+}
+
+action "build" {
+  uses = "docker://node:10"
+  needs = ["install"]
+  args = "yarn run build"
+}
+
+action "lint" {
+  uses = "docker://node:10"
+  needs = ["install"]
+  args = "yarn run lint"
+}
+
+action "test" {
+  uses = "docker://node:10"
+  needs = ["build"]
+  args = "yarn run test"
+}
+
+workflow "release" {
+  resolves = [
+    "github-release",
+    "tag-filter",
+    "lint",
+  ]
+  on = "push"
+}
+
+action "tag-filter" {
+  uses = "actions/bin/filter@master"
+  args = "tag v*"
+}
+
+action "publish" {
+  needs = ["test"]
+  uses = "docker://node:10"
+  args = "sh scripts/publish.sh"
+  secrets = [
+    "REGISTRY_AUTH_TOKEN",
+  ]
+  env = {
+    REGISTRY_URL = "registry.verdaccio.org"
+  }
+}
+
+action "github-release" {
+  needs = ["publish"]
+  uses = "docker://node:10"
+  args = "sh scripts/github-release.sh"
+  secrets = [
+    "GITHUB_TOKEN",
+  ]
+}

.github/pull_request_template.md

@@ -0,0 +1,27 @@
+<!--
+
+Before Pull Request check whether your commits follow this convention
+
+https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#git-commit-guidelines
+
+  * If your PR fix an issue don't forget to update the unit test and documentation in /docs folder
+  * If your PR delivers a new feature, please, provide examples and why such feature should be considered.
+  * Document your changes /docs
+  * Add unit test
+  * Follow the commit guidelines in order to get a quick approval
+
+Pick one/multiple type, if none apply please suggest one, we might be included it by default
+
+eg: bug / feature / documentation / unit test / build
+
+-->
+**Type:**
+
+The following has been addressed in the PR:
+
+*  There is a related issue?
+*  Unit or Functional tests are included in the PR
+
+**Description:**
+
+<!-- Resolves #??? -->