Tweaked Contributing guidelines, Issue and PR templates
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index b568bf6..2820e28 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -14,18 +14,19 @@
**Guidelines to report an issue or ask a question:**
- Please provide your imgui version number.
-- If you are discussing an assert or a crash, please provide a debugger callstack.
+- If you are discussing an assert or a crash, please provide a debugger callstack. Never state "it crashes" without additional information.
- Please state if you have made substantial modifications to your copy of imgui.
- When discussing issues related to rendering or inputs, please state the OS/back-end/renderer you are using. Please state if you are using a vanilla copy of one of the back-end (imgui_impl_xxx files), or a modified one, or if you built your own.
+- Try to be explicit with your expectations and what you have tried.
- Please provide a Minimal, Complete and Verifiable Example ([MCVE](https://stackoverflow.com/help/mcve)) to demonstrate your problem. An ideal submission includes a small piece of code that anyone can paste in one of the examples/ application (e.g. in main.cpp or imgui_demo.cpp) to understand and reproduce it. Narrowing your problem to its shortest and purest form is the easiest way to understand it. Please test your shortened code to ensure it actually exhibit the problem. Often while creating the MCVE you will end up solving the problem! Many questions that are missing a standalone verifiable example are missing the actual cause of their issue in the description, which ends up wasting everyone's time.
- Try to attach screenshots to clarify the context. They often convey useful information that are omitted by the description. You can drag pictures/files here (prefer github attachments over 3rd party hosting).
- When requesting a new feature, please describe the usage context (how you intend to use it, why you need it, etc.).
- Due to frequent abuse of this service from a certain category of users, if your GitHub account is anonymous and was created five minutes ago please understand that your post will receive more scrutiny and less patience for incomplete questions.
-If you have been using dear imgui for a while and/or have been using C/C++ for several years and/or have demonstrated good behavior here, it is ok to not fullfill every item to the letter. Those are guidelines and experienced users of dear imgui will know what information are useful in a given context.
+If you have been using dear imgui for a while or have been using C/C++ for several years or have demonstrated good behavior here, it is ok to not fullfill every item to the letter. Those are guidelines and experienced users of dear imgui will know what information are useful in a given context.
## How to create an Pull Request
-
-- If you are adding a feature, please describe the usage context (how you intend to use it, why you need it, etc.).
+- When adding a feature, please describe the usage context (how you intend to use it, why you need it, etc.).
+- When fixing a warning or compilation problem, please post the compiler log and specify the version and OS you are using.
- Try to attach screenshots to clarify the context and demonstrate the feature at a glance. You can drag pictures/files here (prefer github attachments over 3rd party hosting).
- Make sure you create a branch for the pull request. In Git, 1 PR is associated to 1 branch. If you keep pushing to the same branch after you submitted the PR, your new commits will appear in the PR (we can still cherry-pick individual commits).
diff --git a/.github/issue_template.md b/.github/issue_template.md
index 042a716..0bcd63b 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -13,9 +13,11 @@
XXX
-**Back-end file/Renderer/OS:** _(if the question is related to inputs/rendering/build, otherwise delete this section)_
+**Back-end file/Renderer/OS:** _(or specify if you are using a custom engine back-end)_
-XXX
+Back-ends: imgui_impl_XXX.cpp + imgui_impl_XXX.cpp
+OS: XXX
+Compiler: XXX _(if the question is related to building)_
**My Issue/Question:** _(please provide context)_
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 1a6418d..7b04314 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,4 +1,5 @@
-- If you are adding a feature, please explain the context of the change: what do you need the feature for?
+- When adding a feature, please describe the usage context (how you intend to use it, why you need it, etc.).
+- When fixing a warning or compilation problem, please post the compiler log and specify the version and OS you are using.
- Try to attach screenshots to clarify the context and demonstrate the feature at a glance.
- Make sure you create a branch for the pull request. In Git, 1 PR is associated to 1 branch. If you keep pushing to the same branch after you submitted the PR, your new commits will appear in the PR.
- You can read [CONTRIBUTING.md](https://github.com/ocornut/imgui/blob/master/.github/CONTRIBUTING.md) for more details.
