chore: update templates

.github/ISSUE_TEMPLATE/3-Bug_report.md

@@ -11,9 +11,12 @@ about: You've found a bug with Renovate
 
 <!-- A clear and concise description of what the bug is. -->
 
-**Did you see anything helpful in debug logs?**
+**Relevant debug logs**
 
-<!-- If you're running self-hosted, run with `--log-level=debug` or LOG_LEVEL=debug and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created). The Job ID will help us locate it. -->
+<!--
+Try not to raise a bug report unless you've looked at the logs first.
+If you're running self-hosted, run with `--log-level=debug` or LOG_LEVEL=debug and search for whatever dependency/branch/PR that is causing the problem. If you are using the Renovate App, log into https://app.renovatebot.com/dashboard and locate the correct job log for when the problem occurred (e.g. when the PR was created). The Job ID will help us locate it.
+-->
 
 **To Reproduce**
 

.github/ISSUE_TEMPLATE/4-Feature_request.md

@@ -4,13 +4,15 @@ about: Suggest an idea for this project
 ---
 
 **What would you like Renovate to be able to do?**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what problem needs solving. Make sure you describe what you "really" are trying to achieve (the bigger picture) as that often helps. -->
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**Did you already have any implementation ideas?**
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+<!-- This is totally optional, but we know many people dig into the source code already before raising a request. Try to keep implementation ideas separate from *requirements* above -->
+
+**Are there any workarounds or alternative ideas you've tried to avoid needing this feature?**
+
+**Is this a feature you'd be interested in implementing yourself?**
+
+<!-- Again, totally optional. But let us know if you're interested and if you need any particular help -->

.github/pull_request_template.md

@@ -1,10 +1,9 @@
-<!--
-    Before submitting a Pull Request, please ensure you have signed the CLA using this GitHub App:
-    https://cla-assistant.io/renovateapp/renovate
+<!-- Before submitting a Pull Request, please ensure you have signed the CLA using this GitHub App: https://cla-assistant.io/renovatebot/renovate -->
 
-    Please ensure `Allow edits from maintainers.` checkbox is checked
--->
+<!-- When creating this PR on GitHub, please ensure `Allow edits from maintainers.` checkbox is checked -->
 
-<!-- Replace this text with a description of what this PR fixes or adds -->
+<!-- Please use a conventional commit message (https://www.conventionalcommits.org/en/v1.0.0/) as your PR title -->
 
-Closes # <!-- Ideally each PR should be closing an open issue -->
+<!-- Ideally include at least one sentence saying what this PR achieves -->
+
+<!-- Finish the PR with `Closes #` and then the issue number if it closes any associated issue -->