@@ -19,37 +19,10 @@ should be directed to the [Technical Steering Committee (TSC) repository][]. |
19 | 19 | ## Submitting a Bug Report |
20 | 20 |
|
21 | 21 | When opening a new issue in the `nodejs/node` issue tracker, users will be |
22 | | -presented with a basic template that should be filled in. |
23 | | - |
24 | | -```markdown |
25 | | -<!-- |
26 | | -Thank you for reporting an issue. |
27 | | -
|
28 | | -This issue tracker is for bugs and issues found within Node.js core. |
29 | | -If you require more general support please file an issue on our help |
30 | | -repo. https://github.com/nodejs/help |
31 | | -
|
32 | | -
|
33 | | -Please fill in as much of the template below as you're able. |
34 | | -
|
35 | | -Version: output of `node -v` |
36 | | -Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) |
37 | | -Subsystem: if known, please specify affected core module name |
38 | | -
|
39 | | -If possible, please provide code that demonstrates the problem, keeping it as |
40 | | -simple and free of external dependencies as you are able. |
41 | | ---> |
42 | | - |
43 | | -* **Version**: |
44 | | -* **Platform**: |
45 | | -* **Subsystem**: |
46 | | - |
47 | | -<!-- Enter your issue details below this comment. --> |
48 | | -``` |
49 | | - |
50 | | -If you believe that you have uncovered a bug in Node.js, please fill out this |
51 | | -form, following the template to the best of your ability. Do not worry if you |
52 | | -cannot answer every detail, just fill in what you can. |
| 22 | +presented with a choice of issue templates. If you believe that you have |
| 23 | +uncovered a bug in Node.js, please fill out the `Bug Report` template to the |
| 24 | +best of your ability. Do not worry if you cannot answer every detail; just fill |
| 25 | +in what you can. |
53 | 26 |
|
54 | 27 | The two most important pieces of information we need in order to properly |
55 | 28 | evaluate the report is a description of the behavior you are seeing and a simple |
|