wagtail/.github/ISSUE_TEMPLATE.md

Found a bug? Please fill out the sections below. 👍

### Issue Summary

A summary of the issue.

### Steps to Reproduce

It's essential that you provide enough information for someone else to replicate the problem you're seeing. Simply describing something that's broken on your current project is not enough!

1. (for example) Start a new project with `wagtail start myproject`
2. Edit models.py as follows...
3. ...

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

### Technical details

* Python version: Run `python --version`.
* Django version: Look in your requirements.txt, or run `pip show django | grep Version`.
* Wagtail version: Hover over the Wagtail bird in the admin, or run `pip show wagtail | grep Version:`.
* Browser version: You can use http://www.whatsmybrowser.org/ to find this out.
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00			`Found a bug? Please fill out the sections below. 👍`

			`### Issue Summary`

			`A summary of the issue.`

			`### Steps to Reproduce`

Clarify "Steps to reproduce" in new issue template (#3610) Bug reporters are frequently not making the connection that "Steps to reproduce" means "steps for someone else to independently reproduce this bug", not "steps that I go through on my project to see this bug". Added some example text to gently steer people towards the level of detail we want... Also trimmed down the "Wagtail version" item under "Technical details", since we don't really need to tell people four different ways to do the same thing. (We don't want people to mentally tune this text out, so I think it's a good habit to remove something for every new thing we add) 2017-05-30 21:31:23 +02:00			`It's essential that you provide enough information for someone else to replicate the problem you're seeing. Simply describing something that's broken on your current project is not enough!`

			1. (for example) Start a new project with `wagtail start myproject`
			`2. Edit models.py as follows...`
			`3. ...`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
Updated with feedback from Tom 2016-09-08 14:38:00 +02:00			`Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
			`### Technical details`

Add hints for technical details in issue template (#2999) The more information we get, the easier it is for users to provide it, and the more accurate that information is, the better! 2016-09-15 11:11:36 +02:00			* Python version: Run `python --version`.
Clarify "Steps to reproduce" in new issue template (#3610) Bug reporters are frequently not making the connection that "Steps to reproduce" means "steps for someone else to independently reproduce this bug", not "steps that I go through on my project to see this bug". Added some example text to gently steer people towards the level of detail we want... Also trimmed down the "Wagtail version" item under "Technical details", since we don't really need to tell people four different ways to do the same thing. (We don't want people to mentally tune this text out, so I think it's a good habit to remove something for every new thing we add) 2017-05-30 21:31:23 +02:00			* Django version: Look in your requirements.txt, or run `pip show django \| grep Version`.
			* Wagtail version: Hover over the Wagtail bird in the admin, or run `pip show wagtail \| grep Version:`.
Add hints for technical details in issue template (#2999) The more information we get, the easier it is for users to provide it, and the more accurate that information is, the better! 2016-09-15 11:11:36 +02:00			`* Browser version: You can use http://www.whatsmybrowser.org/ to find this out.`