chore: Update pull request templates

Author: sethaxen

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+---
+name: "Pull request"
+about: "Open a pull request"
+title: "<type>: <title>"
+---
+
+## Description
+<!--
+Thank you so much for your PR! To help us review your contribution, please consider the following points:
+
+- The PR title should include one of the following Conventional Commits type specifier indicating the type of contribution:
+  + `feat`: new non-breaking feature ()
+  + `feat!`: new breaking feature
+  + `fix`: bug fix
+  + `docs`: changes to documentation
+  + `test`: changes to tests
+  + `refactor`: changes to code that leave functionality unchanged
+  + `chore`: miscellaneous changes to project
+
+- The PR title should summarize the changes, for example "feat: Add new group argument for the pair plot".
+  Avoid non-descriptive titles such as "Addresses issue #348".
+
+- The description should provide at least 1-2 sentences describing the pull request in detail and
+  link to any relevant issues.
+
+## Checklist
+<!-- Feel free to remove check-list items aren't relevant to your change -->
+
+- [ ] PR follows [official](https://github.com/arviz-devs/ArviZ.jl/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format
+- [ ] The new feature is properly documented with an example.
+- [ ] New or updated tests cover the new feature.
+- [ ] Code style is correct (formatted using JuliaFormatter with BlueStyle).
+- [ ] Changes are listed in the appropriate section of the [changelog](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#vv0xx-unreleased).
+- [ ] The patch version number been incremented if the change is non-breaking or the minor version number been incremented if the change is breaking.

.github/PULL_REQUEST_TEMPLATE/bug-fix.md

@@ -23,8 +23,8 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does the PR follow [official](https://github.com/arviz-devs/ArviZ.jl/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format?
-- [ ] Does the PR include new or updated tests to prevent issue recurrence?
-- [ ] Is the code style correct (formatted using JuliaFormatter with BlueStyle)?
-- [ ] Is the fix listed in the [Fixes](https://github.com/arviz-devs/PosteriorStats/blob/main/CHANGELOG.md#Fixes) section of the changelog?
-- [ ] Has the patch version number been incremented?
+- [ ] PR follows [official](https://github.com/arviz-devs/ArviZ.jl/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format.
+- [ ] The PR includes new or updated tests to prevent issue recurrence.
+- [ ] Code style is correct (formatted using JuliaFormatter with BlueStyle).
+- [ ] The fix is listed in the [Fixes](https://github.com/arviz-devs/PosteriorStats/blob/main/CHANGELOG.md#Fixes) section of the changelog.
+- [ ] The patch version number has been incremented.

.github/PULL_REQUEST_TEMPLATE/documentation.md

@@ -23,6 +23,5 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does the PR follow [official](https://github.com/arviz-devs/arviz/blob/main/CONTRIBUTING.md#pull-request-checklist)
-      PR format?
-- [ ] Is the new feature listed in the [Documentation](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#Documentation) section of the changelog?
+- [ ] PR follows [official](https://github.com/arviz-devs/arviz/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format.
+- [ ] The docs change is listed in the [Documentation](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#Documentation) section of the changelog.

.github/PULL_REQUEST_TEMPLATE/new-feature.md

@@ -23,9 +23,9 @@ consider the following points:
 ## Checklist
 <!-- Feel free to remove check-list items aren't relevant to your change -->
 
-- [ ] Does the PR follow [official](https://github.com/arviz-devs/ArviZ.jl/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format?
-- [ ] Is the new feature properly documented with an example?
-- [ ] Does the PR include new or updated tests to cover the new feature?
-- [ ] Is the code style correct (formatted using JuliaFormatter with BlueStyle)?
-- [ ] Is the new feature listed in the [Features](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#Features) section of the changelog if the change is non-breaking or the [BREAKING CHANGES](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#BREAKING-CHANGES) section if it is breaking?
-- [ ] Has the patch version number been incremented if the change is non-breaking or the minor version number been incremented if the change is breaking?
+- [ ] PR follows [official](https://github.com/arviz-devs/ArviZ.jl/blob/main/CONTRIBUTING.md#pull-request-checklist) PR format
+- [ ] The new feature is properly documented with an example.
+- [ ] New or updated tests cover the new feature.
+- [ ] Code style is correct (formatted using JuliaFormatter with BlueStyle).
+- [ ] The new feature is listed in the [Features](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#Features) section of the changelog if the change is non-breaking or the [BREAKING CHANGES](https://github.com/arviz-devs/PosteriorStats.jl/blob/main/CHANGELOG.md#BREAKING-CHANGES) section if it is breaking.
+- [ ] The patch version number been incremented if the change is non-breaking or the minor version number been incremented if the change is breaking.