Skip to content

Commit 5f447b7

Browse files
authored
Merge branch 'master' into imported-pr-711
2 parents ffc3ec2 + 4282644 commit 5f447b7

File tree

4 files changed

+263
-102
lines changed

4 files changed

+263
-102
lines changed
Lines changed: 30 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,38 @@
11
---
2-
name: "\U0001F41BBug report"
3-
about: Report an Issue
2+
name: "🐛 Bug report"
3+
about: Report an issue
4+
title: "[BUG] <short summary>"
5+
labels: ["bug"]
6+
assignees: []
47
---
58

6-
<!--- Provide a general summary of the issue in the Title above -->
9+
<!-- Give a clear, concise summary of the bug in 1–2 lines. -->
710

8-
## Expected Behavior
9-
<!--- If you're suggesting a change/improvement, tell us how it should work -->
11+
## Environment
12+
<!-- Helps reproduce and debug faster. -->
13+
- OS:
14+
- Browser / Version:
15+
- Device:
16+
- App version / Commit hash:
1017

11-
## Current Behavior
12-
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
18+
## Expected behavior
19+
<!-- Describe what you expected to happen. -->
1320

14-
## Possible Solution
15-
<!--- Not obligatory, but suggest a fix/reason -->
16-
<!--- or ideas how to implement the addition or change -->
21+
## Current behavior
22+
<!-- Describe what actually happens, including error messages if any. -->
1723

18-
## Steps to Reproduce
19-
<!--- Provide a link to a live example -->
24+
## Steps to reproduce
25+
<!-- Numbered, detailed steps make it easier to reproduce. -->
26+
1. Go to '...'
27+
2. Click on '...'
28+
3. Scroll to '...'
29+
4. See error
2030

21-
## Context [OPTIONAL]
22-
<!--- How has this issue affected you? What are you trying to accomplish? -->
23-
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
31+
## Screenshots / Logs
32+
<!-- Add screenshots or paste relevant logs (sanitized). -->
33+
34+
## Possible solution
35+
<!-- Optional: ideas, suspected cause, or potential fix. -->
36+
37+
## Additional context
38+
<!-- How this affects you, related issues, or any extra details. -->

.github/stale.yml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Number of days of inactivity before an issue becomes stale
2-
daysUntilStale: 30
2+
daysUntilStale: 45
33
# Number of days of inactivity before a stale issue is closed
4-
daysUntilClose: 14
4+
daysUntilClose: 30
55
# Issues with these labels will never be considered stale
66
exemptLabels:
77
- pinned
@@ -11,11 +11,10 @@ exemptLabels:
1111
- enhancement
1212
- in progress
1313
# Label to use when marking an issue as stale
14-
staleLabel: wontfix
14+
stale: wontfix
1515
# Comment to post when marking an issue as stale. Set to `false` to disable
1616
markComment: >
17-
This issue has been automatically marked as stale because it has not had
18-
recent activity. It will be closed if no further activity occurs. Thank you
19-
for your contributions.
17+
This issue has been marked as stale due to inactivity.
18+
Please comment if this is still relevant
2019
# Comment to post when closing a stale issue. Set to `false` to disable
2120
closeComment: true

CONTRIBUTING.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,15 @@ Before making a pull request, please make sure of the following:
1717
* Check the spelling and grammar
1818
* Do the work, write good commit messages, and read the CONTRIBUTING file if there is one
1919
* Remove any trailing whitespaces
20-
* Links must be pointing straight to the tutorials, no URL shorteners. However, if the URL is too long (more than 80 characters), Google URL Shortener is allowed
20+
* Links must be pointing straight to the tutorials, no URL shorteners. However, if the URL is too long (more than 80 characters), Google URL Shortener is allowed.
21+
22+
### Pull request etiquette
23+
24+
Please keep pull requests focused and limited to a single change where possible. Be open to feedback and requested changes, and note that not all submissions may be accepted.
25+
26+
### Improving these guidelines
27+
28+
If you have suggestions to improve this document or the contribution process, feel free to open an issue or submit a pull request explaining your proposal. For small improvements such as wording or clarity fixes, a direct pull request is welcome.
29+
2130
2231
Thank you for your suggestions! If you think there is anything to improve with the guidelines, please contact me at <tuvtran97@gmail.com>

0 commit comments

Comments
 (0)