From 2d0506c566eae73450369e0d77611b2de46cccef Mon Sep 17 00:00:00 2001
From: Wang Shidong <wsdjeg@outlook.com>
Date: Sun, 30 May 2021 15:55:12 +0800
Subject: [PATCH] Disable github issue (#4280)

---
 docs/community.md   | 14 ++++----------
 docs/development.md | 17 ++++++++++-------
 2 files changed, 14 insertions(+), 17 deletions(-)

diff --git a/docs/community.md b/docs/community.md
index cc896a243..20c83c34b 100644
--- a/docs/community.md
+++ b/docs/community.md
@@ -11,8 +11,7 @@ Visit these resources for help or general questions.
 <!-- vim-markdown-toc GFM -->
 
 - [News](#news)
-- [Bug repport and feature request](#bug-repport-and-feature-request)
-- [Mail list](#mail-list)
+- [Mailing list](#mailing-list)
 - [Chat](#chat)
 - [Others](#others)
 
@@ -22,20 +21,15 @@ Visit these resources for help or general questions.
 
 - <i class="fab fa-twitter"></i> [Twitter](https://twitter.com/SpaceVim)
 
-### Bug repport and feature request
+### Mailing list
 
-- [issue tracker](https://github.com/SpaceVim/SpaceVim/issues) for issue and feature requests
-
-### Mail list
-
-Users who are accustomed to using email can also communicate with each other through the mail group.
-They can send email to the mailing list to participate in the discussion.
+To report a bug or feature request, you can use the SpaceVim google mail list.
 
 ```
 spacevim@googlegroups.com
 ```
 
-Please note that to post on these lists, you must be a member,
+Please note that to post on the list, you must be a member,
 To join this group send an empty message to:
 
 ```
diff --git a/docs/development.md b/docs/development.md
index a856178f4..437e8aed4 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -8,7 +8,7 @@ description: "General contributing guidelines and changelog of SpaceVim, includi
 <!-- vim-markdown-toc GFM -->
 
 - [Asking for help](#asking-for-help)
-- [Reporting issues](#reporting-issues)
+- [Bug reporting](#bug-reporting)
 - [Contributing code](#contributing-code)
   - [License](#license)
   - [Conventions](#conventions)
@@ -47,18 +47,21 @@ You can only consider reading the sections relevant to what you are going to do:
 
 ## Asking for help
 
-If you want to ask an usage question, be sure to look first into some places as it may hold the answers:
+If you want to ask an usage question,
+be sure to look first into some places as it may hold the answers:
 
 - <kbd>:h SpaceVim-faq</kbd>: Some of the most frequently asked questions are answered there.
 - [SpaceVim documentation](https://spacevim.org/documentation/): It is the general documentation of SpaceVim.
 
-## Reporting issues
+## Bug reporting
 
-Issues have to be reported on [issues tracker](https://github.com/SpaceVim/SpaceVim/issues), please:
+To report a bug, you can use the spacevim mailing list `spacevim@googlegroups.com`,
+before sending mail, please:
 
-- Check that no duplicate issue is in the issues tracker, you can search for keywords in the issues tracker.
-- Check that the issue has not been fixed in latest version of SpaceVim, please update your SpaceVim, and try to reproduce the bug here.
-- Use a clear title and follow the issue template.
+- Check that no duplicate issue in [google groups](https://groups.google.com/forum/#!forum/spacevim)
+- Check that the issue has not been fixed in latest version of SpaceVim,
+  please update your SpaceVim, and try to reproduce the bug here.
+- Use a clear title with `[bug]` prefix.
 - Include details on how to reproduce it, just like a step by step guide.
 
 ## Contributing code