Skip to content

Commit f705094

Browse files
committed
chore: update issue templates
1 parent e31a6fd commit f705094

10 files changed

+289
-43
lines changed

.github/ISSUE_TEMPLATE.md

Lines changed: 0 additions & 40 deletions
This file was deleted.
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bottom Tab Navigator
3+
about: Report an issue with Bottom Tab Navigator (@react-navigation/bottom-tabs)
4+
title: ''
5+
labels: bug, package:bottom-tabs
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ----------------------------- | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/bottom-tabs |
34+
| react-native-screens |
35+
| react-native |
36+
| expo |
37+
| node |
38+
| npm or yarn |
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Drawer Navigator
3+
about: Report an issue with Drawer Navigator (@react-navigation/drawer)
4+
title: ''
5+
labels: bug, package:drawer
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ------------------------------ | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/drawer |
34+
| react-native-reanimated |
35+
| react-native-gesture-handler |
36+
| react-native-safe-area-context |
37+
| react-native-screens |
38+
| react-native |
39+
| expo |
40+
| node |
41+
| npm or yarn |
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Material Bottom Tab Navigator
3+
about: Report an issue with Material Bottom Tab Navigator (@react-navigation/material-bottom-tabs)
4+
title: ''
5+
labels: bug, package:material-bottom-tabs
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| -------------------------------------- | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/material-bottom-tabs |
34+
| react-native-paper |
35+
| react-native |
36+
| expo |
37+
| node |
38+
| npm or yarn |
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Material Top Tab Navigator
3+
about: Report an issue with Material Top Tab Navigator (@react-navigation/material-top-tabs)
4+
title: ''
5+
labels: bug, package:material-top-tabs
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ----------------------------------- | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/material-top-tabs |
34+
| react-native-tab-view |
35+
| react-native |
36+
| expo |
37+
| node |
38+
| npm or yarn |
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Native Stack Navigator
3+
about: Report an issue with Native Stack Navigator (@react-navigation/native-stack)
4+
title: ''
5+
labels: bug, package:native-stack
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ------------------------------ | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/native-stack |
34+
| react-native-screens |
35+
| react-native |
36+
| expo |
37+
| node |
38+
| npm or yarn |
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
name: Stack Navigator
3+
about: Report an issue with Stack Navigator (@react-navigation/stack)
4+
title: ''
5+
labels: bug, package:stack
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ------------------------------ | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| @react-navigation/stack |
34+
| react-native-gesture-handler |
35+
| react-native-safe-area-context |
36+
| react-native-screens |
37+
| react-native |
38+
| expo |
39+
| node |
40+
| npm or yarn |

.github/ISSUE_TEMPLATE/bug-report.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Other bugs
3+
about: Report an issue which is not about a specific navigator.
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
---
8+
9+
**Current Behavior**
10+
11+
- What code are you running and what is happening?
12+
- Include a screenshot or video if it makes sense.
13+
14+
**Expected Behavior**
15+
16+
- What do you expect should be happening?
17+
- Include a screenshot or video if it makes sense.
18+
19+
**How to reproduce**
20+
21+
- You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of React Navigation.
22+
- Either re-create the bug on [Snack](https://snack.expo.io) or link to a GitHub repository with code that reproduces the bug.
23+
- Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
24+
- Keep the repro code as simple as possible, with the minimum amount of code required to repro the issue.
25+
- Before reporting an issue, make sure you are on latest version of the package.
26+
27+
**Your Environment**
28+
29+
| software | version |
30+
| ------------------------------ | ------- |
31+
| iOS or Android |
32+
| @react-navigation/native |
33+
| react-native |
34+
| expo |
35+
| node |
36+
| npm or yarn |

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Documentation
4+
url: https://next.reactnavigation.org
5+
about: Read the official documentation.
6+
- name: Feature Requests
7+
url: https://react-navigation.canny.io/feature-requests
8+
about: Post a feature request on Canny.
9+
- name: StackOverflow
10+
url: https://stackoverflow.com/questions/tagged/react-navigation
11+
about: Ask and answer questions using the react-navigation label.
12+
- name: Reactiflux
13+
url: https://www.reactiflux.com/
14+
about: Chat with other community members in the react-navigation channel.
15+
- name: Write an RFC
16+
url: https://github.com/react-navigation/rfcs
17+
about: Write a RFC if you have ideas for how to implement a feature request.

.github/PULL_REQUEST.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
Please provide enough information so that others can review your pull request:
22

3-
## Motivation
3+
**Motivation**
44

55
Explain the **motivation** for making this change. What existing problem does the pull request solve?
66

7-
## Test plan
7+
**Test plan**
88

99
Demonstrate the code is solid. Example: the exact commands you ran and their output, screenshots / videos if the pull request changes UI.
1010

1111
Make sure you test on both platforms if your change affects both platforms.
1212

1313
The code must pass tests.
1414

15-
## Code formatting
15+
**Code formatting**
1616

1717
Look around. Match the style of the rest of the codebase. Run `yarn lint --fix` before committing.

0 commit comments

Comments
 (0)