From a67db5607ba2052b4ea44f66657f98b758fb4786 Mon Sep 17 00:00:00 2001
From: Daijiro Wachi <daijiro.wachi@gmail.com>
Date: Thu, 19 Jul 2018 05:29:31 +0900
Subject: [PATCH] docs: replace troubleshooting.md with posts (#17)

Refs: https://github.com/npm/cli/pull/5
PR-URL: https://github.com/npm/cli/pull/17/
Credit: @watilde
Reviewed-By: @zkat
---
 .github/issue_template.md | 70 ---------------------------------------
 CONTRIBUTING.md           |  2 +-
 2 files changed, 1 insertion(+), 71 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?
-
-<!--
-    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/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).
-
-<!--
-    Thank you for contributing to npm! Please review this checklist
-    before submitting your issue.
-
-    - Please check if there's a solution in the troubleshooting wiki:
-      https://github.com/npm/npm/blob/latest/TROUBLESHOOTING.md
-
-    - Also ensure that your new issue conforms to npm's contribution guidelines:
-      https://github.com/npm/npm/blob/latest/CONTRIBUTING.md
-
-    - Participation in this open source project is subject to the npm Code of Conduct:
-      https://www.npmjs.com/policies/conduct
-
-    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
--->
-
-<!--
-
-#### What's the feature?
-
-#### What problem is the feature intended to solve?
-
-#### Is the absence of this feature blocking you or your team? If so, how?
-
-#### Is this feature similar to an existing feature in another tool?
-
-#### Is this a feature you're prepared to implement, with support from the npm CLI team?
-
--->
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.