About billing for GitHub Actions
GitHub Actions 帮助您在您存储代码的同一位置自动执行软件开发工作流程，并协作处理拉取请求和议题。 您可以写入个别任务，称为操作，并结合它们创建一个自定义的工作流程。 For more information, see Understanding GitHub Actions and About GitHub Actions for enterprises.
公共存储库中标准 GitHub 托管的运行器和自托管运行器可免费使用 GitHub Actions。 请参阅“Choosing the runner for a job”。 对于专用仓库，每个 GitHub 帐户可获得一定配额的免费时间和存储以用于 GitHub 托管的运行器，具体取决于帐户的计划。 超出包含金额的任何使用量将计入你的帐户。 For more information, see 关于 GitHub Actions 的计费.
Availability
GitHub Actions is available on all GitHub products, but GitHub Actions is not available for private repositories owned by accounts using legacy per-repository plans. 有关详细信息，请参阅 GitHub 的计划。
Usage limits
There are some limits on GitHub Actions usage when using GitHub-hosted runners. These limits are subject to change.
注意
For self-hosted runners, different usage limits apply. For more information, see 自托管运行器的使用限制.
For more information about service rate limits, see Actions 限制.
Standard GitHub-hosted runners
| GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
|---|---|---|
| Free | 20 | 5 |
| Pro | 40 | 5 |
| Team | 60 | 5 |
| Enterprise | 500 | 50 |
GitHub-hosted 大型运行器s
| GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs | Maximum concurrent GPU jobs |
|---|---|---|---|
| Team | 1000 | 5 | 100 |
| Enterprise | 1000 | 50 | 100 |
注意
- If required, customers on enterprise plans can request a higher limit for concurrent jobs. For more information, contact us through the GitHub 支持门户, or contact your sales representative.
- The maximum concurrent macOS jobs is shared across standard GitHub-hosted runner and GitHub-hosted 大型运行器s.
- Job matrix - 作业矩阵在每次工作流程运行时最多可生成 256 个作业。 此限制适用于 GitHub 托管和自托管运行器。
- 工作流运行队列 - 每个存储库在 10 秒的间隔内可排队的工作流运行不超过 500 个。 如果工作流程运行达到此限制，该工作流程运行将会终止而无法完成。
Usage policy
In addition to the usage limits, you must ensure that you use GitHub Actions within the GitHub Terms of Service. For more information on GitHub Actions-specific terms, see the GitHub Additional Product Terms.
GitHub Actions usage metrics
Organization owners and users with the "View organization Actions metrics" permission can view GitHub Actions usage metrics for their organization. These metrics can help you understand how and where your Actions minutes are being used. For more information, see 查看组织的 GitHub Actions 指标.
When you view usage metrics, it is important to remember that GitHub Actions 使用指标不对显示的指标应用分钟乘数。 虽然_可_帮助你了解自己的账单，但其主要用途是帮助你了解组织中“操作”分钟的方式和位置。
有关分钟乘数的详细信息，请参阅“关于 GitHub Actions 的计费”。
Billing for reusable workflows
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of GitHub-hosted runners is always evaluated using only the caller's context. The caller cannot use GitHub-hosted runners from the called repository.
For more information see, Reusing workflows.
Artifact and log retention policy
You can configure the artifact and log retention period for your repository, organization, or enterprise account.
默认情况下，工作流程生成的构件和日志文件将保留 90 天，然后自动删除。 可以根据存储库类型调整保持期：
- 对于公共仓库：您可以将此保留期更改为 1 至 90 天。
- 对于专用和内部存储库：可以将此保持期更改为 1 天或 400 天之间的任何时长。
自定义保留期时，它仅适用于新构件和日志文件，并且不追溯性地应用于现有对象。 对于托管的仓库和组织，最长保留期不能超过管理组织或企业设置的限制。
For more information, see:
Workflow run history retention policy
The workflow runs in a repository's workflow run history are retained for 400 days. After 400 days, workflow runs are archived. 10 days after archival, they are permanently deleted. The retention period for workflow runs cannot be modified. For more information, see Viewing workflow run history.
Disabling or limiting GitHub Actions for your repository or organization
默认情况下，GitHub Actions 会在所有存储库和组织上启用。 可以选择禁用 GitHub Actions 或将其限制为企业中的操作 和可重用工作流。
For more information, see:
Disabling and enabling workflows
You can enable and disable individual workflows in your repository on GitHub.
为防止不必要的工作流程运行，可能会自动禁用计划的工作流程。 在复刻公共仓库时，默认情况下将禁用计划的工作流程。 在公共仓库中，当 60 天内未发生仓库活动时，将自动禁用计划的工作流程。
For more information, see Disabling and enabling a workflow.