🌟 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.
name: Check inactive-on:schedule:- cron: "0 0 1 * *"-jobs:check-inactive:runs-on: ubuntu-lateststeps:- name: check-inactiveuses: actions-cool/issues-helper@v3with:actions: 'check-inactive'token: ${{ secrets.GITHUB_TOKEN }}inactive-day: 30
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
| contents | Add reaction 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, allissue-state: The default isall. Optional valueopenclosed, when these 2 items are not, both areallissue-assignee: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Enteringnonewill query issues for which the specified person is not addedinactive-day: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, allinactive-label: The default isinactive, others can be customized. When the project does not contain the label, it will be created automaticallyexclude-labels: When set to include$exclude-empty, no label issue can be excluded
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.
name: Check Issue-on:issues:types: [edited]-jobs:check-issue:runs-on: ubuntu-lateststeps:- name: check-issueuses: actions-cool/issues-helper@v3with: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 | 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-includesbody-includessupports the formatx1,x2orx1,x2/y1,y2. Only supports two levels- Return
check-result, due to yml reasons, the judgment condition isif: 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.
name: Check need info-on:schedule:- cron: "0 0 */7 * *"-jobs:check-need-info:runs-on: ubuntu-lateststeps:- name: close-issuesuses: actions-cool/issues-helper@v3with:actions: 'close-issues'token: ${{ secrets.GITHUB_TOKEN }}labels: 'need info'inactive-day: 7
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
| contents | Add reaction 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 | ✖ |
| close-reason | Reason for closing. Default not_planned, another completed | string | ✖ |
labels: When there are multiple, the query will have multiple at the same time. If not entered, allissue-assignee: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Enteringnonewill query issues for which the specified person is not addedinactive-day: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, allexclude-labels: When set to include$exclude-empty, no label issue can be excluded
find-comments
Find the current warehouse issue No. 1, the creator is k and the content contains the comment list of this.
- name: Find commentsuses: actions-cool/issues-helper@v3with:actions: 'find-comments'token: ${{ secrets.GITHUB_TOKEN }}issue-number: 1comment-auth: 'k'body-includes: 'this'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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
commentsin the following format:
[{id: 1, auth: 'x', body: 'xxx', created: '', updated: ''},{id: 2, auth: 'x', body: 'xxx', created: '', updated: ''},]
directiondefaults to ascending order, only whendescis set, descending order will be returned- The
createdupdatedin the returned array, determined by the environment, will be UTC +0
find-issues
Find the current repository, the creator is k , the title contains this , the body contains that, and the list of issues in the open state.
- name: Find issuesuses: actions-cool/issues-helper@v3with:actions: 'find-issues'token: ${{ secrets.GITHUB_TOKEN }}issue-creator: 'k'issue-state: 'open'title-includes: 'this'body-includes: 'that'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| issue-state | State filtering | string | ✖ |
| issue-creator | Creator filtering | string | ✖ |
| title-includes | Title filtering | string | ✖ |
| body-includes | Body filtering | string | ✖ |
| exclude-labels | Exclude labels filtering | string | ✖ |
| inactive-day | Inactive days filtering | number | ✖ |
| direction | Return sort | string | ✖ |
- Returns
issuesin the following format:
[{number: 1, auth: 'x', body: 'xxx', body: 'xxx', state: 'open', created: '', updated: ''},{number: 2, auth: 'x', body: 'xxx', body: 'xxx', state: 'closed', created: '', updated: ''},]
directiondefaults to ascending order, only whendescis set, descending order will be returned- The
createdupdatedin the returned array, determined by the environment, will be UTC +0 exclude-labels: When set to include$exclude-empty, no label issue can be excluded
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.
name: Lock inactive issues-on:schedule:- cron: "0 0 1 */3 *"-jobs:lock-issues:runs-on: ubuntu-lateststeps:- name: lock-issuesuses: actions-cool/issues-helper@v3with:actions: 'lock-issues'token: ${{ secrets.GITHUB_TOKEN }}labels: 'inactive'inactive-day: 128
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| body | When operating an issue, you can comment. Do not comment when not typing | string | ✖ |
| contents | Add reaction 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, allissue-state: The default isall. Optional valueopenclosed, when these 2 items are not, both areallissue-assignee: Multiplayer is not supported. If you do not enter or enter *, all will be searched. Enteringnonewill query issues for which the specified person is not addedinactive-day: When entering, it will filter the issue update time earlier than the current time minus the number of inactive days. If not entered, allexclude-labels: When set to include$exclude-empty, no label issue can be excluded
mark-assignees
Quickly assign person, only for the issue to add editor comments.
name: Issue Mark Assignees-on:issue_comment:types: [created, edited]-jobs:mark-assignees:runs-on: ubuntu-lateststeps:- name: mark-assigneesuses: actions-cool/issues-helper@v3with:actions: 'mark-assignees'token: ${{ secrets.GITHUB_TOKEN }}
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| assign-command | Simple commands can be set, such as: /a | string | ✖ |
| require-permission | Permission required, default is write | string | ✖ |
assign-command: default/assignrequire-permission: Optional values areadmin,write,read,none- If the team member sets the
readpermission, it isread - If the external Collaborator is set to
readpermission, it isread - Ordinary users have
readpermission - When set
write,adminandwritemeet the conditions
- If the team member sets the
mark-duplicate
Quickly mark duplicate questions, only for issue new comments or edit comments.
name: Issue Mark Duplicate-on:issue_comment:types: [created, edited]-jobs:mark-duplicate:runs-on: ubuntu-lateststeps:- name: mark-duplicateuses: actions-cool/issues-helper@v3with:actions: 'mark-duplicate'token: ${{ secrets.GITHUB_TOKEN }}
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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 | ✖ |
| emoji | Add emoji for this comment | string | ✖ |
| close-issue | Whether to close the issue at the same time | string | ✖ |
| require-permission | Permission required, default is write | string | ✖ |
| close-reason | Reason for closing. Default not_planned, another completed | string | ✖ |
duplicate-command: When setting concise commands, while still supporting the originalDuplicate of. Block content contains?labels: Highest priorityclose-issue: Bothtrueor'true'can take effectrequire-permission: Optional values areadmin,write,read,none- If the team member sets the
readpermission, it isread - If the external Collaborator is set to
readpermission, it isread - Ordinary users have
readpermission - When set
write,adminandwritemeet the conditions
- If the team member sets the
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.
toggle-labels
When an issue is reopened, the set labels are removed if they already exist, otherwise they are added.
name: Toggle Labels-on:issues:types: [reopened]-jobs:toggle-labels:runs-on: ubuntu-lateststeps:- name: Toggle labelsuses: actions-cool/issues-helper@v3with:actions: 'toggle-labels'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}labels: 'unread,outdated'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
| labels | The toggle labels. Delete if the label already exists, add if it does not exist | string | ✖ |
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.
name: Issue Welcome-on:issues:types: [opened]-jobs:issue-welcome:runs-on: ubuntu-lateststeps:- name: welcomeuses: actions-cool/issues-helper@v3with:actions: 'welcome'token: ${{ secrets.GITHUB_TOKEN }}body: hi @${{ github.event.issue.user.login }}, welcome!labels: 'welcome1, welcome2'assignees: 'xx1'issue-emoji: '+1, -1, eyes'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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-emoji | Add emoji to this issue | string | ✖ |
- If these 4 options are not filled, no operation
⭐ 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.
name: Add Assigness-on:issues:types: [opened, edited]-jobs:add-assigness:runs-on: ubuntu-lateststeps:- name: Add assignessuses: actions-cool/issues-helper@v3with: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 | 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 | ✖ |
actionssupport multiple and separated by comma. Like:add-assignees,add-labels- The
namecan be modified according to the actual situation - Reference to on
${{ github.event.issue.number }}is the current issue. More referencesassigneessupport multiple and separated by comma- You can assign up to 10 people to each issue
add-labels
When the content of a new issue does not contain the specified format, add labels for the issue.
name: Add Labels-on:issues:types: [opened]-jobs:add-labels:runs-on: ubuntu-latestif: contains(github.event.issue.body, 'xxx') == falsesteps:- name: Add labelsuses: actions-cool/issues-helper@v3with: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 | 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 | ✖ |
labelssupport multiple and separated by comma
close-issue
Close the specified issue.
- name: Close issueuses: actions-cool/issues-helper@v3with:actions: 'close-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: xxx
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
| close-reason | Reason for closing. Default not_planned, another completed | string | ✖ |
create-comment
When a designated label is added, comment on the issue.
name: Create Comment-on:issues:types: [labeled]-jobs:create-comment:runs-on: ubuntu-latestif: github.event.label.name == 'xxx'steps:- name: Create commentuses: actions-cool/issues-helper@v3with: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 }}。巴拉巴拉。emoji: '+1' or '+1,heart'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| issue-number | The number of issue. When not input, it will be obtained from the trigger event | number | ✖ |
| body | Add comment content | string | ✖ |
| emoji | Add emoji | string | ✖ |
- No action when
bodyis empty - Return
comment-id, which can be used for subsequent operations. Usage reference ${{ github.event.issue.user.login }}indicates the creator of the issueemojisupport multiple and separated by comma
create-issue
Here is an example, add an issue at UTC 00:00 on the 1st of every month.
name: Create Issue-on:schedule:- cron: "0 0 1 * *"-jobs:create-issue:runs-on: ubuntu-lateststeps:- name: Create issueuses: actions-cool/issues-helper@v3with:actions: 'create-issue'token: ${{ secrets.GITHUB_TOKEN }}title: 'xxxx'body: 'xxxx'labels: 'xx'assignees: 'xxx'emoji: '+1'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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 | ✖ |
| emoji | Add emoji | string | ✖ |
titledefault isDefault Title- Return
issue-number. Usage reference
create-label
Create label. If you want to maintain labels in batches, see.
- name: Create labeluses: actions-cool/issues-helper@v3with: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 | 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 operationlabel-color: Default isededed
delete-comment
According to comment-id delete the specified comment.
- name: Delete commentuses: actions-cool/issues-helper@v3with:actions: 'delete-comment'token: ${{ secrets.GITHUB_TOKEN }}comment-id: xxx
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
| comment-id | The comment ID | number | ✔ |
get-issue
Query issue information.
- name: Get Issueuses: actions-cool/issues-helper@v3with:actions: 'get-issue'token: ${{ secrets.GITHUB_TOKEN }}
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | string | ✖ |
- Return
issue-numberissue-titleissue-bodyissue-labelsissue-assigneesissue-state. Usage reference
lock-issue
When the invalid label is added, the issue is locked.
name: Lock Issue-on:issues:types: [labeled]-jobs:lock-issue:runs-on: ubuntu-latestif: github.event.label.name == 'invalid'steps:- name: Lock issueuses: actions-cool/issues-helper@v3with:actions: 'lock-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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 areoff-topictoo heatedresolvedspam
open-issue
Open the specified issue.
- name: Open issueuses: actions-cool/issues-helper@v3with:actions: 'open-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: xxx
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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.
- name: Remove assigneesuses: actions-cool/issues-helper@v3with: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 | 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.
- name: Remove labelsuses: actions-cool/issues-helper@v3with: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 | 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 | ✔ |
labelssupports multiple, such asx1,x2,x3, only the labels added by the issue will be removed
set-labels
Replace the labels of issue.
- name: Set labelsuses: actions-cool/issues-helper@v3with: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 | 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.
- name: Unlock issueuses: actions-cool/issues-helper@v3with:actions: 'unlock-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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.
The following example shows that 👀 is added for each new comment.
name: Add eyes to each comment-on:issue_comment:types: [created]-jobs:update-comment:runs-on: ubuntu-lateststeps:- name: Update commentuses: actions-cool/issues-helper@v3with:actions: 'update-comment'token: ${{ secrets.GITHUB_TOKEN }}comment-id: ${{ github.event.comment.id }}emoji: 'eyes'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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 | ✖ |
| emoji | Add emoji | string | ✖ |
- When
bodyis not entered, it will remain as it is - When
update-modeisappend, additional operations will be performed. Anything other thanappendwill be replaced. Only effective forbody - When
out-commentsis entered,comment-iddoes not work
update-issue
Update the specified issue according to the issue-number.
- name: Update issueuses: actions-cool/issues-helper@v3with: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'emoji: '+1'
| Param | Desc | Type | Required |
|---|---|---|---|
| actions | Action type | string | ✔ |
| token | Token explain | 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 | ✖ |
| emoji | Add emoji | string | ✖ |
statedefaults toopen- When the option is not filled, it will keep the original
✨ Changelog
v3.4.0
2023.02.06
v3.3.3
2022.11.13
- 🐞 fix: body null case. #129 @madmansn0w
v3.3.2
2022.10.21
v3.3.1
2022.10.19
- 🐞 fix: body null case. #123
v3.3.0
2022.09.02
- 🚀 feat: add
get-issue. #114
v3.2.1
2022.08.31
- 🐞 fix: mark-duplicate labels invalid. #116
v3.2.0
2022.08.26
- 🚀 feat: add
$exclude-emptyforexclude-labels. #112- When set to include
$exclude-empty, no label issue can be excluded
- When set to include
v3.1.0
2022.08.09
v3.0.1
2022.08.01
- 🐞 fix: check will undefined.
v3.0.0
2022.02.15
- 🚀 New Feature
mark-assignees: Comment quick settings assigneesfind-issues: Conditional query current warehouse issues
- 🐞 Bug Fix
- Fixed
find-commentsreturn result direction not working - Fix
lock-issueslock and comment order issue
- Fixed
- 🛠 Refactor
contentsrenamed to easy-to-understandemojiissue-emojisrenamed toissue-emoji- deleteComment updateComment no longer supports
out-comments, keeping pure functionality - Remove title body default
month-statisticsis removed
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
v2.4.2
2021.09.06
- 🐞 fix:
doRemoveLabelswhen has no label. #88
v2.4.1
2021.09.05
- 🐞 fix: remove labels define error. #86
v2.4.0
2021.08.15
- 🚀 feat: support custom repo. #83
- 🚀 feat: support default issueNumber get from context. #81
- 🐞 fix: action run async. #79
v2.3.1
2021.08.09
- ⚡️ refactor: extract exclude-labels array to outer scope. #75 @meteorlxy
v2.3.0
2021.08.09
- 🚀 feat: add exclude-labels for
check-inactiveclose-issueslock-issues. #74
v2.2.1
2021.03.21
- fix: list comment page lost in
find-comments. #66
v2.2.0
2021.03.21
- feat: Added
title-excludesparameter tocheck-issue. #65
v2.1.2
2021.02.19
- feat: update/delete comment support find-comments out. #63
v2.1.1
2021.02.03
v2.1.0
2021.02.02
- feat: add create-label. #54
v2.0.0
2021.01.26
- refactor: add require-permission default. #51
v1.12
It will be the last version of 1.x
2021.01.26
v1.11
2021.01.14
v1.10
2021.01.12
- fix: duplicate labels set. #36
v1.9
2021.01.11
- feat: add random to. #35
v1.8
2021.01.07
- #31
- refactor: split content
- feat: add
remove-labelsfor duplicate - docs: optimize website
v1.7
2021.01.02
- #27
- feat: add
month-statistics - fix: query issues less because pages max 100
- fix: js nested
require
- feat: add
v1.6
2020.12.30
- perf: optimize duplicate. #24
v1.5
2020.12.30
- feat: add
mark-duplicate. #23
v1.4
2020.12.29
- fix: perfect
inactive-daycheck. #22
v1.3
2020.12.28
- feat: add welcome. #19
v1.2
2020.12.25
- feat: add check-issue & remove labels. #12
v1.1
2020.12.24
- fix: yml not support array. #11
v1
2020.12.23
🎉 First release.
Powered by xrkffgg",prefersColor:{default:"light",switch:!0},logo:"https://gw.alipayobjects.com/mdn/rms_f97235/afts/img/A*8xDgSL-O6O4AAAAAAAAAAAAAARQnAQ",nav:{"zh-CN":[{title:"\u6307 \u5357",link:"/zh-CN/guide"},{title:"\u57FA \u7840",link:"/zh-CN/base"},{title:"\u8FDB \u9636",link:"/zh-CN/advanced"},{title:"\u66F4\u65B0\u65E5\u5FD7",link:"/zh-CN/changelog"}],"en-US":[{title:"Guide",link:"/guide"},{title:"Base",link:"/base"},{title:"Advanced",link:"/advanced"},{title:"Changelog",link:"/changelog"}]},socialLinks:{github:"https://github.com/actions-cool/issues-helper"}}},children:p})}}}]); diff --git a/guide/faq/index.html b/guide/faq/index.html index 4f02818..25cbedc 100644 --- a/guide/faq/index.html +++ b/guide/faq/index.html @@ -1,47 +1,13 @@ - - - - - - - - - - -
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. 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.
Are there any ready-made templates for reference?
Yes.
- You can use this GitHub Actions workflow template repository template
- Personal exercises and tests Actions repository
- You can also refer to the warehouse of online users
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. The latest releases version is recommended.
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
- 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:
- name: Issues Helperuses: actions-cool/issues-helper@main-# or-- name: Issues Helperuses: actions-cool/issues-helper@1.x-# or-- name: Issues Helperuses: actions-cool/issues-helper@v2
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.
v3 changelog
🚀 The refactoring of the v3 version is completed. The main changes are:
- JS to TS
- Encapsulate the core functions of the issue into classes for helpers to use
- Unified prompt information
- Added automatic release script
Reference for functional changes:
- 🚀 New Feature
mark-assignees: Comment quick settings assigneesfind-issues: Conditional query current warehouse issues
- 🐞 Bug Fix
- Fixed
find-commentsreturn result direction not working - Fix
lock-issueslock and comment order issue
- Fixed
- 🛠 Refactor
contentsrenamed to easy-to-understandemojiissue-emojisrenamed toissue-emoji- deleteComment updateComment no longer supports
out-comments, keeping pure functionality - Remove title body default
month-statisticsremoved
What should I do if there is no function I want here?
You can submit it in What do you want?.
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.
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
- Discuss via Discussions
- Submit Pull Request to improve the code of
issues-helper
Here are some things I summarized in my use, I hope it can help you.
Include judgment in 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,
IEand also similar tokiekkcan also be satisfied
More.
Pass value and output in yml
with:actions: 'month-statistics'token: ${{ secrets.GITHUB_TOKEN }}count-lables: 'true'
count-lables: Regardless of settingtrueor'ture', all received in the program is in string format
At the same time, the output is also in string format. See.
check-result: The judgment condition isif: 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
assignees scope
- The owner or collaborator of the warehouse, if there is an organization, including members
- Participants of the issue, including creators and commenters
- Max 10
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.
📍 token
Need to have the person token with push permission.
- Personal token application
- Need to check
Full control of private repositories
- Need to check
- Project add secrets
- Select settings, select secrets, select
New repository secret Nameis the same as in actionsValuefill in the token just applied by the individual
- Select settings, select secrets, select
When the token is not filled in actions or input ${{ secrets.GITHUB_TOKEN }}, it will default to github-actions-bot. More.
📍 GitHub Docs
📍 outputs use
- name: Create issueuses: actions-cool/issues-helper@v1id: createissuewith:actions: 'create-issue'token: ${{ secrets.GITHUB_TOKEN }}- name: Check outputsrun: echo "Outputs issue_number is ${{ steps.createissue.outputs.issue-number }}"
More:
- https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/metadata-syntax-for-github-actions#outputs
- https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs
📍 includes check rules
"title-includes": 'x1,x2'-x1x2-"x1y3y2" true"y2 x1" true"x2" true"x3" false
"title-includes": 'x1,x2/y1,y2'-x1 + y1x2 + y1x1 + y2x2 + y2-"x1y3y2" true"y2 x1" true"1x2y" false"x1" false
📍 emoji Type
| content | emoji |
|---|---|
+1 | 👍 |
-1 | 👎 |
laugh | 😄 |
confused | 😕 |
heart | ❤️ |
hooray | 🎉 |
rocket | 🚀 |
eyes | 👀 |
For details, please view.
📍 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.
Quick start
1. New Action
Click Actions in the warehouse, if Actions have been added, the following interface will be displayed.
Click New workflow to add.
You can click set up a workflow yourself to add a custom action, or you can apply a new action based on a template. Templates.
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.
name: Issue Reply-on:issues:types: [labeled]-jobs:reply-helper:runs-on: ubuntu-lateststeps:- name: help wantedif: github.event.label.name == 'help wanted'uses: actions-cool/issues-helper@v3with: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。
YMLsyntax referencename: The workflow name- Actions workflow name, can be customized according to actual situation
on: The action trigger condition- Reference Events that trigger workflows
uses: Use actions nameuses: actions-cool/issues-helper@v2.0.0。Please refer to version selection
issues-heplerparameteractions: The name of the function used, required. Support multiple, separated by commas, such ascreate-comment,close-issuemeans comment and close issuetoken: A person who needs to have push permission tokenissue-number: Incoming parameter, here means the number of the current issue. If you are confused about the writing, you can viewbody: 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 and Advanced for flexible reference.
- Completely free
Use the Actions service provided by GitHub
- Easy to use
Detailed tutorials and rich templates
- Easy hosting
As long as GitHub is not down, it will not be affected
🍭 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.
name: Issue Reply-on:issues:types: [labeled]-jobs:reply-helper:runs-on: ubuntu-lateststeps:- name: help wantedif: github.event.label.name == 'help wanted'uses: actions-cool/issues-helper@v3with: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?
⚡ 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
- Discuss via Discussions
- Submit Pull Request to improve the code of
issues-helper
🌟 进 阶
进阶用法不建议 actions 多个一次同时使用。
check-inactive
每月 1 号 UTC 0 时，对所有 30 天以上未活跃的 issues 增加 inactive 标签。
name: Check inactive-on:schedule:- cron: "0 0 1 * *"-jobs:check-inactive:runs-on: ubuntu-lateststeps:- name: check-inactiveuses: actions-cool/issues-helper@v3with:actions: 'check-inactive'token: ${{ secrets.GITHUB_TOKEN }}inactive-day: 30
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
| emoji | 为该评论增加 emoji | 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。可选值openclosed，非这 2 项时，均为allissue-assignee：不支持多人。不填或输入 * 时，查询所有。输入none会查询未添加指定人的 issuesinactive-day：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有inactive-label：默认为inactive，可自定义其他。当项目未包含该 label 时，会自动新建exclude-labels：设置包含$exclude-empty时，可排除无 label issue
check-issue
根据传入的参数和 issue-number 来检查该 issue 是否满足条件，返回一个布尔值。
下面的例子效果是：当 issue 新开时，校验当前 issue 指定人是否包含 x1 或者 x2，满足一个指定人即可校验通过，同时校验标题是否满足条件，校验规则。
name: Check Issue-on:issues:types: [edited]-jobs:check-issue:runs-on: ubuntu-lateststeps:- name: check-issueuses: actions-cool/issues-helper@v3with: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 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| assignee-includes | 是否包含指定人 | string | ✖ |
| title-includes | 标题包含校验 | string | ✖ |
| title-excludes | 检测标题移除默认 title 后是否为空 | string | ✖ |
| body-includes | 内容包含校验 | string | ✖ |
title-includesbody-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。
name: Check need info-on:schedule:- cron: "0 0 */7 * *"-jobs:check-need-info:runs-on: ubuntu-lateststeps:- name: close-issuesuses: actions-cool/issues-helper@v3with:actions: 'close-issues'token: ${{ secrets.GITHUB_TOKEN }}labels: 'need info'inactive-day: 7
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
| emoji | 为该评论增加 emoji | string | ✖ |
| labels | 标签筛选 | string | ✖ |
| issue-assignee | 指定人筛选 | string | ✖ |
| issue-creator | 创建人筛选 | string | ✖ |
| issue-mentioned | 提及人筛选 | string | ✖ |
| body-includes | 包含内容筛选 | string | ✖ |
| title-includes | 包含标题筛选 | string | ✖ |
| inactive-day | 非活跃天数筛选 | number | ✖ |
| exclude-labels | 排除标签筛选 | string | ✖ |
| close-reason | 关闭原因。默认not_planned未计划，completed完成 | string | ✖ |
labels：为多个时，会查询同时拥有多个。不填时，会查询所有issue-assignee：不支持多人。不填或输入 * 时，查询所有。输入none会查询未添加指定人的 issuesinactive-day：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有exclude-labels：设置包含$exclude-empty时，可排除无 label issue
find-comments
查找当前仓库 1 号 issue 中，创建者是 k ，内容包含 this 的评论列表。
- name: Find commentsuses: actions-cool/issues-helper@v3with:actions: 'find-comments'token: ${{ secrets.GITHUB_TOKEN }}issue-number: 1comment-auth: 'k'body-includes: 'this'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| comment-auth | 评论创建者，不填时会查询所有 | string | ✖ |
| body-includes | 评论内容包含过滤，不填时无校验 | string | ✖ |
| direction | 返回 comments 排序 | string | ✖ |
- 返回
comments，格式如下：
[{id: 1, auth: 'x', body: 'xxx', created: '', updated: ''},{id: 2, auth: 'x', body: 'xxx', created: '', updated: ''},]
direction默认为升序，只有设置desc时，会返回降序- 返回数组中
createdupdated，由所处环境决定，会是 UTC +0
find-issues
查找当前仓库，创建者是 k ，title 包含 this ，body 包含 that，打开状态的 issues 列表。
- name: Find issuesuses: actions-cool/issues-helper@v3with:actions: 'find-issues'token: ${{ secrets.GITHUB_TOKEN }}issue-creator: 'k'issue-state: 'open'title-includes: 'this'body-includes: 'that'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-state | 状态筛选 | string | ✖ |
| issue-creator | 创建者筛选 | string | ✖ |
| title-includes | 标题包含过滤，不填时无校验 | string | ✖ |
| body-includes | 内容包含过滤，不填时无校验 | string | ✖ |
| exclude-labels | 排除标签筛选 | string | ✖ |
| inactive-day | 非活跃天数筛选 | number | ✖ |
| direction | 返回 issues 排序 | string | ✖ |
- 返回
issues，格式如下：
[{number: 1, auth: 'x', body: 'xxx', body: 'xxx', state: 'open', created: '', updated: ''},{number: 2, auth: 'x', body: 'xxx', body: 'xxx', state: 'closed', created: '', updated: ''},]
direction默认为升序，只有设置desc时，会返回降序- 返回数组中
createdupdated，由所处环境决定，会是 UTC +0 exclude-labels：设置包含$exclude-empty时，可排除无 label issue
lock-issues
每 3 个月 1 号 UTC 0 时，锁定已填加 inactive label 且 128 天以上未活跃的所有 issues。
name: Lock inactive issues-on:schedule:- cron: "0 0 1 */3 *"-jobs:lock-issues:runs-on: ubuntu-lateststeps:- name: lock-issuesuses: actions-cool/issues-helper@v3with:actions: 'lock-issues'token: ${{ secrets.GITHUB_TOKEN }}labels: 'inactive'inactive-day: 128
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| body | 操作 issue 时，可进行评论。不填时，不评论 | string | ✖ |
| emoji | 为该评论增加 emoji | 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。可选值openclosed，非这 2 项时，均为allissue-assignee：不支持多人。不填或输入 * 时，查询所有。输入none会查询未添加指定人的 issuesinactive-day：当输入时，会筛选 issue 更新时间早于当前时间减去非活跃天数。不填时，会查询所有exclude-labels：设置包含$exclude-empty时，可排除无 label issue
mark-assignees
快捷加指定人，仅作用于 issue 新增编辑评论。
name: Issue Mark Assignees-on:issue_comment:types: [created, edited]-jobs:mark-assignees:runs-on: ubuntu-lateststeps:- name: mark-assigneesuses: actions-cool/issues-helper@v3with:actions: 'mark-assignees'token: ${{ secrets.GITHUB_TOKEN }}
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| assign-command | 可设置简洁命令，如：/a | string | ✖ |
| require-permission | 要求权限，默认为 write | string | ✖ |
assign-command：可设置简洁命令。默认：/assignrequire-permission：可选值有admin，write，read，none- 团队成员若设置
read权限，则为read - 外部 Collaborator 若设置
read权限，则为read - 普通用户为
read权限 - 当设置
write后，admin和write满足条件
- 团队成员若设置
mark-duplicate
快捷标记重复问题，仅作用于 issue 新增编辑评论。
name: Issue Mark Duplicate-on:issue_comment:types: [created, edited]-jobs:mark-duplicate:runs-on: ubuntu-lateststeps:- name: mark-duplicateuses: actions-cool/issues-helper@v3with:actions: 'mark-duplicate'token: ${{ secrets.GITHUB_TOKEN }}
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| duplicate-command | 可设置简洁命令，如：/d | string | ✖ |
| duplicate-labels | 为该 issue 额外增加 labels | string | ✖ |
| remove-labels | 设置可移除的 labels | string | ✖ |
| labels | 替换该 issue 的 labels | string | ✖ |
| emoji | 为该评论的增加 emoji | string | ✖ |
| close-issue | 是否同时关闭该 issue | string | ✖ |
| require-permission | 要求权限，默认为 write | string | ✖ |
| close-reason | 关闭原因。默认not_planned未计划，completed完成 | 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满足条件
- 团队成员若设置
注意：使用简洁命令创建的 Duplicate 不显示下图红框内容。但其实这个没有任何影响的。
toggle-labels
当一个 issue 被重新打开，判断设置的 labels 如果已经存在则进行删除，否则进行添加。
name: Toggle Labels-on:issues:types: [reopened]-jobs:toggle-labels:runs-on: ubuntu-lateststeps:- name: Toggle labelsuses: actions-cool/issues-helper@v3with:actions: 'toggle-labels'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}labels: 'unread,outdated'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| labels | 切换 labels。如果 label 已存在则删除，不存在则添加 | string | ✖ |
welcome
当一个 issue 新建时，对首次新建 issue 的用户进行欢迎。若用户非首次新建，则无操作。
name: Issue Welcome-on:issues:types: [opened]-jobs:issue-welcome:runs-on: ubuntu-lateststeps:- name: welcomeuses: actions-cool/issues-helper@v3with:actions: 'welcome'token: ${{ secrets.GITHUB_TOKEN }}body: hi @${{ github.event.issue.user.login }}, welcome!labels: 'welcome1, welcome2'assignees: 'xx1'issue-emoji: '+1, -1, eyes'
- 若这 4 个可选项都不填，则无操作
为了更好的展示功能，下面以实际场景举例，请灵活参考。
⭐ 基 础
add-assignees
当一个 issue 新增或修改时，将这个 issue 指定某人或多人。
name: Add Assigness-on:issues:types: [opened, edited]-jobs:add-assigness:runs-on: ubuntu-lateststeps:- name: Add assignessuses: actions-cool/issues-helper@v3with: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 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| assignees | 指定人。当不填或者为空字符时，不操作 | string | ✖ |
| random-to | 当设置时，会在 assignees 中随机选择 | number | ✖ |
actions支持多个，需用逗号隔开。如：add-assignees,add-labels- 其中的
name可根据自行根据实际情况修改 - on 参考
${{ github.event.issue.number }}表示当前 issue，更多参考assignees支持多个，需用逗号隔开- assign 最多只能设定 10 个
add-labels
当一个新增的 issue 内容不包含指定格式时，为这个 issue 添加 labels。
name: Add Labels-on:issues:types: [opened]-jobs:add-labels:runs-on: ubuntu-latestif: contains(github.event.issue.body, 'xxx') == falsesteps:- name: Add labelsuses: actions-cool/issues-helper@v3with:actions: 'add-labels'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}labels: 'bug' or 'bug1,bug2'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| labels | 新增的 labels。当不填或者为空字符时，不新增 | string | ✖ |
labels支持多个，需用逗号隔开
close-issue
关闭指定 issue。
- name: Close issueuses: actions-cool/issues-helper@v3with:actions: 'close-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: xxx
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| close-reason | 关闭原因。默认not_planned未计划，completed完成 | string | ✖ |
create-comment
当新增一个指定 label 时，对该 issue 进行评论。
name: Create Comment-on:issues:types: [labeled]-jobs:create-comment:runs-on: ubuntu-latestif: github.event.label.name == 'xxx'steps:- name: Create commentuses: actions-cool/issues-helper@v3with: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 }}。巴拉巴拉。emoji: '+1' or '+1,heart'
body为空时，无操作- 返回
comment-id，可用于之后操作。用法参考 ${{ github.event.issue.user.login }}表示该 issue 的创建者emoji支持多个，需用逗号隔开
create-issue
感觉新增 issue 使用场景不多。这里举例，每月 1 号 UTC 00:00 新增一个 issue。
name: Create Issue-on:schedule:- cron: "0 0 1 * *"-jobs:create-issue:runs-on: ubuntu-lateststeps:- name: Create issueuses: actions-cool/issues-helper@v3with:actions: 'create-issue'token: ${{ secrets.GITHUB_TOKEN }}title: 'xxxx'body: 'xxxx'labels: 'xx'assignees: 'xxx'emoji: '+1'
title默认为：Default Title- 返回
issue-number，用法参考
create-label
新增 label。若想批量维护 labels，可查看。
- name: Create labeluses: actions-cool/issues-helper@v3with:actions: 'create-label'token: ${{ secrets.GITHUB_TOKEN }}label-name: 'xx'label-color: '0095b3'label-desc: 'xx'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| label-name | 标签名称，支持 emoji | string | ✔ |
| label-color | 标签颜色，格式为 16 进制色码，不加 # | string | ✖ |
| label-desc | 标签描述 | string | ✖ |
label-name：若已存在，则无操作label-color：默认为ededed
delete-comment
根据 comment-id 删除指定评论。
- name: Delete commentuses: actions-cool/issues-helper@v3with:actions: 'delete-comment'token: ${{ secrets.GITHUB_TOKEN }}comment-id: xxx
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| comment-id | 指定的 comment | number | ✔ |
get-issue
查询 issue 信息。
- name: Get Issueuses: actions-cool/issues-helper@v3with:actions: 'get-issue'token: ${{ secrets.GITHUB_TOKEN }}
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
- 返回
issue-numberissue-titleissue-bodyissue-labelsissue-assigneesissue-state，用法参考
lock-issue
当新增 invalid label 时，对该 issue 进行锁定。
name: Lock Issue-on:issues:types: [labeled]-jobs:lock-issue:runs-on: ubuntu-latestif: github.event.label.name == 'invalid'steps:- name: Lock issueuses: actions-cool/issues-helper@v3with:actions: 'lock-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| lock-reason | 锁定 issue 的原因 | string | ✖ |
lock-reason：可选值有off-topictoo heatedresolvedspam
open-issue
打开指定 issue。
- name: Open issueuses: actions-cool/issues-helper@v3with:actions: 'open-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: xxx
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
remove-assignees
移除 issue 指定人员。
- name: Remove assigneesuses: actions-cool/issues-helper@v3with:actions: 'remove-assignees'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}assignees: 'xx'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| assignees | 移除的指定人。当为空字符时，不进行移除 | string | ✔ |
remove-labels
移除指定 labels。
- name: Remove labelsuses: actions-cool/issues-helper@v3with:actions: 'remove-labels'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}labels: 'xx'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| labels | 移除的 labels。当为空字符时，不进行移除 | string | ✔ |
labels支持多个，如x1,x2,x3，只会移除 issue 已添加的 labels
set-labels
替换 issue 的 labels。
- name: Set labelsuses: actions-cool/issues-helper@v3with:actions: 'set-labels'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}labels: 'xx'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
| labels | labels 设置。当空字符时，会移除所有 | string | ✔ |
unlock-issue
解锁指定 issue。
- name: Unlock issueuses: actions-cool/issues-helper@v3with:actions: 'unlock-issue'token: ${{ secrets.GITHUB_TOKEN }}issue-number: ${{ github.event.issue.number }}
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | token 说明 | string | ✖ |
| issue-number | 指定的 issue，当不传时会从触发事件中获取 | number | ✖ |
update-comment
根据 comment-id 更新指定评论。
下面的例子展示的是，为每个新增的 comment 增加 👀 。
name: Add eyes to each comment-on:issue_comment:types: [created]-jobs:update-comment:runs-on: ubuntu-lateststeps:- name: Update commentuses: actions-cool/issues-helper@v3with:actions: 'update-comment'token: ${{ secrets.GITHUB_TOKEN }}comment-id: ${{ github.event.comment.id }}emoji: 'eyes'
body不填时，会保持原有update-mode为append时，会进行附加操作。非append都会进行替换。仅对body生效- 当
out-comments输入时，comment-id不起作用
update-issue
根据 issue-number 更新指定 issue。
- name: Update issueuses: actions-cool/issues-helper@v3with: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'emoji: '+1'
| 参数 | 描述 | 类型 | 必填 |
|---|---|---|---|
| actions | 操作类型 | string | ✔ |
| token | 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 | ✖ |
| emoji | 增加 emoji | string | ✖ |
state默认为open- 当可选项不填时，会保持原有
v3.4.0
2023.02.06
v3.3.3
2022.11.13
- 🐞 fix: body null case. #129 @madmansn0w
v3.3.2
2022.10.21
v3.3.1
2022.10.19
- 🐞 fix: body null case. #123
v3.3.0
2022.09.02
- 🚀 feat: add
get-issue. #114
v3.2.1
2022.08.31
- 🐞 fix: mark-duplicate labels invalid. #116
v3.2.0
2022.08.26
- 🚀 feat: add
$exclude-emptyforexclude-labels. #112- When set to include
$exclude-empty, no label issue can be excluded
- When set to include
v3.1.0
2022.08.09
v3.0.1
2022.08.01
- 🐞 fix: check will undefined.
v3.0.0
2022.02.15
- 🚀 New Feature
mark-assignees: Comment quick settings assigneesfind-issues: Conditional query current warehouse issues
- 🐞 Bug Fix
- Fixed
find-commentsreturn result direction not working - Fix
lock-issueslock and comment order issue
- Fixed
- 🛠 Refactor
contentsrenamed to easy-to-understandemojiissue-emojisrenamed toissue-emoji- deleteComment updateComment no longer supports
out-comments, keeping pure functionality - Remove title body default
month-statisticsis removed
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
v2.4.2
2021.09.06
- 🐞 fix:
doRemoveLabelswhen has no label. #88
v2.4.1
2021.09.05
- 🐞 fix: remove labels define error. #86
v2.4.0
2021.08.15
- 🚀 feat: support custom repo. #83
- 🚀 feat: support default issueNumber get from context. #81
- 🐞 fix: action run async. #79
v2.3.1
2021.08.09
- ⚡️ refactor: extract exclude-labels array to outer scope. #75 @meteorlxy
v2.3.0
2021.08.09
- 🚀 feat: add exclude-labels for
check-inactiveclose-issueslock-issues. #74
v2.2.1
2021.03.21
- fix: list comment page lost in
find-comments. #66
v2.2.0
2021.03.21
- feat: Added
title-excludesparameter tocheck-issue. #65
v2.1.2
2021.02.19
- feat: update/delete comment support find-comments out. #63
v2.1.1
2021.02.03
v2.1.0
2021.02.02
- feat: add create-label. #54
v2.0.0
2021.01.26
- refactor: add require-permission default. #51
v1.12
It will be the last version of 1.x
2021.01.26
v1.11
2021.01.14
v1.10
2021.01.12
- fix: duplicate labels set. #36
v1.9
2021.01.11
- feat: add random to. #35
v1.8
2021.01.07
- #31
- refactor: split content
- feat: add
remove-labelsfor duplicate - docs: optimize website
v1.7
2021.01.02
- #27
- feat: add
month-statistics - fix: query issues less because pages max 100
- fix: js nested
require
- feat: add
v1.6
2020.12.30
- perf: optimize duplicate. #24
v1.5
2020.12.30
- feat: add
mark-duplicate. #23
v1.4
2020.12.29
- fix: perfect
inactive-daycheck. #22
v1.3
2020.12.28
- feat: add welcome. #19
v1.2
2020.12.25
- feat: add check-issue & remove labels. #12
v1.1
2020.12.24
- fix: yml not support array. #11
v1
2020.12.23
🎉 First release.
该功能是否收费？
GitHub Actions 是由 GitHub 免费提供的。其中 Private 项目每月有 2000 次的限制，具体查看。Public 项目无限制。
有没有速率的限制？
有的。Action 底层使用的是 GitHub REST API。一般情况是每小时 5000 次。原则上基本是够用的，同时也要求在 Action 定义时，尽量避免无效的请求。具体查看。
有没有现成的模板可以参考？
有的。
- 你可以使用这个 GitHub Actions workflow template 仓库的模板
- 个人练习和测试 Actions 的仓库
- 也可以来 线上使用者 的仓库参照
我想暂停 Actions，有没有简单的办法？
有的，你可以将直接修改 actions。例如：actions: 'create-comment' 修改为 actions: '#create-comment'。同时也方便恢复。
这么多版本，如何选择？
你可以查看详细的 更新日志。推荐采用最新 releases 版本。
版本规则
- 采用两级语义化版本，如v1、v1.1、v2、v2.1
- v1 表示初始版本
- 对 v1 版本的修复和新增会发布到 v1.1 版本
- 当发布的 v1.x 运行一定时间稳定或进行重构时，发布进阶 v2.x 版本
- v2 版本后会严格按照三级语义来发布版本，如 v2.0.0、v2.1.0
版本选择
- 建议采用最新 releases 版本。可在 releases 看到
- 同时也可参照下面的更新日志来选择版本
- 最新的 v1.x release 代码会合并到 1.x 分支中
- v2 版本后支持使用 v2 tag，将同步最新 2.x 代码
- 支持直接使用分支版本。如：
- name: Issues Helperuses: actions-cool/issues-helper@main-# or-- name: Issues Helperuses: actions-cool/issues-helper@1.x-# or-- name: Issues Helperuses: actions-cool/issues-helper@v3
从 v1.x 升级到 v2，有什么注意的地方吗？
v1.12 和 v2.0.0 版本的差别只有一处。即 mark-duplicate 中的 require-permission 增加了默认值 write。
v3 变更
🚀 v3 版本重构完成，主要变更内容：
- JS to TS
- 将 issue 核心功能封装成为类供 helper 使用
- 提示信息统一
- 增加自动发布脚本
功能变更参考：
- 🚀 New Feature
mark-assignees: 评论快捷设置 assigneesfind-issues: 条件查询当前仓库 issues
- 🐞 Bug Fix
- 修复
find-comments返回结果 direction 未起作用 - 修复
lock-issueslock 与 comment 的顺序问题
- 修复
- 🛠 Refactor
- contents 更名为容易理解的 emoji
issue-emojis更名为issue-emoji- deleteComment updateComment 不再支持
out-comments，保持纯粹功能 - 移除 title body 默认值
month-statistics移除
如果这里没有我想要的功能，该怎么办？
你可以在 issues 中提出。
介 绍
Issues 助手是一个轻松帮你自动管理 issues 的 GitHub Action。
GitHub Actions 是什么？
GitHub Actions 是由 GitHub 官方提供在存储库中自动化、自定义和执行软件开发工作流程。您可以发现，创建和共享操作以执行所需的任何工作（包括CI / CD），并在完全定制的工作流程中组合操作。更多介绍。
issues-helper 就是以此为基础，利用 GitHub Actions 来帮你处理各种关于 issue 方面的操作。
✨ 特性
- 😎 完全免费
- 🚀 全自动操作
- 🏖 托管于 GitHub 服务器，只要 GitHub 不宕机，它就不受影响
⚡ 反馈
非常欢迎你来尝试使用，并提出意见，你可以通过以下方式：
- 通过 Issue 报告 bug 或进行咨询
- 通过 Discussions 进行讨论
- 提交 Pull Request 改进
issues-helper的代码
这里记录自己在使用中总结的一些东西，希望可以帮助到你。
yml 中包含判断
if: contains(github.event.issue.body, 'ie') == false
- 当 issue body 不包含
ie触发 - 测试 yml 中不支持 js
includes()语法 - 大小写不校验，
IE还有同时类似kiekk也可满足
更多查看。
yml 中传值和输出
with:actions: 'month-statistics'token: ${{ secrets.GITHUB_TOKEN }}count-lables: 'true'
count-lables：不管设置true还是'ture'，在程序里接收到的都是字符串格式
同时输出的也是字符串格式。参看。
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
assignees 范围
- 仓库的所有者或协作者，若有组织，包括成员
- issue 的参与者，包括创建者、评论者
- 最多支持 10 个
运行基准
比如：我用 Tag 触发一个 Action，触发基准的代码就会走这个 Tag 对应代码的 Action 定义，而非主分支代码。
📍 token 说明
需拥有 push 权限的人员 token。
- 个人 token 申请
- 需勾选
Full control of private repositories
- 需勾选
- 项目添加 secrets
- 选择 settings，选择 secrets，选择
New repository secret Name与 actions 中保持一致Value填写刚才个人申请的 token
- 选择 settings，选择 secrets，选择
当 actions 不填写 token 时，或输入 ${{ secrets.GITHUB_TOKEN }}，会默认为 github-actions-bot。更多查看。
📍 GitHub 相关文档
📍 outputs 使用
- name: Create issueuses: actions-cool/issues-helper@v1id: createissuewith:actions: 'create-issue'token: ${{ secrets.GITHUB_TOKEN }}- name: Check outputsrun: echo "Outputs issue_number is ${{ steps.createissue.outputs.issue-number }}"
更多查看：
- https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/metadata-syntax-for-github-actions#outputs
- https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs
📍 includes 校验规则
"title-includes": 'x1,x2'-x1x2-"x1y3y2" true"y2 x1" true"x2" true"x3" false
"title-includes": 'x1,x2/y1,y2'-x1 + y1x2 + y1x1 + y2x2 + y2-"x1y3y2" true"y2 x1" true"1x2y" false"x1" false
📍 emoji 类型
| content | emoji |
|---|---|
+1 | 👍 |
-1 | 👎 |
laugh | 😄 |
confused | 😕 |
heart | ❤️ |
hooray | 🎉 |
rocket | 🚀 |
eyes | 👀 |
如需详细了解，可 查看。
📍 comment-id
点击某个评论右上角 ··· 图标，选择 Copy link，url 末尾数字即是 comment_id。
快速开始
1. 新建 Action
点击仓库的 Actions，若已增加过 Actions，会显示如下界面。
点击 New workflow 新增。
你可以点击 set up a workflow yourself 新增一个自定义 action，也可以根据模板来套用新增一个 action。模板使用。
2. 编写 Action
Actions 存放地址是固定的，统一为 /.github/workflows/xx.yml。
下面拿首页的例子详细说明下。对应场景为：当一个 issue 新增 help wanted 标签时，系统会自动进行评论。
name: Issue Reply-on:issues:types: [labeled]-jobs:reply-helper:runs-on: ubuntu-lateststeps:- name: help wantedif: github.event.label.name == 'help wanted'uses: actions-cool/issues-helper@v3with: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语法参考name：workflow 名称- Actions 流程名称，可根据实际情况自定义
on：action 触发条件- 参考 工作流触发机制
uses：使用 actions 名称uses: actions-cool/issues-helper@v2.0.0。版本选择请 参考
issues-hepler参数
3. 启用 Action
当你完成编写完成提交到主分支后，即可自动启用该 workflow，触发条件遵循 on 的定义。
😏 相信到这里你已经对 如何使用 有了大概的了解，是不是想快点尝试一下。
- 完全免费
使用 GitHub 自带提供的 Actions 服务
- 简单易用
教程详细，模版丰富
- 轻松托管
只要 GitHub 不宕机，它就不受影响
🍭 快速上手
这里列举一个非常简单以及常用的例子。对应场景为：当一个 issue 新增 help wanted 标签时，系统会自动进行评论。
name: Issue Reply-on:issues:types: [labeled]-jobs:reply-helper:runs-on: ubuntu-lateststeps:- name: help wantedif: github.event.label.name == 'help wanted'uses: actions-cool/issues-helper@v3with: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。
💖 谁在使用？
⚡ 反馈
非常欢迎你来尝试使用，并提出意见，你可以通过以下方式：
- 通过 Issue 报告 bug 或进行咨询
- 通过 Discussions 进行讨论
- 提交 Pull Request 改进
issues-helper的代码
也欢迎加入 钉钉交流群
