Issue reporting guidelines

BEGIN HERE

*Search Existing issues & pull requests:

• Open and closed issues. *Determine weather or not a bug report has been dispatched. What is the status of the report? Are there any other bugs to be looked at? If so issue another bug report.
• Include the output of the git--version in addition to the Windows version as sometimes problems arise that are directly dependent on the physical hardware type of server being used. Notating the git/ Windows version is super important to resolving the issues at times. Likewise, please mention your usage of 32-bit Windows &/Or 32-bit Git on a 64-bit Windows ectara. The more info the better. It's better to over do it than leave a lot of guess work! :)
• Detail the option choice(S) used when installing Git for Windows, console type/window (if any). The goal is excellent communication. Think of it like you're trying to explain your process to a child using clear, simple, precise notes to help us understand your method and findings. Prevents ha
• If your setup is different from "normal" setups in any way, it is a good idea to put specifics about that into your bug report, too.
• Describe your issue properly. If you spend 30 seconds throwing out a sloppy report, do expect that others will spend exactly the same amount on trying to resolve it. In contrast, if you write a complete and pleasantly informative bug report, you will almost certainly be rewarded by excellent help with your problem.
• Include a Minimal, Complete, and Verifiable example using GitHub Markdown's codeblock delimiters.
• If your issue stems from a particular repository include its URL. If the repository is proprietary try to create a public test repository showing the same issue.
• Be prepared to test fixes!
• Be polite. You are asking highly competent software developers for help, for free, so you might want to avoid treating them as if they were a commodity or at your free disposal.
• An example for an outstanding report can be found here. You may want to imitate the level of detail.
• For further inspiration, read reports that were resolved successfully, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, http://stackoverflow.com/questions/how-to-ask and http://whathaveyoutried.com/.