mirror of
https://gitea.com/gitea/docs.git
synced 2026-03-27 14:11:03 +07:00
Update faq for actions to correct wrong documentations. (#85)
- [x] User-level runners are supported from 1.20 - [x] Actions are enabled by default from 1.21 Reviewed-on: https://gitea.com/gitea/docs/pulls/85
This commit is contained in:
Lunny Xiao
@@ -8,17 +8,13 @@ sidebar_position: 200
|
||||
|
||||
This page contains some common questions and answers about Gitea Actions.
|
||||
|
||||
## Why is Actions not enabled by default?
|
||||
|
||||
We know it's annoying to enable Actions for the whole instance and each repository one by one, but not everyone likes or needs this feature.
|
||||
We believe that more work needs to be done to improve Gitea Actions before it deserves any further special treatment.
|
||||
|
||||
## Is it possible to enable Actions for new repositories by default for my own instance?
|
||||
## Is it possible to disable Actions for new repositories by default for my own instance?
|
||||
|
||||
Yes, when you enable Actions for the instance, you can choose to enable the `actions` unit for all new repositories by default.
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; remove repo.actions will not enable actions for newly created repositories.
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
@@ -29,11 +25,6 @@ As mentioned, Gitea Actions is designed to be compatible with GitHub Actions.
|
||||
However, we recommend using `gitea.xyz` in case Gitea adds something that GitHub does not have to avoid different kinds of secrets in your workflow file (and because you are using this workflow on Gitea, not GitHub).
|
||||
Still, this is completely optional since both options have the same effect at the moment.
|
||||
|
||||
## Is it possible to register runners for a specific user (not organization)?
|
||||
|
||||
Not yet.
|
||||
It is technically possible to implement, but we need to discuss whether it is necessary.
|
||||
|
||||
## Where will the runner download scripts when using actions such as `actions/checkout@v4`?
|
||||
|
||||
There are tens of thousands of [actions scripts](https://github.com/marketplace?type=actions) in GitHub, and when you write `uses: actions/checkout@v4`, it downloads the scripts from [github.com/actions/checkout](http://github.com/actions/checkout) by default.
|
||||
|
||||
@@ -8,17 +8,13 @@ sidebar_position: 100
|
||||
|
||||
本页面包含一些关于Gitea Actions的常见问题和答案。
|
||||
|
||||
## 为什么默认情况下不启用Actions？
|
||||
|
||||
我们知道为整个实例和每个仓库启用Actions可能很麻烦，但并不是每个人都喜欢或需要此功能。
|
||||
在我们认为Gitea Actions值得被特别对待之前，我们认为还需要做更多的工作来改进它。
|
||||
|
||||
## 是否可以在我的实例中默认启用新仓库的Actions？
|
||||
## 是否可以在我的实例中默认禁用新仓库的Actions？
|
||||
|
||||
是的，当您为实例启用Actions时，您可以选择默认启用actions单元以适用于所有新仓库。
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; 去掉 repo.actions 将不会为新仓库自动启用actions
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
@@ -29,11 +25,6 @@ DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
然而，我们建议在工作流文件中使用`gitea.xyz`，以防止在工作流文件中出现不同类型的密钥（因为您在Gitea上使用此工作流，而不是GitHub）。
|
||||
不过，这完全是可选的，因为目前这两个选项的效果是相同的。
|
||||
|
||||
## 是否可以为特定用户（而不是组织）注册Runner？
|
||||
|
||||
目前还不可以。
|
||||
从技术上讲是可以实现的，但我们需要讨论是否有必要。
|
||||
|
||||
## 使用`actions/checkout@v4`等Actions时，Job容器会从何处下载脚本？
|
||||
|
||||
GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?type=actions)。
|
||||
|
||||
@@ -29,11 +29,6 @@ DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
然而，我们建议在工作流文件中使用`gitea.xyz`，以防止在工作流文件中出现不同类型的密钥（因为您在Gitea上使用此工作流，而不是GitHub）。
|
||||
不过，这完全是可选的，因为目前这两个选项的效果是相同的。
|
||||
|
||||
## 是否可以为特定用户（而不是组织）注册Runner？
|
||||
|
||||
目前还不可以。
|
||||
从技术上讲是可以实现的，但我们需要讨论是否有必要。
|
||||
|
||||
## 使用`actions/checkout@v3`等Actions时，Job容器会从何处下载脚本？
|
||||
|
||||
您可能知道GitHub上有成千上万个[Actions市场](https://github.com/marketplace?type=actions)。
|
||||
|
||||
@@ -1,26 +1,20 @@
|
||||
---
|
||||
date: "2023-05-24T15:00:00+08:00"
|
||||
|
||||
slug: "faq"
|
||||
sidebar_position: 100
|
||||
|
||||
---
|
||||
|
||||
# Gitea Actions常见问题解答
|
||||
|
||||
本页面包含一些关于Gitea Actions的常见问题和答案。
|
||||
|
||||
## 为什么默认情况下不启用Actions？
|
||||
|
||||
我们知道为整个实例和每个仓库启用Actions可能很麻烦，但并不是每个人都喜欢或需要此功能。
|
||||
在我们认为Gitea Actions值得被特别对待之前，我们认为还需要做更多的工作来改进它。
|
||||
|
||||
## 是否可以在我的实例中默认启用新仓库的Actions？
|
||||
## 是否可以在我的实例中默认禁用新仓库的Actions？
|
||||
|
||||
是的，当您为实例启用Actions时，您可以选择默认启用actions单元以适用于所有新仓库。
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; 去掉 repo.actions 将不会为新仓库自动启用actions
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
@@ -31,11 +25,6 @@ DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
然而，我们建议在工作流文件中使用`gitea.xyz`，以防止在工作流文件中出现不同类型的密钥（因为您在Gitea上使用此工作流，而不是GitHub）。
|
||||
不过，这完全是可选的，因为目前这两个选项的效果是相同的。
|
||||
|
||||
## 是否可以为特定用户（而不是组织）注册Runner？
|
||||
|
||||
目前还不可以。
|
||||
从技术上讲是可以实现的，但我们需要讨论是否有必要。
|
||||
|
||||
## 使用`actions/checkout@v4`等Actions时，Job容器会从何处下载脚本？
|
||||
|
||||
GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?type=actions)。
|
||||
|
||||
@@ -1,26 +1,20 @@
|
||||
---
|
||||
date: "2023-05-24T15:00:00+08:00"
|
||||
|
||||
slug: "faq"
|
||||
sidebar_position: 100
|
||||
|
||||
---
|
||||
|
||||
# Gitea Actions常见问题解答
|
||||
|
||||
本页面包含一些关于Gitea Actions的常见问题和答案。
|
||||
|
||||
## 为什么默认情况下不启用Actions？
|
||||
|
||||
我们知道为整个实例和每个仓库启用Actions可能很麻烦，但并不是每个人都喜欢或需要此功能。
|
||||
在我们认为Gitea Actions值得被特别对待之前，我们认为还需要做更多的工作来改进它。
|
||||
|
||||
## 是否可以在我的实例中默认启用新仓库的Actions？
|
||||
## 是否可以在我的实例中默认禁用新仓库的Actions？
|
||||
|
||||
是的，当您为实例启用Actions时，您可以选择默认启用actions单元以适用于所有新仓库。
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; 去掉 repo.actions 将不会为新仓库自动启用actions
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
@@ -31,11 +25,6 @@ DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
然而，我们建议在工作流文件中使用`gitea.xyz`，以防止在工作流文件中出现不同类型的密钥（因为您在Gitea上使用此工作流，而不是GitHub）。
|
||||
不过，这完全是可选的，因为目前这两个选项的效果是相同的。
|
||||
|
||||
## 是否可以为特定用户（而不是组织）注册Runner？
|
||||
|
||||
目前还不可以。
|
||||
从技术上讲是可以实现的，但我们需要讨论是否有必要。
|
||||
|
||||
## 使用`actions/checkout@v4`等Actions时，Job容器会从何处下载脚本？
|
||||
|
||||
GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?type=actions)。
|
||||
|
||||
@@ -29,11 +29,6 @@ As mentioned, Gitea Actions is designed to be compatible with GitHub Actions.
|
||||
However, we recommend using `gitea.xyz` in case Gitea adds something that GitHub does not have to avoid different kinds of secrets in your workflow file (and because you are using this workflow on Gitea, not GitHub).
|
||||
Still, this is completely optional since both options have the same effect at the moment.
|
||||
|
||||
## Is it possible to register runners for a specific user (not organization)?
|
||||
|
||||
Not yet.
|
||||
It is technically possible to implement, but we need to discuss whether it is necessary.
|
||||
|
||||
## Where will the runner download scripts when using actions such as `actions/checkout@v3`?
|
||||
|
||||
You may be aware that there are tens of thousands of [marketplace actions](https://github.com/marketplace?type=actions) in GitHub.
|
||||
|
||||
@@ -8,17 +8,13 @@ sidebar_position: 200
|
||||
|
||||
This page contains some common questions and answers about Gitea Actions.
|
||||
|
||||
## Why is Actions not enabled by default?
|
||||
|
||||
We know it's annoying to enable Actions for the whole instance and each repository one by one, but not everyone likes or needs this feature.
|
||||
We believe that more work needs to be done to improve Gitea Actions before it deserves any further special treatment.
|
||||
|
||||
## Is it possible to enable Actions for new repositories by default for my own instance?
|
||||
## Is it possible to disable Actions for new repositories by default for my own instance?
|
||||
|
||||
Yes, when you enable Actions for the instance, you can choose to enable the `actions` unit for all new repositories by default.
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; remove repo.actions will not enable actions for newly created repositories.
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
|
||||
@@ -8,17 +8,13 @@ sidebar_position: 200
|
||||
|
||||
This page contains some common questions and answers about Gitea Actions.
|
||||
|
||||
## Why is Actions not enabled by default?
|
||||
|
||||
We know it's annoying to enable Actions for the whole instance and each repository one by one, but not everyone likes or needs this feature.
|
||||
We believe that more work needs to be done to improve Gitea Actions before it deserves any further special treatment.
|
||||
|
||||
## Is it possible to enable Actions for new repositories by default for my own instance?
|
||||
## Is it possible to disable Actions for new repositories by default for my own instance?
|
||||
|
||||
Yes, when you enable Actions for the instance, you can choose to enable the `actions` unit for all new repositories by default.
|
||||
|
||||
```ini
|
||||
[repository]
|
||||
; remove repo.actions will not enable actions for newly created repositories.
|
||||
DEFAULT_REPO_UNITS = ...,repo.actions
|
||||
```
|
||||
|
||||
@@ -29,11 +25,6 @@ As mentioned, Gitea Actions is designed to be compatible with GitHub Actions.
|
||||
However, we recommend using `gitea.xyz` in case Gitea adds something that GitHub does not have to avoid different kinds of secrets in your workflow file (and because you are using this workflow on Gitea, not GitHub).
|
||||
Still, this is completely optional since both options have the same effect at the moment.
|
||||
|
||||
## Is it possible to register runners for a specific user (not organization)?
|
||||
|
||||
Not yet.
|
||||
It is technically possible to implement, but we need to discuss whether it is necessary.
|
||||
|
||||
## Where will the runner download scripts when using actions such as `actions/checkout@v4`?
|
||||
|
||||
There are tens of thousands of [actions scripts](https://github.com/marketplace?type=actions) in GitHub, and when you write `uses: actions/checkout@v4`, it downloads the scripts from [github.com/actions/checkout](http://github.com/actions/checkout) by default.
|
||||
|
||||
Reference in New Issue
Block a user