Skip to content

Commit 8a74c88

Browse files
zoontekzoontek
committed
Update .github files
1 parent dd05ddf commit 8a74c88

File tree

5 files changed

+169
-21
lines changed

5 files changed

+169
-21
lines changed

‎.github/ISSUE_TEMPLATE.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# No Template
2+
3+
👉 Please follow one of the issue templates provided by the repo - if you are seeing this message, it means you haven't.
4+
5+
If you don't follow the issue template, we may immediately close it.

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
name: '🐛 Bug report'
3+
about: Report a reproducible bug or regression in this library.
4+
---
5+
6+
# Bug report
7+
8+
<!--
9+
👋 Hi!
10+
11+
🚨 Please read the following carefully before opening a new issue. Your issue may
12+
be closed if it doesn't provide the required pieces of information. 🚨
13+
14+
Before submitting a new issue, please:
15+
16+
- Test using the latest release of the library, as maybe your bug has been already fixed.
17+
- Check for possible duplicate issues, with possible answers.
18+
- Check on https://reactnative.directory if this package supports your target platform (Android, iOS, Expo, …)
19+
20+
Still ready? Fill the template. 👇
21+
-->
22+
23+
## Summary
24+
25+
<!--
26+
Provide a clear and concise description of what the bug is.
27+
-->
28+
29+
## Environment info
30+
31+
<!--
32+
Run `react-native info` in your terminal and paste the results here. Also, include the *precise* version number of this library that you are using in the project.
33+
-->
34+
35+
`react-native info` output:
36+
37+
```bash
38+
# paste it here
39+
```
40+
41+
Library version: x.x.x
42+
43+
## Steps to reproduce
44+
45+
<!--
46+
- You must provide a clear list of steps and code to reproduce the problem.
47+
- Keep the code reproducing the bug as simple as possible, with the minimum amount of code required to reproduce the issue. See https://stackoverflow.com/help/mcve.
48+
- If this library has additional install steps, describe them (e.g., pod install? jetify? etc).
49+
- Either re-create the bug using the repository's example app or link to a GitHub repository with code that reproduces the bug.
50+
- Explain the steps we need to take to reproduce the issue:
51+
-->
52+
53+
1. …
54+
2. …
55+
56+
Describe what you expected to happen:
57+
58+
1. …
59+
2. …
60+
61+
## Reproducible sample code
62+
63+
<!--
64+
Please add minimal runnable repro as explained above so that the bug can be tested in isolation.
65+
If needed, you can also provide other samples: error messages / stack traces, screenshots, gifs, etc.
66+
-->

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: '💡 Feature request'
3+
about: Submit your idea for a change in the codebase.
4+
---
5+
6+
# Feature request
7+
8+
<!--
9+
This issue should serve for you to present or pitch an idea to the maintainers - but remember that it would be better if you were to submit a PR instead 🤗
10+
-->
11+
12+
## Why it is needed
13+
14+
<!--
15+
Please tell us a bit more of why you want this feature to be added, what's its origin.
16+
-->
17+
18+
## Possible implementation
19+
20+
<!--
21+
It really helps if you could describe from a technical POV how this new feature would work, which code it rely on, etc.
22+
-->
23+
24+
### Code sample
25+
26+
<!--
27+
Please show how the new code could work, if doable.
28+
-->

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please follow the template so that the reviewers can easily understand what the code changes affect -->
2+
3+
# Summary
4+
5+
<!--
6+
Explain the **motivation** for making this change: here are some points to help you:
7+
8+
* What issues does the pull request solve? Please tag them so that they will get automatically closed once the PR is merged
9+
* What is the feature? (if applicable)
10+
* How did you implement the solution?
11+
* What areas of the library does it impact?
12+
-->
13+
14+
## Test Plan
15+
16+
<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. -->
17+
18+
### What's required for testing (prerequisites)?
19+
20+
### What are the steps to reproduce (after prerequisites)?
21+
22+
## Compatibility
23+
24+
| OS | Implemented |
25+
| ------- | :---------: |
26+
| iOS | ✅❌ |
27+
| Android | ✅❌ |
28+
29+
## Checklist
30+
31+
<!-- Check completed item, when applicable, via: [X] -->
32+
33+
- [ ] I have tested this on a device and a simulator
34+
- [ ] I added the documentation in `README.md`
35+
- [ ] I mentioned this change in `CHANGELOG.md`
36+
- [ ] I updated the typed files (TS and Flow)
37+
- [ ] I added a sample use of the API in the example project (`example/App.js`)

‎.github/stale.yml‎

Lines changed: 33 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,41 @@
11
# Configuration for probot-stale based on: https://github.com/facebook/react-native/blob/master/.github/stale.yml
22

3-
# Number of days of inactivity before an issue becomes stale
4-
daysUntilStale: 90
5-
6-
# Number of days of inactivity before a stale issue is closed
7-
daysUntilClose: 7
8-
9-
# Issues with these labels will never be considered stale
3+
# Number of days of inactivity before an Issue or Pull Request becomes stale
4+
daysUntilStale:
5+
60
6+
# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
7+
daysUntilClose:
8+
7
9+
# Issues or Pull Requests.
1010
exemptLabels:
11-
- security
1211
- pinned
13-
- good first issue
14-
- help wanted
15-
16-
# Label to use when marking an issue as stale
17-
staleLabel: Stale
12+
- security
13+
- discussion
1814

19-
# Comment to post when marking an issue as stale. Set to `false` to disable
15+
# Set to true to ignore issues in a project (defaults to false)
16+
exemptProjects:
17+
false
18+
# Set to true to ignore issues in a milestone (defaults to false)
19+
exemptMilestones:
20+
false
21+
# Set to true to ignore issues with an assignee (defaults to false)
22+
exemptAssignees:
23+
false
24+
# Label to use when marking as stale
25+
staleLabel:
26+
stale
27+
# Comment to post when marking as stale. Set to `false` to disable
2028
markComment: >
21-
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs.
22-
You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open.
23-
Thank you for your contributions.
24-
25-
# Comment to post when closing a stale issue. Set to `false` to disable
29+
This issue has been automatically marked as stale because it has not had
30+
recent activity. It will be closed if no further activity occurs. Thank you
31+
for your contributions. You may also mark this issue as a "discussion" and I
32+
will leave this open.
33+
# Comment to post when closing a stale Issue or Pull Request.
2634
closeComment: >
27-
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.
28-
35+
Closing this issue after a prolonged period of inactivity. Fell free to reopen
36+
this issue, if this still affecting you.
37+
# Limit the number of actions per hour, from 1-30. Default is 30
38+
limitPerRun:
39+
30
40+
# Limit to only `issues` or `pulls`
2941
only: issues

0 commit comments

Comments
 (0)