@@ -38,6 +38,8 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
|
||||
|
||||
{% data reusables.actions.actions-do-not-trigger-workflows %}
|
||||
|
||||
{% data reusables.actions.actions-do-not-trigger-pages-rebuilds %}
|
||||
|
||||
### Example 1: passing the `GITHUB_TOKEN` as an input
|
||||
|
||||
{% data reusables.actions.github_token-input-example %}
|
||||
|
||||
@@ -1152,6 +1152,15 @@ jobs:
|
||||
run: echo $MESSAGE
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
|
||||
- The maximum number of top-level properties in `client_payload` is 10.
|
||||
- The payload can contain a maximum of 65,535 characters.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## `schedule`
|
||||
|
||||
| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
Commits pushed by a {% data variables.product.prodname_actions %} workflow that uses the `GITHUB_TOKEN` do not trigger a {% data variables.product.prodname_pages %} build.
|
||||
@@ -2,7 +2,11 @@
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The workflow will also receive the inputs in the `github.event.inputs` context. The information in the `inputs` context and `github.event.inputs` context is identical except that the `inputs` context preserves Boolean values as Booleans instead of converting them to strings. The `choice` type resolves to a string and is a single selectable option.
|
||||
**Notes**:
|
||||
|
||||
- The workflow will also receive the inputs in the `github.event.inputs` context. The information in the `inputs` context and `github.event.inputs` context is identical except that the `inputs` context preserves Boolean values as Booleans instead of converting them to strings. The `choice` type resolves to a string and is a single selectable option.
|
||||
- The maximum number of top-level properties for `inputs` is 10.
|
||||
- The maximum payload for `inputs` is 65,535 characters.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
@@ -32,6 +32,8 @@ The available space on the root filesystem will be 50% of the total disk size. Y
|
||||
|
||||
The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations.
|
||||
|
||||
Any VMs you provision for {% data variables.location.product_location %} must use the x86-64 CPU architecture. Other architectures are not supported, such as Aarch64 or arm64.
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources for your instance. For more information, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
| User licenses | vCPUs | Memory | Root storage | Attached (data) storage |
|
||||
| User licenses | x86-64 vCPUs | Memory | Root storage | Attached (data) storage |
|
||||
| :- | -: | -: | -: | -: |
|
||||
| Trial, demo, or 10 light users | 4 | 32 GB | 200 GB | 150 GB |
|
||||
| 10 to 3,000 | 8 | 48 GB | 200 GB | 300 GB |
|
||||
|
||||
@@ -1,5 +1,9 @@
|
||||
{% note %}
|
||||
|
||||
**Note**: {% ifversion pages-custom-workflow %}If you are publishing from a branch and{% else %}If{% endif %} your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source.
|
||||
**Notes**:
|
||||
|
||||
- {% ifversion pages-custom-workflow %}If you are publishing from a branch and{% else %}If{% endif %} your site has not published automatically, make sure someone with admin permissions and a verified email address has pushed to the publishing source.
|
||||
|
||||
- {% data reusables.actions.actions-do-not-trigger-pages-rebuilds %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Reference in New Issue
Block a user