From c5c97d27a942ce14c1d86de2490a3ff1c25a85dc Mon Sep 17 00:00:00 2001
From: Robert Zaremba <robert@zaremba.ch>
Date: Mon, 25 Nov 2024 22:48:20 +0100
Subject: [PATCH] chore: update github setup

---
 .github/ISSUE_TEMPLATE/feature-request.md | 15 ++++++++++-----
 .github/PULL_REQUEST_TEMPLATE.md          | 13 ++++++++++++-
 Makefile                                  |  4 ++--
 3 files changed, 24 insertions(+), 8 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md
index 8f4ca4d..5eceaa4 100644
--- a/.github/ISSUE_TEMPLATE/feature-request.md
+++ b/.github/ISSUE_TEMPLATE/feature-request.md
@@ -7,15 +7,20 @@ about: Create a proposal to request a feature
 
 ## Summary
 
-## Problem Definition
 
-<!-- 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? -->
+
+## Context
+
+#### Why do we need this feature? What problems may be addressed by introducing this feature?
+
+#### What are the benefits by including this feature?
+
+#### Are there any disadvantages of including this feature?
 
 ## Proposal
 
+
+
 ---
 
 ## For Admin Use
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 2df542e..ea5064c 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -2,7 +2,7 @@
 
 ## Description
 
-closes: #XXXX
+Closes: #XXXX
 
 ---
 
@@ -14,6 +14,17 @@ 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
+    <!-- * `feat`: A new feature
+    * `fix`: A bug fix
+    * `docs`: Documentation only changes
+    * `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+    * `refactor`: A code change that neither fixes a bug nor adds a feature
+    * `perf`: A code change that improves performance
+    * `test`: Adding missing tests or correcting existing tests
+    * `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+    * `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+    * `chore`: Other changes that don't modify src or test files
+    * `revert`: Reverts a previous commit -->
 - [ ] 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))
diff --git a/Makefile b/Makefile
index de44472..3290a50 100644
--- a/Makefile
+++ b/Makefile
@@ -11,7 +11,7 @@ out:
 build: out .git/hooks/pre-commit
 	go build -o ./out ./cmd/*
 
-run:
+start:
 	@if [ ! -f .env ]; then echo "Create .env file by copying and updating .env.example"; exit 1; fi
 	@./out/native-ika start --block 8713586
 
@@ -39,7 +39,7 @@ lint-fix-go-all:
 	@gofmt -w -s -l .
 
 
-.PHONY: build run clean setup
+.PHONY: build start clean setup
 .PHONY: lint lint-all lint-fix-all lint-fix-go-all
 
 ###############################################################################