Jason Song 97aacc3ea1 Improve pull_request_template.md (#22888) ... Update `pull_request_template.md` because: - It's a kind idea to hide the tips. However, it's easier to include them in the commit message by mistake when you cannot see them. Check `git log | grep 'Please check the following:'`. So don't hide it, expose it and help fix it. - "for backports" is much clearer than "for bug fixes". I saw someone post a PR to a release branch because they believed it was the right way for a bugfix. - "Allow edits by maintainers", or we have to ask the contributor to update the branch and they could be confused. - Remind the contributor that the words could be included in the commit message, to avoid some words like "Hello", "Sorry". If they really need them, they can separate them with a line, like: ```markdown Close #xxxx Because ... Then ... Finally ... --- Hello, this is my first time opening a pull request. Sorry for any mistakes. ``` And the merger should be careful, check and delete the extra content before merging. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>		2023-02-20 19:14:02 -05:00
..
ISSUE_TEMPLATE	update discord invite (#19907)	2022-06-07 11:40:27 -04:00
FUNDING.yml	Kd/add bountysource (#14323)	2021-01-13 10:53:17 -05:00
lock.yml	Config lock bot (#13624)	2020-11-18 14:42:31 -05:00
pull_request_template.md	Improve pull_request_template.md (#22888)	2023-02-20 19:14:02 -05:00
stale.yml