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