docs-bot
@@ -79,7 +79,7 @@ Anytime you comment in a conversation or when someone @mentions your username, y
|
|||||||
|
|
||||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox. For more information, see [Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings).
|
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox. For more information, see [Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings).
|
||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
For example, on your "Notification settings" page:
|
For example, on your "Notification settings" page:
|
||||||
* If you don't want notifications to be sent to your email, deselect **email** for participating and watching notifications.
|
* If you don't want notifications to be sent to your email, deselect **email** for participating and watching notifications.
|
||||||
@@ -236,8 +236,6 @@ For more information about the notification delivery methods available to you, a
|
|||||||
|
|
||||||
For more information on how to configure notifications for {% data variables.secret-scanning.alerts %}, see [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts).
|
For more information on how to configure notifications for {% data variables.secret-scanning.alerts %}, see [AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning/monitoring-alerts).
|
||||||
|
|
||||||
{% ifversion update-notification-settings-22 or ghes %}
|
|
||||||
|
|
||||||
## {% data variables.product.prodname_actions %} notification options
|
## {% data variables.product.prodname_actions %} notification options
|
||||||
|
|
||||||
For repositories that are set up with {% data variables.product.prodname_actions %} and that you are watching, you can choose how you want to receive workflow run updates.
|
For repositories that are set up with {% data variables.product.prodname_actions %} and that you are watching, you can choose how you want to receive workflow run updates.
|
||||||
@@ -245,7 +243,7 @@ For repositories that are set up with {% data variables.product.prodname_actions
|
|||||||
{% ifversion update-notification-settings-22 %}
|
{% ifversion update-notification-settings-22 %}
|
||||||
1. On the "Notification settings" page, under "System", then under "Actions", select the **Don't notify** dropdown menu.
|
1. On the "Notification settings" page, under "System", then under "Actions", select the **Don't notify** dropdown menu.
|
||||||
|
|
||||||
|
|
||||||
1. To opt into web notifications, from the dropdown menu, select "On {% data variables.product.prodname_dotcom %}."
|
1. To opt into web notifications, from the dropdown menu, select "On {% data variables.product.prodname_dotcom %}."
|
||||||
|
|
||||||
To opt into email notifications, from the dropdown menu, select "Email."
|
To opt into email notifications, from the dropdown menu, select "Email."
|
||||||
@@ -254,9 +252,7 @@ For repositories that are set up with {% data variables.product.prodname_actions
|
|||||||
{% ifversion ghes %}
|
{% ifversion ghes %}
|
||||||
On the "Notification settings" page, select "Email" or "Web" notifications. Optionally, to only receive notifications for failed workflow runs, select "Send notifications for failed workflows only".
|
On the "Notification settings" page, select "Email" or "Web" notifications. Optionally, to only receive notifications for failed workflow runs, select "Send notifications for failed workflows only".
|
||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
## Organization alerts notification options
|
## Organization alerts notification options
|
||||||
|
|
||||||
|
|||||||
@@ -92,8 +92,6 @@ Add pronouns to your public user profile to share information about yourself wit
|
|||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
{% ifversion profile-time-zone %}
|
|
||||||
|
|
||||||
## Setting your location and time zone
|
## Setting your location and time zone
|
||||||
|
|
||||||
You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
|
You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
|
||||||
@@ -111,8 +109,6 @@ When you view your profile, you will see your location, local time, and your tim
|
|||||||
* Select the **Time zone** dropdown menu, then click your local time zone.
|
* Select the **Time zone** dropdown menu, then click your local time zone.
|
||||||
{% data reusables.profile.update-profile %}
|
{% data reusables.profile.update-profile %}
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
{% ifversion profile-social-links %}
|
{% ifversion profile-social-links %}
|
||||||
|
|
||||||
## Adding links to your social accounts
|
## Adding links to your social accounts
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ The person you invite to be your successor must have a {% data variables.product
|
|||||||
|
|
||||||
1. Under "Successor settings", to invite a successor, begin typing a username, full name, or email address, then click their name when it appears.
|
1. Under "Successor settings", to invite a successor, begin typing a username, full name, or email address, then click their name when it appears.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Click **Add successor**.
|
1. Click **Add successor**.
|
||||||
{% data reusables.user-settings.sudo-mode-popup %}
|
{% data reusables.user-settings.sudo-mode-popup %}
|
||||||
|
|||||||
@@ -48,8 +48,6 @@ By default, all keyboard shortcuts are enabled on {% data variables.product.prod
|
|||||||
* To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see [AUTOTITLE](/get-started/accessibility/github-command-palette).
|
* To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see [AUTOTITLE](/get-started/accessibility/github-command-palette).
|
||||||
{%- endif %}
|
{%- endif %}
|
||||||
|
|
||||||
{% ifversion motion-management %}
|
|
||||||
|
|
||||||
## Managing motion
|
## Managing motion
|
||||||
|
|
||||||
You can control how {% data variables.product.product_name %} displays animated _.gif_ images.
|
You can control how {% data variables.product.product_name %} displays animated _.gif_ images.
|
||||||
@@ -61,5 +59,3 @@ By default, {% data variables.product.product_name %} syncs with your system-lev
|
|||||||
1. Under "Motion", manage settings for motion.
|
1. Under "Motion", manage settings for motion.
|
||||||
|
|
||||||
* To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
|
* To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|||||||
@@ -35,7 +35,7 @@ For an overview of repository-level security, see [AUTOTITLE](/code-security/get
|
|||||||
1. Under {% ifversion code-security-wording-only %}"Code security"{% else %}"Code security and analysis"{% endif %}, to the right of the feature, click **Disable all** or **Enable all**.
|
1. Under {% ifversion code-security-wording-only %}"Code security"{% else %}"Code security and analysis"{% endif %}, to the right of the feature, click **Disable all** or **Enable all**.
|
||||||
1. Optionally, enable the feature by default for new repositories that you own.{% ifversion not ghes %}
|
1. Optionally, enable the feature by default for new repositories that you own.{% ifversion not ghes %}
|
||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
|
1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
|
||||||
|
|
||||||
|
|||||||
@@ -27,6 +27,6 @@ You can customize how non-essential cookies behave on any {% data variables.prod
|
|||||||
|
|
||||||
1. Under "Manage cookie preferences," to accept or reject each non-essential cookie, click **Accept** or **Reject**.
|
1. Under "Manage cookie preferences," to accept or reject each non-essential cookie, click **Accept** or **Reject**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Click **Save changes**.
|
1. Click **Save changes**.
|
||||||
|
|||||||
@@ -28,7 +28,7 @@ You can set scheduled reminders for personal or team-level review requests for p
|
|||||||
{% data reusables.reminders.scheduled-reminders %}
|
{% data reusables.reminders.scheduled-reminders %}
|
||||||
1. Next to the organization you'd like to schedule reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
1. Next to the organization you'd like to schedule reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
{% data reusables.reminders.authorize-slack %}
|
{% data reusables.reminders.authorize-slack %}
|
||||||
{% data reusables.reminders.days-dropdown %}
|
{% data reusables.reminders.days-dropdown %}
|
||||||
@@ -45,7 +45,7 @@ You can set scheduled reminders for personal or team-level review requests for p
|
|||||||
{% data reusables.reminders.scheduled-reminders %}
|
{% data reusables.reminders.scheduled-reminders %}
|
||||||
1. Next to the organization you'd like to edit scheduled reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
1. Next to the organization you'd like to edit scheduled reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
{% data reusables.reminders.edit-page %}
|
{% data reusables.reminders.edit-page %}
|
||||||
{% data reusables.reminders.update-buttons %}
|
{% data reusables.reminders.update-buttons %}
|
||||||
@@ -57,7 +57,7 @@ You can set scheduled reminders for personal or team-level review requests for p
|
|||||||
{% data reusables.reminders.scheduled-reminders %}
|
{% data reusables.reminders.scheduled-reminders %}
|
||||||
1. Next to the organization you'd like to delete reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
1. Next to the organization you'd like to delete reminders for, click {% octicon "pencil" aria-label="Edit reminder" %}.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
{% data reusables.reminders.delete %}
|
{% data reusables.reminders.delete %}
|
||||||
|
|
||||||
|
|||||||
@@ -27,4 +27,4 @@ shortTitle: Show or hide membership
|
|||||||
* To publicize your membership, choose **Public**.
|
* To publicize your membership, choose **Public**.
|
||||||
* To hide your membership, choose **Private**.
|
* To hide your membership, choose **Private**.
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -18,7 +18,7 @@ shortTitle: Request {% data variables.product.prodname_oauth_app %} approval
|
|||||||
|
|
||||||
## About requesting organization approval for an {% data variables.product.prodname_oauth_app %}
|
## About requesting organization approval for an {% data variables.product.prodname_oauth_app %}
|
||||||
|
|
||||||
Organization members can always request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.{% ifversion limit-app-access-requests %} Outside collaborators can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use if integration access requests are enabled. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/limiting-oauth-app-and-github-app-access-requests).{% endif %}
|
Organization members can always request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests. Outside collaborators can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use if integration access requests are enabled. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/limiting-oauth-app-and-github-app-access-requests).
|
||||||
|
|
||||||
## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
|
## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
|
||||||
|
|
||||||
|
|||||||
@@ -32,7 +32,7 @@ shortTitle: User into an organization
|
|||||||
> * Since organizations cannot star repositories, you will no longer have access to your original list of starred repositories.
|
> * Since organizations cannot star repositories, you will no longer have access to your original list of starred repositories.
|
||||||
> * You will no longer have access to the list of users you were following from your user account.
|
> * You will no longer have access to the list of users you were following from your user account.
|
||||||
> * Any followers of your user account will not automatically follow the new organization.
|
> * Any followers of your user account will not automatically follow the new organization.
|
||||||
{% ifversion projects-v2 %}> * Any existing collaborators on your projects will still have access to those projects in the new organization.{% endif %}
|
> * Any existing collaborators on your projects will still have access to those projects in the new organization.
|
||||||
> * {% data variables.product.prodname_actions %} is not automatically enabled on the account after converting it to an organization, and will have to be re-enabled. To re-enable {% data variables.product.prodname_actions %}, create a new workflow file in the `.github/workflows` directory of your repository.
|
> * {% data variables.product.prodname_actions %} is not automatically enabled on the account after converting it to an organization, and will have to be re-enabled. To re-enable {% data variables.product.prodname_actions %}, create a new workflow file in the `.github/workflows` directory of your repository.
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|||||||
@@ -28,12 +28,8 @@ For information on supported operating systems for self-hosted runners, or using
|
|||||||
|
|
||||||
You can set up automation to scale the number of self-hosted runners. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners).
|
You can set up automation to scale the number of self-hosted runners. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners).
|
||||||
|
|
||||||
{% ifversion actions-single-use-tokens %}
|
|
||||||
|
|
||||||
You can register ephemeral runners that perform a single job before the registration is cleaned up by using just-in-time runner registration. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-just-in-time-runners).
|
You can register ephemeral runners that perform a single job before the registration is cleaned up by using just-in-time runner registration. For more information, see [AUTOTITLE](/actions/security-guides/security-hardening-for-github-actions#using-just-in-time-runners).
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|
||||||
{% data reusables.actions.self-hosted-runners-prerequisites %}
|
{% data reusables.actions.self-hosted-runners-prerequisites %}
|
||||||
|
|||||||
@@ -48,12 +48,8 @@ The {% data variables.product.prodname_actions %} service will then automaticall
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires.
|
> If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires.
|
||||||
|
|
||||||
{% ifversion actions-single-use-tokens %}
|
|
||||||
|
|
||||||
Alternatively, you can create ephemeral, just-in-time runners using the REST API. For more information, see [AUTOTITLE](/rest/actions/self-hosted-runners).
|
Alternatively, you can create ephemeral, just-in-time runners using the REST API. For more information, see [AUTOTITLE](/rest/actions/self-hosted-runners).
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
## Controlling runner software updates on self-hosted runners
|
## Controlling runner software updates on self-hosted runners
|
||||||
|
|
||||||
By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available. If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released. Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
|
By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available. If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released. Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
|
||||||
|
|||||||
@@ -20,9 +20,7 @@ shortTitle: Remove self-hosted runners
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
||||||
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
||||||
{%- ifversion actions-single-use-tokens %}
|
|
||||||
> * {% data reusables.actions.jit-runner-removal %}
|
> * {% data reusables.actions.jit-runner-removal %}
|
||||||
{%- endif %}
|
|
||||||
|
|
||||||
To remove a self-hosted runner from a user repository you must be the repository owner. Organization owners{% ifversion custom-org-roles %} and users with the "Manage organization runners and runner groups" permission{% endif %} can remove a runner from a repository in the organization. {% ifversion custom-org-roles %}For more information about custom organization roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles).{% endif %}
|
To remove a self-hosted runner from a user repository you must be the repository owner. Organization owners{% ifversion custom-org-roles %} and users with the "Manage organization runners and runner groups" permission{% endif %} can remove a runner from a repository in the organization. {% ifversion custom-org-roles %}For more information about custom organization roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles).{% endif %}
|
||||||
|
|
||||||
@@ -42,9 +40,7 @@ For information about how to remove a self-hosted runner with the REST API, see
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
||||||
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
||||||
{%- ifversion actions-single-use-tokens %}
|
|
||||||
> * {% data reusables.actions.jit-runner-removal %}
|
> * {% data reusables.actions.jit-runner-removal %}
|
||||||
{%- endif %}
|
|
||||||
|
|
||||||
To remove a self-hosted runner from an organization, you must be an organization owner{% ifversion custom-org-roles %} or have the "Manage organization runners and runner groups" permission{% endif %}. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see [AUTOTITLE](/rest/actions/self-hosted-runners).
|
To remove a self-hosted runner from an organization, you must be an organization owner{% ifversion custom-org-roles %} or have the "Manage organization runners and runner groups" permission{% endif %}. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see [AUTOTITLE](/rest/actions/self-hosted-runners).
|
||||||
|
|
||||||
@@ -67,11 +63,8 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
> * {% data reusables.actions.self-hosted-runner-removal-impact %}
|
||||||
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
> * {% data reusables.actions.self-hosted-runner-auto-removal %}
|
||||||
{%- ifversion actions-single-use-tokens %}
|
|
||||||
> * {% data reusables.actions.jit-runner-removal %}
|
> * {% data reusables.actions.jit-runner-removal %}
|
||||||
|
|
||||||
{%- endif %}
|
|
||||||
|
|
||||||
To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/actions/self-hosted-runners).
|
To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/actions/self-hosted-runners).
|
||||||
|
|
||||||
{% data reusables.actions.self-hosted-runner-reusing %}
|
{% data reusables.actions.self-hosted-runner-reusing %}
|
||||||
|
|||||||
@@ -92,7 +92,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
|
|||||||
| {% endif %} |
|
| {% endif %} |
|
||||||
| issues | read/write | none | read |
|
| issues | read/write | none | read |
|
||||||
| metadata | read | read | read |
|
| metadata | read | read | read |
|
||||||
| packages | read/write | {% ifversion actions-default-workflow-permissions-restrictive %}read{% else %}none{% endif %} | read |
|
| packages | read/write | read | read |
|
||||||
| pages | read/write | none | read |
|
| pages | read/write | none | read |
|
||||||
| pull-requests | read/write | none | read |
|
| pull-requests | read/write | none | read |
|
||||||
| repository-projects | read/write | none | read |
|
| repository-projects | read/write | none | read |
|
||||||
|
|||||||
@@ -352,8 +352,6 @@ You should also consider the environment of the self-hosted runner machines:
|
|||||||
|
|
||||||
Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
|
Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
|
||||||
|
|
||||||
{% ifversion actions-single-use-tokens %}
|
|
||||||
|
|
||||||
### Using just-in-time runners
|
### Using just-in-time runners
|
||||||
|
|
||||||
To improve runner registration security, you can use the REST API to create ephemeral, just-in-time (JIT) runners. These self-hosted runners perform at most one job before being automatically removed from the repository, organization, or enterprise. For more information about configuring JIT runners, see [AUTOTITLE](/rest/actions/self-hosted-runners#create-configuration-for-a-just-in-time-runner-for-an-organization).
|
To improve runner registration security, you can use the REST API to create ephemeral, just-in-time (JIT) runners. These self-hosted runners perform at most one job before being automatically removed from the repository, organization, or enterprise. For more information about configuring JIT runners, see [AUTOTITLE](/rest/actions/self-hosted-runners#create-configuration-for-a-just-in-time-runner-for-an-organization).
|
||||||
@@ -367,8 +365,6 @@ Once you have the config file from the REST API response, you can pass it to the
|
|||||||
./run.sh --jitconfig ${encoded_jit_config}
|
./run.sh --jitconfig ${encoded_jit_config}
|
||||||
```
|
```
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
### Planning your management strategy for self-hosted runners
|
### Planning your management strategy for self-hosted runners
|
||||||
|
|
||||||
A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
|
A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
|
||||||
|
|||||||
@@ -16,7 +16,7 @@ redirect_from:
|
|||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
You can configure a workflow that must run in repositories in an organization for all pull requests opened against {% ifversion actions-required-workflow-improvements %}any target branch{% else %}the default branch{% endif %}. Required workflows allow you to implement organization-wide CI/CD policies that apply to current and future repositories. A required workflow is triggered by {% ifversion actions-required-workflow-improvements %}`pull_request` and `pull_request_target` default events{% else %}pull request events{% endif %} and appears as a required status check, which blocks the ability to merge the pull request until the required workflow succeeds.
|
You can configure a workflow that must run in repositories in an organization for all pull requests opened against any target branch. Required workflows allow you to implement organization-wide CI/CD policies that apply to current and future repositories. A required workflow is triggered by `pull_request` and `pull_request_target` default events and appears as a required status check, which blocks the ability to merge the pull request until the required workflow succeeds.
|
||||||
|
|
||||||
Required workflows are not the same as reusable workflows. Reusable workflows can be called by another workflow. Required workflows are enforced on repositories by an organization owner.
|
Required workflows are not the same as reusable workflows. Reusable workflows can be called by another workflow. Required workflows are enforced on repositories by an organization owner.
|
||||||
|
|
||||||
|
|||||||
@@ -104,7 +104,6 @@ Called workflows that are owned by the same user or organization{% ifversion ghe
|
|||||||
* You can call a maximum of 20 unique reusable workflows from a single workflow file.
|
* You can call a maximum of 20 unique reusable workflows from a single workflow file.
|
||||||
{% endif %}
|
{% endif %}
|
||||||
{% ifversion private-actions %}{% else %}- Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
|
{% ifversion private-actions %}{% else %}- Reusable workflows stored within a private repository can only be used by workflows within the same repository.{% endif %}
|
||||||
{% ifversion actions-reusable-workflow-matrix %}{% else %}* The `strategy` property is not supported in any job that calls a reusable workflow.{% endif %}
|
|
||||||
* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information, see [AUTOTITLE](/actions/learn-github-actions/variables) and [AUTOTITLE](/actions/learn-github-actions/contexts#env-context).
|
* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information, see [AUTOTITLE](/actions/learn-github-actions/variables) and [AUTOTITLE](/actions/learn-github-actions/contexts#env-context).
|
||||||
* Similarly, environment variables set in the `env` context, defined in the called workflow, are not accessible in the `env` context of the caller workflow. Instead, you must use outputs of the reusable workflow. For more information, see [Using outputs from a reusable workflow](#using-outputs-from-a-reusable-workflow).
|
* Similarly, environment variables set in the `env` context, defined in the called workflow, are not accessible in the `env` context of the caller workflow. Instead, you must use outputs of the reusable workflow. For more information, see [Using outputs from a reusable workflow](#using-outputs-from-a-reusable-workflow).
|
||||||
* To reuse variables in multiple workflows, set them at the organization, repository, or environment levels and reference them using the `vars` context. For more information see [AUTOTITLE](/actions/learn-github-actions/variables) and [AUTOTITLE](/actions/learn-github-actions/contexts#vars-context).
|
* To reuse variables in multiple workflows, set them at the organization, repository, or environment levels and reference them using the `vars` context. For more information see [AUTOTITLE](/actions/learn-github-actions/variables) and [AUTOTITLE](/actions/learn-github-actions/contexts#vars-context).
|
||||||
@@ -142,16 +141,11 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
|||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecrets).
|
For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecrets).
|
||||||
{% ifversion actions-inherit-secrets-reusable-workflows %}
|
|
||||||
1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
|
1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If the secrets are inherited by using `secrets: inherit` in the calling workflow, you can reference them even if they are not explicitly defined in the `on` key. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit).
|
> If the secrets are inherited by using `secrets: inherit` in the calling workflow, you can reference them even if they are not explicitly defined in the `on` key. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit).
|
||||||
|
|
||||||
{%- else %}
|
|
||||||
1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
|
|
||||||
{%- endif %}
|
|
||||||
|
|
||||||
{% raw %}
|
{% raw %}
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
@@ -225,8 +219,6 @@ You can call multiple workflows, referencing each in a separate job.
|
|||||||
|
|
||||||
{% data reusables.actions.pass-inputs-to-reusable-workflows %}
|
{% data reusables.actions.pass-inputs-to-reusable-workflows %}
|
||||||
|
|
||||||
{% ifversion actions-reusable-workflow-matrix %}
|
|
||||||
|
|
||||||
### Using a matrix strategy with a reusable workflow
|
### Using a matrix strategy with a reusable workflow
|
||||||
|
|
||||||
Jobs using the matrix strategy can call a reusable workflow.
|
Jobs using the matrix strategy can call a reusable workflow.
|
||||||
@@ -249,7 +241,6 @@ jobs:
|
|||||||
```
|
```
|
||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
### Supported keywords for jobs that call a reusable workflow
|
### Supported keywords for jobs that call a reusable workflow
|
||||||
|
|
||||||
@@ -261,12 +252,8 @@ When you call a reusable workflow, you can only use the following keywords in th
|
|||||||
* [`jobs.<job_id>.with.<input_id>`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idwithinput_id)
|
* [`jobs.<job_id>.with.<input_id>`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idwithinput_id)
|
||||||
* [`jobs.<job_id>.secrets`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecrets)
|
* [`jobs.<job_id>.secrets`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecrets)
|
||||||
* [`jobs.<job_id>.secrets.<secret_id>`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id)
|
* [`jobs.<job_id>.secrets.<secret_id>`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id)
|
||||||
{%- ifversion actions-inherit-secrets-reusable-workflows %}
|
|
||||||
* [`jobs.<job_id>.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit)
|
* [`jobs.<job_id>.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit)
|
||||||
{%- endif %}
|
|
||||||
{%- ifversion actions-reusable-workflow-matrix %}
|
|
||||||
* [`jobs.<job_id>.strategy`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategy)
|
* [`jobs.<job_id>.strategy`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategy)
|
||||||
{%- endif %}
|
|
||||||
* [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds)
|
* [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds)
|
||||||
* [`jobs.<job_id>.if`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif)
|
* [`jobs.<job_id>.if`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif)
|
||||||
* [`jobs.<job_id>.concurrency`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idconcurrency)
|
* [`jobs.<job_id>.concurrency`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idconcurrency)
|
||||||
@@ -368,10 +355,10 @@ For information on how to use the API to determine which workflow files were inv
|
|||||||
|
|
||||||
## Using outputs from a reusable workflow
|
## Using outputs from a reusable workflow
|
||||||
|
|
||||||
A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.{% ifversion actions-reusable-workflow-matrix %}
|
A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.
|
||||||
|
|
||||||
If a reusable workflow that sets an output is executed with a matrix strategy, the output will be the output set by the last successful completing reusable workflow of the matrix which actually sets a value.
|
If a reusable workflow that sets an output is executed with a matrix strategy, the output will be the output set by the last successful completing reusable workflow of the matrix which actually sets a value.
|
||||||
That means if the last successful completing reusable workflow sets an empty string for its output, and the second last successful completing reusable workflow sets an actual value for its output, the output will contain the value of the second last completing reusable workflow.{% endif %}
|
That means if the last successful completing reusable workflow sets an empty string for its output, and the second last successful completing reusable workflow sets an actual value for its output, the output will contain the value of the second last completing reusable workflow.
|
||||||
|
|
||||||
The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
|
The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
|
||||||
|
|
||||||
|
|||||||
@@ -148,9 +148,8 @@ You can use `go get` to install dependencies:
|
|||||||
|
|
||||||
### Caching dependencies
|
### Caching dependencies
|
||||||
|
|
||||||
You can cache and restore dependencies using the [`setup-go` action](https://github.com/actions/setup-go). By default, caching is {% ifversion actions-setup-go-default-cache-enabled %}enabled when using the `setup-go` action.{% else %}disabled, but you can set the `cache` parameter to `true` to enable it.{% endif %}
|
You can cache and restore dependencies using the [`setup-go` action](https://github.com/actions/setup-go). By default, caching is enabled when using the `setup-go` action.
|
||||||
|
|
||||||
{% ifversion actions-setup-go-default-cache-enabled %}
|
|
||||||
The `setup-go` action searches for the dependency file, `go.sum`, in the repository root and uses the hash of the dependency file as a part of the cache key.
|
The `setup-go` action searches for the dependency file, `go.sum`, in the repository root and uses the hash of the dependency file as a part of the cache key.
|
||||||
|
|
||||||
You can use the `cache-dependency-path` parameter for cases when multiple dependency files are used, or when they are located in different subdirectories.
|
You can use the `cache-dependency-path` parameter for cases when multiple dependency files are used, or when they are located in different subdirectories.
|
||||||
@@ -163,30 +162,6 @@ You can use the `cache-dependency-path` parameter for cases when multiple depend
|
|||||||
cache-dependency-path: subdir/go.sum
|
cache-dependency-path: subdir/go.sum
|
||||||
```
|
```
|
||||||
|
|
||||||
{% else %}
|
|
||||||
|
|
||||||
When caching is enabled, the `setup-go` action searches for the dependency file, `go.sum`, in the repository root and uses the hash of the dependency file as a part of the cache key.
|
|
||||||
|
|
||||||
```yaml copy
|
|
||||||
- name: Setup Go
|
|
||||||
uses: {% data reusables.actions.action-setup-go %}
|
|
||||||
with:
|
|
||||||
go-version: '1.21.x'
|
|
||||||
cache: true
|
|
||||||
```
|
|
||||||
|
|
||||||
Alternatively, you can use the `cache-dependency-path` parameter for cases when multiple dependency files are used, or when they are located in different subdirectories.
|
|
||||||
|
|
||||||
```yaml copy
|
|
||||||
- uses: {% data reusables.actions.action-setup-go %}
|
|
||||||
with:
|
|
||||||
go-version: '1.17'
|
|
||||||
cache: true
|
|
||||||
cache-dependency-path: subdir/go.sum
|
|
||||||
```
|
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see [AUTOTITLE](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
|
If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see [AUTOTITLE](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
|
||||||
|
|
||||||
## Building and testing your code
|
## Building and testing your code
|
||||||
|
|||||||
@@ -3,7 +3,7 @@ title: Enabling GitHub Actions with Google Cloud Storage
|
|||||||
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Google Cloud Storage to store data generated by workflow runs.'
|
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Google Cloud Storage to store data generated by workflow runs.'
|
||||||
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
||||||
versions:
|
versions:
|
||||||
feature: actions-ghes-gcp-storage
|
ghes: '*'
|
||||||
type: how_to
|
type: how_to
|
||||||
topics:
|
topics:
|
||||||
- Actions
|
- Actions
|
||||||
|
|||||||
@@ -79,9 +79,7 @@ All other {% data variables.product.prodname_actions %} data, such as the workfl
|
|||||||
|
|
||||||
* Azure Blob storage
|
* Azure Blob storage
|
||||||
* Amazon S3
|
* Amazon S3
|
||||||
{%- ifversion actions-ghes-gcp-storage %}
|
|
||||||
* Google Cloud Storage
|
* Google Cloud Storage
|
||||||
{%- endif %}
|
|
||||||
* S3-compatible MinIO cluster
|
* S3-compatible MinIO cluster
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@@ -101,9 +99,7 @@ Follow one of the procedures below to enable {% data variables.product.prodname_
|
|||||||
|
|
||||||
* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage)
|
* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage)
|
||||||
* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage)
|
* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage)
|
||||||
{%- ifversion actions-ghes-gcp-storage %}
|
|
||||||
* [Enabling GitHub Actions with Google Cloud Storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage)
|
* [Enabling GitHub Actions with Google Cloud Storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage)
|
||||||
{%- endif %}
|
|
||||||
* [Enabling GitHub Actions with MinIO storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage)
|
* [Enabling GitHub Actions with MinIO storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage)
|
||||||
|
|
||||||
## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
|
## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
|
||||||
|
|||||||
@@ -29,11 +29,9 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
|
|||||||
|
|
||||||
For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository), [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization), and [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise).
|
For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository), [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization), and [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise).
|
||||||
|
|
||||||
{% ifversion ghec or ghes %}
|
|
||||||
Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see [AUTOTITLE](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows).
|
Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see [AUTOTITLE](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows).
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise) and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).{% else %}{% ifversion audit-log-streaming %}[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise) and {% endif %}[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding).{% endif %}
|
You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise) and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).{% else %}[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise) and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding).{% endif %}
|
||||||
|
|
||||||
{% ifversion custom-org-roles %}You can practice the principle of least privilege by administering custom organization roles for access to settings in your {% data variables.product.prodname_actions %} CI/CD pipeline. For more information about custom organization roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles).{% endif %}
|
{% ifversion custom-org-roles %}You can practice the principle of least privilege by administering custom organization roles for access to settings in your {% data variables.product.prodname_actions %} CI/CD pipeline. For more information about custom organization roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles).{% endif %}
|
||||||
|
|
||||||
|
|||||||
@@ -96,7 +96,6 @@ The following aggregate metrics will be collected and transmitted on a daily bas
|
|||||||
| AN | `ghe_stats.users.total_users` | Number of user accounts |
|
| AN | `ghe_stats.users.total_users` | Number of user accounts |
|
||||||
| AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators |
|
| AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators |
|
||||||
| AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended |
|
| AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended |
|
||||||
| {% ifversion actions-server-statistics %} |
|
|
||||||
| AQ | `actions_stats.number_of_repos_using_actions` | Number of repositories using {% data variables.product.prodname_actions %} |
|
| AQ | `actions_stats.number_of_repos_using_actions` | Number of repositories using {% data variables.product.prodname_actions %} |
|
||||||
| AR | `actions_stats.percentage_of_repos_using_actions` | Percentage of repositories using {% data variables.product.prodname_actions %} |
|
| AR | `actions_stats.percentage_of_repos_using_actions` | Percentage of repositories using {% data variables.product.prodname_actions %} |
|
||||||
| AS | `packages_stats.registry_enabled` | Whether {% data variables.product.prodname_registry %} with repository-scoped packages is enabled for {% data variables.location.product_location %} |
|
| AS | `packages_stats.registry_enabled` | Whether {% data variables.product.prodname_registry %} with repository-scoped packages is enabled for {% data variables.location.product_location %} |
|
||||||
@@ -167,7 +166,6 @@ The following aggregate metrics will be collected and transmitted on a daily bas
|
|||||||
| DF |`packages_stats.ecosystems.containers.daily_update_count` | Number of container images updated |
|
| DF |`packages_stats.ecosystems.containers.daily_update_count` | Number of container images updated |
|
||||||
| DG |`packages_stats.ecosystems.containers.daily_delete_count` | Number of container images deleted |
|
| DG |`packages_stats.ecosystems.containers.daily_delete_count` | Number of container images deleted |
|
||||||
| DH | `packages_stats.ecosystems.containers.daily_create_count` | Number of container images created |
|
| DH | `packages_stats.ecosystems.containers.daily_create_count` | Number of container images created |
|
||||||
| {% endif %} |
|
|
||||||
|
|
||||||
## {% data variables.product.prodname_server_statistics %} data examples
|
## {% data variables.product.prodname_server_statistics %} data examples
|
||||||
|
|
||||||
|
|||||||
@@ -43,14 +43,12 @@ In addition to viewing your audit log, you can monitor activity in your enterpri
|
|||||||
As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
|
As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
|
||||||
* You can view the audit log for your enterprise. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise).
|
* You can view the audit log for your enterprise. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise).
|
||||||
* You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise){% ifversion ghec %} and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise){% endif %}.{% ifversion token-audit-log %}
|
* You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise){% ifversion ghec %} and [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise){% endif %}.{% ifversion token-audit-log %}
|
||||||
* You can identify all events that were performed by a specific access token. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token).{% endif %}{% ifversion audit-data-retention-tab %}
|
* You can identify all events that were performed by a specific access token. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token).{% endif %}{% ifversion ghes %}
|
||||||
* You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% endif %}
|
* You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% endif %}
|
||||||
{%- ifversion enterprise-audit-log-ip-addresses %}
|
{%- ifversion enterprise-audit-log-ip-addresses %}
|
||||||
* You can display the IP address associated with events in the audit log. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise).
|
* You can display the IP address associated with events in the audit log. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise).
|
||||||
{%- endif %}
|
{%- endif %}
|
||||||
{%- ifversion audit-log-streaming %}
|
|
||||||
* You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
* You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
||||||
{%- endif %}
|
|
||||||
{%- ifversion ghes %}
|
{%- ifversion ghes %}
|
||||||
* You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding).
|
* You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding).
|
||||||
{%- endif %}
|
{%- endif %}
|
||||||
|
|||||||
@@ -4,7 +4,7 @@ intro: You can configure settings for your enterprise's audit log.
|
|||||||
shortTitle: Configure audit logs
|
shortTitle: Configure audit logs
|
||||||
permissions: Enterprise owners can configure the audit log.
|
permissions: Enterprise owners can configure the audit log.
|
||||||
versions:
|
versions:
|
||||||
feature: audit-data-retention-tab
|
ghes: '*'
|
||||||
type: how_to
|
type: how_to
|
||||||
topics:
|
topics:
|
||||||
- Auditing
|
- Auditing
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
title: Streaming the audit log for your enterprise
|
title: Streaming the audit log for your enterprise
|
||||||
intro: 'Learn how to stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
|
intro: 'Learn how to stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
|
||||||
versions:
|
versions:
|
||||||
feature: audit-log-streaming
|
ghes: '*'
|
||||||
ghec: '*'
|
ghec: '*'
|
||||||
type: tutorial
|
type: tutorial
|
||||||
topics:
|
topics:
|
||||||
|
|||||||
@@ -47,7 +47,7 @@ For a list of audit log events, see [AUTOTITLE](/admin/monitoring-activity-in-yo
|
|||||||
|
|
||||||
For information on how to access the audit log for your enterprise or organization, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) and [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization).
|
For information on how to access the audit log for your enterprise or organization, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) and [AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization).
|
||||||
|
|
||||||
{% ifversion audit-log-streaming %}
|
{% ifversion ghec or ghes %}
|
||||||
|
|
||||||
You can also stream audit data from {% data variables.product.prodname_dotcom %} to an external data management system, which enables you to analyze and collect data for internal charts. Enterprise owners can configure audit log streaming. For more information, see [Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
You can also stream audit data from {% data variables.product.prodname_dotcom %} to an external data management system, which enables you to analyze and collect data for internal charts. Enterprise owners can configure audit log streaming. For more information, see [Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
||||||
|
|
||||||
|
|||||||
@@ -276,10 +276,6 @@ To avoid exceeding a rate limit, you should pause at least 1 second between muta
|
|||||||
|
|
||||||
You should also subscribe to webhook events instead of polling the API for data. For more information, see [AUTOTITLE](/webhooks).
|
You should also subscribe to webhook events instead of polling the API for data. For more information, see [AUTOTITLE](/webhooks).
|
||||||
|
|
||||||
{% ifversion audit-log-streaming %}
|
|
||||||
|
|
||||||
You can also stream the audit log in order to view API requests. This can help you troubleshoot integrations that are exceeding the rate limit. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
You can also stream the audit log in order to view API requests. This can help you troubleshoot integrations that are exceeding the rate limit. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
||||||
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|||||||
@@ -19,8 +19,7 @@ shortTitle: '{% data variables.product.prodname_oauth_app %} restrictions'
|
|||||||
|
|
||||||
{% data reusables.apps.oauth-app-access-restrictions %}
|
{% data reusables.apps.oauth-app-access-restrictions %}
|
||||||
|
|
||||||
{% ifversion limit-app-access-requests %}
|
{% data reusables.organizations.restricted-app-access-requests %}
|
||||||
{% data reusables.organizations.restricted-app-access-requests %}{% endif %}
|
|
||||||
|
|
||||||
Even if you restrict {% data variables.product.prodname_oauth_apps %} access in your organization, users can still authorize internal {% data variables.product.prodname_oauth_apps %} apps and use them to access data from the organization. For more information, see [AUTOTITLE](/apps/oauth-apps/using-oauth-apps/internal-oauth-apps).
|
Even if you restrict {% data variables.product.prodname_oauth_apps %} access in your organization, users can still authorize internal {% data variables.product.prodname_oauth_apps %} apps and use them to access data from the organization. For more information, see [AUTOTITLE](/apps/oauth-apps/using-oauth-apps/internal-oauth-apps).
|
||||||
|
|
||||||
|
|||||||
@@ -16,8 +16,7 @@ shortTitle: Approve {% data variables.product.prodname_oauth_app %} access
|
|||||||
---
|
---
|
||||||
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators must [request approval](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources.
|
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators must [request approval](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources.
|
||||||
|
|
||||||
{% ifversion limit-app-access-requests %}
|
{% data reusables.organizations.restricted-app-access-requests %}
|
||||||
{% data reusables.organizations.restricted-app-access-requests %}{% endif %}
|
|
||||||
|
|
||||||
{% data reusables.profile.access_org %}
|
{% data reusables.profile.access_org %}
|
||||||
{% data reusables.profile.org_settings %}
|
{% data reusables.profile.org_settings %}
|
||||||
|
|||||||
@@ -98,7 +98,7 @@ You can configure this behavior for an organization using the procedure below. M
|
|||||||
|
|
||||||
{% data reusables.actions.workflows.required-workflow-beta %}
|
{% data reusables.actions.workflows.required-workflow-beta %}
|
||||||
|
|
||||||
You can configure required workflows to run in all or selected repositories in an organization where you are an owner. Required workflows are triggered by {% ifversion actions-required-workflow-improvements %}`pull_request` and `pull_request_target` default events{% else %}pull requests{% endif %} and must pass before a pull request can be merged. For more information, see [AUTOTITLE](/actions/using-workflows/required-workflows).
|
You can configure required workflows to run in all or selected repositories in an organization where you are an owner. Required workflows are triggered by `pull_request` and `pull_request_target` default events and must pass before a pull request can be merged. For more information, see [AUTOTITLE](/actions/using-workflows/required-workflows).
|
||||||
|
|
||||||
### Prerequisites
|
### Prerequisites
|
||||||
|
|
||||||
@@ -125,7 +125,7 @@ Note the following restrictions and behaviors for the target repositories:
|
|||||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||||
1. To the right of "Required Workflows", click **Add workflow**.
|
1. To the right of "Required Workflows", click **Add workflow**.
|
||||||
|
|
||||||
1. Under "Required workflow", use the drop-down menu to select the repository that contains the workflow. Then, enter the path to the workflow in the text field. {% ifversion actions-required-workflow-improvements %}You can reference any branch, tag, or commit SHA from the repository containing the workflow file using the `{path}@{ref}` syntax.{% endif %}
|
1. Under "Required workflow", use the drop-down menu to select the repository that contains the workflow. Then, enter the path to the workflow in the text field. You can reference any branch, tag, or commit SHA from the repository containing the workflow file using the `{path}@{ref}` syntax.
|
||||||
|
|
||||||
1. Under "Apply to repositories...", use the drop-down menu to select which repositories the required workflow applies to. Select **All repositories** to apply the required workflow to all repositories in your organization, or **Selected repositories** to choose which repositories it will apply to.
|
1. Under "Apply to repositories...", use the drop-down menu to select which repositories the required workflow applies to. Select **All repositories** to apply the required workflow to all repositories in your organization, or **Selected repositories** to choose which repositories it will apply to.
|
||||||
|
|
||||||
@@ -160,9 +160,7 @@ You can set the default permissions for the `GITHUB_TOKEN` in the settings for y
|
|||||||
|
|
||||||
### Configuring the default `GITHUB_TOKEN` permissions
|
### Configuring the default `GITHUB_TOKEN` permissions
|
||||||
|
|
||||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
|
||||||
By default, when you create a new organization,{% ifversion ghec or ghes %} the setting is inherited from what is configured in the enterprise settings.{% else %} `GITHUB_TOKEN` only has read access for the `contents` and `packages` scopes.{% endif %}
|
By default, when you create a new organization,{% ifversion ghec or ghes %} the setting is inherited from what is configured in the enterprise settings.{% else %} `GITHUB_TOKEN` only has read access for the `contents` and `packages` scopes.{% endif %}
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
{% data reusables.profile.access_profile %}
|
{% data reusables.profile.access_profile %}
|
||||||
{% data reusables.profile.access_org %}
|
{% data reusables.profile.access_org %}
|
||||||
@@ -171,23 +169,19 @@ By default, when you create a new organization,{% ifversion ghec or ghes %} the
|
|||||||
{% data reusables.actions.workflows.github-token-access %}
|
{% data reusables.actions.workflows.github-token-access %}
|
||||||
1. Click **Save** to apply the settings.
|
1. Click **Save** to apply the settings.
|
||||||
|
|
||||||
{% ifversion allow-actions-to-approve-pr %}
|
### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
|
||||||
|
|
||||||
### Preventing {% data variables.product.prodname_actions %} from {% ifversion allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests
|
|
||||||
|
|
||||||
{% data reusables.actions.workflow-pr-approval-permissions-intro %}
|
{% data reusables.actions.workflow-pr-approval-permissions-intro %}
|
||||||
|
|
||||||
By default, when you create a new organization, workflows are not allowed to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests.
|
By default, when you create a new organization, workflows are not allowed to create or approve pull requests.
|
||||||
|
|
||||||
{% data reusables.profile.access_profile %}
|
{% data reusables.profile.access_profile %}
|
||||||
{% data reusables.profile.access_org %}
|
{% data reusables.profile.access_org %}
|
||||||
{% data reusables.profile.org_settings %}
|
{% data reusables.profile.org_settings %}
|
||||||
{% data reusables.organizations.settings-sidebar-actions-general %}
|
{% data reusables.organizations.settings-sidebar-actions-general %}
|
||||||
1. Under "Workflow permissions", use the **Allow GitHub Actions to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests** setting to configure whether `GITHUB_TOKEN` can {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests.
|
1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
|
||||||
1. Click **Save** to apply the settings.
|
1. Click **Save** to apply the settings.
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
## Managing {% data variables.product.prodname_actions %} cache storage for your organization
|
## Managing {% data variables.product.prodname_actions %} cache storage for your organization
|
||||||
|
|
||||||
Organization administrators can view {% ifversion ghes %}and manage {% endif %}{% data variables.product.prodname_actions %} cache storage for all repositories in the organization.
|
Organization administrators can view {% ifversion ghes %}and manage {% endif %}{% data variables.product.prodname_actions %} cache storage for all repositories in the organization.
|
||||||
|
|||||||
@@ -22,7 +22,7 @@ versions:
|
|||||||
|
|
||||||
Organization owners can install {% data variables.product.prodname_github_apps %} on their organization. Repository admins can also install a {% data variables.product.prodname_github_app %} on the organization if the app does not request organization resources and if they only grant the app access to repositories where they are an admin. Organization members can submit a request for their organization owner to install a {% data variables.product.prodname_github_app %} on the organization. For more information, see {% ifversion fpt or ghec %}[AUTOTITLE](/apps/using-github-apps/installing-an-app-in-your-organization).{% else %}[AUTOTITLE](/apps/maintaining-github-apps/installing-github-apps).{% endif %}
|
Organization owners can install {% data variables.product.prodname_github_apps %} on their organization. Repository admins can also install a {% data variables.product.prodname_github_app %} on the organization if the app does not request organization resources and if they only grant the app access to repositories where they are an admin. Organization members can submit a request for their organization owner to install a {% data variables.product.prodname_github_app %} on the organization. For more information, see {% ifversion fpt or ghec %}[AUTOTITLE](/apps/using-github-apps/installing-an-app-in-your-organization).{% else %}[AUTOTITLE](/apps/maintaining-github-apps/installing-github-apps).{% endif %}
|
||||||
|
|
||||||
{% ifversion limit-app-access-requests %}Organization owners can prevent outside collaborators from requesting {% data variables.product.prodname_github_apps %} or from installing a {% data variables.product.prodname_github_app %} even if the collaborator is a repository admin. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/limiting-oauth-app-and-github-app-access-requests).{% endif %}
|
Organization owners can prevent outside collaborators from requesting {% data variables.product.prodname_github_apps %} or from installing a {% data variables.product.prodname_github_app %} even if the collaborator is a repository admin. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/limiting-oauth-app-and-github-app-access-requests).
|
||||||
|
|
||||||
Organization owners can review the {% data variables.product.prodname_github_apps %} that are installed on their organization and modify the repositories that each app can access. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/reviewing-github-apps-installed-in-your-organization).
|
Organization owners can review the {% data variables.product.prodname_github_apps %} that are installed on their organization and modify the repositories that each app can access. For more information, see [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/reviewing-github-apps-installed-in-your-organization).
|
||||||
|
|
||||||
|
|||||||
@@ -19,7 +19,7 @@ To perform any actions on {% data variables.product.product_name %}, such as cre
|
|||||||
|
|
||||||
Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
|
Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
|
||||||
|
|
||||||
You can have more granular control over the permissions you grant at the repository level by creating up to {% ifversion authz-increased-custom-repo-roles %}five {% else %}three {% endif %} custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-custom-repository-roles-for-an-organization).
|
You can have more granular control over the permissions you grant at the repository level by creating up to five custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-custom-repository-roles-for-an-organization).
|
||||||
|
|
||||||
After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository).
|
After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository) and [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository).
|
||||||
|
|
||||||
|
|||||||
@@ -91,9 +91,7 @@ The default permissions can also be configured in the organization settings. If
|
|||||||
|
|
||||||
### Configuring the default `GITHUB_TOKEN` permissions
|
### Configuring the default `GITHUB_TOKEN` permissions
|
||||||
|
|
||||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
|
||||||
By default, when you create a new repository in your personal account, `GITHUB_TOKEN` only has read access for the `contents` and `packages` scopes. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
|
By default, when you create a new repository in your personal account, `GITHUB_TOKEN` only has read access for the `contents` and `packages` scopes. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
{% data reusables.repositories.navigate-to-repo %}
|
{% data reusables.repositories.navigate-to-repo %}
|
||||||
{% data reusables.repositories.sidebar-settings %}
|
{% data reusables.repositories.sidebar-settings %}
|
||||||
@@ -101,22 +99,17 @@ By default, when you create a new repository in your personal account, `GITHUB_T
|
|||||||
{% data reusables.actions.workflows.github-token-access %}
|
{% data reusables.actions.workflows.github-token-access %}
|
||||||
1. Click **Save** to apply the settings.
|
1. Click **Save** to apply the settings.
|
||||||
|
|
||||||
{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
|
|
||||||
|
|
||||||
### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
|
### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
|
||||||
|
|
||||||
{% data reusables.actions.workflow-pr-approval-permissions-intro %}
|
{% data reusables.actions.workflow-pr-approval-permissions-intro %}
|
||||||
|
|
||||||
{% ifversion actions-default-workflow-permissions-restrictive %}
|
|
||||||
By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
|
By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
{% data reusables.repositories.navigate-to-repo %}
|
{% data reusables.repositories.navigate-to-repo %}
|
||||||
{% data reusables.repositories.sidebar-settings %}
|
{% data reusables.repositories.sidebar-settings %}
|
||||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||||
1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
|
1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
|
||||||
1. Click **Save** to apply the settings.
|
1. Click **Save** to apply the settings.
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
{% ifversion ghes or ghec %}
|
{% ifversion ghes or ghec %}
|
||||||
|
|
||||||
|
|||||||
@@ -19,13 +19,11 @@ shortTitle: Configure autolinks
|
|||||||
|
|
||||||
Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests, commit messages, and release descriptions to external third-party services.
|
Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests, commit messages, and release descriptions to external third-party services.
|
||||||
|
|
||||||
{% ifversion autolink-reference-alphanumeric %}
|
|
||||||
Autolink references can now accept alphanumeric characters. When originally introduced, custom autolinks were limited to external resources that used numeric identifiers. Custom autolinks now work with alphanumeric and numeric identifiers.
|
Autolink references can now accept alphanumeric characters. When originally introduced, custom autolinks were limited to external resources that used numeric identifiers. Custom autolinks now work with alphanumeric and numeric identifiers.
|
||||||
|
|
||||||
You define custom autolinks by specifying a reference prefix and a target URL.
|
You define custom autolinks by specifying a reference prefix and a target URL.
|
||||||
* Reference prefixes cannot have overlapping names. For example, a repository cannot have two custom autolinks with prefixes such as `TICKET` and `TICK`, since both prefixes would match the string `TICKET123a`.
|
* Reference prefixes cannot have overlapping names. For example, a repository cannot have two custom autolinks with prefixes such as `TICKET` and `TICK`, since both prefixes would match the string `TICKET123a`.
|
||||||
* Target URLs include a `<num>` variable which represents the reference identifier of the linked resource.
|
* Target URLs include a `<num>` variable which represents the reference identifier of the linked resource.
|
||||||
{% endif %}
|
|
||||||
|
|
||||||
## Configuring autolinks to reference external resources
|
## Configuring autolinks to reference external resources
|
||||||
|
|
||||||
@@ -37,9 +35,7 @@ This procedure demonstrates how to configure autolinks to reference external res
|
|||||||
1. At the top right of the page, click **Add autolink reference**.
|
1. At the top right of the page, click **Add autolink reference**.
|
||||||
|
|
||||||
|
|
||||||
{% ifversion autolink-reference-alphanumeric %}
|
|
||||||
1. Select the format of the reference identifier used in the external resource, either **Alphanumeric** or **Numeric**.
|
1. Select the format of the reference identifier used in the external resource, either **Alphanumeric** or **Numeric**.
|
||||||
{% endif %}
|
|
||||||
1. Under "Reference prefix", type a short, meaningful prefix. Collaborators will use this text to generate autolinks for the external resource.
|
1. Under "Reference prefix", type a short, meaningful prefix. Collaborators will use this text to generate autolinks for the external resource.
|
||||||
1. Under "Target URL", type the format of the link to the external system you want to create. Use the `<num>` variable as a placeholder for the reference identifier.
|
1. Under "Target URL", type the format of the link to the external system you want to create. Use the `<num>` variable as a placeholder for the reference identifier.
|
||||||
1. Review the preview and verify that the autolink and external reference are both correct, then click **Add autolink reference** to define the link.
|
1. Review the preview and verify that the autolink and external reference are both correct, then click **Add autolink reference** to define the link.
|
||||||
|
|||||||
@@ -109,7 +109,7 @@ Continuing to make requests while you are rate limited may result in the banning
|
|||||||
|
|
||||||
You should follow best practices to help you stay under the rate limits. See [AUTOTITLE](/rest/guides/best-practices-for-using-the-rest-api).
|
You should follow best practices to help you stay under the rate limits. See [AUTOTITLE](/rest/guides/best-practices-for-using-the-rest-api).
|
||||||
|
|
||||||
{% ifversion audit-log-streaming %}
|
{% ifversion ghec or ghes %}
|
||||||
|
|
||||||
You can also stream the audit log in order to view API requests. This can help you troubleshoot integrations that are exceeding the rate limit. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
You can also stream the audit log in order to view API requests. This can help you troubleshoot integrations that are exceeding the rate limit. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
|
||||||
|
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
actions/setup-go@{% ifversion actions-setup-go-default-cache-enabled %}v5{% else %}v3{% endif %}
|
actions/setup-go@v5
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
When you use the repository's `GITHUB_TOKEN` to perform tasks, events triggered by the `GITHUB_TOKEN`{% ifversion actions-token-updated-triggers %}, with the exception of `workflow_dispatch` and `repository_dispatch`,{% endif %} will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's `GITHUB_TOKEN`, a new workflow will not run even when the repository contains a workflow configured to run when `push` events occur.
|
When you use the repository's `GITHUB_TOKEN` to perform tasks, events triggered by the `GITHUB_TOKEN`, with the exception of `workflow_dispatch` and `repository_dispatch`, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's `GITHUB_TOKEN`, a new workflow will not run even when the repository contains a workflow configured to run when `push` events occur.
|
||||||
|
|||||||
@@ -10,11 +10,8 @@
|
|||||||
ghe-config secrets.actions.storage.blob-provider "s3"
|
ghe-config secrets.actions.storage.blob-provider "s3"
|
||||||
```
|
```
|
||||||
|
|
||||||
{%- ifversion actions-ghes-gcp-storage %}
|
|
||||||
* Google Cloud Storage:
|
* Google Cloud Storage:
|
||||||
|
|
||||||
```shell copy
|
```shell copy
|
||||||
ghe-config secrets.actions.storage.blob-provider "gcs"
|
ghe-config secrets.actions.storage.blob-provider "gcs"
|
||||||
```
|
```
|
||||||
|
|
||||||
{%- endif %}
|
|
||||||
|
|||||||
@@ -21,7 +21,6 @@
|
|||||||
ghe-config secrets.actions.storage.s3.force-path-style true
|
ghe-config secrets.actions.storage.s3.force-path-style true
|
||||||
```
|
```
|
||||||
|
|
||||||
{%- ifversion actions-ghes-gcp-storage %}
|
|
||||||
* Google Cloud Storage:
|
* Google Cloud Storage:
|
||||||
|
|
||||||
```shell copy
|
```shell copy
|
||||||
@@ -30,5 +29,3 @@
|
|||||||
ghe-config secrets.actions.storage.gcs.access-key-id "HMAC ACCESS ID"
|
ghe-config secrets.actions.storage.gcs.access-key-id "HMAC ACCESS ID"
|
||||||
ghe-config secrets.actions.storage.gcs.access-secret "HMAC SECRET"
|
ghe-config secrets.actions.storage.gcs.access-secret "HMAC SECRET"
|
||||||
```
|
```
|
||||||
|
|
||||||
{%- endif %}
|
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3,{% ifversion actions-ghes-gcp-storage %} Google Cloud Storage,{% endif %} or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure{% ifversion actions-ghes-gcp-storage %}, Google Cloud,{% endif %} or AWS.
|
{% data variables.product.prodname_actions %} uses external storage to store workflow artifacts and logs. This data is stored on your external provider, such as Azure blob storage, Amazon S3, Google Cloud Storage, or MinIO. As a result, {% data variables.product.prodname_ghe_server %} backups and {% data variables.product.prodname_ghe_server %} high availability configurations do not provide protection for the data stored on this external storage, and instead rely on the data protection and replication provided by the external storage provider, such as Azure, Google Cloud, or AWS.
|
||||||
|
|||||||
@@ -1,8 +1,4 @@
|
|||||||
{% ifversion actions-unified-inputs %}
|
|
||||||
|
|
||||||
> [!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.
|
> * 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 number of top-level properties for `inputs` is 10.
|
||||||
> * The maximum payload for `inputs` is 65,535 characters.
|
> * The maximum payload for `inputs` is 65,535 characters.
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|||||||
@@ -14,7 +14,6 @@ jobs:
|
|||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
|
|
||||||
{% ifversion actions-inherit-secrets-reusable-workflows %}
|
|
||||||
Workflows that call reusable workflows in the same organization or enterprise can use the `inherit` keyword to implicitly pass the secrets.
|
Workflows that call reusable workflows in the same organization or enterprise can use the `inherit` keyword to implicitly pass the secrets.
|
||||||
|
|
||||||
{% raw %}
|
{% raw %}
|
||||||
@@ -29,5 +28,3 @@ jobs:
|
|||||||
```
|
```
|
||||||
|
|
||||||
{% endraw %}
|
{% endraw %}
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
|
|||||||
@@ -27,8 +27,8 @@ on:
|
|||||||
jobs:
|
jobs:
|
||||||
print-tag:
|
print-tag:
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
if: {% ifversion actions-unified-inputs %}{% raw %} ${{ inputs.print_tags }} {% endraw %}{% else %}{% raw %} ${{ github.event.inputs.print_tags == 'true' }} {% endraw %}{% endif %}
|
if:{% raw %} ${{ inputs.print_tags }} {% endraw %}
|
||||||
steps:
|
steps:
|
||||||
- name: Print the input tag to STDOUT
|
- name: Print the input tag to STDOUT
|
||||||
run: {% ifversion actions-unified-inputs %}echo {% raw %} The tags are ${{ inputs.tags }} {% endraw %}{% else %}echo {% raw %} The tags are ${{ github.event.inputs.tags }} {% endraw %}{% endif %}
|
run: echo {% raw %} The tags are ${{ inputs.tags }} {% endraw %}
|
||||||
```
|
```
|
||||||
|
|||||||
@@ -1,3 +1,3 @@
|
|||||||
The triggered workflow receives the inputs in the {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} context. For more information, see [Contexts]({% ifversion actions-unified-inputs %}/actions/learn-github-actions/contexts#inputs-context{% else %}/actions/learn-github-actions/contexts#github-context{% endif %}).
|
The triggered workflow receives the inputs in the `inputs` context. For more information, see [Contexts](/actions/learn-github-actions/contexts#inputs-context).
|
||||||
|
|
||||||
{% data reusables.actions.inputs-vs-github-event-inputs %}
|
{% data reusables.actions.inputs-vs-github-event-inputs %}
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
You can choose to allow or prevent {% data variables.product.prodname_actions %} workflows from{% ifversion allow-actions-to-approve-pr-with-ent-repo %} creating or{% endif %} approving pull requests.
|
You can choose to allow or prevent {% data variables.product.prodname_actions %} workflows from creating or approving pull requests.
|
||||||
|
|||||||
@@ -1 +1 @@
|
|||||||
1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all permissions (the permissive setting), or just read access for the `contents` {% ifversion actions-default-workflow-permissions-restrictive %}and `packages` permissions{% else %}permission{% endif %} (the restricted setting).
|
1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all permissions (the permissive setting), or just read access for the `contents` and `packages` permissions (the restricted setting).
|
||||||
|
|||||||
@@ -1,8 +1,8 @@
|
|||||||
* {% data variables.product.prodname_actions %} must be enabled for a repository in the organization's settings in order for required workflows to run. Once enabled at an organization-level, required workflows will run even when {% data variables.product.prodname_actions %} is disabled in the repository's settings. For more information on managing {% data variables.product.prodname_actions %} in your organization's repositories, see [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization).
|
* {% data variables.product.prodname_actions %} must be enabled for a repository in the organization's settings in order for required workflows to run. Once enabled at an organization-level, required workflows will run even when {% data variables.product.prodname_actions %} is disabled in the repository's settings. For more information on managing {% data variables.product.prodname_actions %} in your organization's repositories, see [AUTOTITLE](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization).
|
||||||
* Required workflows are available for organizations and only in repositories where the organization's plan supports required status checks. If required status checks are not supported, the workflow will still run, but it will not be a required check and will not block merging. For more information about support for required status checks, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches).
|
* Required workflows are available for organizations and only in repositories where the organization's plan supports required status checks. If required status checks are not supported, the workflow will still run, but it will not be a required check and will not block merging. For more information about support for required status checks, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches).
|
||||||
* The repository's default branch must match the organization's default branch setting in order for required workflows to run as required status checks. If the default branch names do not match, the workflow will still run, but it will not be a required check. For more information about managing default branch names, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization) and [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch).
|
* The repository's default branch must match the organization's default branch setting in order for required workflows to run as required status checks. If the default branch names do not match, the workflow will still run, but it will not be a required check. For more information about managing default branch names, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization) and [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch).
|
||||||
* For required workflows to run, the pull request's source repository must be in the same organization as the target repository. {% data variables.product.product_name %} will source the required workflow from {% ifversion actions-required-workflow-improvements %}a specified branch, tag, or commit SHA {% else %}the HEAD commit of the default branch {% endif %}from the repository containing the workflow.
|
* For required workflows to run, the pull request's source repository must be in the same organization as the target repository. {% data variables.product.product_name %} will source the required workflow from a specified branch, tag, or commit SHA from the repository containing the workflow.
|
||||||
* Secrets used in a required workflow should be created at either the organization level or in the target repositories.
|
* Secrets used in a required workflow should be created at either the organization level or in the target repositories.
|
||||||
* Secrets in the source repository will not be fetched when a workflow runs in the target repository.
|
* Secrets in the source repository will not be fetched when a workflow runs in the target repository.
|
||||||
{% ifversion actions-required-workflow-improvements %}* When a workflow is run as a required workflow it will ignore all the filters in the `on:` section, for example: `branches`, `branches-ignore`, `paths`, `types` etc. The required workflow will run only for the `pull_request` and `pull_request_target` default events. For more information on default activity types, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request).{% endif %}
|
* When a workflow is run as a required workflow it will ignore all the filters in the `on:` section, for example: `branches`, `branches-ignore`, `paths`, `types` etc. The required workflow will run only for the `pull_request` and `pull_request_target` default events. For more information on default activity types, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request).
|
||||||
* Required workflows are not automatically triggered on already existing pull requests even though they automatically appear as expected checks. To trigger required workflows for an already existing pull request, push a new change to that pull request.
|
* Required workflows are not automatically triggered on already existing pull requests even though they automatically appear as expected checks. To trigger required workflows for an already existing pull request, push a new change to that pull request.
|
||||||
|
|||||||
@@ -2,10 +2,8 @@
|
|||||||
* If the required workflow is contained in a private {% ifversion ghes or ghec %}or internal {% endif %}repository, you must ensure that workflows within the repository are accessible by other repositories in your organization. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-access-for-a-private-repository){% ifversion ghes or ghec %} and [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}.
|
* If the required workflow is contained in a private {% ifversion ghes or ghec %}or internal {% endif %}repository, you must ensure that workflows within the repository are accessible by other repositories in your organization. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-access-for-a-private-repository){% ifversion ghes or ghec %} and [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}.
|
||||||
* Workflows stored in a public repository can be configured as required workflows for any repository in your organization. Workflows stored in a private repository can only be configured as required workflows for other private repositories in your organization. {% ifversion ghes or ghec %} Workflows stored in internal repositories can be configured as required workflows for internal and private repositories in your organization.{% endif %}
|
* Workflows stored in a public repository can be configured as required workflows for any repository in your organization. Workflows stored in a private repository can only be configured as required workflows for other private repositories in your organization. {% ifversion ghes or ghec %} Workflows stored in internal repositories can be configured as required workflows for internal and private repositories in your organization.{% endif %}
|
||||||
* {% data variables.product.prodname_codeql %} is not supported in required workflows because {% data variables.product.prodname_codeql %} requires configuration at the repository level. For information on configuring code scanning, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
|
* {% data variables.product.prodname_codeql %} is not supported in required workflows because {% data variables.product.prodname_codeql %} requires configuration at the repository level. For information on configuring code scanning, see [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning).
|
||||||
{% ifversion actions-required-workflow-improvements %}
|
|
||||||
{% ifversion fpt or ghec %}
|
{% ifversion fpt or ghec %}
|
||||||
* To push to a branch where required workflows are enforced at the organizational level, create a pull request to make the necessary changes. You cannot push directly to branches with required workflow enforcements.
|
* To push to a branch where required workflows are enforced at the organizational level, create a pull request to make the necessary changes. You cannot push directly to branches with required workflow enforcements.
|
||||||
* If you want to allow direct pushes for a particular repository, you must remove the repository as a target from respective required workflows.
|
* If you want to allow direct pushes for a particular repository, you must remove the repository as a target from respective required workflows.
|
||||||
{% endif %}
|
{% endif %}
|
||||||
* Required workflows can be referenced using any branch, tag, or commit SHA from the repository containing the workflow file.
|
* Required workflows can be referenced using any branch, tag, or commit SHA from the repository containing the workflow file.
|
||||||
{% endif %}
|
|
||||||
|
|||||||
@@ -5,9 +5,7 @@
|
|||||||
| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). |
|
| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see [AUTOTITLE](/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories). |
|
||||||
| {% endif %} |
|
| {% endif %} |
|
||||||
| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. |
|
| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. |
|
||||||
| {% ifversion audit-log-streaming %} |
|
|
||||||
| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. |
|
| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. |
|
||||||
| {% endif %} |
|
|
||||||
| {% ifversion fpt or ghec %} |
|
| {% ifversion fpt or ghec %} |
|
||||||
| `billing` | Contains activities related to an organization's billing. |
|
| `billing` | Contains activities related to an organization's billing. |
|
||||||
| {% endif %} |
|
| {% endif %} |
|
||||||
|
|||||||
@@ -1,3 +1,3 @@
|
|||||||
The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely{% ifversion audit-data-retention-tab %}, unless an enterprise owner configured a different retention period. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% else %}.{% endif %}{% else %} within the last 180 days. {% data reusables.audit_log.git-events-retention-period %}{% endif %}
|
The audit log lists events triggered by activities that affect your enterprise{% ifversion ghes %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely, unless an enterprise owner configured a different retention period. See [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise).{% else %} within the last 180 days. {% data reusables.audit_log.git-events-retention-period %}{% endif %}
|
||||||
|
|
||||||
{% data reusables.audit_log.only-three-months-displayed %}
|
{% data reusables.audit_log.only-three-months-displayed %}
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
An SBOM is a formal, machine-readable inventory of a project's dependencies and associated information (such as {% ifversion ghes %}versions and package identifiers{% else %}versions, package identifiers, licenses, and copyright information{% endif %}). SBOMs help reduced supply chain risks by:
|
An SBOM is a formal, machine-readable inventory of a project's dependencies and associated information (such as {% ifversion ghes %}versions and package identifiers{% else %}versions, package identifiers, licenses, and copyright information{% endif %}). SBOMs help reduced supply chain risks by:
|
||||||
|
|
||||||
* providing transparency about the dependencies used by your repository
|
* Providing transparency about the dependencies used by your repository
|
||||||
* allowing vulnerabilities to be identified early in the process
|
* Allowing vulnerabilities to be identified early in the process
|
||||||
* providing insights in the license compliance, security, or quality issues that may exist in your codebase
|
* Providing insights in the license compliance, security, or quality issues that may exist in your codebase
|
||||||
* enabling you to better comply with various data protection standards
|
* Enabling you to better comply with various data protection standards
|
||||||
|
|||||||
Reference in New Issue
Block a user