From 0f9313726cbecaa31e2e7e4ca9b52305aa46b14b Mon Sep 17 00:00:00 2001
From: Robert Zaremba <robert@zaremba.ch>
Date: Tue, 21 Jun 2022 23:14:07 +0200
Subject: [PATCH] chore: updated github templates (#1048)

---
 .github/ISSUE_TEMPLATE/feature-request.md | 18 ++----------------
 .github/PULL_REQUEST_TEMPLATE.md          | 20 ++++++++------------
 2 files changed, 10 insertions(+), 28 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md
index 1f4846f388..8f4ca4d5e9 100644
--- a/.github/ISSUE_TEMPLATE/feature-request.md
+++ b/.github/ISSUE_TEMPLATE/feature-request.md
@@ -3,34 +3,20 @@ name: Feature Request
 about: Create a proposal to request a feature
 ---
 
-<!--------------------------------------------------------------------------- ☺
-|       Thanks for opening an issue!
-|
-|       Before smashing the submit button please review the template.
-|       Word of caution, poorly thought-out proposals may be rejected 
-|       without deliberation.
-|
-|       Also, please also ensure that this is not a duplicate issue :)
-☺ ---------------------------------------------------------------------------->
-
 <!-- markdownlint-disable MD041 -->
 
 ## Summary
 
-<!-- Short, concise description of the proposed feature -->
-
 ## Problem Definition
 
-<!-- Why do we need this feature? 
+<!-- Why do we need this feature?
 What problems may be addressed by introducing this feature?
 What benefits does Tendermint stand to gain by including this feature?
 Are there any disadvantages of including this feature? -->
 
 ## Proposal
 
-<!-- Detailed description of requirements of implementation -->
-
-----
+---
 
 ## For Admin Use
 
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index c1f449aa0e..056ed7bed4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,24 +1,21 @@
-## Description
+<!-- markdownlint-disable MD041 -->
 
-<!--
-Add a description of the changes that this PR introduces and the files that
-are the most critical to review.
--->
+## Description
 
 closes: #XXXX
 
-----
+---
 
 ### Author Checklist
 
-*All items are required. Please add a note to the item if the item is not applicable and
-please add links to any relevant follow up issues.*
+_All items are required. Please add a note to the item if the item is not applicable and
+please add links to any relevant follow up issues._
 
 I have...
 
 - [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
-- [ ] added appropriate labels to the PR
 - [ ] added `!` to the type prefix if API or client breaking change
+- [ ] added appropriate labels to the PR
 - [ ] targeted the correct branch (see [PR Targeting](https://github.com/umee-network/umee/blob/main/CONTRIBUTING.md#pr-targeting))
 - [ ] provided a link to the relevant issue or specification
 - [ ] added a changelog entry to `CHANGELOG.md`
@@ -29,13 +26,12 @@ I have...
 
 ### Reviewers Checklist
 
-*All items are required. Please add a note if the item is not applicable and please add
-your handle next to the items reviewed if you only reviewed selected items.*
+_All items are required. Please add a note if the item is not applicable and please add
+your handle next to the items reviewed if you only reviewed selected items._
 
 I have...
 
 - [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
-- [ ] confirmed `!` in the type prefix if API or client breaking change
 - [ ] confirmed all author checklist items have been addressed
 - [ ] reviewed state machine logic
 - [ ] reviewed API design and naming