Merge pull request #104 from actions-cool/main

branch: merge main into 2.x

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,8 +8,8 @@ assignees:
 
 ### 🐛 Bug 描述 Bug description
 
-<!-- 请在上方详细地描述 bug，让大家都能理解。 -->
-<!-- Please describe the bug in detail above so that everyone can understand. -->
+<!-- 请在上方详细地描述 bug，让大家都能理解。建议附上使用代码。 -->
+<!-- Please describe the bug in detail above so that everyone can understand. It is recommended to attach the use code. -->
 
 ### 🏞 期望结果 Desired result
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -8,11 +8,11 @@ First of all, thank you for your contribution! 😄
 - [ ] 新特性提交 / New feature
 - [ ] bug 修复 / Fix bug
 - [ ] 样式优化 / Style optimization
-- [ ] 包体积优化 / Package size optimization
-- [ ] 性能优化 / Performance optimization
 - [ ] 代码风格优化 / Code style optimization
+- [ ] 性能优化 / Performance optimization
 - [ ] 构建优化 / Build optimization
 - [ ] 网站、文档、Demo 改进 / Website, documentation, demo improvements
+- [ ] 重构代码或样式 / Refactor code or style
 - [ ] 测试相关 / Test related
 - [ ] 其他 / Other
 
@@ -42,14 +42,4 @@ Describe changes from the user side, and list all potential break changes or oth
 | 🇺🇸 English |           |
 | 🇨🇳 Chinese |           |
 
-
-### ☑️ 请求合并前的自查清单 / Self Check before Merge
-
-⚠️ 请自检并全部**勾选全部选项**。/ Please check all items below before review. ⚠️
-
-- [ ] 文档已补充或无须补充 / Doc is updated/provided or not needed
-- [ ] 代码演示已提供或无须提供 / Demo is updated/provided or not needed
-- [ ] TypeScript 定义已补充或无须补充 / TypeScript definition is updated/provided or not needed
-- [ ] Changelog 已提供或无须提供 / Changelog is provided or not needed
-
 <!-- From: https://github.com/one-template/pr-template -->

.github/workflows/ci-notice.yml

@@ -0,0 +1,22 @@
+name: CI Notice
+
+on:
+  schedule:
+    - cron: '0 0 * * *'
+  workflow_dispatch:
+
+jobs:
+  setup:
+    runs-on: ubuntu-latest
+    steps:
+      - name: checkout
+        uses: actions/checkout@main
+      
+      - uses: actions-cool/ci-notice@main
+        with:
+          ci: |
+            yarn
+            yarn run package
+            yarn run docs:build
+          notice-types: 'issue'
+          issue-assignees: 'xrkffgg'

.github/workflows/ci.yml

@@ -11,6 +11,12 @@ jobs:
 
       - name: install
         run: yarn install
+      
+      - name: format
+        run: yarn format-check
+
+      - name: test
+        run: yarn test
 
       - name: package
         run: yarn package

.github/workflows/gh-pages.yml

@@ -0,0 +1,19 @@
+name: GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - run: npm install
+      - run: npm run docs:build
+      - name: Deploy
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: ./docs-dist

.github/workflows/preview-build.yml

@@ -0,0 +1,40 @@
+name: Preview Build
+
+on: 
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  build-preview:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+
+      - name: build
+        run: |
+          yarn
+          yarn docs-dev:build
+
+      - run: |
+          zip -r dist.zip docs-dist
+
+      - name: upload dist artifact
+        uses: actions/upload-artifact@v2
+        with:
+          name: dist
+          path: dist.zip
+          retention-days: 5
+
+      - name: Save PR number
+        if: ${{ always() }}
+        run: echo ${{ github.event.number }} > ./pr-id.txt
+
+      - name: Upload PR number
+        if: ${{ always() }}
+        uses: actions/upload-artifact@v2
+        with:
+          name: pr
+          path: ./pr-id.txt

.github/workflows/preview-deploy.yml

@@ -0,0 +1,92 @@
+name: Preview Deploy
+
+on:
+  workflow_run:
+    workflows: ["Preview Build"]
+    types:
+      - completed
+
+jobs:
+  success:
+    runs-on: ubuntu-latest
+    if: github.event.workflow_run.event == 'pull_request' && github.event.workflow_run.conclusion == 'success'
+    steps:
+      - name: download pr artifact
+        uses: dawidd6/action-download-artifact@v2
+        with:
+          workflow: ${{ github.event.workflow_run.workflow_id }}
+          name: pr
+
+      - name: save PR id
+        id: pr
+        run: echo "::set-output name=id::$(<pr-id.txt)"
+
+      - name: download dist artifact
+        uses: dawidd6/action-download-artifact@v2
+        with:
+          workflow: ${{ github.event.workflow_run.workflow_id }}
+          workflow_conclusion: success
+          name: dist
+
+      - run: |
+          unzip dist.zip
+
+      - name: upload surge service
+        id: deploy
+        run: |
+          export DEPLOY_DOMAIN=https://issues-helper-preview-pr-${{ steps.pr.outputs.id }}.surge.sh
+          npx surge --project ./docs-dist --domain $DEPLOY_DOMAIN --token ${{ secrets.SURGE_TOKEN }}
+
+      - name: update status comment
+        uses: actions-cool/maintain-one-comment@v1.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: |
+            🎊 PR Preview has been successfully built and deployed to https://issues-helper-preview-pr-${{ steps.pr.outputs.id }}.surge.sh
+            
+            <img width="300" src="https://user-images.githubusercontent.com/507615/90250366-88233900-de6e-11ea-95a5-84f0762ffd39.png">
+
+            <!-- Sticky Pull Request Comment -->
+          body-include: '<!-- Sticky Pull Request Comment -->'
+          number: ${{ steps.pr.outputs.id }}
+
+      - name: The job failed
+        if: ${{ failure() }}
+        uses: actions-cool/maintain-one-comment@v1.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: |
+            😭 Deploy PR Preview failed.
+
+            <img width="300" src="https://user-images.githubusercontent.com/507615/90250824-4e066700-de6f-11ea-8230-600ecc3d6a6b.png">
+
+            <!-- Sticky Pull Request Comment -->
+          body-include: '<!-- Sticky Pull Request Comment -->'
+          number: ${{ steps.pr.outputs.id }}
+
+  failed:
+    runs-on: ubuntu-latest
+    if: github.event.workflow_run.event == 'pull_request' && github.event.workflow_run.conclusion == 'failure'
+    steps:
+      - name: download pr artifact
+        uses: dawidd6/action-download-artifact@v2
+        with:
+          workflow: ${{ github.event.workflow_run.workflow_id }}
+          name: pr
+
+      - name: save PR id
+        id: pr
+        run: echo "::set-output name=id::$(<pr-id.txt)"
+
+      - name: The job failed
+        uses: actions-cool/maintain-one-comment@v1.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: |
+            😭 Deploy PR Preview failed.
+
+            <img width="300" src="https://user-images.githubusercontent.com/507615/90250824-4e066700-de6f-11ea-8230-600ecc3d6a6b.png">
+
+            <!-- Sticky Pull Request Comment -->
+          body-include: '<!-- Sticky Pull Request Comment -->'
+          number: ${{ steps.pr.outputs.id }}

.github/workflows/preview-start.yml

@@ -0,0 +1,19 @@
+name: Preview Start
+
+on: pull_request_target
+
+jobs:
+  preview:
+    runs-on: ubuntu-latest
+    steps:
+      - name: create
+        uses: actions-cool/maintain-one-comment@v1.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: |
+            ⚡️ Deploying PR Preview...
+
+            <img src="https://user-images.githubusercontent.com/507615/90240294-8d2abd00-de5b-11ea-8140-4840a0b2d571.gif" width="300" />
+
+            <!-- Sticky Pull Request Comment -->
+          body-include: '<!-- Sticky Pull Request Comment -->'

.gitignore

@@ -18,7 +18,7 @@ yarn-error.log*
 
 # dependencies
 node_modules
-yarn.lock
+# yarn.lock
 package-lock.json
 
 # local env files

.prettierignore

@@ -0,0 +1,5 @@
+dist/
+lib/
+docs-dist/
+node_modules/
+src/.umi/

.prettierrc.js

@@ -0,0 +1,6 @@
+const fabric = require('@umijs/fabric');
+
+module.exports = {
+  ...fabric.prettier,
+  arrowParens: 'avoid',
+};

.umirc.dev.ts

@@ -0,0 +1,4 @@
+export default {
+  base: '/',
+  publicPath: '/',
+};

.umirc.ts

@@ -0,0 +1,79 @@
+// more config: https://d.umijs.org/config
+import { defineConfig } from 'dumi';
+
+const name = 'issues-helper';
+
+export default defineConfig({
+  title: 'Issues Helper',
+  mode: 'site',
+  favicon: 'https://avatars1.githubusercontent.com/u/73879334?s=200&v=4',
+  logo: 'https://avatars1.githubusercontent.com/u/73879334?s=200&v=4',
+  exportStatic: {},
+  ssr: {},
+  outputPath: 'docs-dist',
+  hash: true,
+  base: `/${name}/`,
+  publicPath: `/${name}/`,
+  locales: [
+    ['zh-CN', '中文'],
+    ['en-US', 'English'],
+  ],
+  theme: {
+    '@c-primary': '#1890ff',
+  },
+  navs: {
+    'zh-CN': [
+      { title: '指 南', path: '/guide' },
+      { title: '基 础', path: '/base' },
+      { title: '进 阶', path: '/advanced' },
+      { title: '更新日志', path: '/changelog' },
+      { title: '国内镜像', path: 'https://issues-helper.gitee.io' },
+      { title: 'GitHub', path: 'https://github.com/actions-cool/issues-helper' },
+    ],
+    'en-US': [
+      { title: 'Guide', path: '/en-US/guide' },
+      { title: 'Base', path: '/en-US/base' },
+      { title: 'Advanced', path: '/en-US/advanced' },
+      { title: 'Changelog', path: '/en-US/changelog' },
+      { title: 'GitHub', path: 'https://github.com/actions-cool/issues-helper' },
+    ],
+  },
+  menus: {
+    '/guide': [
+      {
+        title: '🍭 介 绍',
+        children: ['/guide/index', '/guide/start'],
+      },
+      {
+        title: '🎁 参 考',
+        path: '/guide/ref',
+      },
+      {
+        title: '🎗 记 录',
+        path: '/guide/note',
+      },
+      {
+        title: '💬 FAQ',
+        path: '/guide/faq',
+      },
+    ],
+    '/en-US/guide': [
+      {
+        title: '🍭 Guide',
+        children: ['/guide/index', '/guide/start'],
+      },
+      {
+        title: '🎁 Reference',
+        path: '/guide/ref',
+      },
+      {
+        title: '🎗 Note',
+        path: '/guide/note',
+      },
+      {
+        title: '💬 FAQ',
+        path: '/guide/faq',
+      },
+    ],
+  },
+});

CHANGELOG.md

