From 9aba7f122c84f7191b94a238652c1388835b5a80 Mon Sep 17 00:00:00 2001
From: Hirokazu Hata <h.hata.ai.t@gmail.com>
Date: Tue, 9 Jun 2020 17:59:09 +0900
Subject: add GitHub issue template for lsp

---
 .github/ISSUE_TEMPLATE/lsp_bug_report.md | 47 ++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/lsp_bug_report.md

diff --git a/.github/ISSUE_TEMPLATE/lsp_bug_report.md b/.github/ISSUE_TEMPLATE/lsp_bug_report.md
new file mode 100644
index 0000000000..5b0ffdc1bf
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/lsp_bug_report.md
@@ -0,0 +1,47 @@
+---
+name: Language server client bug report
+about: Report a built-in lsp problem in Nvim
+title: ''
+labels:
+  - bug
+  - lsp
+---
+
+<!-- Before reporting: search existing issues and check the FAQ. -->
+
+- `nvim --version`:
+- language server name/version:
+- Operating system/version:
+
+<details>
+<summary>`nvim -c ":checkhealth nvim nvim_lsp"`</summary>
+
+<!-- Paste the results from `nvim -c ":checkhealth nvim nvim_lsp"` here. -->
+
+</details>
+
+<details>
+<summary>lsp.log</summary>
+
+<!--
+Please paste the lsp log before and after the problem.
+
+You can set log level like this.
+`:lua vim.lsp.set_log_level("debug")`
+
+You can find the location of the log with the following command.
+`:lua print(vim.lsp.get_log_path())`
+-->
+
+</details>
+
+### Steps to reproduce using `nvim -u NORC`
+
+```
+nvim -u NORC
+```
+
+### Actual behaviour
+
+### Expected behaviour
+
-- 
cgit