Commit b0aad34
meta: ask expected behavior reason in bug template
It happens too often that bug reporters only report _what_ they expect
to see without motivating _why_. Having to repeatedly ask for that info
gets old.
PR-URL: #47049
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Debadree Chatterjee <debadree333@gmail.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent b58d523 commit b0aad34Copy full SHA for b0aad34
File tree
Expand file treeCollapse file tree
1 file changed
+1
-1
lines changedOpen diff view settings
Filter options
- .github/ISSUE_TEMPLATE
Expand file treeCollapse file tree
1 file changed
+1
-1
lines changedOpen diff view settings
Collapse file
.github/ISSUE_TEMPLATE/1-bug-report.yml
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/1-bug-report.yml+1-1Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| ||
33 | 33 | |
34 | 34 | |
35 | 35 | |
36 | | - |
| 36 | + |
37 | 37 | |
38 | 38 | |
39 | 39 | |
|
0 commit comments