@@ -0,0 +1,178 @@
+<!--
+🐞 Bug fix
+🚀 New feature
+💄 Perf
+📝 Docs
+⚡️ Code style
+-->
+
+## v2.5.0
+
+`2021.10.19`
+
+- 🚀 feat: add thanks.
+
+> 🐣 This will be the last version of 2.x, 3.x is under development.
+
+## v2.4.3
+
+`2021.09.13`
+
+- 🚀 feat: default number support `issue-comment`. [#90](https://github.com/actions-cool/issues-helper/pull/90)
+
+## v2.4.2
+
+`2021.09.06`
+
+- 🐞 fix: `doRemoveLabels` when has no label. [#88](https://github.com/actions-cool/issues-helper/pull/88)
+
+## v2.4.1
+
+`2021.09.05`
+
+- 🐞 fix: remove labels define error. [#86](https://github.com/actions-cool/issues-helper/pull/86)
+
+## v2.4.0
+
+`2021.08.15`
+
+- 🚀 feat: support custom repo. [#83](https://github.com/actions-cool/issues-helper/pull/83)
+- 🚀 feat: support default issueNumber get from context. [#81](https://github.com/actions-cool/issues-helper/pull/81)
+- 🐞 fix: action run async. [#79](https://github.com/actions-cool/issues-helper/pull/79)
+
+## v2.3.1
+
+`2021.08.09`
+
+- ⚡️ refactor: extract exclude-labels array to outer scope. [#75](https://github.com/actions-cool/issues-helper/pull/75) [@meteorlxy](https://github.com/meteorlxy)
+
+## v2.3.0
+
+`2021.08.09`
+
+- 🚀 feat: add exclude-labels for `check-inactive` `close-issues` `lock-issues`. [#74](https://github.com/actions-cool/issues-helper/pull/74)
+
+## v2.2.1
+
+`2021.03.21`
+
+- fix: list comment page lost in `find-comments`. [#66](https://github.com/actions-cool/issues-helper/pull/66)
+
+## v2.2.0
+
+`2021.03.21`
+
+- feat: Added `title-excludes` parameter to `check-issue`. [#65](https://github.com/actions-cool/issues-helper/pull/65)
+
+## v2.1.2
+
+`2021.02.19`
+
+- feat: update/delete comment support find-comments out. [#63](https://github.com/actions-cool/issues-helper/pull/63)
+
+## v2.1.1
+
+`2021.02.03`
+
+- fix: api request limit. [#57](https://github.com/actions-cool/issues-helper/pull/57)
+- chore: add catch. [#59](https://github.com/actions-cool/issues-helper/pull/59)
+
+## v2.1.0
+
+`2021.02.02`
+
+- feat: add create-label. [#54](https://github.com/actions-cool/issues-helper/pull/54)
+
+## v2.0.0
+
+`2021.01.26`
+
+- refactor: add require-permission default. [#51](https://github.com/actions-cool/issues-helper/pull/51)
+
+## v1.12
+
+> It will be the last version of 1.x
+
+`2021.01.26`
+
+- feat: add require-permission. [#46](https://github.com/actions-cool/issues-helper/pull/46) [#48](https://github.com/actions-cool/issues-helper/pull/48)
+- feat: add lock-reason. [#49](https://github.com/actions-cool/issues-helper/pull/49)
+
+## v1.11
+
+`2021.01.14`
+
+- feat: add question mark duplicate. [#38](https://github.com/actions-cool/issues-helper/pull/38)
+- perf: expand duplicate action. [#40](https://github.com/actions-cool/issues-helper/pull/40)
+
+## v1.10
+
+`2021.01.12`
+
+- fix: duplicate labels set. [#36](https://github.com/actions-cool/issues-helper/pull/36)
+
+## v1.9
+
+`2021.01.11`
+
+- feat: add random to. [#35](https://github.com/actions-cool/issues-helper/pull/35)
+
+## v1.8
+
+`2021.01.07`
+
+- [#31](https://github.com/actions-cool/issues-helper/pull/31)
+  - refactor: split content
+  - feat: add `remove-labels` for duplicate
+  - docs: optimize website
+
+## v1.7
+
+`2021.01.02`
+
+- [#27](https://github.com/actions-cool/issues-helper/pull/27)
+  - feat: add `month-statistics`
+  - fix: query issues less because pages max 100
+  - fix: js nested `require`
+
+## v1.6
+
+`2020.12.30`
+
+- perf: optimize duplicate. [#24](https://github.com/actions-cool/issues-helper/pull/24)
+
+## v1.5
+
+`2020.12.30`
+
+- feat: add `mark-duplicate`. [#23](https://github.com/actions-cool/issues-helper/pull/23)
+
+## v1.4
+
+`2020.12.29`
+
+- fix: perfect `inactive-day` check. [#22](https://github.com/actions-cool/issues-helper/pull/22)
+
+## v1.3
+
+`2020.12.28`
+
+- feat: add welcome. [#19](https://github.com/actions-cool/issues-helper/pull/19)
+
+## v1.2
+
+`2020.12.25`
+
+- feat: add check-issue & remove labels. [#12](https://github.com/actions-cool/issues-helper/pull/12)
+
+## v1.1
+
+`2020.12.24`
+
+- fix: yml not support array. [#11](https://github.com/actions-cool/issues-helper/pull/11)
+
+## v1
+
+`2020.12.23`
+
+🎉 First release.

CONTRIBUTING.md

@@ -0,0 +1,9 @@
+## release
+
+完整版本在网页上进行
+
+### 替换小版本
+- 删除 v2 tag
+  - git push origin :refs/tags/v2
+- 把最新的 v2.1.0 推送到 远端 v2 tag
+  - git push origin v2.1.0:v2

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2020 xrkffgg
+Copyright (c) 2020-present xrkffgg
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.zh-CN.md

@@ -1,858 +0,0 @@
-# 🤖 Issues 助手
-
-[English](./README.md) | 简体中文
-
-[![](https://img.shields.io/github/workflow/status/actions-cool/issues-helper/ci?style=flat-square)](https://github.com/actions-cool/issues-helper/actions) [![](https://img.shields.io/badge/marketplace-issues--helper-red?style=flat-square)](https://github.com/marketplace/actions/issues-helper) [![](https://img.shields.io/github/stars/actions-cool/issues-helper?style=flat-square)](https://github.com/actions-cool/issues-helper/stargazers) [![](https://img.shields.io/github/v/release/actions-cool/issues-helper?style=flat-square&color=orange)](https://github.com/actions-cool/issues-helper/releases) [![](https://img.shields.io/badge/discussions-on%20github-blue?style=flat-square&color=%2308979c)](https://github.com/actions-cool/issues-helper/discussions) [![](https://img.shields.io/github/license/actions-cool/issues-helper?style=flat-square)](https://github.com/actions-cool/issues-helper/blob/main/LICENSE)
-
-一个帮你管理 issues 的 GitHub Action
-
-在线文档 | [更新日志](./changelog.zh-CN.md)
-
-## 😎 为什么用 GitHub Action？
-
-1. 完全免费。
-2. 全自动操作。
-3. 托管于 GitHub 服务器，只要 GitHub 不宕机，它就会一直跑下去。
-
-> Private 项目每月有 2000 次的限制，[具体查看](https://github.com/settings/billing)。Public 项目无限制。
-
-## 列 表
-
-- ⭐ 基 础
-  - [`add-assignees`](#add-assignees)
-  - [`add-labels`](#add-labels)
-  - [`close-issue`](#close-issue)
-  - [`create-comment`](#create-comment)
-  - [`create-issue`](#create-issue)
-  - [`delete-comment`](#delete-comment)
-  - [`lock-issue`](#lock-issue)
-  - [`open-issue`](#open-issue)
-  - [`remove-assignees`](#remove-assignees)
-  - [`remove-labels`](#remove-labels)
-  - [`set-labels`](#set-labels)
-  - [`unlock-issue`](#unlock-issue)
-  - [`update-comment`](#update-comment)
-  - [`update-issue`](#update-issue)
-- ⭐ 进 阶
-  - [`check-inactive`](#check-inactive)
-  - [`check-issue`](#check-issue)
-  - [`close-issues`](#close-issues)
-  - [`find-comments`](#find-comments)
-  - [`lock-issues`](#lock-issues)
-- 🌰 例 子
-  - [`find-comments + create-comment + update-comment`](#find-comments--create-comment--update-comment)
-
-## 🚀 使 用
-
-### ⭐ 基 础
-
-为了更好的展示功能，下面以实际场景举例，请灵活参考。
-
-#### `add-assignees`
-
-当一个 issue 新增或修改时，将这个 issue 指定某人或多人。
-
-```yml
-name: Add Assigness
-
-on:
-  issues:
-    types: [opened, edited]
-
-jobs:
-  add-assigness:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Add assigness
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'add-assignees'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          assignees: 'xxx' or 'xx1,xx2'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| assignees | 指定人。当不填或者为空字符时，不操作 | string | ✖ | v1 |
-
-- `actions` 支持多个，需用逗号隔开。如：`add-assignees,add-labels`
-- 其中的 `name` 可根据自行根据实际情况修改
-- [on 参考](#github-docs)
-- `${{ github.event.issue.number }}` 表示当前 issue，[更多参考](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events)
-- `assignees` 支持多个，需用逗号隔开。注意设置多个，需使用v1.1以上版本
-
-⏫ [返回列表](#列-表)
-
-#### `add-labels`
-
-当一个新增的 issue 内容不包含指定格式时，为这个 issue 添加 labels。
-
-```yml
-name: Add Labels
-
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  add-labels:
-    runs-on: ubuntu-latest
-    if: contains(github.event.issue.body, 'xxx') == false
-    steps:
-      - name: Add labels
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'add-labels'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          labels: 'bug' or 'bug1,bug2'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| labels | 新增的 labels。当不填或者为空字符时，不新增 | string | ✖ | v1 |
-
-- `labels` 支持多个，需用逗号隔开。注意设置多个，需使用v1.1以上版本
-
-⏫ [返回列表](#列-表)
-
-#### `close-issue`
-
-关闭指定 issue。
-
-```yml
-- name: Close issue
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'close-issue'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: xxx
-      body: 'This is auto closed.'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `create-comment`
-
-当新增一个指定 label 时，对该 issue 进行评论。
-
-```yml
-name: Create Comment
-
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  create-comment:
-    runs-on: ubuntu-latest
-    if: github.event.label.name == 'xxx'
-    steps:
-      - name: Create comment
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'create-comment'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          body: |
-            Hello ${{ github.event.issue.user.login }}. Add some comments.
-
-            你好 ${{ github.event.issue.user.login }}。巴拉巴拉。
-          contents: '+1' or '+1,heart'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| body | 新增评论的内容  | string | ✖ | v1 |
-| contents | 为新增评论的增加 [reaction](#reactions-types) | string | ✖ | v1 |
-
-- `body` 默认为：`Currently at ${owner}/${repo}. And this is default comment.`
-  - 其中 `${owner}/${repo}` 表示当前仓库
-- 返回 `comment-id`，可用于之后操作。[用法参考](#outputs-使用)
-- `${{ github.event.issue.user.login }}` 表示该 issue 的创建者
-- `contents` 支持多个，需用逗号隔开。注意设置多个，需使用v1.1以上版本
-
-⏫ [返回列表](#列-表)
-
-#### `create-issue`
-
-感觉新增 issue 使用场景不多。这里举例，每月 1 号 UTC 00:00 新增一个 issue。
-
-```yml
-name: Create Issue
-
-on:
-  schedule:
-    - cron: "0 0 1 * *"
-
-jobs:
-  create-issue:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Create issue
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'create-issue'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          title: 'xxxx'
-          body: 'xxxx'
-          labels: 'xx'
-          assignees: 'xxx'
-          contents: '+1'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| title | 新增 issue 的标题 | string | ✖ | v1 |
-| body | 新增 issue 的内容 | string | ✖ | v1 |
-| labels | 为新增 issue 添加 labels | string | ✖ | v1 |
-| assignees | 为新增 issue 添加 assignees | string | ✖ | v1 |
-| contents | 为新增 issue 增加 [reaction](#reactions-types) | string | ✖ | v1 |
-
-- `title` 默认为：`Default Title`
-- 返回 `issue-number`，[用法参考](#outputs-使用)
-
-⏫ [返回列表](#列-表)
-
-#### `delete-comment`
-
-根据 [`comment-id`](#comment-id) 删除指定评论。
-
-```yml
-- name: Delete comment
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'delete-comment'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      comment-id: xxx
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| comment-id | 指定的 comment | number | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `lock-issue`
-
-当新增 `invalid` label 时，对该 issue 进行锁定。
-
-```yml
-name: Lock Issue
-
-on:
-  issues:
-    types: [labeled]
-
-jobs:
-  lock-issue:
-    runs-on: ubuntu-latest
-    if: github.event.label.name == 'invalid'
-    steps:
-      - name: Lock issue
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'lock-issue'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `open-issue`
-
-打开指定 issue。
-
-```yml
-- name: Open issue
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'open-issue'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: xxx
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `remove-assignees`
-
-移除 issue 指定人员。
-
-```yml
-- name: Remove assignees
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'remove-assignees'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: ${{ github.event.issue.number }}
-      assignees: 'xx'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| assignees | 移除的指定人。当为空字符时，不进行移除 | string | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `remove-labels`
-
-移除指定 labels。
-
-```yml
-- name: Remove labels
-    uses: actions-cool/issues-helper@v1.2
-    with:
-      actions: 'remove-labels'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: ${{ github.event.issue.number }}
-      labels: 'xx'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1.2 |
-| token | [token 说明](#token) | string | ✔ | v1.2 |
-| issue-number | 指定的 issue | number | ✔ | v1.2 |
-| labels | 移除的 labels。当为空字符时，不进行移除 | string | ✔ | v1.2 |
-
-- `labels` 支持多个，如 `x1,x2,x3`，只会移除 issue 已添加的 labels
-
-⏫ [返回列表](#列-表)
-
-#### `set-labels`
-
-替换 issue 的 labels。
-
-```yml
-- name: Set labels
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'set-labels'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: ${{ github.event.issue.number }}
-      labels: 'xx'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| labels | labels 设置。当空字符时，会移除所有 | string | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `unlock-issue`
-
-解锁指定 issue。
-
-```yml
-- name: Unlock issue
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'unlock-issue'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: ${{ github.event.issue.number }}
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-
-⏫ [返回列表](#列-表)
-
-#### `update-comment`
-
-根据 [`comment-id`](#comment-id) 更新指定评论。
-
-下面的例子展示的是，为每个新增的 comment 增加 👀 。
-
-```yml
-name: Add eyes to each comment
-
-on:
-  issue_comment:
-    types: [created]
-
-jobs:
-  update-comment:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Update comment
-          uses: actions-cool/issues-helper@v1
-          with:
-            actions: 'update-comment'
-            token: ${{ secrets.GITHUB_TOKEN }}
-            comment-id: ${{ github.event.comment.id }}
-            contents: 'eyes'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| comment-id | 指定的 comment | number | ✔ | v1 |
-| body | 更新 comment 的内容 | string | ✖ | v1 |
-| update-mode | 更新模式。默认 `replace` 替换，`append` 附加 | string | ✖ | v1 |
-| contents | 增加 [reaction](#reactions-types) | string | ✖ | v1 |
-
-- `body` 不填时，会保持原有
-- `update-mode` 为 `append` 时，会进行附加操作。非 `append` 都会进行替换。仅对 `body` 生效
-
-⏫ [返回列表](#列-表)
-
-#### `update-issue`
-
-根据 `issue-number` 更新指定 issue。
-
-```yml
-- name: Update issue
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'update-issue'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: ${{ github.event.issue.number }}
-      state: 'open'
-      title: 'xxx'
-      body: 'xxxx'
-      update-mode: 'replace'
-      labels: 'xx'
-      assignees: 'xxx'
-      contents: '+1'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| state | 修改 issue 的状态，可选值 `open` `closed` | string | ✖ | v1 |
-| title | 修改 issue 的标题 | string | ✖ | v1 |
-| body | 修改 issue 的内容 | string | ✖ | v1 |
-| update-mode | 更新模式。默认 `replace` 替换，`append` 附加 | string | ✖ | v1 |
-| labels | 替换 issue 的 labels | string | ✖ | v1 |
-| assignees | 替换 issue 的 assignees | string | ✖ | v1 |
-| contents | 增加 [reaction](#reactions-types) | string | ✖ | v1 |
-
-- `state` 默认为 `open`
-- 当可选项不填时，会保持原有
-
-⏫ [返回列表](#列-表)
-
-### ⭐ 进 阶
-
-进阶用法不建议 actions 多个一次同时使用。
-
-#### `check-inactive`
-
-每月 1 号 UTC 0 时，对所有 30 天以上未活跃的 issues 增加 `inactive` 标签。
-
-```yml
-name: Check inactive
-
-on:
-  schedule:
-    - cron: "0 0 1 * *"
-
-jobs:
-  check-inactive:
-    runs-on: ubuntu-latest
-    steps:
-      - name: check-inactive
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'check-inactive'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          inactive-day: 30
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ | v1 |
-| labels | 标签筛选 | string | ✖ | v1 |
-| issue-state | 状态筛选 | string | ✖ | v1 |
-| issue-assignee | 指定人筛选 | string | ✖ | v1 |
-| issue-creator | 创建人筛选 | string | ✖ | v1 |
-| issue-mentioned | 提及人筛选 | string | ✖ | v1 |
-| body-includes | 包含内容筛选 | string | ✖ | v1 |
-| title-includes | 包含标题筛选 | string | ✖ | v1 |
-| inactive-day | 非活跃天数筛选 | number | ✖ | v1 |
-| inactive-label | 新增标签名称 | string | ✖ | v1 |
-
-- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
-- `issue-state`：默认为 `all`。可选值 `open` `closed`，非这 2 项时，均为 `all`
-- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
-- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
-- `inactive-label`：默认为 `inactive`，可自定义其他。当项目未包含该 label 时，会自动新建
-
-⏫ [返回列表](#列-表)
-
-#### `check-issue`
-
-根据传入的参数和 `issue-number` 来检查该 issue 是否满足条件，返回一个布尔值。
-
-下面的例子效果是：当 issue 新开时，校验当前 issue 指定人是否包含 `x1` 或者 `x2`，满足一个指定人即可校验通过，同时校验标题是否满足条件。条件如下：
-
-```js
-x1 + y1
-x2 + y1
-x1 + y2
-x2 + y2
-
-"x1y3y2"  true
-"1x2y"    false
-"y2 x1"   true
-"x1"      false
-```
-
-```yml
-name: Check Issue
-
-on:
-  issues:
-    types: [edited]
-
-jobs:
-  check-issue:
-    runs-on: ubuntu-latest
-    steps:
-      - name: check-issue
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'check-issue'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          assignee-includes: 'x1,x2'
-          title-includes: 'x1,x2/y1,y2'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1.2 |
-| token | [token 说明](#token) | string | ✔ | v1.2 |
-| issue-number | 指定的 issue | number | ✔ | v1.2 |
-| assignee-includes | 是否包含指定人 | string | ✖ | v1.2 |
-| title-includes | 标题包含校验 | string | ✖ | v1.2 |
-| body-includes | 内容包含校验 | string | ✖ | v1.2 |
-
-- `title-includes` `body-includes` 支持格式 `x1,x2` 或者 `x1,x2/y1,y2`。只支持两个层级
-- 返回 `check-result`
-
-⏫ [返回列表](#列-表)
-
-#### `close-issues`
-
-每 7 天 UTC 0 时，关闭已填加 `need info` label 且 7 天以上未活跃的 issues。
-
-```yml
-name: Check need info
-
-on:
-  schedule:
-    - cron: "0 0 */7 * *"
-
-jobs:
-  check-need-info:
-    runs-on: ubuntu-latest
-    steps:
-      - name: close-issues
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'close-issues'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          labels: 'need info'
-          inactive-day: 7
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ | v1 |
-| labels | 标签筛选 | string | ✖ | v1 |
-| issue-assignee | 指定人筛选 | string | ✖ | v1 |
-| issue-creator | 创建人筛选 | string | ✖ | v1 |
-| issue-mentioned | 提及人筛选 | string | ✖ | v1 |
-| body-includes | 包含内容筛选 | string | ✖ | v1 |
-| title-includes | 包含标题筛选 | string | ✖ | v1 |
-| inactive-day | 非活跃天数筛选 | number | ✖ | v1 |
-
-- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
-- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
-- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
-
-⏫ [返回列表](#列-表)
-
-#### `find-comments`
-
-查找当前仓库 1 号 issue 中，创建者是 k ，内容包含 `this` 的评论列表。
-
-```yml
-- name: Find comments
-    uses: actions-cool/issues-helper@v1
-    with:
-      actions: 'find-comments'
-      token: ${{ secrets.GITHUB_TOKEN }}
-      issue-number: 1
-      comment-auth: 'k'
-      body-includes: 'this'
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| issue-number | 指定的 issue | number | ✔ | v1 |
-| comment-auth | 评论创建者，不填时会查询所有 | string | ✖ | v1 |
-| body-includes | 评论内容包含过滤，不填时无校验 | string | ✖ | v1 |
-| direction | 返回 `comments` 排序 | string | ✖ | v1 |
-
-- 返回 `comments`，格式如下：
-
-```js
-[
-  {id: 1, auth: 'x', body: 'xxx', created: '', updated: ''},
-  {id: 2, auth: 'x', body: 'xxx', created: '', updated: ''},
-]
-```
-
-- `direction` 默认为升序，只有设置 `desc` 时，会返回降序
-- 返回数组中 `created` `updated`，由所处环境决定，会是 UTC +0
-
-⏫ [返回列表](#列-表)
-
-#### `lock-issues`
-
-每 3 个月 1 号 UTC 0 时，锁定已填加 `inactive` label 且 128 天以上未活跃的所有 issues。
-
-```yml
-name: Lock inactive issues
-
-on:
-  schedule:
-    - cron: "0 0 1 */3 *"
-
-jobs:
-  lock-issues:
-    runs-on: ubuntu-latest
-    steps:
-      - name: lock-issues
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'lock-issues'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          labels: 'inactive'
-          inactive-day: 128
-```
-
-| 参数 | 描述 | 类型 | 必填 | 版本 |
-| -- | -- | -- | -- | -- |
-| actions | 操作类型 | string | ✔ | v1 |
-| token | [token 说明](#token) | string | ✔ | v1 |
-| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ | v1 |
-| labels | 标签筛选 | string | ✖ | v1 |
-| issue-state | 状态筛选 | string | ✖ | v1 |
-| issue-assignee | 指定人筛选 | string | ✖ | v1 |
-| issue-creator | 创建人筛选 | string | ✖ | v1 |
-| issue-mentioned | 提及人筛选 | string | ✖ | v1 |
-| body-includes | 包含内容筛选 | string | ✖ | v1 |
-| title-includes | 包含标题筛选 | string | ✖ | v1 |
-| inactive-day | 非活跃天数筛选 | number | ✖ | v1 |
-
-- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
-- `issue-state`：默认为 `all`。可选值 `open` `closed`，非这 2 项时，均为 `all`
-- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
-- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
-
-⏫ [返回列表](#列-表)
-
-## 🌰 例 子
-
-灵活参考。
-
-### `find-comments + create-comment + update-comment`
-
-假设场景：当添加了 `watch` label 的 issue 修改时，查找是否有 k 创建的包含 `error` 的评论，如果只有一个，则更新该 comment，如果没有，则新增一个 comment。
-
-```yml
-name: Test
-
-on:
-  isssue:
-    types: [edited]
-
-jobs:
-  do-test:
-    runs-on: ubuntu-latest
-    if: github.event.label.name == 'watch'
-    steps:
-      - name: find comments
-        uses: actions-cool/issues-helper@v1
-        id: fcid
-        with:
-          actions: 'find-comments'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          comment-auth: k
-          body-includes: 'error'
-
-      - name: create comment
-        if: ${{ steps.fcid.outputs.comments.length == 0 }}
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'create-comment'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          issue-number: ${{ github.event.issue.number }}
-          body: 'Some error!'
-
-      - name: update comment
-        if: ${{ steps.fcid.outputs.comments.length == 1 }}
-        uses: actions-cool/issues-helper@v1
-        with:
-          actions: 'update-comment'
-          token: ${{ secrets.GITHUB_TOKEN }}
-          comment-id: ${{ steps.fcid.outputs.comments[0].id }}
-          body: 'Some error again!'
-          update-mode: 'append'
-```
-
-⏫ [返回列表](#列-表)
-
-## 🎁 参 考
-
-### token
-
-需拥有 push 权限的人员 token。
-
-- [个人 token 申请](https://github.com/settings/tokens)
-  - 需勾选 `Full control of private repositories`
-- 项目添加 secrets
-  - 选择 settings，选择 secrets，选择 `New repository secret`
-  - `Name` 与 actions 中保持一致
-  - `Value` 填写刚才个人申请的 token
-
-当 actions 不填写 token 时，或项目未添加对应 secrets 时，会默认为 github-actions <kbd>bot</kbd>。
-
-⏫ [返回列表](#列-表)
-
-### `outputs` 使用
-
-```yml
-- name: Create issue
-  uses: actions-cool/issues-helper@v1
-  id: createissue
-  with:
-    actions: 'create-issue'
-    token: ${{ secrets.GITHUB_TOKEN }}
-- name: Check outputs
-  run: echo "Outputs issue_number is ${{ steps.createissue.outputs.issue-number }}"
-```
-
-### GitHub Docs
-
-- [GitHub Actions 语法](https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#on)
-- [工作流触发机制](https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows)
-
-⏫ [返回列表](#列-表)
-
-### Reactions types
-
-| content | emoji |
-| -- | -- |
-| `+1` | 👍 |
-| `-1` | 👎 |
-| `laugh` | 😄 |
-| `confused` | 😕 |
-| `heart` | ❤️ |
-| `hooray` | 🎉 |
-| `rocket` | 🚀 |
-| `eyes` | 👀 |
-
-⏫ [返回列表](#列-表)
-
-### `comment-id`
-
-点击某个评论右上角 `···` 图标，选择 `Copy link`，url 末尾数字即是 `comment_id`。
-
-⏫ [返回列表](#列-表)
-
-## Actions 模板
-
-- 可直接使用这个 [GitHub Actions workflow template](https://github.com/actions-cool/.github) 仓库的模板
-
-- 个人练习和测试 [Actions](https://github.com/xrkffgg/test-ci) 的仓库
-
-## 💖 谁在使用？
-
-你可以来以下项目进行参考。欢迎在 [**这里**](https://github.com/actions-cool/issues-helper/issues/6) 留言。
-
-同时，如果你在使用过程中有什么疑问，也可以在 issue 或者 discussion 中进行提问和查询。
-
-<table>
-  <tr>
-    <td align="center">
-      <a href="https://github.com/ant-design/ant-design">
-        <img src="https://avatars1.githubusercontent.com/u/12101536?s=200&v=4" width="46" />
-      </a>
-      <br/>
-      <strong>ant-design</strong>
-    </td>
-    <td align="center">
-      <a href="https://github.com/vueComponent/ant-design-vue">
-        <img src="https://avatars2.githubusercontent.com/u/32120805?s=200&v=4" width="46" />
-      </a>
-      <br/>
-      <strong>ant-design-vue</strong>
-    </td>
-    <td align="center">
-      <a href="https://github.com/AttoJS/vue-request">
-        <img src="https://raw.githubusercontent.com/AttoJS/art/master/vue-request-logo.png" width="46" />
-      </a>
-      <br/>
-      <strong>vue-request</strong>
-    </td>
-  </tr>
-</table>
-
-## LICENSE
-
-[MIT](https://github.com/actions-cool/issues-helper/blob/main/LICENSE)

USERS.js

@@ -0,0 +1,100 @@
+// **************************************************************************
+// step1: add to end
+// step2: npm run users
+
+/**
+ * @param {string} url        github地址
+ * @param {string} logo       logo地址
+ * @param {string} width      自定义宽度，设置 auto 用于长型 logo
+ */
+
+const users = [
+  {
+    url: 'https://github.com/ant-design/ant-design',
+    logo: 'https://avatars1.githubusercontent.com/u/12101536?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/vueComponent/ant-design-vue',
+    logo: 'https://avatars1.githubusercontent.com/u/32120805?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/umijs/dumi',
+    logo: 'https://avatars1.githubusercontent.com/u/33895495?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/umijs/umi',
+    logo: 'https://avatars1.githubusercontent.com/u/33895495?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/AttoJS/vue-request',
+    logo: 'https://user-images.githubusercontent.com/29775873/129506134-55044c85-24cd-47d3-81ef-dba842214d71.png'
+  },
+  {
+    url: 'https://github.com/mui-org/material-ui',
+    logo: 'https://avatars2.githubusercontent.com/u/33663932?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/lijinke666/react-music-player',
+    logo: 'https://user-images.githubusercontent.com/29775873/129506058-b0d8c741-f73a-496c-98de-7db2fb586db7.png'
+  },
+  {
+    url: 'https://github.com/ant-design-blazor/ant-design-blazor',
+    logo: 'https://user-images.githubusercontent.com/29775873/129505619-5abddb68-8663-4c71-b7d2-049c716aab26.png'
+  },
+  {
+    url: 'https://github.com/zoo-js/zoo',
+    logo: 'https://avatars1.githubusercontent.com/u/70757173?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/react-component',
+    logo: 'https://avatars3.githubusercontent.com/u/9441414?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/ant-design/pro-components',
+    logo: 'https://avatars1.githubusercontent.com/u/12101536?s=200&v=4'
+  },
+  {
+    url: 'https://github.com/prettier/prettier',
+    logo: 'https://user-images.githubusercontent.com/29775873/129505900-ca248179-2435-429d-9fd3-779206bcd899.png',
+  },
+  {
+    url: 'https://github.com/vuejs/jsx-next',
+    logo: 'https://avatars.githubusercontent.com/u/6128107?s=200&v=4',
+  },
+  {
+    url: 'https://github.com/vitejs/vite',
+    logo: 'https://avatars.githubusercontent.com/u/65625612?s=200&v=4',
+  },
+  {
+    url: 'https://github.com/jdf2e/nutui',
+    logo: 'https://img14.360buyimg.com/imagetools/jfs/t1/167902/2/8762/791358/603742d7E9b4275e3/e09d8f9a8bf4c0ef.png',
+  },
+  {
+    width: 'auto',
+    url: 'https://github.com/alibaba/formily',
+    logo: 'https://img.alicdn.com/imgextra/i2/O1CN01Kq3OHU1fph6LGqjIz_!!6000000004056-55-tps-1141-150.svg',
+  },
+  {
+    url: 'https://github.com/vuepress/vuepress-next',
+    logo: 'https://v2.vuepress.vuejs.org/images/hero.png',
+  },
+  {
+    url: 'https://github.com/TuSimple/naive-ui',
+    logo: 'https://camo.githubusercontent.com/b8ebecade711b9ae1fa306e7a1c9dd680fb56b0e2b9f015fec9cbad343570353/68747470733a2f2f6e6169766575692e6f73732d636e2d686f6e676b6f6e672e616c6979756e63732e636f6d2f6e616976656c6f676f2e737667',
+  },
+  {
+    url: 'https://github.com/element-plus/element-plus',
+    logo: 'https://avatars.githubusercontent.com/u/68583457',
+  },
+  {
+    url: 'https://github.com/antvis/S2',
+    logo: 'https://gw.alipayobjects.com/mdn/rms_56cbb2/afts/img/A*TI8XSK3W0EkAAAAAAAAAAAAAARQnAQ',
+  },
+];
+
+// **************************************************************************
+module.exports = {
+  users
+};
+
+// **************************************************************************

action.yml

@@ -1,15 +1,21 @@
 name: 'Issues Helper'
-description: 'A GitHub Action to help you manage issues'
+description: 'A GitHub Action that easily helps you automatically manage issues'
 author: 'xrkffgg'
+
+# https://actions-cool.github.io/github-action-branding/
 branding:
   icon: 'message-square'
   color: 'black'
+
 inputs:
   actions:
     description: 'Action name'
   token:
     description: 'Github_token'
     default: ${{ github.token }}
+  repo:
+    description: 'The repositorie'
+
   issue-number:
     description: 'Issue-number'
   comment-id:
@@ -20,8 +26,18 @@ inputs:
     description: 'Issue title'
   assignees:
     description: 'Issue assignees'
+  random-to:
+    description: 'Issue assignees random to'
+  # label
   labels:
     description: 'Issue labels'
+  label-name:
+    description: 'Create label name'
+  label-color:
+    description: 'Create label color, default #ededed'
+  label-desc:
+    description: 'Create label description'
+
   state:
     description: 'Issue state'
   update-mode:
@@ -30,12 +46,19 @@ inputs:
     description: 'Issue reactions emoji'
   direction:
     description: 'Find comments direction'
+
+  # comments
   comment-auth:
     description: 'Find comments query auth'
+  out-comments:
+    description: 'Find comments out comments'
   assignee-includes:
     description: 'Check use'
   body-includes:
     description: 'Query use'
+  # check
+  title-excludes:
+    description: 'Remove some to check title whether empty.'
   title-includes:
     description: 'Query use'
   issue-creator:
@@ -44,12 +67,34 @@ inputs:
     description: 'Query use'
   issue-mentioned:
     description: 'Query use'
+  issue-contents:
+    description: 'For welcome'
   issue-state:
     description: 'Query use'
   inactive-day:
     description: 'Query use'
+  lock-reason:
+    description: 'The reason lock issue'
   inactive-label:
     description: 'Issue label set use'
+  exclude-labels:
+    description: 'Query issues exclude labels'
+
+  duplicate-command:
+    description: 'For mark-duplicate'
+  duplicate-labels:
+    description: 'For mark-duplicate add labels'
+  require-permission:
+    description: 'Only the allow can do. Possible admin, write, read, and none.'
+  remove-labels:
+    description: 'For remove labels'
+  close-issue:
+    description: 'For mark-duplicate'
+  count-lables:
+    description: 'For month-statistics'
+  count-comments:
+    description: 'For month-statistics'
+
 outputs:
   issue-number:
     description: 'Create Issue Number'
@@ -59,6 +104,7 @@ outputs:
     description: 'Find comments'
   check-result:
     description: 'Check issue'
+
 runs:
   using: node12
   main: 'dist/index.js'

changelog.md

@@ -1,41 +0,0 @@
-# ✨ Changelog
-
-## Version rules
-
-- Use two-level semantic version, such as v1, v1.1, v2, v2.1
-- v1 represents the initial version
-- The fixes and additions to the v1 version will be released to the v1.1 version
-- When the released v1.x runs stable for a certain period of time, release the advanced v2 version
-
-## Version selection
-
-- It is recommended to use the latest releases version. It can be seen in [releases](https://github.com/actions-cool/issues-helper/releases)
-
-- You can also refer to the update log below to select the version
-
-- It also supports the direct use of branch versions. Such as:
-
-```yml
-- name: Issues Helper
-  uses: actions-cool/issues-helper@main
-```
-
-## Change Log
-
-### v1.2
-
-`2020.12.25`
-
-- feat: add check-issue & remove labels. [#12](https://github.com/actions-cool/issues-helper/pull/12)
-
-### v1.1
-
-`2020.12.24`
-
-- fix: yml not support array. [#11](https://github.com/actions-cool/issues-helper/pull/11)
-
-### v1
-
-`2020.12.23`
-
-🎉 First release.

changelog.zh-CN.md

@@ -1,41 +0,0 @@
-# ✨ 更新日志
-
-## 版本规则
-
-- 采用两级语义化版本，如v1、v1.1、v2、v2.1
-- v1 表示初始版本
-- 对 v1 版本的修复和新增会发布到 v1.1 版本
-- 当发布的 v1.x 运行一定时间稳定后，发布进阶 v2 版本
-
-## 版本选择
-
-- 建议采用最新 releases 版本。可在 [releases](https://github.com/actions-cool/issues-helper/releases) 看到
-
-- 同时也可参照下面的更新日志来选择版本
-
-- 也支持直接使用分支版本。如：
-
-```yml
-- name: Issues Helper
-  uses: actions-cool/issues-helper@main
-```
-
-## 更新日志
-
-### v1.2
-
-`2020.12.25`
-
-- feat: add check-issue & remove labels. [#12](https://github.com/actions-cool/issues-helper/pull/12)
-
-### v1.1
-
-`2020.12.24`
-
-- fix: yml not support array. [#11](https://github.com/actions-cool/issues-helper/pull/11)
-
-### v1
-
-`2020.12.23`
-
-🎉 First release.

docs/advanced.en-US.md

@@ -0,0 +1,262 @@
+---
+toc: menu
+---
+
+# 🌟 Advanced
+
+Advanced usage is not recommended to use multiple actions at the same time.
+
+## `check-inactive`
+
+At UTC 0 on the 1st of each month, add the `inactive` tag to all issues that have not been active for more than 30 days.
+
+```yml
+name: Check inactive
+
+on:
+  schedule:
+    - cron: "0 0 1 * *"
+
+jobs:
+  check-inactive:
+    runs-on: ubuntu-latest
+    steps:
+      - name: check-inactive
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'check-inactive'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          inactive-day: 30
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) for this comment | string | ✖ |
+| labels | Labels filtering | string | ✖ |
+| issue-state | State filtering | string | ✖ |
+| issue-assignee | Assignee filtering | string | ✖ |
+| issue-creator | Creator filtering | string | ✖ |
+| issue-mentioned | Mentioned filtering | string | ✖ |
+| body-includes | Body filtering | string | ✖ |
+| title-includes | Title filtering | string | ✖ |
+| inactive-day | Inactive days filtering | number | ✖ |
+| inactive-label | The label name adding | string | ✖ |
+| exclude-labels | Exclude labels filtering | string | ✖ |
+
+- `labels`: When there are multiple, the query will have multiple at the same time. If not entered, all
+- `issue-state`: The default is `all`. Optional value `open` `closed`, when these 2 items are not, both are `all`
+- `issue-assignee`: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Entering `none` will query issues for which the specified person is not added
+- `inactive-day`: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, all
+- `inactive-label`: The default is `inactive`, others can be customized. When the project does not contain the label, it will be created automatically
+
+## `check-issue`
+
+Check whether the issue meets the conditions according to the passed parameters and `issue-number`, and return a boolean value.
+
+The effect of the following example is: when an issue is newly opened, verify whether the current issue designator contains `x1` or `x2`.
+
+If one designated person is satisfied, the verification will pass, and at the same time, verify whether the title meets the conditions.
+
+[Check rules](/en-US/guide/ref#-includes-check-rules)
+
+```yml
+name: Check Issue
+
+on:
+  issues:
+    types: [edited]
+
+jobs:
+  check-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: check-issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'check-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          assignee-includes: 'x1,x2'
+          title-includes: 'x1,x2/y1,y2'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| assignee-includes | Assignees contains check | string | ✖ |
+| title-includes | Title contains check | string | ✖ |
+| title-excludes | Check whether the title is empty after removing the default title | string | ✖ |
+| body-includes | Body contains check | string | ✖ |
+
+- `title-includes` `body-includes` supports the format `x1,x2` or `x1,x2/y1,y2`. Only supports two levels
+- Return `check-result`, due to yml reasons, the judgment condition is `if: steps.xxid.outputs.check-result =='true'`
+
+## `close-issues`
+
+Every 7 days at UTC 0, close the issues that have been filled with the `need info` label and have not been active for more than 7 days.
+
+```yml
+name: Check need info
+
+on:
+  schedule:
+    - cron: "0 0 */7 * *"
+
+jobs:
+  check-need-info:
+    runs-on: ubuntu-latest
+    steps:
+      - name: close-issues
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'close-issues'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          labels: 'need info'
+          inactive-day: 7
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) for this comment | string | ✖ |
+| labels | Labels filtering | string | ✖ |
+| issue-assignee | Assignee filtering | string | ✖ |
+| issue-creator | Creator filtering | string | ✖ |
+| issue-mentioned | Mentioned filtering | string | ✖ |
+| body-includes | Body filtering | string | ✖ |
+| title-includes | Title filtering | string | ✖ |
+| inactive-day | Inactive days filtering | number | ✖ |
+| exclude-labels | Exclude labels filtering | string | ✖ |
+
+- `labels`: When there are multiple, the query will have multiple at the same time. If not entered, all
+- `issue-assignee`: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Entering `none` will query issues for which the specified person is not added
+- `inactive-day`: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, all
+
+## `find-comments`
+
+Find the current warehouse issue No. 1, the creator is k and the content contains the comment list of `this`.
+
+```yml
+- name: Find comments
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'find-comments'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: 1
+      comment-auth: 'k'
+      body-includes: 'this'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| comment-auth | Comment creator, all will be queried if not filled | string | ✖ |
+| body-includes | Comment content includes filtering, no verification if not filled | string | ✖ |
+| direction | Return `comments` sort | string | ✖ |
+
+- Return `comments` in the following format:
+
+```js
+[
+  {id: 1, auth: 'x', body: 'xxx', created: '', updated: ''},
+  {id: 2, auth: 'x', body: 'xxx', created: '', updated: ''},
+]
+```
+
+- `direction` defaults to ascending order, only when `desc` is set, descending order will be returned
+- The `created` `updated` in the returned array, determined by the environment, will be UTC +0
+
+## `lock-issues`
+
+Every 3 months at UTC 0 on the 1st, lock all issues that have been filled with the `inactive` label and have not been active for more than 128 days.
+
+```yml
+name: Lock inactive issues
+
+on:
+  schedule:
+    - cron: "0 0 1 */3 *"
+
+jobs:
+  lock-issues:
+    runs-on: ubuntu-latest
+    steps:
+      - name: lock-issues
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'lock-issues'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          labels: 'inactive'
+          inactive-day: 128
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) for this comment | string | ✖ |
+| labels | Labels filtering | string | ✖ |
+| issue-state | State filtering | string | ✖ |
+| issue-assignee | Assignee filtering | string | ✖ |
+| issue-creator | Creator filtering | string | ✖ |
+| issue-mentioned | Mentioned filtering | string | ✖ |
+| body-includes | Body filtering | string | ✖ |
+| title-includes | Title filtering | string | ✖ |
+| inactive-day | Inactive days filtering | number | ✖ |
+| lock-reason | Reason for locking issue | string | ✖ |
+| exclude-labels | Exclude labels filtering | string | ✖ |
+
+- `labels`: When there are multiple, the query will have multiple at the same time. If not entered, all
+- `issue-state`: The default is `all`. Optional value `open` `closed`, when these 2 items are not, both are `all`
+- `issue-assignee`: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Entering `none` will query issues for which the specified person is not added
+- `inactive-day`: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, all
+
+## `month-statistics`
+
+At 1 o'clock on the 1st of each month, an issue is generated for the statistics of the previous month.
+
+```
+name: Issue Month Statistics
+
+on:
+  schedule:
+    - cron: "0 1 1 * *"
+
+jobs:
+  month-statistics:
+    runs-on: ubuntu-latest
+    steps:
+      - name: month-statistics
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'month-statistics'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          count-lables: 'true'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| labels | The labels for the new issue | string | ✖ |
+| assignees | The assignees for the new issue | string | ✖ |
+| count-lables | Whether the new issue count labels | string | ✖ |
+| count-comments | Whether the new issue count comments | string | ✖ |
+
+- The new issue title defaults to `[Current repo] Month Statistics: Year-Month`
+- `count-lables`: You can set `'true'` to add labels statistics
+- `count-comments`: You can set `'true'` to add comments statistics
+
+As follows:
+
+![](../public/month.png)

docs/advanced.md

@@ -0,0 +1,258 @@
+---
+toc: menu
+---
+
+# 🌟 进 阶
+
+进阶用法不建议 actions 多个一次同时使用。
+
+## `check-inactive`
+
+每月 1 号 UTC 0 时，对所有 30 天以上未活跃的 issues 增加 `inactive` 标签。
+
+```yml
+name: Check inactive
+
+on:
+  schedule:
+    - cron: "0 0 1 * *"
+
+jobs:
+  check-inactive:
+    runs-on: ubuntu-latest
+    steps:
+      - name: check-inactive
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'check-inactive'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          inactive-day: 30
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
+| contents | 为该评论增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+| labels | 标签筛选 | string | ✖ |
+| issue-state | 状态筛选 | string | ✖ |
+| issue-assignee | 指定人筛选 | string | ✖ |
+| issue-creator | 创建人筛选 | string | ✖ |
+| issue-mentioned | 提及人筛选 | string | ✖ |
+| body-includes | 包含内容筛选 | string | ✖ |
+| title-includes | 包含标题筛选 | string | ✖ |
+| inactive-day | 非活跃天数筛选 | number | ✖ |
+| inactive-label | 新增标签名称 | string | ✖ |
+| exclude-labels | 排除标签筛选 | string | ✖ |
+
+- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
+- `issue-state`：默认为 `all`。可选值 `open` `closed`，非这 2 项时，均为 `all`
+- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
+- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
+- `inactive-label`：默认为 `inactive`，可自定义其他。当项目未包含该 label 时，会自动新建
+
+## `check-issue`
+
+根据传入的参数和 `issue-number` 来检查该 issue 是否满足条件，返回一个布尔值。
+
+下面的例子效果是：当 issue 新开时，校验当前 issue 指定人是否包含 `x1` 或者 `x2`，满足一个指定人即可校验通过，同时校验标题是否满足条件，[校验规则](/guide/ref#-includes-校验规则)。
+
+```yml
+name: Check Issue
+
+on:
+  issues:
+    types: [edited]
+
+jobs:
+  check-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: check-issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'check-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          assignee-includes: 'x1,x2'
+          title-includes: 'x1,x2/y1,y2'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| assignee-includes | 是否包含指定人 | string | ✖ |
+| title-includes | 标题包含校验 | string | ✖ |
+| title-excludes | 检测标题移除默认 title 后是否为空 | string | ✖ |
+| body-includes | 内容包含校验 | string | ✖ |
+
+- `title-includes` `body-includes` 支持格式 `x1,x2` 或者 `x1,x2/y1,y2`。只支持两个层级
+- 返回 `check-result`，由于 yml 原因，判断条件为 `if: steps.xxid.outputs.check-result == 'true'`
+
+## `close-issues`
+
+每 7 天 UTC 0 时，关闭已填加 `need info` label 且 7 天以上未活跃的 issues。
+
+```yml
+name: Check need info
+
+on:
+  schedule:
+    - cron: "0 0 */7 * *"
+
+jobs:
+  check-need-info:
+    runs-on: ubuntu-latest
+    steps:
+      - name: close-issues
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'close-issues'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          labels: 'need info'
+          inactive-day: 7
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
+| contents | 为该评论增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+| labels | 标签筛选 | string | ✖ |
+| issue-assignee | 指定人筛选 | string | ✖ |
+| issue-creator | 创建人筛选 | string | ✖ |
+| issue-mentioned | 提及人筛选 | string | ✖ |
+| body-includes | 包含内容筛选 | string | ✖ |
+| title-includes | 包含标题筛选 | string | ✖ |
+| inactive-day | 非活跃天数筛选 | number | ✖ |
+| exclude-labels | 排除标签筛选 | string | ✖ |
+
+- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
+- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
+- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
+
+## `find-comments`
+
+查找当前仓库 1 号 issue 中，创建者是 k ，内容包含 `this` 的评论列表。
+
+```yml
+- name: Find comments
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'find-comments'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: 1
+      comment-auth: 'k'
+      body-includes: 'this'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| comment-auth | 评论创建者，不填时会查询所有 | string | ✖ |
+| body-includes | 评论内容包含过滤，不填时无校验 | string | ✖ |
+| direction | 返回 `comments` 排序 | string | ✖ |
+
+- 返回 `comments`，格式如下：
+
+```js
+[
+  {id: 1, auth: 'x', body: 'xxx', created: '', updated: ''},
+  {id: 2, auth: 'x', body: 'xxx', created: '', updated: ''},
+]
+```
+
+- `direction` 默认为升序，只有设置 `desc` 时，会返回降序
+- 返回数组中 `created` `updated`，由所处环境决定，会是 UTC +0
+
+## `lock-issues`
+
+每 3 个月 1 号 UTC 0 时，锁定已填加 `inactive` label 且 128 天以上未活跃的所有 issues。
+
+```yml
+name: Lock inactive issues
+
+on:
+  schedule:
+    - cron: "0 0 1 */3 *"
+
+jobs:
+  lock-issues:
+    runs-on: ubuntu-latest
+    steps:
+      - name: lock-issues
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'lock-issues'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          labels: 'inactive'
+          inactive-day: 128
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
+| contents | 为该评论增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+| labels | 标签筛选 | string | ✖ |
+| issue-state | 状态筛选 | string | ✖ |
+| issue-assignee | 指定人筛选 | string | ✖ |
+| issue-creator | 创建人筛选 | string | ✖ |
+| issue-mentioned | 提及人筛选 | string | ✖ |
+| body-includes | 包含内容筛选 | string | ✖ |
+| title-includes | 包含标题筛选 | string | ✖ |
+| inactive-day | 非活跃天数筛选 | number | ✖ |
+| lock-reason | 锁定 issue 的原因 | string | ✖ |
+| exclude-labels | 排除标签筛选 | string | ✖ |
+
+- `labels`：为多个时，会查询同时拥有多个。不填时，会查询所有
+- `issue-state`：默认为 `all`。可选值 `open` `closed`，非这 2 项时，均为 `all`
+- `issue-assignee`：不支持多人。不填或输入 * 时，查询所有。输入 `none` 会查询未添加指定人的 issues
+- `inactive-day`：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有
+
+## `month-statistics`
+
+每月 1 号 1 时，生成一个 issue 上月统计。
+
+```
+name: Issue Month Statistics
+
+on:
+  schedule:
+    - cron: "0 1 1 * *"
+
+jobs:
+  month-statistics:
+    runs-on: ubuntu-latest
+    steps:
+      - name: month-statistics
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'month-statistics'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          count-lables: 'true'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| labels | 为新增 issue 添加 labels | string | ✖ |
+| assignees | 为新增 issue 添加 assignees | string | ✖ |
+| count-lables | 新增 issue 是否统计 labels | string | ✖ |
+| count-comments | 新增 issue 是否统计 comments | string | ✖ |
+
+- 新增 `issue` 的标题默认为 `[当前仓库] Month Statistics: 年-月`
+- `count-lables`：可设置 `'true'`，增加 labels 统计
+- `count-comments`：可设置 `'true'`，增加 comments 统计
+
+如下所示：
+
+![](../public/month.png)

docs/base.en-US.md

@@ -0,0 +1,531 @@
+---
+toc: menu
+---
+
+# ⭐ Base
+
+In order to better display the function, the following is an example of the actual scene, please refer to it flexibly.
+
+## `add-assignees`
+
+When an issue is added or modified, assign this issue to one or more people.
+
+```yml
+name: Add Assigness
+
+on:
+  issues:
+    types: [opened, edited]
+
+jobs:
+  add-assigness:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add assigness
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'add-assignees'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          assignees: 'xxx' or 'xx1,xx2'
+          random-to: 1
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| assignees | Designated person. No operation when no input or empty character | string | ✖ |
+| random-to | When set, it will be randomly selected in assignees | number | ✖ |
+
+- `actions` support multiple and separated by comma. Like: `add-assignees,add-labels`
+- The `name` can be modified according to the actual situation
+- [Reference to on](/en-US/guide/ref#-github-docs)
+- `${{ github.event.issue.number }}` is the current issue. [More references](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events)
+- `assignees` support multiple and separated by comma
+
+## `add-labels`
+
+When the content of a new issue does not contain the specified format, add labels for the issue.
+
+```yml
+name: Add Labels
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  add-labels:
+    runs-on: ubuntu-latest
+    if: contains(github.event.issue.body, 'xxx') == false
+    steps:
+      - name: Add labels
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'add-labels'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          labels: 'bug' or 'xx1,xx2'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| labels | New labels. When it is not filled in or is empty character, do not add | string | ✖ |
+
+- `labels` support multiple and separated by comma
+
+## `close-issue`
+
+Close the specified issue.
+
+```yml
+- name: Close issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'close-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: xxx
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+
+## `create-comment`
+
+When a designated label is added, comment on the issue.
+
+```yml
+name: Create Comment
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  create-comment:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'xxx'
+    steps:
+      - name: Create comment
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello @${{ github.event.issue.user.login }}. Add some comments.
+
+            你好 @${{ github.event.issue.user.login }}。巴拉巴拉。
+          contents: '+1' or '+1,heart'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| body | Add comment content | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) | string | ✖ |
+
+- `body` default is `Currently at ${owner}/${repo}. And this is default comment.`
+  - Where `${owner}/${repo}` means the current repo
+- Return `comment-id`, which can be used for subsequent operations. [Usage reference](/en-US/guide/ref#-outputs-use)
+- `${{ github.event.issue.user.login }}` indicates the creator of the issue
+- `contents` support multiple and separated by comma
+
+## `create-issue`
+
+Here is an example, add an issue at UTC 00:00 on the 1st of every month.
+
+```yml
+name: Create Issue
+
+on:
+  schedule:
+    - cron: "0 0 1 * *"
+
+jobs:
+  create-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          title: 'xxxx'
+          body: 'xxxx'
+          labels: 'xx'
+          assignees: 'xxx'
+          contents: '+1'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| title | The title of the new issue | string | ✖ |
+| body | The body of the new issue | string | ✖ |
+| labels | The labels for the new issue | string | ✖ |
+| assignees | The assignees for the new issue | string | ✖ |
+| random-to | When set, it will be randomly selected in assignees | number | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) | string | ✖ |
+
+- `title` default is `Default Title`
+- Return `issue-number`. [Usage reference](/en-US/guide/ref#-outputs-use)
+
+## `create-label`
+
+Create label. If you want to maintain labels in batches, [see](https://github.com/actions-cool/labels-helper).
+
+```yml
+- name: Create label
+  uses: actions-cool/issues-helper@v2
+  with:
+    actions: 'create-label'
+    token: ${{ secrets.GITHUB_TOKEN }}
+    label-name: 'xx'
+    label-color: '0095b3'
+    label-desc: 'xx'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| label-name | Label name, emoji support | string | ✔ |
+| label-color | Label color, the format is hexadecimal color code, without `#` | string | ✖ |
+| label-desc | Label description | string | ✖ |
+
+- `label-name`: If it already exists, no operation
+- `label-color`: Default is `ededed`
+
+## `delete-comment`
+
+According to [`comment-id`](/en-US/guide/ref#-comment-id) delete the specified comment.
+
+```yml
+- name: Delete comment
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'delete-comment'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      comment-id: xxx
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| comment-id | The comment ID | number | ✔ |
+| out-comments | The output of `find-comments`, if you find multiple, operate multiple | string | ✖ |
+
+- When `out-comments` is entered, `comment-id` does not work
+
+## `lock-issue`
+
+When the `invalid` label is added, the issue is locked.
+
+```yml
+name: Lock Issue
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  lock-issue:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'invalid'
+    steps:
+      - name: Lock issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'lock-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| lock-reason | Reason for locking issue | string | ✖ |
+
+- `lock-reason`: Optional values are `off-topic` `too heated` `resolved` `spam`
+
+## `mark-duplicate`
+
+Quickly mark duplicate questions, only for issue new comments or edit comments.
+
+```yml
+name: Issue Mark Duplicate
+
+on:
+  issue_comment:
+    types: [created, edited]
+
+jobs:
+  mark-duplicate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: mark-duplicate
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'mark-duplicate'
+          token: ${{ secrets.GITHUB_TOKEN }}
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| duplicate-command | Simple commands can be set, such as: `/d` | string | ✖ |
+| duplicate-labels | Add additional labels to this issue | string | ✖ |
+| remove-labels | Set removable labels | string | ✖ |
+| labels | Replace the labels of the issue | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) for this comment | string | ✖ |
+| close-issue | Whether to close the issue at the same time | string | ✖ |
+| require-permission | Permission required, default is `write` | string | ✖ |
+
+- `duplicate-command`: When setting concise commands, while still supporting the original `Duplicate of`. Block content contains `?`
+- `labels`: Highest priority
+- `close-issue`: Both `true` or `'true'` can take effect
+- `require-permission`: Optional values are `admin`, `write`, `read`, `none`
+  - If the team member sets the `read` permission, it is `read`
+  - If the external Collaborator is set to `read` permission, it is `read`
+  - Ordinary users have `read` permission
+  - When set `write`, `admin` and `write` meet the conditions
+
+<Alert>
+Note: Duplicate created with the concise command does not display the content of the red box in the figure below. But in fact this has no effect.
+</Alert>
+
+![](../public/duplicate.png)
+
+## `open-issue`
+
+Open the specified issue.
+
+```yml
+- name: Open issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'open-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: xxx
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+
+## `remove-assignees`
+
+Remove the person designated by issue.
+
+```yml
+- name: Remove assignees
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'remove-assignees'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      assignees: 'xx'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| assignees | Designated person removed. When it is an empty character, do not remove | string | ✔ |
+
+## `remove-labels`
+
+Remove the specified labels.
+
+```yml
+- name: Remove labels
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'remove-labels'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: 'xx'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| labels | The removed labels. When it is a blank character, do not remove | string | ✔ |
+
+- `labels` supports multiple, such as `x1,x2,x3`, only the labels added by the issue will be removed
+
+## `set-labels`
+
+Replace the labels of issue.
+
+```yml
+- name: Set labels
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'set-labels'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: 'xx'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| labels | labels set. When empty characters, will remove all | string | ✔ |
+
+## `unlock-issue`
+
+Unlock the specified issue.
+
+```yml
+- name: Unlock issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'unlock-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+
+## `update-comment`
+
+Update the specified comment according to [`comment-id`](/en-US/guide/ref#-comment-id).
+
+The following example shows that 👀 is added for each new comment.
+
+```yml
+name: Add eyes to each comment
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  update-comment:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Update comment
+          uses: actions-cool/issues-helper@v2
+          with:
+            actions: 'update-comment'
+            token: ${{ secrets.GITHUB_TOKEN }}
+            comment-id: ${{ github.event.comment.id }}
+            contents: 'eyes'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| comment-id | The comment ID | number | ✔ |
+| out-comments | The output of `find-comments`, if you find multiple, operate multiple | string | ✖ |
+| body | Update the content of comment | string | ✖ |
+| update-mode | Update mode. Default `replace`, another `append` | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) | string | ✖ |
+
+- When `body` is not entered, it will remain as it is
+- When `update-mode` is `append`, additional operations will be performed. Anything other than `append` will be replaced. Only effective for `body`
+- When `out-comments` is entered, `comment-id` does not work
+
+## `update-issue`
+
+Update the specified issue according to the `issue-number`.
+
+```yml
+- name: Update issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'update-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      state: 'open'
+      title: 'xxx'
+      body: 'xxxx'
+      update-mode: 'replace'
+      labels: 'xx'
+      assignees: 'xxx'
+      contents: '+1'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
+| state | Modify the status of issue, optional value `open` `closed` | string | ✖ |
+| title | Modify the title of the issue | string | ✖ |
+| body | Modify the content of issue | string | ✖ |
+| update-mode |  Update mode. Default `replace`, another `append` | string | ✖ |
+| labels | Replace the labels of issue | string | ✖ |
+| assignees | Replace the assignees of issue | string | ✖ |
+| contents | Add [reaction](/en-US/guide/ref#-reactions-type) | string | ✖ |
+
+- `state` defaults to `open`
+- When the option is not filled, it will keep the original
+
+## `welcome`
+
+When an issue is created, the user who created the issue for the first time is welcome.
+
+If the user is not creating for the first time, there is no operation.
+
+```yml
+name: Issue Welcome
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  issue-welcome:
+    runs-on: ubuntu-latest
+    steps:
+      - name: welcome
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'welcome'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: hi @${{ github.event.issue.user.login }}, welcome!
+          labels: 'welcome1, welcome2'
+          assignees: 'xx1'
+          issue-contents: '+1, -1, eyes'
+```
+
+| Param | Desc  | Type | Required |
+| -- | -- | -- | -- |
+| actions | Action type | string | ✔ |
+| token | [Token explain](/en-US/guide/ref#-token) | string | ✔ |
+| body | Comment on the welcome content, no comment if you leave it blank | string | ✖ |
+| labels | Add labels to this issue | string | ✖ |
+| assignees | Add assignees to this issue | string | ✖ |
+| issue-contents | Add [reaction](/en-US/guide/ref#-reactions-type) to this issue| string | ✖ |
+
+- If these 4 options are not filled, no operation

docs/base.md

@@ -0,0 +1,530 @@
+---
+toc: menu
+---
+
+为了更好的展示功能，下面以实际场景举例，请灵活参考。
+
+# ⭐ 基 础
+
+## `add-assignees`
+
+当一个 issue 新增或修改时，将这个 issue 指定某人或多人。
+
+```yml
+name: Add Assigness
+
+on:
+  issues:
+    types: [opened, edited]
+
+jobs:
+  add-assigness:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add assigness
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'add-assignees'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          assignees: 'xxx' or 'xx1,xx2'
+          random-to: 1
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| assignees | 指定人。当不填或者为空字符时，不操作 | string | ✖ |
+| random-to | 当设置时，会在 assignees 中随机选择 | number | ✖ |
+
+- `actions` 支持多个，需用逗号隔开。如：`add-assignees,add-labels`
+- 其中的 `name` 可根据自行根据实际情况修改
+- [on 参考](/guide/ref#-github-相关文档)
+- `${{ github.event.issue.number }}` 表示当前 issue，[更多参考](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events)
+- `assignees` 支持多个，需用逗号隔开
+
+## `add-labels`
+
+当一个新增的 issue 内容不包含指定格式时，为这个 issue 添加 labels。
+
+```yml
+name: Add Labels
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  add-labels:
+    runs-on: ubuntu-latest
+    if: contains(github.event.issue.body, 'xxx') == false
+    steps:
+      - name: Add labels
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'add-labels'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          labels: 'bug' or 'bug1,bug2'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| labels | 新增的 labels。当不填或者为空字符时，不新增 | string | ✖ |
+
+- `labels` 支持多个，需用逗号隔开
+
+## `close-issue`
+
+关闭指定 issue。
+
+```yml
+- name: Close issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'close-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: xxx
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+
+## `create-comment`
+
+当新增一个指定 label 时，对该 issue 进行评论。
+
+```yml
+name: Create Comment
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  create-comment:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'xxx'
+    steps:
+      - name: Create comment
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello ${{ github.event.issue.user.login }}. Add some comments.
+
+            你好 ${{ github.event.issue.user.login }}。巴拉巴拉。
+          contents: '+1' or '+1,heart'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| body | 新增评论的内容  | string | ✖ |
+| contents | 为新增评论的增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+
+- `body` 默认为：`Currently at ${owner}/${repo}. And this is default comment.`
+  - 其中 `${owner}/${repo}` 表示当前仓库
+- 返回 `comment-id`，可用于之后操作。[用法参考](/guide/ref#-outputs-使用)
+- `${{ github.event.issue.user.login }}` 表示该 issue 的创建者
+- `contents` 支持多个，需用逗号隔开
+
+## `create-issue`
+
+感觉新增 issue 使用场景不多。这里举例，每月 1 号 UTC 00:00 新增一个 issue。
+
+```yml
+name: Create Issue
+
+on:
+  schedule:
+    - cron: "0 0 1 * *"
+
+jobs:
+  create-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          title: 'xxxx'
+          body: 'xxxx'
+          labels: 'xx'
+          assignees: 'xxx'
+          contents: '+1'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| title | 新增 issue 的标题 | string | ✖ |
+| body | 新增 issue 的内容 | string | ✖ |
+| labels | 为新增 issue 添加 labels | string | ✖ |
+| assignees | 为新增 issue 添加 assignees | string | ✖ |
+| random-to | 当设置时，会在 assignees 中随机选择 | number | ✖ |
+| contents | 为新增 issue 增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+
+- `title` 默认为：`Default Title`
+- 返回 `issue-number`，[用法参考](/guide/ref#-outputs-使用)
+
+## `create-label`
+
+新增 label。若想批量维护 labels，[可查看](https://github.com/actions-cool/labels-helper)。
+
+```yml
+- name: Create label
+  uses: actions-cool/issues-helper@v2
+  with:
+    actions: 'create-label'
+    token: ${{ secrets.GITHUB_TOKEN }}
+    label-name: 'xx'
+    label-color: '0095b3'
+    label-desc: 'xx'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| label-name | 标签名称，支持 emoji | string | ✔ |
+| label-color | 标签颜色，格式为 16 进制色码，不加 `#` | string | ✖ |
+| label-desc | 标签描述 | string | ✖ |
+
+- `label-name`：若已存在，则无操作
+- `label-color`：默认为 `ededed`
+
+## `delete-comment`
+
+根据 [`comment-id`](/guide/ref#-comment-id) 删除指定评论。
+
+```yml
+- name: Delete comment
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'delete-comment'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      comment-id: xxx
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| comment-id | 指定的 comment | number | ✔ |
+| out-comments | `find-comments` 的输出，若查找多个，则操作多个 | string | ✖ |
+
+- 当 `out-comments` 输入时，`comment-id` 不起作用
+
+## `lock-issue`
+
+当新增 `invalid` label 时，对该 issue 进行锁定。
+
+```yml
+name: Lock Issue
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  lock-issue:
+    runs-on: ubuntu-latest
+    if: github.event.label.name == 'invalid'
+    steps:
+      - name: Lock issue
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'lock-issue'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| lock-reason | 锁定 issue 的原因 | string | ✖ |
+
+- `lock-reason`：可选值有 `off-topic` `too heated` `resolved` `spam`
+
+## `mark-duplicate`
+
+快捷标记重复问题，仅作用于 issue 新增编辑评论。
+
+```yml
+name: Issue Mark Duplicate
+
+on:
+  issue_comment:
+    types: [created, edited]
+
+jobs:
+  mark-duplicate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: mark-duplicate
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'mark-duplicate'
+          token: ${{ secrets.GITHUB_TOKEN }}
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| duplicate-command | 可设置简洁命令，如：`/d` | string | ✖ |
+| duplicate-labels | 为该 issue 额外增加 labels | string | ✖ |
+| remove-labels | 设置可移除的 labels | string | ✖ |
+| labels | 替换该 issue 的 labels | string | ✖ |
+| contents | 为该评论的增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+| close-issue | 是否同时关闭该 issue | string | ✖ |
+| require-permission | 要求权限，默认为 `write` | string | ✖ |
+
+- `duplicate-command`：当设置简洁命令时，同时仍支持原有 `Duplicate of`。屏蔽内容包含 `?`
+- `labels`：优先级最高
+- `close-issue`：`true` 或 `'true'` 均可生效
+- `require-permission`：可选值有 `admin`，`write`，`read`，`none`
+  - 团队成员若设置 `read` 权限，则为 `read`
+  - 外部 Collaborator 若设置 `read` 权限，则为 `read`
+  - 普通用户为 `read` 权限
+  - 当设置 `write` 后，`admin` 和 `write` 满足条件
+
+<Alert>
+注意：使用简洁命令创建的 Duplicate 不显示下图红框内容。但其实这个没有任何影响的。
+</Alert>
+
+![](../public/duplicate.png)
+
+## `open-issue`
+
+打开指定 issue。
+
+```yml
+- name: Open issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'open-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: xxx
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+
+## `remove-assignees`
+
+移除 issue 指定人员。
+
+```yml
+- name: Remove assignees
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'remove-assignees'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      assignees: 'xx'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| assignees | 移除的指定人。当为空字符时，不进行移除 | string | ✔ |
+
+## `remove-labels`
+
+移除指定 labels。
+
+```yml
+- name: Remove labels
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'remove-labels'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: 'xx'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| labels | 移除的 labels。当为空字符时，不进行移除 | string | ✔ |
+
+- `labels` 支持多个，如 `x1,x2,x3`，只会移除 issue 已添加的 labels
+
+## `set-labels`
+
+替换 issue 的 labels。
+
+```yml
+- name: Set labels
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'set-labels'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      labels: 'xx'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| labels | labels 设置。当空字符时，会移除所有 | string | ✔ |
+
+## `unlock-issue`
+
+解锁指定 issue。
+
+```yml
+- name: Unlock issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'unlock-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+
+## `update-comment`
+
+根据 [`comment-id`](/guide/ref#-comment-id) 更新指定评论。
+
+下面的例子展示的是，为每个新增的 comment 增加 👀 。
+
+```yml
+name: Add eyes to each comment
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  update-comment:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Update comment
+          uses: actions-cool/issues-helper@v2
+          with:
+            actions: 'update-comment'
+            token: ${{ secrets.GITHUB_TOKEN }}
+            comment-id: ${{ github.event.comment.id }}
+            contents: 'eyes'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| comment-id | 指定的 comment | number | ✔ |
+| out-comments | `find-comments` 的输出，若查找多个，则操作多个 | string | ✖ |
+| body | 更新 comment 的内容 | string | ✖ |
+| update-mode | 更新模式。默认 `replace` 替换，`append` 附加 | string | ✖ |
+| contents | 增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+
+- `body` 不填时，会保持原有
+- `update-mode` 为 `append` 时，会进行附加操作。非 `append` 都会进行替换。仅对 `body` 生效
+- 当 `out-comments` 输入时，`comment-id` 不起作用
+
+## `update-issue`
+
+根据 `issue-number` 更新指定 issue。
+
+```yml
+- name: Update issue
+    uses: actions-cool/issues-helper@v2
+    with:
+      actions: 'update-issue'
+      token: ${{ secrets.GITHUB_TOKEN }}
+      issue-number: ${{ github.event.issue.number }}
+      state: 'open'
+      title: 'xxx'
+      body: 'xxxx'
+      update-mode: 'replace'
+      labels: 'xx'
+      assignees: 'xxx'
+      contents: '+1'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明) | string | ✔ |
+| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
+| state | 修改 issue 的状态，可选值 `open` `closed` | string | ✖ |
+| title | 修改 issue 的标题 | string | ✖ |
+| body | 修改 issue 的内容 | string | ✖ |
+| update-mode | 更新模式。默认 `replace` 替换，`append` 附加 | string | ✖ |
+| labels | 替换 issue 的 labels | string | ✖ |
+| assignees | 替换 issue 的 assignees | string | ✖ |
+| contents | 增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+
+- `state` 默认为 `open`
+- 当可选项不填时，会保持原有
+
+
+## `welcome`
+
+当一个 issue 新建时，对首次新建 issue 的用户进行欢迎。若用户非首次新建，则无操作。
+
+```yml
+name: Issue Welcome
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  issue-welcome:
+    runs-on: ubuntu-latest
+    steps:
+      - name: welcome
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'welcome'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          body: hi @${{ github.event.issue.user.login }}, welcome!
+          labels: 'welcome1, welcome2'
+          assignees: 'xx1'
+          issue-contents: '+1, -1, eyes'
+```
+
+| 参数 | 描述 | 类型 | 必填 |
+| -- | -- | -- | -- |
+| actions | 操作类型 | string | ✔ |
+| token | [token 说明](/guide/ref#-token-说明)  | string | ✔ |
+| body | 评论欢迎的内容，不填则不评论 | string | ✖ |
+| labels | 为该 issue 增加 labels | string | ✖ |
+| assignees | 为该 issue 增加 assignees | string | ✖ |
+| issue-contents | 为该 issue 增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
+
+- 若这 4 个可选项都不填，则无操作

docs/changelog.en-US.md

@@ -0,0 +1,38 @@
+---
+toc: menu
+---
+
+# ✨ Changelog
+
+- Version rules
+  - Use two-level semantic version, such as v1, v1.1, v2, v2.1
+  - v1 represents the initial version
+  - The fixes and additions to the v1 version will be released to the v1.1 version
+  - When the released v1.x runs stable for a certain period of time or undergoes refactoring, release the advanced v2.x version
+  - After the v2 version, the version will be released strictly according to the three-level semantics, such as v2.0.0, v2.1.0
+
+- Version selection
+  - It is recommended to use the latest releases version. It can be seen in [releases](https://github.com/actions-cool/issues-helper/releases)
+  - You can also refer to the update log below to select the version
+  - The latest v1.x release code will be merged into the 1.x branch
+  - After the v2 version, the v2 tag is supported, and the latest 2.x code will be synchronized
+  - It also supports the direct use of branch versions. Such as:
+
+```yml
+- name: Issues Helper
+  uses: actions-cool/issues-helper@main
+
+# or
+
+- name: Issues Helper
+  uses: actions-cool/issues-helper@1.x
+
+# or
+
+- name: Issues Helper
+  uses: actions-cool/issues-helper@v2
+```
+
+- v2 [upgrade reference](/en-US/guide/faq)
+
+<embed src="../CHANGELOG.md"></embed>

docs/changelog.md

@@ -0,0 +1,38 @@
+---
+toc: menu
+---
+
+# ✨ 更新日志
+
+- 版本规则
+  - 采用两级语义化版本，如v1、v1.1、v2、v2.1
+  - v1 表示初始版本
+  - 对 v1 版本的修复和新增会发布到 v1.1 版本
+  - 当发布的 v1.x 运行一定时间稳定或进行重构时，发布进阶 v2.x 版本
+  - v2 版本后会严格按照三级语义来发布版本，如 v2.0.0、v2.1.0
+
+- 版本选择
+  - 建议采用最新 releases 版本。可在 [releases](https://github.com/actions-cool/issues-helper/releases) 看到
+  - 同时也可参照下面的更新日志来选择版本
+  - 最新的 v1.x release 代码会合并到 1.x 分支中
+  - v2 版本后支持使用 v2 tag，将同步最新 2.x 代码
+  - 支持直接使用分支版本。如：
+
+```yml
+- name: Issues Helper
+  uses: actions-cool/issues-helper@main
+
+# or
+
+- name: Issues Helper
+  uses: actions-cool/issues-helper@1.x
+
+# or
+
+- name: Issues Helper
+  uses: actions-cool/issues-helper@v2
+```
+
+- v2 [升级参考](/guide/faq)
+
+<embed src="../CHANGELOG.md"></embed>

docs/guide/faq.en-US.md

@@ -0,0 +1,35 @@
+---
+toc: menu
+---
+
+## Is there a charge for this feature?
+
+GitHub Actions is provided free of charge by GitHub. Among them, the `Private` project has a monthly limit of 2000 times, [see details](https://github.com/settings/billing). The `Public` project is unlimited.
+
+### Is there a rate limit?
+
+Yes. The bottom layer of Action uses GitHub REST API. The general situation is 5000 times per hour. It is basically sufficient in principle, and it is also required to avoid invalid requests when defining Action. [Detailed view](https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting).
+
+## Are there any ready-made templates for reference?
+
+Yes.
+
+1. You can use this [GitHub Actions workflow template](https://github.com/actions-cool/.github) repository template
+2. Personal exercises and tests [Actions](https://github.com/actions-cool/test-issues-helper) repository
+3. You can also refer to the warehouse of [online users](/en-US#-who-is-using)
+
+## I want to pause Actions, is there an easy way?
+
+Yes, you can directly modify `actions`. For example: `actions:'create-comment'` is changed to `actions:'#create-comment'`. It is also convenient for recovery.
+
+## So many versions, how to choose?
+
+You can view the detailed [changelog](/en-US/changelog). The latest releases version is recommended.
+
+## What should I pay attention to when upgrading from v1.x to v2?
+
+There is only one difference between v1.12 and v2.0.0. That is, `require-permission` in `mark-duplicate` has added the default value `write`.
+
+## What should I do if there is no function I want here?
+
+You can submit it in [What do you want?](https://github.com/actions-cool/issues-helper/discussions/18).

docs/guide/faq.md

@@ -0,0 +1,35 @@
+---
+toc: menu
+---
+
+## 该功能是否收费？
+
+GitHub Actions 是由 GitHub 免费提供的。其中 `Private` 项目每月有 2000 次的限制，[具体查看](https://github.com/settings/billing)。`Public` 项目无限制。
+
+### 有没有速率的限制？
+
+有的。Action 底层使用的是 GitHub REST API。一般情况是每小时 5000 次。原则上基本是够用的，同时也要求在 Action 定义时，尽量避免无效的请求。[具体查看](https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting)。
+
+## 有没有现成的模板可以参考？
+
+有的。
+
+1. 你可以使用这个 [GitHub Actions workflow template](https://github.com/actions-cool/.github) 仓库的模板
+2. 个人练习和测试 [Actions](https://github.com/actions-cool/test-issues-helper) 的仓库
+3. 也可以来 [线上使用者](/#-谁在使用？) 的仓库参照
+
+## 我想暂停 Actions，有没有简单的办法？
+
+有的，你可以将直接修改 `actions`。例如：`actions: 'create-comment'` 修改为 `actions: '#create-comment'`。同时也方便恢复。
+
+## 这么多版本，如何选择？
+
+你可以查看详细的 [更新日志](/changelog)。推荐采用最新 releases 版本。
+
+## 从 v1.x 升级到 v2，有什么注意的地方吗？
+
+v1.12 和 v2.0.0 版本的差别只有一处。即 `mark-duplicate` 中的 `require-permission` 增加了默认值 `write`。
+
+## 如果这里没有我想要的功能，该怎么办？
+
+你可以在 [What do you want?](https://github.com/actions-cool/issues-helper/discussions/18) 中提出。

docs/guide/index.en-US.md

@@ -0,0 +1,23 @@
+## Introduction
+
+The Issues Helper is a GitHub Action that easily helps you automatically manage issues.
+
+### What are GitHub Actions?
+
+Automate, customize, and execute your software development workflows right in your repository with GitHub Actions. You can discover, create, and share actions to perform any job you'd like, including CI/CD, and combine actions in a completely customized workflow. [More](https://docs.github.com/en/free-pro-team@latest/actions).
+
+`issues-helper` is based on this, using GitHub Actions to help you deal with various operations on issues.
+
+### ✨ Feature
+
+- 😎 Complete free
+- 🚀 Fully automatic
+- 🏖 Hosted on the GitHub server, as long as GitHub is not down, it is not affected
+
+### ⚡ Feedback
+
+You are very welcome to try it out and put forward your comments. You can use the following methods:
+
+- Report bugs or consult with [Issue](https://github.com/actions-cool/issues-helper/issues)
+- Discuss via [Discussions](https://github.com/actions-cool/issues-helper/discussions)
+- Submit [Pull Request](https://github.com/actions-cool/issues-helper/pulls) to improve the code of `issues-helper`

docs/guide/index.md

@@ -0,0 +1,23 @@
+## 介 绍
+
+Issues 助手是一个轻松帮你自动管理 issues 的 GitHub Action。
+
+### GitHub Actions 是什么？
+
+GitHub Actions 是由 GitHub 官方提供在存储库中自动化、自定义和执行软件开发工作流程。您可以发现，创建和共享操作以执行所需的任何工作（包括CI / CD），并在完全定制的工作流程中组合操作。[更多介绍](https://docs.github.com/en/free-pro-team@latest/actions)。
+
+`issues-helper` 就是以此为基础，利用 GitHub Actions 来帮你处理各种关于 issue 方面的操作。
+
+### ✨ 特性
+
+- 😎 完全免费
+- 🚀 全自动操作
+- 🏖 托管于 GitHub 服务器，只要 GitHub 不宕机，它就不受影响
+
+### ⚡ 反馈
+
+非常欢迎你来尝试使用，并提出意见，你可以通过以下方式：
+
+- 通过 [Issue](https://github.com/actions-cool/issues-helper/issues) 报告 bug 或进行咨询
+- 通过 [Discussions](https://github.com/actions-cool/issues-helper/discussions) 进行讨论
+- 提交 [Pull Request](https://github.com/actions-cool/issues-helper/pulls) 改进 `issues-helper` 的代码

docs/guide/note.en-US.md

@@ -0,0 +1,50 @@
+---
+toc: menu
+---
+
+<Alert type="success">
+Here are some things I summarized in my use, I hope it can help you.
+</Alert>
+
+## Include judgment in `yml`
+
+```yml
+if: contains(github.event.issue.body, 'ie') == false
+```
+- Triggered when the issue body does not contain `ie`
+- The js `includes()` syntax is not supported in the yml
+- Case is not checked, `IE` and also similar to `kiekk` can also be satisfied
+
+[More](https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions#functions).
+
+## Pass value and output in `yml`
+
+```
+with:
+  actions: 'month-statistics'
+  token: ${{ secrets.GITHUB_TOKEN }}
+  count-lables: 'true'
+```
+
+- `count-lables`: Regardless of setting `true` or `'ture'`, all received in the program is in string format
+
+At the same time, the output is also in string format. [See](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs).
+
+- `check-result`: The judgment condition is `if: steps.xxid.outputs.check-result =='true'`
+
+## `GitHub Actions bot` trigger
+
+When an action is set, such as adding a label `x1` to an issue, Actions will automatically add a label `x2` to the issue.
+
+But if this is done by `GitHub Actions bot` (that is, the token in the actions is not passed, or the default `token: ${{ secrets.GITHUB_TOKEN }}` is used), the actions of label `x2` will not be triggered.
+
+ref: [GitHub docs](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token)
+
+## `assignees` scope
+
+- The owner or collaborator of the warehouse, if there is an organization, including members
+- Participants of the issue, including creators and commenters
+
+## Benchmark
+
+For example: I use a Tag to trigger an Action, and the code that triggers the benchmark will follow the Action definition of the code corresponding to this Tag instead of the main branch code.

docs/guide/note.md

@@ -0,0 +1,51 @@
+---
+toc: menu
+---
+
+<Alert type="success">
+这里记录自己在使用中总结的一些东西，希望可以帮助到你。
+</Alert>
+
+## `yml` 中包含判断
+
+```yml
+if: contains(github.event.issue.body, 'ie') == false
+```
+
+- 当 issue body 不包含 `ie` 触发
+- 测试 yml 中不支持 js `includes()` 语法
+- 大小写不校验，`IE` 还有同时类似 `kiekk` 也可满足
+
+更多[查看](https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions#functions)。
+
+## `yml` 中传值和输出
+
+```
+with:
+  actions: 'month-statistics'
+  token: ${{ secrets.GITHUB_TOKEN }}
+  count-lables: 'true'
+```
+
+- `count-lables`：不管设置 `true` 还是 `'ture'`，在程序里接收到的都是字符串格式
+
+同时输出的也是字符串格式。[参看](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs)。
+
+- `check-result`：判断条件为 `if: steps.xxid.outputs.check-result == 'true'`
+
+## `GitHub Actions bot` 触发
+
+当设置了一个 Actions，如为给一个 issue 新增 label `x1` 时，Actions 自动为该 issue 增加 `x2` label。
+
+但如果这个是由 `GitHub Actions bot` 完成的（即 actions 中 token 不传，或使用默认 `token: ${{ secrets.GITHUB_TOKEN }}`），则不会触发 label `x2` 的 Actions。
+
+ref: [GitHub docs](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token)
+
+## `assignees` 范围
+
+- 仓库的所有者或协作者，若有组织，包括成员
+- issue 的参与者，包括创建者、评论者
+
+## 运行基准
+
+比如：我用 Tag 触发一个 Action，触发基准的代码就会走这个 Tag 对应代码的 Action 定义，而非主分支代码。

docs/guide/ref.en-US.md

@@ -0,0 +1,86 @@
+---
+toc: menu
+---
+
+## 📍 `token`
+
+Need to have the person token with push permission.
+
+- [Personal token application](https://github.com/settings/tokens)
+  - Need to check `Full control of private repositories`
+- Project add secrets
+  - Select settings, select secrets, select `New repository secret`
+  - `Name` is the same as in actions
+  - `Value` fill in the token just applied by the individual
+
+When the token is not filled in actions or input `${{ secrets.GITHUB_TOKEN }}`, it will default to `github-actions-bot`. [More](https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow).
+
+## 📍 GitHub Docs
+
+- [Workflow syntax for GitHub Actions](https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#on)
+- [Events that trigger workflows](https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows)
+
+## 📍 `outputs` use
+
+```yml
+- name: Create issue
+  uses: actions-cool/issues-helper@v1
+  id: createissue
+  with:
+    actions: 'create-issue'
+    token: ${{ secrets.GITHUB_TOKEN }}
+- name: Check outputs
+  run: echo "Outputs issue_number is ${{ steps.createissue.outputs.issue-number }}"
+```
+
+More:
+
+1. https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/metadata-syntax-for-github-actions#outputs
+2. https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs
+
+## 📍 `includes` check rules
+
+```js
+"title-includes": 'x1,x2'
+
+x1
+x2
+
+"x1y3y2"  true
+"y2 x1"   true
+"x2"      true
+"x3"      false
+```
+
+```js
+"title-includes": 'x1,x2/y1,y2'
+
+x1 + y1
+x2 + y1
+x1 + y2
+x2 + y2
+
+"x1y3y2"  true
+"y2 x1"   true
+"1x2y"    false
+"x1"      false
+```
+
+## 📍 `Reactions` Type
+
+| content | emoji |
+| -- | -- |
+| `+1` | 👍 |
+| `-1` | 👎 |
+| `laugh` | 😄 |
+| `confused` | 😕 |
+| `heart` | ❤️ |
+| `hooray` | 🎉 |
+| `rocket` | 🚀 |
+| `eyes` | 👀 |
+
+For details, please [view](https://docs.github.com/en/free-pro-team@latest/rest/reference/reactions).
+
+## 📍 `comment-id`
+
+Click the `···` icon in the upper right corner of a comment, select `Copy link`, and the number at the end of the url is `comment_id`.

docs/guide/ref.md

@@ -0,0 +1,86 @@
+---
+toc: menu
+---
+
+## 📍 `token` 说明
+
+需拥有 push 权限的人员 token。
+
+- [个人 token 申请](https://github.com/settings/tokens)
+  - 需勾选 `Full control of private repositories`
+- 项目添加 secrets
+  - 选择 settings，选择 secrets，选择 `New repository secret`
+  - `Name` 与 actions 中保持一致
+  - `Value` 填写刚才个人申请的 token
+
+当 actions 不填写 token 时，或输入 `${{ secrets.GITHUB_TOKEN }}`，会默认为 `github-actions-bot`。[更多查看](https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow)。
+
+## 📍 GitHub 相关文档
+
+- [GitHub Actions 语法](https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#on)
+- [工作流触发机制](https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows)
+
+## 📍 `outputs` 使用
+
+```yml
+- name: Create issue
+  uses: actions-cool/issues-helper@v1
+  id: createissue
+  with:
+    actions: 'create-issue'
+    token: ${{ secrets.GITHUB_TOKEN }}
+- name: Check outputs
+  run: echo "Outputs issue_number is ${{ steps.createissue.outputs.issue-number }}"
+```
+
+更多查看：
+
+1. https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/metadata-syntax-for-github-actions#outputs
+2. https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs
+
+## 📍 `includes` 校验规则
+
+```js
+"title-includes": 'x1,x2'
+
+x1
+x2
+
+"x1y3y2"  true
+"y2 x1"   true
+"x2"      true
+"x3"      false
+```
+
+```js
+"title-includes": 'x1,x2/y1,y2'
+
+x1 + y1
+x2 + y1
+x1 + y2
+x2 + y2
+
+"x1y3y2"  true
+"y2 x1"   true
+"1x2y"    false
+"x1"      false
+```
+
+## 📍 `Reactions` 类型
+
+| content | emoji |
+| -- | -- |
+| `+1` | 👍 |
+| `-1` | 👎 |
+| `laugh` | 😄 |
+| `confused` | 😕 |
+| `heart` | ❤️ |
+| `hooray` | 🎉 |
+| `rocket` | 🚀 |
+| `eyes` | 👀 |
+
+如需详细了解，可 [查看](https://docs.github.com/en/free-pro-team@latest/rest/reference/reactions)。
+
+## 📍 `comment-id`
+
+点击某个评论右上角 `···` 图标，选择 `Copy link`，url 末尾数字即是 `comment_id`。

docs/guide/start.en-US.md

@@ -0,0 +1,67 @@
+## Quick start
+
+### 1. New Action
+
+Click Actions in the warehouse, if Actions have been added, the following interface will be displayed.
+
+![](../../public/add-1.jpg)
+
+Click `New workflow` to add.
+
+![](../../public/add-2.jpg)
+
+<Alert type="success">
+You can click <Badge>set up a workflow yourself</Badge> to add a custom action, or you can apply a new action based on a template. <a target="_blank" href="https://github.com/actions-cool/.github">Templates</a>.
+</Alert>
+
+### 2. Edit Action
+
+Actions storage address is fixed, unified as `/.github/workflows/xx.yml`.
+
+Let's take the example of the home page and explain it in detail. The corresponding scenario is: when an issue adds the `help wanted` tag, the system will automatically comment.
+
+```yml
+name: Issue Reply
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  reply-helper:
+    runs-on: ubuntu-latest
+    steps:
+      - name: help wanted
+        if: github.event.label.name == 'help wanted'
+        uses: actions-cool/issues-helper@v2.0.0
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello @${{ github.event.issue.user.login }}. We totally like your proposal/feedback, welcome PR。
+
+            你好 @${{ github.event.issue.user.login }}，我们完全同意你的提议/反馈，欢迎PR。
+```
+- `YML` syntax reference
+  - [Workflow syntax for GitHub Actions](https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#on)
+- `name`: The workflow name
+  - Actions workflow name, can be customized according to actual situation
+- `on`: The action trigger condition
+  - Reference [Events that trigger workflows](https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows)
+- `uses`: Use actions name
+  - `uses: actions-cool/issues-helper@v2.0.0`。Please [refer](/en-US/changelog) to version selection
+- `issues-hepler` parameter
+  - `actions`: The name of the function used, **required**. Support multiple, separated by commas, such as `create-comment,close-issue` means comment and close issue
+  - `token`: A person who needs to have push permission token
+    - [More view](/en-US/guide/ref#-token)
+  - `issue-number`: Incoming parameter, here means the number of the current issue. If you are confused about the writing, you can [view](https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions#github-context)
+  - `body`: Incoming parameters, here means the content of the current comment
+
+### 3. Enable Action
+
+When you finish writing and submit to the master branch, you can automatically enable the workflow, and the trigger conditions follow the definition of `on`.
+
+😏 I believe that you have a general understanding of `how to use`, do you want to try it quickly?
+
+Please check the functions you need in [Basic](/en-US/base) and [Advanced](/en-US/advanced) for flexible reference.

docs/guide/start.md

@@ -0,0 +1,67 @@
+## 快速开始
+
+### 1. 新建 Action
+
+点击仓库的 Actions，若已增加过 Actions，会显示如下界面。
+
+![](../../public/add-1.jpg)
+
+点击 `New workflow` 新增。
+
+![](../../public/add-2.jpg)
+
+<Alert type="success">
+你可以点击 <Badge>set up a workflow yourself</Badge> 新增一个自定义 action，也可以根据模板来套用新增一个 action。<a target="_blank" href="https://github.com/actions-cool/.github">模板使用</a>。
+</Alert>
+
+### 2. 编写 Action
+
+Actions 存放地址是固定的，统一为 `/.github/workflows/xx.yml`。
+
+下面拿首页的例子详细说明下。对应场景为：当一个 issue 新增 `help wanted` 标签时，系统会自动进行评论。
+
+```yml
+name: Issue Reply
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  reply-helper:
+    runs-on: ubuntu-latest
+    steps:
+      - name: help wanted
+        if: github.event.label.name == 'help wanted'
+        uses: actions-cool/issues-helper@v2.0.0
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello @${{ github.event.issue.user.login }}. We totally like your proposal/feedback, welcome PR。
+
+            你好 @${{ github.event.issue.user.login }}，我们完全同意你的提议/反馈，欢迎PR。
+```
+- `YML` 语法参考
+  - [GitHub Actions 语法](https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#on)
+- `name`：workflow 名称
+  - Actions 流程名称，可根据实际情况自定义
+- `on`：action 触发条件
+  - 参考 [工作流触发机制](https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows)
+- `uses`：使用 actions 名称
+  - `uses: actions-cool/issues-helper@v2.0.0`。版本选择请 [参考](/changelog)
+- `issues-hepler` 参数
+  - `actions`：使用功能的名称，**必填**。支持多个，需用逗号隔开，如 `create-comment,close-issue` 表示评论和关闭 issue
+  - `token`：需拥有 push 权限的人员 token
+    - 更多 [参考](/guide/ref#-token-说明)
+  - `issue-number`：传入参数，这里表示当前 issue 的编号。如果你对写法疑惑，可 [查看](https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions#github-context)
+  - `body`：传入参数，这里表示当前进行评论的内容
+
+### 3. 启用 Action
+
+当你完成编写完成提交到主分支后，即可自动启用该 workflow，触发条件遵循 `on` 的定义。
+
+😏 相信到这里你已经对 `如何使用` 有了大概的了解，是不是想快点尝试一下。
+
+下面请在 [基 础](/base) 和 [进 阶](/advanced) 查看你需要的功能，灵活参考。

docs/index.en-US.md

@@ -0,0 +1,62 @@
+---
+title: Issues Helper
+order: 1
+hero:
+  title: Issues Helper
+  image: https://avatars1.githubusercontent.com/u/73879334?s=200&v=4
+  desc: 🤖 A GitHub Action that easily helps you automatically manage issues
+  actions:
+    - text: Quick start
+      link: /en-US/guide/start
+features:
+  - icon: https://github.com/actions-cool/resources/blob/main/image/free.png?raw=true
+    title: Completely free
+    desc: Use the Actions service provided by GitHub
+  - icon: https://github.com/actions-cool/resources/blob/main/image/snap.png?raw=true
+    title: Easy to use
+    desc: Detailed tutorials and rich templates
+  - icon: https://github.com/actions-cool/resources/blob/main/image/network.png?raw=true
+    title: Easy hosting
+    desc: As long as GitHub is not down, it will not be affected
+footer: Open-source MIT Licensed | Copyright © 2020-present<br />Powered by xrkffgg
+---
+
+## 🍭 Get started quickly
+
+Here is a very simple and commonly used example. The corresponding scenario is: when an issue adds the `help wanted` tag, the system will automatically comment.
+
+```yml
+name: Issue Reply
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  reply-helper:
+    runs-on: ubuntu-latest
+    steps:
+      - name: help wanted
+        if: github.event.label.name == 'help wanted'
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello @${{ github.event.issue.user.login }}. We totally like your proposal/feedback, welcome PR。
+
+            你好 @${{ github.event.issue.user.login }}，我们完全同意你的提议/反馈，欢迎PR。
+```
+
+## 💖 Who is using?
+
+<embed src="../README.md#RE-/<table>[^]+?[\r\n]<\/table>/"></embed>
+
+## ⚡ Feedback
+
+You are very welcome to try it out and put forward your comments. You can use the following methods:
+
+- Report bugs or consult with [Issue](https://github.com/actions-cool/issues-helper/issues)
+- Discuss via [Discussions](https://github.com/actions-cool/issues-helper/discussions)
+- Submit [Pull Request](https://github.com/actions-cool/issues-helper/pulls) to improve the code of `issues-helper`

docs/index.md

@@ -0,0 +1,66 @@
+---
+title: Issues 助手
+order: 1
+hero:
+  title: Issues 助手
+  image: https://avatars1.githubusercontent.com/u/73879334?s=200&v=4
+  desc: 🤖 一个轻松帮你自动管理 issues 的 GitHub Action
+  actions:
+    - text: 快速开始
+      link: /guide/start
+features:
+  - icon: https://github.com/actions-cool/resources/blob/main/image/free.png?raw=true
+    title: 完全免费
+    desc: 使用 GitHub 自带提供的 Actions 服务
+  - icon: https://github.com/actions-cool/resources/blob/main/image/snap.png?raw=true
+    title: 简单易用
+    desc: 教程详细，模版丰富
+  - icon: https://github.com/actions-cool/resources/blob/main/image/network.png?raw=true
+    title: 轻松托管
+    desc: 只要 GitHub 不宕机，它就不受影响
+footer: Open-source MIT Licensed | Copyright © 2020-present<br />Powered by xrkffgg
+---
+
+## 🍭 快速上手
+
+这里列举一个非常简单以及常用的例子。对应场景为：当一个 issue 新增 `help wanted` 标签时，系统会自动进行评论。
+
+```yml
+name: Issue Reply
+
+on:
+  issues:
+    types: [labeled]
+
+jobs:
+  reply-helper:
+    runs-on: ubuntu-latest
+    steps:
+      - name: help wanted
+        if: github.event.label.name == 'help wanted'
+        uses: actions-cool/issues-helper@v2
+        with:
+          actions: 'create-comment'
+          token: ${{ secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          body: |
+            Hello @${{ github.event.issue.user.login }}. We totally like your proposal/feedback, welcome PR。
+
+            你好 @${{ github.event.issue.user.login }}，我们完全同意你的提议/反馈，欢迎PR。
+```
+
+## 💖 谁在使用？
+
+<embed src="../README.md#RE-/<table>[^]+?[\r\n]<\/table>/"></embed>
+
+## ⚡ 反馈
+
+非常欢迎你来尝试使用，并提出意见，你可以通过以下方式：
+
+- 通过 [Issue](https://github.com/actions-cool/issues-helper/issues) 报告 bug 或进行咨询
+- 通过 [Discussions](https://github.com/actions-cool/issues-helper/discussions) 进行讨论
+- 提交 [Pull Request](https://github.com/actions-cool/issues-helper/pulls) 改进 `issues-helper` 的代码
+
+也欢迎加入 钉钉交流群
+
+![](https://github.com/actions-cool/resources/blob/main/dingding.jpeg?raw=true)

less/main.less

@@ -0,0 +1,3 @@
+html {
+  scroll-behavior: smooth;
+}

less/markdown.less

@@ -0,0 +1,20 @@
+.markdown table {
+  width: auto !important;
+
+  a:hover {
+    text-decoration: none;
+  }
+}
+
+.markdown table td:first-child {
+  font-weight: normal !important;
+}
+
+code {
+  padding: 1px 5px !important;
+  border-radius: 4px;
+  color: #ff7875 !important;
+  background: rgba(0, 0, 0, 0.06) !important;
+  box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.1);
+  border: 1px solid rgba(0,0,0,0.1);
+}

package.json

@@ -1,17 +1,28 @@
 {
-  "name": "issue-helper",
-  "version": "1.0",
   "private": true,
-  "description": "Some operations on issue.",
+  "description": "A GitHub Action easily helps you automatically manage issues.",
   "main": "src/main.js",
   "scripts": {
-    "package": "ncc build src/main.js -o dist"
+    "start": "dumi dev",
+    "docs:build": "dumi build",
+    "docs-dev:build": "UMI_ENV=dev dumi build",
+    "docs:deploy": "gh-pages -d docs-dist",
+    "deploy": "npm run docs:build && npm run docs:deploy",
+    "format": "prettier --write **/*.ts **/*.js",
+    "format-check": "prettier --check **/*.ts **/*.js",
+    "test": "father test",
+    "package": "ncc build src/main.js -o dist",
+    "users": "node ./script/update-users.js",
+    "main": "node ./src/main.js",
+    "ver": "node ./script/update-version.js",
+    "pub": "npm run package"
   },
   "author": "xrkffgg",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/actions-cool/issue-helper.git"
+    "url": "https://github.com/actions-cool/issues-helper.git",
+    "branch": "main"
   },
   "keywords": [
     "actions",
@@ -23,10 +34,16 @@
     "@actions/core": "^1.2.6",
     "@actions/github": "^4.0.0",
     "@octokit/rest": "^18.0.12",
-    "dayjs": "^1.9.7"
+    "actions-util": "^1.1.3",
+    "dayjs": "^1.9.7",
+    "father": "^2.30.7",
+    "lodash": "^4.17.20"
   },
   "devDependencies": {
+    "@umijs/fabric": "^2.5.6",
     "@vercel/ncc": "^0.25.1",
-    "dotenv": "^8.2.0"
+    "common-tags": "^1.8.2",
+    "dumi": "^1.1.26",
+    "gh-pages": "^3.1.0"
   }
 }

script/update-users.js

@@ -0,0 +1,111 @@
+const { readFileSync, writeFileSync } = require('fs');
+const { stripIndent } = require('common-tags');
+
+// **************************************************************************
+
+let { users } = require('../USERS.js');
+
+users.sort((a, b) => getCurrentName(a).localeCompare(getCurrentName(b)));
+
+// **************************************************************************
+const DEFAULT_WIDTH = 46;
+
+// **************************************************************************
+let table = '';
+let row = users.length / 4;
+let lastNo = users.length % 4;
+if (lastNo != 0) row += 1;
+for (let j = 1; j <= row; j++) {
+  let data = '';
+  data = stripIndent`
+<tr>
+  <td align="center" width="180">${getImg(users[(j - 1) * 4])}</td>
+  <td align="center" width="180">${getImg(users[(j - 1) * 4 + 1])}</td>
+  <td align="center" width="180">${getImg(users[(j - 1) * 4 + 2])}</td>
+  <td align="center" width="180">${getImg(users[(j - 1) * 4 + 3])}</td>
+</tr>
+<tr>
+  <td align="center" width="180">${getName(users[(j - 1) * 4])}</td>
+  <td align="center" width="180">${getName(users[(j - 1) * 4 + 1])}</td>
+  <td align="center" width="180">${getName(users[(j - 1) * 4 + 2])}</td>
+  <td align="center" width="180">${getName(users[(j - 1) * 4 + 3])}</td>
+</tr>
+`;
+  table += data;
+}
+
+table = `<table>
+${table}
+</table>
+
+`;
+
+// **************************************************************************
+
+const point = '<table>';
+const cnPoint = `## README 图标`;
+const enPoint = `## README Badge`;
+
+// **************************************************************************
+
+const cn = readFileSync('./README.md', 'utf8');
+const cnIn = cn.indexOf(point);
+const cnAfterIn = cn.indexOf(cnPoint);
+const cnBefore = cn.substring(0, cnIn);
+const cnAfter = cn.substring(cnAfterIn, cn.length);
+const newcn = cnBefore + table + cnAfter;
+writeFileSync('./README.md', newcn);
+console.log(`🎉 Done cn`);
+
+// **************************************************************************
+
+const en = readFileSync('./README.en-US.md', 'utf8');
+const enIn = en.indexOf(point);
+const enAfterIn = en.indexOf(enPoint);
+const enBefore = en.substring(0, enIn);
+const enAfter = en.substring(enAfterIn, en.length);
+const newen = enBefore + table + enAfter;
+writeFileSync('./README.en-US.md', newen);
+console.log(`🎉 Done en`);
+
+// **************************************************************************
+
+function getImg(o) {
+  if (o) {
+    return `
+    <a href="${o.url}">
+      <img src="${o.logo}"${getImgWidth(o)}/>
+    </a>
+  `;
+  }
+  return ``;
+}
+
+function getImgWidth(o) {
+  if (o) {
+    let width = o.width;
+    if (width === 'auto') {
+      width = '';
+    } else {
+      width = width ? width : DEFAULT_WIDTH;
+    }
+    return ` width="${width}"`;
+  }
+  return '';
+}
+
+function getName(o) {
+  if (o) {
+    return `<a href="${o.url}">${o.url.split('/').slice(-1)[0]}</a>`;
+  }
+  return ``;
+}
+
+function getCurrentName(o) {
+  if (o) {
+    return o.url.split('/').slice(-1)[0];
+  }
+  return ``;
+}
+
+// **************************************************************************

script/update-version.js

@@ -0,0 +1,44 @@
+const { readFileSync, writeFileSync } = require('fs');
+
+const last = /v2\.4\.2/g;
+const now = `v2`;
+
+let readme = readFileSync('./README.md', 'utf-8');
+readme = readme.replace(last, now);
+writeFileSync('./README.md', readme);
+console.log('readme done!');
+
+let readmeen = readFileSync('./README.en-US.md', 'utf-8');
+readmeen = readmeen.replace(last, now);
+writeFileSync('./README.en-US.md', readmeen);
+console.log('readmeen done!');
+
+let index = readFileSync('./docs/index.md', 'utf-8');
+index = index.replace(last, now);
+writeFileSync('./docs/index.md', index);
+console.log('index done!');
+
+let indexen = readFileSync('./docs/index.en-US.md', 'utf-8');
+indexen = indexen.replace(last, now);
+writeFileSync('./docs/index.en-US.md', indexen);
+console.log('indexen done!');
+
+let base = readFileSync('./docs/base.md', 'utf-8');
+base = base.replace(last, now);
+writeFileSync('./docs/base.md', base);
+console.log('base done!');
+
+let baseen = readFileSync('./docs/base.en-US.md', 'utf-8');
+baseen = baseen.replace(last, now);
+writeFileSync('./docs/base.en-US.md', baseen);
+console.log('baseen done!');
+
+let adv = readFileSync('./docs/advanced.md', 'utf-8');
+adv = adv.replace(last, now);
+writeFileSync('./docs/advanced.md', adv);
+console.log('adv done!');
+
+let adven = readFileSync('./docs/advanced.en-US.md', 'utf-8');
+adven = adven.replace(last, now);
+writeFileSync('./docs/advanced.en-US.md', adven);
+console.log('adven done!');

src/advanced.js

@@ -1,55 +1,56 @@
-require('dotenv').config();
-const core = require("@actions/core");
+const core = require('@actions/core');
 const { Octokit } = require('@octokit/rest');
 
-var dayjs = require('dayjs');
-var utc = require('dayjs/plugin/utc');
-dayjs.extend(utc);
-var isSameOrBefore = require('dayjs/plugin/isSameOrBefore');
-dayjs.extend(isSameOrBefore);
-
 const {
   doAddLabels,
-  doCloseIssue,
   doCreateComment,
-  doLockIssue
+  doCloseIssue,
+  doLockIssue,
+  doCreateIssue,
 } = require('./base.js');
 
-const { dealInput, matchKeyword } = require('./util.js');
+const { doQueryIssues, getIssuesInMonth, getCreatedMonth } = require('./public.js');
 
+const { dealStringToArr, matchKeyword, getPreMonth } = require('./util.js');
+
+// **************************************************************************
+var dayjs = require('dayjs');
+var utc = require('dayjs/plugin/utc');
+dayjs.extend(utc);
+
+// **************************************************************************
 const token = core.getInput('token');
 const octokit = new Octokit({ auth: `token ${token}` });
 
-let direction = core.getInput("direction");
+let direction = core.getInput('direction');
 direction = direction === 'desc' ? 'desc' : 'asc';
-
-const commentAuth = core.getInput("comment-auth");
+const commentAuth = core.getInput('comment-auth');
 const bodyIncludes = core.getInput('body-includes');
 const titleIncludes = core.getInput('title-includes');
+const titleRemove = core.getInput('title-excludes');
 const assigneeIncludes = core.getInput('assignee-includes');
 
-const issueCreator = core.getInput("issue-creator");
-const issueAssignee = core.getInput('issue-assignee');
-const issueMentioned = core.getInput('issue-mentioned');
-
-let issueState = core.getInput("issue-state") || 'all';
-
-if (issueState != 'open' && issueState != 'closed') {
-  issueState = 'all';
+let issueState = core.getInput('issue-state') || 'open';
+if (issueState != 'all' && issueState != 'closed') {
+  issueState = 'open';
 }
 
-const inactiveDay = core.getInput("inactive-day");
-const inactiveLabel = core.getInput("inactive-label") || 'inactive';
+const inactiveLabel = core.getInput('inactive-label') || 'inactive';
 
-async function doCheckInactive (owner, repo, labels) {
+// **************************************************************************
+async function doCheckInactive(owner, repo, labels) {
   const issues = await doQueryIssues(owner, repo, labels, issueState);
 
   if (issues.length) {
     for (let i = 0; i < issues.length; i++) {
-      if (!JSON.stringify(issues[i].labels).includes(inactiveLabel)) {
+      let arr = [];
+      issues[i].labels.forEach(it => {
+        arr.push(it.name);
+      });
+      if (!arr.includes(inactiveLabel)) {
         await doAddLabels(owner, repo, issues[i].number, inactiveLabel);
-        if (core.getInput("body")) {
-          await doCreateComment(owner, repo, issues[i].number, core.getInput("body"));
+        if (core.getInput('body')) {
+          await doCreateComment(owner, repo, issues[i].number, core.getInput('body'));
         }
       } else {
         core.info(`Actions: [add-inactive] issue ${issues[i].number} has label!`);
@@ -58,80 +59,85 @@ async function doCheckInactive (owner, repo, labels) {
   } else {
     core.info(`Actions: [query-issues] empty!`);
   }
-};
+}
 
 /**
  * 检查 issue 是否满足条件，满足返回 true
  * 当前 issue 的指定人是否有一个满足 assigneeIncludes 里的某个
  * 关键字匹配，是否包含前一个某个+后一个某个 '官网,网站/挂了,无法访问'
  */
-async function doCheckIssue (owner, repo, issueNumber) {
-  var checkResult = true;
+async function doCheckIssue(owner, repo, issueNumber) {
+  let checkResult = true;
   const issue = await octokit.issues.get({
     owner,
     repo,
-    issue_number: issueNumber
+    issue_number: issueNumber,
   });
 
   if (!!checkResult && assigneeIncludes) {
-    let assigneesCheck = dealInput(assigneeIncludes);
+    let assigneesCheck = dealStringToArr(assigneeIncludes);
     let checkAssignee = false;
     issue.data.assignees.forEach(it => {
       if (checkResult && !checkAssignee && assigneesCheck.includes(it.login)) {
         checkResult = true;
         checkAssignee = true;
       }
-    })
-    !checkAssignee ? checkResult = false : null;
+    });
+    !checkAssignee ? (checkResult = false) : null;
+  }
+
+  if (!!checkResult && titleRemove) {
+    const removes = dealStringToArr(titleRemove);
+    let t = issue.data.title;
+    removes.forEach(re => {
+      t = t.replace(re, '');
+    });
+    if (t.trim().length == 0) {
+      checkResult = false;
+    }
   }
 
   if (!!checkResult && titleIncludes) {
     const titleArr = titleIncludes.split('/');
-    const keyword1 = dealInput(titleArr[0]);
-    const keyword2 = dealInput(titleArr[1]);
-    checkResult =
-      keyword2.length ?
-        matchKeyword(issue.data.title, keyword1) && matchKeyword(issue.data.title, keyword2) :
-        matchKeyword(issue.data.title, keyword1);
+    const keyword1 = dealStringToArr(titleArr[0]);
+    const keyword2 = dealStringToArr(titleArr[1]);
+    checkResult = keyword2.length
+      ? matchKeyword(issue.data.title, keyword1) && matchKeyword(issue.data.title, keyword2)
+      : matchKeyword(issue.data.title, keyword1);
   }
 
   if (!!checkResult && bodyIncludes) {
     const bodyArr = bodyIncludes.split('/');
-    const keyword1 = dealInput(bodyArr[0]);
-    const keyword2 = dealInput(bodyArr[1]);
-    checkResult =
-      keyword2.length ?
-        matchKeyword(issue.data.body, keyword1) && matchKeyword(issue.data.body, keyword2) :
-        matchKeyword(issue.data.body, keyword1);
+    const keyword1 = dealStringToArr(bodyArr[0]);
+    const keyword2 = dealStringToArr(bodyArr[1]);
+    checkResult = keyword2.length
+      ? matchKeyword(issue.data.body, keyword1) && matchKeyword(issue.data.body, keyword2)
+      : matchKeyword(issue.data.body, keyword1);
   }
   core.info(`Actions: [check-issue][${!!checkResult}] success!`);
-  core.setOutput("check-result", !!checkResult);
-};
+  core.setOutput('check-result', !!checkResult);
+}
 
-async function doCloseIssues (owner, repo, labels) {
+async function doCloseIssues(owner, repo, labels) {
   const issues = await doQueryIssues(owner, repo, labels, 'open');
 
   if (issues.length) {
     for (let i = 0; i < issues.length; i++) {
       await doCloseIssue(owner, repo, issues[i].number);
-      if (core.getInput("body")) {
-        await doCreateComment(owner, repo, issues[i].number, core.getInput("body"));
+      if (core.getInput('body')) {
+        await doCreateComment(owner, repo, issues[i].number, core.getInput('body'));
       }
     }
   } else {
     core.info(`Actions: [query-issues] empty!`);
   }
-};
+}
 
-async function doFindComments (owner, repo, issueNumber) {
-  const res = await octokit.issues.listComments({
-    owner,
-    repo,
-    issue_number: issueNumber
-  });
+async function doFindComments(owner, repo, issueNumber) {
+  const commentList = await listComments(owner, repo, issueNumber);
   core.info(`Actions: [find-comments][${issueNumber}] success!`);
   let comments = [];
-  res.data.forEach(item => {
+  commentList.forEach(item => {
     const a = commentAuth ? item.user.login === commentAuth : true;
     const b = bodyIncludes ? item.body.includes(bodyIncludes) : true;
     if (a && b) {
@@ -140,76 +146,173 @@ async function doFindComments (owner, repo, issueNumber) {
         auth: item.user.login,
         body: item.body,
         created: item.created_at,
-        updated: item.updated_at
-      })
+        updated: item.updated_at,
+      });
       if (direction === 'desc') {
         comments.reverse();
       }
     }
-  })
-  core.setOutput("comments", comments);
-};
+  });
+  core.setOutput('comments', comments);
+  core.info(`out-comments: ${JSON.stringify(comments)}`);
+}
 
-async function doLockIssues (owner, repo, labels) {
+async function listComments(owner, repo, issueNumber, page = 1) {
+  let { data: comments } = await octokit.issues.listComments({
+    owner,
+    repo,
+    issue_number: issueNumber,
+    per_page: 100,
+    page,
+  });
+  if (comments.length >= 100) {
+    comments = comments.concat(await listComments(page + 1));
+  }
+  return comments;
+}
+
+async function doLockIssues(owner, repo, labels) {
   const issues = await doQueryIssues(owner, repo, labels, issueState);
 
   if (issues.length) {
     for (let i = 0; i < issues.length; i++) {
       await doLockIssue(owner, repo, issues[i].number);
-      if (core.getInput("body")) {
-        await doCreateComment(owner, repo, issues[i].number, core.getInput("body"));
+      if (core.getInput('body')) {
+        await doCreateComment(owner, repo, issues[i].number, core.getInput('body'));
       }
     }
   } else {
     core.info(`Actions: [query-issues] empty!`);
   }
-};
+}
 
-async function doQueryIssues (owner, repo, labels, state) {
-  let params = {
-    owner,
-    repo,
-    state,
-  };
+async function doMonthStatistics(owner, repo, labels, assignees) {
+  const countLables = core.getInput('count-lables');
+  const countComments = core.getInput('count-comments');
 
-  issueCreator ? params.creator = issueCreator : null;
-  issueAssignee ? params.assignee = issueAssignee : null;
-  issueMentioned ? params.mentioned = issueMentioned : null;
+  const thisMonth = dayjs.utc().month() + 1;
+  const year = thisMonth == 1 ? dayjs.utc().year() - 1 : dayjs.utc().year();
 
-  if (labels) {
-    params.labels = labels;
+  const month = getPreMonth(thisMonth);
+  const showMonth = month < 10 ? `0${month}` : month;
+
+  let issues = await getIssuesInMonth(owner, repo, thisMonth);
+  if (issues.length == 0) {
+    core.info(`Actions: [query-issues-${month}] empty!`);
+    return false;
+  }
+  issues = issues.filter(i => {
+    return getCreatedMonth(i.created_at) == month;
+  });
+  let total = issues.length;
+  let totalIssues = [...issues];
+  let openTotal = 0;
+  let openIssuesNumber = [];
+  let closeTotal = 0;
+  let closeIssuesNumber = [];
+  let labelsTotals = [];
+  const title = `[${owner}/${repo}] Month Statistics: ${year}-${showMonth}`;
+  for (let i = 0; i < issues.length; i++) {
+    if (issues[i].state == 'closed') {
+      closeTotal += 1;
+      closeIssuesNumber.push(issues[i].number);
+    } else if (issues[i].state == 'open') {
+      openTotal += 1;
+      openIssuesNumber.push(issues[i].number);
+    }
+    if (countLables && issues[i].labels) {
+      issues[i].labels.forEach(l => {
+        if (l.name in labelsTotals) {
+          labelsTotals[l.name] += 1;
+        } else {
+          labelsTotals[l.name] = 1;
+        }
+      });
+    }
+  }
+  let now = dayjs().utc().format('YYYY-MM-DD HH:mm:ss');
+  let body = `
+- Created time: ${now}
+
+- Time base: UTC +0
+`;
+  let totalShow = `
+### Count
+
+| Total | Open | Closed |
+| -- | -- | -- |
+| ${total} | ${openTotal} | ${closeTotal} |
+
+`;
+
+  body += totalShow;
+
+  if (countLables == 'true') {
+    let labelsArr = [];
+    for (var lab in labelsTotals) {
+      labelsArr.push({
+        labelName: lab,
+        number: labelsTotals[lab],
+      });
+    }
+    labelsArr.sort((a, b) => b.number - a.number);
+    let labelsTitle = `
+### Labels statistics
+
+<table>
+<tr>
+<th>Name</th>
+<th>Number</th>
+</tr>`;
+    let labelsBody = '';
+    labelsArr.forEach(it => {
+      labelsBody += `<tr><td>${it.labelName}</td><td>${it.number}</td></tr>`;
+    });
+    body =
+      body +
+      labelsTitle +
+      labelsBody +
+      `</table>
+
+`;
   }
 
-  const res = await octokit.issues.listForRepo(params);
-  let issues = [];
-  res.data.forEach(iss => {
-    const a = bodyIncludes ? iss.body.includes(bodyIncludes) : true;
-    const b = titleIncludes ? iss.title.includes(titleIncludes) : true;
-    /**
-     * Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request.
-     * For this reason, "Issues" endpoints may return both issues and pull requests in the response.
-     * You can identify pull requests by the pull_request key.
-     */
-    if (a && b && iss.pull_request === undefined) {
-      if (inactiveDay && typeof(inactiveDay) === 'number') {
-        let lastTime = dayjs.utc().subtract(inactiveDay, 'day');
-        let updateTime = dayjs.utc(iss.updated_at);
-        if (updateTime.isSameOrBefore(lastTime)) {
-          issues.push(iss);
-        }
-      } else {
-        issues.push(iss);
-      }
-    }
-  })
+  if (countComments == 'true') {
+    totalIssues.sort((a, b) => b.comments - a.comments);
+    const maxComments = totalIssues.slice(0, 3);
+    let commentTitle = `
+### Most comments
 
-  return issues;
-};
+<table>
+<tr>
+<th>#</th>
+<th>Issue</th>
+<th>Title</th>
+<th>Number</th>
+<th>State</th>
+</tr>
+`;
+    let commentBody = '';
+    maxComments.forEach((it, ind) => {
+      commentBody += `<tr>
+<td>${ind + 1}</td>
+<td>${it.number}</td>
+<td>${it.title}</td>
+<td>${it.comments}</td>
+<td>${it.state}</td></tr>`;
+    });
+    body = body + commentTitle + commentBody + '</table>';
+  }
 
+  await doCreateIssue(owner, repo, title, body, labels, assignees);
+}
+
+// **************************************************************************
 module.exports = {
   doCheckInactive,
   doCheckIssue,
   doCloseIssues,
   doFindComments,
   doLockIssues,
+  doMonthStatistics,
 };

src/app.ts

@@ -0,0 +1,4 @@
+// For dumi style
+import '../less/main.less';
+import '../less/markdown.less';
+import '../less/dumi.less';

src/base.js

@@ -1,69 +1,74 @@
-require('dotenv').config();
-const core = require("@actions/core");
+const core = require('@actions/core');
+const github = require('@actions/github');
 const { Octokit } = require('@octokit/rest');
 
-const ALLREACTIONS = [
-  "+1",
-  "-1",
-  "laugh",
-  "confused",
-  "heart",
-  "hooray",
-  "rocket",
-  "eyes",
-];
+// **************************************************************************
+const ALLREACTIONS = ['+1', '-1', 'laugh', 'confused', 'heart', 'hooray', 'rocket', 'eyes'];
 
-const { dealInput } = require('./util.js');
+const { doQueryIssues } = require('./public.js');
 
+const {
+  dealStringToArr,
+  dealRandomAssignees,
+  testDuplicate,
+  checkPermission,
+} = require('./util.js');
+
+// **************************************************************************
 const token = core.getInput('token');
 const octokit = new Octokit({ auth: `token ${token}` });
+const context = github.context;
 
-const contents = core.getInput("contents");
+const contents = core.getInput('contents');
 
-async function doAddAssignees (owner, repo, issueNumber, assignees) {
+const randomTo = core.getInput('random-to');
+
+// **************************************************************************
+async function doAddAssignees(owner, repo, issueNumber, assignees) {
+  const arr = dealRandomAssignees(assignees, randomTo);
   await octokit.issues.addAssignees({
     owner,
     repo,
     issue_number: issueNumber,
-    assignees: dealInput(assignees)
+    assignees: arr,
   });
-  core.info(`Actions: [add-assignees][${assignees}] success!`);
-};
+  core.info(`Actions: [add-assignees][${arr}] success!`);
+}
 
-async function doAddLabels (owner, repo, issueNumber, labels) {
+async function doAddLabels(owner, repo, issueNumber, labels) {
   await octokit.issues.addLabels({
     owner,
     repo,
     issue_number: issueNumber,
-    labels: dealInput(labels)
+    labels: dealStringToArr(labels),
   });
   core.info(`Actions: [add-labels][${labels}] success!`);
-};
+}
 
-async function doCloseIssue (owner, repo, issueNumber) {
+async function doCloseIssue(owner, repo, issueNumber) {
   await octokit.issues.update({
     owner,
     repo,
     issue_number: issueNumber,
-    state: 'closed'
+    state: 'closed',
   });
   core.info(`Actions: [close-issue][${issueNumber}] success!`);
-};
+}
 
-async function doCreateComment (owner, repo, issueNumber, body) {
+async function doCreateComment(owner, repo, issueNumber, body) {
   const { data } = await octokit.issues.createComment({
     owner,
     repo,
     issue_number: issueNumber,
-    body
+    body,
   });
   core.info(`Actions: [create-comment][${body}] success!`);
-  core.setOutput("comment-id", data.id);
+  core.setOutput('comment-id', data.id);
 
   if (contents) {
-    await doCreateCommentContent(owner, repo, data.id, dealInput(contents));
+    await doCreateCommentContent(owner, repo, data.id, dealStringToArr(contents));
   }
-};
+}
 
 async function doCreateCommentContent(owner, repo, commentId, contents) {
   if (contents.length) {
@@ -73,32 +78,32 @@ async function doCreateCommentContent(owner, repo, commentId, contents) {
           owner,
           repo,
           comment_id: commentId,
-          content: item
+          content: item,
         });
         core.info(`Actions: [create-reactions][${item}] success!`);
       }
-    })
+    });
   }
-};
+}
 
-async function doCreateIssue (owner, repo, title, body, labels, assignees) {
+async function doCreateIssue(owner, repo, title, body, labels, assignees) {
   let params = {
     owner,
     repo,
     title,
     body,
-    labels: dealInput(labels),
-    assignees: dealInput(assignees),
+    labels: dealStringToArr(labels),
+    assignees: dealRandomAssignees(assignees, randomTo),
   };
 
   const { data } = await octokit.issues.create(params);
   core.info(`Actions: [create-issue][${title}] success!`);
-  core.setOutput("issue-number", data.number);
+  core.setOutput('issue-number', data.number);
 
   if (contents) {
-    await doCreateIssueContent(owner, repo, data.number, dealInput(contents));
+    await doCreateIssueContent(owner, repo, data.number, dealStringToArr(contents));
   }
-};
+}
 
 async function doCreateIssueContent(owner, repo, issueNumber, contents) {
   if (contents.length) {
@@ -108,130 +113,293 @@ async function doCreateIssueContent(owner, repo, issueNumber, contents) {
           owner,
           repo,
           issue_number: issueNumber,
-          content: item
+          content: item,
         });
         core.info(`Actions: [create-reactions][${item}] success!`);
       }
-    })
+    });
   }
-};
+}
 
-async function doDeleteComment (owner, repo, commentId) {
-  await octokit.issues.deleteComment({
-    owner,
-    repo,
-    comment_id: commentId
-  });
-  core.info(`Actions: [delete-comment][${commentId}] success!`);
-};
+async function doCreateLabel(owner, repo) {
+  const name = core.getInput('label-name');
+  const color = core.getInput('label-color') || 'ededed';
+  const description = core.getInput('label-desc') || '';
 
-async function doLockIssue (owner, repo, issueNumber) {
-  await octokit.issues.lock({
+  if (!name) {
+    core.setFailed(`This actions should input 'label-name'!`);
+    return false;
+  }
+
+  try {
+    await octokit.issues.createLabel({
+      owner,
+      repo,
+      name,
+      color,
+      description,
+    });
+    core.info(`Actions: [create-label][${name}] success!`);
+  } catch (err) {
+    console.log(err.message);
+  }
+}
+
+async function doDeleteComment(owner, repo, commentId) {
+  let id = commentId;
+
+  const outComments = core.getInput('out-comments');
+  if (outComments) {
+    const outCommentsArr = JSON.parse(outComments);
+    core.info(`Actions: [out-comments-length][${outCommentsArr.length}] success!`);
+    outCommentsArr.forEach(async item => {
+      await doDelet(item.id);
+    });
+  } else {
+    await doDelet(id);
+  }
+
+  async function doDelet(id) {
+    await octokit.issues.deleteComment({
+      owner,
+      repo,
+      comment_id: id,
+    });
+    core.info(`Actions: [delete-comment][${id}] success!`);
+  }
+}
+
+async function doLockIssue(owner, repo, issueNumber) {
+  const lockReason = core.getInput('lock-reason');
+  let params = {
     owner,
     repo,
     issue_number: issueNumber,
-  });
+  };
+  const reasons = ['off-topic', 'too heated', 'resolved', 'spam'];
+  if (lockReason && reasons.includes(lockReason)) {
+    params.lock_reason = lockReason;
+  }
+  await octokit.issues.lock(params);
   core.info(`Actions: [lock-issue][${issueNumber}] success!`);
-};
+}
 
-async function doOpenIssue (owner, repo, issueNumber) {
+async function doMarkDuplicate(owner, repo, labels) {
+  if (context.eventName != 'issue_comment') {
+    core.info(`This actions only support on 'issue_comment'!`);
+    return false;
+  }
+
+  if (context.payload.action == 'created' || context.payload.action == 'edited') {
+    const duplicateCommand = core.getInput('duplicate-command');
+    const duplicateLabels = core.getInput('duplicate-labels');
+    const removeLables = core.getInput('remove-labels');
+    const closeIssue = core.getInput('close-issue');
+    const requirePermission = core.getInput('require-permission') || 'write';
+
+    const commentId = context.payload.comment.id;
+    const commentBody = context.payload.comment.body;
+    const commentUser = context.payload.comment.user.login;
+    const issueNumber = context.payload.issue.number;
+
+    const ifCommandInput = !!duplicateCommand;
+
+    if (
+      !commentBody.includes('?') &&
+      ((ifCommandInput &&
+        commentBody.startsWith(duplicateCommand) &&
+        commentBody.split(' ')[0] == duplicateCommand) ||
+        testDuplicate(commentBody))
+    ) {
+      try {
+        const res = await octokit.repos.getCollaboratorPermissionLevel({
+          owner,
+          repo,
+          username: commentUser,
+        });
+        const { permission } = res.data;
+        if (!checkPermission(requirePermission, permission)) {
+          core.info(`The user ${commentUser} is not allow!`);
+          return false;
+        }
+
+        if (ifCommandInput) {
+          const nextBody = commentBody.replace(duplicateCommand, 'Duplicate of');
+          await doUpdateComment(owner, repo, commentId, nextBody, 'replace', true);
+        } else if (contents) {
+          await doCreateCommentContent(owner, repo, commentId, dealStringToArr(contents));
+        }
+
+        const issue = await octokit.issues.get({
+          owner,
+          repo,
+          issue_number: issueNumber,
+        });
+        let newLabels = [];
+        if (issue.data.labels.length > 0) {
+          newLabels = issue.data.labels
+            .map(({ name }) => name)
+            .filter(name => !dealStringToArr(removeLables).includes(name));
+        }
+        if (duplicateLabels) {
+          newLabels = [...newLabels, ...dealStringToArr(duplicateLabels)];
+        }
+        if (labels) {
+          newLabels = dealStringToArr(labels);
+        }
+        if (newLabels.length > 0) {
+          await doSetLabels(owner, repo, issueNumber, newLabels.toString());
+          core.info(`Actions: [mark-duplicate-labels][${newLabels}] success!`);
+        }
+
+        if (closeIssue == 'true') {
+          await doCloseIssue(owner, repo, issueNumber);
+        }
+      } catch (error) {
+        core.info(error.message);
+      }
+    } else {
+      core.info(
+        `This comment body should start whith 'duplicate-command' or 'Duplicate of' and not include '?'`,
+      );
+    }
+  } else {
+    core.info(`This actions only support on 'issue_comment' created or edited!`);
+  }
+}
+
+async function doOpenIssue(owner, repo, issueNumber) {
   await octokit.issues.update({
     owner,
     repo,
     issue_number: issueNumber,
-    state: 'open'
+    state: 'open',
   });
   core.info(`Actions: [open-issue][${issueNumber}] success!`);
-};
+}
 
-async function doRemoveAssignees (owner, repo, issueNumber, assignees) {
+async function doRemoveAssignees(owner, repo, issueNumber, assignees) {
   await octokit.issues.removeAssignees({
     owner,
     repo,
     issue_number: issueNumber,
-    assignees: dealInput(assignees),
+    assignees: dealStringToArr(assignees),
   });
   core.info(`Actions: [remove-assignees][${assignees}] success!`);
-};
+}
 
-async function doRemoveLabels (owner, repo, issueNumber, labels) {
+async function doRemoveLabels(owner, repo, issueNumber, labels) {
   const issue = await octokit.issues.get({
     owner,
     repo,
-    issue_number: issueNumber
+    issue_number: issueNumber,
   });
-  const dealLabels = dealInput(labels);
-  let addLables = [];
-  if (dealLabels.length) {
-    issue.data.labels.forEach(item => {
-      !dealLabels.includes(item.name) ? addLables.push(item.name) : '';
-    })
-    await octokit.issues.setLabels({
+
+  const baseLabels = issue.data.labels.map(({ name }) => name);
+  const removeLabels = baseLabels.filter(name => dealStringToArr(labels).includes(name));
+
+  core.info(`Actions: [filter-labels][${removeLabels.join(',')}] success!`);
+
+  for (const label of removeLabels) {
+    await octokit.issues.removeLabel({
       owner,
       repo,
       issue_number: issueNumber,
-      labels: addLables
+      name: label,
     });
-    core.info(`Actions: [remove-labels][${labels}] success!`);
+    core.info(`Actions: [remove-label][${label}] success!`);
   }
-};
 
-async function doSetLabels (owner, repo, issueNumber, labels) {
-  await octokit.issues.setLabels({
-    owner,
-    repo,
-    issue_number: issueNumber,
-    labels: dealInput(labels)
-  });
-  core.info(`Actions: [set-labels][${labels}] success!`);
-};
+  core.info(`Actions: [remove-labels][${labels}] success!`);
+}
 
-async function doUnlockIssue (owner, repo, issueNumber) {
+async function doSetLabels(owner, repo, issueNumber, labels) {
+  // 概率性出现问题：https://github.com/octokit/rest.js/issues/1982，规避 setLabels
+  if (labels) {
+    // await octokit.issues.setLabels({
+    //   owner,
+    //   repo,
+    //   issue_number: issueNumber,
+    //   labels: dealStringToArr(labels)
+    // });
+    const issue = await octokit.issues.get({
+      owner,
+      repo,
+      issue_number: issueNumber,
+    });
+    const baseLabels = issue.data.labels.map(({ name }) => name);
+    const removeLabels = baseLabels.filter(name => !dealStringToArr(labels).includes(name));
+    const addLabels = dealStringToArr(labels).filter(name => !baseLabels.includes(name));
+
+    if (removeLabels.length > 0) {
+      await doRemoveLabels(owner, repo, issueNumber, removeLabels.toString());
+      core.info(`Actions: [set-labels-remove][${removeLabels}] success!`);
+    }
+
+    if (addLabels.length > 0) {
+      await doAddLabels(owner, repo, issueNumber, addLabels.toString());
+      core.info(`Actions: [set-labels-add][${addLabels}] success!`);
+    }
+
+    core.info(`Actions: [set-labels][${labels}] success!`);
+  }
+}
+
+async function doUnlockIssue(owner, repo, issueNumber) {
   await octokit.issues.unlock({
     owner,
     repo,
     issue_number: issueNumber,
   });
   core.info(`Actions: [unlock-issue][${issueNumber}] success!`);
-};
+}
 
-async function doUpdateComment (
-  owner,
-  repo,
-  commentId,
-  body,
-  updateMode
-) {
-  const comment = await octokit.issues.getComment({
-    owner,
-    repo,
-    comment_id: commentId
-  })
-  const comment_body = comment.data.body;
+async function doUpdateComment(owner, repo, commentId, body, updateMode, ifUpdateBody) {
+  let id = commentId;
 
-  let params = {
-    owner,
-    repo,
-    comment_id: commentId
-  };
+  const outComments = core.getInput('out-comments');
+  if (outComments) {
+    const outCommentsArr = JSON.parse(outComments);
+    core.info(`Actions: [out-comments-length][${outCommentsArr.length}] success!`);
+    outCommentsArr.forEach(async item => {
+      await doComment(item.id);
+    });
+  } else {
+    await doComment(id);
+  }
 
-  if (core.getInput("body")) {
-    if (updateMode === 'append') {
-      params.body = `${comment_body}\n${body}`;
-    } else {
-      params.body = body;
+  async function doComment(id) {
+    const comment = await octokit.issues.getComment({
+      owner,
+      repo,
+      comment_id: id,
+    });
+    const comment_body = comment.data.body;
+
+    let params = {
+      owner,
+      repo,
+      comment_id: id,
+    };
+
+    if (core.getInput('body') || ifUpdateBody) {
+      if (updateMode === 'append') {
+        params.body = `${comment_body}\n${body}`;
+      } else {
+        params.body = body;
+      }
+
+      await octokit.issues.updateComment(params);
+      core.info(`Actions: [update-comment][${id}] success!`);
     }
 
-    await octokit.issues.updateComment(params);
-    core.info(`Actions: [update-comment][${commentId}] success!`);
+    if (contents) {
+      await doCreateCommentContent(owner, repo, id, dealStringToArr(contents));
+    }
   }
+}
 
-  if (contents) {
-    await doCreateCommentContent(owner, repo, commentId, dealInput(contents));
-  }
-};
-
-async function doUpdateIssue (
+async function doUpdateIssue(
   owner,
   repo,
   issueNumber,
@@ -240,26 +408,26 @@ async function doUpdateIssue (
   body,
   updateMode,
   assignees,
-  labels
+  labels,
 ) {
   const issue = await octokit.issues.get({
     owner,
     repo,
-    issue_number: issueNumber
-  })
+    issue_number: issueNumber,
+  });
   const issue_body = issue.data.body;
   const issue_title = issue.data.title;
 
   let issue_labels = [];
   if (issue.data.labels.length > 0) {
-    issue.data.labels.forEach(it =>{
+    issue.data.labels.forEach(it => {
       issue_labels.push(it.name);
     });
   }
 
   let issue_assignees = [];
   if (issue.data.assignees.length > 0) {
-    issue.data.assignees.forEach(it =>{
+    issue.data.assignees.forEach(it => {
       issue_assignees.push(it.login);
     });
   }
@@ -268,13 +436,13 @@ async function doUpdateIssue (
     owner,
     repo,
     issue_number: issueNumber,
-    state
+    state,
   };
 
-  params.title = core.getInput("title") ? title : issue_title;
+  params.title = core.getInput('title') ? title : issue_title;
 
   let next_body;
-  if (core.getInput("body")) {
+  if (core.getInput('body')) {
     if (updateMode === 'append') {
       next_body = `${issue_body}\n${body}`;
     } else {
@@ -285,8 +453,8 @@ async function doUpdateIssue (
   }
   params.body = next_body;
 
-  params.labels = labels ? dealInput(labels) : issue_labels;
-  params.assignees = assignees ? dealInput(assignees) : issue_assignees;
+  params.labels = labels ? dealStringToArr(labels) : issue_labels;
+  params.assignees = assignees ? dealStringToArr(assignees) : issue_assignees;
 
   await octokit.issues.update(params);
   core.info(`Actions: [update-issue][${issueNumber}] success!`);
@@ -294,19 +462,54 @@ async function doUpdateIssue (
   if (contents) {
     await doCreateIssueContent(owner, repo, issueNumber, contents);
   }
-};
+}
 
-// tool
+async function doWelcome(owner, repo, assignees, labels, body) {
+  const context = github.context;
+  const isIssue = !!context.payload.issue;
+  const issueContents = core.getInput('issue-contents');
+  if (!isIssue) {
+    core.setFailed('The event that triggered this action must be a issue. Error!');
+  } else {
+    const auth = context.payload.sender.login;
+    core.info(`Actions: [welcome: auth=][${auth}]`);
+    const issueNumber = context.issue.number;
+    const issues = await doQueryIssues(owner, repo, false, 'all', auth);
+    if (issues.length == 0 || (issues.length == 1 && issues[0].number == issueNumber)) {
+      if (core.getInput('body')) {
+        await doCreateComment(owner, repo, issueNumber, body);
+      } else {
+        core.info(`Actions: [welcome] no body!`);
+      }
+
+      if (assignees) {
+        await doAddAssignees(owner, repo, issueNumber, assignees);
+      }
+
+      if (labels) {
+        await doAddLabels(owner, repo, issueNumber, labels);
+      }
+
+      if (issueContents) {
+        await doCreateIssueContent(owner, repo, issueNumber, dealStringToArr(issueContents));
+      }
+    } else {
+      core.info(`Actions: [welcome][${auth}] is not first time!`);
+    }
+  }
+}
+
+// **************************************************************************
 function testContent(con) {
   if (ALLREACTIONS.includes(con)) {
     return true;
   } else {
-    core.setFailed("This actions not supported!");
+    core.setFailed('This actions not supported!');
     return false;
   }
-};
+}
 
-// exports
+// **************************************************************************
 module.exports = {
   doAddAssignees,
   doAddLabels,
@@ -315,7 +518,9 @@ module.exports = {
   doCreateCommentContent,
   doCreateIssue,
   doCreateIssueContent,
+  doCreateLabel,
   doDeleteComment,
+  doMarkDuplicate,
   doLockIssue,
   doOpenIssue,
   doRemoveAssignees,
@@ -324,4 +529,5 @@ module.exports = {
   doUnlockIssue,
   doUpdateComment,
   doUpdateIssue,
+  doWelcome,
 };

src/main.js

@@ -1,15 +1,17 @@
-const core = require("@actions/core");
-const github = require("@actions/github");
+const core = require('@actions/core');
+const github = require('@actions/github');
+const { THANKS } = require('actions-util/lib/thanks');
 
+// **************************************************************************
 const {
   doAddAssignees,
   doAddLabels,
   doCloseIssue,
   doCreateComment,
-  doCreateCommentContent,
   doCreateIssue,
-  doCreateIssueContent,
+  doCreateLabel,
   doDeleteComment,
+  doMarkDuplicate,
   doLockIssue,
   doOpenIssue,
   doRemoveAssignees,
@@ -18,6 +20,7 @@ const {
   doUnlockIssue,
   doUpdateComment,
   doUpdateIssue,
+  doWelcome,
 } = require('./base.js');
 
 const {
@@ -26,8 +29,10 @@ const {
   doCloseIssues,
   doFindComments,
   doLockIssues,
+  doMonthStatistics,
 } = require('./advanced.js');
 
+// **************************************************************************
 const ALLACTIONS = [
   // base
   'add-assignees',
@@ -35,8 +40,10 @@ const ALLACTIONS = [
   'close-issue',
   'create-comment',
   'create-issue',
+  'create-label',
   'delete-comment',
   'lock-issue',
+  'mark-duplicate',
   'open-issue',
   'remove-assignees',
   'remove-labels',
@@ -44,6 +51,7 @@ const ALLACTIONS = [
   'unlock-issue',
   'update-comment',
   'update-issue',
+  'welcome',
 
   // advanced
   'check-inactive',
@@ -51,45 +59,63 @@ const ALLACTIONS = [
   'close-issues',
   'find-comments',
   'lock-issues',
+  'month-statistics',
 ];
 
+// **************************************************************************
 async function main() {
   try {
-    const owner = github.context.repo.owner;
-    const repo = github.context.repo.repo;
+    const ctx = github.context;
 
-    const issueNumber = core.getInput('issue-number');
+    // No display to outside
+    let owner, repo;
+    if (core.getInput('repo')) {
+      owner = core.getInput('repo').split('/')[0];
+      repo = core.getInput('repo').split('/')[1];
+    } else {
+      owner = ctx.repo.owner;
+      repo = ctx.repo.repo;
+    }
+
+    let defaultNo;
+    if (ctx.eventName === 'issues' || ctx.eventName === 'issue_comment') {
+      defaultNo = ctx.payload.issue.number;
+    }
+
+    const issueNumber = core.getInput('issue-number') || defaultNo;
     const commentId = core.getInput('comment-id');
 
-    const defaultBody = `Currently at ${owner}/${repo}. And this is default comment.`
-    const body = core.getInput("body") || defaultBody;
+    const defaultBody = `Currently at ${owner}/${repo}. And this is default comment.`;
+    const body = core.getInput('body') || defaultBody;
 
     const defaultTitle = `Default Title`;
-    const title = core.getInput("title") || defaultTitle;
+    const title = core.getInput('title') || defaultTitle;
 
-    const assignees = core.getInput("assignees");
+    const assignees = core.getInput('assignees');
 
-    const labels = core.getInput("labels");
-    const state = core.getInput("state") || 'open';
+    const labels = core.getInput('labels');
+    const state = core.getInput('state') || 'open';
 
-    let updateMode = core.getInput("update-mode");
+    let updateMode = core.getInput('update-mode');
     if (updateMode !== 'append') {
       updateMode = 'replace';
     }
 
-    const actions = core.getInput("actions", { required: true });
-    const actionsArr = actions.split(',');
-    actionsArr.forEach(item => {
-      testActions(item.trim());
-    });
+    // actions
+    const actions = core.getInput('actions', { required: true });
 
-    function testActions(action) {
+    const actionsArr = actions.split(',');
+    for (const action of actionsArr) {
+      await testActions(action.trim());
+    }
+
+    async function testActions(action) {
       if (ALLACTIONS.includes(action)) {
-        choseActions(action);
+        await choseActions(action);
       } else {
-        core.setFailed("This actions not supported!");
+        core.setFailed(`Actions: [${action}] is not supported!`);
       }
-    };
+    }
 
     async function choseActions(action) {
       switch (action) {
@@ -109,12 +135,18 @@ async function main() {
         case 'create-issue':
           await doCreateIssue(owner, repo, title, body, labels, assignees);
           break;
+        case 'create-label':
+          await doCreateLabel(owner, repo);
+          break;
         case 'delete-comment':
           await doDeleteComment(owner, repo, commentId);
           break;
         case 'lock-issue':
           await doLockIssue(owner, repo, issueNumber);
           break;
+        case 'mark-duplicate':
+          await doMarkDuplicate(owner, repo, labels);
+          break;
         case 'open-issue':
           await doOpenIssue(owner, repo, issueNumber);
           break;
@@ -131,13 +163,7 @@ async function main() {
           await doUnlockIssue(owner, repo, issueNumber);
           break;
         case 'update-comment':
-          await doUpdateComment(
-            owner,
-            repo,
-            commentId,
-            body,
-            updateMode
-          );
+          await doUpdateComment(owner, repo, commentId, body, updateMode);
           break;
         case 'update-issue':
           await doUpdateIssue(
@@ -149,55 +175,43 @@ async function main() {
             body,
             updateMode,
             assignees,
-            labels
+            labels,
           );
           break;
+        case 'welcome':
+          await doWelcome(owner, repo, assignees, labels, body);
+          break;
 
         // advanced
         case 'check-inactive':
-          await doCheckInactive(
-            owner,
-            repo,
-            labels
-          )
+          await doCheckInactive(owner, repo, labels);
           break;
         case 'check-issue':
-          await doCheckIssue(
-            owner,
-            repo,
-            issueNumber
-          );
+          await doCheckIssue(owner, repo, issueNumber);
           break;
         case 'close-issues':
-          await doCloseIssues(
-            owner,
-            repo,
-            labels
-          )
+          await doCloseIssues(owner, repo, labels);
           break;
         case 'find-comments':
-          await doFindComments(
-            owner,
-            repo,
-            issueNumber
-          );
+          await doFindComments(owner, repo, issueNumber);
           break;
         case 'lock-issues':
-          await doLockIssues(
-            owner,
-            repo,
-            labels
-          );
+          await doLockIssues(owner, repo, labels);
+          break;
+        case 'month-statistics':
+          await doMonthStatistics(owner, repo, labels, assignees);
           break;
         // default
         default:
           break;
       }
-    };
-  }
-  catch (error) {
+    }
+
+    core.info('\n' + THANKS);
+  } catch (error) {
     core.setFailed(error.message);
   }
 }
 
+// **************************************************************************
 main();

src/public.js

@@ -0,0 +1,139 @@
+const core = require('@actions/core');
+const { Octokit } = require('@octokit/rest');
+
+const { getPreMonth, dealStringToArr } = require('./util.js');
+
+// **************************************************************************
+var dayjs = require('dayjs');
+var utc = require('dayjs/plugin/utc');
+dayjs.extend(utc);
+var isSameOrBefore = require('dayjs/plugin/isSameOrBefore');
+dayjs.extend(isSameOrBefore);
+
+// **************************************************************************
+const token = core.getInput('token');
+const octokit = new Octokit({ auth: `token ${token}` });
+
+const perPage = 100;
+
+const issueCreator = core.getInput('issue-creator');
+const issueAssignee = core.getInput('issue-assignee');
+const issueMentioned = core.getInput('issue-mentioned');
+
+const bodyIncludes = core.getInput('body-includes');
+const titleIncludes = core.getInput('title-includes');
+
+const excludeLabels = core.getInput('exclude-labels');
+
+const inactiveDay = core.getInput('inactive-day');
+
+// **************************************************************************
+/**
+ * 查询 Issues 列表
+ * @param {*} owner
+ * @param {*} repo
+ * @param {*} labels
+ * @param {*} state
+ * @param {*} creator
+ * @returns
+ */
+async function doQueryIssues(owner, repo, labels, state, creator) {
+  let params = {
+    owner,
+    repo,
+    state,
+  };
+
+  issueCreator ? (params.creator = issueCreator) : null;
+  issueAssignee ? (params.assignee = issueAssignee) : null;
+  issueMentioned ? (params.mentioned = issueMentioned) : null;
+
+  if (labels) {
+    params.labels = labels;
+  }
+
+  if (creator) {
+    params.creator = creator;
+  }
+
+  const res = await getIssues(params);
+  let issues = [];
+  let issueNumbers = [];
+  if (res.length) {
+    const excludeLabelsArr = dealStringToArr(excludeLabels);
+    res.forEach(iss => {
+      const a = bodyIncludes ? iss.body.includes(bodyIncludes) : true;
+      const b = titleIncludes ? iss.title.includes(titleIncludes) : true;
+      /**
+       * Note: GitHub's REST API v3 considers every pull request an issue, but not every issue is a pull request.
+       * For this reason, "Issues" endpoints may return both issues and pull requests in the response.
+       * You can identify pull requests by the pull_request key.
+       */
+      if (a && b && iss.pull_request === undefined) {
+        if (excludeLabelsArr.length) {
+          for (let i = 0; i < iss.labels.length; i += 1) {
+            if (excludeLabelsArr.includes(iss.labels[i].name)) return;
+          }
+        }
+
+        if (inactiveDay) {
+          let lastTime = dayjs.utc().subtract(Number(inactiveDay), 'day');
+          let updateTime = dayjs.utc(iss.updated_at);
+          if (updateTime.isSameOrBefore(lastTime)) {
+            issues.push(iss);
+            issueNumbers.push(iss.number);
+          }
+        } else {
+          issues.push(iss);
+          issueNumbers.push(iss.number);
+        }
+      }
+    });
+    core.info(`Actions: [query-issues]: [${JSON.stringify(issueNumbers)}]!`);
+  }
+
+  return issues;
+}
+
+async function getIssues(params, page = 1) {
+  let { data: issues } = await octokit.issues.listForRepo({
+    ...params,
+    per_page: perPage,
+    page,
+  });
+  if (issues.length >= perPage) {
+    issues = issues.concat(await getIssues(params, page + 1));
+  }
+  return issues;
+}
+
+async function getIssuesInMonth(owner, repo, thisMonth, page = 1) {
+  const month = getPreMonth(thisMonth);
+  let { data: issues } = await octokit.issues.listForRepo({
+    owner,
+    repo,
+    state: 'all',
+    per_page: perPage,
+    page,
+  });
+  issues = issues.filter(i => {
+    return i.pull_request === undefined;
+  });
+  if (issues.length && getCreatedMonth(issues[issues.length - 1].created_at) >= month) {
+    issues = issues.concat(await getIssuesInMonth(owner, repo, thisMonth, page + 1));
+  }
+  return issues;
+}
+
+// **************************************************************************
+function getCreatedMonth(d) {
+  return dayjs(d).utc().month() + 1;
+}
+
+// **************************************************************************
+module.exports = {
+  doQueryIssues,
+  getIssues,
+  getIssuesInMonth,
+  getCreatedMonth,
+};

src/util.js

@@ -1,21 +1,68 @@
-function dealInput (para) {
+const sampleSize = require('lodash/sampleSize');
+
+function dealStringToArr(para) {
+  /**
+   * in  'x1,x2,x3'
+   * out ['x1','x2','x3']
+   */
   let arr = [];
   if (para) {
     const paraArr = para.split(',');
     paraArr.forEach(it => {
-      if(it.trim()){
-        arr.push(it.trim())
+      if (it.trim()) {
+        arr.push(it.trim());
       }
-    })
+    });
   }
   return arr;
-};
+}
+
+function dealRandomAssignees(assignees, randomTo) {
+  let arr = dealStringToArr(assignees);
+  if (randomTo && Number(randomTo) > 0 && Number(randomTo) < arr.length) {
+    arr = sampleSize(arr, randomTo);
+  }
+  return arr;
+}
 
 function matchKeyword(content, keywords) {
   return keywords.find(item => content.toLowerCase().includes(item));
-};
+}
 
+function testDuplicate(body) {
+  if (!body || !body.startsWith('Duplicate of')) {
+    return false;
+  }
+
+  let arr = body.split(' ');
+  if (arr[0] == 'Duplicate' && arr[1] == 'of') {
+    return true;
+  } else {
+    return false;
+  }
+}
+
+function getPreMonth(m) {
+  return m == 1 ? 12 : m - 1;
+}
+
+function checkPermission(require, permission) {
+  /**
+   * 有权限返回 true
+   */
+  const permissions = ['none', 'read', 'write', 'admin'];
+  const requireNo = permissions.indexOf(require);
+  const permissionNo = permissions.indexOf(permission);
+
+  return requireNo <= permissionNo;
+}
+
+// **********************************************************
 module.exports = {
-  dealInput,
+  dealStringToArr,
+  dealRandomAssignees,
+  getPreMonth,
   matchKeyword,
+  testDuplicate,
+  checkPermission,
 };

tests/public.test.js

@@ -0,0 +1,45 @@
+describe('Test Public', () => {
+  it('test query', () => {
+    const issues = [
+      {
+        id: 0,
+        labels: [{ name: '0' }, { name: '1' }],
+      },
+      {
+        id: 1,
+        labels: [{ name: '1' }, { name: '2' }],
+      },
+      {
+        id: 2,
+        labels: [{ name: '2' }, { name: '3' }],
+      },
+      {
+        id: 3,
+        labels: [{ name: '1' }, { name: '4' }],
+      },
+      {
+        id: 4,
+        labels: [{ name: '1' }, { name: '3' }],
+      },
+      {
+        id: 5,
+        labels: [{ name: '1' }, { name: '5' }],
+      },
+    ];
+
+    let ex = ['2', '4'];
+    let r = [];
+
+    issues.forEach(iss => {
+      for (let i = 0; i < iss.labels.length; i += 1) {
+        if (ex.includes(iss.labels[i].name)) return;
+      }
+      r.push(iss);
+    });
+
+    expect(r[0].id).toEqual(0);
+    expect(r[1].id).toEqual(4);
+    expect(r[2].id).toEqual(5);
+    expect(r.length).toEqual(3);
+  });
+});