ISSUE_TEMPLATE.md

   1 ## How to file an issue
   2
   3 If you encounter an issue with SmoothieWare, you are welcome to
   4 [submit an issue](https://github.com/Smoothieware/Smoothieware/issues)
   5
   6 Before you do that for the first time though please take a moment to read the
   7 following section *completely*. Thank you! :)
   8
   9 ### What should I do before submitting an issue?
  10
  11 1. **this is not the right issue tracker if you are running a
  12    forked version of Smoothieware**. Seek help for such unofficial versions from
  13    the people maintaining them instead.
  14
  15 2. Please make sure to **test out the current edge version** of Smoothieware to see
  16    whether the problem you are encountering still exists, and **test with a clean config**.
  17
  18 3. The problem still exists? Then please look through the
  19    [existing tickets](https://github.com/Smoothieware/Smoothieware/issues?state=open)
  20    to check if there already exists a report of the issue you are encountering.
  21
  22    **Very important:** Please make absolutely sure that if you find a bug that looks like
  23    it is the same as your's, it actually behaves the same as your's. E.g. if someone gives steps
  24    to reproduce his bug that looks like your's, reproduce the bug like that if possible,
  25    and only add a "me too" if you actually can reproduce the same
  26    issue. Also **provide all information** as [described below](#what-should-i-include-in-a-bug-report)
  27    and whatever was additionally requested over the course of the ticket
  28    even if you "only" add to an existing ticket. The more information available regarding a bug, the higher
  29    the chances of reproducing and solving it. But "me too" on an actually unrelated ticket
  30    makes it more difficult due to on top of having to figure out the original problem
  31    there's now also a [red herring](https://en.wikipedia.org/wiki/Red_herring) interfering - so please be
  32    very diligent here!
  33
  34 ### What should I include in a bug report?
  35
  36 Always use the following template (you can remove what's within `[...]`, that's
  37 only provided here as some additional information for you), **even if only adding a
  38 "me too" to an existing ticket**:
  39
  40 #### What were you doing?
  41
  42     [Please be as specific as possible here. The maintainers will need to reproduce
  43     your issue in order to fix it and that is not possible if they don't know
  44     what you did to get it to happen in the first place. If you encountered
  45     a problem with specific files of any sorts, make sure to also include a link to a file
  46     with which to reproduce the problem.]
  47
  48 #### What did you expect to happen?
  49
  50 #### What happened instead?
  51
  52 #### Branch & Commit or Version of Smoothieware
  53
  54     [Can be found with the version command. (@version in pronterface)]
  55
  56 #### Hardware model you are using (Make, and version)
  57
  58     [eg Smoothieboard 5X V1b, Azteeg X5 Mini V2, ... etc]
  59
  60 #### Host and Operating System running the Host
  61
  62     [eg Pronterface, Octoprint, linux x64]
  63
  64 #### Link to and console logs
  65
  66     [On gist.github.com or pastebin.com. Always include and never truncate.]
  67
  68 #### Link to running config and M503 results
  69
  70     [On gist.github.com or pastebin.com. Always include and never truncate.]
  71
  72 I have read the [Wiki](http://smoothieware.org) and Especially the [Trouble Shooting section](http://smoothieware.org/troubleshooting)...
  73
  74 Copy-paste this template **completely**. Do not skip any lines!
  75
  76 It might happen that you are asked to provide a more thorough crash log which you can find out how to do [here](http://smoothieware.org/mri-debugging
  77 )