Github 操作在分叉的存储库上可用吗？
Is Github Actions available on forked repositories?
我分叉了 watchman 存储库，我想在其 main.workflow 中添加一些步骤（目标是发布工件以创建快照包）。
但我无法在存储库中看到 Actions 选项卡。
是否有任何额外的步骤来配置 Github 分支存储库上可用的操作？
只要您或您的组织已登录 beta，就无需采取进一步行动。您应该在下一次推送到分叉时看到 Actions 运行，或者设置了工作流。还经常建议在您的分支中提交对工作流文件的更改（编辑来自上游的文件或添加您自己的文件）。
如果时间过长，您可以随时在Actions forum上报告；我在上周看到了一些关于完全相同问题的帖子，GitHub 工作人员手动修复了它。
I'm not able to see the Actions tab in the repository.
2020 年 8 月更新，10 个月后，请参阅：
GitHub Actions improvements for fork and pull request workflows
written by Chris Patterson
New settings for private repository forks
[...] To enable these users to run workflows on fork pull requests, we’ve introduced three new settings at the enterprise, organization, and repository level for private repositories only.
Improvements for public repository forks
[...] we’ve added a new pull_request_target event, which behaves in an almost identical way to the pull_request event with the same set of filters and payload.
However, instead of running against the workflow and code from the merge commit, the event runs against the workflow and code from the base of the pull request.
This means the workflow is running from a trusted source and is given access to a read/write token as well as secrets enabling the maintainer to safely comment on or label a pull request.
This event can be used in combination with the private repository settings as well.
我分叉了 watchman 存储库，我想在其 main.workflow 中添加一些步骤（目标是发布工件以创建快照包）。
但我无法在存储库中看到 Actions 选项卡。
是否有任何额外的步骤来配置 Github 分支存储库上可用的操作？
只要您或您的组织已登录 beta，就无需采取进一步行动。您应该在下一次推送到分叉时看到 Actions 运行，或者设置了工作流。还经常建议在您的分支中提交对工作流文件的更改（编辑来自上游的文件或添加您自己的文件）。
如果时间过长，您可以随时在Actions forum上报告；我在上周看到了一些关于完全相同问题的帖子，GitHub 工作人员手动修复了它。
I'm not able to see the Actions tab in the repository.
2020 年 8 月更新，10 个月后，请参阅：
GitHub Actions improvements for fork and pull request workflows
written by Chris Patterson
New settings for private repository forks
[...] To enable these users to run workflows on fork pull requests, we’ve introduced three new settings at the enterprise, organization, and repository level for private repositories only.
Improvements for public repository forks
[...] we’ve added a new
pull_request_targetevent, which behaves in an almost identical way to thepull_requestevent with the same set of filters and payload.However, instead of running against the workflow and code from the merge commit, the event runs against the workflow and code from the base of the pull request.
This means the workflow is running from a trusted source and is given access to a read/write token as well as secrets enabling the maintainer to safely comment on or label a pull request.
This event can be used in combination with the private repository settings as well.