* Update reusable workflows docs * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/actions/learn-github-actions/reusing-workflows.md * Update content/actions/learn-github-actions/reusing-workflows.md * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Martin Lopes <martin389@github.com> * Apply review suggestion from Lucas * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Martin Lopes <martin389@github.com> * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Martin Lopes <martin389@github.com> * Update content/actions/learn-github-actions/reusing-workflows.md Co-authored-by: Martin Lopes <martin389@github.com> * Add information about use of runners As per review comment from Ajay Krishna Nalisetty * Update content/actions/learn-github-actions/workflow-syntax-for-github-actions.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/actions/learn-github-actions/workflow-syntax-for-github-actions.md * Fix version as per Lucas's review comment * Explain using environment secrets * Add workflow diagram * Move explanation of diagram above it * Slight change to job_workflow-ref description Include the syntax of the response data, as per https://github.slack.com/archives/C01SMLA6MNY/p1637731982336700 * Clarify difference between repo and job_workflow_ref Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Martin Lopes <martin389@github.com> Co-authored-by: Octomerger Bot <63058869+Octomerger@users.noreply.github.com>
6.4 KiB
title, intro, redirect_from, versions, topics, shortTitle
| title | intro | redirect_from | versions | topics | shortTitle | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Usage limits, billing, and administration | There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository. |
|
|
|
Workflow billing & limits |
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.ae-beta %}
About billing for {% data variables.product.prodname_actions %}
{% ifversion fpt or ghec %} {% data reusables.github-actions.actions-billing %} For more information, see "About billing for {% data variables.product.prodname_actions %}." {% else %} GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners. {% endif %}
Availability
{% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
Usage limits
{% ifversion fpt or ghec %} There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
{% note %}
Note: For self-hosted runners, different usage limits apply. For more information, see "About self-hosted runners."
{% endnote %}
- Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete. {% data reusables.github-actions.usage-workflow-run-time %} {% data reusables.github-actions.usage-api-requests %}
- Concurrent jobs - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
GitHub plan Total concurrent jobs Maximum concurrent macOS jobs Free 20 5 Pro 40 5 Team 60 5 Enterprise 180 50 - Job matrix - {% data reusables.github-actions.usage-matrix-limits %} {% data reusables.github-actions.usage-workflow-queue-limits %}
{% else %} Usage limits apply to self-hosted runners. For more information, see "About self-hosted runners." {% endif %}
{% ifversion fpt or ghec %}
Usage policy
In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the GitHub Terms of Service. For more information on {% data variables.product.prodname_actions %}-specific terms, see the GitHub Additional Product Terms. {% endif %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
Billing for reusable workflows
If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dotcom %}-hosted runners{% endif %}{% ifversion ghae %}{% data variables.actions.hosted_runner %}s{% endif %} is always evaluated using only the caller's context. The caller cannot use {% ifversion fpt or ghes or ghec %}{% data variables.product.prodname_dotcom %}-hosted runners{% endif %}{% ifversion ghae %}{% data variables.actions.hosted_runner %}s{% endif %} from the called repository.
For more information see, "Reusing workflows." {% endif %}
Artifact and log retention policy
You can configure the artifact and log retention period for your repository, organization, or enterprise account.
{% data reusables.actions.about-artifact-log-retention %}
For more information, see:
- "Managing {% data variables.product.prodname_actions %} settings for a repository"
- "Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization"
- "Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise"
Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
{% data reusables.github-actions.disabling-github-actions %}
For more information, see:
- "Managing {% data variables.product.prodname_actions %} settings for a repository"
- "Disabling or limiting {% data variables.product.prodname_actions %} for your organization"
- "Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise"
Disabling and enabling workflows
You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
{% data reusables.actions.scheduled-workflows-disabled %}
For more information, see "Disabling and enabling a workflow."