From b77bb3b71504ff312a148a605cf13262c6a35ecc Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 12:00:37 +0900 Subject: [PATCH 1/2] docs: replace troubleshooting.md with posts Refs: https://github.com/npm/cli/pull/5 --- CONTRIBUTING.md | 2 +- README.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f412dc93ed82b..3fc4ff5dc7a82 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,7 +35,7 @@ This includes anyone who may show up to the npm/npm repo with issues, PRs, comme * Comment on issues when they have a reference to the answer. * If community members aren't sure they are correct and don't have a reference to the answer, please leave the issue and try another one. * Defer to collaborators and npm employees for answers. -* Make sure to search for [the troubleshooting doc](./TROUBLESHOOTING.md) and search on the issue tracker for similar issues before opening a new one. +* Make sure to search for [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting) and search on the issue tracker for similar issues before opening a new one. * Any users with urgent support needs are welcome to email support@npmjs.com, and our dedicated support team will be happy to help. PLEASE don't @ collaborators or npm employees on issues. The CLI team is small, and has many outstanding commitments to fulfill. diff --git a/README.md b/README.md index 87aab26d90bc4..0124336465289 100644 --- a/README.md +++ b/README.md @@ -87,8 +87,7 @@ Many improvements for Windows users have been made in npm 3 - you will have a be experience if you run a recent version of npm. To upgrade, either use [Microsoft's upgrade tool](https://github.com/felixrieseberg/npm-windows-upgrade), [download a new version of Node](https://nodejs.org/en/download/), -or follow the Windows upgrade instructions in the -[npm Troubleshooting Guide](./TROUBLESHOOTING.md). +or follow the Windows upgrade instructions in [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting). If that's not fancy enough for you, then you can fetch the code with git, and mess with it directly. From 630d512464b9a75f0fd3a7c578060e1f485e0d6f Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 12:01:10 +0900 Subject: [PATCH 2/2] docs: remove issue_template.md --- .github/issue_template.md | 70 --------------------------------------- 1 file changed, 70 deletions(-) delete mode 100644 .github/issue_template.md diff --git a/.github/issue_template.md b/.github/issue_template.md deleted file mode 100644 index ec78009f7605b..0000000000000 --- a/.github/issue_template.md +++ /dev/null @@ -1,70 +0,0 @@ -#### I'm opening this issue because: - - - [ ] npm is crashing. - - [ ] npm is producing an incorrect install. - - [ ] npm is doing something I don't understand. - - [ ] npm is producing incorrect or undesirable behavior. - - [ ] Other (_see below for feature requests_): - -#### What's going wrong? - -#### How can the CLI team reproduce the problem? - - - -### supporting information: - - - `npm -v` prints: - - `node -v` prints: - - `npm config get registry` prints: - - Windows, OS X/macOS, 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). - - - -