docs: polish github templates

- information for submitter are now comments
- removed redundancy in titles, we use labels now
- typos corrections

Author: woile

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,30 +1,38 @@
 ---
 name: 🛠 Bug report
 about: Create a report to help us improve
-title: "[Bug Report] Good bug title tells us about precise symptom, not about the root cause."
+title: "Good bug title tells us about precise symptom, not about the root cause."
 labels: "bug"
 assignees: ""
 ---
 
 ## Description
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
-## commitizen version
-x.y.z
-
-## Steps to Reproduce
-Steps to reproduce the behavior:
+## Steps to reproduce
+<!-- Steps to reproduce the behavior:
 1. Run ...
 2. ...
-3. ...
+3. ... -->
+
+## Current behavior
+<!-- What happens actually so you think this is a bug. -->
 
-## Expected Behavior
+## Desired behavior
+<!--
 A clear and concise description of what you expected to happen.
 
 **Screenshots**
 If applicable, add screenshots to help explain your problem.
+-->
 
-## Actual Behavior
-What happens actually so you think this is a bug.
+## Environment
+<!--
+cz version
+python --version
+python3 -c "import platform; print(platform.system())"
+-->
 
-## More Information
+- commitizen version:
+- python version:
+- operating system:

.github/ISSUE_TEMPLATE/documentation.md

@@ -1,18 +1,19 @@
 ---
 name: 📖 Documentation
 about: Suggest an improvement for the documentation of this project
-title: "[Documentation] Content to be added or fixed"
+title: "Content to be added or fixed"
 labels: "documentation"
 assignees: ""
 ---
 
 ## Type
-* [ ] Conent inaccurate
+
+* [ ] Content inaccurate
 * [ ] Content missing
 * [ ] Typo
 
 ## URL
-URL to the code we did not clearly describe or the document page where the content is inaccurate
+<!-- URL to the code we did not clearly describe or the document page where the content is inaccurate -->
 
 ## Description
-A clear and concise description of what content should be added or fixed
+<!-- A clear and concise description of what content should be added or fixed -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,19 +1,19 @@
 ---
 name: 🚀 Feature request
 about: Suggest an idea for this project
-title: "[Feature Request] <One feature request per issue>"
-labels: ""
+title: "<One feature request per issue>"
+labels: "enhancement"
 assignees: ""
 ---
 
 ## Description
-A clear and concise description for us to know your idea.
+<!-- A clear and concise description for us to know your idea. -->
 
 ## Possible Solution
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what you want to happen. -->
 
 ## Additional context
-Add any other context or screenshots about the feature request here.
+<!-- Add any other context or screenshots about the feature request here. -->
 
 ## Related Issue
-If applicable, add link to existing issue also help us know better.
+<!-- If applicable, add link to existing issue also help us know better. -->

.github/pull_request_template.md

@@ -1,35 +1,45 @@
-(Thanks for sending a pull request! Please fill in the following content to let us know better about this change.)
+<!--
+Thanks for sending a pull request!
+Please fill in the following content to let us know better about this change.
+-->
 
 ## Types of changes
-Please put an `x` in the box that applies
 
-- [ ] **Bugfix**
+<!-- Please put an `x` in the box that applies -->
+
+- [ ] **Bug fix**
 - [ ] **New feature**
 - [ ] **Refactoring**
 - [ ] **Breaking change** (any change that would cause existing functionality to not work as expected)
-- [ ] **Documentation Update**
+- [ ] **Documentation update**
 - [ ] **Other (please describe)**
 
 ## Description
-**Describe what the change is**
 
-## Checklist:
+<!-- Describe what the change is -->
+
+## Checklist
+
 - [ ] Add test cases to all the changes you introduce
 - [ ] Run `./script/format` and `./script/test` locally to ensure this change passes linter check and test
 - [ ] Test the changes on the local machine manually
 - [ ] Update the documentation for the changes
 
 ## Steps to Test This Pull Request
-Steps to reproduce the behavior:
+
+<!-- Steps to reproduce the behavior:
 1. ...
 2. ...
-3. ...
+3. ... -->
 
 ## Expected behavior
-A clear and concise description of what you expected to happen
+
+<!-- A clear and concise description of what you expected to happen -->
 
 ## Related Issue
-If applicable, reference to the issue related to this pull request.
+
+<!-- If applicable, reference to the issue related to this pull request. -->
 
 ## Additional context
-Add any other context or screenshots about the pull request here.
+
+<!-- Add any other context or screenshots about the pull request here. -->