Skip to content

Commit 2890de4

Browse files
RyanCavanaughRyanCavanaugh
committed
Update issue templates
1 parent b467cd8 commit 2890de4

3 files changed

Lines changed: 90 additions & 0 deletions

File tree

‎.github/ISSUE_TEMPLATE/Bug_report.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨
8+
9+
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs" section!
10+
11+
Please help us by doing the following steps before logging an issue:
12+
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
13+
* Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
14+
15+
Please fill in the *entire* template below.
16+
-->
17+
18+
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
19+
**TypeScript Version:** 2.9.0-dev.201xxxxx
20+
21+
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
22+
**Search Terms:**
23+
24+
**Code**
25+
26+
```ts
27+
// A *self-contained* demonstration of the problem follows...
28+
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.
29+
```
30+
31+
**Expected behavior:**
32+
33+
**Actual behavior:**
34+
35+
**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
36+
37+
**Related Issues:** <!-- Did you find other bugs that looked similar? -->

‎.github/ISSUE_TEMPLATE/Custom.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: Question
3+
about: Ask a question
4+
5+
---
6+
7+
THE ISSUE TRACKER IS NOT FOR QUESTIONS.
8+
9+
DO NOT CREATE A NEW ISSUE TO ASK A QUESTION.
10+
11+
IF YOU ARE HAVING PROBLEMS WITH YOUR TYPESCRIPT CODE, DO NOT ASK A QUESTION HERE.
12+
13+
Tens of thousands of TypeScript questions have been asked and answered on StackOverflow; see https://stackoverflow.com/questions/tagged/typescript . You can ask questions there or on other websites.
14+
15+
The only exception is if you have a question about *the TypeScript compiler API itself*. Please post a complete example of what you're trying to do and precisely describe what your question is.

‎.github/ISSUE_TEMPLATE/Feature_request.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨
8+
9+
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.
10+
11+
-->
12+
13+
## Search Terms
14+
15+
<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
16+
17+
## Suggestion
18+
19+
<!-- A summary of what you'd like to see added or changed -->
20+
21+
## Use Cases
22+
23+
<!--
24+
What do you want to use this for?
25+
What shortcomings exist with current approaches?
26+
-->
27+
28+
## Examples
29+
30+
<!-- Show how this would be used and what the behavior would be -->
31+
32+
## Checklist
33+
34+
I attest that all of the following are true:
35+
[ ] This wouldn't change the behavior of existing JavaScript code
36+
[ ] This could be implemented without emitting different JS based on the types of the expressions
37+
[ ] This isn't a runtime feature that should be handled by TC39 instead
38+
[ ] This wouldn't be a breaking change in existing TypeScript / JavaScript code

0 commit comments

Comments
 (0)