diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-04-17 17:57:47 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-04-17 17:57:47 +0000 |
commit | 1d63948d79ca6f32889656692d6736c9127f2ee1 (patch) | |
tree | bb26a34d7c7b62ac30b0d4da15584efe3e2a754a /.github/ISSUE_TEMPLATE | |
parent | Releasing debian version 1.13.0-1. (diff) | |
download | netdata-1d63948d79ca6f32889656692d6736c9127f2ee1.tar.xz netdata-1d63948d79ca6f32889656692d6736c9127f2ee1.zip |
Merging upstream version 1.14.0~rc0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r-- | .github/ISSUE_TEMPLATE.md | 10 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 34 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/feature_request.md | 16 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/question.md | 25 |
4 files changed, 85 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..4fe94ad65 --- /dev/null +++ b/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,10 @@ +<!--- +This is a generic issue template. We usually prefer contributors to use one +of 3 other specific issue templates (bug report, feature request, question) +to allow our automation classify those so you can get response faster. +However if your issue doesn't fall into either one of those 3 categories +use this generic template. +---> + +#### Summary + diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 000000000..fbd69a2f6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,34 @@ +--- +name: Bug report +about: Create a bug report to help us improve + +--- + +<!--- +When creating a bug report please: +- Verify first that your issue is not already reported on GitHub +- Test if the latest release and master branch are affected too. +- Provide a clear and concise description of what the bug is in "Bug report + summary" section. +- Try to provide as much information about your environment (OS distribution, + running in container, etc.) as possible to allow us reproduce this bug faster. +- Write which component is affected. We group our components the same way our + code is structured so basically: + component name = dir in top level directory of repository +- Describe how you found this bug and how we can reproduce it. Preferable with + a minimal test-case scenario. You can paste gist.github.com links for larger + files +- Provide a clear and concise description of what you expected to happen. +--> + +##### Bug report summary + +##### OS / Environment + +##### Netdata version (ouput of `netdata -V`) + +##### Component Name + +##### Steps To Reproduce + +##### Expected behavior diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 000000000..b27ba2653 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,16 @@ +--- +name: Feature request +about: Suggest an idea for our project + +--- + +<!--- +When creating a feature request please: +- Verify first that your issue is not already reported on GitHub +- Explain new feature briefly in "Feature idea summary" section +- Provide a clear and concise description of what you expect to happen. +---> + +##### Feature idea summary + +##### Expected behavior diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md new file mode 100644 index 000000000..9bdf6f14e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/question.md @@ -0,0 +1,25 @@ +--- +name: Question +about: You just want to ask a question? Go on. +--- + +<!--- +When asking a new question please: +- Verify first that your question wasn't asked before on GitHub. + HINT: Use label "question" when searching for such issues. +- Briefly explain what is the problem you are having +- Try to provide as much information about your environment (OS distribution, + running in container, etc.) as possible to allow us reproduce this bug faster. +- Write which component is affected. We group our components the same way our + code is structured so basically: + component name = dir in top level directory of repository +- Provide a clear and concise description of what you expected to happen. +--> + +##### Question summary + +##### OS / Environment + +##### Component Name + +##### Expected results |