From 1736b6530db47abf78ae835aa6fe80cfca1ad4f3 Mon Sep 17 00:00:00 2001 From: Zlatko Knezevic Date: Fri, 26 Feb 2016 15:22:33 -0800 Subject: [PATCH] Adding ISSUE_TEMPLATE Addin template for new issues. Also adding instructions for "clone, run, repro" that we want to be at. --- Documentation/issue-filing-guide.md | 12 ++++++++++++ ISSUE_TEMPLATE | 17 +++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 ISSUE_TEMPLATE diff --git a/Documentation/issue-filing-guide.md b/Documentation/issue-filing-guide.md index dff05d5af..4daf160d3 100644 --- a/Documentation/issue-filing-guide.md +++ b/Documentation/issue-filing-guide.md @@ -37,3 +37,15 @@ you would like to see, what scenario it covers and especially why the current tools cannot satisfy that scenario. Thanks and happy filing! :) + +## Providing the repro for bugs +For bugs, what we need more than anything is a good repro of the defective +behavior. We would like to go towards the "clone, run, repro" model. In short: + +1. If you find a bug, package up a repro in a git repo somewhere (GitHub is +usually a good place :)). +2. Inside the issue, specify what needs to be done (steps) to get an accurate +repro of the bug. Ideally, this should be "here is how to build, these are the +commands you run from the dotnet tools". +3. We use the above to get the repro, investigate and fix! + diff --git a/ISSUE_TEMPLATE b/ISSUE_TEMPLATE new file mode 100644 index 000000000..7b9e8923c --- /dev/null +++ b/ISSUE_TEMPLATE @@ -0,0 +1,17 @@ +## Expected behavior + + +## Actual behavior + + +## Steps to reproduce + + +## Environment data +`dotnet --version` output: + + + + + +