actions-cool/issues-helper
1
0
Fork 0
mirror of https://gitea.com/Lydanne/issues-helper.git synced 2025-08-19 18:25:58 +08:00
Code Issues Packages Projects Releases Wiki Activity

refactor: rename allow-permissions (#48)

Browse Source 
* refactor: rename allow-permissions

* up
This commit is contained in:
xrkffgg
2021-01-26 21:50:10 +08:00
committed by GitHub
parent f777971d6d
commit 1425c335af
8 changed files with 69 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/base.en-US.md
View File

@@ -264,15 +264,16 @@ jobs:
| 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 | ✖ |
| allow-permissions | Permission to operate | string | ✖ |
| require-permission | Permission required | 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
- `allow-permissions`: When you do not input, there is no limit. Anyone comment will trigger. 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
- `require-permission`: When you do not input, there is no limit. Anyone comment will trigger. 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.

11
docs/base.md
View File

@@ -264,15 +264,16 @@ jobs:
| labels | 替换该 issue 的 labels | string | ✖ |
| contents | 为该评论的增加 [reaction](/guide/ref#-reactions-类型) | string | ✖ |
| close-issue | 是否同时关闭该 issue | string | ✖ |
| allow-permissions | 允许操作的权限 | string | ✖ |
| require-permission | 要求权限 | string | ✖ |
- `duplicate-command`：当设置简洁命令时，同时仍支持原有 `Duplicate of`。屏蔽内容包含 `?`
- `labels`：优先级最高
- `close-issue`：`true` 或 `'true'` 均可生效
- `allow-permissions`：当不输时，即无限制。任何人评论都会触发。可选值有 `admin`，`write`，`read`，`none`
- 团队成员若设置 read 权限，则为 read
- 外部 Collaborator 若设置 read 权限，则为 read
- 普通用户为 read 权限
- `require-permission`：当不输时，即无限制，任何人评论都会触发。可选值有 `admin`，`write`，`read`，`none`
- 团队成员若设置 `read` 权限，则为 `read`
- 外部 Collaborator 若设置 `read` 权限，则为 `read`
- 普通用户为 `read` 权限
- 当设置 `write` 后，`admin` 和 `write` 满足条件
<Alert>
注意：使用简洁命令创建的 Duplicate 不显示下图红框内容。但其实这个没有任何影响的。