From 05e14e2a18c9f0049c717a82031ee647e38724b4 Mon Sep 17 00:00:00 2001
From: Kagaya <kagaya85@outlook.com>
Date: Sat, 31 Jul 2021 14:23:57 +0800
Subject: [PATCH] ci: add pull request template (#1280)

---
 .github/pull_request_template.md | 38 ++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..d52564233
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,38 @@
+<!--
+🎉 Thanks for sending a pull request to Kratos! Here are some tips for you:
+
+1. If this is your first time contributing to Kratos, please read our contribution guide: https://go-kratos.dev/en/docs/community/contribution/
+2. Ensure you have added or ran the appropriate tests for your PR, such as using `go test ./...`
+3. If the PR is unfinished, you may need mark it as a WIP(Work In Progress) PR or draft PR
+4. Please use a conventional commits format title: `<type>[optional scope]: <description>`
+    
+    Some suggestion on <type>:
+
+    fix: A bug fix
+    feat: A new feature
+    deps: Changes external dependencies
+    break: Changes has break change
+
+    docs: Documentation only changes
+    refactor: A code change that neither fixes a bug nor adds a feature
+    style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
+    test: Adding missing tests or correcting existing tests
+    chore Daily work, examples, etc.
+    ci: Changes to our CI configuration files and scripts
+-->
+
+#### Description (what this PR does / why we need it):
+<!--
+* The description should include the motivation for this PR or contrast this with previous behavior
+-->
+
+
+#### Which issue(s) this PR fixes:
+<!--
+* Automatically closes linked issue when PR is merged.
+
+Usage: `fixes/resolves #<issue number>`, or `fixes/resolves (paste link of issue)`.
+-->
+fixes #
+
+#### Other special notes for reviewer: