Skip to content

Commit 12aca3e

Browse files
GiteaBotZettat123
andauthored
Add documentation about supported workflow trigger events (#25582) (#25589)
Backport #25582 by @Zettat123 Right now Gitea doesn't support all [Events that trigger workflows](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows). This PR lists the supported events to help users write workflow files. Co-authored-by: Zettat123 <[email protected]>
1 parent 2390a46 commit 12aca3e

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed

docs/content/doc/usage/actions/faq.en-us.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,3 +164,23 @@ Although we would like to provide more options, our limited manpower means that
164164
However, both Gitea and act runner are completely open source, so anyone can create a new/better implementation.
165165
We support your choice, no matter how you decide.
166166
In case you fork act runner to create your own version: Please contribute the changes back if you can and if you think your changes will help others as well.
167+
168+
## What workflow trigger events does Gitea support?
169+
170+
All events listed in this table are supported events and are compatible with GitHub.
171+
For events supported only by GitHub, see GitHub's [documentation](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows).
172+
173+
| trigger event | activity types |
174+
|-----------------------------|--------------------------------------------------------------------------------------------------------------------------|
175+
| create | not applicable |
176+
| delete | not applicable |
177+
| fork | not applicable |
178+
| gollum | not applicable |
179+
| push | not applicable |
180+
| issues | `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `milestoned`, `demilestoned`, `labeled`, `unlabeled` |
181+
| issue_comment | `created`, `edited`, `deleted` |
182+
| pull_request | `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `synchronize`, `labeled`, `unlabeled` |
183+
| pull_request_review | `submitted`, `edited` |
184+
| pull_request_review_comment | `created`, `edited` |
185+
| release | `published`, `edited` |
186+
| registry_package | `published` |

docs/content/doc/usage/actions/faq.zh-cn.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,3 +164,23 @@ defaults:
164164
然而,无论您如何决定,Gitea 和act runner都是完全开源的,所以任何人都可以创建一个新的/更好的实现。
165165
我们支持您的选择,无论您如何决定。
166166
如果您选择分支act runner来创建自己的版本,请在您认为您的更改对其他人也有帮助的情况下贡献这些更改。
167+
168+
## Gitea 支持哪些工作流触发事件?
169+
170+
表格中列出的所有事件都是支持的,并且与 GitHub 兼容。
171+
对于仅 GitHub 支持的事件,请参阅 GitHub 的[文档](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows)。
172+
173+
| 触发事件 | 活动类型 |
174+
|-----------------------------|--------------------------------------------------------------------------------------------------------------------------|
175+
| create | 不适用 |
176+
| delete | 不适用 |
177+
| fork | 不适用 |
178+
| gollum | 不适用 |
179+
| push | 不适用 |
180+
| issues | `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `milestoned`, `demilestoned`, `labeled`, `unlabeled` |
181+
| issue_comment | `created`, `edited`, `deleted` |
182+
| pull_request | `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `synchronize`, `labeled`, `unlabeled` |
183+
| pull_request_review | `submitted`, `edited` |
184+
| pull_request_review_comment | `created`, `edited` |
185+
| release | `published`, `edited` |
186+
| registry_package | `published` |

0 commit comments

Comments
 (0)