react-navigation/.github/ISSUE_TEMPLATE.md

## The issue list is reserved for bugs and feature requests, not for questions.

For usage questions, try to:

- [Read the docs](https://reactnavigation.org/)
- [Ask on the Reactiflux (#react-navigation)](https://discord.gg/reactiflux)
- [Look for / ask questions on StackOverflow](https://stackoverflow.com/questions/tagged/react-navigation)
- Search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue.

---

### Current Behavior
- _If describing a bug, tell us what happens. Please provide a repository with code and steps to reproduce the bug. **Not providing code that other people can run makes is significantly harder to fix your bug.** Provide a screenshot when possible_
- _If suggesting a change/improvement, explain the difference from current behavior_

### Expected Behavior
- _If you're describing a bug, tell us what should happen_
- _If you're suggesting a change/improvement, tell us how it should work_

### Your Environment

| software         | version
| ---------------- | -------
| react-navigation |
| react-native     |
| node             |
| npm or yarn      |
Update ISSUE_TEMPLATE.md (#2668) the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to: 1 . emphasise how important it is to include a runnable reproduction 2 . cut down on some extra words at the beginning of the template so it's more to the point 2017-09-29 22:51:06 +02:00			`## The issue list is reserved for bugs and feature requests, not for questions.`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00
Update ISSUE_TEMPLATE.md (#2668) the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to: 1 . emphasise how important it is to include a runnable reproduction 2 . cut down on some extra words at the beginning of the template so it's more to the point 2017-09-29 22:51:06 +02:00			`For usage questions, try to:`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00
			`- [Read the docs](https://reactnavigation.org/)`
			`- [Ask on the Reactiflux (#react-navigation)](https://discord.gg/reactiflux)`
			`- [Look for / ask questions on StackOverflow](https://stackoverflow.com/questions/tagged/react-navigation)`
Update ISSUE_TEMPLATE.md (#2668) the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to: 1 . emphasise how important it is to include a runnable reproduction 2 . cut down on some extra words at the beginning of the template so it's more to the point 2017-09-29 22:51:06 +02:00			`- Search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue.`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00
			`---`
Add issue template (#1199) * Add issue template * Ask for screenshot * Update ISSUE_TEMPLATE.md 2017-04-24 19:40:43 +02:00
			`### Current Behavior`
Update ISSUE_TEMPLATE.md (#2668) the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to: 1 . emphasise how important it is to include a runnable reproduction 2 . cut down on some extra words at the beginning of the template so it's more to the point 2017-09-29 22:51:06 +02:00			`- _If describing a bug, tell us what happens. Please provide a repository with code and steps to reproduce the bug. Not providing code that other people can run makes is significantly harder to fix your bug. Provide a screenshot when possible_`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00			`- _If suggesting a change/improvement, explain the difference from current behavior_`
Add issue template (#1199) * Add issue template * Ask for screenshot * Update ISSUE_TEMPLATE.md 2017-04-24 19:40:43 +02:00
			`### Expected Behavior`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00			`- _If you're describing a bug, tell us what should happen_`
			`- _If you're suggesting a change/improvement, tell us how it should work_`
Add issue template (#1199) * Add issue template * Ask for screenshot * Update ISSUE_TEMPLATE.md 2017-04-24 19:40:43 +02:00
			`### Your Environment`

			`\| software \| version`
			`\| ---------------- \| -------`
Add additional guidance information to the GitHub issue template. (#2428) * Add additional guidance information to the GitHub issue template. - Provides links to best places to ask usage questions. - Uncomments guiding information in issue template that wasn't visible when creating issue. - Based on questions asked here: https://new-issue.vuejs.org/#modal * Remove ' instead of the expected behavior' 2017-08-20 15:08:56 -05:00			`\| react-navigation \|`
			`\| react-native \|`
			`\| node \|`
Add issue template (#1199) * Add issue template * Ask for screenshot * Update ISSUE_TEMPLATE.md 2017-04-24 19:40:43 +02:00			`\| npm or yarn \|`