|
1 | | -> Select one of the following: |
2 | | -> |
3 | | -> I am filing a bug. |
4 | | -> |
5 | | -> > In this case you need the following information: |
6 | | -> |
| 1 | +> Please provide us with the following information: |
7 | 2 | > --------------------------------------------------------------- |
8 | | -1. OS. Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) |
| 3 | +1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) |
| 4 | + |
| 5 | + |
9 | 6 | 2. Versions. Please run `ng --version`. If there's nothing outputted, please |
10 | 7 | run in a Terminal: |
11 | | - |
12 | 8 | node --version |
13 | | - npm --version |
14 | | - npm info angular-cli |
15 | 9 | And paste the result here. |
16 | | -3. Repro steps. Tell us exactly what you did and how you came to the failure. |
17 | | - If you can give us steps from the moment you created an empty application, |
18 | | - even better! Please try to be as descriptive as you can; this will avoid |
19 | | - unnecessary back and forth. Was this an app that wasn't created using the |
20 | | - CLI? What change did you do on your code? etc. |
| 10 | + |
| 11 | + |
| 12 | +3. Repro steps. Was this an app that wasn't created using the CLI? What change did you |
| 13 | + do on your code? etc. |
| 14 | + |
| 15 | + |
21 | 16 | 4. The log given by the failure. Normally this include a stack trace and some |
22 | 17 | more information. |
| 18 | + |
| 19 | + |
23 | 20 | 5. Mention any other details that might be useful. |
24 | 21 | > --------------------------------------------------------------- |
25 | 22 | > > Thanks! We'll be in touch soon. |
26 | | -> |
27 | | -> I am filing a feature request. |
28 | | -> |
29 | | -> Unfortunately, for now, although we accept proposals, it will be probably be |
30 | | -> deferred. It's not that we don't want to hear you, it's that we're focusing |
31 | | -> on the beta release and as such we want to keep things a bit tidier than it |
32 | | -> will be once this is out in the open. |
33 | | -> |
34 | | -> We're not closed to good ideas, we simply have a limited amount of bandwidth. |
35 | | -> There's only 24 hours per day. |
36 | | -> |
37 | | -> --------------------------------------------------------------- |
38 | | -> |
39 | | -> I want customer support / I don't know how to do X. |
40 | | -> |
41 | | -> This is unfortunately not the right place. Please join the discussion on |
42 | | -> gitter, Stack Overflow or twitter and don't be afraid to post your |
43 | | -> questions there. A FAQ will be created with those and it will help answer |
44 | | -> questions other people might have as well. |
45 | | -> |
46 | | -> --------------------------------------------------------------- |
47 | | -> |
48 | | -> I want to help! |
49 | | -> |
50 | | -> Please read our contributing guidelines; |
51 | | -> https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md |
52 | | -> |
53 | | -> If you really want to be part of the crew and start cracking, |
54 | | -> try to contact us on gitter. We're never really far and we might have |
55 | | -> something just for you! |
0 commit comments