From e4ca03ff16dc7748d335237fcf5322b092c99247 Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Thu, 16 Jan 2020 02:11:08 +0530
Subject: [PATCH 01/12] Added new PR template

---
 .github/PR_TEMPLATE/pull_request.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 .github/PR_TEMPLATE/pull_request.md

diff --git a/.github/PR_TEMPLATE/pull_request.md b/.github/PR_TEMPLATE/pull_request.md
new file mode 100644
index 0000000000..f54252fcfa
--- /dev/null
+++ b/.github/PR_TEMPLATE/pull_request.md
@@ -0,0 +1,16 @@
+## Description
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Change Type
+<!-- Please select all items that apply either now or after creating the pull request: -->
+- [ ] Documentation update
+- [ ] Bug fix
+- [ ] New feature
+
+## Checklist:
+<!-- Please select all items that apply either now or after creating the pull request. -->
+- [ ] I am familiar with the [**Contributing Guidelines**](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md).
+- [ ] I have read and will abide by [**Code of Conduct**](https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md).
+- [ ] My code follows the [pull request checklist](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist).
+- [ ] The changes introduced by this pull request are covered by existing or newly introduced tests.

From 4b8925dbedeaaf8d2721f796d482cc8b97480f94 Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Thu, 16 Jan 2020 20:00:18 +0530
Subject: [PATCH 02/12] Add temlates for bug-fix, documentation and new
 features

---
 .github/PR_TEMPLATE/pull_request.md           | 16 ------
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md      | 53 +++++++++++++++++
 .../PULL_REQUEST_TEMPLATE/documentation.md    | 50 ++++++++++++++++
 .github/PULL_REQUEST_TEMPLATE/new-feature.md  | 57 +++++++++++++++++++
 4 files changed, 160 insertions(+), 16 deletions(-)
 delete mode 100644 .github/PR_TEMPLATE/pull_request.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/bug-fix.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/documentation.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE/new-feature.md

