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 b0aad34
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -33,7 +33,7 @@ body: | |||
| 33 | 33 | label: How often does it reproduce? Is there a required condition? | |
| 34 | 34 | - type: textarea | |
| 35 | 35 | attributes: | |
| 36 | - label: What is the expected behavior? | ||
| 36 | + label: What is the expected behavior? Why is that the expected behavior? | ||
| 37 | 37 | description: If possible please provide textual output instead of screenshots. | |
| 38 | 38 | - type: textarea | |
| 39 | 39 | attributes: | |
0 commit comments