Skip to content

Commit 3bd4281

Browse files
authored
Make the description of issue templates easier (#4168)
1 parent 8d23842 commit 3bd4281

File tree

2 files changed

+29
-35
lines changed

2 files changed

+29
-35
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 17 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
name: Bug report
3-
about: Create a report to help us improve Files
3+
about: Create a report to improve Files
44
title: ''
55
labels: bug
66
assignees: ''
@@ -10,39 +10,37 @@ assignees: ''
1010
<!--
1111
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
1212
I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
13-
1. Issue might get deleted if it is not following the template
14-
2. Only post one issue per bug report
15-
3. Try to avoid duplicates. Do a quick search before posting
16-
4. Add a descriptive title
13+
1. Issue may be deleted if it is not following the template
14+
2. Only post one issue per one bug report
15+
3. Try not to make duplicates. Do a quick search before posting
16+
4. Add a title that describes the issue clearly
1717
--->
1818

19-
**Describe the bug**
20-
A clear and concise description of what the bug is.
19+
**Explain the bug**
20+
Write a clear description of what the bug is.
2121

2222
**To reproduce**
23-
Steps to reproduce the behavior:
2423
1. Go to '....'
2524
2. Click on '....'
2625
3. Scroll down to '....'
27-
4. See error
26+
4. See the error
2827

2928
**Expected behavior**
30-
A clear and concise description of what you expected to happen.
29+
Write a clear description of what you expected.
3130

32-
**Log file**
33-
Please upload the log file here so that we can understand your issue better.
34-
* You can access it from Settings->About->Open log location.
31+
**Logfile**
32+
Upload the log file here for us to understand your issue better.
33+
- You can access it from Settings->About->Open log location.
3534
or
36-
* `%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState`
37-
38-
You should see a file in this directory called debug.txt or/and debug_fulltrust.txt.
35+
- Copy the debug.txt and debug_fulltrust.txt from the following directory, and upload the files here.
36+
`%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState`
3937

4038
**Screenshots**
41-
If applicable, add screenshots to help explain your problem.
39+
Add screenshots to help explain your problem if needed.
4240

4341
**System Information**
4442
- OS Version: [e.g. Windows 10 20H2 19042.804] (Press WIN + PAUSE/BREAK, use the copy button at the bottom)
4543
- App version: [e.g. v1.0] (In the app, go to Settings -> About, the version is shown at the top)
4644

47-
**Additional context**
48-
Add any other context about the problem here. Does this problem occur again after restarting the app?
45+
**Additional comment**
46+
Add any other comment about the problem here. Does this problem happen again after restarting the app?

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -9,26 +9,22 @@ assignees: ''
99
---
1010

1111
<!--
12-
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
13-
12+
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
1413
I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
15-
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
16-
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
17-
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
18-
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
19-
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
20-
21-
All good? Then proceed!
14+
1. Issue may be deleted if it is not following the template
15+
2. Only post one request per one feature request
16+
3. Try not to make duplicates. Do a quick search before posting
17+
4. Add a clarified title
2218
-->
2319

24-
**Is your feature request related to a problem? Please describe.**
25-
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
20+
**Is your feature request related to a problem?**
21+
A clear description of what the problem is.
2622

27-
**Describe the solution you'd like**
28-
A clear and concise description of what you want to happen.
23+
**Describe the solution**
24+
A clear description of what you want.
2925

3026
**Describe alternatives you've considered**
31-
A clear and concise description of any alternative solutions or features you've considered.
27+
A clear description of any alternative solutions or features you've considered.
3228

33-
**Additional context**
34-
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?
29+
**Additional comment**
30+
Add any other comment or screenshots about the feature request here. What device type/UI layout and app version?

0 commit comments

Comments
 (0)