diff --git a/.github/PR_TEMPLATE/pull_request.md b/.github/PR_TEMPLATE/pull_request.md
deleted file mode 100644
index f54252fcfa..0000000000
--- a/.github/PR_TEMPLATE/pull_request.md
+++ /dev/null
@@ -1,16 +0,0 @@
-## Description
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
-
-## Change Type
-<!-- Please select all items that apply either now or after creating the pull request: -->
-- [ ] Documentation update
-- [ ] Bug fix
-- [ ] New feature
-
-## Checklist:
-<!-- Please select all items that apply either now or after creating the pull request. -->
-- [ ] I am familiar with the [**Contributing Guidelines**](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md).
-- [ ] I have read and will abide by [**Code of Conduct**](https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md).
-- [ ] My code follows the [pull request checklist](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist).
-- [ ] The changes introduced by this pull request are covered by existing or newly introduced tests.
diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
new file mode 100644
index 0000000000..ba05ca87c2
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -0,0 +1,53 @@
+## Description
+<!-- Briefly describe the bug you are trying to fix -->
+
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below)?
+- [ ] Have you added the unit tests to prevent issue reoccurance( using [pytest fixture pattern](
+      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Have you run the unit tests using pytest?
+- [ ] Is your code style correct (are you using PEP8, pylint)?
+
+<!--
+Thank you so much for your PR!  To help us review your contribution, please
+consider the following points:
+
+- Read contributing guidelines carefully before submitting the PR. It is available
+  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+
+- Read and abide by the Code of Conduct. It is available at  
+  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
+
+- Do not create the PR out of master, but out of a separate branch.
+
+- The PR title should summarize the changes, for example "Add new group argument for the
+  pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
+  request addresses an issue, please use the pull request title to describe 
+  the issue and mention the issue number in the pull request description.
+
+- The description should provide at least 1-2 sentences describing the pull request
+  in detail (Why is this change required?  What problem does it solve?) and
+  link to any relevant issues. If modifying a plot, render your plot to inspect for changes 
+  and copy image in the pull request message on Github
+
+- Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
+  progress). WIPs may be useful to (1) indicate you are working on something to avoid 
+  duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
+  
+- If you are contributing fixes to docstrings, please pay attention to
+  https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
+  In particular, note the difference between using single backquotes, double backquotes, and
+  asterisks in the markup.
+
+We understand that PRs can sometimes be overwhelming, especially as the
+reviews start coming in.  Please let us know if the reviews are unclear or
+the recommended next step seems overly demanding, if you would like help in
+addressing a reviewer's comments, or if you have been waiting too long to hear
+back on your PR.
+-->
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
new file mode 100644
index 0000000000..d4839efaed
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -0,0 +1,50 @@
+## Description
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] This PR is following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below).
+- [ ] Documentation is [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant.
+
+
+
+<!--
+Thank you so much for your PR!  To help us review your contribution, please
+consider the following points:
+
+- Read contributing guidelines carefully before submitting the PR. It is available
+  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+
+- Read and abide by the Code of Conduct. It is available at  
+  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
+
+- Do not create the PR out of master, but out of a separate branch.
+
+- The PR title should summarize the changes, for example "Add new group argument for the
+  pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
+  request addresses an issue, please use the pull request title to describe 
+  the issue and mention the issue number in the pull request description.
+
+- The description should provide at least 1-2 sentences describing the pull request
+  in detail (Why is this change required?  What problem does it solve?) and
+  link to any relevant issues. If modifying a plot, render your plot to inspect for changes 
+  and copy image in the pull request message on Github
+
+- Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
+  progress). WIPs may be useful to (1) indicate you are working on something to avoid 
+  duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
+  
+- If you are contributing fixes to docstrings, please pay attention to
+  https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
+  In particular, note the difference between using single backquotes, double backquotes, and
+  asterisks in the markup.
+
+We understand that PRs can sometimes be overwhelming, especially as the
+reviews start coming in.  Please let us know if the reviews are unclear or
+the recommended next step seems overly demanding, if you would like help in
+addressing a reviewer's comments, or if you have been waiting too long to hear
+back on your PR.
+-->
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
new file mode 100644
index 0000000000..119510b58e
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -0,0 +1,57 @@
+## Description
+<!-- Describe the need of new functionality in detail -->
+
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below)?
+- [ ] Included a sample plot to visually illustrate your changes?
+- [ ] Do all of your functions and methods have docstrings?
+- [ ] Have you added/updated unit tests where appropriate( using [pytest fixture pattern](
+      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Have you run the unit tests using pytest?
+- [ ] Is your code style correct (are you using PEP8, pylint)?
+- [ ] Have you added the documentation for your new feature/functionality?
+
+
+<!--
+Thank you so much for your PR!  To help us review your contribution, please
+consider the following points:
+
+- Read contributing guidelines carefully before submitting the PR. It is available
+  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+
+- Read and abide by the Code of Conduct. It is available at  
+  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
+
+- Do not create the PR out of master, but out of a separate branch.
+
+- The PR title should summarize the changes, for example "Add new group argument for the
+  pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
+  request addresses an issue, please use the pull request title to describe 
+  the issue and mention the issue number in the pull request description.
+
+- The description should provide at least 1-2 sentences describing the pull request
+  in detail (Why is this change required?  What problem does it solve?) and
+  link to any relevant issues. If modifying a plot, render your plot to inspect for changes 
+  and copy image in the pull request message on Github
+
+- Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
+  progress). WIPs may be useful to (1) indicate you are working on something to avoid 
+  duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
+  
+- If you are contributing fixes to docstrings, please pay attention to
+  https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
+  In particular, note the difference between using single backquotes, double backquotes, and
+  asterisks in the markup.
+
+We understand that PRs can sometimes be overwhelming, especially as the
+reviews start coming in.  Please let us know if the reviews are unclear or
+the recommended next step seems overly demanding, if you would like help in
+addressing a reviewer's comments, or if you have been waiting too long to hear
+back on your PR.
+-->

From 3450af3846f8928285cbd1e1a609ea8042bfdeed Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Fri, 17 Jan 2020 19:03:09 +0530
Subject: [PATCH 03/12] changed the templates

---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md      | 46 +++++++----------
 .../PULL_REQUEST_TEMPLATE/documentation.md    | 39 +++++++--------
 .github/PULL_REQUEST_TEMPLATE/new-feature.md  | 50 +++++++++----------
 3 files changed, 59 insertions(+), 76 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index ba05ca87c2..a36401edf7 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -1,31 +1,8 @@
 ## Description
-<!-- Briefly describe the bug you are trying to fix -->
-
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
-
-## Checklist
-<!-- Feel free to remove check-list items aren't relevant to your change -->
-
-- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below)?
-- [ ] Have you added the unit tests to prevent issue reoccurance( using [pytest fixture pattern](
-      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Have you run the unit tests using pytest?
-- [ ] Is your code style correct (are you using PEP8, pylint)?
-
 <!--
 Thank you so much for your PR!  To help us review your contribution, please
 consider the following points:
 
-- Read contributing guidelines carefully before submitting the PR. It is available
-  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
-
-- Read and abide by the Code of Conduct. It is available at  
-  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
-
-- Do not create the PR out of master, but out of a separate branch.
-
 - The PR title should summarize the changes, for example "Add new group argument for the
   pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
   request addresses an issue, please use the pull request title to describe 
@@ -39,11 +16,24 @@ consider the following points:
 - Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
   progress). WIPs may be useful to (1) indicate you are working on something to avoid 
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
-  
-- If you are contributing fixes to docstrings, please pay attention to
-  https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
-  In particular, note the difference between using single backquotes, double backquotes, and
-  asterisks in the markup.
+-->
+<!-- Briefly describe the bug you are trying to fix -->
+
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below)?
+- [ ] Has added unit tests to prevent issue recurrence( using [pytest fixture pattern](
+      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Is code style correct (are you using pylint, black)?
+
+<!--
+Also, read the contributing guidelines carefully before submitting the PR. It is available 
+at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
 
 We understand that PRs can sometimes be overwhelming, especially as the
 reviews start coming in.  Please let us know if the reviews are unclear or
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index d4839efaed..04ce3c64be 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -1,28 +1,8 @@
 ## Description
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
-
-## Checklist
-<!-- Feel free to remove check-list items aren't relevant to your change -->
-
-- [ ] This PR is following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below).
-- [ ] Documentation is [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant.
-
-
-
 <!--
 Thank you so much for your PR!  To help us review your contribution, please
 consider the following points:
 
-- Read contributing guidelines carefully before submitting the PR. It is available
-  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
-
-- Read and abide by the Code of Conduct. It is available at  
-  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
-
-- Do not create the PR out of master, but out of a separate branch.
-
 - The PR title should summarize the changes, for example "Add new group argument for the
   pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
   request addresses an issue, please use the pull request title to describe 
@@ -36,7 +16,24 @@ consider the following points:
 - Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
   progress). WIPs may be useful to (1) indicate you are working on something to avoid 
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
-  
+-->
+
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] This PR is following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below).
+- [ ] Documentation is [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant.
+
+<!--
+Keep in mind the following points:
+
+- Read contributing guidelines carefully before submitting the PR. It is available
+  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
   In particular, note the difference between using single backquotes, double backquotes, and
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index 119510b58e..e28179923b 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -1,35 +1,8 @@
 ## Description
-<!-- Describe the need of new functionality in detail -->
-
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
-
-## Checklist
-<!-- Feel free to remove check-list items aren't relevant to your change -->
-
-- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below)?
-- [ ] Included a sample plot to visually illustrate your changes?
-- [ ] Do all of your functions and methods have docstrings?
-- [ ] Have you added/updated unit tests where appropriate( using [pytest fixture pattern](
-      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Have you run the unit tests using pytest?
-- [ ] Is your code style correct (are you using PEP8, pylint)?
-- [ ] Have you added the documentation for your new feature/functionality?
-
-
 <!--
 Thank you so much for your PR!  To help us review your contribution, please
 consider the following points:
 
-- Read contributing guidelines carefully before submitting the PR. It is available
-  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
-
-- Read and abide by the Code of Conduct. It is available at  
-  https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
-
-- Do not create the PR out of master, but out of a separate branch.
-
 - The PR title should summarize the changes, for example "Add new group argument for the
   pair plot".  Avoid non-descriptive titles such as "Addresses issue #348". If your pull 
   request addresses an issue, please use the pull request title to describe 
@@ -43,6 +16,29 @@ consider the following points:
 - Please prefix the title of incomplete contributions with [WIP] (to indicate a work in 
   progress). WIPs may be useful to (1) indicate you are working on something to avoid 
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
+-->
+<!-- Describe the need of new functionality in detail -->
+
+<!-- Describe your changes in detail -->
+<!-- If it fixes an open issue, please link to the issue here. -->
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format (described below)?
+- [ ] Included a sample plot to visually illustrate your changes?
+- [ ] Do all the added functions and methods have docstrings?
+- [ ] Has added/updated unit tests where appropriate( using [pytest fixture pattern](
+      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Is code style correct (are you using pylint, black)?
+- [ ] Has added documentation for new feature/functionality?
+
+<!--
+Keep in mind the following points:
+
+- Read contributing guidelines carefully before submitting the PR. It is available
+  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
   
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.

From 2a8a020e98b803a2a723405442cc5dea9f99a21c Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Fri, 17 Jan 2020 22:23:49 +0530
Subject: [PATCH 04/12] final changes in the template

---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md       | 13 +++++--------
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 12 ++++--------
 .github/PULL_REQUEST_TEMPLATE/new-feature.md   | 15 +++++----------
 3 files changed, 14 insertions(+), 26 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index a36401edf7..ec5fd21e66 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -17,23 +17,20 @@ consider the following points:
   progress). WIPs may be useful to (1) indicate you are working on something to avoid 
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
 -->
-<!-- Briefly describe the bug you are trying to fix -->
 
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
 
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below)?
+- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format?
 - [ ] Has added unit tests to prevent issue recurrence( using [pytest fixture pattern](
       (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (are you using pylint, black)?
+- [ ] Is code style correct (follows pylint, black guidelines?
 
 <!--
-Also, read the contributing guidelines carefully before submitting the PR. It is available 
-at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. It is available at 
+https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
 
 We understand that PRs can sometimes be overwhelming, especially as the
 reviews start coming in.  Please let us know if the reviews are unclear or
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index 04ce3c64be..f8a2b4a376 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -18,21 +18,17 @@ consider the following points:
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
 -->
 
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
-
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] This PR is following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format (described below).
 - [ ] Documentation is [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant.
 
 <!--
-Keep in mind the following points:
-
-- Read contributing guidelines carefully before submitting the PR. It is available
-  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. 
+It is available at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
 
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index e28179923b..10ce591596 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -17,28 +17,23 @@ consider the following points:
   progress). WIPs may be useful to (1) indicate you are working on something to avoid 
   duplicated work, (2) request broad review of functionality or API, or (3) seek collaborators.
 -->
-<!-- Describe the need of new functionality in detail -->
 
-<!-- Describe your changes in detail -->
-<!-- If it fixes an open issue, please link to the issue here. -->
 
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Is this PR following the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below)?
+- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format?
 - [ ] Included a sample plot to visually illustrate your changes?
 - [ ] Do all the added functions and methods have docstrings?
 - [ ] Has added/updated unit tests where appropriate( using [pytest fixture pattern](
       (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (are you using pylint, black)?
+- [ ] Is code style correct (follows pylint, black guidelines)?
 - [ ] Has added documentation for new feature/functionality?
 
 <!--
-Keep in mind the following points:
-
-- Read contributing guidelines carefully before submitting the PR. It is available
-  at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md.
+Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. It is available at 
+https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
   
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.

From cafe55c7451410c7afe8daf0744c304bbcf756c7 Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Sat, 18 Jan 2020 03:32:51 +0530
Subject: [PATCH 05/12] final changes to the PR template

---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md       | 13 +++++++------
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 12 ++++++------
 .github/PULL_REQUEST_TEMPLATE/new-feature.md   | 18 +++++++++---------
 3 files changed, 22 insertions(+), 21 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index ec5fd21e66..5e37eb045a 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -22,15 +22,16 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+- [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
-- [ ] Has added unit tests to prevent issue recurrence( using [pytest fixture pattern](
-      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (follows pylint, black guidelines?
+- [ ] Does the PR include new or updated tests to prevent issue recurrence (using [pytest fixture pattern](
+      https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Is code style correct (follows pylint and black guidelines)?
 
 <!--
-Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. It is available at 
-https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
+Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
 
 We understand that PRs can sometimes be overwhelming, especially as the
 reviews start coming in.  Please let us know if the reviews are unclear or
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index f8a2b4a376..5c97ca62df 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -21,14 +21,14 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
-      PR format (described below).
-- [ ] Documentation is [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant.
+- [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+      PR format?
+- [ ] Is the documentation [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant?
 
 <!--
-Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. 
-It is available at https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
-https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
+Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
 
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index 10ce591596..fbcd2ebd4e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -22,18 +22,18 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does this PR follow the [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
+- [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
-- [ ] Included a sample plot to visually illustrate your changes?
-- [ ] Do all the added functions and methods have docstrings?
-- [ ] Has added/updated unit tests where appropriate( using [pytest fixture pattern](
-      (https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (follows pylint, black guidelines)?
-- [ ] Has added documentation for new feature/functionality?
+- [ ] Included a sample plot to visually illustrate your changes? (only for plot-related functions)
+- [ ] Is the new feature properly documented with an example?
+- [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
+      https://docs.pytest.org/en/latest/fixture.html#fixture))?
+- [ ] Is code style correct (follows pylint and black guidelines)?
 
 <!--
-Also, please consider reading the contributing guidelines and code of conduct  carefully before submitting the PR. It is available at 
-https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md.
+Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
   
 - If you are contributing fixes to docstrings, please pay attention to
   https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#docstring-formatting.

From 1f19cbc99f6da982d25cf4865a9da708701493d2 Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Sat, 18 Jan 2020 04:41:57 +0530
Subject: [PATCH 06/12] added the changelog check to PR template

---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md       | 5 +++--
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 3 ++-
 .github/PULL_REQUEST_TEMPLATE/new-feature.md   | 7 ++++---
 3 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index 5e37eb045a..d2be6f04e4 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -26,11 +26,12 @@ consider the following points:
       PR format?
 - [ ] Does the PR include new or updated tests to prevent issue recurrence (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (follows pylint and black guidelines)?
+- [ ] Is your code style correct (follows pylint and black guidelines)?
+- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
-- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md
 - https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
 
 We understand that PRs can sometimes be overwhelming, especially as the
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index 5c97ca62df..814b5b048e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -24,10 +24,11 @@ consider the following points:
 - [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
 - [ ] Is the documentation [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant?
+- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
-- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md
 - https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
 
 - If you are contributing fixes to docstrings, please pay attention to
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index fbcd2ebd4e..3de2ef5ae5 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -24,15 +24,16 @@ consider the following points:
 
 - [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
-- [ ] Included a sample plot to visually illustrate your changes? (only for plot-related functions)
+- [ ] Has included a sample plot to visually illustrate the changes? (only for plot-related functions)
 - [ ] Is the new feature properly documented with an example?
 - [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
-- [ ] Is code style correct (follows pylint and black guidelines)?
+- [ ] Is your code style correct (follows pylint and black guidelines)?
+- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
-- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md and 
+- https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md
 - https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md
   
 - If you are contributing fixes to docstrings, please pay attention to

From 66d08447e0f6747a655a7169096fc9c3771f161b Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Sun, 19 Jan 2020 02:49:08 +0530
Subject: [PATCH 07/12] modified changelog check

---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md       | 3 ++-
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 3 ++-
 .github/PULL_REQUEST_TEMPLATE/new-feature.md   | 3 ++-
 3 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index d2be6f04e4..7cb97c4527 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -27,7 +27,8 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to prevent issue recurrence (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
+- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+      section of the changelog?
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index 814b5b048e..97f453838e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -24,7 +24,8 @@ consider the following points:
 - [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
 - [ ] Is the documentation [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant?
-- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
+- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+      section of the changelog?
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index 3de2ef5ae5..dd72886c82 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -29,7 +29,8 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Added the change in [change log](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md) in correct format.
+- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+      section of the changelog?
 
 <!--
 Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at 

From 68a3f891b37baac74a1cb39647d7b8efc5c71565 Mon Sep 17 00:00:00 2001
From: percygautam <gautampiyus@gmail.com>
Date: Mon, 20 Jan 2020 03:32:05 +0530
Subject: [PATCH 08/12] Minor changes

---
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 2 +-
 .github/PULL_REQUEST_TEMPLATE/new-feature.md   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index 97f453838e..e60f3332b9 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -24,7 +24,7 @@ consider the following points:
 - [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
 - [ ] Is the documentation [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant?
-- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+- [ ] Is fix listed in the [Documentation](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#documentation) 
       section of the changelog?
 
 <!--
diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index dd72886c82..1f6bb9003a 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -29,7 +29,7 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+- [ ] Is fix listed in the [New features](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#new-features) 
       section of the changelog?
 
 <!--

From 08f7c942b88cf25e5df0b2a26061bc4afb7d552e Mon Sep 17 00:00:00 2001
From: Osvaldo Martin <aloctavodia@gmail.com>
Date: Wed, 22 Jan 2020 10:34:50 -0300
Subject: [PATCH 09/12] Update bug-fix.md

minor fix
---
 .github/PULL_REQUEST_TEMPLATE/bug-fix.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
index 7cb97c4527..4816c08216 100644
--- a/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
+++ b/.github/PULL_REQUEST_TEMPLATE/bug-fix.md
@@ -27,7 +27,7 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to prevent issue recurrence (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Is fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
+- [ ] Is the fix listed in the [Maintenance and fixes](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#maintenance-and-fixes) 
       section of the changelog?
 
 <!--

From c214e1ce26d7402c8825c7fbb4c24e9e15a5b9ee Mon Sep 17 00:00:00 2001
From: Osvaldo Martin <aloctavodia@gmail.com>
Date: Wed, 22 Jan 2020 10:35:25 -0300
Subject: [PATCH 10/12] Update documentation.md

minor fix
---
 .github/PULL_REQUEST_TEMPLATE/documentation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/documentation.md b/.github/PULL_REQUEST_TEMPLATE/documentation.md
index e60f3332b9..a37bea1044 100644
--- a/.github/PULL_REQUEST_TEMPLATE/documentation.md
+++ b/.github/PULL_REQUEST_TEMPLATE/documentation.md
@@ -24,7 +24,7 @@ consider the following points:
 - [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md#pull-request-checklist) 
       PR format?
 - [ ] Is the documentation [numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html) compliant?
-- [ ] Is fix listed in the [Documentation](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#documentation) 
+- [ ] Is the fix listed in the [Documentation](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#documentation) 
       section of the changelog?
 
 <!--

From 281cd214c1a166a886d3e85e3fb1da4d54be002c Mon Sep 17 00:00:00 2001
From: Osvaldo Martin <aloctavodia@gmail.com>
Date: Wed, 22 Jan 2020 10:35:53 -0300
Subject: [PATCH 11/12] Update new-feature.md

---
 .github/PULL_REQUEST_TEMPLATE/new-feature.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index 1f6bb9003a..c76015587e 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -29,7 +29,7 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Is fix listed in the [New features](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#new-features) 
+- [ ] Is the fix listed in the [New features](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#new-features) 
       section of the changelog?
 
 <!--

From cc4cc6f8b454ae6a00e8a70ca25043a012b5f10b Mon Sep 17 00:00:00 2001
From: Osvaldo Martin <aloctavodia@gmail.com>
Date: Wed, 22 Jan 2020 10:36:43 -0300
Subject: [PATCH 12/12] Update new-feature.md

---
 .github/PULL_REQUEST_TEMPLATE/new-feature.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE/new-feature.md b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
index c76015587e..1bd7eb53ad 100644
--- a/.github/PULL_REQUEST_TEMPLATE/new-feature.md
+++ b/.github/PULL_REQUEST_TEMPLATE/new-feature.md
@@ -29,7 +29,7 @@ consider the following points:
 - [ ] Does the PR include new or updated tests to cover the new feature (using [pytest fixture pattern](
       https://docs.pytest.org/en/latest/fixture.html#fixture))?
 - [ ] Is your code style correct (follows pylint and black guidelines)?
-- [ ] Is the fix listed in the [New features](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#new-features) 
+- [ ] Is the new feature listed in the [New features](https://github.com/arviz-devs/arviz/blob/master/CHANGELOG.md#new-features) 
       section of the changelog?
 
 <!--