Merge remote-tracking branch 'tikv/master' into upgrade-to-near-7.6

.dockerignore

@@ -0,0 +1,39 @@
+# OSX leaves these everywhere on SMB shares
+._*
+
+# OSX trash
+.DS_Store
+
+# Eclipse files
+.classpath
+.project
+.settings/**
+
+# Vim swap files
+*.swp
+
+# Files generated by JetBrains IDEs, e.g. IntelliJ IDEA
+.idea/
+*.iml
+out/
+
+# Vscode files
+.vscode/**
+
+target
+dist
+tmp
+/bin
+
+# fuzzing hack, see fuzz/cli.rs
+fuzz-incremental/
+
+# cargo configuration. We presently use this to create custom cargo profiles
+# that should not be checked in at this location.
+.cargo/
+
+# Files generated by tikv-server
+/LOCK
+/db/
+/last_tikv.toml
+/raft/

.github/pull_request_template.md

@@ -1,10 +1,41 @@
-### What problem does this PR solve?
+<!--
+Thank you for contributing to TiKV!
 
-Issue Number: close #xxx
+If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.
 
-Problem Summary:
+If you're unsure about anything, just ask; somebody should be along to answer within a day or two.
+
+PR Title Format:
+1. module [, module2, module3]: what's changed
+2. *: what's changed
+-->
 
 ### What is changed and how it works?
+<!--
+Please create an issue first to describe the problem.
+
+There MUST be one line starting with "Issue Number:  " and 
+linking the relevant issues via the "close" or "ref".
+
+For more info, check https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md#linking-issues.
+-->
+
+Issue Number: Close #xxx
+
+<!--
+You could use "commit message" code block to add more description to the final commit message.
+For more info, check https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md#format-of-the-commit-message.
+-->
+What's Changed:
+
+```commit-message
+
+```
+
+### Related changes
+
+- [ ] PR to update `pingcap/docs`/`pingcap/docs-cn`:
+- [ ] Need to cherry-pick to the release branch
 
 ### Check List
 
@@ -21,18 +52,16 @@ Side effects
 - [ ] Performance regression: Consumes more Memory
 - [ ] Breaking backward compatibility
 
-Documentation
-
-- [ ] Affects user behaviors
-- [ ] Contains syntax changes
-- [ ] Contains variable changes
-- [ ] Contains experimental features
-- [ ] Changes MySQL compatibility
-
 ### Release note
+<!-- 
+Compatibility change, improvement, bugfix, and new feature need a release note.
+
+Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.
 
-<!-- bugfix or new feature needs a release note -->
+If you don't think this PR needs a release note then fill it with None.
+If this PR will be picked to release branch, then a release note is probably required.
+-->
 
 ```release-note
-None
+
 ```