sync icarus 4.0

.github/ISSUE_TEMPLATE/Bug反馈.md

@@ -0,0 +1,39 @@
+---
+name: Bug反馈
+about: 请按照模板填写Bug反馈，否则你的Issue可能会被直接关闭。
+title: [Bug] 问题概述
+labels: ''
+assignees: ''
+
+---
+
+> 确保你在提交Bug反馈之前仔细阅读了[Hexo文档](https://hexo.io/zh-cn/)，[Icarus用户指南](https://ppoffice.github.io/hexo-theme-icarus/tags/Icarus%E7%94%A8%E6%88%B7%E6%8C%87%E5%8D%97/)，和[GitHub issues](https://github.com/ppoffice/hexo-theme-icarus/issues)来了解你的问题是否已经被他人提出过。
+
+**Bug描述**
+简洁清晰地描述你遇到的Bug是什么。
+
+**系统与环境**
+列出你的Hexo和Icarus的版本和配置。
+
+- Hexo，操作系统，和Node.js的版本（使用`hexo version`命令来查看）
+- 站点配置文件`_config.yml`
+- 主题配置文件`_config.icarus.yml`或`themes/icarus/_config.yml`
+- 其他额外的配置文件（文章front-matter，`_config.post.yml`，或`_config.page.yml`）
+- 浏览器版本（如Firefox 70.0，Chrome Android 80.0）
+
+**复现方式**
+列出复现这个Bug的步骤，如：
+
+1. 访问‘...’
+2. 点击’...‘
+3. 下拉到‘...’
+4. 出现‘...’的错误
+
+**期望行为**
+简洁清晰地描述没有这个情况下你期望得到的结果。
+
+**截图**
+如果可以的话，请附上几张截图来帮助说明你遇到的问题。
+
+**额外上下文**
+附上与问题有关的其他上下文信息。

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug Report
+about: Please follow this template if you are reporting a bug, or your issue may be closed without further notice.
+title: [Bug] Bug summary
+labels: ''
+assignees: ''
+
+---
+
+> Make sure you go through the [Hexo docs](https://hexo.io), [Icarus user manual](https://ppoffice.github.io/hexo-theme-icarus/tags/Icarus-User-Guide/), and [GitHub issues](https://github.com/ppoffice/hexo-theme-icarus/issues) to see if the bug you are reporting has been already addressed by others.
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**System and Environment**
+The version and configuration of Hexo and Icarus.
+
+- Hexo, OS, and node version (use `hexo version` command to view these information)
+- Site configuration file `_config.yml`
+- Theme configuration file `_config.icarus.yml` or `themes/icarus/_config.yml`
+- Any additional theme configuration files (post front-matter, `_config.post.yml`, or `_config.page.yml`)
+- Browser and version (e.g., Firefox 70.0, Chrome Android 80.0)
+
+**To Reproduce**
+Steps to reproduce the behavior, such as:
+
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. '...' error appears
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,20 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Gitter
+    url: https://gitter.im/hexo-theme-icarus/community
+    about: Redirect your Icarus usage questions to Gitter.
+  - name: Gitter
+    url: https://gitter.im/hexo-theme-icarus/community
+    about: 与Icarus使用相关的问题请转至这里。
+  - name: Bug Report
+    url: https://github.com/ppoffice/hexo-theme-icarus/issues/new?template=bug_report.md
+    about: Please follow this template if you are reporting a bug, or your issue may be closed without further notice.
+  - name: Bug反馈
+    url: https://github.com/ppoffice/hexo-theme-icarus/issues/new?template=Bug反馈.md
+    about: 请按照模板填写Bug反馈，否则你的Issue可能会被直接关闭。
+  - name: Feature Request
+    url: https://github.com/ppoffice/hexo-theme-icarus/issues/new?template=feature_request.md
+    about: Please follow this template if you are requesting a new feature, or your issue may be closed without further notice.
+  - name: 功能建议
+    url: https://github.com/ppoffice/hexo-theme-icarus/issues/new?template=功能建议.md
+    about: 请按照模板填写功能建议，否则你的Issue可能会被直接关闭。

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature Request
+about: Please follow this template if you are requesting a new feature, or your issue may be closed without further notice.
+title: [FEAT] Feature request summary
+labels: ''
+assignees: ''
+
+---
+
+> Make sure you go through the [Hexo docs](https://hexo.io), [Icarus user manual](https://ppoffice.github.io/hexo-theme-icarus/tags/Icarus-User-Guide/), and [GitHub issues](https://github.com/ppoffice/hexo-theme-icarus/issues) to see if the feature you are requesting has been already addressed by others.
+
+**Is your feature request related to a problem? Please describe.**
+
+A clear and concise description of what the problem is (e.g., I'm always frustrated when [...]).
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/功能建议.md

@@ -0,0 +1,26 @@
+---
+name: 功能建议
+about: 请按照模板填写功能建议，否则你的Issue可能会被直接关闭。
+title: [FEAT] 功能建议概述
+labels: ''
+assignees: ''
+
+---
+
+> 确保你在提交功能建议之前仔细阅读了[Hexo文档](https://hexo.io/zh-cn/)，[Icarus用户指南](https://ppoffice.github.io/hexo-theme-icarus/tags/Icarus%E7%94%A8%E6%88%B7%E6%8C%87%E5%8D%97/)，和[GitHub issues](https://github.com/ppoffice/hexo-theme-icarus/issues)来了解你的建议是否已经被他人提出过。
+
+**你的功能建议与某个使用问题相关么？请详述。**
+
+简洁清晰地描述你遇到的问题是什么（如：我在使用...的时候遇到了...）。
+
+**描述你想要的解决方案**
+
+简洁清晰地描述你想要的解决方案可以达到的效果。
+
+**描述你考虑过的替代办法**
+
+简洁清晰地描述你考虑过的替代解决方案或是新功能。
+
+**额外上下文**
+
+附上与功能请求有关的其他上下文信息或者截图。

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,30 @@
+---
+name: Pull Request
+about: Suggest a code change to this project.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Note 0**
+Please review [the contributing guide](https://github.com/ppoffice/hexo-theme-icarus/blob/master/CONTRIBUTING.md) before making this pull request.
+
+**Note 1**
+
+Please break up your pull request into multiple smaller requests if it contains multiple bug fixes 
+or new features.
+Each pull request should have one bug fix or new feature only for better code maintainability.
+
+**Note 2**
+
+Many components of this theme, including core functions, some Hexo extensions, widgets and plugins, 
+have been moved to [ppoffice/hexo-component-inferno](https://github.com/ppoffice/hexo-component-inferno).
+Please make a pull request to that repository instead of this one if your changes are related to
+the above components.
+
+**Detailed description**
+
+> Please use the [Icarus issue template](https://github.com/ppoffice/hexo-theme-icarus/blob/master/.github/ISSUE_TEMPLATE/bug_report.md) if it is a bug fix.
+
+> Please use the [Icarus feature request template](https://github.com/ppoffice/hexo-theme-icarus/blob/master/.github/ISSUE_TEMPLATE/feature_request.md) if it is a bug fix.

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: 'daily'

.github/stale.yml

@@ -0,0 +1,32 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 14
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - bug:core
+  - bug:extension
+  - bug:general
+  - feature:core
+  - feature:extension
+  - feature:general
+  - tutorial:v1
+  - tutorial:v2
+  - tutorial:v3
+  - tutorial:v4
+  - tutorial:v5
+  - tutorial:v6
+  - tutorial:v7
+  - tutorial:v8
+  - tutorial:v9
+  - Gitalk
+  - utterances
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

.github/workflows/github-release.yml

@@ -0,0 +1,20 @@
+name: GitHub Release
+
+on:
+  push:
+    tags:
+      - "*"
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: ${{ github.ref }}
+          release_name: ${{ github.ref }}
+          draft: true
+          prerelease: false

.github/workflows/lint.yml

@@ -0,0 +1,15 @@
+name: Code Linting
+
+on: [push, pull_request]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+      - run: npm install
+      - run: >
+          npm install $(node -e "const deps=require('./package.json').peerDependencies;
+          console.log(Object.keys(deps).map(key=>key+'@'+deps[key]).join(' '));")
+      - run: npm run lint

.github/workflows/npm-publish.yml

@@ -0,0 +1,18 @@
+name: Node.js Package
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}