chore: update github templates

.github/issue_template.md

@@ -1,41 +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 behaviour is correct.
+  * Provide your config file is really helpful. Please be aware to hide sensisive data (passwords, server IP, etc) before post.
+-->
+
 #### My reason:
-
-<!-- 
-	a brief explanation of the issue, suggestion, feature
--->
-
 #### Steps to reproduce:
-
-<!-- 
-	(if it applies)
-	how can I do in order to reproduce it? environment? 
--->
 #### App Version:
-<!-- 
-      Define which version the issue happens and whether previous version the behaviour is correct
--->
-
 #### Config file:
-<!-- 
-      Provide your config file might be really helpful. Please be aware to hide sensisive data before post.
--->
-
 #### Additional information:
 
-<!--
+ - `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
-	provide the following information would be helpful
+ - `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
--->
+ - `$ npm -ddd` prints:
-	
- - `$ set DEBUG=express:* verdaccio` enable extreme verdaccio debug mode
- - `$ npm --verbose` prints:
  - `$ npm config get registry` prints:
  - Verdaccio terminal output
- - Windows, OS X/macOS, or Linux?:
+ - Which (Windows, OS X/macOS, or Linux) environment are you running verdaccio?:
  - Verdaccio configuration file, eg: `cat ~/.config/verdaccio/config.yaml`
- <!-- Remove those does not apply for you -->
+  - Container Options:
- - Container:
+   - Docker?:
-   - I use local environment
+   - Kubernetes?:
-   - I develop / deploy using Docker.
-   - I deploy to a PaaS.
 
 #### Additional verbose log:
+

.github/pull_request_template.md

@@ -1,29 +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 Pull Request fix an issue don't forget to update the unit test and documentation in /docs folder
-  If your Pull Request delivers a new feature, please, provide examples and why such feature should be considered, this information is important to document the Github changelog. Also, try to increase documentation and create new unit/functional test.  
--->
 
-<!-- Pick only one type, whether none apply, please suggest one, we might be included it by default -->
+Before Pull Request check whether your commits follow this convention
-**Type:** bug / feature / documentation / unit test / build
+
+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:
 
-<!-- Remove the sections that your PR does not apply -->
+*  There is a related issue?
-*  There is a related issue
 *  Unit or Functional tests are included in the PR
 
-<!--
-Our bots should ensure:
-* The PR passes CI testing
--->
-
-<!-- If there is no issue related to this PR just remove the following section -->
 **Description:**
 
-Resolves #???
+<!-- Resolves #??? -->
-
-<!-- We are glad your code is part of this community, thanks for your valuable time !! -->