Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorForrest L Norvell <forrest@npmjs.com>2016-06-28 21:36:50 +0300
committerForrest L Norvell <forrest@npmjs.com>2016-06-30 06:17:18 +0300
commitdd2b5e861cc6f14693682ceba776764c6ac71465 (patch)
treef9791934c2080eb87b167c1b2c75f571fc41286c /.github
parent8a5b926188c8c2296d59061af97d98b5743f3d75 (diff)
doc: tweak issue template
- move important bits to top - condense supporting info down to a smaller section - more structured request for proxy & network info
Diffstat (limited to '.github')
-rw-r--r--.github/issue_template.md91
1 files changed, 40 insertions, 51 deletions
diff --git a/.github/issue_template.md b/.github/issue_template.md
index a98b6403e..a40c57fa3 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -1,3 +1,40 @@
+#### I'm opening this issue because:
+
+ - [ ] npm is crashing.
+ - [ ] npm is producing an incorrect install.
+ - [ ] npm is doing something I don't understand.
+ - [ ] Other (_see below for feature requests_):
+
+#### What's going wrong?
+
+#### How can the CLI team reproduce the problem?
+
+<!--
+ Please a complete description of how to reproduce the problem.
+ Include a gist of your npm-debug.log file.
+ If you've never used gist.github.com, start here:
+ https://github.com/EmmaRamirez/how-to-submit-your-npm-debug-log
+-->
+
+### supporting information:
+
+ - `npm -v` prints:
+ - `node -v` prints:
+ - `npm config get registry` prints:
+ - Windows, OS X, or Linux?:
+ - Network issues:
+ - Geographic location where npm was run:
+ - [ ] I use a proxy to connect to the npm registry.
+ - [ ] I use a proxy to connect to the web.
+ - [ ] I use a proxy when downloading Git repos.
+ - [ ] I access the npm registry via a VPN
+ - [ ] I don't use a proxy, but have limited or unreliable internet access.
+ - Container:
+ - [ ] I develop using Vagrant on Windows.
+ - [ ] I develop using Vagrant on OS X or Linux.
+ - [ ] I develop / deploy using Docker.
+ - [ ] I deploy to a PaaS (Triton, Heroku).
+
<!--
Thank you for contributing to npm! Please review this checklist
before submitting your issue.
@@ -11,57 +48,9 @@
- Participation in this open source project is subject to the npm Code of Conduct:
https://www.npmjs.com/policies/conduct
- If you're here to provide a feature request, uncomment the final block below.
--->
-
-### I'm opening this issue because:
-
- - [ ] npm is crashing
- - [ ] npm is producing an incorrect install
- - [ ] npm is doing something I don't understand
- - [ ] other (_see below for feature requests_)
-
-#### Node version:
-
-<!-- output of 'node -v' -->
-
-#### npm version:
-
-<!-- output of 'npm -v' -->
-
-#### How did you install Node and npm?
-
-<!-- nodejs.org installer, Homebrew, apt-get -->
-
-#### Operating system version and distribution:
-
-<!--
- operating systems: Linux, Windows 7, Windows 10, OS X 10.11.5, SmartOS
- distributions: Ubuntu, Arch
- ('uname -a' output is also helpful here, on non-Windows systems)
--->
-
-#### Containerization or virtualization environment:
-
-<!-- Docker, Vagrant on Windows, Triton, Heroku, VirtualBox, Azure -->
-
-#### Are you using [a proxy](https://docs.npmjs.com/misc/config#proxy)?
-
-#### What problem are you seeing?
-
-#### How can the problem be reproduced?
-
-<!--
- Please provide minimal steps to reproducing the problem.
- Include a gist of your npm-debug.log file.
- If you've never used gist, read here:
- https://github.com/EmmaRamirez/how-to-submit-your-npm-debug-log
--->
-
-<!--
- For feature requests, delete the above and uncomment the section following this one.
-
- But first, take a look at the existing feature requests:
+ For feature requests, delete the above and uncomment the section following this one. But first, review the existing feature requests
+ and make sure there isn't one that already describes the feature
+ you'd like to see added:
https://github.com/npm/npm/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+label%3Aalready-looked-at
-->