diff --git a/.devcontainer/test-custom-devcontainer/devcontainer.json b/.devcontainer/test-custom-devcontainer/devcontainer.json index f01eb04cd2..ab3c53f7a7 100644 --- a/.devcontainer/test-custom-devcontainer/devcontainer.json +++ b/.devcontainer/test-custom-devcontainer/devcontainer.json @@ -2,7 +2,7 @@ "name": "test", "settings": { - "terminal.integrated.shell.linux": "/bin/csh", + "terminal.integrated.shell.linux": "/bin/zsh", }, // Visual Studio Code extensions which help authoring for docs.github.com. diff --git a/.vscode/settings.json b/.vscode/settings.json index 1be4592020..2949e3e7ec 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -3,5 +3,5 @@ "**/translations": true }, "workbench.editor.enablePreview": false, - "workbench.editor.enablePreviewFromQuickOpen": false + "workbench.editor.enablePreviewFromQuickOpen": false } diff --git a/codespaces-settings.json b/codespaces-settings.json new file mode 100644 index 0000000000..840c49b326 --- /dev/null +++ b/codespaces-settings.json @@ -0,0 +1 @@ +"isInternal": true diff --git a/components/ui/MarkdownContent/MarkdownContent.module.scss b/components/ui/MarkdownContent/MarkdownContent.module.scss index 9bd45008ec..8b24220d94 100644 --- a/components/ui/MarkdownContent/MarkdownContent.module.scss +++ b/components/ui/MarkdownContent/MarkdownContent.module.scss @@ -6,6 +6,7 @@ .markdownBody { a { text-decoration: underline; + text-underline-offset: 25%; } summary { diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index 8665f92a1b..a51cc186df 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -71,6 +71,14 @@ Secrets stored in an environment are only available to workflow jobs that refere {% data reusables.actions.permissions-statement-environment %} +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.actions.sidebar-environment %} diff --git a/content/actions/security-guides/security-hardening-for-github-actions.md b/content/actions/security-guides/security-hardening-for-github-actions.md index 63f865b05d..efbb783477 100644 --- a/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/content/actions/security-guides/security-hardening-for-github-actions.md @@ -48,6 +48,12 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - **Consider requiring review for access to secrets** - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." +{% warning %} + +**Warning**: Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required. + +{% endwarning %} + ## Using `CODEOWNERS` to monitor changes You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer. diff --git a/content/code-security/security-overview/about-the-security-overview.md b/content/code-security/security-overview/about-the-security-overview.md index d30f5e94a8..468aed1cfe 100644 --- a/content/code-security/security-overview/about-the-security-overview.md +++ b/content/code-security/security-overview/about-the-security-overview.md @@ -22,7 +22,9 @@ topics: shortTitle: About security overview --- +{% ifversion ghes < 3.5 or ghae-issue-4554 %} {% data reusables.security-center.beta %} +{% endif %} ## About the security overview diff --git a/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index dd986de0e4..76c15fc8a5 100644 --- a/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -17,7 +17,9 @@ topics: shortTitle: Filtering alerts --- +{% ifversion ghes < 3.5 or ghae-issue-4554 %} {% data reusables.security-center.beta %} +{% endif %} ## About filtering the security overview diff --git a/content/code-security/security-overview/viewing-the-security-overview.md b/content/code-security/security-overview/viewing-the-security-overview.md index 6ab744c81f..8239d2dffc 100644 --- a/content/code-security/security-overview/viewing-the-security-overview.md +++ b/content/code-security/security-overview/viewing-the-security-overview.md @@ -17,7 +17,9 @@ topics: shortTitle: View the security overview --- +{% ifversion ghes < 3.5 or ghae-issue-4554 %} {% data reusables.security-center.beta %} +{% endif %} ## Viewing the security overview for an organization @@ -43,7 +45,7 @@ shortTitle: View the security overview ## Viewing the security overview for an enterprise {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} -1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Security**. +1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**. {% endif %} ## Viewing alerts for a repository diff --git a/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index 3686f1a295..e1e2978286 100644 --- a/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -34,6 +34,8 @@ shortTitle: Configure default editor - [CodeRunner](https://coderunnerapp.com/) - [SlickEdit](https://www.slickedit.com/) - [Xcode](https://developer.apple.com/xcode/) +- [RStudio](https://rstudio.com/) +- [Nova](https://nova.app/) - [Android Studio](https://developer.android.com/studio) {% endmac %} @@ -47,10 +49,18 @@ shortTitle: Configure default editor - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) - [Typora](https://typora.io/) - [SlickEdit](https://www.slickedit.com/) +- [JetBrains IntelliJ Idea](https://www.jetbrains.com/idea/) - [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) - [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) - [JetBrains Rider](https://www.jetbrains.com/rider/) +- [JetBrains CLion](https://www.jetbrains.com/clion/) +- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/) +- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/) +- [JetBrains GoLand](https://www.jetbrains.com/go/) +- [Android Studio](https://developer.android.com/studio) +- [Brackets](http://brackets.io/) - [Notepad++](https://notepad-plus-plus.org/) +- [RStudio](https://rstudio.com/) {% endwindows %} diff --git a/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md index 97616c843a..02a07cdf21 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ b/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -12,12 +12,17 @@ topics: - Organizations - Teams shortTitle: View organization insights +permissions: Organization members can view organization insights. --- -All members of an organization can view organization insights. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." - You can use organization activity insights to help you better understand how members of your organization are using {% data variables.product.product_name %} to collaborate and work on code. Dependency insights can help you track, report, and act on your organization's open source usage. +{% note %} + +**Note:** To view organization insights, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + ## Viewing organization activity insights {% note %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md index a10e14367e..2a2ac15aba 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md @@ -17,6 +17,13 @@ You can access {% data variables.product.company_short %}'s compliance reports i {% data reusables.security.compliance-report-list %} + +{% note %} + +**Note:** To view compliance reports, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + ## Accessing compliance reports for your organization {% data reusables.profile.access_org %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 61b87d6530..8fd6ad0d77 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -114,8 +114,7 @@ You can enable or disable features for all repositories. ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) {% endif %} -{% ifversion ghec or ghes > 3.2 %} - +{% ifversion fpt or ghec or ghes > 3.2 %} ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md index 79c65d6fe2..354201e86e 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md @@ -30,6 +30,14 @@ When restricted email notifications are enabled in an organization, members can {% data reusables.notifications.email-restrictions-verification %} +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To restrict email notifications, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)." diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 15c9218d68..265289d743 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -135,18 +135,17 @@ Using the qualifier `country`, you can filter events in the audit log based on t You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}. {% ifversion fpt or ghec %} -The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} + +{% note %} + +**Note:** To use the audit log API, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} ### Using the GraphQL API {% endif %} -{% note %} - -**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} - -{% endnote %} - To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audit-log-api-info %} @@ -162,12 +161,6 @@ For example, you can make a GraphQL request to see all the new organization memb ### Using the REST API -{% note %} - -**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. - -{% endnote %} - To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audited-data-list %} diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index a75bc10070..9005a244e3 100644 --- a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -20,6 +20,8 @@ shortTitle: SSH certificate authorities An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. +{% data reusables.organizations.ssh-ca-ghec-only %} + After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/content/organizations/managing-git-access-to-your-organizations-repositories/index.md index ddff241ba3..cd69a68029 100644 --- a/content/organizations/managing-git-access-to-your-organizations-repositories/index.md +++ b/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -20,3 +20,4 @@ children: shortTitle: Manage Git access --- +{% data reusables.organizations.ssh-ca-ghec-only %} diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md index 2603271a40..2551468622 100644 --- a/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md +++ b/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -14,12 +14,13 @@ topics: - Organizations - Teams shortTitle: Manage SSH authorities +permissions: Organization owners can manage an organization's SSH certificate authorities (CA). --- -Organization owners can manage an organization's SSH certificate authorities (CA). - You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)." +{% data reusables.organizations.ssh-ca-ghec-only %} + {% data reusables.organizations.add-extension-to-cert %} ## Adding an SSH certificate authority diff --git a/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index e64b4978fc..5c3a4f8519 100644 --- a/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -40,10 +40,12 @@ Enterprise owners can restrict the options you have available for your organizat ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + {%- endif %} + {% ifversion fpt or ghec %} {% note %} - **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. + **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endnote %} {%- endif %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 5839c6e333..53c1f2768f 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -18,6 +18,8 @@ shortTitle: IAM with SAML SSO {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.ghec-only %} + {% data reusables.saml.saml-accounts %} Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index e1e40f531d..cb58f5ff04 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -15,6 +15,8 @@ topics: If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. +{% data reusables.saml.ghec-only %} + If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation. diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index 113bb91e75..9a6ab87ccb 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML & SCIM with Okta You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). +{% data reusables.saml.ghec-only %} + SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index 2e09343277..d4d569a662 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -14,6 +14,8 @@ shortTitle: Connect an IdP When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)." +{% data reusables.saml.ghec-only %} + You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation. - Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) - Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 5ba478b6a8..22503faaa7 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -16,6 +16,8 @@ shortTitle: Enable & test SAML SSO You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization. +{% data reusables.saml.ghec-only %} + If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." {% data reusables.saml.outside-collaborators-exemption %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index 28532d2b0b..e87bf93da5 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -20,6 +20,8 @@ When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prom You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. +{% data reusables.saml.ghec-only %} + {% data reusables.saml.removed-users-can-rejoin %} If a user rejoins the organization within three months, the user's access privileges and settings will be restored. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md index 668ba3b7bc..dce8fa16a7 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -25,3 +25,4 @@ children: shortTitle: Manage SAML single sign-on --- +{% data reusables.saml.ghec-only %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 606daa4141..ba6c28bb5f 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -24,6 +24,8 @@ You can enable team synchronization between your IdP and {% data variables.produ {% data reusables.identity-and-permissions.about-team-sync %} +{% data reusables.saml.ghec-only %} + {% data reusables.identity-and-permissions.supported-idps-team-sync %} {% data reusables.identity-and-permissions.sync-team-with-idp-group %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md index 8af5f30451..8191fab81c 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -12,6 +12,8 @@ topics: shortTitle: Prepare to enforce SAML SSO --- +{% data reusables.saml.ghec-only %} + {% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following. | Task | More information | diff --git a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index a4693fa9ad..35e1e8388f 100644 --- a/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.private-pages %}' versions: fpt: '*' ghec: '*' -permissions: 'People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.' +permissions: 'People with admin access to a repository can change the visibility of a {% data variables.product.prodname_pages %} site.' redirect_from: - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site shortTitle: Change visibility of site @@ -15,6 +15,12 @@ shortTitle: Change visibility of site With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. +{% note %} + +**Note:** To publish a {% data variables.product.prodname_pages %} site privately, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." diff --git a/data/features/job-hooks-for-runners.yml b/data/features/job-hooks-for-runners.yml index fdeed1fcb4..568ccdec80 100644 --- a/data/features/job-hooks-for-runners.yml +++ b/data/features/job-hooks-for-runners.yml @@ -3,3 +3,5 @@ versions: fpt: '*' ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6530' diff --git a/data/reusables/organizations/ssh-ca-ghec-only.md b/data/reusables/organizations/ssh-ca-ghec-only.md new file mode 100644 index 0000000000..e87e7ff46c --- /dev/null +++ b/data/reusables/organizations/ssh-ca-ghec-only.md @@ -0,0 +1,8 @@ +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To use SSH certificate authorities, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/saml/ghec-only.md b/data/reusables/saml/ghec-only.md new file mode 100644 index 0000000000..dd0c53e196 --- /dev/null +++ b/data/reusables/saml/ghec-only.md @@ -0,0 +1,7 @@ +{% ifversion ghec %} +{% note %} + +**Note:** To use SAML single sign-on, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md index d22b228765..fc3439a85f 100644 --- a/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md +++ b/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -1 +1 @@ -Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see the "[secret scanning API](rest/reference/secret-scanning)." +Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see the "[secret scanning API](/rest/reference/secret-scanning)." diff --git a/lib/rest/static/apps/enabled-for-apps.json b/lib/rest/static/apps/enabled-for-apps.json index 1398a72cac..91dd7fac54 100644 --- a/lib/rest/static/apps/enabled-for-apps.json +++ b/lib/rest/static/apps/enabled-for-apps.json @@ -946,7 +946,33 @@ "requestPath": "/codes_of_conduct/{key}" } ], - "codespaces": [], + "codespaces": [ + { + "slug": "list-available-machine-types-for-a-repository", + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/machines" + }, + { + "slug": "list-repository-secrets", + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets" + }, + { + "slug": "get-a-repository-secret", + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}" + }, + { + "slug": "create-or-update-a-repository-secret", + "verb": "put", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}" + }, + { + "slug": "delete-a-repository-secret", + "verb": "delete", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}" + } + ], "collaborators": [ { "slug": "list-repository-collaborators", diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index 19bc5f997a..4000cd220b 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -30881,7 +30881,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the codespaces associated to a specified repository and the authenticated user.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Lists the codespaces associated to a specified repository and the authenticated user.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have read access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -31031,7 +31031,7 @@ "slug": "create-a-codespace-in-a-repository", "category": "codespaces", "notes": [], - "descriptionHTML": "

Creates a codespace owned by the authenticated user in the specified repository.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Creates a codespace owned by the authenticated user in the specified repository.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "201", @@ -31238,7 +31238,7 @@ "slug": "create-a-codespace-from-a-pull-request", "category": "codespaces", "notes": [], - "descriptionHTML": "

Creates a codespace owned by the authenticated user for the specified pull request.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Creates a codespace owned by the authenticated user for the specified pull request.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "201", @@ -31371,7 +31371,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists the authenticated user's codespaces.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Lists the authenticated user's codespaces.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have read access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -31683,7 +31683,7 @@ "slug": "create-a-codespace-for-the-authenticated-user", "category": "codespaces", "notes": [], - "descriptionHTML": "

Creates a new codespace, owned by the authenticated user.

\n

This endpoint requires either a repository_id OR a pull_request but not both.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Creates a new codespace, owned by the authenticated user.

\n

This endpoint requires either a repository_id OR a pull_request but not both.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "201", @@ -31874,7 +31874,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets information about a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Gets information about a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have read access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -31993,7 +31993,7 @@ "slug": "update-a-codespace-for-the-authenticated-user", "category": "codespaces", "notes": [], - "descriptionHTML": "

Updates a codespace owned by the authenticated user. Currently only the codespace's machine type and recent folders can be modified using this endpoint.

\n

If you specify a new machine type it will be applied the next time your codespace is started.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Updates a codespace owned by the authenticated user. Currently only the codespace's machine type and recent folders can be modified using this endpoint.

\n

If you specify a new machine type it will be applied the next time your codespace is started.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32086,7 +32086,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deletes a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Deletes a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "202", @@ -32156,7 +32156,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Triggers an export of the specified codespace and returns a URL and ID where the status of the export can be monitored.

\n

You must authenticate using a personal access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Triggers an export of the specified codespace and returns a URL and ID where the status of the export can be monitored.

\n

You must authenticate using a personal access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_lifecycle_admin repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "202", @@ -32237,7 +32237,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets information about an export of a codespace.

\n

You must authenticate using a personal access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Gets information about an export of a codespace.

\n

You must authenticate using a personal access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_lifecycle_admin repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32288,7 +32288,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Starts a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Starts a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_lifecycle_admin repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32374,7 +32374,7 @@ "category": "codespaces", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Stops a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

Stops a user's codespace.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_lifecycle_admin repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32454,7 +32454,7 @@ ], "summary": "List available machine types for a repository", "x-github": { - "enabledForGitHubApps": false, + "enabledForGitHubApps": true, "category": "codespaces", "subcategory": "machines" }, @@ -32463,7 +32463,7 @@ "subcategory": "machines", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List the machine types available for a given repository based on its configuration.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

List the machine types available for a given repository based on its configuration.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_metadata repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32534,7 +32534,7 @@ "subcategory": "machines", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List the machine types a codespace can transition to use.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

", + "descriptionHTML": "

List the machine types a codespace can transition to use.

\n

You must authenticate using an access token with the codespace scope to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_metadata repository permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32570,6 +32570,386 @@ ] } ], + "repository-secrets": [ + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + }, + "descriptionHTML": "

Results per page (max 100)

" + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + }, + "descriptionHTML": "

Page number of the results to fetch.

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/codespaces/secrets" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/codespaces/secrets', {\n owner: 'octocat',\n repo: 'hello-world'\n})" + } + ], + "summary": "List repository secrets", + "x-github": { + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + }, + "slug": "list-repository-secrets", + "category": "codespaces", + "subcategory": "repository-secrets", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Lists all secrets available in a repository without revealing their encrypted values. You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the secrets repository permission to use this endpoint.

", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "

Response

", + "payload": "{\n \"total_count\": 2,\n \"secrets\": [\n {\n \"name\": \"GH_TOKEN\",\n \"created_at\": \"2019-08-10T14:59:22Z\",\n \"updated_at\": \"2020-01-10T14:59:22Z\"\n },\n {\n \"name\": \"GIST_ID\",\n \"created_at\": \"2020-01-10T10:59:22Z\",\n \"updated_at\": \"2020-01-11T11:59:22Z\"\n }\n ]\n}" + } + ] + }, + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/public-key", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/codespaces/secrets/public-key" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/codespaces/secrets/public-key', {\n owner: 'octocat',\n repo: 'hello-world'\n})" + } + ], + "summary": "Get a repository public key", + "x-github": { + "enabledForGitHubApps": false, + "category": "codespaces", + "subcategory": "repository-secrets" + }, + "slug": "get-a-repository-public-key", + "category": "codespaces", + "subcategory": "repository-secrets", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the repo scope. GitHub Apps must have the secrets repository permission to use this endpoint.

", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "

Response

", + "payload": "{\n \"key_id\": \"012345678912345678\",\n \"key\": \"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234\"\n}" + } + ] + }, + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

secret_name parameter

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/codespaces/secrets/SECRET_NAME" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/codespaces/secrets/{secret_name}', {\n owner: 'octocat',\n repo: 'hello-world',\n secret_name: 'secret_name'\n})" + } + ], + "summary": "Get a repository secret", + "x-github": { + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + }, + "slug": "get-a-repository-secret", + "category": "codespaces", + "subcategory": "repository-secrets", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Gets a single repository secret without revealing its encrypted value. You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the codespaces_secrets repository permission to use this endpoint.

", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "

Response

", + "payload": "{\n \"name\": \"GH_TOKEN\",\n \"created_at\": \"2019-08-10T14:59:22Z\",\n \"updated_at\": \"2020-01-10T14:59:22Z\"\n}" + } + ] + }, + { + "verb": "put", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

secret_name parameter

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X PUT \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/codespaces/secrets/SECRET_NAME \\\n -d '{\"encrypted_value\":\"encrypted_value\"}'" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('PUT /repos/{owner}/{repo}/codespaces/secrets/{secret_name}', {\n owner: 'octocat',\n repo: 'hello-world',\n secret_name: 'secret_name',\n encrypted_value: 'encrypted_value'\n})" + } + ], + "summary": "Create or update a repository secret", + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "properties": { + "encrypted_value": { + "type": "string", + "description": "

Value for your secret, encrypted with LibSodium using the public key retrieved from the Get a repository public key endpoint.

", + "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$", + "name": "encrypted_value", + "in": "body", + "rawType": "string", + "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/codespaces#get-a-repository-public-key) endpoint.", + "childParamsGroups": [] + }, + "key_id": { + "type": "string", + "description": "

ID of the key you used to encrypt the secret.

", + "name": "key_id", + "in": "body", + "rawType": "string", + "rawDescription": "ID of the key you used to encrypt the secret.", + "childParamsGroups": [] + } + } + }, + "example": { + "encrypted_value": "c2VjcmV0", + "key_id": "012345678912345678" + } + } + } + }, + "x-github": { + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + }, + "slug": "create-or-update-a-repository-secret", + "category": "codespaces", + "subcategory": "repository-secrets", + "notes": [], + "responses": [ + { + "httpStatusCode": "201", + "httpStatusMessage": "Created", + "description": "

Response when creating a secret

" + }, + { + "httpStatusCode": "204", + "httpStatusMessage": "No Content", + "description": "

Response when updating a secret

" + } + ], + "descriptionHTML": "

Creates or updates a repository secret with an encrypted value. Encrypt your secret using\nLibSodium. You must authenticate using an access\ntoken with the repo scope to use this endpoint. GitHub Apps must have the codespaces_secrets repository\npermission to use this endpoint.

\n

Example of encrypting a secret using Node.js

\n

Encrypt your secret using the tweetsodium library.

\n
const sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n
\n

Example of encrypting a secret using Python

\n

Encrypt your secret using pynacl with Python 3.

\n
from base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n
\n

Example of encrypting a secret using C#

\n

Encrypt your secret using the Sodium.Core package.

\n
var secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n
\n

Example of encrypting a secret using Ruby

\n

Encrypt your secret using the rbnacl gem.

\n
require \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n
", + "bodyParameters": [ + { + "type": "string", + "description": "

Value for your secret, encrypted with LibSodium using the public key retrieved from the Get a repository public key endpoint.

", + "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$", + "name": "encrypted_value", + "in": "body", + "rawType": "string", + "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/codespaces#get-a-repository-public-key) endpoint.", + "childParamsGroups": [] + }, + { + "type": "string", + "description": "

ID of the key you used to encrypt the secret.

", + "name": "key_id", + "in": "body", + "rawType": "string", + "rawDescription": "ID of the key you used to encrypt the secret.", + "childParamsGroups": [] + } + ] + }, + { + "verb": "delete", + "requestPath": "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "

secret_name parameter

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -X DELETE \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/codespaces/secrets/SECRET_NAME" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('DELETE /repos/{owner}/{repo}/codespaces/secrets/{secret_name}', {\n owner: 'octocat',\n repo: 'hello-world',\n secret_name: 'secret_name'\n})" + } + ], + "summary": "Delete a repository secret", + "x-github": { + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + }, + "slug": "delete-a-repository-secret", + "category": "codespaces", + "subcategory": "repository-secrets", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Deletes a secret in a repository using the secret name. You must authenticate using an access token with the repo scope to use this endpoint. GitHub Apps must have the codespaces_secrets repository permission to use this endpoint.

", + "responses": [ + { + "httpStatusCode": "204", + "httpStatusMessage": "No Content", + "description": "

Response

" + } + ] + } + ], "secrets": [ { "verb": "get", @@ -32617,7 +32997,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Lists all secrets available for a user's Codespaces without revealing their\nencrypted values.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Lists all secrets available for a user's Codespaces without revealing their\nencrypted values.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_user_secrets user permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32652,7 +33032,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with one of the 'read:user' or 'user' scopes in their personal access token. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_user_secrets user permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32698,7 +33078,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Gets a secret available to a user's codespaces without revealing its encrypted value.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Gets a secret available to a user's codespaces without revealing its encrypted value.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_user_secrets user permission to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -32819,7 +33199,7 @@ "description": "

Validation failed

" } ], - "descriptionHTML": "

Creates or updates a secret for a user's codespace with an encrypted value. Encrypt your secret using\nLibSodium. You must authenticate using an access token with the user scope to use this endpoint. User must also have Codespaces access to use this endpoint.

\n

Example encrypting a secret using Node.js

\n

Encrypt your secret using the tweetsodium library.

\n
const sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n
\n

Example encrypting a secret using Python

\n

Encrypt your secret using pynacl with Python 3.

\n
from base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n
\n

Example encrypting a secret using C#

\n

Encrypt your secret using the Sodium.Core package.

\n
var secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n
\n

Example encrypting a secret using Ruby

\n

Encrypt your secret using the rbnacl gem.

\n
require \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n
", + "descriptionHTML": "

Creates or updates a secret for a user's codespace with an encrypted value. Encrypt your secret using\nLibSodium.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must also have Codespaces access to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_user_secrets user permission and codespace_secrets repository permission on all referenced repositories to use this endpoint.

\n

Example encrypting a secret using Node.js

\n

Encrypt your secret using the tweetsodium library.

\n
const sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n
\n

Example encrypting a secret using Python

\n

Encrypt your secret using pynacl with Python 3.

\n
from base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n
\n

Example encrypting a secret using C#

\n

Encrypt your secret using the Sodium.Core package.

\n
var secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n
\n

Example encrypting a secret using Ruby

\n

Encrypt your secret using the rbnacl gem.

\n
require \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n
", "bodyParameters": [ { "type": "string", @@ -32890,7 +33270,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Deletes a secret from a user's codespaces using the secret name. Deleting the secret will remove access from all codespaces that were allowed to access the secret. You must authenticate using an access token with the user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Deletes a secret from a user's codespaces using the secret name. Deleting the secret will remove access from all codespaces that were allowed to access the secret.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_user_secrets user permission to use this endpoint.

", "responses": [ { "httpStatusCode": "204", @@ -32935,7 +33315,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

List the repositories that have been granted the ability to use a user's codespace secret.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

List the repositories that have been granted the ability to use a user's codespace secret.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have read access to the codespaces_user_secrets user permission and write access to the codespace_secrets repository permission on all referenced repositories to use this endpoint.

", "responses": [ { "httpStatusCode": "200", @@ -33033,7 +33413,7 @@ "category": "codespaces", "subcategory": "secrets", "notes": [], - "descriptionHTML": "

Select the repositories that will use a user's codespace secret.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Select the repositories that will use a user's codespace secret.

\n

You must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.

\n

GitHub Apps must have write access to the codespaces_user_secrets user permission and write access to the codespace_secrets repository permission on all referenced repositories to use this endpoint.

", "responses": [ { "httpStatusCode": "204", @@ -33121,7 +33501,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Adds a repository to the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Adds a repository to the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.\nGitHub Apps must have write access to the codespaces_user_secrets user permission and write access to the codespace_secrets repository permission on the referenced repository to use this endpoint.

", "responses": [ { "httpStatusCode": "204", @@ -33195,7 +33575,7 @@ "subcategory": "secrets", "notes": [], "bodyParameters": [], - "descriptionHTML": "

Removes a repository from the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the user or read:user scope to use this endpoint. User must have Codespaces access to use this endpoint.

", + "descriptionHTML": "

Removes a repository from the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the codespace or codespace:secrets scope to use this endpoint. User must have Codespaces access to use this endpoint.\nGitHub Apps must have write access to the codespaces_user_secrets user permission to use this endpoint.

", "responses": [ { "httpStatusCode": "204", diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 312142e442..0e3667fa6c 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -232795,7 +232795,7 @@ "/repos/{owner}/{repo}/codespaces": { "get": { "summary": "List codespaces in a repository for the authenticated user", - "description": "Lists the codespaces associated to a specified repository and the authenticated user.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Lists the codespaces associated to a specified repository and the authenticated user.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -236022,7 +236022,7 @@ }, "post": { "summary": "Create a codespace in a repository", - "description": "Creates a codespace owned by the authenticated user in the specified repository.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Creates a codespace owned by the authenticated user in the specified repository.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -241993,7 +241993,7 @@ "/repos/{owner}/{repo}/codespaces/machines": { "get": { "summary": "List available machine types for a repository", - "description": "List the machine types available for a given repository based on its configuration.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "List the machine types available for a given repository based on its configuration.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_metadata` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -242263,12 +242263,480 @@ }, "x-github": { "githubCloudOnly": false, - "enabledForGitHubApps": false, + "enabledForGitHubApps": true, "category": "codespaces", "subcategory": "machines" } } }, + "/repos/{owner}/{repo}/codespaces/secrets": { + "get": { + "summary": "List repository secrets", + "description": "Lists all secrets available in a repository without revealing their encrypted values. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `secrets` repository permission to use this endpoint.", + "tags": [ + "codespaces" + ], + "operationId": "codespaces/list-repo-secrets", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/codespaces#list-repository-secrets" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "secrets" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "secrets": { + "type": "array", + "items": { + "title": "Codespaces Secret", + "description": "Set repository secrets for GitHub Codespaces.", + "type": "object", + "properties": { + "name": { + "description": "The name of the secret.", + "type": "string", + "examples": [ + "SECRET_TOKEN" + ] + }, + "created_at": { + "type": "string", + "format": "date-time" + }, + "updated_at": { + "type": "string", + "format": "date-time" + } + }, + "required": [ + "name", + "created_at", + "updated_at" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 2, + "secrets": [ + { + "name": "GH_TOKEN", + "created_at": "2019-08-10T14:59:22Z", + "updated_at": "2020-01-10T14:59:22Z" + }, + { + "name": "GIST_ID", + "created_at": "2020-01-10T10:59:22Z", + "updated_at": "2020-01-11T11:59:22Z" + } + ] + } + } + } + } + }, + "headers": { + "Link": { + "example": "; rel=\"next\", ; rel=\"last\"", + "schema": { + "type": "string" + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + } + } + }, + "/repos/{owner}/{repo}/codespaces/secrets/public-key": { + "get": { + "summary": "Get a repository public key", + "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `secrets` repository permission to use this endpoint.", + "tags": [ + "codespaces" + ], + "operationId": "codespaces/get-repo-public-key", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/codespaces#get-a-repository-public-key" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "title": "CodespacesPublicKey", + "description": "The public key used for setting Codespaces secrets.", + "type": "object", + "properties": { + "key_id": { + "description": "The identifier for the key.", + "type": "string", + "examples": [ + "1234567" + ] + }, + "key": { + "description": "The Base64 encoded public key.", + "type": "string", + "examples": [ + "hBT5WZEj8ZoOv6TYJsfWq7MxTEQopZO5/IT3ZCVQPzs=" + ] + }, + "id": { + "type": "integer", + "examples": [ + 2 + ] + }, + "url": { + "type": "string", + "examples": [ + "https://api.github.com/user/keys/2" + ] + }, + "title": { + "type": "string", + "examples": [ + "ssh-rsa AAAAB3NzaC1yc2EAAA" + ] + }, + "created_at": { + "type": "string", + "examples": [ + "2011-01-26T19:01:12Z" + ] + } + }, + "required": [ + "key_id", + "key" + ] + }, + "examples": { + "default": { + "value": { + "key_id": "012345678912345678", + "key": "2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": false, + "category": "codespaces", + "subcategory": "repository-secrets" + } + } + }, + "/repos/{owner}/{repo}/codespaces/secrets/{secret_name}": { + "get": { + "summary": "Get a repository secret", + "description": "Gets a single repository secret without revealing its encrypted value. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `codespaces_secrets` repository permission to use this endpoint.", + "tags": [ + "codespaces" + ], + "operationId": "codespaces/get-repo-secret", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/codespaces#get-a-repository-secret" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "title": "Codespaces Secret", + "description": "Set repository secrets for GitHub Codespaces.", + "type": "object", + "properties": { + "name": { + "description": "The name of the secret.", + "type": "string", + "examples": [ + "SECRET_TOKEN" + ] + }, + "created_at": { + "type": "string", + "format": "date-time" + }, + "updated_at": { + "type": "string", + "format": "date-time" + } + }, + "required": [ + "name", + "created_at", + "updated_at" + ] + }, + "examples": { + "default": { + "value": { + "name": "GH_TOKEN", + "created_at": "2019-08-10T14:59:22Z", + "updated_at": "2020-01-10T14:59:22Z" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + } + }, + "put": { + "summary": "Create or update a repository secret", + "description": "Creates or updates a repository secret with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access\ntoken with the `repo` scope to use this endpoint. GitHub Apps must have the `codespaces_secrets` repository\npermission to use this endpoint.\n\n#### Example of encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example of encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/latest/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n sealed_box = public.SealedBox(public_key)\n encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example of encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example of encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```", + "tags": [ + "codespaces" + ], + "operationId": "codespaces/create-or-update-repo-secret", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/codespaces#create-or-update-a-repository-secret" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "requestBody": { + "required": true, + "content": { + "application/json": { + "schema": { + "type": "object", + "properties": { + "encrypted_value": { + "type": "string", + "description": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/codespaces#get-a-repository-public-key) endpoint.", + "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$" + }, + "key_id": { + "type": "string", + "description": "ID of the key you used to encrypt the secret." + } + } + }, + "example": { + "encrypted_value": "c2VjcmV0", + "key_id": "012345678912345678" + } + } + } + }, + "responses": { + "201": { + "description": "Response when creating a secret", + "content": { + "application/json": { + "schema": { + "type": "object", + "properties": { + }, + "additionalProperties": false + } + } + } + }, + "204": { + "description": "Response when updating a secret" + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + } + }, + "delete": { + "summary": "Delete a repository secret", + "description": "Deletes a secret in a repository using the secret name. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `codespaces_secrets` repository permission to use this endpoint.", + "tags": [ + "codespaces" + ], + "operationId": "codespaces/delete-repo-secret", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/codespaces#delete-a-repository-secret" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "secret_name", + "description": "secret_name parameter", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + } + ], + "responses": { + "204": { + "description": "Response" + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "category": "codespaces", + "subcategory": "repository-secrets" + } + } + }, "/repos/{owner}/{repo}/collaborators": { "get": { "summary": "List repository collaborators", @@ -400171,7 +400639,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/codespaces": { "post": { "summary": "Create a codespace from a pull request", - "description": "Creates a codespace owned by the authenticated user for the specified pull request.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Creates a codespace owned by the authenticated user for the specified pull request.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -479786,7 +480254,7 @@ "/user/codespaces": { "get": { "summary": "List codespaces for the authenticated user", - "description": "Lists the authenticated user's codespaces.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Lists the authenticated user's codespaces.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -483153,7 +483621,7 @@ }, "post": { "summary": "Create a codespace for the authenticated user", - "description": "Creates a new codespace, owned by the authenticated user.\n\nThis endpoint requires either a `repository_id` OR a `pull_request` but not both.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Creates a new codespace, owned by the authenticated user.\n\nThis endpoint requires either a `repository_id` OR a `pull_request` but not both.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -489157,7 +489625,7 @@ "/user/codespaces/secrets": { "get": { "summary": "List secrets for the authenticated user", - "description": "Lists all secrets available for a user's Codespaces without revealing their\nencrypted values.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Lists all secrets available for a user's Codespaces without revealing their\nencrypted values.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_user_secrets` user permission to use this endpoint.", "tags": [ "codespaces" ], @@ -489524,7 +489992,7 @@ "/user/codespaces/secrets/public-key": { "get": { "summary": "Get public key for the authenticated user", - "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with one of the 'read:user' or 'user' scopes in their personal access token. User must have Codespaces access to use this endpoint.", + "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_user_secrets` user permission to use this endpoint.", "tags": [ "codespaces" ], @@ -489586,7 +490054,7 @@ "/user/codespaces/secrets/{secret_name}": { "get": { "summary": "Get a secret for the authenticated user", - "description": "Gets a secret available to a user's codespaces without revealing its encrypted value.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Gets a secret available to a user's codespaces without revealing its encrypted value.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_user_secrets` user permission to use this endpoint.", "tags": [ "codespaces" ], @@ -489680,7 +490148,7 @@ }, "put": { "summary": "Create or update a secret for the authenticated user", - "description": "Creates or updates a secret for a user's codespace with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access token with the `user` scope to use this endpoint. User must also have Codespaces access to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/latest/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n sealed_box = public.SealedBox(public_key)\n encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```", + "description": "Creates or updates a secret for a user's codespace with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages).\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must also have Codespaces access to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_user_secrets` user permission and `codespace_secrets` repository permission on all referenced repositories to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/latest/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n sealed_box = public.SealedBox(public_key)\n encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```", "tags": [ "codespaces" ], @@ -489867,7 +490335,7 @@ }, "delete": { "summary": "Delete a secret for the authenticated user", - "description": "Deletes a secret from a user's codespaces using the secret name. Deleting the secret will remove access from all codespaces that were allowed to access the secret. You must authenticate using an access token with the `user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Deletes a secret from a user's codespaces using the secret name. Deleting the secret will remove access from all codespaces that were allowed to access the secret.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_user_secrets` user permission to use this endpoint.", "tags": [ "codespaces" ], @@ -489903,7 +490371,7 @@ "/user/codespaces/secrets/{secret_name}/repositories": { "get": { "summary": "List selected repositories for a user secret", - "description": "List the repositories that have been granted the ability to use a user's codespace secret.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "List the repositories that have been granted the ability to use a user's codespace secret.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_user_secrets` user permission and write access to the `codespace_secrets` repository permission on all referenced repositories to use this endpoint.", "tags": [ "codespaces" ], @@ -492419,7 +492887,7 @@ }, "put": { "summary": "Set selected repositories for a user secret", - "description": "Select the repositories that will use a user's codespace secret.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Select the repositories that will use a user's codespace secret.\n\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_user_secrets` user permission and write access to the `codespace_secrets` repository permission on all referenced repositories to use this endpoint.", "tags": [ "codespaces" ], @@ -492587,7 +493055,7 @@ "/user/codespaces/secrets/{secret_name}/repositories/{repository_id}": { "put": { "summary": "Add a selected repository to a user secret", - "description": "Adds a repository to the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Adds a repository to the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\nGitHub Apps must have write access to the `codespaces_user_secrets` user permission and write access to the `codespace_secrets` repository permission on the referenced repository to use this endpoint.", "tags": [ "codespaces" ], @@ -492733,7 +493201,7 @@ }, "delete": { "summary": "Remove a selected repository from a user secret", - "description": "Removes a repository from the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the `user` or `read:user` scope to use this endpoint. User must have Codespaces access to use this endpoint.", + "description": "Removes a repository from the selected repositories for a user's codespace secret.\nYou must authenticate using an access token with the `codespace` or `codespace:secrets` scope to use this endpoint. User must have Codespaces access to use this endpoint.\nGitHub Apps must have write access to the `codespaces_user_secrets` user permission to use this endpoint.", "tags": [ "codespaces" ], @@ -492881,7 +493349,7 @@ "/user/codespaces/{codespace_name}": { "get": { "summary": "Get a codespace for the authenticated user", - "description": "Gets information about a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Gets information about a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -495922,7 +496390,7 @@ }, "patch": { "summary": "Update a codespace for the authenticated user", - "description": "Updates a codespace owned by the authenticated user. Currently only the codespace's machine type and recent folders can be modified using this endpoint.\n\nIf you specify a new machine type it will be applied the next time your codespace is started.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Updates a codespace owned by the authenticated user. Currently only the codespace's machine type and recent folders can be modified using this endpoint.\n\nIf you specify a new machine type it will be applied the next time your codespace is started.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -498968,7 +499436,7 @@ }, "delete": { "summary": "Delete a codespace for the authenticated user", - "description": "Deletes a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Deletes a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -499118,7 +499586,7 @@ "/user/codespaces/{codespace_name}/exports": { "post": { "summary": "Export a codespace for the authenticated user", - "description": "Triggers an export of the specified codespace and returns a URL and ID where the status of the export can be monitored.\n\nYou must authenticate using a personal access token with the `codespace` scope to use this endpoint.", + "description": "Triggers an export of the specified codespace and returns a URL and ID where the status of the export can be monitored.\n\nYou must authenticate using a personal access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_lifecycle_admin` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -499417,7 +499885,7 @@ "/user/codespaces/{codespace_name}/exports/{export_id}": { "get": { "summary": "Get details about a codespace export", - "description": "Gets information about an export of a codespace.\n\nYou must authenticate using a personal access token with the `codespace` scope to use this endpoint.", + "description": "Gets information about an export of a codespace.\n\nYou must authenticate using a personal access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_lifecycle_admin` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -499572,7 +500040,7 @@ "/user/codespaces/{codespace_name}/machines": { "get": { "summary": "List machine types for a codespace", - "description": "List the machine types a codespace can transition to use.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "List the machine types a codespace can transition to use.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have read access to the `codespaces_metadata` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -499833,7 +500301,7 @@ "/user/codespaces/{codespace_name}/start": { "post": { "summary": "Start a codespace for the authenticated user", - "description": "Starts a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Starts a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_lifecycle_admin` repository permission to use this endpoint.", "tags": [ "codespaces" ], @@ -502996,7 +503464,7 @@ "/user/codespaces/{codespace_name}/stop": { "post": { "summary": "Stop a codespace for the authenticated user", - "description": "Stops a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.", + "description": "Stops a user's codespace.\n\nYou must authenticate using an access token with the `codespace` scope to use this endpoint.\n\nGitHub Apps must have write access to the `codespaces_lifecycle_admin` repository permission to use this endpoint.", "tags": [ "codespaces" ], diff --git a/tests/rendering/static-assets.js b/tests/rendering/static-assets.js index 915d9b9556..e12f0a1f93 100644 --- a/tests/rendering/static-assets.js +++ b/tests/rendering/static-assets.js @@ -1,7 +1,7 @@ import fs from 'fs' import path from 'path' -import { expect } from '@jest/globals' +import { jest, expect } from '@jest/globals' import { get } from '../helpers/e2etest.js' import { checkCachingHeaders } from '../helpers/caching-headers.js' @@ -14,6 +14,8 @@ function getNextStaticAsset(directory) { } describe('static assets', () => { + jest.setTimeout(60 * 1000) + it('should serve /assets/cb-* with optimal headers', async () => { const res = await get('/assets/cb-1234/images/site/logo.png') expect(res.statusCode).toBe(200) diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index bb025280a4..78d19e3424 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -298,7 +298,7 @@ Organizationの管理タスクをモニタするために、監査ログを使 たとえば、監査ログを使用して、Organization のシークレットへの変更を追跡する `org.update_actions_secret` イベントを追跡できます。 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) -以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)." +以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)" and "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)." {% ifversion fpt or ghec %} ### 環境のイベント @@ -313,9 +313,10 @@ Organizationの管理タスクをモニタするために、監査ログを使 {% ifversion fpt or ghes or ghec %} ### 設定変更のイベント -| アクション | 説明 | -| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.actions_enabled` | リポジトリに対して {% data variables.product.prodname_actions %} が有効化されたときにトリガーされます。 UI を使用して表示できます。 このイベントは、REST API を使用して Audit log にアクセスした場合には表示されません。 詳しい情報については、「[REST API を使用する](#using-the-rest-api)」を参照してください。 | +| アクション | 説明 | +| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.actions_enabled` | リポジトリに対して {% data variables.product.prodname_actions %} が有効化されたときにトリガーされます。 UI を使用して表示できます。 このイベントは、REST API を使用して Audit log にアクセスした場合には表示されません。 詳しい情報については、「[REST API を使用する](#using-the-rest-api)」を参照してください。 | +| `repo.update_actions_access_settings` | Triggered when the setting to control how your repository is used by {% data variables.product.prodname_actions %} workflows in other repositories is changed. | {% endif %} ### シークレット管理のイベント diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index 9cb3ba1b65..6d88cf3891 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -45,9 +45,9 @@ Data for GitHub's [trending page][] is calculated into daily, weekly, and monthl {% data variables.product.product_name %} keeps a running log of audited actions that you can query. -By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)." +By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)." -For more information on audit logging in general, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." For a full list of audited actions, see "[Audited actions](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)." +For more information on audit logging in general, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." For a full list of audited actions, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." ## Reports diff --git a/translations/ja-JP/content/admin/enterprise-management/index.md b/translations/ja-JP/content/admin/enterprise-management/index.md index ac69a9ccde..319ad9d4ba 100644 --- a/translations/ja-JP/content/admin/enterprise-management/index.md +++ b/translations/ja-JP/content/admin/enterprise-management/index.md @@ -13,6 +13,6 @@ children: - /configuring-clustering - /configuring-high-availability - /caching-repositories -shortTitle: 'Monitor, manage & update' +shortTitle: 'Monitor, manage, and update your appliance' --- diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md new file mode 100644 index 0000000000..2ee79fbfe8 --- /dev/null +++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md @@ -0,0 +1,62 @@ +--- +title: About system logs +intro: '{% data variables.product.product_name %} keeps error and message logs for system events. Logs are useful for identifying user, application and system-level actions and exceptions.' +versions: + ghes: '*' +type: overview +topics: + - Auditing + - Enterprise + - Logging + - Security +--- + +## System logs + +By default, system logs for {% data variables.product.product_name %} are automatically rotated every 24 hours and are retained for seven days. System logs include system-level events, application logs, and Git events data. As log files are often being written to and can be large in size, it may be beneficial to extract and parse relevant log entries on a host separate to your {% data variables.product.prodname_ghe_server %} instance. + +You can forward system logs to a third-party system or server for longer retention. 詳しい情報については、「[ログの転送](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)」を参照してください。 + +In addition to reviewing your system logs, you can monitor activity in your enterprise in other ways, such as viewing audit logs, push logs and managing global webhooks. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)." + +## Types of logs + +Listed below are the main logs used by the {% data variables.product.product_name %} appliance and their functions: + +| パス | Description​ | +| -------------------------------- | ----------------------------------------------------------------------------- | +| `/var/log/github/audit.log` | Audited user, repository and system events. | +| `/var/log/github/unicorn.log` | API and web interface traffic. | +| `/var/log/github/exceptions.log` | Application-level errors. | +| `/var/log/haproxy.log` | All IP traffic reaching the appliance. | +| `/var/log/hookshot/resqued.log` | Webhook delivery and failures. | +| `/var/log/github/auth.log` | Authentication requests, whether through built in, LDAP, CAS or SAML methods. | +| `/var/log/github/gitauth.log` | All Git authentication requests. | + +Git activity and authentication requests are processed by the `babeld` service. + +Several {% data variables.product.product_name %} services, such as the `babeld` service, are containerized. Containerized logs are written to the `systemd journal`, and can be queried at any time using the `journalctl` command. + +## Audited system events + +All entries from the `audit.log` file use and can be filtered with the `github_audit` keyword. + +たとえば、次のエントリは新規リポジトリが作成されたことを示しています。 + +``` +Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"} +``` + +次の例は、コミットがリポジトリにプッシュされたことを示しています。 + +``` +Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" } +``` + +## Support Bundle + +The support bundle includes system logs and all audit information is logged to the `audit.log` file in the `github-logs` directory. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/support/contacting-github-support/providing-data-to-github-support)." + +## 参考リンク + +- [Linux man page for the `journalctl` command](http://man7.org/linux/man-pages/man1/journalctl.1.html) diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md index 756b8149e1..6bd7a56b60 100644 --- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md +++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md @@ -16,6 +16,7 @@ children: - /setting-up-external-monitoring - /configuring-collectd - /monitoring-using-snmp + - /about-system-logs - /generating-a-health-check-for-your-enterprise --- diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index dcc67d6f38..1cdcda101a 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions 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 "[Using OpenID Connect with reusable workflows](/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 audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% 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 audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[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)" and "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."{% else %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %} ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md index 346526ae98..45ab5bf19d 100644 --- a/translations/ja-JP/content/admin/guides.md +++ b/translations/ja-JP/content/admin/guides.md @@ -31,7 +31,6 @@ includeGuides: - /admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users - - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta @@ -75,6 +74,7 @@ includeGuides: - /admin/enterprise-management/setting-up-external-monitoring - /admin/enterprise-management/upgrade-requirements - /admin/enterprise-management/upgrading-github-enterprise-server + - /admin/enterprise-management/monitoring-your-appliance/about-system-logs - /admin/enterprise-support/about-github-enterprise-support - /admin/github-actions/about-using-actions-in-your-enterprise - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled @@ -103,7 +103,6 @@ includeGuides: - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance - /admin/user-management/about-migrations - /admin/user-management/adding-people-to-teams - - /admin/user-management/audited-actions - /admin/user-management/auditing-ssh-keys - /admin/user-management/auditing-users-across-your-enterprise - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise @@ -115,11 +114,19 @@ includeGuides: - /admin/user-management/exporting-migration-data-from-your-enterprise - /admin/user-management/importing-data-from-third-party-version-control-systems - /admin/user-management/managing-dormant-users - - /admin/user-management/managing-global-webhooks + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise + - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard + - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs + - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding + - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise - - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account - - /admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise - /admin/user-management/managing-projects-using-jira - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise - /admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise @@ -128,7 +135,6 @@ includeGuides: - /admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise - /admin/user-management/migrating-data-to-your-enterprise - /admin/user-management/migrating-to-internal-repositories - - /admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization - /admin/user-management/preparing-to-migrate-data-to-your-enterprise - /admin/user-management/preventing-users-from-creating-organizations diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md deleted file mode 100644 index 13ea0381ed..0000000000 --- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Auditing activity in your enterprise -shortTitle: Auditing activity -intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' -permissions: Enterprise owners can access the audit log. -product: '{% data reusables.gated-features.emus %}' -redirect_from: - - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise - - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise -versions: - ghec: '*' -topics: - - Accounts - - Enterprise ---- - -## About the audit log - -The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. - -- アクションが実行された Organization -- アクションを実行したユーザ -- アクションの対象となったリポジトリ -- 実行されたアクション -- アクションが実行された国 -- アクションが発生した日時 - -## Audit log にアクセスする - -You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} -1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md index 880796da13..6889c03c76 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md @@ -17,6 +17,5 @@ children: - /configuring-scim-provisioning-for-enterprise-managed-users - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta - /managing-team-memberships-with-identity-provider-groups - - /auditing-activity-in-your-enterprise --- diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index 0779c3cbb1..db889b0de8 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -100,8 +100,8 @@ featuredLinks: - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}' - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}' - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}' - - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}' - - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}' + - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise{% endif %}' + - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}' - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}' - /admin/configuration/configuring-github-connect/managing-github-connect - /admin/enterprise-support/about-github-enterprise-support @@ -125,6 +125,7 @@ children: - /identity-and-access-management - /user-management - /policies + - /monitoring-activity-in-your-enterprise - /enterprise-management - /github-actions - /packages diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md similarity index 93% rename from translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md rename to translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md index 47e1ac0ce5..28b6b45b61 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /enterprise/admin/installation/activity-dashboard - /enterprise/admin/user-management/activity-dashboard - /admin/user-management/activity-dashboard + - /admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard versions: ghes: '*' ghae: '*' diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md new file mode 100644 index 0000000000..d88073aa78 --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md @@ -0,0 +1,17 @@ +--- +title: Exploring user activity in your enterprise +intro: 'You can view user and system activity by leveraging dashboards, webhooks and log forwarding.' +versions: + ghec: '*' + ghes: '*' + ghae: '*' +topics: + - Enterprise +children: + - /activity-dashboard + - /viewing-push-logs + - /log-forwarding + - /managing-global-webhooks +shortTitle: Explore user activity +--- + diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md similarity index 98% rename from translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md rename to translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md index 496032645c..54501b522d 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md @@ -7,6 +7,7 @@ redirect_from: - /enterprise/admin/enterprise-management/log-forwarding - /admin/enterprise-management/log-forwarding - /admin/user-management/log-forwarding + - /admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding versions: ghes: '*' ghae: '*' diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md new file mode 100644 index 0000000000..750407afce --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md @@ -0,0 +1,100 @@ +--- +title: Managing global webhooks +shortTitle: Manage global webhooks +intro: You can configure global webhooks to notify external web servers when events occur within your enterprise. +permissions: Enterprise owners can manage global webhooks for an enterprise account. +redirect_from: + - /enterprise/admin/user-management/about-global-webhooks + - /enterprise/admin/user-management/managing-global-webhooks + - /admin/user-management/managing-global-webhooks + - /admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks + - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account + - /articles/configuring-webhooks-for-organization-events-in-your-business-account + - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account + - /admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Enterprise + - Webhooks +--- + +## About global webhooks + +You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)." + +For example, you can configure {% data variables.product.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook. + +![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) + +{% data reusables.enterprise_user_management.manage-global-webhooks-api %} + +## Adding a global webhook + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Click **Add webhook**. + ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) +6. Type the URL where you'd like to receive payloads. + ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) +7. Optionally, use the **Content type** drop-down menu, and click a payload format. + ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) +8. Optionally, in the **Secret** field, type a string to use as a `secret` key. + ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) +9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**. + ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) + + {% warning %} + + **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification. + + {% endwarning %} +10. Decide if you'd like this webhook to trigger for every event or for selected events. + ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) + - For every event, select **Send me everything**. + - To choose specific events, select **Let me select individual events**. +11. If you chose to select individual events, select the events that will trigger the webhook. + {% ifversion ghec %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) + {% elsif ghes or ghae %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) + {% endif %} +12. Confirm that the **Active** checkbox is selected. + ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png) +13. Click **Add webhook**. + +## Editing a global webhook + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to edit, click **Edit**. + ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) +6. Update the webhook's settings. +7. Click **Update webhook**. + +## Deleting a global webhook + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to delete, click **Delete**. + ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) +6. Read the information about deleting a webhook, then click **Yes, delete webhook**. + ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) + +## Viewing recent deliveries and responses + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. In the list of webhooks, click the webhook for which you'd like to see deliveries. + ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) +6. Under "Recent deliveries", click a delivery to view details. + ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md similarity index 92% rename from translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md rename to translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md index 2a27d30993..d966672e08 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md @@ -6,6 +6,7 @@ redirect_from: - /enterprise/admin/installation/viewing-push-logs - /enterprise/admin/user-management/viewing-push-logs - /admin/user-management/viewing-push-logs + - /admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs versions: ghes: '*' ghae: '*' @@ -41,6 +42,6 @@ topics: {% data reusables.enterprise_installation.ssh-into-instance %} 1. 適切な Git リポジトリで Audit log ファイルを開いてください。 ```shell - ghe-repo コードオーナー/リポジトリ -c "less audit_log" + ghe-repo owner/repository -c "cat audit_log" ``` {% endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md new file mode 100644 index 0000000000..cc0e93de2b --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md @@ -0,0 +1,17 @@ +--- +title: Enterprise でアクティビティを監視する +intro: 'You can view user and system activity by leveraging audit logs{% ifversion ghes or ghae %}, push logs, dashboards, webhooks, and log forwarding{% else %}and webhooks{% endif %}.' +redirect_from: + - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance +versions: + ghec: '*' + ghes: '*' + ghae: '*' +topics: + - Enterprise +children: + - /reviewing-audit-logs-for-your-enterprise + - /exploring-user-activity +shortTitle: Monitor activity +--- + diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md new file mode 100644 index 0000000000..aedd8d562b --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -0,0 +1,61 @@ +--- +title: About the audit log for your enterprise +intro: 'To support debugging and internal and external compliance, {% data variables.product.product_name %} provides logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events.' +shortTitle: About audit logs +redirect_from: + - /enterprise/admin/articles/audit-logging + - /enterprise/admin/installation/audit-logging + - /enterprise/admin/user-management/audit-logging + - /admin/user-management/audit-logging + - /admin/user-management/monitoring-activity-in-your-enterprise/audit-logging + - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise + - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise + - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise +versions: + ghes: '*' + ghae: '*' + ghec: '*' +type: overview +topics: + - Auditing + - Enterprise + - Logging + - Security +--- + +## About audit logs + +{% data reusables.audit_log.retention-periods %} + +{% data reusables.audit_log.audit-log-search-list-info-about-action %} + +In addition to viewing your audit log, you can monitor activity in your enterprise in other ways, such as {% ifversion ghes or ghae %}viewing push logs and {% endif %}managing global webhooks. For more information, see "[Exploring user activity in your enterprise](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity)." + +## Using your audit logs + +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 "[Accessing the audit log for your enterprise](/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 "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}. +{%- ifversion ghec %} +- You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. 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)." +{%- else %} +- You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. 詳しい情報については、「[ログの転送](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)」を参照してください。 +{%- endif %} +{%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} +- You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." +{%- endif %} + +For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." + +{% ifversion ghec %} +## Git events + +Git events data, such as cloning, fetching, and pushing is logged. 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)." + +{% endif %} + +## 参考リンク +- 「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)」 +{%- ifversion ghes %} +- "[About system logs](/admin/enterprise-management/monitoring-your-appliance/about-system-logs)" +{%- endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md new file mode 100644 index 0000000000..0a0be317ee --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md @@ -0,0 +1,27 @@ +--- +title: Accessing the audit log for your enterprise +intro: You can view aggregated actions from all of the organizations owned by an enterprise account in the enterprise's audit log. +shortTitle: Access audit logs +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can access the audit log.' +redirect_from: + - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account + - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account + - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: how_to +topics: + - Auditing + - Enterprise + - Logging +--- + +{% data reusables.audit_log.retention-periods %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md new file mode 100644 index 0000000000..9bdcb6beb5 --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -0,0 +1,1210 @@ +--- +title: Audit log events for your enterprise +intro: Learn about audit log events recorded for your enterprise. +shortTitle: Audit log events +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.' +miniTocMaxHeadingLevel: 4 +redirect_from: + - /enterprise/admin/articles/audited-actions + - /enterprise/admin/installation/audited-actions + - /enterprise/admin/user-management/audited-actions + - /admin/user-management/audited-actions + - /admin/user-management/monitoring-activity-in-your-enterprise/audited-actions +versions: + ghec: '*' + ghes: '*' + ghae: '*' +type: reference +topics: + - Auditing + - Enterprise + - Logging + - Security +--- + +{%- ifversion fpt or ghec %} +### `account` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `account.billing_plan_change` | An organization's billing cycle changed. 詳しい情報については「[支払いサイクルの期間の変更](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)」を参照してください。 | +| `account.plan_change` | An organization's subscription changed. For more information, see "[About billing for GitHub accounts](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)." | +| `account.pending_plan_change` | An organization owner or billing manager canceled or downgraded a paid subscription. 詳細は「[アップグレードやダウングレードは支払い処理にどのように影響しますか?](/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process)」を参照してください。 | +| `account.pending_subscription_change` | A {% data variables.product.prodname_marketplace %} free trial started or expired. For more information, see "[About billing for GitHub Marketplace](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace)." | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `advisory_credit` カテゴリアクション + +| アクション | 説明 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `advisory_credit.accept` | Someone accepted credit for a security advisory. 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 | +| `advisory_credit.create` | The administrator of a security advisory added someone to the credit section. | +| `advisory_credit.decline` | Someone declined credit for a security advisory. | +| `advisory_credit.destroy` | The administrator of a security advisory removed someone from the credit section. | +{%- endif %} + +### `artifact` category actions + +| アクション | 説明 | +| ------------------ | --------------------------------------------- | +| `artifact.destroy` | A workflow run artifact was manually deleted. | + +{%- ifversion ghec %} +### `audit_log_streaming` category actions + +| アクション | 説明 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | +| `audit_log_streaming.check` | A manual check was performed of the endpoint configured for audit log streaming. | +| `audit_log_streaming.create` | An endpoint was added for audit log streaming. | +| `audit_log_streaming.update` | An endpoint configuration was updated for audit log streaming, such as the stream was paused, enabled, or disabled. | +| `audit_log_streaming.destroy` | An audit log streaming endpoint was deleted. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `billing` カテゴリアクション + +| アクション | 説明 | +| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing.change_billing_type` | An organization changed how it paid for {% data variables.product.prodname_dotcom %}. 詳細は「[支払い方法を追加または編集する](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)」を参照してください。 | +| `billing.change_email` | An organization's billing email address changed. 詳細は「[支払い請求先メールアドレスを設定する](/billing/managing-your-github-billing-settings/setting-your-billing-email)」を参照してください。 | +{%- endif %} + +### `business`カテゴリアクション + +| アクション | 説明 | +| -------------------- | ---------------------------------------------------------------------------------------------------- | +| `business.add_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was added to an enterprise. | +{%- ifversion ghec %} +| `business.add_billing_manager` | A billing manager was added to an enterprise. +{%- endif %} +| `business.add_organization` | An organization was added to an enterprise. +{%- ifversion ghec %} +| `business.add_support_entitlee` | A support entitlement was added to a member of an enterprise. 詳しい情報については「[Enterpriseのサポート資格の管理](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。 +{%- endif %} +{%- ifversion ghes > 3.0 or ghae %} +| `business.advanced_security_policy_update` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} created, updated, or removed a policy for {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_advanced_security %}のポリシーの施行](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)」を参照してください。 +{%- endif %} +{%- ifversion ghec %} +| `business.cancel_admin_invitation` | An invitation for someone to be an owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was canceled. | `business.cancel_billing_manager_invitation` | An invitation for someone to be an billing manager of an enterprise was canceled. +{%- endif %} +{%- ifversion ghes %} +| `business.clear_actions_settings` | An enterprise owner or site administrator cleared {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)." +{%- endif %} +| `business.clear_default_repository_permission` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the base repository permission policy setting for an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)." | `business.clear_members_can_create_repos` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared a restriction on repository creation in organizations in the enterprise. 詳しい情報については、「[Enterprise でのリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。 | `business.create` | An enterprise was created. +{%- ifversion ghec %} +| `business.disable_saml` | SAML single sign-on was disabled for an enterprise. +{%- endif %} +| `business.disable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was disabled. +{%- ifversion ghec %} +| `business.enable_saml` | SAML single sign-on was enabled for an enterprise. +{%- endif %} +| `business.enable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was enabled. +{%- ifversion ghec %} +| `business.enterprise_server_license_download` | A {% data variables.product.prodname_ghe_server %} license was downloaded. | `business.import_license_usage` | License usage information was imported from a {% data variables.product.prodname_ghe_server %} instance to an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. | `business.invite_admin` | An invitation for someone to be an enterprise owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was sent. | `business.invite_billing_manager` | An invitation for someone to be an billing manager of an enterprise was sent. +{%- endif %} +| `business.members_can_update_protected_branches.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unset a policy for whether members of an enterprise can update protected branches on repositories for individual organizations. Organization administrators can choose whether to allow updating protected branches settings. | `business.members_can_update_protected_branches.disable` | The ability for enterprise members to update branch protection rules was disabled. Only enterprise owners can update protected branches. | `business.members_can_update_protected_branches.enable` | The ability for enterprise members to update branch protection rules was enabled. Enterprise owners and members can update protected branches. | `business.remove_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was removed from an enterprise. +{%- ifversion ghes > 3.1 %} +| `business.referrer_override_enable` | An enterprise owner or site administrator enabled the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." | `business.referrer_override_disable` | An enterprise owner or site administrator disabled the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." +{%- endif %} +{%- ifversion ghec %} +| `business.remove_billing_manager` | A billing manager was removed from an enterprise. | `business.remove_member` | A member was removed from an enterprise. +{%- endif %} +| `business.remove_organization` | An organization was removed from an enterprise. +{%- ifversion ghec %} +| `business.remove_support_entitlee` | A support entitlement was removed from a member of an enterprise. 詳しい情報については「[Enterpriseのサポート資格の管理](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。 +{%- endif %} +| `business.rename_slug` | The slug for the enterprise URL was renamed. +{%- ifversion ghec %} +| `business.revoke_external_identity` | The external identity for a member in an enterprise was revoked. | `business.revoke_sso_session` | The SAML single sign-on session for a member in an enterprise was revoked. +{%- endif %} +{%- ifversion ghec %} +| `business.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an enterprise. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_actions %}のポリシーの施行](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)」を参照してください。 +{%- endif %} +| `business.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs was changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)." +{%- ifversion ghec or ghes %} +| `business.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "{% ifversion ghec %}[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}." +{%- endif %} +{%- ifversion ghes %} +| `business.update_actions_settings` | An enterprise owner or site administrator updated {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)." +{%- endif %} +| `business.update_default_repository_permission` | The base repository permission setting was updated for all organizations in an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)." | `business.update_member_repository_creation_permission` | The repository creation setting was updated for an enterprise. For more information, see "[Enforcing a policy for repository creation](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." | `business.update_member_repository_invitation_permission` | The policy setting for enterprise members inviting outside collaborators to repositories was updated. For more information, see "[Enforcing a policy for inviting outside collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)." +{%- ifversion ghec %} +| `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated. +{%- endif %} + +{%- if secret-scanning-audit-log-custom-patterns %} +### `business_secret_scanning_custom_pattern` category actions + +| アクション | 説明 | +| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| | `business_secret_scanning_custom_pattern.create` | An enterprise-level custom pattern is published for secret scanning. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-enterprise-account)." | +| | `business_secret_scanning_custom_pattern.delete` | An enterprise-level custom pattern is removed from secret scanning. | +| | `business_secret_scanning_custom_pattern.update` | Changes to an enterprise-level custom pattern are saved for secret scanning. | +{%- endif %} + +### `checks` category actions + +| アクション | 説明 | +| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `checks.auto_trigger_disabled` | Automatic creation of check suites was disabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." | +| `checks.auto_trigger_enabled` | Automatic creation of check suites was enabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." | +{%- ifversion fpt or ghec %} +| `checks.delete_logs` | Logs in a check suite were deleted. +{%- endif %} + +{%- ifversion fpt or ghec %} +### `codespaces` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `codespaces.connect` | A codespace was started. | +| `codespaces.create` | A user [created a codespace](/github/developing-online-with-codespaces/creating-a-codespace). | +| `codespaces.destroy` | A user [deleted a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). | +| `codespaces.allow_permissions` | A codespace using custom permissions from its `devcontainer.json` file was launched. | +| `codespaces.attempted_to_create_from_prebuild` | An attempt to create a codespace from a prebuild was made. | +| `codespaces.create_an_org_secret` | A user created an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) | +| `codespaces.update_an_org_secret` | A user updated an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | +| `codespaces.remove_an_org_secret` | A user removed an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | +| `codespaces.manage_access_and_security` | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `commit_comment` category actions + +| アクション | 説明 | +| ------------------------ | ----------------------------- | +| `commit_comment.destroy` | A commit comment was deleted. | +| `commit_comment.update` | A commit comment was updated. | +{%- endif %} + +{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +### `dependabot_alerts` カテゴリアクション + +| アクション | 説明 | +| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dependabot_alerts.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependabot_alerts.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. | + +### `dependabot_alerts_new_repos` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dependabot_alerts_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependabot_alerts_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. | + +### `dependabot_repository_access`category actions + +| アクション | 説明 | +| --------------------------------------------------- | ----------------------------------------------------------------------------------------------- | +| `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated. | +{%- endif %} + +{%- ifversion fpt or ghec or ghes > 3.2 %} +### `dependabot_security_updates` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dependabot_security_updates.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependabot_security_updates.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. | + +### `dependabot_security_updates_new_repos` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dependabot_security_updates_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | +{%- endif %} + +{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +### `dependency_graph` カテゴリアクション + +| アクション | 説明 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dependency_graph.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all existing repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependency_graph.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all existing repositories. | + +### `dependency_graph_new_repos` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `dependency_graph_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all new repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | +| `dependency_graph_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all new repositories. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `discussion` category actions + +| アクション | 説明 | +| -------------------- | ------------------------------ | +| `discussion.destroy` | A team discussion was deleted. | + +### `discussion_comment` category actions + +| アクション | 説明 | +| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `discussion_comment.destroy` | A [comment on a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment). | +| `discussion_comment.update` | A [comment on a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment). | + +### `discussion_post` カテゴリアクション + +| アクション | 説明 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `discussion_post.destroy` | A [team discussion post was deleted](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion). | +| `discussion_post.update` | A [team discussion post was edited](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion). | + +### `discussion_post_reply` カテゴリアクション + +| アクション | 説明 | +| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| `discussion_post_reply.destroy` | A [reply to a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment). | +| `discussion_post_reply.update` | A [reply to a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment). | +{%- endif %} + +{%- ifversion ghec or ghes %} +### `dotcom_connection` category actions + +| アクション | 説明 | +| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `dotcom_connection.create` | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was created. | +| `dotcom_connection.destroy` | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was deleted. | +| `dotcom_connection.token_updated` | The {% data variables.product.prodname_github_connect %} connection token for {% data variables.product.prodname_dotcom_the_website %} was updated. | +| `dotcom_connection.upload_license_usage` | {% data variables.product.prodname_ghe_server %} license usage was manually uploaded to {% data variables.product.prodname_ghe_cloud %}. | +| `dotcom_connection.upload_usage_metrics` | {% data variables.product.prodname_ghe_server %} usage metrics were uploaded to {% data variables.product.prodname_dotcom_the_website %}. | +{%- endif %} + +### `enterprise` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.config.disable_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled anonymous Git read access for repositories in the enterprise. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。 | +| `enterprise.config.enable_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled anonymous Git read access for repositories in the enterprise. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。 | +| `enterprise.config.lock_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} locked anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。 | +| `enterprise.config.unlock_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unlocked anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。 | +| `enterprise.register_self_hosted_runner` | A new {% data variables.product.prodname_actions %} self-hosted runner was registered. 詳しい情報については、「[リポジトリにセルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)」を参照してください。 | +| `enterprise.remove_self_hosted_runner` | A {% data variables.product.prodname_actions %} self-hosted runner was removed. 詳しい情報については、「[リポジトリからランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)」を参照してください。 | +| `enterprise.runner_group_created` | A {% data variables.product.prodname_actions %} self-hosted runner group was created. 詳しい情報については、「[Organization のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)」を参照してください。 | +| `enterprise.runner_group_removed` | A {% data variables.product.prodname_actions %} self-hosted runner group was removed. 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 | +| `enterprise.runner_group_renamed` | A {% data variables.product.prodname_actions %} self-hosted runner group was renamed. 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | +| `enterprise.runner_group_updated` | The configuration of a {% data variables.product.prodname_actions %} self-hosted runner group was changed. 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | +| `enterprise.runner_group_runner_removed` | The REST API was used to remove a {% data variables.product.prodname_actions %} self-hosted runner from a group. 詳しい情報については、「[Organization のグループからセルフホストランナーを削除する](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)」を参照してください。 | +| `enterprise.runner_group_runners_added` | A {% data variables.product.prodname_actions %} self-hosted runner was added to a group. 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 | +| `enterprise.runner_group_runners_updated` | A {% data variables.product.prodname_actions %} runner group's list of members was updated. 詳しい情報については「[Organizationのグループ内にセルフホストランナーをセットする](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。 | +{%- ifversion ghec %} +| `enterprise.runner_group_visiblity_updated` | The visibility of a {% data variables.product.prodname_actions %} self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)." +{%- endif %} +{%- ifversion ghec or ghes > 3.1 or ghae %} +| `enterprise.self_hosted_runner_online` | The {% data variables.product.prodname_actions %} runner application was started. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 | `enterprise.self_hosted_runner_offline` | The {% data variables.product.prodname_actions %} runner application was stopped. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 +{%- endif %} +{%- ifversion ghec or ghes %} +| `enterprise.self_hosted_runner_updated` | The {% data variables.product.prodname_actions %} runner application was updated. REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。 +{%- endif %} + +{%- ifversion ghec %} +### `enterprise_domain` category actions + +| アクション | 説明 | +| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise_domain.approve` | An enterprise domain was approved for an enterprise. For more information, see "[Approving a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#approving-a-domain-for-your-enterprise-account)." | +| `enterprise_domain.create` | An enterprise domain was added to an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." | +| `enterprise_domain.destroy` | An enterprise domain was removed from an enterprise. For more information, see "[Removing an approved or verified domain](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#removing-an-approved-or-verified-domain)." | +| `enterprise_domain.verify` | An enterprise domain was verified for an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." | + +### `enterprise_installation` category actions + +| アクション | 説明 | +| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise_installation.create` | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was created. | +| `enterprise_installation.destroy` | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was deleted. | +| `enterprise_installation.token_updated` | The token belonging to {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was updated. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `environment` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `environment.add_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was created via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | +| `environment.create_actions_secret` | A secret was created for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | +| `environment.delete` | An environment was deleted via the API. For more information, see "[Deleting an environment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment)." | +| `environment.remove_actions_secret` | A secret was deleted for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | +| `environment.remove_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was deleted via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | +| `environment.update_actions_secret` | A secret was updated for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)." | +| `environment.update_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was updated via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." | +{%- endif %} + +{%- ifversion ghae %} +### `external_group`カテゴリアクション + +| アクション | 説明 | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `external_group.delete` | An Okta group was deleted. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.link` | An Okta group was mapped to a {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.provision` | An Okta group was mapped to a team on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.unlink` | An Okta group was unmapped from a {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_group.update` | An Okta group's settings were updated. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | + +### `external_identity`カテゴリアクション +| アクション | 説明 | +| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `external_identity.deprovision` | A user was removed from an Okta group and was subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_identity.provision` | An Okta user was added to an Okta group and was subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +| `external_identity.update` | An Okta user's settings were updated. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." | +{%- endif %} + +### `git` カテゴリアクション + +| アクション | 説明 | +| ----------- | --------------------------------------- | +| `git.clone` | A repository was cloned. | +| `git.fetch` | Changes were fetched from a repository. | +| `git.push` | Changes were pushed to a repository. | + +### `hook` カテゴリアクション + +| アクション | 説明 | +| ----- | -- | +| | | +{%- ifversion ghes or ghae %} +| `hook.active_changed` | A hook's active status was updated. +{%- endif %} +| `hook.config_changed` | A hook's configuration was changed. | `hook.create` | A new hook was added. | `hook.destroy` | A hook was deleted. | `hook.events_changed` | A hook's configured events were changed. + +### `integration` category actions + +| アクション | 説明 | +| ---------------------------------- | ---------------------------------------------------------------------------------------- | +| `integration.create` | An integration was created. | +| `integration.destroy` | An integration was deleted. | +| `integration.manager_added` | A member of an enterprise or organization was added as an integration manager. | +| `integration.manager_removed` | A member of an enterprise or organization was removed from being an integration manager. | +| `integration.transfer` | Ownership of an integration was transferred to another user or organization. | +| `integration.remove_client_secret` | A client secret for an integration was removed. | +| `integration.revoke_all_tokens` | All user tokens for an integration were requested to be revoked. | +| `integration.revoke_tokens` | Token(s) for an integration were revoked. | + +### `integration_installation`category actions + +| アクション | 説明 | +| ------------------------------------------------ | ----------------------------------------------- | +| `integration_installation.contact_email_changed` | A contact email for an integration was changed. | +| `integration_installation.create` | An integration was installed. | +| `integration_installation.destroy` | An integration was uninstalled. | +| `integration_installation.repositories_added` | Repositories were added to an integration. | +| `integration_installation.repositories_removed` | Repositories were removed from an integration. | +{%- ifversion fpt or ghec %} +| `integration_installation.suspend` | An integration was suspended. | `integration_installation.unsuspend` | An integration was unsuspended. +{%- endif %} +| `integration_installation.version_updated` | Permissions for an integration were updated. + +### `integration_installation_request` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `integration_installation_request.create` | An member requested that an owner install an integration for use in an enterprise or organization. | +| `integration_installation_request.close` | A request to install an integration for use in an enterprise or organization was either approved or denied by an owner, or canceled by the member who opened the request. | + +{%- ifversion ghec or ghae %} +### `ip_allow_list`カテゴリアクション + +| アクション | 説明 | +| ------------------------------------------ | --------------------------------------------------------------------------------------- | +| `ip_allow_list.enable` | IP 許可リストが有効化されました。 | +| `ip_allow_list.enable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが有効化されました。 | +| `ip_allow_list.disable` | IP 許可リストが無効化されました。 | +| `ip_allow_list.disable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが無効化されました。 | + +### `ip_allow_list_entry`カテゴリアクション + +| アクション | 説明 | +| ----------------------------- | --------------------------- | +| `ip_allow_list_entry.create` | IP アドレスが IP 許可リストに追加されました。 | +| `ip_allow_list_entry.update` | IP アドレスまたはその説明が変更されました。 | +| `ip_allow_list_entry.destroy` | IP アドレスが IP 許可リストから削除されました。 | +{%- endif %} + +### `issue` カテゴリアクション + +| アクション | 説明 | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `issue.destroy` | Issue がリポジトリから削除されました。 詳しい情報については、「[>Issue を削除する](/issues/tracking-your-work-with-issues/deleting-an-issue)」を参照してください。 | +| `issue.pinned` | An issue was pinned to a repository. 詳細は「[Issue をリポジトリにピン止めする](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)」を参照してください。 | +| `issue.transfer` | An issue was transferred to another repository. 詳細は「[他のリポジトリへ Issue を移譲する](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)」を参照してください。 | +| `issue.unpinned` | An issue was unpinned from a repository. 詳細は「[Issue をリポジトリにピン止めする](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)」を参照してください。 | + +### `issue_comment` category actions + +| アクション | 説明 | +| ------------------------ | ------------------------------------------------------ | +| `issue_comment.destroy` | A comment on an issue was deleted from the repository. | +| `issue_comment.pinned` | A comment on an issue was pinned to a repository. | +| `issue_comment.unpinned` | A comment on an issue was unpinned from a repository. | +| `issue_comment.update` | Issue （最初以外）のコメントが変更されました。 | + +### `issues` category actions + +| アクション | 説明 | +| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `issues.deletes_disabled` | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | +| `issues.deletes_enabled` | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | +| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." | + +{%- ifversion fpt or ghec %} +### `marketplace_agreement_signature` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| `marketplace_agreement_signature.create` | A user signed the {% data variables.product.prodname_marketplace %} Developer Agreement on behalf of an organization. | + +### `marketplace_listing` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | ----------------------------------------------------------------------------------------------------- | +| `marketplace_listing.approve` | A listing was approved for inclusion in {% data variables.product.prodname_marketplace %}. | +| `marketplace_listing.change_category` | A category for a listing for an app in {% data variables.product.prodname_marketplace %} was changed. | +| `marketplace_listing.create` | A listing for an app in {% data variables.product.prodname_marketplace %} was created. | +| `marketplace_listing.delist` | A listing was removed from {% data variables.product.prodname_marketplace %}. | +| `marketplace_listing.redraft` | A listing was sent back to draft state. | +| `marketplace_listing.reject` | A listing was not accepted for inclusion in {% data variables.product.prodname_marketplace %}. | +{%- endif %} + +### `members_can_create_pages` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| `members_can_create_pages.enable` | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | + +### `members_can_create_private_pages` category actions + +| アクション | 説明 | +| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| `members_can_create_private_pages.enable` | The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | + +### `members_can_create_public_pages` category actions + +| アクション | 説明 | +| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_create_public_pages.disable` | The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | +| `members_can_create_public_pages.enable` | The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | + +{%- ifversion ghec or ghes or ghae %} +### `members_can_delete_repos` category actions + +| アクション | 説明 | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `members_can_delete_repos.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | +| `members_can_delete_repos.disable` | The ability for enterprise members to delete repositories was disabled. Members cannot delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | +| `members_can_delete_repos.enable` | The ability for enterprise members to delete repositories was enabled. Members can delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." | + +### `members_can_view_dependency_insights` category actions + +| アクション | 説明 | +| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `members_can_view_dependency_insights.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for viewing dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %} +| `members_can_view_dependency_insights.disable` | The ability for enterprise members to view dependency insights was disabled. Members cannot view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %} +| `members_can_view_dependency_insights.enable` | The ability for enterprise members to view dependency insights was enabled. Members can view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %} + +### `migration` category actions + +| アクション | 説明 | +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `migration.create` | A migration file was created for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. | +| `migration.destroy_file` | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was deleted. | +| `migration.download` | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was downloaded. | +{%- endif %} + +### `oauth_access` カテゴリアクション + +| アクション | 説明 | +| ----- | -- | +| | | + + +`oauth_access.create` | An [OAuth access token][] was generated for a user account. 詳しい情報については、「[個人アクセストークンを作成する](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 `oauth_access.destroy` | An [OAuth access token][] was deleted from a user account. + +### `oauth_application` カテゴリアクション + +| アクション | 説明 | +| --------------------------- | ------------------------------------------------------------------------ | +| `oauth_application.create` | An [OAuth application][] was created for a user or organization account. | +| `oauth_application.destroy` | [OAuth application][]がユーザまたは Organization のアカウントから削除されました。 | +{%- ifversion fpt or ghec %} +| `oauth_application.generate_client_secret` | An [OAuth application][]'s secret key was generated. | `oauth_application.remove_client_secret` | An [OAuth application][]'s secret key was deleted. +{%- endif %} +| `oauth_application.reset_secret` | An [OAuth application][]'s secret key was reset. +{%- ifversion fpt or ghec %} +| `oauth_application.revoke_all_tokens` | All user tokens for an [OAuth application][] were requested to be revoked. +{%- endif %} +| `oauth_application.revoke_tokens` | Token(s) for an [OAuth application][] were revoked. | `oauth_application.transfer` | An [OAuth application][] was transferred from one user or organization account to another. +{%- ifversion ghes or ghae %} +| `oauth_application.unsuspend` | An [OAuth application][] was unsuspended for a user or organization account. +{%- endif %} + +{%- ifversion fpt or ghec %} +### `oauth_authorization` category actions + +| アクション | 説明 | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `oauth_authorization.create` | An authorization for an OAuth application was created. 詳しい情報については、「[OAuth App を認証する](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)」を参照してください。 | +| `oauth_authorization.destroy` | An authorization for an OAuth application was deleted. 詳しい情報については、「[OAuth App を認証する](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)」を参照してください。 | +| `oauth_authorization.update` | An authorization for an OAuth application was updated. 詳しい情報については、「[OAuth App を認証する](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)」を参照してください。 | +{%- endif %} + +### `org` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | +| `org.accept_business_invitation` | An invitation sent to an organization to join an enterprise was accepted. | +| {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %} | | +| `org.add_billing_manager` | A billing manager was added to an organization. | +| {% ifversion fpt or ghec %}For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."{% endif %} | | +| `org.add_member` | A user joined an organization. | +{%- ifversion ghes > 3.0 or ghae or ghec %} +| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in an organization. | `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for all repositories in an organization. | `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in an organization. | `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for all repositories in an organization. | `org.advanced_security_policy_selected_member_disabled` | An enterprise owner prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +{%- endif %} +| `org.async_delete` | A user initiated a background job to delete an organization. +{%- ifversion ghec %} +| `org.audit_log_export` | An organization owner created an export of the organization audit log. エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。 For more information, see "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)." +{%- endif %} +| `org.block_user` | An organization owner blocked a user from accessing the organization's repositories. |{% ifversion fpt or ghec %}For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | An invitation for an organization to join an enterprise was revoked. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | An invitation sent to a user to join an organization was revoked. | `org.clear_actions_settings` | An organization owner cleared {% data variables.product.prodname_actions %} policy settings for an organization. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)." | `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." | `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. 詳細は「[Organization のチーム作成権限を設定する](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)」を参照してください。 | `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. |{% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos` | An organization owner cleared a restriction on repository creation in an organization. 詳しい情報については「[Organization でのリポジトリ作成の制限](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)」を参照してください。 | `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. 詳しい情報については「[外部のコラボレータを追加する権限の設定](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)」を参照してください。 | `org.clear_new_repository_default_branch_setting` | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)." +{%- ifversion fpt or ghec %} +| `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_codespaces %} was granted trusted repository access to all other repositories in an organization. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_codespaces %} trusted repository access to all other repositories in an organization was revoked. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." +{%- endif %} +| `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | The interaction limit for prior contributors only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | The interaction limit for collaborators only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | The interaction limit for prior contributors only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | An invitation for an organization to join an enterprise was confirmed. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | An organization was created. 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 +{%- ifversion fpt or ghec or ghes %} +| `org.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for an organization. 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。 +{%- endif %} +| `org.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for an organization. | `org.delete` | An organization was deleted by a user-initiated background job. | `org.disable_member_team_creation_permission` | An organization owner limited team creation to owners. 詳細は「[Organization のチーム作成権限を設定する](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)」を参照してください。 | `org.disable_reader_discussion_creation_permission` | An organization owner limited discussion creation to users with at least triage permission in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %} +{%- ifversion fpt or ghec %} +| `org.disable_oauth_app_restrictions` | Third-party application access restrictions for an organization were disabled. For more information, see "[Disabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization)." +{%- endif %} +{%- ifversion ghec %} +| `org.disable_saml` | An organization owner disabled SAML single sign-on for an organization. +{%- endif %} +{%- ifversion not ghae %} +| `org.disable_two_factor_requirement` | An organization owner disabled a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization. +{%- endif %} +| `org.display_commenter_full_name_disabled` | An organization owner disabled the display of a commenter's full name in an organization. Members cannot see a comment author's full name. | `org.display_commenter_full_name_enabled` | An organization owner enabled the display of a commenter's full name in an organization. Members can see a comment author's full name. | `org.enable_member_team_creation_permission` | An organization owner allowed members to create teams. 詳細は「[Organization のチーム作成権限を設定する](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)」を参照してください。 | `org.enable_reader_discussion_creation_permission` | An organization owner allowed users with read access to create discussions in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %} +{%- ifversion fpt or ghec %} +| `org.enable_oauth_app_restrictions` | Third-party application access restrictions for an organization were enabled. For more information, see "[Enabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization)." +{%- endif %} +{%- ifversion ghec %} +| `org.enable_saml` | An organization owner [enabled SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization. +{%- endif %} +{%- ifversion not ghae %} +| `org.enable_two_factor_requirement` | An organization owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization. +{%- endif %} +| `org.integration_manager_added` | An organization owner granted a member access to manage all GitHub Apps owned by an organization. | `org.integration_manager_removed` | An organization owner removed access to manage all GitHub Apps owned by an organization from an organization member. | `org.invite_member` | A new user was invited to join an organization. |{% ifversion fpt or ghec %}For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."{% endif %}| | `org.invite_to_business` | An organization was invited to join an enterprise. | `org.members_can_update_protected_branches.clear` | An organization owner unset a policy for whether members of an organization can update protected branches on repositories in an organization. Organization administrators can choose whether to allow updating protected branches settings. | `org.members_can_update_protected_branches.disable` | The ability for enterprise members to update protected branches was disabled. Only enterprise owners can update protected branches. | `org.members_can_update_protected_branches.enable` | The ability for enterprise members to update protected branches was enabled. Members of an organization can update protected branches. +{%- ifversion fpt or ghec %} +| `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization. +{%- endif %} +| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}| | `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。 | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)." +{%- ifversion ghec %} +| `org.revoke_external_identity` | An organization owner revoked a member's linked identity. 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 | `org.revoke_sso_session` | An organization owner revoked a member's SAML session. 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 +{%- endif %} +| `org.runner_group_created` | A self-hosted runner group was created. 詳しい情報については、「[Organization のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)」を参照してください。 | `org.runner_group_removed` | A self-hosted runner group was removed. 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 +{%- ifversion fpt or ghec %} +| `org.runner_group_renamed` | A self-hosted runner group was renamed. 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 +{%- endif %} +| `org.runner_group_updated` | The configuration of a self-hosted runner group was changed. 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | `org.runner_group_runner_removed` | The REST API was used to remove a self-hosted runner from a group. 詳しい情報については、「[Organization のグループからセルフホストランナーを削除する](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)」を参照してください。 | `org.runner_group_runners_added` | A self-hosted runner was added to a group. 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 | `org.runner_group_runners_updated`| A runner group's list of members was updated. 詳しい情報については「[Organizationのグループ内にセルフホストランナーをセットする](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。 +{%- ifversion fpt or ghec %} +| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)." +{%- endif %} +{%- if secret-scanning-audit-log-custom-patterns %} +| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. 詳しい情報については「[Secret scanningでのプッシュの保護](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。 | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} +| `org.self_hosted_runner_online` | The runner application was started. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 | `org.self_hosted_runner_offline` | The runner application was stopped. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 +{%- endif %} +{%- ifversion fpt or ghec or ghes %} +| `org.self_hosted_runner_updated` | The runner application was updated. REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。 +{%- endif %} +{%- ifversion fpt or ghec %} +| `org.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)." +{%- endif %} +| `org.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in an organization was changed. For more information, see "[Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)." +{%- ifversion fpt or ghec or ghes %} +| `org.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)." +{%- endif %} +{%- ifversion ghes %} +| `org.sso_response` | A SAML single sign-on response was generated when a member attempted to authenticate with an organization. +{%- endif %} +{%- ifversion not ghae %} +| `org.transform` | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)." +{%- endif %} +| `org.unblock_user` | An organization owner unblocked a user from an organization. {% ifversion fpt or ghec %}For more information, see "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."{% endif %} +{%- ifversion fpt or ghec or ghes %} +| `org.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. +{%- endif %} +| `org.update_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was updated for an organization. | `org.update_default_repository_permission` | An organization owner changed the default repository permission level for organization members. | `org.update_member` | An organization owner changed a person's role from owner to member or member to owner. | `org.update_member_repository_creation_permission` | An organization owner changed the create repository permission for organization members. | `org.update_member_repository_invitation_permission` | An organization owner changed the policy setting for organization members inviting outside collaborators to repositories. 詳しい情報については「[外部のコラボレータを追加する権限の設定](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)」を参照してください。 | `org.update_new_repository_default_branch_setting` | An organization owner changed the name of the default branch for new repositories in the organization. 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。 +{%- ifversion ghec or ghae %} +| `org.update_saml_provider_settings` | An organization's SAML provider settings were updated. | `org.update_terms_of_service` | An organization changed between the Standard Terms of Service and the Corporate Terms of Service. {% ifversion ghec %}For more information, see "[Upgrading to the Corporate Terms of Service](/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service)."{% endif %} +{%- endif %} + +{%- ifversion ghec or ghes or ghae %} +### `org_credential_authorization` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_credential_authorization.deauthorized` | A member deauthorized credentials for use with SAML single sign-on. | +| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | +| `org_credential_authorization.grant` | A member authorized credentials for use with SAML single sign-on. | +| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | +| `org_credential_authorization.revoke` | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %} +{%- endif %} + +{%- if secret-scanning-audit-log-custom-patterns %} +### `org_secret_scanning_custom_pattern` category actions + +| アクション | 説明 | +| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)」を参照してください。 | +| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)」を参照してください。 | +| `org_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in an organization. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)」を参照してください。 | +{%- endif %} + +### `organization_default_label` category actions + +| アクション | 説明 | +| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `organization_default_label.create` | A default label for repositories in an organization was created. For more information, see "[Creating a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#creating-a-default-label)." | +| `organization_default_label.update` | A default label for repositories in an organization was edited. For more information, see "[Editing a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#editing-a-default-label)." | +| `organization_default_label.destroy` | A default label for repositories in an organization was deleted. For more information, see "[Deleting a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#deleting-a-default-label)." | + +{%- ifversion fpt or ghec or ghes > 3.1 %} +### `organization_domain` category actions + +| アクション | 説明 | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)." | +| `organization_domain.create` | An enterprise domain was added to an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." | +| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)." | +| `organization_domain.verify` | An enterprise domain was verified for an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." | + +### `organization_projects_change` category actions + +| アクション | 説明 | +| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `organization_projects_change.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for organization-wide project boards in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | +| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | +| `organization_projects_change.enable` | Organization projects were enabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." | +{%- endif %} + +{%- ifversion fpt or ghec or ghes > 3.0 or ghae %} +### `packages` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `packages.insecure_hash` | Maven published an insecure hash for a specific package version. | +| `packages.package_deleted` | A package was deleted from an organization.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `packages.package_published` | A package was published or republished to an organization. | +| `packages.package_restored` | An entire package was restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `packages.package_version_deleted` | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `packages.package_version_published` | A specific package version was published or republished to a package. | +| `packages.package_version_restored` | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `packages.part_upload` | A specific package version was partially uploaded to an organization. | +| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy. | +| `packages.version_download` | A specific package version was downloaded. | +| `packages.version_upload` | A specific package version was uploaded. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `pages_protected_domain` category actions + +| アクション | 説明 | +| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pages_protected_domain.create` | A {% data variables.product.prodname_pages %} verified domain was created for an organization or enterprise. 詳しい情報については「[{% data variables.product.prodname_pages %}のカスタムドメインの検証](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)」を参照してください。 | +| `pages_protected_domain.delete` | A {% data variables.product.prodname_pages %} verified domain was deleted from an organization or enterprise. 詳しい情報については「[{% data variables.product.prodname_pages %}のカスタムドメインの検証](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)」を参照してください。 | +| `pages_protected_domain.verify` | A {% data variables.product.prodname_pages %} domain was verified for an organization or enterprise. 詳しい情報については「[{% data variables.product.prodname_pages %}のカスタムドメインの検証](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)」を参照してください。 | + +### `payment_method` カテゴリアクション + +| アクション | 説明 | +| ----------------------- | ---------------------------------------------------------------------------- | +| `payment_method.create` | A new payment method was added, such as a new credit card or PayPal account. | +| `payment_method.remove` | A payment method was removed. | +| `payment_method.update` | An existing payment method was updated. | + +### `prebuild_configuration` category actions + +| アクション | 説明 | +| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | +| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | +| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | +| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | +{%- endif %} + +{%- ifversion ghes %} +### `pre_receive_environment` category actions + +| アクション | 説明 | +| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pre_receive_environment.create` | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| `pre_receive_environment.destroy` | A pre-receive hook environment was deleted. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| `pre_receive_environment.update` | A pre-receive hook environment was updated. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | + +### `pre_receive_hook` category actions + +| アクション | 説明 | +| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pre_receive_hook.create` | A pre-receive hook was created. For more information, see "[Creating pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)." | +| `pre_receive_hook.destroy` | A pre-receive hook was deleted. For more information, see "[Deleting pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)." | +| `pre_receive_hook.enforcement` | A pre-receive hook enforcement setting allowing repository and organization administrators to override the hook configuration was enabled or disabled. For more information, see "[Managing pre-receive hooks on the GitHub Enterprise Server appliance](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)." | +| `pre_receive_hook.rejected_push` | A pre-receive hook rejected a push. | +| `pre_receive_hook.update` | A pre-receive hook was created. For more information, see "[Editing pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)." | +| `pre_receive_hook.warned_push` | A pre-receive hook warned about a push. | +{%- endif %} + +### `private_repository_forking` category actions + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `private_repository_forking.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)." | +| `private_repository_forking.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are never allowed to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)." | +| `private_repository_forking.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are always allowed to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)." | + +{%- ifversion fpt or ghec %} +### `profile_picture` カテゴリアクション + +| アクション | 説明 | +| ------------------------ | ------------------------------ | +| `profile_picture.update` | A profile picture was updated. | +{%- endif %} + +### `project` カテゴリアクション + +| アクション | 説明 | +| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `project.access` | A project board visibility was changed. For more information, see "[Changing project board visibility](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)." | +| `project.close` | A project board was closed. For more information, see "[Closing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)." | +| `project.create` | A project board was created. For more information, see "[Creating a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)." | +| `project.delete` | A project board was deleted. For more information, see "[Deleting a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)." | +| `project.link` | A repository was linked to a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)." | +| `project.open` | A project board was reopened. For more information, see "[Reopening a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)." | +| `project.rename` | A project board was renamed. For more information, see "[Editing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board)." | +| `project.unlink` | A repository was unlinked from a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)." | +| `project.update_org_permission` | The project's base-level permission for all organization members was changed or removed. For more information, see "[Managing access to a project board for organization members](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)." | +| `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)." | +| `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." | + +{%- ifversion fpt or ghec %} +### `project_field` category actions + +| アクション | 説明 | +| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." | +| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." | + +### `project_view` category actions + +| アクション | 説明 | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)." | +| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)." | +{%- endif %} + +### `protected_branch` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------- | ---------------------------------------------------------------------- | +| `protected_branch.create` | Branch protection was enabled on a branch. | +| `protected_branch.destroy` | Branch protection was disabled on a branch. | +| `protected_branch.dismiss_stale_reviews` | Enforcement of dismissing stale pull requests was updated on a branch. | +{%- ifversion ghes %} +| `protected_branch.dismissal_restricted_users_teams` | Enforcement of restricting users and/or teams who can dismiss reviews was updated on a branch. +{%- endif %} +| `protected_branch.policy_override` | A branch protection requirement was overridden by a repository administrator. | `protected_branch.rejected_ref_update` | A branch update attempt was rejected. | `protected_branch.required_status_override` | The required status checks branch protection requirement was overridden by a repository administrator. | `protected_branch.review_policy_and_required_status_override` | The required reviews and required status checks branch protection requirements were overridden by a repository administrator. | `protected_branch.review_policy_override` | The required reviews branch protection requirement was overridden by a repository administrator. | `protected_branch.update_admin_enforced` | Branch protection was enforced for repository administrators. +{%- ifversion ghes %} +| `protected_branch.update_allow_deletions_enforcement_level` | Enforcement of allowing users with push access to delete matching branches was updated on a branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | Enforcement of allowing force pushes for all users with push access was updated on a branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch. +{%- endif %} +| `protected_branch.update_pull_request_reviews_enforcement_level` | Enforcement of required pull request reviews was updated on a branch. `0`（無効化）、`1`（非管理者）、`2`（全員）のいずれか。 | `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review was updated on a branch. | `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch. | `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch. + +### `public_key` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------- | ------------------------------------------------------------------------------------------------ | +| `public_key.create` | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository. | +| `public_key.delete` | An SSH key was removed from a user account or a [deploy key][] was removed from a repository. | +| `public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated. | +| `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified. | +| `public_key.unverify` | A user account's SSH key or a repository's [deploy key][] was unverified. | +| `public_key.verification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be verified. | +| `public_key.verify` | A user account's SSH key or a repository's [deploy key][] was verified. | + +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} +### `pull_request`カテゴリのアクション + +| アクション | 説明 | +| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | +| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." | +| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | +| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request.in_progress` | A pull request was marked as in progress. | +| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | +| `pull_request.merge` | A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 | +| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." | +| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request.reopen` | A pull request was reopened after previously being closed. | +| `pull_request_review.delete` | A review on a pull request was deleted. | +| `pull_request_review.dismiss` | A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 | +| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | + +### `pull_request_review`カテゴリのアクション + +| アクション | 説明 | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pull_request_review.delete` | A review on a pull request was deleted. | +| `pull_request_review.dismiss` | A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 | +| `pull_request_review.submit` | A review on a pull request was submitted. For more information, see "[Submitting your review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review)." | + +### `pull_request_review_comment`カテゴリのアクション + +| アクション | 説明 | +| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." | +| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. | +| `pull_request_review_comment.update` | A review comment on a pull request was changed. | +{%- endif %} + +### `repo` カテゴリアクション + +| アクション | 説明 | +| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repo.access` | リポジトリの可視性がプライベート{%- ifversion ghes %}、パブリック、{% endif %} または内部に変更されました。 | +| `repo.actions_enabled` | {% data variables.product.prodname_actions %} was enabled for a repository. | +| `repo.add_member` | リポジトリにコラボレーターが追加されました。 | +| `repo.add_topic` | A topic was added to a repository. | +| `repo.advanced_security_disabled` | {% data variables.product.prodname_GH_advanced_security %} was disabled for a repository. | +| `repo.advanced_security_enabled` | {% data variables.product.prodname_GH_advanced_security %} was enabled for a repository. | +| `repo.advanced_security_policy_selected_member_disabled` | A repository administrator prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for a repository. | +| `repo.advanced_security_policy_selected_member_enabled` | A repository administrator allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for a repository. | +| `repo.archived` | リポジトリがアーカイブされました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。 | +| `repo.code_scanning_analysis_deleted` | Code scanning analysis for a repository was deleted. For more information, see "[Delete a code scanning analysis from a repository](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)." | +| `repo.change_merge_setting` | Pull request merge options were changed for a repository. | +| `repo.clear_actions_settings` | A repository administrator cleared {% data variables.product.prodname_actions %} policy settings for a repository. | +| `repo.config` | A repository administrator blocked force pushes. 詳しくは、 [リポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)を参照してください。 | +{%- ifversion fpt or ghec %} +| `repo.config.disable_collaborators_only` | The interaction limit for collaborators only was disabled. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 | `repo.config.disable_contributors_only` | The interaction limit for prior contributors only was disabled in a repository. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 | `repo.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only was disabled in a repository. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 | `repo.config.enable_collaborators_only` | The interaction limit for collaborators only was enabled in a repository. Users that are not collaborators or organization members were unable to interact with a repository for a set duration. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 | `repo.config.enable_contributors_only` | The interaction limit for prior contributors only was enabled in a repository. Users that are not prior contributors, collaborators or organization members were unable to interact with a repository for a set duration. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 | `repo.config.enable_sockpuppet_disallowed` | The interaction limit for existing users was enabled in a repository. New users aren't able to interact with a repository for a set duration. Existing users of the repository, contributors, collaborators or organization members are able to interact with a repository. 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 +{%- endif %} +{%- ifversion ghes %} +| `repo.config.disable_anonymous_git_access`| Anonymous Git read access was disabled for a repository. 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | `repo.config.enable_anonymous_git_access` | Anonymous Git read access was enabled for a repository. 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | `repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting was locked, preventing repository administrators from changing (enabling or disabling) this setting. 詳細は「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。 | `repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting was unlocked, allowing repository administrators to change (enable or disable) this setting. 詳細は「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。 +{%- endif %} +| `repo.create` | A repository was created. | `repo.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for a repository. 詳しい情報については、「[リポジトリに対して暗号化されたシークレットを作成する](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。 | `repo.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for a repository. | `repo.destroy` | A repository was deleted. +{%- ifversion ghes %} +| `repo.disk_archive` | A repository was archived on disk. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." +{%- endif %} +| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file. | `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository. | `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created. | `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted. | `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_source` | A {% data variables.product.prodname_pages %} source was modified. | `repo.pages_private` | A {% data variables.product.prodname_pages %} site visibility was changed to private. | `repo.pages_public` | A {% data variables.product.prodname_pages %} site visibility was changed to public. | `repo.register_self_hosted_runner` | A new self-hosted runner was registered. 詳しい情報については、「[リポジトリにセルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)」を参照してください。 | `repo.remove_self_hosted_runner` | A self-hosted runner was removed. 詳しい情報については、「[リポジトリからランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)」を参照してください。 | `repo.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was deleted for a repository. | `repo.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was deleted for a repository. | `repo.remove_member` | A collaborator was removed from a repository. | `repo.remove_topic` | A topic was removed from a repository. | `repo.rename` | A repository was renamed. +{%- ifversion fpt or ghec %} +| `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. For more information, see "[Configuring required approval for workflows from public forks](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)." +{%- endif %} +| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. 詳しい情報については「[{% data variables.product.prodname_actions %}の成果物とログの保持期間をリポジトリで設定する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)」を参照してください。 +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} +| `repo.self_hosted_runner_online` | The runner application was started. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 | `repo.self_hosted_runner_offline` | The runner application was stopped. REST APIを通じてのみ見ることができます。UIあるいはJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[セルフホストランナーのステータスチェック](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)」を参照してください。 | `repo.self_hosted_runner_updated` | The runner application was updated. REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。 +{%- endif %} +| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。 | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed. + +{%- ifversion fpt or ghec %} +### `repository_advisory` カテゴリアクション + +| アクション | 説明 | +| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_advisory.close` | Someone closed a security advisory. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | +| `repository_advisory.cve_request` | Someone requested a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. | +| `repository_advisory.github_broadcast` | {% data variables.product.prodname_dotcom %} made a security advisory public in the {% data variables.product.prodname_advisory_database %}. | +| `repository_advisory.github_withdraw` | {% data variables.product.prodname_dotcom %} withdrew a security advisory that was published in error. | +| `repository_advisory.open` | Someone opened a draft security advisory. | +| `repository_advisory.publish` | Someone publishes a security advisory. | +| `repository_advisory.reopen` | Someone reopened as draft security advisory. | +| `repository_advisory.update` | Someone edited a draft or published security advisory. | + +### `repository_content_analysis`カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_content_analysis.enable` | An organization owner or repository administrator [enabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). | +| `repository_content_analysis.disable` | An organization owner or repository administrator [disabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). | + +### `repository_dependency_graph` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repository_dependency_graph.disable` | A repository owner or administrator disabled the dependency graph for a private repository. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | +| `repository_dependency_graph.enable` | A repository owner or administrator enabled the dependency graph for a private repository. | +{%- endif %} + +### `repository_image` category actions + +| アクション | 説明 | +| -------------------------- | ------------------------------------------------ | +| `repository_image.create` | An image to represent a repository was uploaded. | +| `repository_image.destroy` | An image to represent a repository was deleted. | + +### `repository_projects_change` category actions + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repository_projects_change.clear` | The repository projects policy was removed for an organization, or all organizations in the enterprise. Organization admins can now control their repository projects settings. For more information, see "[Enforcing project board policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise)." | +| `repository_projects_change.disable` | Repository projects were disabled for a repository, all repositories in an organization, or all organizations in an enterprise. | +| `repository_projects_change.enable` | Repository projects were enabled for a repository, all repositories in an organization, or all organizations in an enterprise. | + +{%- ifversion ghec or ghes or ghae %} +### `repository_secret_scanning` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_secret_scanning.disable` | A repository owner or administrator disabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `repository_secret_scanning.enable` | A repository owner or administrator enabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. | +{%- endif %} + +{%- if secret-scanning-audit-log-custom-patterns %} + +### `repository_secret_scanning_custom_pattern` category actions + +| アクション | 説明 | +| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in a repository. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)」を参照してください。 | +| `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)」を参照してください。 | +| `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)」を参照してください。 | + +### `repository_secret_scanning_push_protection` category actions + +| アクション | 説明 | +| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator disabled secret scanning for a repository. 詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。 | +| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator enabled secret scanning for a repository. 詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。 | +{%- endif %} +### `repository_visibility_change` category actions + +| アクション | 説明 | +| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_visibility_change.clear` | The repository visibility change setting was cleared for an organization or enterprise. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)" and "[Enforcing a policy for changes to repository visibility](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-changes-to-repository-visibility) for an enterprise." | +| `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | +| `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. | + +{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +### `repository_vulnerability_alert` カテゴリアクション + +| アクション | 説明 | +| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `repository_vulnerability_alert.create` | {% data variables.product.product_name %} created a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | +| `repository_vulnerability_alert.dismiss` | An organization owner or repository administrator dismissed a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency. | +| `repository_vulnerability_alert.resolve` | Someone with write access to a repository pushed changes to update and resolve a vulnerability in a project dependency. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `repository_vulnerability_alerts` カテゴリアクション + +| アクション | 説明 | +| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repository_vulnerability_alerts.authorized_users_teams` | An organization owner or repository administrator updated the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 | +| `repository_vulnerability_alerts.disable` | A repository owner or repository administrator disabled {% data variables.product.prodname_dependabot_alerts %}. | +| `repository_vulnerability_alerts.enable` | A repository owner or repository administrator enabled {% data variables.product.prodname_dependabot_alerts %}. | +{%- endif %} + +### `required_status_check` category actions + +| アクション | 説明 | +| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `required_status_check.create` | A status check was marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." | +| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." | + +{%- ifversion ghec or ghes > 3.1 %} +### `restrict_notification_delivery` category actions + +| アクション | 説明 | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `restrict_notification_delivery.enable` | Email notification restrictions for an organization or enterprise were enabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." | +| `restrict_notification_delivery.disable` | Email notification restrictions for an organization or enterprise were disabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." | +{%- endif %} + +{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %} +### `role`カテゴリアクション + +| アクション | 説明 | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | An organization owner created a new custom repository role. 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 | +| `destroy` | An organization owner deleted a custom repository role. 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 | +| `update` | An organization owner edited an existing custom repository role. 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 | +{%- endif %} + +{%- ifversion ghec or ghes or ghae %} +### `secret_scanning` カテゴリアクション + +| アクション | 説明 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `secret_scanning.disable` | An organization owner disabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `secret_scanning.enable` | An organization owner enabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. | + +### `secret_scanning_new_repos` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `secret_scanning_new_repos.disable` | An organization owner disabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | +| `secret_scanning_new_repos.enable` | An organization owner enabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories. | +{%- endif %} + +{%- ifversion ghec or ghes or ghae %} +### `security_key` category actions + +| アクション | 説明 | +| ----------------------- | --------------------------------------------- | +| `security_key.register` | A security key was registered for an account. | +| `security_key.remove` | A security key was removed from an account. | +{%- endif %} + +{%- ifversion fpt or ghec %} +### `sponsors` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sponsors.agreement_sign` | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization. | +| `sponsors.custom_amount_settings_change` | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." | +| `sponsors.fiscal_host_change` | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated. | +| `sponsors.withdraw_agreement_signature` | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization. | +| `sponsors.repo_funding_links_file_action` | The FUNDING file in a repository was changed. 詳しい情報については「[リポジトリにスポンサーボタンを表示する](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)」を参照してください。 | +| `sponsors.sponsor_sponsorship_cancel` | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)." | +| `sponsors.sponsor_sponsorship_create` | A sponsorship was created, by sponsoring an account. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)." | +| `sponsors.sponsor_sponsorship_payment_complete` | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)." | +| `sponsors.sponsor_sponsorship_preference_change` | The option to receive email updates from a sponsored account was changed. 詳細は「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照してください。 | +| `sponsors.sponsor_sponsorship_tier_change` | A sponsorship was upgraded or downgraded. 詳細は「[スポンサーシップをアップグレードする](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)」を参照してください。 | +| `sponsors.sponsored_developer_approve` | A {% data variables.product.prodname_sponsors %} account was approved. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | +| `sponsors.sponsored_developer_create` | A {% data variables.product.prodname_sponsors %} account was created. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | +| `sponsors.sponsored_developer_disable` | A {% data variables.product.prodname_sponsors %} account was disabled. | +| `sponsors.sponsored_developer_profile_update` | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)." | +| `sponsors.sponsored_developer_redraft` | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state. | +| `sponsors.sponsored_developer_request_approval` | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." | +| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." | +| `sponsors.update_tier_welcome_message` | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated. | +| `sponsors.update_tier_repository` | A {% data variables.product.prodname_sponsors %} tier changed access for a repository. | +{%- endif %} + +{%- ifversion ghec or ghes or ghae %} +### `ssh_certificate_authority` category actions + +| アクション | 説明 | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ssh_certificate_authority.create` | An SSH certificate authority for an organization or enterprise was created. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." | +| `ssh_certificate_authority.destroy` | An SSH certificate authority for an organization or enterprise was deleted. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." | + +### `ssh_certificate_requirement` category actions + +| アクション | 説明 | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ssh_certificate_requirement.enable` | The requirement for members to use SSH certificates to access an organization resources was enabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." | +| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." | +{%- endif %} + +### `staff` category actions + +| アクション | 説明 | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `staff.disable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks. | +| `staff.enable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks. | +{%- ifversion ghes > 3.2 or ghae %} +| `staff.exit_fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}. | `staff.fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user. +{%- endif %} +| `staff.repo_lock` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator locked (temporarily gained full access to) a user's private repository. | `staff.repo_unlock` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator unlocked (ended their temporary access to) a user's private repository. | `staff.unlock` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unlocked (temporarily gained full access to) all of a user's private repositories. | `staff.set_domain_token_expiration` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}| | `staff.unverify_domain` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff verified an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} + +### `team` カテゴリアクション + +| アクション | 説明 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team.add_member` | A member of an organization was added to a team. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)." | +| `team.add_repository` | A team was given access and permissions to a repository. | +| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)." | +| `team.change_privacy` | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)." | +| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | +| `team.delete` | ユーザアカウントまたはリポジトリが Team から削除されました。 | +| `team.destroy` | Teamが削除されました。 | +{%- ifversion ghec or ghes or ghae %} +| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member. | `team.promote_maintainer` | A user was promoted from a team member to a team maintainer. For more information, see "[Promoting an organization member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)." +{%- endif %} +| `team.remove_member` | A member of an organization was removed from a team. For more information, see "[Removing organization members from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)." | `team.remove_repository` | A repository was no longer under a team's control. | `team.rename` | A team's name was changed. | `team.update_permission` | A team's access was changed. | `team.update_repository_permission` | A team's permission to a repository was changed. + +### `team_discussions` カテゴリアクション + +| アクション | 説明 | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team_discussions.clear` | An organization owner cleared the setting to allow team discussions for an organization or enterprise. | +| `team_discussions.disable` | An organization owner disabled team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization)." | +| `team_discussions.enable` | An organization owner enabled team discussions for an organization. | + +{%- ifversion ghec %} +### `team_sync_tenant` category actions + +| アクション | 説明 | +| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `team_sync_tenant.disabled` | Team synchronization with a tenant was disabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." | +| `team_sync_tenant.enabled` | Team synchronization with a tenant was enabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." | +| `team_sync_tenant.update_okta_credentials` | The Okta credentials for team synchronization with a tenant were changed. | +{%- endif %} + +{%- ifversion fpt or ghes %} +### `two_factor_authentication` カテゴリアクション + +| アクション | 説明 | +| ------------------------------------------------------- | -------------------------------------------------------------------------- | +| `two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account. | +| `two_factor_authentication.enabled` | [Two-factor authentication][2fa] was enabled for a user account. | +| `two_factor_authentication.password_reset_fallback_sms` | A one-time password code was sent to a user account fallback phone number. | +| `two_factor_authentication.recovery_codes_regenerated` | Two factor recovery codes were regenerated for a user account. | +| `two_factor_authentication.sign_in_fallback_sms` | A one-time password code was sent to a user account fallback phone number. | +| `two_factor_authentication.update_fallback` | The two-factor authentication fallback for a user account was changed. | +{%- endif %} + +{%- ifversion fpt or ghes or ghae %} +### `user` カテゴリアクション + +| アクション | 説明 | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user.add_email` | ユーザアカウントにメールアドレスが追加されました。 | +| `user.async_delete` | An asynchronous job was started to destroy a user account, eventually triggering a `user.delete` event. | +| `user.audit_log_export` | Audit log entries were exported. | +| `user.block_user` | A user was blocked by another user{% ifversion ghes %} or a site administrator{% endif %}. | +| `user.change_password` | ユーザがパスワードを変更しました。 | +| `user.create` | 新規ユーザが作成されました。 | +| `user.creation_rate_limit_exceeded` | The rate of creation of user accounts, applications, issues, pull requests or other resources exceeded the configured rate limits, or too many users were followed too quickly. | +| `user.delete` | ユーザアカウントが非同期的ジョブによって削除されました。 | +{%- ifversion ghes %} +| `user.demote` | A site administrator was demoted to an ordinary user account. +{%- endif %} +| `user.destroy` | A user deleted his or her account, triggering `user.async_delete`. | `user.failed_login` | A user tries to sign in with an incorrect username, password, or two-factor authentication code. | `user.flag_as_large_scale_contributor` | A user account was flagged as a large scale contributor. Only contributions from public repositories the user owns will be shown in their contribution graph, in order to prevent timeouts. | `user.forgot_password` | A user requested a password reset via the sign-in page. | `user.hide_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now hidden. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)." | `user.lockout` | A user was locked out of their account. | `user.login` | A user signed in. +{%- ifversion ghes or ghae %} +| `user.mandatory_message_viewed` | A user viewed a mandatory message. For more information see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise)" for details." +{%- endif %} +| `user.minimize_comment` | A comment made by a user was minimized. +{%- ifversion ghes %} +| `user.promote` | An ordinary user account was promoted to a site administrator. +{%- endif %} +| `user.recreate` | A user's account was restored. | `user.remove_email` | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename` | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)." | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend` | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account. | `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account. | `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account. | `user.two_factor_requested` | A user was prompted for a two-factor authentication code. | `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}. | `user.unminimize_comment` | A comment made by a user was unminimized. | `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. +{%- endif %} + +{%- ifversion ghec or ghes %} +### `user_license` category actions + +| アクション | 説明 | +| ---------------------- | ------------------------------------------------------------ | +| `user_license.create` | A seat license for a user in an enterprise was created. | +| `user_license.destroy` | A seat license for a user in an enterprise was deleted. | +| `user_license.update` | A seat license type for a user in an enterprise was changed. | +{%- endif %} + +{% ifversion fpt or ghec or ghes > 3.1 or ghae %} +### `workflows` カテゴリアクション + +{% data reusables.audit_log.audit-log-events-workflows %} +{%- endif %} + + [OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps + + [OAuth application]: /guides/basics-of-authentication/#registering-your-app + + [add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account + [deploy key]: /developers/overview/managing-deploy-keys#deploy-keys + + [2fa]: /authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md new file mode 100644 index 0000000000..1b4a948ab8 --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md @@ -0,0 +1,51 @@ +--- +title: Exporting audit log activity for your enterprise +intro: You can export audit and Git events data to a file for offline analysis. +shortTitle: Export audit logs +permissions: Enterprise owners can export the audit log. +miniTocMaxHeadingLevel: 3 +versions: + ghec: '*' +type: tutorial +topics: + - Auditing + - Enterprise + - Logging +--- + +## About exports of audit log and Git events data + +You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)." + +You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface. + +{% data reusables.audit_log.exported-log-keys-and-values %} + +As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" and "[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)." + +## Exporting audit log data + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters. +2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in. + + ![エクスポートボタン](/assets/images/help/organizations/org-audit-log-export.png) + +## Exporting Git events data + +You can also export Git events data by date range. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for. + + ![Export Git events button](/assets/images/help/organizations/org-audit-log-export-git-events.png) +1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file. +1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. 例: + + ``` + gunzip export-avocado-corp-1642896556.json.gz + ``` diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md new file mode 100644 index 0000000000..d554271aaa --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md @@ -0,0 +1,20 @@ +--- +title: Reviewing audit logs for your enterprise +intro: You can view user and system activity in the audit logs for your enterprise. +shortTitle: Review audit logs +versions: + ghec: '*' + ghes: '*' + ghae: '*' +topics: + - Enterprise +children: + - /about-the-audit-log-for-your-enterprise + - /accessing-the-audit-log-for-your-enterprise + - /searching-the-audit-log-for-your-enterprise + - /exporting-audit-log-activity-for-your-enterprise + - /streaming-the-audit-log-for-your-enterprise + - /using-the-audit-log-api-for-your-enterprise + - /audit-log-events-for-your-enterprise +--- + diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md new file mode 100644 index 0000000000..e9a91c01dc --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md @@ -0,0 +1,130 @@ +--- +title: Searching the audit log for your enterprise +intro: You can search an extensive list of audited actions in your enterprise. +shortTitle: Search audit logs +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can search the audit log.' +redirect_from: + - /enterprise/admin/articles/searching-the-audit-log + - /enterprise/admin/installation/searching-the-audit-log + - /enterprise/admin/user-management/searching-the-audit-log + - /admin/user-management/searching-the-audit-log + - /admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log +versions: + ghes: '*' + ghae: '*' + ghec: '*' +type: how_to +topics: + - Auditing + - Enterprise + - Logging +miniTocMaxHeadingLevel: 3 +--- + +## About search for the enterprise audit log + +You can search your enterprise audit log directly from the user interface by using the **Filters** dropdown, or by typing a search query. + + ![検索クエリ](/assets/images/enterprise/site-admin-settings/search-query.png) + +For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." + +You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." + +テキストを使用してエントリを検索することはできません。 ただし、さまざまなフィルターを使用すれば検索クエリを作成できます。 ログを検索するときに使用される多くの演算子 (`-`、`>`、`<` など) は、{% data variables.product.product_name %} 全体で検索するものと同じ形式です。 詳細は「[{% data variables.product.prodname_dotcom %} での検索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +{% note %} + +**注釈**: {% data reusables.audit_log.retention-periods %} + +{% endnote %} + +## Search query filters + +| フィルタ | 説明 | +| -------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Yesterday's activity` | All actions created in the past day. | +| `Enterprise account management` | All actions in the `business` category. | +| `Organization membership` | All actions for when a new user was invited to join an organization. | +| `Team management` | All actions related to team management.
- When a user account or repository was added or removed from a team
- When a team maintainer was promoted or demoted
- When a team was deleted | +| `Repository management` | All actions for repository management.
- When a repository was created or deleted
- When the repository visibility was changed
- When a team was added or removed from a repository{% ifversion ghec %} +| `Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %} +| `Hook activity` | All actions for webhooks and pre-receive hooks. | +| `Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories. | + +## 検索クエリの構文 + +You can compose a search query from one or more `key:value` pairs, separated by AND/OR logical operators. たとえば、2017 年の初めからリポジトリ `octocat/Spoon-Knife` に影響を与えたすべてのアクションを確認するには、次のようにします: + + `repo:"octocat/Spoon-Knife" AND created:>=2017-01-01` + +The `key:value` pairs that can be used in a search query are: + +| キー | 値 | +| --------------:| --------------------------------------------------------------------------------------------------------------------------------------------------- | +| `actor_id` | アクションを開始したユーザアカウントの ID | +| `actor` | アクションを開始したユーザアカウントの名前 | +| `oauth_app_id` | アクションに関連付けられている OAuth アプリケーションの ID | +| `action` | 監査されたアクションの名前 | +| `user_id` | アクションによって影響を受けたユーザの ID | +| `ユーザ` | アクションによって影響を受けたユーザの名前 | +| `repo_id` | アクションによって影響を受けたリポジトリの ID （妥当な場合） | +| `repo` | アクションによって影響を受けたリポジトリの名前 （妥当な場合） | +| `actor_ip` | アクション元の IP アドレス | +| `created` | Time at which the action occurred{% ifversion ghes %}. If querying the audit log from the site admin dashboard, use `created_at` instead{% endif %} +| `from` | アクション元の View | +| `note` | イベント固有の他の情報（プレーンテキストまたは JSON フォーマット） | +| `org` | アクションによって影響を受けたOrganizationの名前（該当する場合） | +| `org_id` | アクションによって影響を受けたOrganizationの ID（該当する場合） | +| `business` | Name of the enterprise affected by the action (if applicable) | +| `business_id` | ID of the enterprise affected by the action (if applicable) | + +To see actions grouped by category, you can also use the action qualifier as a `key:value` pair. For more information, see "[Search based on the action performed](#search-based-on-the-action-performed)." + +For a full list of actions in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." + +## Audit log を検索する + +{% data reusables.audit_log.audit-log-search-by-operation %} + +{% data reusables.audit_log.audit-log-search-by-repo %} + +{% data reusables.audit_log.audit-log-search-by-user %} + +### 実行されたアクションに基づく検索 + +特定のイベントを検索するには、クエリで `action` 修飾子を使用します。 例: + + * `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。 + * `-action:hook` は webhook カテゴリ内のすべてのイベントを除外します。 + +各カテゴリには、フィルタできる一連の関連アクションがあります。 例: + + * `action:team.create`はTeamが作成されたすべてのイベントを検索します。 + * `-action:hook.events_changed` は webhook の変更されたすべてのイベントを除外します。 + +Actions that can be found in your enterprise audit log are grouped within the following categories: + +{% data reusables.audit_log.audit-log-action-categories %} +### アクション時間に基づく検索 + +`created` 修飾子を使用して、行われた日時に基づいて Audit log 内のイベントをフィルタします。 + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +例: + + * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。 + * `created:>=2014-07-08` は、2014 年 7 月 8 日かそれ以降に生じたすべてのイベントを検索します。 + * `created:<=2014-07-08`は、2014 年 7 月 8 日かそれ以前に生じたすべてのイベントを検索します。 + * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。 + +### 場所に基づく検索 + +修飾子 `country` を使用すれば、発信元の国に基づいて Audit log 内のイベントをフィルタリングできます。 You can use a country's two-letter short code or full name. Countries with spaces in their name will need to be wrapped in quotation marks. 例: + + * `country:de` は、ドイツで発生したイベントをすべて検索します。 + * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。 + * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。 diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md similarity index 91% rename from translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md rename to translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index 89cb36c878..69da24a1f5 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Streaming the audit logs for organizations in your enterprise account +title: Streaming the audit log for your enterprise intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.' miniTocMaxHeadingLevel: 3 versions: @@ -10,27 +10,13 @@ topics: - Enterprise - Logging - Organizations -shortTitle: Stream organization audit logs +shortTitle: Stream audit logs redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account + - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account permissions: Enterprise owners can configure audit log streaming. --- -## About exporting audit data - -You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways: - -* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)." -* Use the API to poll for new audit log events. For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)." -* Set up {% data variables.product.product_name %} to stream audit data as events are logged. - -Currently, audit log streaming is supported for multiple storage providers. -- Amazon S3 -- Azure Blob Storage -- Azure Event Hubs -- Google Cloud Storage -- Splunk - ## About audit log streaming To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor: @@ -40,7 +26,7 @@ The benefits of streaming audit data include: * **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account. * **Data continuity**. You can pause the stream for up to seven days without losing any audit data. -* **Data retention**. You can keep your exported audit logs and Git data as long as you need to. +* **Data retention**. You can keep your exported audit logs and Git events data as long as you need to. Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise. diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md new file mode 100644 index 0000000000..3dc0507819 --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md @@ -0,0 +1,143 @@ +--- +title: Using the audit log API for your enterprise +intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.' +shortTitle: Audit log API +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.' +miniTocMaxHeadingLevel: 3 +versions: + ghec: '*' + ghes: '>=3.0' + ghae: '*' +type: tutorial +topics: + - Auditing + - Enterprise + - Logging + - API +--- + +## Audit log API を使用する + +GraphQL API{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} または REST API を使用して Audit log を操作できます{% endif %}。 + +Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time). + +{% ifversion ghec or ghes > 3.0 or ghae %} +## Querying the audit log GraphQL API + +To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audit-log-api-info %} + +Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. Git イベントを取得するには、代わりに REST API を使用してください。 For more information, see `git` category actions in "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)", and also the "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization) audit log endpoints in the REST API documentation."{% endif %} + +GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。 + +### Example 1: Members added to or removed from organizations in an enterprise + +The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned. + +This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise. + +```shell +{ + enterprise(slug: "avocado-corp") { + organizations(first: 10, orderBy: {field: LOGIN, direction: DESC}) { + nodes { + name + auditLog(first: 20) { + edges { + node { + ... on OrgAddMemberAuditEntry { + action + actorLogin + createdAt + } + ... on OrgRemoveMemberAuditEntry { + action + actorLogin + createdAt + } + } + } + } + } + pageInfo { + hasNextPage + endCursor + } + } + } +} +``` + +The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation. +### Example 2: Events in an organization, for a specific date and actor + +You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space. + +The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first. + +This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) interface. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an owner of the `octo-org` organization. + +```shell +{ + enterprise(slug: "avocado-corp") { + organizations(first: 1, query: "octo-org") { + nodes { + name + auditLog(first: 20, query: "actor:octocat created:>=2022-01-01T00:00:00.000Z", orderBy: {field: CREATED_AT, direction: DESC}) { + edges { + node { + ... on AuditEntry { + action + actorLogin + createdAt + user { + name + } + } + } + } + } + } + } + } +} +``` + +For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries). + +{% endif %} +{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} +## Querying the audit log REST API + +To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor: +{% data reusables.audit_log.audited-data-list %} + +{% data reusables.audit_log.retention-periods %} + +For more information about the audit log REST API, see "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." + +### Example 1: All events in an enterprise, for a specific date, with pagination + +The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination): + +```shell +curl -H "Authorization: token TOKEN" \ +--request GET \ +"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100" +``` + +### Example 2: Events for pull requests in an enterprise, for a specific date and actor + +You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`. + +The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user: + +```shell +curl -H "Authorization: token TOKEN" \ +--request GET \ +"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat" +``` + +{% endif %} diff --git a/translations/ja-JP/content/admin/overview/system-overview.md b/translations/ja-JP/content/admin/overview/system-overview.md index 226a461ae3..c6b884b2e6 100644 --- a/translations/ja-JP/content/admin/overview/system-overview.md +++ b/translations/ja-JP/content/admin/overview/system-overview.md @@ -39,15 +39,15 @@ The user filesystem contains user configuration and data, such as: ## Deployment options -You can deploy {% data variables.product.prodname_ghe_server %} as a single virtual appliance, or in a high availability configuration. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." +You can deploy {% data variables.product.prodname_ghe_server %} as a single virtual appliance, or in a high availability configuration. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/admin/enterprise-management/configuring-high-availability)." -Some organizations with tens of thousands of developers may also benefit from {% data variables.product.prodname_ghe_server %} Clustering. For more information, see "[About clustering](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)." +Some organizations with tens of thousands of developers may also benefit from {% data variables.product.prodname_ghe_server %} Clustering. For more information, see "[About clustering](/admin/enterprise-management/configuring-clustering/about-clustering)." ## Data retention and datacenter redundancy {% danger %} -Before using {% data variables.product.prodname_ghe_server %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan. For more information, see "[Configuring backups on your appliance](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)." +Before using {% data variables.product.prodname_ghe_server %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." {% enddanger %} @@ -55,7 +55,7 @@ Before using {% data variables.product.prodname_ghe_server %} in a production en In addition to network backups, both AWS (EBS) and VMware disk snapshots of the user storage volumes are supported while the appliance is offline or in maintenance mode. Regular volume snapshots can be used as a low-cost, low-complexity alternative to network backups with {% data variables.product.prodname_enterprise_backup_utilities %} if your service level requirements allow for regular offline maintenance. -For more information, see "[Configuring backups on your appliance](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)." +For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." ## Security @@ -80,11 +80,11 @@ For more information, see "[Configuring backups on your appliance](/enterprise/{ Currently, the base of the {% data variables.product.prodname_ghe_server %} appliance is Debian 9 (Stretch) and receives support under the Debian Long Term Support program. There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch. -Regular patch updates are released on the {% data variables.product.prodname_ghe_server %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/enterprise-server/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.prodname_ghe_server %} patch release. +Regular patch updates are released on the {% data variables.product.prodname_ghe_server %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.prodname_ghe_server %} patch release. ### Network security -{% data variables.product.prodname_ghe_server %}'s internal firewall restricts network access to the appliance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)." +{% data variables.product.prodname_ghe_server %}'s internal firewall restricts network access to the appliance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports)." ### Application security @@ -92,15 +92,15 @@ Regular patch updates are released on the {% data variables.product.prodname_ghe ### External services and support access -{% data variables.product.prodname_ghe_server %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)," "[Setting up external monitoring](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)," and "[Log forwarding](/admin/user-management/log-forwarding)." +{% data variables.product.prodname_ghe_server %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)," "[Setting up external monitoring](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)," and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." -You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)." +You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)." ### Encrypted communication -{% data variables.product.prodname_dotcom %} designs {% data variables.product.prodname_ghe_server %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.prodname_ghe_server %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)." +{% data variables.product.prodname_dotcom %} designs {% data variables.product.prodname_ghe_server %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.prodname_ghe_server %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)." -By default, the appliance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/enterprise/user/articles/about-ssh)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." +By default, the appliance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." {% ifversion ghes > 3.3 %} @@ -112,24 +112,24 @@ If you configure SAML authentication for {% data variables.product.product_locat {% data variables.product.prodname_ghe_server %} provides three types of accounts. -- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." +- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." - User accounts in the appliance's web application have full access to their own data and any data that other users or organizations explicitly grant. - Site administrators in the appliance's web application are user accounts that can manage high-level web application and appliance settings, user and organization account settings, and repository data. -For more information about {% data variables.product.prodname_ghe_server %}'s user permissions, see "[Access permissions on GitHub](/enterprise/user/articles/access-permissions-on-github)." +For more information about {% data variables.product.prodname_ghe_server %}'s user permissions, see "[Access permissions on GitHub](/get-started/learning-about-github/access-permissions-on-github)." ### Authentication {% data variables.product.prodname_ghe_server %} provides four authentication methods. -- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/enterprise/user/articles/about-ssh)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." -- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)." -- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Authenticating users for your GitHub Enterprise Server instance](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)." +- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)." +- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Authenticating users for your GitHub Enterprise Server instance](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance)." - OAuth and Personal Access Tokens provide access to Git repository data and APIs for both external clients and services. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." ### Audit and access logging -{% data variables.product.prodname_ghe_server %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.prodname_ghe_server %} stores permanently. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[Log forwarding](/admin/user-management/log-forwarding)." +{% data variables.product.prodname_ghe_server %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.prodname_ghe_server %} stores permanently. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." Access and audit logs include information like the following. @@ -158,6 +158,6 @@ Tarballs are also available, with a full list of dependencies and metadata, at ` ## Further reading -- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" -- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)" +- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)" +- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" - [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the `github/roadmap` repository diff --git a/translations/ja-JP/content/admin/user-management/index.md b/translations/ja-JP/content/admin/user-management/index.md index bff54a1b2a..283e3704b5 100644 --- a/translations/ja-JP/content/admin/user-management/index.md +++ b/translations/ja-JP/content/admin/user-management/index.md @@ -1,6 +1,6 @@ --- title: ユーザ、Organization、リポジトリデータを管理する -shortTitle: ユーザ、Organization、リポジトリデータを管理する +shortTitle: 'Manage users, organizations, and repositories' intro: このガイドでは、Enterprise にサインインするユーザの認証方式、リポジトリへのアクセスとコラボレーションのための Organization と Team を作成する方法、およびユーザセキュリティで推奨されるベストプラクティスについて説明します。 redirect_from: - /enterprise/admin/categories/user-management @@ -18,7 +18,6 @@ children: - /managing-users-in-your-enterprise - /managing-organizations-in-your-enterprise - /managing-repositories-in-your-enterprise - - /monitoring-activity-in-your-enterprise - /migrating-data-to-and-from-your-enterprise --- diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index 93562f856f..0c68504fda 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -23,8 +23,6 @@ children: - /requiring-two-factor-authentication-for-an-organization - /creating-teams - /adding-people-to-teams - - /viewing-the-audit-logs-for-organizations-in-your-enterprise - - /streaming-the-audit-logs-for-organizations-in-your-enterprise-account - /managing-your-role-in-an-organization-owned-by-your-enterprise - /removing-users-from-teams-and-organizations - /removing-organizations-from-your-enterprise diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md deleted file mode 100644 index 77bda1ca39..0000000000 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Viewing the audit logs for organizations in your enterprise -intro: Enterprise オーナーは、Enterprise アカウントが所有するすべての Organization からのアクションが集約された Audit log を表示できます。 -redirect_from: - - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account - - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account -versions: - ghec: '*' -type: how_to -topics: - - Auditing - - Enterprise - - Logging - - Organizations -shortTitle: View organization audit logs ---- - -各 Audit log エントリには、次のようなイベントに関する適切な情報が表示されます: - -- アクションが実行された Organization -- アクションを実行したユーザ -- アクションの対象となったリポジトリ -- 実行されたアクション -- アクションが実行された国 -- アクションが発生した日時 - -Audit log で特定のイベントを検索したり、Audit log データをエクスポートしたりできます。 Audit log の検索と特定の Organization イベントの詳細については、「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)」を参照してください。 - -You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)." - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md index 08fa2ee5c0..db8649977f 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md @@ -81,7 +81,7 @@ Audit log には、Enterprise 内で行われたアクションに関する次 ### 実行されたアクションに基づく検索 -`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 以下のカテゴリに関連するイベントの詳しい情報については「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 +`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 For information on the events associated with these categories, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)". | カテゴリ名 | 説明 | | ------ | -------------------------------------------- | diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index 365b260e06..02929a11f8 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -1,12 +1,12 @@ --- -title: Enterprise のユーザメッセージをカスタマイズする +title: Customizing user messages for your enterprise shortTitle: Customizing user messages redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-for-your-enterprise -intro: '{% data variables.product.product_location %} でユーザに表示されるカスタムメッセージを作成できます。' +intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: ghes: '*' ghae: '*' @@ -15,64 +15,69 @@ topics: - Enterprise - Maintenance --- +## About user messages -## ユーザメッセージについて - -ユーザメッセージにはいくつかの種類があります。 -- {% ifversion ghes %}サインインまたは{% endif %}サインアウトページ{% ifversion ghes or ghae %}に表示されるメッセージ +There are several types of user messages. +- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %} - Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} -- すべてのページの上部に表示されるアナウンスバナー{% endif %} +- Announcement banners, which appear at the top of every page{% endif %} {% ifversion ghes %} {% note %} -**メモ:** 認証に SAML を使っている場合は、サインインページはアイデンティティプロバイダによって提示されるため、{% data variables.product.prodname_ghe_server %} でカスタマイズすることはできません。 +**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}. {% endnote %} -メッセージの書式設定には Markdown を使用できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github/)」を参照してください。 +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." -## カスタムサインインメッセージの作成 +## Creating a custom sign in message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![{% ifversion ghes %}[Add]{% else %}[Edit]{% endif %} メッセージボタン](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. [**Sign in message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} +5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. +![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. +![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} - ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. 表示されたメッセージを確認します。 ![サインインメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Review the rendered message. +![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} -## カスタムサインアウトメッセージを作成する +## Creating a custom sign out message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes or ghae %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. [**Sign out message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} +5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. +![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. +![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} - ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. 表示されたメッセージを確認します。 ![サインアウトメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Review the rendered message. +![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% ifversion ghes or ghae %} -## 必須メッセージを作成する +## Creating a mandatory message -メッセージを保存した後に初めてサインインしたときに、すべてのユーザに表示される必須メッセージを {% data variables.product.product_name %} で作成できます。 メッセージはポップアップウィンドウ内に表示され、ユーザは {% data variables.product.product_location %} を使用する前に閉じる必要があります。 +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. -必須メッセージにはさまざまな用途があります。 +Mandatory messages have a variety of uses. -- 新入社員にオンボーディング情報を提供する -- {% data variables.product.product_location %} のヘルプの取得方法をユーザに伝える -- すべてのユーザが {% data variables.product.product_location %} を使用時の利用規約を確実に読むようにする +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} -メッセージに Markdown チェックボックスを含める場合、ユーザがメッセージを閉じる前に、すべてのチェックボックスを選択する必要があります。 たとえば、必須メッセージに利用規約を含める場合、各ユーザにチェックボックスを選択して、ユーザが利用規約を読んだことを確認するように要求できます。 +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. -ユーザに必須メッセージが表示されるたびに、監査ログイベントが作成されます。 イベントには、ユーザが表示したメッセージのバージョンが含まれます。 詳しい情報については、「[監査されたアクション](/admin/user-management/audited-actions)」を参照してください。 +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." {% note %} @@ -83,30 +88,35 @@ topics: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. [Mandatory message] の右側にある [**Add message**] をクリックします。 ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. [Mandatory message] の下のテキストボックスに、メッセージを入力します。 ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +1. To the right of "Mandatory message", click **Add message**. + ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. + ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} {% ifversion ghes or ghae %} -## グローバルアナウンスバナーを作成する +## Creating a global announcement banner -各ページの上部にグローバルアナウンスバナーを設定し、すべてのユーザに対して表示できます。 +You can set a global announcement banner to be displayed to all users at the top of every page. {% ifversion ghae or ghes %} -You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. 詳しい情報については、{% ifversion ghes %}「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」および{% endif %}「[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)」を参照してください。 +You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." {% else %} -コマンドラインユーティリティを使用して、管理シェルでアナウンスバナーを設定することもできます。 詳しい情報については、「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」を参照してください。 +You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. {% ifversion ghes or ghae %}[Announcement] の右側{% else %}下{% endif %}にある [**Add announcement**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. [Announcement] のテキストフィールドに、バナーに表示するお知らせを入力します。 ![アナウンスを入力するテキストフィールド](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. 必要に応じて、[Expires on] でカレンダーのドロップダウンメニューを選択し、有効期限をクリックします。 ![有効期限を選択するためのカレンダードロップダウンメニュー](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. + ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. + ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. + ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md index 42f322522b..cf9a0aaba5 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md @@ -19,7 +19,7 @@ If you need to temporarily take over a user account, for example when troublesho For each impersonation session, you need to provide a reason for the impersonation. A session is limited to one hour, and you will have the same access as the user being impersonated. -Actions you perform during an impersonation session are recorded as events in the enterprise audit log, as well as the impersonated user's security log. The person being impersonated is sent an email notification when the impersonation session starts. For more information, see "[Audited actions](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions)" and "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)." +Actions you perform during an impersonation session are recorded as events in the enterprise audit log, as well as the impersonated user's security log. The person being impersonated is sent an email notification when the impersonation session starts. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)" and "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)." ## Impersonating a user diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md deleted file mode 100644 index c464510264..0000000000 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: 監査ログ -intro: '{% data variables.product.product_name %} は、{% ifversion ghes %}監査対象システム、{% endif %}ユーザ、Organization、リポジトリのイベントのログを保持します。 ログはデバッグや内部および外部のコンプライアンスに役立ちます。' -redirect_from: - - /enterprise/admin/articles/audit-logging - - /enterprise/admin/installation/audit-logging - - /enterprise/admin/user-management/audit-logging - - /admin/user-management/audit-logging -versions: - ghes: '*' - ghae: '*' -type: reference -topics: - - Auditing - - Enterprise - - Logging - - Security ---- - -完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 特定のアクションを見つける方法について詳しくは、「[Audit log を検索する](/admin/user-management/searching-the-audit-log)」を参照してください。 - -## プッシュのログ - -Git プッシュ操作はすべてログに記録されます。 詳しい情報については、「[プッシュログを表示する](/admin/user-management/viewing-push-logs)」を参照してください。 - -{% ifversion ghes %} -## システムイベント - -All audited system events are logged to `/var/log/github/audit.log`. ログは 24 時間ごとに自動的に交換され、7 日間保持されます。 - -Support Bundle にはシステムログが含まれています。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Support にデータを提供する](/admin/enterprise-support/providing-data-to-github-support)」を参照してください。 - -## Support Bundle - -すべての監査情報は、Support Bundle の `github-logs` ディレクトリにある `audit.log` ファイルに記録されます。 ログの転送が有効な場合、[Splunk](http://www.splunk.com/) や [Logstash](http://logstash.net/) などの外部の syslog ストリーミングコンシューマに、このデータをストリーミングすることができます。 このログからのすべてのエントリは、`github_audit` キーワードでフィルタリングできます。 詳しい情報については、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。 - -たとえば、次のエントリは新規リポジトリが作成されたことを示しています。 - -``` -Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"} -``` - -次の例は、コミットがリポジトリにプッシュされたことを示しています。 - -``` -Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" } -``` -{% endif %} diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md deleted file mode 100644 index 4b1f54d219..0000000000 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -title: 監査されたアクション -intro: 監査ログでいろんなアクションを検索することができます。 -miniTocMaxHeadingLevel: 3 -redirect_from: - - /enterprise/admin/articles/audited-actions - - /enterprise/admin/installation/audited-actions - - /enterprise/admin/user-management/audited-actions - - /admin/user-management/audited-actions -versions: - ghes: '*' - ghae: '*' -type: reference -topics: - - Auditing - - Enterprise - - Security ---- - -## 認証 - -| アクション | 説明 | -| ------------------------------------ | ---------------------------------------------------------------- | -| `oauth_access.create` | ユーザアカウントに[OAuth アクセストークン][] が[作成][generate token] されました。 | -| `oauth_access.destroy` | [OAuth アクセストークン][] がユーザアカウントから削除されました。 | -| `oauth_application.destroy` | [OAuth application][]がユーザまたは Organization のアカウントから削除されました。 | -| `oauth_application.reset_secret` | [OAuth アプリケーション][]の秘密鍵がリセットされました。 | -| `oauth_application.transfer` | [OAuth アプリケーション][]が別のユーザ、または Organization のアカウントへ移されました。 | -| `public_key.create` | SSHキーがユーザアカウントに[追加][add key]されたか[デプロイキー][]がリポジトリに追加されました。 | -| `public_key.delete` | SSHキーがユーザアカウントから削除されたか[デプロイキー][]がリポジトリから削除されました。 | -| `public_key.update` | ユーザアカウントの SSH キーまたはリポジトリの[デプロイキー][]が更新されました。{% ifversion ghes %} -| `two_factor_authentication.enabled` | ユーザアカウントの[二段階認証][2fa]が有効化されました。 | -| `two_factor_authentication.disabled` | ユーザアカウントの [2 要素認証][2fa]が無効になりました。{% endif %} - -{% ifversion ghes %} -## {% data variables.product.prodname_actions %} - -{% data reusables.actions.actions-audit-events-for-enterprise %} - -{% endif %} - -## フック - -| アクション | 説明 | -| --------------------- | ------------------------ | -| `hook.create` | リポジトリに新規フックが追加されました。 | -| `hook.config_changed` | フックのコンフィグレーションが変更されました。 | -| `hook.destroy` | フックが削除されました。 | -| `hook.events_changed` | フックの設定されているイベントが変更されました。 | - -## Enterprise 設定 - -| アクション | 説明 | -| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% ifversion ghes or ghae %} -| `business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_advanced_security %}のポリシーの施行](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)」を参照してください。{% endif %} -| `business.clear_members_can_create_repos` | サイトアドミンは、Enterprise 内の Organization でのリポジトリ作成の制限を解除します。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。{% ifversion ghes > 3.1 %} -| `business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." | -| `business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %} -| `business.update_member_repository_creation_permission` | サイトアドミンは、Enterprise 内の Organization でのリポジトリの作成を制限します。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。{% ifversion ghes %} -| `enterprise.config.lock_anonymous_git_access` | サイトアドミンは匿名の Git 読み取りアクセスをロックして、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できないようにします。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。 | -| `enterprise.config.unlock_anonymous_git_access` | サイトアドミンは匿名 Git 読み取りアクセスのロックを解除して、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できるようにします。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。{% endif %} - -{% ifversion ghae %} - -## IP 許可リスト - -| 名前 | 説明 | -| ------------------------------------------:| --------------------------------------------------------------------------------------- | -| `ip_allow_list_entry.create` | IP アドレスが IP 許可リストに追加されました。 | -| `ip_allow_list_entry.update` | IP アドレスまたはその説明が変更されました。 | -| `ip_allow_list_entry.destroy` | IP アドレスが IP 許可リストから削除されました。 | -| `ip_allow_list.enable` | IP 許可リストが有効化されました。 | -| `ip_allow_list.enable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが有効化されました。 | -| `ip_allow_list.disable` | IP 許可リストが無効化されました。 | -| `ip_allow_list.disable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが無効化されました。 | - -{% endif %} - -## Issue - -| アクション | 説明 | -| ---------------------- | -------------------------------------------------------------------------------------------------------------------- | -| `issue.update` | Issue のテキスト本体（最初のコメント）が変更されました。 | -| `issue_comment.update` | Issue （最初以外）のコメントが変更されました。 | -| `issue.destroy` | Issue がリポジトリから削除されました。 詳しい情報については、「[>Issue を削除する](/github/managing-your-work-on-github/deleting-an-issue)」を参照してください。 | - -## Organization - -| アクション | 説明 | -| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | ユーザが Organization を削除するための背景ジョブを開始しました。 | -| `org.delete` | ユーザが開始したバックグラウンドジョブによって Organization が削除されました。{% ifversion not ghae %} -| `org.transform` | ユーザアカウントが Organization へと変換されました。 詳しい情報については、「[ユーザを Organization に変換する](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)」を参照してください。{% endif %} - -## プルリクエスト - -| Action | Description | | :- | :- |{% ifversion ghes > 3.1 or ghae %} | `pull_request.create` | A pull request was created. 詳しい情報については[プルリクエストの作成](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)を参照してください。 | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.reopen` | A pull request was reopened after previously being closed. | | `pull_request.merge` | A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | | `pull_request.ready_for_review` | A pull request was marked as ready for review. 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)」を参照してください。 | | `pull_request.converted_to_draft` | A pull request was converted to a draft. 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)」を参照してください。 | | `pull_request.create_review_request` | A review was requested on a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request.remove_review_request` | A review request was removed from a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review.submit` | A review was submitted for a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review.dismiss` | A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 | | `pull_request_review.delete` | A review on a pull request was deleted. | | `pull_request_review_comment.create` | A review comment was added to a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %} | `pull_request_review_comment.delete` | A review comment on a pull request was deleted. | - -## 保護されたブランチ - -| アクション | 説明 | -| ------------------------------------------------------------------ | --------------------------------------------------------------- | -| `protected_branch.create` | ブランチ保護がブランチで有効になっています。 | -| `protected_branch.destroy` | ブランチ保護がブランチで無効になっています。 | -| `protected_branch.update_admin_enforced` | ブランチ保護がリポジトリ管理者に対して強制されます。 | -| `protected_branch.update_require_code_owner_review` | 必要なコードオーナーレビューの強制がブランチで更新されます。 | -| `protected_branch.dismiss_stale_reviews` | 却下している古いプルリクエストの強制がブランチで更新されます。 | -| `protected_branch.update_signature_requirement_enforcement_level` | 必要なコミット署名の強制がブランチで更新されます。 | -| `protected_branch.update_pull_request_reviews_enforcement_level` | 必要なプルリクエストレビューの強制がブランチで更新されます。 `0`（無効化）、`1`（非管理者）、`2`（全員）のいずれか。 | -| `protected_branch.update_required_status_checks_enforcement_level` | 必要なステータスチェックの強制がブランチで更新されます。 | -| `protected_branch.rejected_ref_update` | ブランチ更新の試行が拒否されます。 | -| `protected_branch.policy_override` | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされます。 | - -## リポジトリ - -| アクション | 説明 | -| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | リポジトリの可視性がプライベート{% ifversion ghes %}、パブリック、{% endif %} または内部に変更されました。 | -| `repo.archived` | リポジトリがアーカイブされました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。 | -| `repo.add_member` | リポジトリにコラボレーターが追加されました。 | -| `repo.config` | サイト管理者がフォースプッシュをブロックしました。 詳しくは、 [リポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)を参照してください。 | -| `repo.create` | リポジトリが作成されました。 | -| `repo.destroy` | リポジトリが削除されました。 | -| `repo.remove_member` | コラボレーターがリポジトリから削除されました。 | -| `repo.rename` | リポジトリの名前が変更されました。 | -| `repo.transfer` | ユーザーが転送されたリポジトリを受け取る要求を受け入れました。 | -| `repo.transfer_start` | ユーザーがリポジトリを別のユーザーまたは Organization に転送する要求を送信しました。 | -| `repo.unarchived` | リポジトリがアーカイブ解除されました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。{% ifversion ghes %} -| `repo.config.disable_anonymous_git_access` | 匿名 Git 読み取りアクセスがリポジトリに対して無効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | -| `repo.config.enable_anonymous_git_access` | 匿名 Git 読み取りアクセスがリポジトリに対して有効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。 | -| `repo.config.lock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロックされているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できません。 詳しい情報については、「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。 | -| `repo.config.unlock_anonymous_git_access` | リポジトリの匿名 Git 読み取りアクセス設定がロック解除されているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できます。 詳しい情報については、「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。{% endif %} - -{% if secret-scanning-audit-log-custom-patterns %} -## Secret scanning - -| アクション | 説明 | -| ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| | `business_secret_scanning_custom_pattern.create` | Triggered when an enterprise-level custom pattern is published for secret scanning. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-enterprise-account)." | -| | `business_secret_scanning_custom_pattern.update` | Triggered when changes to an enterprise-level custom pattern are saved for secret scanning. | -| | `business_secret_scanning_custom_pattern.delete` | Triggered when an enterprise-level custom pattern is removed from secret scanning. | -{% endif %} - -## サイトアドミンのツール - -| アクション | 説明 | -| ----------------------- | ------------------------------------------------------------------------------------------------------ | -| `staff.disable_repo` | サイトアドミンがリポジトリとその全てのフォークへのアクセスを無効にしました。 | -| `staff.enable_repo` | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghae or ghes > 3.2 %} -| `staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}. | -| `staff.fake_login` | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %} -| `staff.repo_unlock` | サイトアドミンがユーザのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。 | -| `staff.unlock` | サイトアドミンがユーザの全てのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。 | - -## Team - -| アクション | 説明 | -| ------------------------- | --------------------------------------------------------------------------------- | -| `team.create` | ユーザアカウントまたはリポジトリが Team に追加されました。 | -| `team.delete` | A user account or repository was removed from a team.{% ifversion ghes or ghae %} -| `team.demote_maintainer` | ユーザがチームメンテナからチームメンバーに降格されました。{% endif %} -| `team.destroy` | Team が削除されました。{% ifversion ghes or ghae %} -| `team.promote_maintainer` | ユーザーがチームメンバーからチームメンテナに昇格しました。{% endif %} - -## ユーザ - -| アクション | 説明 | -| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | ユーザアカウントにメールアドレスが追加されました。 | -| `user.async_delete` | ユーザアカウントを破棄する非同期ジョブが開始され、最終的に ` user.delete ` がトリガーされました。{% ifversion ghes %} -| `user.change_password` | ユーザがパスワードを変更しました。{% endif %} -| `user.create` | 新規ユーザが作成されました。 | -| `user.delete` | ユーザアカウントが非同期的ジョブによって削除されました。 | -| `user.demote` | サイトアドミンが一般ユーザアカウントに変更されました。 | -| `user.destroy` | ユーザが自分のアカウントを削除し、`user.async_delete` をトリガーしました。{% ifversion ghes %} -| `user.failed_login` | ユーザが間違ったユーザネームやパスワード、または二段階認証コードでサインインしようとしました。 | -| `user.forgot_password` | ユーザがサインインページでパスワードリセットを申請しました。{% endif %} -| `user.login` | ユーザがサインインしました。{% ifversion ghes or ghae %} -| `user.mandatory_message_viewed` | ユーザが必須メッセージを表示します（詳細については、「[ユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください） | {% endif %} -| `user.promote` | 一般ユーザアカウントがサイトアドミンへと変更されました。 | -| `user.remove_email` | ユーザアカウントからメールアドレスが削除されました。 | -| `user.rename` | ユーザ名が変更されました。 | -| `user.suspend` | A user account was suspended by a site admin.{% ifversion ghes %} -| `user.two_factor_requested` | ユーザが 2 要素認証コードを求められました。{% endif %} -| `user.unsuspend` | サイトアドミンがユーザアカウント停止を解除しました。 | - -{% ifversion ghes > 3.1 or ghae %} -## ワークフロー - -{% data reusables.actions.actions-audit-events-workflow %} -{% endif %} - - [add key]: /articles/adding-a-new-ssh-key-to-your-github-account - [デプロイキー]: /guides/managing-deploy-keys/#deploy-keys - [generate token]: /articles/creating-an-access-token-for-command-line-use - [OAuth アクセストークン]: /developers/apps/authorizing-oauth-apps - [OAuth application]: /guides/basics-of-authentication/#registering-your-app - [OAuth アプリケーション]: /guides/basics-of-authentication/#registering-your-app - [2fa]: /articles/about-two-factor-authentication - [2fa]: /articles/about-two-factor-authentication diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md deleted file mode 100644 index 811659c2b6..0000000000 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Enterprise でアクティビティを監視する -intro: You can view activity by leveraging dashboards and logs in your enterprise. -redirect_from: - - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise -versions: - ghec: '*' - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /activity-dashboard - - /audit-logging - - /searching-the-audit-log - - /audited-actions - - /viewing-push-logs - - /log-forwarding - - /managing-global-webhooks -shortTitle: Monitor your enterprise ---- - diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md deleted file mode 100644 index 4a6b9c62dc..0000000000 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -title: グローバルwebhookの管理 -shortTitle: Manage global webhooks -intro: You can configure global webhooks to notify external web servers when events occur within your enterprise. -permissions: Enterprise owners can manage global webhooks for an enterprise account. -redirect_from: - - /enterprise/admin/user-management/about-global-webhooks - - /enterprise/admin/user-management/managing-global-webhooks - - /admin/user-management/managing-global-webhooks - - /admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks - - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account - - /articles/configuring-webhooks-for-organization-events-in-your-business-account - - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account -versions: - ghec: '*' - ghes: '*' - ghae: '*' -type: how_to -topics: - - Enterprise - - Webhooks ---- - -## グローバルwebhookについて - -You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. 詳しい情報については、「[webhook](/developers/webhooks-and-events/webhooks)」を参照してください。 - -For example, you can configure {% data variables.product.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook. - -![グローバル webhook のリスト](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) - -{% data reusables.enterprise_user_management.manage-global-webhooks-api %} - -## グローバルwebhookの追加 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. **Add webhook（webhookの追加）**をクリックしてください。 ![Admin center の webhook ページ上の webhook 追加ボタン](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) -6. ペイロードの受信に使用する URL を入力します。 ![ペイロード URL を入力するフィールド](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) -7. **Content type（コンテントタイプ）**ドロップダウンメニューを使ってペイロードの形式をクリックすることもできます。 ![コンテンツタイプのオプションが並ぶドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) -8. **Secret（秘密）**フィールドに、`secret`キーとして使う文字列を入力することもできます。 ![シークレットキーとして使う文字列を入力するフィールド](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) -9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. SSLの検証に関する情報を読んで、 **I understand my webhooks may not be secure（webhookがセキュアではないかもしれないことを理解しました）**をクリックしてください。 ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) - - {% warning %} - - **警告:** SSL 検証は、フックのペイロードがセキュアにデリバリされることを保証するのに役立ちます。 SSL 検証を無効化することはおすすめしません。 - - {% endwarning %} -10. Decide if you'd like this webhook to trigger for every event or for selected events. ![ペイロードをすべてのイベントあるいは選択されたイベントで受け取る選択肢のラジオボタン](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) - - すべてのイベントの場合は [**Send me everything**] を選択します。 - - 特定のイベントを選択するには [**Let me select individual events**] を選択します。 -11. If you chose to select individual events, select the events that will trigger the webhook. - {% ifversion ghec %} - ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) - {% elsif ghes or ghae %} - ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) - {% endif %} -12. Confirm that the **Active** checkbox is selected. ![選択されたアクティブチェックボックス](/assets/images/help/business-accounts/webhook-active.png) -13. **Add webhook（webhookの追加）**をクリックしてください。 - -## グローバルwebhookの編集 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. 編集したいwebhookの隣の**Edit（編集）**をクリックしてください。 ![webhook の隣の編集ボタン](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) -6. webhookの設定の更新。 -7. **Update webhook（webhookの更新）**をクリックしてください。 - -## グローバルwebhookの削除 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. 削除したいwebhookの隣の**Delete（削除）**をクリックしてください。 ![webhook の隣の削除ボタン](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) -6. webhookの削除に関する情報を読んで、**Yes, delete webhook（はい、webhookを削除します）**をクリックしてください。 ![警告情報のポップアップボックスとwebhookの削除ボタン](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) - -## 最近のデリバリとレスポンスの表示 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. webhook のリストで、デリバリを見たい webhook をクリックします。 ![各 webhook の表示リンクを持つ webhook のリスト](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) -6. [Recent deliveries（最近のデリバリ）] の下で、詳細を表示したいデリバリをクリックしてください。 ![詳細表示へのリンクを持つ最近のwebhookのデリバリリスト](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md deleted file mode 100644 index 9000531219..0000000000 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Audit log を検索する -intro: サイト管理者は、Enterprise で監査されたアクションの広範なリストを検索できます。 -redirect_from: - - /enterprise/admin/articles/searching-the-audit-log - - /enterprise/admin/installation/searching-the-audit-log - - /enterprise/admin/user-management/searching-the-audit-log - - /admin/user-management/searching-the-audit-log -versions: - ghes: '*' - ghae: '*' -type: how_to -topics: - - Auditing - - Enterprise - - Logging ---- - -## 検索クエリの構文 - -AND/ORの論理演算子で区切られた値のペア:1つ以上のキーを使って、検索クエリを構成します。 - -| キー | 値 | -| --------------:| --------------------------------------- | -| `actor_id` | アクションを開始したユーザアカウントの ID | -| `actor` | アクションを開始したユーザアカウントの名前 | -| `oauth_app_id` | アクションに関連付けられている OAuth アプリケーションの ID | -| `action` | 監査されたアクションの名前 | -| `user_id` | アクションによって影響を受けたユーザの ID | -| `ユーザ` | アクションによって影響を受けたユーザの名前 | -| `repo_id` | アクションによって影響を受けたリポジトリの ID （妥当な場合） | -| `repo` | アクションによって影響を受けたリポジトリの名前 （妥当な場合） | -| `actor_ip` | アクション元の IP アドレス | -| `created_at` | アクションが作成された時間 | -| `from` | アクション元の View | -| `note` | イベント固有の他の情報（プレーンテキストまたは JSON フォーマット） | -| `org` | アクションによって影響を受けたOrganizationの名前（該当する場合） | -| `org_id` | アクションによって影響を受けたOrganizationの ID（該当する場合） | - -たとえば、2017 年の初めからリポジトリ `octocat/Spoon-Knife` に影響を与えたすべてのアクションを確認するには、次のようにします: - - `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` - -アクションの完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 - -## Audit log を検索する - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} -4. 検索クエリを入力します。![検索クエリ](/assets/images/enterprise/site-admin-settings/search-query.png) diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index 41ce84e5ec..052cdbfa06 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -33,35 +33,37 @@ shortTitle: Configure dependabot.yml セキュリティアップデートに影響するオプションは、次にセキュリティアラートがセキュリティアップデートのためのプルリクエストをトリガーするときにも使用されます。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)」を参照してください。 -*dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 必要に応じて、最上位に `registries` キーを含めることができます。 ファイルは、`version: 2` で始まる必要があります。 +*dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 You can, optionally, include a top-level `registries` key{% ifversion fpt or ghec or ghes > 3.4 %} and/or a `enable-beta-ecosystems` key{% endif %}. ファイルは、`version: 2` で始まる必要があります。 ## 更新の設定オプション 最上位の `updates` キーは必須です。 これを使用することで、{% data variables.product.prodname_dependabot %} がバージョンやプロジェクトの依存性を更新する方法を設定できます。 各エントリは、特定のパッケージマネージャーの更新設定を行います。 次のオプションを使用できます。 -| オプション | 必須 | 説明 | -|:-------------------------------------------------------------------------- |:-----:|:-------------------------------------------------------------------- | -| [`package-ecosystem`](#package-ecosystem) | **X** | 使用するパッケージマネージャー | -| [`directory`](#directory) | **X** | パッケージマニフェストの場所 | -| [`schedule.interval`](#scheduleinterval) | **X** | 更新を確認する頻度 | -| [`allow`](#allow) | | 許可する更新をカスタマイズする | -| [`assignees`](#assignees) | | プルリクエストのアサイン担当者 | -| [`commit-message`](#commit-message) | | コミットメッセージの環境設定 | -| [`ignore`](#ignore) | | 特定の依存関係またはバージョンを無視する | -| [`insecure-external-code-execution`](#insecure-external-code-execution) | | マニフェストファイル内でコードの実行を許可または拒否する | -| [`labels`](#labels) | | プルリクエストに設定するラベル | -| [`マイルストーン`](#milestone) | | プルリクエストに設定するマイルストーン | -| [`open-pull-requests-limit`](#open-pull-requests-limit) | | バージョン更新時のオープンなプルリクエスト数を制限する | -| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | プルリクエストブランチ名の区切り文字を変更する | -| [`rebase-strategy`](#rebase-strategy) | | 自動リベースを無効にする | -| [`registries`](#registries) | | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ | -| [`レビュー担当者`](#reviewers) | | プルリクエストのレビュー担当者 | -| [`schedule.day`](#scheduleday) | | 更新を確認する曜日 | -| [`schedule.time`](#scheduletime) | | 更新を確認する時刻 (hh:mm) | -| [`schedule.timezone`](#scheduletimezone) | | 時刻のタイムゾーン（ゾーン識別子） | -| [`target-branch`](#target-branch) | | プルリクエストを作成するブランチ | -| [`vendor`](#vendor) | | ベンダーまたはキャッシュされた依存関係を更新する | -| [`versioning-strategy`](#versioning-strategy) | | マニフェストのバージョン要件の更新方法 | +| オプション | 必須 | 説明 | +|:-------------------------------------------------------------------------- |:-----:|:-------------------------------------------------------------------------------------- | +| [`package-ecosystem`](#package-ecosystem) | **X** | 使用するパッケージマネージャー | +| [`directory`](#directory) | **X** | パッケージマニフェストの場所 | +| [`schedule.interval`](#scheduleinterval) | **X** | 更新を確認する頻度 | +| [`allow`](#allow) | | 許可する更新をカスタマイズする | +| [`assignees`](#assignees) | | プルリクエストのアサイン担当者 | +| [`commit-message`](#commit-message) | | Commit message preferences |{% ifversion fpt or ghec or ghes > 3.4 %} +| [`enable-beta-ecosystems`](#enable-beta-ecosystems) | | Enable ecosystems that have beta-level support +{% endif %} +| [`ignore`](#ignore) | | 特定の依存関係またはバージョンを無視する | +| [`insecure-external-code-execution`](#insecure-external-code-execution) | | マニフェストファイル内でコードの実行を許可または拒否する | +| [`labels`](#labels) | | プルリクエストに設定するラベル | +| [`マイルストーン`](#milestone) | | プルリクエストに設定するマイルストーン | +| [`open-pull-requests-limit`](#open-pull-requests-limit) | | バージョン更新時のオープンなプルリクエスト数を制限する | +| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | プルリクエストブランチ名の区切り文字を変更する | +| [`rebase-strategy`](#rebase-strategy) | | 自動リベースを無効にする | +| [`registries`](#registries) | | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ | +| [`レビュー担当者`](#reviewers) | | プルリクエストのレビュー担当者 | +| [`schedule.day`](#scheduleday) | | 更新を確認する曜日 | +| [`schedule.time`](#scheduletime) | | 更新を確認する時刻 (hh:mm) | +| [`schedule.timezone`](#scheduletimezone) | | 時刻のタイムゾーン（ゾーン識別子） | +| [`target-branch`](#target-branch) | | プルリクエストを作成するブランチ | +| [`vendor`](#vendor) | | ベンダーまたはキャッシュされた依存関係を更新する | +| [`versioning-strategy`](#versioning-strategy) | | マニフェストのバージョン要件の更新方法 | これらのオプションは、次のようなカテゴリに幅広く適合しています。 @@ -302,7 +304,6 @@ updates: prefix-development: "pip dev" include: "scope" ``` - ### `ignore` {% data reusables.dependabot.default-dependencies-allow-ignore %} @@ -330,7 +331,7 @@ updates: {% data reusables.dependabot.option-affects-security-updates %} ```yaml -# `ignore`を使って更新されるべきではない依存関係を指定 +# Use `ignore` to specify dependencies that should not be updated version: 2 updates: @@ -340,11 +341,11 @@ updates: interval: "daily" ignore: - dependency-name: "express" - # Expressについてはバージョン4と5に対するすべての更新を無視 + # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # Lodashについてはすべての更新を無視 + # For Lodash, ignore all updates - dependency-name: "lodash" - # AWS SDKについてはすべてのパッチアップデートを無視 + # For AWS SDK, ignore all patch updates - dependency-name: "aws-sdk" update-types: ["version-update:semver-patch"] ``` @@ -356,6 +357,15 @@ updates: {% endnote %} +{% ifversion fpt or ghec or ghes > 3.4 %} +{% note %} + +**Note**: For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available. + +{% endnote %} + +{% endif %} + ### `insecure-external-code-execution` `package-ecosystem` の値が `bundler`、`mix`、および`pip` であるパッケージマネージャーは、バージョン更新プロセスの一環として間にファスト内の外部コードを実行できます。 これにより、セキュリティが侵害されたパッケージが認証情報を盗んだり、構成済みのレジストリにアクセスしたりすることが可能になる場合もあります。 `updates` 設定内で [`registries`](#registries) を追加すると、{% data variables.product.prodname_dependabot %} は自動的に外部コードの実行を防ぎ、この場合はバージョン更新が失敗することもあります。 この動作をオーバーライドし、`bundler`、`mix`、および `pip` パッケージマネージャーで外部コードの実行を許可するには、`insecure-external-code-execution` を `allow` に設定します。 @@ -503,7 +513,7 @@ updates: {% data variables.product.prodname_dependabot %} が `bundler`、`mix`、および `pip` パッケージマネージャーを使用してプライベートレジストリの依存関係を更新できるようにするため、外部コードの実行を許可できます。 For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above. ```yaml -# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries +# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries # when updating dependency versions for this ecosystem {% raw %} @@ -733,11 +743,11 @@ updates: {% raw %} ```yaml -# 1つのプライベートリポジトリ内の依存関係の更新のための最小設定 +# Minimal settings to update dependencies in one private registry version: 2 registries: - dockerhub: # Define access for a private registry + dockerhub: # Define access for a private registry type: docker-registry url: registry.hub.docker.com username: octocat @@ -971,3 +981,23 @@ registries: token: ${{secrets.MY_TERRAFORM_API_TOKEN}} ``` {% endraw %} + +{% ifversion fpt or ghec or ghes > 3.4 %} +## Enabling support for beta-level ecosystems + +### `enable-beta-ecosystems` + +By default, {% data variables.product.prodname_dependabot %} updates the dependency manifests and lock files only for fully supported ecosystems. Use the `enable-beta-ecosystems` flag to opt in to updates for ecosystems that are not yet generally available. + +```yaml +# Configure beta ecosystem + +version: 2 +enable-beta-ecosystems: true +updates: + - package-ecosystem: "pub" + directory: "/" + schedule: + interval: "daily" +``` +{% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index a17ecb06cb..42dfec9464 100644 --- a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -121,10 +121,10 @@ Available in the code scanning alert views. All code scanning alerts have one of Available in the secret scanning alert views. -| 修飾子 | 説明 | -| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `secret-type:SERVICE_PROVIDER` | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." | -| `secret-type:CUSTOM-PATTERN` | Displays alerts for secrets matching the specified custom pattern. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." | +| 修飾子 | 説明 | +| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `secret-type:SERVICE_PROVIDER` | Displays alerts for the specified secret and provider. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." | +| `secret-type:CUSTOM-PATTERN` | Displays alerts for secrets matching the specified custom pattern. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 | ## Filter by provider diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 83b02f5157..5bf91ee3bf 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -50,3 +50,17 @@ Dependency review is available when dependency graph is enabled for {% data vari The dependency review feature becomes available when you enable the dependency graph. For more information, see "{% ifversion ghec %}[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph){% elsif ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% endif %}." {% endif %} + +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6396 %} +## Dependency review enforcement + +{% data reusables.dependency-review.dependency-review-action-beta-note %} + +You can use the Dependency Review GitHub Action in your repository to enforce dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository. For more information, see [`dependency-review-action`](https://github.com/actions/dependency-review-action). + +![Dependency review action example](/assets/images/help/graphs/dependency-review-action.png) + +The Dependency Review GitHub Action check will fail if it discovers any vulnerable package, but will only block a pull request from being merged if the repository owner has required the check to pass before merging. 詳しい情報については、「[保護されたブランチについて](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)」を参照してください。 + +The action uses the Dependency Review REST API to get the diff of dependency changes between the base commit and head commit. You can use the Dependency Review API to get the diff of dependency changes, including vulnerability data, between any two commits on a repository. For more information, see "[Dependency review](/rest/reference/dependency-graph#dependency-review)." +{% endif %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md index c00b8c6ef7..9c7d4e222b 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md @@ -22,10 +22,10 @@ After {% data variables.product.company_short %} creates the owner account for { You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 詳しい情報については、「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)」を参照してください。 ### 4. Managing identity and access for {% data variables.product.product_location %} -You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. 詳しい情報については、「[Enterprise のアイデンティティとアクセス管理について](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)」を参照してください。 +You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. 詳しい情報については、「[Enterprise のアイデンティティとアクセス管理について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)」を参照してください。 ### 5. Managing billing for {% data variables.product.product_location %} -Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." ## Part 2: Organizing and managing enterprise members As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. @@ -52,7 +52,7 @@ As an enterprise owner for {% data variables.product.product_name %}, you can ma To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations. ### 1. Monitoring {% data variables.product.product_location %} -You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)." +You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)." ### 2. Configuring security features for your organizations {% data reusables.getting-started.configuring-security-features %} @@ -66,7 +66,7 @@ You can customize and automate work in organizations in {% data variables.produc ### 2. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)." +For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)." ### 3. {% data variables.product.prodname_pages %}を使用する {% data reusables.getting-started.github-pages-enterprise %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 8ca336b0f7..58bdaef78b 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -67,7 +67,7 @@ To get an enterprise account created for you, contact [{% data variables.product An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 詳細は「[Enterprise アカウントについて](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)」を参照してください。 #### 2. Enterprise アカウントに Organization を追加する -Enterprise アカウント内に、新しい Organization を作成して管理できます。 For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." +Enterprise アカウント内に、新しい Organization を作成して管理できます。 詳しい情報については「[EnterpriseへのOrganizationの追加](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)」を参照してください。 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. #### 3. Enterprise アカウントのプランおよび利用状況を表示する @@ -179,7 +179,7 @@ To manage and moderate your enterprise, you can set policies for organizations w You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." #### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise -You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)." +You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Reviewing audit logs for your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" and "[Monitoring your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)." You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index cc5cc567e7..ce3969eee6 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -72,7 +72,7 @@ You can use {% data variables.product.product_name %}'s built-in authentication You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." ### 2. Staying in compliance -You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)." +You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." {% ifversion ghes %} ### 3. Configuring security features for your organizations diff --git a/translations/ja-JP/content/get-started/using-github/supported-browsers.md b/translations/ja-JP/content/get-started/using-github/supported-browsers.md index abe0f1bc77..4d03130ca2 100644 --- a/translations/ja-JP/content/get-started/using-github/supported-browsers.md +++ b/translations/ja-JP/content/get-started/using-github/supported-browsers.md @@ -6,7 +6,7 @@ redirect_from: - /articles/supported-browsers - /github/getting-started-with-github/supported-browsers - /github/getting-started-with-github/using-github/supported-browsers -intro: '{% data variables.product.product_name %} は、最新の Web ブラウザをサポートするよう設計されています。 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/)、[Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)の現在のバージョンがサポートされています。' +intro: 'For the best experience with {% data variables.product.product_name %}, we recommend using the latest version of [Chrome](https://google.com/chrome), [Edge](https://microsoft.com/windows/microsoft-edge), [Firefox](https://mozilla.org/firefox), or [Safari](https://apple.com/safari).' versions: fpt: '*' ghes: '*' @@ -14,9 +14,28 @@ versions: ghec: '*' --- -## Firefox の延長サポートリリース +## About web browser support for {% data variables.product.product_name %} + +We design {% data variables.product.product_name %} with the latest web browsers in mind. We recommend that you use the latest version of one of the following browsers. + + - [Apple Safari](https://apple.com/safari) + - [Google Chrome](https://google.com/chrome) + - [Microsoft Edge](https://microsoft.com/windows/microsoft-edge) + - [Mozilla Firefox](https://mozilla.org/firefox) + +If you do not use the latest version of a recommended browser, or if you use a browser that is not listed above, {% data variables.product.product_name %} or some features may not work as you expect, or at all. + +For more information about how we maintain browser compatibility for {% data variables.product.company_short %}'s products, see the [`github/browser-support`](https://github.com/github/browser-support) repository. +## Extended support for recommended web browsers + +Some browser vendors provide extended support releases. We do our best to ensure that {% data variables.product.product_name %} functions properly in the latest extended support release for: + +- Chrome's [extended stable channel](https://support.google.com/chrome/a/answer/9027636) +- Edge's [Extended Stable Channel](https://docs.microsoft.com/en-gb/deployedge/microsoft-edge-channels#extended-stable-channel) +- Firefox's [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) + +In earlier extended support releases, {% data variables.product.product_name %} may not work as you expect, and some features may not be available. -弊社は Firefox の最新の[拡張サポートサービス](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) をサポートするのに最善を尽くしています。 Firefox の古いバージョンは、{% data variables.product.product_name %} のいくつかの機能を作動させなくする可能性がありますので、Firefox の最新バージョンが必要です。 ## ベータ版および開発者版 diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md index 9aa5fff7e0..2d050dd6bf 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md @@ -25,7 +25,7 @@ shortTitle: Organization設定へのアクセス {% tip %} -**Tip:** Only organization owners and billing managers can see and change the billing information and the full set of account settings for an organization. Organization moderators only see moderation settings. {% data reusables.organizations.new-org-permissions-more-info %} +**参考:** Organization の支払い情報とアカウント設定全体を見て変更できるのは、Organization のオーナーと支払いマネージャーのみです。 Organizationのモデレーターには、モデレーション設定だけが表示されます。 {% data reusables.organizations.new-org-permissions-more-info %} {% endtip %} diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 07398ecdd3..15c9218d68 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -41,9 +41,9 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} -| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." -| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %} | [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." @@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} -| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes or ghec %} -| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. +| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} | [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | [`project`](#project-category-actions) | Contains all activities related to project boards. @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} ### `dependabot_alerts` category actions | Action | Description @@ -250,7 +250,9 @@ An overview of some of the most common actions that are recorded as events in th |------------------|------------------- | `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. +{% endif %} +{% ifversion fpt or ghec or ghes > 3.2 %} ### `dependabot_security_updates` category actions | Action | Description @@ -516,18 +518,15 @@ For more information, see "[Managing the publication of {% data variables.produc | `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. | `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. -{% ifversion fpt or ghes or ghec %} ### `packages` category actions | Action | Description | |--------|-------------| | `package_version_published` | Triggered when a package version is published. | -| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} -| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} - -{% endif %} +| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} {% ifversion fpt or ghec %} diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 53409418ac..461a58b860 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -35,6 +35,10 @@ shortTitle: Review dependency changes 依存関係のレビューでは、「左にシフト」することができます。 提供された予測情報を使用して、本番環境に至る前に脆弱性のある依存関係をキャッチできます。 詳しい情報については「[依存関係のレビュー](/code-security/supply-chain-security/about-dependency-review)」を参照してください。 +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6396 %} +You can use the Dependency Review GitHub Action to help enforce dependency reviews on pull requests in your repository. For more information, see "[Dependency review enforcement](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)." +{% endif %} + ## プルリクエスト内の依存関係を確認する {% data reusables.repositories.sidebar-pr %} diff --git a/translations/ja-JP/content/rest/reference/dependency-graph.md b/translations/ja-JP/content/rest/reference/dependency-graph.md new file mode 100644 index 0000000000..d7527d5683 --- /dev/null +++ b/translations/ja-JP/content/rest/reference/dependency-graph.md @@ -0,0 +1,16 @@ +--- +title: 依存関係グラフ +intro: 'With the Dependency Graph API, you can view dependency changes and their security impact on your repository.' +versions: + fpt: '*' + ghes: '>=3.6' + ghec: '*' + ghae: issue-6396 +topics: + - API +miniTocMaxHeadingLevel: 3 +--- + + diff --git a/translations/ja-JP/content/rest/reference/index.md b/translations/ja-JP/content/rest/reference/index.md index 4c1aeeb062..78390442cf 100644 --- a/translations/ja-JP/content/rest/reference/index.md +++ b/translations/ja-JP/content/rest/reference/index.md @@ -22,6 +22,7 @@ children: - /collaborators - /commits - /dependabot + - /dependency-graph - /deploy_keys - /deployments - /emojis diff --git a/translations/ja-JP/content/site-policy/github-terms/github-corporate-terms-of-service.md b/translations/ja-JP/content/site-policy/github-terms/github-corporate-terms-of-service.md index a9569da5e4..82609823c0 100644 --- a/translations/ja-JP/content/site-policy/github-terms/github-corporate-terms-of-service.md +++ b/translations/ja-JP/content/site-policy/github-terms/github-corporate-terms-of-service.md @@ -304,7 +304,7 @@ GitHub は、週末および米国の休日を除き、1 日 24時間、週 5 本契約のいずれかの規定が管轄裁判所により違法、無効または執行不能であると判断された場合には、両「当事者」は、当該規定が可能な限り効力を持つように本契約を修正または改正するものとします。 このような修正または改正ができない規定は、削除されたものとみなされ、本契約の残りの規定は、引き続き効力を持つものとします。 ### 6. 修正、完全合意、優先順位 -本「契約」は、GitHub の権限のある代表者が署名した書面による修正、または「セクション T」に従った GitHub による改訂版の投稿によってのみ変更できます。本契約は、関係者間の完全かつ排他的な合意を表しています。 本「契約」は、守秘義務契約または機密保持契約を含むかかる規約の主題に関する口頭または書面による提案または事前の契約、および関係者間のその他の通信に優先します。 本契約の規定と、あらゆる「注文書」または「SOW」との間に万が一矛盾がある場合、その「注文書」または「SOW」に関してのみ、「注文書」または「SOW」の規定が支配するものとします。 +This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by GitHub posting a revised version in accordance with Section R. This Agreement represents the complete and exclusive agreement between the Parties. 本「契約」は、守秘義務契約または機密保持契約を含むかかる規約の主題に関する口頭または書面による提案または事前の契約、および関係者間のその他の通信に優先します。 本契約の規定と、あらゆる「注文書」または「SOW」との間に万が一矛盾がある場合、その「注文書」または「SOW」に関してのみ、「注文書」または「SOW」の規定が支配するものとします。 ### 7. 広報 お客様が、自らのアカウントに、自らの会社または組織の名前を公に表示しているか、プロフィールページに商標やロゴを公に表示している場合、お客様はその会社または組織の名前を、GitHub のお客様として宣伝素材において取り上げることを、GitHub に対して許諾するものとします。 お客様は、企業または組織の名前を公に非表示とし、組織名を宣伝素材において使用することを止めるよう、GitHub に対して書面で通知することにより、この許諾を取り消すことができます。 ただし、宣伝素材で過去に使用または配布したものについて、GitHub はそれらを削除または回収する義務を負いません。 diff --git a/translations/ja-JP/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md b/translations/ja-JP/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md index 426b3845f2..160d27e652 100644 --- a/translations/ja-JP/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md +++ b/translations/ja-JP/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md @@ -128,6 +128,10 @@ GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptab If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHubは、責任を負うことなくGitHubの任意のサブドメインを取得する権利を常に有します。 +## Previews + +Previews means software, online services and additional products and features provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of those, such as alpha, beta, or early access. If your Agreement does not include terms and conditions that address Previews, then the following terms apply. GitHub grants a limited right to use a non-production instance of the Preview. Previews are provided “AS-IS”, “WITH ALL FAULTS” and “AS AVAILABLE”. GitHub may change or discontinue Previews at any time without notice. Any information we give you about a private Preview will be considered GitHub’s confidential information. If you choose to provide comments or suggestions about a Preview, we may use that feedback for any purpose without obligation of any kind. GitHub’s maximum liability is limited to direct damages up to US $5,000. GitHub has no obligation to defend, indemnify, or hold you harmless for claims brought by third parties arising from your use of Previews. + ## Sponsorsプログラム GitHub Sponsorsにより、開発者コミュニティが依存しているオープンソースプロジェクトの設計、構築、維持に携わる人々や Organization を、GitHubで直接、経済的に支援できます。 スポンサード開発者になるには、[GitHub Sponsorsプログラムの追加条項](/github/site-policy/github-sponsors-additional-terms)に同意する必要があります。 diff --git a/translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md index ae27011a29..ccb3ae837e 100644 --- a/translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md @@ -89,7 +89,7 @@ $ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt - `collectd/logs/collectd.log`：Collectdのログ - `mail-logs/mail.log`：SMTPのメール配送ログ -詳細は「[監査ログ](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)」を参照してください。 +For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." Support Bundle には過去 2 日分のログが含まれます。 過去 7 日分のログを取得したい場合には、拡張 Support Bundle をダウンロードできます。 詳細は「[拡張 Support Bundle の作成と共有](#creating-and-sharing-extended-support-bundles)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md new file mode 100644 index 0000000000..a190d3b999 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md @@ -0,0 +1,155 @@ +| カテゴリ名 | 説明 | +| ----- | -- | +| | | +{%- ifversion fpt or ghec %} +| `account` | Contains activities related to an organization account. | `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 +{%- endif %} +| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. +{%- ifversion ghec %} +| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. +{%- endif %} +{%- ifversion fpt or ghec %} +| `billing` | Contains activities related to an organization's billing. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `business` | Contains activities related to business settings for an enterprise. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `business` | Contains activities related to business settings for an enterprise. +{%- endif %} +{%- if secret-scanning-audit-log-custom-patterns %} +| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an enterprise. +{%- endif %} +| `checks` | Contains activities related to check suites and runs. +{%- ifversion fpt or ghec %} +| `codespaces` | Contains activities related to an organization's codespaces. +{%- endif %} +| `commit_comment` | Contains activities related to updating or deleting commit comments. +{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 %} +| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。 | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. +{%- endif %} +{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. +{%- endif %} +{%- ifversion fpt or ghec %} +| `discussion` | Contains activities related to team discussions. | `discussion_comment` | Contains activities related to comments posted in discussions on a team page. | `discussion_post` | Contains activities related to discussions posted to a team page. | `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page. +{%- endif %} +{%- ifversion ghec or ghes %} +| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. | `enterprise` | Contains activities related to enterprise settings. +{%- endif %} +{%- ifversion ghec %} +| `enterprise_domain` | Contains activities related to verified enterprise domains. | `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection. +{%- endif %} +{%- ifversion fpt or ghec %} +| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments. +{%- endif %} +{%- ifversion ghae %} +| `external_group` | Contains activities related to Okta groups. | `external_identity` | Contains activities related to a user in an Okta group. +{%- endif %} +| `git` | Contains activities related to Git events. | `hook` | Contains activities related to webhooks. | `integration` | Contains activities related to integrations in an account. | `integration_installation` | Contains activities related to integrations installed in an account. | `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization. +{%- ifversion ghec or ghae %} +| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization. | `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. +{%- endif %} +| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository. | `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. | `issues` | Contains activities related to enabling or disabling issue creation for an organization. +{%- ifversion fpt or ghec %} +| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}. +{%- endif %} +| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. 詳しい情報については「[Organizationの{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 | `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. | `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization. +{%- ifversion ghec or ghes or ghae %} +| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. +{%- endif %} +{%- ifversion fpt or ghec %} +| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. | `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. +{%- endif %} +| `oauth_access` | Contains activities related to OAuth access tokens. | `oauth_application` | Contains activities related to OAuth Apps. +{%- ifversion fpt or ghec %} +| `oauth_authorization` | Contains activities related to authorizing OAuth Apps. +{%- endif %} +| `org` | Contains activities related to organization membership. +{%- ifversion ghec or ghes or ghae %} +| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. +{%- endif %} +{%- if secret-scanning-audit-log-custom-patterns %} +| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. 詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。 +{%- endif %} +| `organization_default_label` | Contains activities related to default labels for repositories in an organization. +{%- ifversion fpt or ghec or ghes > 3.1 %} +| `organization_domain` | Contains activities related to verified organization domains. | `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.0 or ghae %} +| `packages` | Contains activities related to {% data variables.product.prodname_registry %}. +{%- endif %} +{%- ifversion fpt or ghec %} +| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. | `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. | `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}. +{%- endif %} +{%- ifversion ghes %} +| `pre_receive_environment` | Contains activities related to pre-receive hook environments. | `pre_receive_hook` | Contains activities related to pre-receive hooks. +{%- endif %} +{%- ifversion ghes %} +| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise. +{%- endif %} +| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise. +{%- ifversion fpt or ghec %} +| `profile_picture` | Contains activities related to an organization's profile picture. +{%- endif %} +| `project` | Contains activities related to project boards. | `project_field` | Contains activities related to field creation and deletion in a project board. | `project_view` | Contains activities related to view creation and deletion in a project board. | `protected_branch` | Contains activities related to protected branches. | `public_key` | Contains activities related to SSH keys and deploy keys. +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} +| `pull_request` | Contains activities related to pull requests. | `pull_request_review` | Contains activities related to pull request reviews. | `pull_request_review_comment` | Contains activities related to pull request review comments. +{%- endif %} +| `repo` | Contains activities related to the repositories owned by an organization. +{%- ifversion fpt or ghec %} +| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). | `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 +{%- endif %} +| `repository_image` | Contains activities related images for a repository. | `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization. +{%- ifversion ghec or ghes or ghae %} +| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 +{%- endif %} +{%- if secret-scanning-audit-log-custom-patterns %} +| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. 詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。 +{%- endif %} +{%- ifversion fpt or ghec %} +| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. +{%- endif %} +{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). +{%- endif %} +{%- ifversion fpt or ghec %} +| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. | `required_status_check` | Contains activities related to required status checks for protected branches. +{%- endif %} +{%- ifversion ghec or ghes > 3.1 %} +| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. +{%- endif %} +{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %} +| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `security_key` | Contains activities related to security keys registration and removal. +{%- endif %} +{%- ifversion fpt or ghec %} +| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. | `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources. +{%- endif %} +| `staff` | Contains activities related to a site admin performing an action. | `team` | Contains activities related to teams in an organization. | `team_discussions` | Contains activities related to managing team discussions for an organization. +{%- ifversion ghec %} +| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization. +{%- endif %} +{%- ifversion fpt or ghes %} +| `two_factor_authentication` | Contains activities related to two-factor authentication. +{%- endif %} +{%- ifversion fpt or ghec or ghes or ghae %} +| `user` | Contains activities related to users in an enterprise or organization. +{%- endif %} +{%- ifversion ghec or ghes %} +| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.1 or ghae %} +| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows. +{%- endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md new file mode 100644 index 0000000000..83d408e240 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md @@ -0,0 +1,9 @@ +| アクション | 説明 | +| ----- | -- | +| | | +{%- ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `workflows.approve_workflow_job` | A workflow job was approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | `workflows.cancel_workflow_run` | A workflow run was cancelled. 詳しい情報については「[ワークフローのキャンセル](/actions/managing-workflow-runs/canceling-a-workflow)」を参照してください。 | `workflows.delete_workflow_run` | A workflow run was deleted. 詳しい情報については「[ワークフローの実行の削除](/actions/managing-workflow-runs/deleting-a-workflow-run)」を参照してください。 | `workflows.disable_workflow` | A workflow was disabled. | `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`. | `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | `workflows.rerun_workflow_run` | A workflow run was re-run. 詳しい情報については「[ワークフローの再実行](/actions/managing-workflow-runs/re-running-a-workflow)」を参照してください。 +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %} +| `workflows.completed_workflow_run` | A workflow status changed to `completed`. REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history). | `workflows.created_workflow_run` | A workflow run was created. REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳しい情報については「[サンプルワークフローの作成](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。 | `workflows.prepared_workflow_job` | A workflow job was started. ジョブに渡されたシークレットのリストを含みます。 Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 +{%- endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-operation.md b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-operation.md new file mode 100644 index 0000000000..93b1fd44f5 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-operation.md @@ -0,0 +1,11 @@ +### 操作に基づく検索 + +`operation`修飾子は、アクションを特定の操作の種類に限定するときに使ってください。 例: + + * `operation:access`は、リソースがアクセスされたすべてのイベントを見つけます。 + * `operation:authentication`は認証イベントが生じたすべてのイベントを見つけます。 + * `operation:create`は、リソースが作成されたすべてのイベントを見つけます。 + * `operation:modify`は、リソースが修正されたすべてのイベントを見つけます。 + * `operation:remove`は、既存のリソースが削除されたすべてのイベントを見つけます。 + * `operation:restore`は、既存のリソースがリストアされたすべてのイベントを見つけます。 + * `operation:transfer`は既存のリソースが移譲されたすべてのイベントを見つけます。 diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-repo.md b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-repo.md new file mode 100644 index 0000000000..b3781b9f75 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-repo.md @@ -0,0 +1,9 @@ +### リポジトリに基づく検索 + +`repo`修飾子は、アクションを特定のリポジトリに限定するときに使ってください。 例: + + * `repo:my-org/our-repo`は`my-org` Organization内の`our-repo`リポジトリで起きたすべてのイベントを検索します。 + * `repo:my-org/our-repo repo:my-org/another-repo`は、`my-org` Organization内の`our-repo`及び`another-repo`の両リポジトリ内で起きたすべてのイベントを検索します。 + * `-repo:my-org/not-this-repo`は、`my-org` Organization内の`not-this-repo`リポジトリで起きたすべてのイベントを除外します。 + +`repo` 修飾子内にアカウント名を加える必要があることに注意してください。 `repo:our-repo` だけを検索しても機能しません。 diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-user.md b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-user.md new file mode 100644 index 0000000000..fd425580d5 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-search-by-user.md @@ -0,0 +1,9 @@ +### ユーザーに基づく検索 + +`actor`修飾子は、アクションを実行した人に基づいてイベントの範囲を指定できます。 例: + + * `actor:octocat`は`octocat`が行ったすべてのイベントを検索します。 + * `actor:octocat actor:hubot`は、`octocat`及び`hubot`が行ったすべてのイベントを検索します。 + * `-actor:hubot`は、`hubot`が行ったすべてのイベントを除外します。 + +使用できるのは {% data variables.product.product_name %} のユーザー名のみであり、個人の実名ではないことに注意してください。 diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-search-list-info-about-action.md b/translations/ja-JP/data/reusables/audit_log/audit-log-search-list-info-about-action.md new file mode 100644 index 0000000000..b47a12544e --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-search-list-info-about-action.md @@ -0,0 +1,11 @@ +The name for each audit log entry is composed of the `action` object or category qualifier, followed by an operation type. For example, the `repo.create` entry refers to the `create` operation on the `repo` category. + +各 Audit log エントリには、次のようなイベントに関する適切な情報が表示されます: + +- The {% ifversion ghec or ghes or ghae %}enterprise or {% endif %}organization an action was performed in +- The user (actor) who performed the action +- The user affected by the action +- アクションの対象となったリポジトリ +- 実行されたアクション +- アクションが実行された国 +- アクションが発生した日時 diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-search.md b/translations/ja-JP/data/reusables/audit_log/audit-log-search.md index 8bd93933c4..d129bb2a9c 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-log-search.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-search.md @@ -1,41 +1,9 @@ -ログには、それぞれのアクションに関する以下の情報があります。 - -* アクションの対象となったリポジトリ -* アクションを実行したユーザ -* 実行されたアクション -* アクションが実行された国 -* アクションが発生した日時 +{% data reusables.audit_log.audit-log-search-list-info-about-action %} テキストを使用してエントリを検索することはできません。 ただし、さまざまなフィルターを使用すれば検索クエリを作成できます。 ログを検索するときに使用される多くの演算子 (`-`、`>`、`<` など) は、{% data variables.product.product_name %} 全体で検索するものと同じ形式です。 詳細は「[{% data variables.product.prodname_dotcom %} での検索](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 -### 操作に基づく検索 +{% data reusables.audit_log.audit-log-search-by-operation %} -`operation`修飾子は、アクションを特定の操作の種類に限定するときに使ってください。 例: +{% data reusables.audit_log.audit-log-search-by-repo %} - * `operation:access`は、リソースがアクセスされたすべてのイベントを見つけます。 - * `operation:authentication`は認証イベントが生じたすべてのイベントを見つけます。 - * `operation:create`は、リソースが作成されたすべてのイベントを見つけます。 - * `operation:modify`は、リソースが修正されたすべてのイベントを見つけます。 - * `operation:remove`は、既存のリソースが削除されたすべてのイベントを見つけます。 - * `operation:restore`は、既存のリソースがリストアされたすべてのイベントを見つけます。 - * `operation:transfer`は既存のリソースが移譲されたすべてのイベントを見つけます。 - -### リポジトリに基づく検索 - -`repo`修飾子は、アクションを特定のリポジトリに限定するときに使ってください。 例: - - * `repo:my-org/our-repo`は`my-org` Organization内の`our-repo`リポジトリで起きたすべてのイベントを検索します。 - * `repo:my-org/our-repo repo:my-org/another-repo`は、`my-org` Organization内の`our-repo`及び`another-repo`の両リポジトリ内で起きたすべてのイベントを検索します。 - * `-repo:my-org/not-this-repo`は、`my-org` Organization内の`not-this-repo`リポジトリで起きたすべてのイベントを除外します。 - -`repo` 修飾子内にアカウント名を加える必要があることに注意してください。 `repo:our-repo` だけを検索しても機能しません。 - -### ユーザーに基づく検索 - -`actor`修飾子は、アクションを実行した人に基づいてイベントの範囲を指定できます。 例: - - * `actor:octocat`は`octocat`が行ったすべてのイベントを検索します。 - * `actor:octocat actor:hubot`は、`octocat`及び`hubot`が行ったすべてのイベントを検索します。 - * `-actor:hubot`は、`hubot`が行ったすべてのイベントを除外します。 - -使用できるのは {% data variables.product.product_name %} のユーザー名のみであり、個人の実名ではないことに注意してください。 +{% data reusables.audit_log.audit-log-search-by-user %} diff --git a/translations/ja-JP/data/reusables/audit_log/audited-data-list.md b/translations/ja-JP/data/reusables/audit_log/audited-data-list.md index a9327d6e85..282c3ca009 100644 --- a/translations/ja-JP/data/reusables/audit_log/audited-data-list.md +++ b/translations/ja-JP/data/reusables/audit_log/audited-data-list.md @@ -1,2 +1,2 @@ {% data reusables.audit_log.audit-log-api-info %} -* クローン、フェッチ、プッシュなどの Git イベント +{% ifversion fpt or ghec %}* Git events, such as cloning, fetching, and pushing{% endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/exported-git-log-keys-and-values.md b/translations/ja-JP/data/reusables/audit_log/exported-git-log-keys-and-values.md new file mode 100644 index 0000000000..e3708ddb4c --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/exported-git-log-keys-and-values.md @@ -0,0 +1,13 @@ +ログをJSONあるいはCSVとしてエクスポートすると、出力されたファイルには以下のキーと値があります。 + +| キー | 値の例 | +| ------------------- | ---------------------- | +| `@timestamp` | 1429548104000 | +| `actor` | octocat | +| `action` | git.clone | +| `org` | octo-org | +| `business` | avocado-corp | +| `repo` | octo-org/documentation | +| `repository_public` | false | +| `ユーザ` | codertocat | +| `protocol_name` | http | diff --git a/translations/ja-JP/data/reusables/audit_log/exported-log-keys-and-values.md b/translations/ja-JP/data/reusables/audit_log/exported-log-keys-and-values.md index 1e1b172bac..b07cf25e3d 100644 --- a/translations/ja-JP/data/reusables/audit_log/exported-log-keys-and-values.md +++ b/translations/ja-JP/data/reusables/audit_log/exported-log-keys-and-values.md @@ -1,16 +1,18 @@ -ログをJSONあるいはCSVとしてエクスポートすると、出力されたファイルには以下のキーと値があります。 +After you export the log, you'll see the following keys and values in the resulting file. -| キー | 値の例 | -| ------------------- | ------------------------------------------------------------------------------ | -| `action` | team.create | -| `actor` | octocat | -| `ユーザ` | codertocat | -| `org` | octo-org | -| `repo` | octo-org/documentation | -| `created_at` | 1429548104000 (タイムスタンプは Epoch からの経過時間をミリ秒で示します。) | -| `data.hook_id` | 245 | -| `data.events` | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] | -| `data.events_were` | ["push", "pull_request", "issues"] | -| `data.target_login` | octocat | -| `data.old_user` | hubot | -| `data.team` | octo-org/engineering | +| キー | 値の例 | +| ----------------------------- | ------------------------------------------------------------------------------ | +| `action` | team.create | +| `actor` | octocat | +| `ユーザ` | codertocat | +| `actor_location.country_code` | US | +| `org` | octo-org | +| `repo` | octo-org/documentation | +| `created_at` | 1429548104000 (タイムスタンプは Epoch からの経過時間をミリ秒で示します。) | +| `data.email` | octocat@nowhere.com | +| `data.hook_id` | 245 | +| `data.events` | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] | +| `data.events_were` | ["push", "pull_request", "issues"] | +| `data.target_login` | octocat | +| `data.old_user` | hubot | +| `data.team` | octo-org/engineering | diff --git a/translations/ja-JP/data/reusables/audit_log/retention-periods.md b/translations/ja-JP/data/reusables/audit_log/retention-periods.md new file mode 100644 index 0000000000..dbed08d376 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/retention-periods.md @@ -0,0 +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.{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %} + +{% data reusables.audit_log.only-three-months-displayed %} diff --git a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md index 67d3f14952..4c468c1daf 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -4,27 +4,35 @@ - プライベートの{% data variables.product.prodname_dotcom %}リポジトリあるいはレジストリ内の依存関係がサポートされているか - ベンダーの依存関係がサポートされているか -| パッケージマネージャー | YAML値 | サポートされているバージョン | プライベートリポジトリ | プライベートレジストリ | ベンダー | -| -------------- | ---------------- | -------------------------- |:-----------:|:-----------:|:-----:| -| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | -| Cargo | `cargo` | v1 | **✓** | **✓** | | -| Composer | `composer` | v1, v2 | **✓** | **✓** | | -| Docker | `docker` | v1 | **✓** | **✓** | | -| Hex | `mix` | v1 | | **✓** | | -| elm-package | `elm` | v0.19 | **✓** | **✓** | | -| Gitサブモジュール | `gitsubmodule` | N/A (バージョンなし) | **✓** | **✓** | | -| GitHub Actions | `github-actions` | N/A (バージョンなし) | **✓** | **✓** | | -| Goモジュール | `gomod` | v1 | **✓** | **✓** | **✓** | -| Gradle | `gradle` | N/A（バージョンなし）[1] | **✓** | **✓** | | -| Maven | `maven` | N/A（バージョンなし）[2] | **✓** | **✓** | | -| npm | `npm` | v6, v7, v8 | **✓** | **✓** | | -| NuGet | `nuget` | <= 4.8[3] | **✓** | **✓** | | -| pip | `pip` | v21.1.2 | | **✓** | | -| pipenv | `pip` | <= 2021-05-29 | | **✓** | | -| pip-compile | `pip` | 6.1.0 | | **✓** | | -| poetry | `pip` | v1 | | **✓** | | -| Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | -| yarn | `npm` | v1 | **✓** | **✓** | | +| パッケージマネージャー | YAML値 | サポートされているバージョン | プライベートリポジトリ | プライベートレジストリ | ベンダー | +| -------------- | ---------------- | -------------------------- |:-----------:|:-----------:|:------------------------------------------:| +| Bundler | `bundler` | v1, v2 | | **✓** | **✓** | +| Cargo | `cargo` | v1 | **✓** | **✓** | | +| Composer | `composer` | v1, v2 | **✓** | **✓** | | +| Docker | `docker` | v1 | **✓** | **✓** | | +| Hex | `mix` | v1 | | **✓** | | +| elm-package | `elm` | v0.19 | **✓** | **✓** | | +| Gitサブモジュール | `gitsubmodule` | N/A (バージョンなし) | **✓** | **✓** | | +| GitHub Actions | `github-actions` | N/A (バージョンなし) | **✓** | **✓** | | +| Goモジュール | `gomod` | v1 | **✓** | **✓** | **✓** | +| Gradle | `gradle` | N/A（バージョンなし）[1] | **✓** | **✓** | | +| Maven | `maven` | N/A（バージョンなし）[2] | **✓** | **✓** | | +| npm | `npm` | v6, v7, v8 | **✓** | **✓** | | +| NuGet | `nuget` | <= 4.8[3] | **✓** | **✓** | | +| pip | `pip` | v21.1.2 | | **✓** | | +| pipenv | `pip` | <= 2021-05-29 | | **✓** | | +| pip-compile | `pip` | 6.1.0 | | **✓** | | +| poetry | `pip` | v1 | | **✓** | |{% ifversion fpt or ghec or ghes > 3.4 %} +| pub | `pub` | v2 [4] | | | +{% endif %} +| Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | +| yarn | `npm` | v1 | **✓** | **✓** | | + +{% tip %} + +**Tip:** For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. たとえばPythonの依存関係を管理するのに`poetry`を使っており、{% data variables.product.prodname_dependabot %}に新しいバージョンのために依存関係のマニフェストファイルをモニターさせたい場合は、*dependabot.yml*ファイル中で`package-ecosystem: "pip"`を使ってください。 + +{% endtip %} [1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). @@ -32,4 +40,8 @@ [3] {% data variables.product.prodname_dependabot %}はNuGet CLIを実行しませんが、バージョン4.8までのほとんどの機能をサポートします。 -`pipenv`や`poetry`といったパッケージマネージャでは、`pip`のYAML値を使う必要があります。 たとえばPythonの依存関係を管理するのに`poetry`を使っており、{% data variables.product.prodname_dependabot %}に新しいバージョンのために依存関係のマニフェストファイルをモニターさせたい場合は、*dependabot.yml*ファイル中で`package-ecosystem: "pip"`を使ってください。 +{% ifversion fpt or ghec or ghes > 3.4 %}[4] `pub` support is currently in beta. Any known limitations are subject to change. Note that {% data variables.product.prodname_dependabot %}: + - Doesn't support updating git dependencies for `pub`. + - Won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available. + + For information about configuring your _dependabot.yml_ file for `pub`, see "[Enabling support for beta-level ecosystems](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)." {% endif %} diff --git a/translations/ja-JP/data/reusables/dependency-review/dependency-review-action-beta-note.md b/translations/ja-JP/data/reusables/dependency-review/dependency-review-action-beta-note.md new file mode 100644 index 0000000000..c227b119b0 --- /dev/null +++ b/translations/ja-JP/data/reusables/dependency-review/dependency-review-action-beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note**: The Dependency Review GitHub Action is currently in public beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/dependency-review/dependency-review-api-beta-note.md b/translations/ja-JP/data/reusables/dependency-review/dependency-review-api-beta-note.md new file mode 100644 index 0000000000..d93a217cd8 --- /dev/null +++ b/translations/ja-JP/data/reusables/dependency-review/dependency-review-api-beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note**: The Dependency Review API is currently in public beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise/link-to-ghe-trial.md b/translations/ja-JP/data/reusables/enterprise/link-to-ghe-trial.md new file mode 100644 index 0000000000..c85fcbf7a9 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise/link-to-ghe-trial.md @@ -0,0 +1 @@ +For more information about how you can try {% data variables.product.prodname_enterprise %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)" and "[Setting up a trial of {% data variables.product.prodname_ghe_server %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)." diff --git a/translations/ja-JP/data/reusables/gated-features/more-info-org-products.md b/translations/ja-JP/data/reusables/gated-features/more-info-org-products.md index e6c5d81c39..55f6679e7b 100644 --- a/translations/ja-JP/data/reusables/gated-features/more-info-org-products.md +++ b/translations/ja-JP/data/reusables/gated-features/more-info-org-products.md @@ -1 +1 @@ -{% ifversion fpt or ghec %}詳しい情報については「[{% data variables.product.prodname_dotcom %}の製品](/articles/github-s-products)」を参照してください。{% endif %} +{% ifversion fpt or ghec %}詳しい情報については「[{% data variables.product.prodname_dotcom %}の製品](/get-started/learning-about-github/githubs-products)」を参照してください。{% endif %} diff --git a/translations/ja-JP/data/reusables/rest-reference/dependency-graph/dependency-review.md b/translations/ja-JP/data/reusables/rest-reference/dependency-graph/dependency-review.md new file mode 100644 index 0000000000..be1d47323a --- /dev/null +++ b/translations/ja-JP/data/reusables/rest-reference/dependency-graph/dependency-review.md @@ -0,0 +1,5 @@ +## 依存関係のレビュー + +{% data reusables.dependency-review.dependency-review-api-beta-note %} + +The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." \ No newline at end of file diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index 11c12f769e..2a4ba73ee5 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -53,6 +53,7 @@ translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from- translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md,broken liquid tags translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags +translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error translations/ja-JP/content/admin/overview/system-overview.md,broken liquid tags translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags @@ -66,6 +67,7 @@ translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hook translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags diff --git a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index d101b290dd..044e0c2506 100644 --- a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -71,6 +71,14 @@ Os segredos armazenados em um ambiente só estão disponíveis para trabalhos de {% data reusables.actions.permissions-statement-environment %} +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.actions.sidebar-environment %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index d650204f54..65cbe28ae3 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -58,10 +58,10 @@ O serviço {% data variables.product.prodname_actions %} irá cancelar o resgist Por padrão, os executores auto-hospedados realizarão automaticamente uma atualização de software sempre que uma nova versão do executor estiver disponível. Se você usar executoresefêmeros em contêineres, isso pode gerar a atualizações de software repetidas quando uma nova versão do executor for lançada. A desabilitação das atualizações automáticas permite que você atualize a versão do executor na imagem do contêiner diretamente no seu próprio agendamento. -Se você deseja desativar as atualizações automáticas de software e instalar as atualizações de software, você poderá especificar o parâmetro `--disableupdate` ao iniciar o executor. Por exemplo: +To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. Por exemplo: ```shell -./run.sh --disableupdate +./config.sh --url https://github.com/octo-org --token example-token --disableupdate ``` Se você desabilitar as atualizações automáticas, você ainda deverá atualizar sua versão do executor regularmente. A nova funcionalidade em {% data variables.product.prodname_actions %} exige alterações no serviço de {% data variables.product.prodname_actions %} service _e_ no software do executor. O executor pode não conseguir de processar corretamente os trabalhos que aproveitam novas funcioanlidades em {% data variables.product.prodname_actions %} sem a atualização de um software. diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index 3ce9d66fb5..9ca8f2897f 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -48,6 +48,12 @@ Para ajudar a prevenir a divulgação acidental, o {% data variables.product.pro - **Considere a necessidade de revisão para acesso a segredos** - Você pode usar revisores necessários para proteger os segredos do ambiente. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por um revisor. Para mais informações sobre armazenar segredos em ambientes ou exigir revisões para ambientes, consulte "[segredos criptografados](/actions/reference/encrypted-secrets)" e "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". +{% warning %} + +**Warning**: Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required. + +{% endwarning %} + ## Usar `CODEOWNERS` para monitorar alterações Você pode usar o recurso `CODEOWNERS` para controlar como são feitas alterações nos seus arquivos de fluxo de trabalho. Por exemplo, se todos os arquivos de fluxo de trabalho forem armazenados em `.github/workflows`, você pode adicionar este diretório à lista de proprietários do código para que quaisquer alterações propostas nestes arquivos exijam primeiro a aprovação de um revisor designado. @@ -298,7 +304,7 @@ Você pode usar o log de auditoria para monitorar tarefas administrativas em uma Por exemplo, você pode usar o log de auditoria para acompanhar o evento `org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) -As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)" and "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)." +As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre o uso do log de auditoria, consulte "[Revisando o log de auditoria para sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)" e "[Revisando logs de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)." {% ifversion fpt or ghec %} ### Eventos para ambientes @@ -316,7 +322,7 @@ As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_a | Ação | Descrição | | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `repo.actions_enabled` | Acionada quando {% data variables.product.prodname_actions %} está habilitado para um repositório. Pode ser visto usando a interface do usuário. Este evento não fica visível quando você acessar o log de auditoria usando a API REST. Para obter mais informações, consulte "[Usar a API REST](#using-the-rest-api)". | -| `repo.update_actions_access_settings` | Triggered when the setting to control how your repository is used by {% data variables.product.prodname_actions %} workflows in other repositories is changed. | +| `repo.update_actions_access_settings` | Acionada quando a configuração de controle de como o repositório é usado pelos fluxos de trabalho {% data variables.product.prodname_actions %} em outros repositórios é alterada. | {% endif %} ### Eventos para gerenciamento de segredo diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md index 7545d987f9..c2e01d3614 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -214,7 +214,7 @@ Cria uma mensagem de aviso e a imprime no log. {% data reusables.actions.message {% data reusables.actions.message-parameters %} -### Example: Setting a warning message +### Exemplo: Configurando uma mensagem de aviso {% bash %} @@ -241,7 +241,7 @@ Cria uma mensagem de erro e a imprime no log. {% data reusables.actions.message- {% data reusables.actions.message-parameters %} -### Example: Setting an error message +### Exemplo: Configurando uma mensagem de erro {% bash %} @@ -268,7 +268,7 @@ Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo ::endgroup:: ``` -### Example: Grouping log lines +### Exemplo: Agrupamento de linhas de log {% bash %} @@ -310,9 +310,9 @@ jobs: ::add-mask::{value} ``` -Mascarar um valor evita que uma string ou variável seja impressa no log. Cada palavra mascarada separada por espaço em branco é substituída pelo caractere `*`. Você pode usar uma variável de ambiente ou string para o `value` da máscara. Quando você mascara um valor, ele é tratado como um segredo e será redatado no executor. For example, after you mask a value, you won't be able to set that value as an output. +Mascarar um valor evita que uma string ou variável seja impressa no log. Cada palavra mascarada separada por espaço em branco é substituída pelo caractere `*`. Você pode usar uma variável de ambiente ou string para o `value` da máscara. Quando você mascara um valor, ele é tratado como um segredo e será redatado no executor. Por exemplo, depois de você mascarar um valor, você nãopoderá configurar esse valor como uma saída. -### Example: Masking a string +### Exemplo: Mascarando uma string Quando você imprime `"Mona The Octocat"` no log, você verá `"***"`. @@ -332,7 +332,7 @@ Write-Output "::add-mask::Mona The Octocat" {% endpowershell %} -### Example: Masking an environment variable +### Exemplo: Mascarando uma variável de ambiente Ao imprimir a variável `MY_NAME` ou o valor `"Mona The Octocat"` no log, você verá `"***"` em vez de `"Mona The Octocat"`. @@ -689,7 +689,7 @@ echo "$HOME/.local/bin" >> $GITHUB_PATH {% endbash %} -This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`: +Este exemplo demonstra como adicionar o diretório do usuário `$env:HOMEPATH/.local/bin` a `PATH`: {% powershell %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 10f71e3518..6cccf09662 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -17,11 +17,11 @@ topics: Se configurar um nome de host em vez de um endereço IP codificado, você poderá alterar o hardware físico em que a {% data variables.product.product_location %} é executada sem afetar os usuários ou o software cliente. -A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. +A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. Por exemplo, a configuração do nome de host pode ser `github.companyname.com.`As solicitações da web e da API serão automaticamente redirecionadas para o nome de host configurado no {% data variables.enterprise.management_console %}. -After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". +Depois de configurar um nome de host, você poderá habilitar o isolamento de subdomínio para aumentar ainda mais a segurança de {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". -For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). +Para obter mais informações sobre os tipos de nome de host compatíveis, consulte a [seção 2.1 do HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} @@ -33,4 +33,4 @@ For more information on the supported hostname types, see [Section 2.1 of the HT {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". +Para ajudar a mitigar várias vulnerabilidades de script entre sites, recomendamos que você habilite o isolamento de subdomínio para {% data variables.product.product_location %} depois de configurar um nome de host. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 3be49f6c74..c2906df017 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -115,7 +115,7 @@ Permite encontrar o identificador universalmente exclusivo (UUID) do seu nó em ``` {% ifversion ghes %} -Permite isentar uma lista de usuários do limite de taxa de da API. Um limite rígido de 120.000 solicitações ainda será aplicado a esses usuários. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)". +Allows you to exempt a list of users from REST API rate limits. Um limite rígido de 120.000 solicitações ainda será aplicado a esses usuários. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)". ``` shell $ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions" diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index 3162fee7fd..cc7c888a97 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -61,22 +61,22 @@ Se o isolamento de subdomínio estiver desabilitado para sua empresa, você tamb {% ifversion ghes > 3.4 %} -## Configuring {% data variables.product.prodname_pages %} response headers for your enterprise +## Configurando cabeçalhos de resposta de {% data variables.product.prodname_pages %} para a sua empresa -You can add or override response headers for {% data variables.product.prodname_pages %} sites hosted by {% data variables.product.product_location %}. +Você pode adicionar ou substituir os cabeçalhos de resposta para sites de {% data variables.product.prodname_pages %} hospedados por {% data variables.product.product_location %}. {% warning %} -**Warning:** Ensure that your response headers are properly configured before saving. Improper configurations may negatively impact the security of {% data variables.product.product_location %}. +**Aviso:** Certifique-se de que seus cabeçalhos de resposta estão corretamente configurados antes de salvar. As configurações impróprias podem impactar negativamente a segurança de {% data variables.product.product_location %}. {% endwarning %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -1. Type the headers settings, then click **Add headers**. - - In the **Http Header Name** field, type the header name. The length of header name should less than 128 characters. - - In the **Http Header Value** field, type the header value. The length of header value should less than 300 characters. ![The {% data variables.product.prodname_pages %} response header name and value fields in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png) +1. Digite as configurações de cabeçalhos e, em seguida, clique em **Adicionar cabeçalhos**. + - No campo **Http Header Name**, digite o nome do cabeçalho. O comprimento do nome do cabeçalho deve ter menos de 128 caracteres. + - No campo **Http Header Value** , digite o valor do cabeçalho. O comprimento do balor do cabeçalho deve ter menos de 300 caracteres. ![O nome do cabeçalho de resposta de {% data variables.product.prodname_pages %} e os campos de valor em {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png) {% data reusables.enterprise_management_console.save-settings %} {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md index 06f29ff383..f5af65a765 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Gerenciando o GitHub Mobile para a sua empresa -intro: 'You can decide whether people can use {% data variables.product.prodname_mobile %} to connect to {% data variables.product.product_location %}.' +intro: 'Você pode decidir se as pessoas podem usar {% data variables.product.prodname_mobile %} para se conectar a {% data variables.product.product_location %}.' permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for a {% data variables.product.product_name %} instance.' versions: ghes: '*' @@ -16,14 +16,14 @@ shortTitle: Gerenciar o GitHub Mobile ## Sobre o {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} allows people to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device after successful authentication. {% data reusables.mobile.about-mobile %} Para obter mais informações, consulte "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)". +{% data variables.product.prodname_mobile %} permite às pessoas testar, colaborar e gerenciar trabalhos em {% data variables.product.product_location %} por meio de um dispositivo móvel após a autenticação bem-sucedida. {% data reusables.mobile.about-mobile %} Para obter mais informações, consulte "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)". -You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is{% ifversion ghes > 3.3 %} enabled for people who use {% data variables.product.product_location %}.{% else %} not enabled for people who use {% data variables.product.product_location %}. To allow connection to your instance with {% data variables.product.prodname_mobile %}, you must enable the feature for your instance.{% endif %} +Você pode permitir ou impedir que as pessoas usem {% data variables.product.prodname_mobile %} para efetuar a autenticação em {% data variables.product.product_location %} e acessar os dados da sua instância. Por padrão, {% data variables.product.prodname_mobile %} é{% ifversion ghes > 3.3 %} habilitado para pessoas que usam {% data variables.product.product_location %}.{% else %} não habilitado para pessoas que usam {% data variables.product.product_location %}. Para permitir conexão com a sua instância com {% data variables.product.prodname_mobile %}, você deve habilitar o recurso para a sua instância.{% endif %} {% ifversion ghes < 3.6 and ghes > 3.1 %} {% note %} -**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." +**Observação:** Se você fizer a atualização para {% data variables.product.prodname_ghe_server %} 3.4. ou posterior e não tiver previamente desabilitado ou habilitado {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} será habilitado por padrão. Se você desabilitou ou habilitou {% data variables.product.prodname_mobile %} anteriormente para a sua instância, a sua preferência será preservada após a atualização. Para obter mais informações sobre como atualizar sua instância, consulte "[Atualizando {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)". {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md index b9b4180c3c..e77739227f 100644 --- a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md +++ b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/about-repository-caching.md @@ -16,6 +16,6 @@ Um cache de repositório elimina a necessidade de {% data variables.product.prod O cache do repositório escuta a instância principal, seja uma instância única ou um conjunto de instâncias replicadas georreplicado, para alterações nos dados do Git. As farms de CI e outros consumidores muito pesados clonam e buscam do cache do repositório em vez da instância primária. As alterações são propagadas na rede, em intervalos periódicos, uma vez por instância de cache ao invés de uma vez por cliente. Os dados do Git normalmente serão visíveis no cache do repositório dentro de alguns minutos após os dados serem enviados para a instância primária. {% ifversion ghes > 3.3 %}O webhook [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) pode ser usado por sistemas de CI para reagir a dados que estão disponíveis no cache.{% endif %} -Você tem controle refinado sobre quais repositórios estão autorizados a sincronizar com o cache do repositório. Git data will only be replicated to the locations you specify. +Você tem controle refinado sobre quais repositórios estão autorizados a sincronizar com o cache do repositório. Os dados do Git só serão replicados nos locais que você especificar. {% data reusables.enterprise.repository-caching-config-summary %} Para obter mais informações, consulte "[Configurando um cache do repositório](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)". diff --git a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index 558aa65a89..2b018ddda0 100644 --- a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -69,11 +69,11 @@ Em seguida, quando for dito para buscar `https://github.example.com/myorg/myrepo Você pode controlar a localidade de dados configurando as políticas de localização de dados para seus repositórios com o comando `spokesctl cache-policy` As políticas de localização de dados determinam quais redes de repositório são replicadas em quais caches de repositório. Por padrão, nenhuma rede de repositório será replicada em todos os caches de repositórios até que uma política de localização de dados seja configurada. -Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy. +As políticas de localização de dados afetam apenas o conteúdo do Git. O conteúdo no banco de dados, como problemas e comentários de pull request, serão replicados em todos os nós independentemente da política. {% note %} -**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +**Observação:** As políticas de localização de dados não são as mesmas que o controle de acesso. Você deve usar as funções do repositório para controlar quais usuários podem acessar um repositório. Para obter mais informações sobre as funções do repositório, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". {% endnote %} diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index 54c752c8a2..2faf9b9fdd 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -19,9 +19,9 @@ O tempo do failover dependerá do tempo necessário para promover manualmente a {% data reusables.enterprise_installation.promoting-a-replica %} -1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode. +1. Se o dispositivo primário estiver disponível, para permitir que a replicação termine antes de trocar os dispositivos, no dispositivo primário, coloque o dispositivo primário em modo de manutenção. - - Put the appliance into maintenance mode. + - Coloque o dispositivo em modo de manutenção. - Para usar o console de gerenciamento, consulte "[Habilitar e programar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"; @@ -44,7 +44,7 @@ O tempo do failover dependerá do tempo necessário para promover manualmente a $ ghe-repl-status -vv ``` -4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. A ação também colocará automaticamente o nó primário no nó de manutenção, se ele for acessível. +4. No dispositivo da réplica, para parar a replicação e promover o dispositivo da réplica ao estado primário, use o comando `ghe-repl-promote`. A ação também colocará automaticamente o nó primário no nó de manutenção, se ele for acessível. ```shell $ ghe-repl-promote ``` diff --git a/translations/pt-BR/content/admin/enterprise-management/index.md b/translations/pt-BR/content/admin/enterprise-management/index.md index 5702e8a0d5..33c75fe484 100644 --- a/translations/pt-BR/content/admin/enterprise-management/index.md +++ b/translations/pt-BR/content/admin/enterprise-management/index.md @@ -13,6 +13,6 @@ children: - /configuring-clustering - /configuring-high-availability - /caching-repositories -shortTitle: 'Monitor, manage, and update your appliance' +shortTitle: 'Monitorar, gerenciar e atualizar seu dispositivo' --- diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md index a756fc4d5b..692ceb7d9a 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md @@ -1,6 +1,6 @@ --- -title: About system logs -intro: '{% data variables.product.product_name %} keeps error and message logs for system events. Logs are useful for identifying user, application and system-level actions and exceptions.' +title: Sobre os registros do sistema +intro: '{% data variables.product.product_name %} mantém registros de erros e mensagens para eventos do sistema. Os registros são úteis para identificar exceções e ações de usuário, aplicação e nível de sistema.' versions: ghes: '*' type: overview @@ -11,35 +11,35 @@ topics: - Security --- -## System logs +## Registros do sistema -By default, system logs for {% data variables.product.product_name %} are automatically rotated every 24 hours and are retained for seven days. System logs include system-level events, application logs, and Git events data. As log files are often being written to and can be large in size, it may be beneficial to extract and parse relevant log entries on a host separate to your {% data variables.product.prodname_ghe_server %} instance. +Por padrão, os registros do sistema para {% data variables.product.product_name %} são girados automaticamente a cada 24 horas e são retidos por sete dias. Os registros do sistema incluem eventos em nível de sistema, registros de aplicativos e dados de eventos do Git. Como os arquivos de registro são normalmente gravados e podem ser grandes, pode ser benéfico extrair e analisar entradas de registros relevantes em um host separado pela sua instância {% data variables.product.prodname_ghe_server %}. -You can forward system logs to a third-party system or server for longer retention. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)". +Você pode encaminhar registros do sistema para um sistema de terceiros ou servidor para retenção mais longa. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)". -In addition to reviewing your system logs, you can monitor activity in your enterprise in other ways, such as viewing audit logs, push logs and managing global webhooks. Para obter mais informações, consulte "[Atividade de monitoramento na sua empresa](/admin/monitoring-activity-in-your-enterprise)". +Além de analisar os logs do sistema, você pode monitorar as atividades na sua empresa de outras formas, como ver logs de auditoria, registros de push e gerenciar webhooks globais. Para obter mais informações, consulte "[Atividade de monitoramento na sua empresa](/admin/monitoring-activity-in-your-enterprise)". -## Types of logs +## Tipos de registros -Listed below are the main logs used by the {% data variables.product.product_name %} appliance and their functions: +Abaixo estão listados os principais registros usados pelo dispositivo de {% data variables.product.product_name %} e suas funções: | Caminho | Descrição​ | | -------------------------------- | ----------------------------------------------------------------------------- | -| `/var/log/github/audit.log` | Audited user, repository and system events. | -| `/var/log/github/unicorn.log` | API and web interface traffic. | -| `/var/log/github/exceptions.log` | Application-level errors. | -| `/var/log/haproxy.log` | All IP traffic reaching the appliance. | -| `/var/log/hookshot/resqued.log` | Webhook delivery and failures. | -| `/var/log/github/auth.log` | Authentication requests, whether through built in, LDAP, CAS or SAML methods. | -| `/var/log/github/gitauth.log` | All Git authentication requests. | +| `/var/log/github/audit.log` | Eventos de usuário, repositório e sistema auditados. | +| `/var/log/github/unicorn.log` | API e o tráfego da interface web. | +| `/var/log/github/exceptions.log` | Erros no nível do aplicativo. | +| `/var/log/haproxy.log` | Todo o tráfego IP que chega ao dispositivo. | +| `/var/log/hookshot/resqued.log` | Entrega de webhook e falhas. | +| `/var/log/github/auth.log` | Solicita autenticação, seja através de métodos integrados, LDAP, CAS ou SAML. | +| `/var/log/github/gitauth.log` | Todos os pedidos de autenticação do Git. | -Git activity and authentication requests are processed by the `babeld` service. +As solicitações de atividade e autenticação do Git são processadas pelo serviço `babeld`. -Several {% data variables.product.product_name %} services, such as the `babeld` service, are containerized. Containerized logs are written to the `systemd journal`, and can be queried at any time using the `journalctl` command. +Vários serviços de {% data variables.product.product_name %}, como o serviço de `babeld` estão em contêineres. Os registros armazenados em contêiner são gravados em `systemd` e podem ser consultados a qualquer momento usando o comando `journalctl`. -## Audited system events +## Eventos do sistema auditado -All entries from the `audit.log` file use and can be filtered with the `github_audit` keyword. +Todas as entradas do `audit.log` usam e podem ser filtradas com a palavra-chave `github_audit`. Por exemplo, esta entrada mostra que um repositório foi criado. @@ -55,8 +55,8 @@ Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program": ## Pacotes de suporte -The support bundle includes system logs and all audit information is logged to the `audit.log` file in the `github-logs` directory. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/support/contacting-github-support/providing-data-to-github-support)." +O pacote de suporte inclui logs de sistema e todas as informações de auditoria são registradas no arquivo `audit.log` no diretório `github-logs`. Para obter mais informações, consulte "[Fornecer dados para suporte de {% data variables.product.prodname_dotcom %}](/support/contacting-github-support/providing-data-to-github-support)." ## Leia mais -- [Linux man page for the `journalctl` command](http://man7.org/linux/man-pages/man1/journalctl.1.html) +- [A página de man do Linux para o comando `journalctl`](http://man7.org/linux/man-pages/man1/journalctl.1.html) diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index f9ffb53343..0c7a487e9e 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -28,7 +28,7 @@ Como alternativa, você pode usar máquinas de executores que {% data variables. Este guia mostra como aplicar uma abordagem de gerenciamento centralizada para os executores auto-hospedados para {% data variables.product.prodname_actions %} na sua empresa. No guia, você realizará as seguintes tarefas. -1. Configure a limited policy to restrict the actions{% if actions-workflow-policy %} and reusable workflows{% endif %} that can run within your enterprise +1. Configure uma política limitada para restringir as ações{% if actions-workflow-policy %} e fluxos de trabalho{% endif %} reutilizáveis que podem ser executados dentro da sua empresa 1. Implantar um executor auto-hospedado para a sua empresa 1. Criar um grupo para gerenciar o acesso aos executores disponíveis para sua empresa 1. Opcionalmente, restringir ainda mais os repositórios que podem usar o executor @@ -48,7 +48,7 @@ Depois de terminar o guia, {% ifversion ghec or ghae %}os integrantes da sua emp ## 1. Configurar políticas para {% data variables.product.prodname_actions %} -First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% if actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.product.product_location %}{% endif %}. Opcionalmente, os proprietários da organização podem restringir ainda mais essas políticas para cada organização. +Primeiro, habilite {% data variables.product.prodname_actions %} para todas as organizações e configure uma política para restringir as ações{% if actions-workflow-policy %} e os fluxos de trabalho reutilizáveis{% endif %} que podem executar {% ifversion ghec or ghae%}dentro da sua empresa em {% data variables.product.product_name %}{% elsif ghes %}em {% data variables.product.product_location %}{% endif %}. Opcionalmente, os proprietários da organização podem restringir ainda mais essas políticas para cada organização. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -56,7 +56,7 @@ First, enable {% data variables.product.prodname_actions %} for all organization 1. Em "Políticas", selecione **Habilitar para todas as organizações**. ![Captura de tela da política "Habilitar para todas as organizações" para {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-enable-for-all-organizations.png) -1. Select {% data reusables.actions.policy-label-for-select-actions-workflows %} and **Allow actions created by GitHub** to allow local actions{% if actions-workflow-policy %} and reusable workflows{% endif %}, and actions created by {% data variables.product.company_short %}. +1. Selecione {% data reusables.actions.policy-label-for-select-actions-workflows %} e **Permitir ações criadas pelo GitHub** para permitir ações locais{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %}, e ações criadas por {% data variables.product.company_short %}. {% if actions-workflow-policy %} ![Captura de tela de "Permitir selecionar ações" e "Permitir ações criadas por {% data variables.product.company_short %}" para {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png) diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 9504b5018f..07191544a4 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -26,9 +26,9 @@ Antes de apresentar {% data variables.product.prodname_actions %} a uma grande e Você deve criar um plano para reger o uso de {% data variables.product.prodname_actions %} da empresa e cumprir suas obrigações de conformidade. -Determine which actions {% if actions-workflow-policy %}and reusable workflows{% endif %} your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions {% if actions-workflow-policy %}and reusable workflows{% endif %} from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)". +Determine quais ações {% if actions-workflow-policy %}e fluxos de trabalho reutilizáveis{% endif %} seus desenvolvedores poderão usar. {% ifversion ghes %}Primeiro, decida se você vai permitir o acesso às ações {% if actions-workflow-policy %}e aos fluxos de trabalho reutilizáveis{% endif %} de fora de sua instância. {% data reusables.actions.access-actions-on-dotcom %} Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)". -Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions {% if actions-workflow-policy %}and reusable workflows{% endif %} that were not created by {% data variables.product.company_short %}. You can configure the actions {% if actions-workflow-policy %}and reusable workflows{% endif %} that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions{% if actions-workflow-policy %} and reusable workflows{% endif %}, you can limit allowed actions to those created by verified creators or a list of specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/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)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/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)." +Em seguida,{% else %}Primeiro,{% endif %} decide se você permitirá ações de terceiros {% if actions-workflow-policy %}e fluxos de trabalho reutilizáveis{% endif %} que não foram criados por {% data variables.product.company_short %}. Você pode configurar as ações {% if actions-workflow-policy %}e os fluxos de trabalho reutilizáveis{% endif %} que podem ser executados no repositório, nos níveis da organização e da empresa e pode optar por permitir apenas ações criadas por {% data variables.product.company_short %}. Se você permitir ações de terceiros{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %}, você poderá limitar as ações permitidas para as criadas por criadores verificados ou uma lista de ações específicas{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %}. Para obter mais informações, consulte "[Gerenciando as configurações de {% data variables.product.prodname_actions %} para um repositório](/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)", "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)" e "[Aplicando políticas de {% data variables.product.prodname_actions %} na sua empresa](/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)." {% if actions-workflow-policy %} ![Captura de tela das políticas de {% data variables.product.prodname_actions %}](/assets/images/help/organizations/enterprise-actions-policy-with-workflows.png) @@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions Considere combinar o OpenID Connect (OIDC) com fluxos de trabalho reutilizáveis para aplicar implantações consistentes no seu repositório, organização ou empresa. Você pode fazer isso definindo condições de confiança nas funções da nuvem com base em fluxos de trabalho reutilizáveis. Para obter mais informações, consulte "["Usando o OpenID Connect com fluxos de trabalho reutilizáveis"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows). {% endif %} -Você pode acessar informações sobre atividades relacionadas ao {% data variables.product.prodname_actions %} nos logs de auditoria da sua empresa. Se a sua empresa tiver de manter os logs de auditoria por mais de seis meses, planeje como você exportará e armazenará esses dados fora de {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[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)" and "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."{% else %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %} +Você pode acessar informações sobre atividades relacionadas ao {% data variables.product.prodname_actions %} nos logs de auditoria da sua empresa. Se a sua empresa tiver de manter os logs de auditoria por mais de seis meses, planeje como você exportará e armazenará esses dados fora de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte {% ifversion ghec %}"[Transmitindo o log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" e "[Exportando atividade de log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise).{% else %}"[Encaminhamento de registro](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %} ![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png) diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index ad4520308f..4af65033cb 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -29,7 +29,7 @@ Para atualizar as ações agrupadas, você pode usar a ferramenta `actions-sync` Você pode usar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} use ações a partir do {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". -Uma vez configurado {% data variables.product.prodname_github_connect %}, você poderá usar a última versão de uma ação, excluindo seu repositório local nas `ações` da organização na sua instância. For example, if your enterprise instance is using `v1` of the `actions/checkout` action, and you need to use `{% data reusables.actions.action-checkout %}` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: +Uma vez configurado {% data variables.product.prodname_github_connect %}, você poderá usar a última versão de uma ação, excluindo seu repositório local nas `ações` da organização na sua instância. Por exemplo, se sua instância corporativa estiver usando `v1` da ação `ações/checkout`, e você precisa usar `{% data reusables.actions.action-checkout %}`, que não está disponível na instância corporativa, execute as seguintes etapas para poder usar a última ação `checkout` de {% data variables.product.prodname_dotcom_the_website %}: 1. Em uma conta de proprietário corporativo em {% data variables.product.product_name %}, acesse o repositório que você deseja excluir da organização *ações* (neste exemplo `checkout`). 1. Por padrão, os administradores do site não são proprietários da organização de *ações* agrupadas. Para obter o acesso necessário para excluir o repositório de `checkout`, você deve usar as ferramentas de administrador do site. Clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página do repositório. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) @@ -39,8 +39,8 @@ Uma vez configurado {% data variables.product.prodname_github_connect %}, você 1. Agora que o repositório está desbloqueado, você pode sair das páginas de administrador do site e excluir o repositório dentro das `ações da organização`. Na parte superior da página, clique no nome do repositório, neste exemplo **check-out**, para retornar à página de resumo. ![Link para nome do repositório](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) 1. Em "Informações do repositório", clique em **Ver código** para sair das páginas de administração do site e exibir o repositório `check-out`. 1. Exclua o repositório do `check-out` dentro organização das `ações`. Para obter informações sobre como excluir um repositório, consulte "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)". ![Ver link de código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) -1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. -1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. +1. Configure o YAML do seu fluxo de trabalho para usar `{% data reusables.actions.action-checkout %}`. +1. Cada vez que o seu fluxo de trabalho é executado, o executor usará a versão especificada `ações/checkout` de {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes > 3.2 or ghae-issue-4815 %} {% note %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md index d88073aa78..23bb68c5f4 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md @@ -1,6 +1,6 @@ --- -title: Exploring user activity in your enterprise -intro: 'You can view user and system activity by leveraging dashboards, webhooks and log forwarding.' +title: Explorando a atividade do usuário em sua empresa +intro: 'Você pode visualizar as atividades do usuário e do sistema utilizando painéis, webhooks e encaminhamentos de logs.' versions: ghec: '*' ghes: '*' @@ -12,6 +12,6 @@ children: - /viewing-push-logs - /log-forwarding - /managing-global-webhooks -shortTitle: Explore user activity +shortTitle: Explorar atividade do usuário --- diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/index.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/index.md index a631d51d51..fa12881bf3 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/index.md @@ -1,6 +1,6 @@ --- title: Monitorar atividades na sua empresa -intro: 'You can view user and system activity by leveraging audit logs{% ifversion ghes or ghae %}, push logs, dashboards, webhooks, and log forwarding{% else %}and webhooks{% endif %}.' +intro: 'Você pode ver as atividades de usuário e sistema aproveitando os logs de auditoria{% ifversion ghes or ghae %}, puslgos de push, painéis, webhooks e o encaminhamento de registros{% else %}e webhooks{% endif %}.' redirect_from: - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance versions: @@ -12,6 +12,6 @@ topics: children: - /reviewing-audit-logs-for-your-enterprise - /exploring-user-activity -shortTitle: Monitor activity +shortTitle: Monitorar atividade --- diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md index 2d34b9df41..158dcac4c5 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: About the audit log for your enterprise -intro: 'To support debugging and internal and external compliance, {% data variables.product.product_name %} provides logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events.' -shortTitle: About audit logs +title: Sobre o log de auditoria da sua empresa +intro: 'Para suportar depuração e conformidade interna e externa, {% data variables.product.product_name %} fornece logs de sistema auditado{% ifversion ghes %} ,{% endif %} usuário, organização e eventos de repositórios.' +shortTitle: Sobre os logs de auditoria redirect_from: - /enterprise/admin/articles/audit-logging - /enterprise/admin/installation/audit-logging @@ -23,39 +23,39 @@ topics: - Security --- -## About audit logs +## Sobre os logs de auditoria {% data reusables.audit_log.retention-periods %} {% data reusables.audit_log.audit-log-search-list-info-about-action %} -In addition to viewing your audit log, you can monitor activity in your enterprise in other ways, such as {% ifversion ghes or ghae %}viewing push logs and {% endif %}managing global webhooks. For more information, see "[Exploring user activity in your enterprise](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity)." +Além de visualizar seu registro de auditoria, você pode monitorar atividades na sua empresa de outras formas, tais como {% ifversion ghes or ghae %}visualizando os logs de push e {% endif %}gerenciando webhooks globais. Para obter mais informações, consulte "[Explorando atividades de usuário na sua empresa](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity)". -## Using your audit logs +## Usando seus logs de auditoria -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 "[Accessing the audit log for your enterprise](/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 "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}. +Como proprietário corporativo{% ifversion ghes %} ou administrador do site{% endif %}, você pode interagir com os dados do log de auditoria na sua empresa de várias maneiras: +- Você pode visualizar o log de auditoria da sua empresa. Para obter mais informações, consulte[Acessando o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)". +- Você pode pesquisar eventos específicos no log de auditoria{% ifversion ghec %} e exportar dados de log de auditoria{% endif %}. Para obter mais informações, consulte "[Pesquisando o log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} e "[Exportando o log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}. {%- ifversion ghec %} -- Você pode transmitir dados de auditoria e eventos do Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados. 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)." +- Você pode transmitir dados de auditoria e eventos do Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados. Para obter mais informações, consulte[Transmitindo o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)". {%- else %} -- You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)". +- Você pode encaminhar logs de auditoria e sistema, da sua empresa para um sistema de monitoramento hospedado por terceiros. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)". {%- endif %} {%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} -- You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." +- Você pode usar a API do log de auditoria para visualizar as ações realizadas na sua empresa. Para obter mais informações, consulte[Usando a API do log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)". {%- endif %} -For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." +Para obter uma lista completa de ações de log de auditoria que podem aparecer no log de auditoria da sua empresa, consulte "[Ações de log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)". {% ifversion ghec %} -## Git events +## Eventos do Git -Git events data, such as cloning, fetching, and pushing is logged. 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)." +Os dados de eventos do Git, como clonar, buscar e fazer push são registrados. Para obter mais informações, consulte[Transmitindo o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)". {% endif %} ## Leia mais - "[Revisar o log de auditoria da organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" {%- ifversion ghes %} -- "[About system logs](/admin/enterprise-management/monitoring-your-appliance/about-system-logs)" +- "[Sobre os logs do sistema](/admin/enterprise-management/monitoring-your-appliance/about-system-logs)" {%- endif %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md index 0a0be317ee..94058d53dd 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Accessing the audit log for your enterprise -intro: You can view aggregated actions from all of the organizations owned by an enterprise account in the enterprise's audit log. -shortTitle: Access audit logs +title: Acessando o log de auditoria para a sua empresa +intro: Você pode ver as ações agregadas de todas as organizações pertencentes a uma conta corporativa no log de auditoria da empresa. +shortTitle: Acessar logs de auditoria permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can access the audit log.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index b71cb6f507..6beb6446ec 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Audit log events for your enterprise -intro: Learn about audit log events recorded for your enterprise. -shortTitle: Audit log events +title: Log de eventos de auditoria para sua empresa +intro: Saiba mais sobre os eventos de log de auditoria registrados para sua empresa. +shortTitle: Eventos de log de auditoria permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.' miniTocMaxHeadingLevel: 4 redirect_from: @@ -25,56 +25,56 @@ topics: {%- ifversion fpt or ghec %} ### ações de categoria da `conta` -| Ação | Descrição | -| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `account.billing_plan_change` | An organization's billing cycle changed. Para obter mais informações, consulte "[Alterando a duração do seu ciclo de cobrança](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)". | -| `account.plan_change` | An organization's subscription changed. For more information, see "[About billing for GitHub accounts](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)." | -| `account.pending_plan_change` | An organization owner or billing manager canceled or downgraded a paid subscription. Para obter mais informações, consulte "[Como a atualização ou o downgrade afeta o processo de cobrança?](/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process)." | -| `account.pending_subscription_change` | A {% data variables.product.prodname_marketplace %} free trial started or expired. For more information, see "[About billing for GitHub Marketplace](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace)." | +| Ação | Descrição | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `account.billing_plan_change` | O ciclo de cobrança de uma organização foi alterado. Para obter mais informações, consulte "[Alterando a duração do seu ciclo de cobrança](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)". | +| `account.plan_change` | A assinatura de uma organização foi alterada. Para obter mais informações, consulte[Sobre a cobrança para contas do GitHub](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)". | +| `account.pending_plan_change` | Um proprietário ou gerente de cobrança da organização cancelou ou rebaixou uma assinatura paga. Para obter mais informações, consulte "[Como a atualização ou o downgrade afeta o processo de cobrança?](/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process)." | +| `account.pending_subscription_change` | Um teste gratuito de {% data variables.product.prodname_marketplace %} foi iniciado ou venceu. Para obter mais informações, consulte[Sobre a cobrança para o GitHub Marketplace](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace)". | {%- endif %} {%- ifversion fpt or ghec %} ### ações de categoria de `advisory_credit` -| Ação | Descrição | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `advisory_credit.accept` | Someone accepted credit for a security advisory. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory)". | -| `advisory_credit.create` | The administrator of a security advisory added someone to the credit section. | -| `advisory_credit.decline` | Someone declined credit for a security advisory. | -| `advisory_credit.destroy` | The administrator of a security advisory removed someone from the credit section. | +| Ação | Descrição | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `advisory_credit.accept` | Alguém aceitou o crédito por uma consultoria de segurança. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory)". | +| `advisory_credit.create` | O administrador de uma consultoria de segurança adicionou alguém à seção de crédito. | +| `advisory_credit.decline` | Alguém recusou o crédito para uma consultoria de segurança. | +| `advisory_credit.destroy` | O administrador de uma consultoria de segurança removeu alguém da seção de crédito. | {%- endif %} -### `artifact` category actions +### Ações de categoria `artefato` -| Ação | Descrição | -| ------------------ | --------------------------------------------- | -| `artifact.destroy` | A workflow run artifact was manually deleted. | +| Ação | Descrição | +| ------------------ | ---------------------------------------------------------------------- | +| `artifact.destroy` | Um artefato da execução de fluxo de trabalho foi excluído manualmente. | {%- ifversion ghec %} -### `audit_log_streaming` category actions +### Ações da categoria `audit_log_streaming` -| Ação | Descrição | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | -| `audit_log_streaming.check` | A manual check was performed of the endpoint configured for audit log streaming. | -| `audit_log_streaming.create` | An endpoint was added for audit log streaming. | -| `audit_log_streaming.update` | An endpoint configuration was updated for audit log streaming, such as the stream was paused, enabled, or disabled. | -| `audit_log_streaming.destroy` | An audit log streaming endpoint was deleted. | +| Ação | Descrição | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `audit_log_streaming.check` | Foi realizada uma verificação manual do ponto de extremidae configurado para transmissão de logs de auditoria. | +| `audit_log_streaming.create` | Um ponto de extremidade foi adicionado ao streaming do log de auditoria. | +| `audit_log_streaming.update` | Uma configuração de ponto de extremidade foi atualizada para a transmissão do log de auditoria, como a transmissão foi pausada, habilitada ou desabilitada. | +| `audit_log_streaming.destroy` | Um ponto de extremidade da transmissão do log auditoria foi excluído. | {%- endif %} {%- ifversion fpt or ghec %} ### ações de categoria de `cobrança` -| Ação | Descrição | -| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `billing.change_billing_type` | An organization changed how it paid for {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)". | -| `billing.change_email` | An organization's billing email address changed. Para obter mais informações, consulte "[Configurar o e-mail de cobrança](/billing/managing-your-github-billing-settings/setting-your-billing-email)". | +| Ação | Descrição | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing.change_billing_type` | Uma organização alterou a forma como pagou por {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)". | +| `billing.change_email` | O endereço de e-mail de cobrança de uma organização foi alterado. Para obter mais informações, consulte "[Configurar o e-mail de cobrança](/billing/managing-your-github-billing-settings/setting-your-billing-email)". | {%- endif %} ### ações da categoria `business` -| Ação | Descrição | -| -------------------- | ---------------------------------------------------------------------------------------------------- | -| `business.add_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was added to an enterprise. | +| Ação | Descrição | +| -------------------- | ---------------------------------------------------------------------------------------------------------------- | +| `business.add_admin` | Um proprietário da empresa{% ifversion ghes %} ou administrador do site{% endif %} foi adicionado a uma empresa. | {%- ifversion ghec %} | `business.add_billing_manager` | A billing manager was added to an enterprise. {%- endif %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md index d72e6d063b..4acc3720b7 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Exporting audit log activity for your enterprise -intro: You can export audit and Git events data to a file for offline analysis. -shortTitle: Export audit logs +title: Exportando a atividade de log de auditoria da sua empresa +intro: Você pode exportar dados de eventos de auditoria e do Git para um arquivo para análise off-line. +shortTitle: Exportar logs de auditoria permissions: Enterprise owners can export the audit log. miniTocMaxHeadingLevel: 3 versions: @@ -13,38 +13,38 @@ topics: - Logging --- -## About exports of audit log and Git events data +## Sobre exportações de dados de registros de auditoria e eventos do Git -You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)." +Você pode exportar o log de auditoria fazendo o download de um arquivo do JSON ou CSV da sua empresa em {% data variables.product.product_name %}. Ao exportar eventos do log de auditoria, você pode consultar por um ou mais desses classificadores para filtrar eventos de log específicos para exportação. Para obter mais informações sobre os qualificadores de pesquisa, consulte "[Pesquisa baseada na ação executada](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed). -You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface. +Você pode exportar dados de eventos Git fazendo o download de um arquivo JSON do log de auditoria da empresa. Ao contrário dos dados de log de auditoria, você não pode consultar eventos específicos do Git para filtrar e exportar na interface do usuário do log de auditoria. {% data reusables.audit_log.exported-log-keys-and-values %} -As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" and "[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)." +Como alternativa à exportação de eventos de log, você pode usar a API para recuperar os eventos de log de auditoria ou configurar {% data variables.product.product_name %} para transmitir dados de auditoria quando os eventos forem registrados. Para obter mais informações, consulte "[Usando a API de registro de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" e "[Transmitindo o registro de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)". -## Exporting audit log data +## Exportando dados de log de auditoria {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters. -2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in. +1. Opcionalmente, apenas para exportar resultados filtrados, pesquise um ou mais qualificadores ou filtros de log. +2. Selecione o menu suspenso {% octicon "download" aria-label="The Download icon" %} **Exportar** e escolha o formato de arquivo (JSON ou CSV) para exportar eventos de log. ![Botão de exportação](/assets/images/help/organizations/org-audit-log-export.png) -## Exporting Git events data +## Exportando dados de eventos do Git -You can also export Git events data by date range. +Você também pode exportar dados de eventosdo Git por intervalo de datas. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for. +1. Selecione o menu suspenso {% octicon "download" aria-label="The Download icon" %} **Exportar eventos do Git** e escolha um intervalo de datas para exportar eventos de registro. - ![Export Git events button](/assets/images/help/organizations/org-audit-log-export-git-events.png) -1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file. -1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. Por exemplo: + ![Exportar botão de eventos do Git](/assets/images/help/organizations/org-audit-log-export-git-events.png) +1. Clique em {% octicon "file-zip" aria-label="The File-zip icon" %} **Fazer o download dos resultados** para fazer o download do arquivo. +1. Os dados são exportados como um arquivo JSON comprimido. Para extrair os dados do JSON, descompacte o arquivo usando um cliente de utilitário do arquiv ou comando. Por exemplo: ``` gunzip export-avocado-corp-1642896556.json.gz diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md index d554271aaa..ca332060f5 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md @@ -1,7 +1,7 @@ --- -title: Reviewing audit logs for your enterprise -intro: You can view user and system activity in the audit logs for your enterprise. -shortTitle: Review audit logs +title: Revisando logs de auditoria para sua empresa +intro: Você pode visualizar as atividades de usuário e sistema nos logs de auditoria da sua empresa. +shortTitle: Revisar logs de auditoria versions: ghec: '*' ghes: '*' diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md index c3613203ae..16a4e11442 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Searching the audit log for your enterprise -intro: You can search an extensive list of audited actions in your enterprise. -shortTitle: Search audit logs +title: Pesquisando o log de auditoria para a sua empresa +intro: Você pode pesquisar uma extensa lista de ações auditadas em sua empresa. +shortTitle: Pesquisar logs de auditoria permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can search the audit log.' redirect_from: - /enterprise/admin/articles/searching-the-audit-log @@ -21,15 +21,15 @@ topics: miniTocMaxHeadingLevel: 3 --- -## About search for the enterprise audit log +## Sobre a pesquisa do log de auditoria da empresa -You can search your enterprise audit log directly from the user interface by using the **Filters** dropdown, or by typing a search query. +Você pode pesquisar o log de auditoria da empresa diretamente a partir da interface do usuário, usando o menu suspenso **Filtros** ou digitando uma consulta de pesquisa. ![Consulta de pesquisa](/assets/images/enterprise/site-admin-settings/search-query.png) -For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." +Para obter mais informações sobre como visualizar o seu log de auditoria corporativa, consulte[Acessando o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)". -You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." +Você também pode usar a API para recuperar os eventos de log de auditoria. Para obter mais informações, consulte[Usando a API do log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)". Observe que não é possível pesquisar as entradas usando texto. No entanto, é possível criar consultas de pesquisa usando diversos filtros. Muitos operadores usados ao consultar o log de auditoria, como `-`, `>`, ou `<`, correspondem ao mesmo formato de pesquisa no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." @@ -39,18 +39,18 @@ Observe que não é possível pesquisar as entradas usando texto. No entanto, é {% endnote %} -## Search query filters +## Filtros de consulta de pesquisa -| Filtrar | Descrição | -| -------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Yesterday's activity` | All actions created in the past day. | -| `Enterprise account management` | All actions in the `business` category. | -| `Associação à organização` | All actions for when a new user was invited to join an organization. | -| `Team management` | All actions related to team management.
- When a user account or repository was added or removed from a team
- When a team maintainer was promoted or demoted
- When a team was deleted | -| `Repository management` | All actions for repository management.
- When a repository was created or deleted
- When the repository visibility was changed
- When a team was added or removed from a repository{% ifversion ghec %} -| `Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %} -| `Hook activity` | All actions for webhooks and pre-receive hooks. | -| `Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories. | +| Filtrar | Descrição | +| ------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Actividade de ontem` | Todas as ações criadas no dia anterior. | +| `Gestão de conta corporativa` | Todas as ações na categoria `negócios`. | +| `Associação à organização` | Todas as ações para quando um novo usuário foi convidado a participar de uma organização. | +| `Gestão de equipe` | Todas as ações relacionadas ao gerenciamento de equipe.
- Quando a conta de um usuário ou repositório foi adicionads ou removids de uma equipe
- Quando um mantenedor de equipe foi promovido ou rebaixado
- Quando uma equipe foi excluída | +| `Gerenciamento do repositório` | Todas as ações para o gerenciamento de repositório.
- Quando um repositório foi criado ou excluído
- Quando a visibilidade do repositório foi alterada
- Quando uma equipe foi adicionada ou removida de um repositório{% ifversion ghec %} +| `Atualizações de cobrança` | Todas as ações sobre como sua empresa paga por {% data variables.product.prodname_dotcom %} e quando seu endereço de e-mail de cobrança foi alterado.{% endif %} +| `Atividade do hook` | Todas as ações para webhooks e hooks pre-receive. | +| `Gerenciamento de segurança` | Todas as ações referentes a chaves SSH, chaves de implantação, chaves de segurança, 2FA e logon único SAML e alertas de vulnerabilidade para repositórios. | ## Sintaxe de consulta de pesquisa diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index da88d635d1..b3d03a1964 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Streaming the audit log for your enterprise +title: Transmissão do log de auditoria para a sua empresa intro: 'Você pode transmitir dados de auditoria e eventos do Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados.' miniTocMaxHeadingLevel: 3 versions: @@ -10,7 +10,7 @@ topics: - Enterprise - Logging - Organizations -shortTitle: Stream audit logs +shortTitle: Transmitir logs de auditoria redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account @@ -26,7 +26,7 @@ Os benefícios do streaming de dados de auditoria incluem: * **Exploração de dados**. Você pode examinar eventos transmitidos usando sua ferramenta preferida para consultar grandes quantidades de dados. A transmissão contém eventos de auditoria e Git em toda a conta corporativa. * **Continuidade dos dados**. Você pode pausar a transmissão por até sete dias sem perder nenhum dado da auditoria. -* **Retenção de dados**. You can keep your exported audit logs and Git events data as long as you need to. +* **Retenção de dados**. Você pode manter seus registros de auditoria exportados e dados de eventos do Git se precisar. Os proprietários das empresas podem configurar, pausar ou excluir uma transmissão a qualquer momento. A transmissão exporta os dados de auditoria para todas as organizações da sua empresa. diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md index 11cd9ecfe9..a4514d4c43 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Using the audit log API for your enterprise -intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.' -shortTitle: Audit log API +title: Usando a API do log de auditoria para a sua empresa +intro: 'Você pode recuperar programaticamente eventos corporativos com a API REST{% ifversion ghec or ghes > 3.2 %} ou{% endif %} API do GraphQL.' +shortTitle: API do log de auditoria permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.' miniTocMaxHeadingLevel: 3 versions: @@ -23,20 +23,20 @@ Você pode interagir com o log de auditoria usando a API GraphQL{% ifversion ghe Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time). {% ifversion ghec or ghes > 3.0 or ghae %} -## Querying the audit log GraphQL API +## Consultando o log auditoria da API do GraphQL -To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +Para garantir que a sua propriedade intelectual esteja protegida e que você mantenha a conformidade para a sua empresa, você pode usar a API do GraphQL do log de auditoria para guardar cópias dos seus dados de log de auditoria e para monitorar: {% data reusables.audit_log.audit-log-api-info %} -Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. Para recuperar eventos do Git, use a API REST. For more information, see `git` category actions in "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)", and also the "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization) audit log endpoints in the REST API documentation."{% endif %} +Observe que você não pode recuperar eventos do Git usando a API de registro de auditoria {% ifversion not ghec %}.{% else %}API GraphQL. Para recuperar eventos do Git, use a API REST. Para obter mais informações, consulte as ações da categoria do `git` em[Ações do log de auditoria para a sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" e também a "[Administração da empresa](/rest/reference/enterprise-admin#audit-log)" e os pontos de extremidade das "[Organizações](/rest/reference/orgs#get-the-audit-log-for-an-organization) do log de auditoria na documentação da API REST.{% endif %} A resposta do GraphQL pode incluir dados por até 90 a 120 dias. -### Example 1: Members added to or removed from organizations in an enterprise +### Exemplo 1: Integrantes adicionados ou removidos das organizações de uma empresa -The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned. +A consulta abaixo busca os logs de auditoria da empresa `avocado-corp` e retorna as primeiras 10 organizações da empresa, em que as únicas ações realizadas estavam adicionando ou removendo um integrante de uma organização. As primeiras 20 entradas de logs de auditoria para cada organização são devolvidas. -This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise. +Esta consulta usa o campo [auditlog](/graphql/reference/objects) do objeto Organização, e os objetos [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) e [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry). A conta de {% data variables.product.prodname_dotcom %} que consultou o log de auditoria corporativa deve ser o proprietário de uma organização para cada organização dentro da empresa. ```shell { @@ -70,14 +70,14 @@ This query uses the [auditlog](/graphql/reference/objects) field from the Organi } ``` -The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation. -### Example 2: Events in an organization, for a specific date and actor +A API do GraphQL retornará, no máximo, 100 nós por consulta. Para recuperar resultados adicionais, você deve implementar a paginação. Para obter mais informações, consulte "[limitações de recursos](/graphql/overview/resource-limitations#node-limit)" na documentação da API do GraphQL e [Paginação](https://graphql.org/learn/pagination/) na documentação oficial do GraphQL. +### Exemplo 2: Eventos de uma organização, para uma data e ator específicos -You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space. +Você pode especificar várias frases de pesquisa, como `criado` e `ator`, separando-as na sua string de consulta com um espaço. -The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first. +A consulta abaixo busca todos os logs de auditoria para o projeto `avocado-corp` que estão relacionados à organização `octo-org`, em que as ações foram realizadas pelo usuário do `octocat` em ou após 1 de janeiro de 2022. As primeiras 20 entradas do log de auditoria são retornadas, com a entrada de log mais recente aparecendo primeiro. -This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) interface. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an owner of the `octo-org` organization. +Essa consulta usa a interface [AuditEntry](/graphql/reference/interfaces#auditentry). A conta de {% data variables.product.prodname_dotcom %} que consulta o log de auditoria corporativa deve ser um proprietário da organização `octo-org`. ```shell { @@ -105,22 +105,22 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter } ``` -For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries). +Para obter mais exemplos de consulta, veja [o repositporio das amostras da plataforma](https://github.com/github/platform-samples/blob/master/graphql/queries). {% endif %} {% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} -## Querying the audit log REST API +## Consultando o log de auditoria da API REST -To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor: +Para garantir que a sua propriedade intelectual esteja protegida e que você mantenha a conformidade para a sua empresa, você pode usar a API REST do log de auditoria para guardar cópias dos seus dados de log de auditoria e para monitorar: {% data reusables.audit_log.audited-data-list %} {% data reusables.audit_log.retention-periods %} -For more information about the audit log REST API, see "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." +Para obter mais informações sobre a REST API do log de auditoria, consulte "[Administração empresarial](/rest/reference/enterprise-admin#audit-log)" e "[Organizações](/rest/reference/orgs#get-the-audit-log-for-an-organization)". -### Example 1: All events in an enterprise, for a specific date, with pagination +### Exemplo 1: Todos os eventos de uma empresa, para uma data específica, com paginação -The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination): +A consulta abaixo procura eventos de log de auditoria criados em 1 de janeiro de 2022 na empresa `avocado-corp` e retorna a primeira página com um máximo de 100 itens por página usando a [Paginação da API REST](/rest/overview/resources-in-the-rest-api#pagination): ```shell curl -H "Authorization: token TOKEN" \ @@ -128,11 +128,11 @@ curl -H "Authorization: token TOKEN" \ "https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100" ``` -### Example 2: Events for pull requests in an enterprise, for a specific date and actor +### Exemplo 2: Eventos para pull requests em uma empresa, para uma data ou ator específico -You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`. +Você pode especificar várias frases de pesquisa, como `criado` e `ator`, separando-os no seu URL formado com o símbolo `+` ou código de carctere ASCII `%20`. -The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user: +A consulta abaixo pesquisa eventos de log de auditoria para pull requests, em que o evento ocorreu em ou depois de 1 de janeiro de 2022 na empresa `avocado-corp` e a ação foi realizada pelo usuário do `octocat`: ```shell curl -H "Authorization: token TOKEN" \ diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 3aaa4e5e1c..dbf73ff6ef 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -33,9 +33,9 @@ shortTitle: Políticas do GitHub Actions {% ifversion ghes %}Se você habilitar {% data variables.product.prodname_actions %}, qualquer{% else %}Qualquer{% endif %} organização em {% data variables.product.product_location %} poderá usar {% data variables.product.prodname_actions %}. Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} usam {% data variables.product.prodname_actions %}. Por padrão, os proprietários da organização podem gerenciar como os integrantes usam {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)". -## Enforcing a policy to restrict the use of {% data variables.product.prodname_actions %} in your enterprise +## Forçando uma política para restringir o uso de {% data variables.product.prodname_actions %} na sua empresa -Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. You can also limit the use of public actions {% if actions-workflow-policy %}and reusable workflows{% endif %}, so that people can only use local actions {% if actions-workflow-policy %}and reusable workflows{% endif %} that exist in your enterprise. +Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. Você também pode limitar o uso de ações públicas {% if actions-workflow-policy %}e fluxos de trabalho reutilizáveis{% endif %}, para que as pessoas só possam usar ações locais {% if actions-workflow-policy %}e fluxos de trabalho reutilizáveis{% endif %} que existem na sua empresa. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -47,7 +47,7 @@ Você pode optar por desativar {% data variables.product.prodname_actions %} par {%- ifversion ghes or ghae %} {% note %} - **Note:** To enable access to public actions{% if actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + **Obersvação:** Para permitir o acesso a ações públicas{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %}, você deve primeiro configurar {% data variables.product.product_location %} para se conectar a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". {% endnote %} {%- endif %} @@ -63,13 +63,13 @@ Você pode optar por desativar {% data variables.product.prodname_actions %} par {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list. +1. Em "Políticas", selecione {% data reusables.actions.policy-label-for-select-actions-workflows %} e adicione suas ações necessárias{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} à lista. {% if actions-workflow-policy %} - ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) + ![Adicionar ações e fluxos de trabalho reutilizáveis à lista de permissões](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) {%- elsif ghes or ghae-issue-5094 %} - ![Add actions to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + ![Adicionar ações à lista de permissões](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} - ![Add actions to the allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + ![Adicionar ações à lista de permissões](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) {%- endif %} ## Aplicando uma política de artefato e registrando a retenção na sua empresa diff --git a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md index 830d1d7281..55d7f698a8 100644 --- a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md @@ -39,7 +39,7 @@ shortTitle: Ver visão geral de segurança ## Visualizando a visão geral de segurança de uma empresa {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} -1. Na barra lateral esquerda, clique em {% octicon "shield" aria-label="The shield icon" %} **Segurança**. +1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**. {% endif %} ## Visualizando alertas de um repositório diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index e589fb49ac..91a4d97265 100644 --- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -35,6 +35,8 @@ O {% data variables.product.prodname_desktop %} é compatível com os seguintes - [CodeRunner](https://coderunnerapp.com/) - [SlickEdit](https://www.slickedit.com/) - [Xcode](https://developer.apple.com/xcode/) +- [RStudio](https://rstudio.com/) +- [Nova](https://nova.app/) - [Android Studio](https://developer.android.com/studio) {% endmac %} @@ -48,10 +50,18 @@ O {% data variables.product.prodname_desktop %} é compatível com os seguintes - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) - [Typora](https://typora.io/) - [SlickEdit](https://www.slickedit.com/) +- [JetBrains IntelliJ Idea](https://www.jetbrains.com/idea/) - [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) - [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) - [JetBrains Rider](https://www.jetbrains.com/rider/) +- [JetBrains CLion](https://www.jetbrains.com/clion/) +- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/) +- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/) +- [JetBrains GoLand](https://www.jetbrains.com/go/) +- [Android Studio](https://developer.android.com/studio) +- [Brackets](http://brackets.io/) - [Notepad++](https://notepad-plus-plus.org/) +- [RStudio](https://rstudio.com/) {% endwindows %} diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md index d9dd9b18c0..3c3de86702 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -12,12 +12,17 @@ topics: - Organizations - Teams shortTitle: Visualizar ideias da organização +permissions: Organization members can view organization insights. --- -Todos os integrantes de uma organização podem exibir informações da organização. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". - Você pode usar informações de atividade da organização para entender melhor como os integrantes da sua organização estão usando o {% data variables.product.product_name %} para colaborar e trabalhar no código. As informações de dependência podem ajudar você a monitorar, reportar e agir de acordo com o uso de código aberto da organização. +{% note %} + +**Note:** To view organization insights, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + ## Exibir informações de atividade da organização {% note %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md index 1bc4af77df..12b2edfa9c 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md @@ -17,6 +17,13 @@ Você pode acessar os relatórios de conformidade de {% data variables.product.c {% data reusables.security.compliance-report-list %} + +{% note %} + +**Note:** To view compliance reports, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + ## Acessando relatórios de conformidade para a sua organização {% data reusables.profile.access_org %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index f259df5ec1..9c4581aca4 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -113,8 +113,7 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. ![Captura de tela de uma caixa de seleção para habilitar um revurso para novos repositórios](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) {% endif %} -{% ifversion ghec or ghes > 3.2 %} - +{% ifversion fpt or ghec or ghes > 3.2 %} ## Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md index 6070cc6339..0e3565930c 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md @@ -30,6 +30,14 @@ Quando as notificações de e-mail restritas são habilitadas em uma organizaç {% data reusables.notifications.email-restrictions-verification %} +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To restrict email notifications, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + Os colaboradores externos não estão sujeitos às restrições de notificações por e-mail para domínios verificados ou aprovados. Para obter mais informações sobre colaboradores externos, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)". Se sua organização pertence a uma conta corporativa os integrantes da organização poderão receber notificações de qualquer domínio verificado ou aprovado para a conta corporativa, Além de quaisquer domínios verificados ou aprovados para a organização. Para obter mais informações, consulte "[Verificando ou aprovando um domínio para sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)". diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 15c9218d68..265289d743 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -135,18 +135,17 @@ Using the qualifier `country`, you can filter events in the audit log based on t You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}. {% ifversion fpt or ghec %} -The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} + +{% note %} + +**Note:** To use the audit log API, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} ### Using the GraphQL API {% endif %} -{% note %} - -**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} - -{% endnote %} - To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audit-log-api-info %} @@ -162,12 +161,6 @@ For example, you can make a GraphQL request to see all the new organization memb ### Using the REST API -{% note %} - -**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. - -{% endnote %} - To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: {% data reusables.audit_log.audited-data-list %} diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index 3f9da213ae..d1665594d2 100644 --- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -20,6 +20,8 @@ shortTitle: Autoridades do certificado SSH Um certificado SSH é um mecanismo utilizado para uma chave SSH assinar outra chave SSH. Se você usa uma autoridade certificada (CA) SSH para fornecer certificados SSH aos integrantes da organização, você pode adicionar a CA em sua conta corporativa ou organização para permitir que integrantes da organização usem os certificados deles para acessar os recursos da organização. +{% data reusables.organizations.ssh-ca-ghec-only %} + Depois de adicionar uma CA SSH à sua organização ou conta corporativa, você pode usar a CA para assinar certificados SSH de cliente para integrantes da organização. Integrantes da organização podem usar os certificados assinados para acessar os repositórios da sua organização (e somente os repositórios da sua organização) no Git. Opcionalmente, você pode exigir que os integrantes utilizem certificados SSH para acessar recursos da organização. Para obter mais informações, consulte "[Gerenciando as autoridades certificadas SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)" e "[Aplicando as políticas para configurações de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise). " Por exemplo, você pode desenvolver um sistema interno que emite um novo certificado para seus desenvolvedores todas as manhãs. Cada desenvolvedor pode usar o certificado diário para trabalhar nos repositórios da organização no {% data variables.product.product_name %}. No final do dia, o certificado pode expirar automaticamente, protegendo seus repositórios caso o certificado seja adulterado mais tarde. diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md index e7dfc07c43..16da2f61bb 100644 --- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md @@ -20,3 +20,4 @@ children: shortTitle: Gerenciar acesso do Git --- +{% data reusables.organizations.ssh-ca-ghec-only %} diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md index 400466ea26..318b4c6c35 100644 --- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md @@ -14,12 +14,13 @@ topics: - Organizations - Teams shortTitle: Gerenciar autoridades SSH +permissions: Organization owners can manage an organization's SSH certificate authorities (CA). --- -Proprietários da organização podem gerenciar as autoridades certificadas (CA, certificate authorities) de SSH da organização. - Você pode permitir que os integrantes acessem os repositórios da organização com certificados SSH fornecidos por você, adicionando um CA SSH à organização. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/articles/about-ssh-certificate-authorities)". +{% data reusables.organizations.ssh-ca-ghec-only %} + {% data reusables.organizations.add-extension-to-cert %} ## Adicionar uma autoridade certificada de SSH diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index b12308f9ec..3faf44394c 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -55,14 +55,14 @@ You can choose to disable {% data variables.product.prodname_actions %} for all {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions-general %} -1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list. +1. Em "Políticas", selecione {% data reusables.actions.policy-label-for-select-actions-workflows %} e adicione suas ações necessárias{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} à lista. {% if actions-workflow-policy %} - ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/actions-policy-allow-list-with-workflows.png) + ![Adicionar ações e fluxos de trabalho reutilizáveis à lista de permissões](/assets/images/help/organizations/actions-policy-allow-list-with-workflows.png) {%- elsif ghes %} - ![Add actions to the allow list](/assets/images/help/organizations/actions-policy-allow-list.png) + ![Adicionar ações à lista de permissões](/assets/images/help/organizations/actions-policy-allow-list.png) {%- else %} - ![Add actions to the allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + ![Adicionar ações à lista de permissões](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) {%- endif %} 1. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 64d8c37344..b7b0fab275 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -40,10 +40,12 @@ Os proprietários de empresas podem restringir as opções que você tem dispon ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) {%- elsif fpt %} ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png) + {%- endif %} + {% ifversion fpt or ghec %} {% note %} - **Observação:** Para restringir os integrantes de criar repositórios privados apenas, sua organização deverá usar {% data variables.product.prodname_ghe_cloud %}. + **Observação:** Para restringir os integrantes de criar repositórios privados apenas, sua organização deverá usar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endnote %} {%- endif %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 7f52b2ee95..9833cc9e42 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -18,6 +18,8 @@ shortTitle: IAM com SSO do SAML {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.ghec-only %} + {% data reusables.saml.saml-accounts %} Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index e2b0455756..7f708f41e4 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -15,6 +15,8 @@ topics: Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) em sua organização, é possível implementar o SCIM pra adicionar, gerenciar e remover o acesso dos integrantes da organização ao {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização. +{% data reusables.saml.ghec-only %} + Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM. Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/rest/reference/scim) na documentação da API {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index b49351496c..ae314531b0 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configurar SAML & SCIM com Okta Você pode controlar o acesso à sua organização em {% data variables.product.product_location %} e outros aplicativos da web a partir de uma interface central, configurando a organização para usar SAML SSO e o SCIM com Okta, um provedor de identidade (IdP). +{% data reusables.saml.ghec-only %} + O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização em {% data variables.product.product_location %} quando você fizer alterações no Okta. Para obter mais informações, consulte "[Sobre a identidade e gerenciamento de acesso com logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" e "[Sobre SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta. diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index 4c6f749885..9216f2f440 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -14,6 +14,8 @@ shortTitle: Conectar um IdP Ao habilitar o SAML SSO para sua organização de {% data variables.product.product_name %}, você conecta seu provedor de identidade (IdP) à sua organização. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". +{% data reusables.saml.ghec-only %} + Você pode encontrar as informações de implementação do SAML e SCIM para seu IdP na documentação do IdP. - [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) do Active Directory Federation Services (AD FS) - [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) e [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) do Azure Active Directory (Azure AD) diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 3954d17881..28f8ff19a8 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -16,6 +16,8 @@ shortTitle: Habilitar & testar o SSO do SAML Você pode habilitar o SAML SSO na sua organização sem exigir que todos os integrantes o utilizem. A habilitação (em vez da aplicação) do SAML SSO facilitará a adoção dele pela organização. Depois que a maioria dos integrantes da sua organização já estiver usando o SAML SSO, você poderá aplicá-lo a toda a organização. +{% data reusables.saml.ghec-only %} + Se você habilitar em vez de aplicar o SAML SSO, os integrantes da organização que preferem não usá-lo poderão continuar sendo integrantes da organização. Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index 0e5726da27..3111e37c24 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -20,6 +20,8 @@ Ao habilitar o SAML SSO, {% data variables.product.prodname_dotcom %} solicitar Você também pode aplicar SAML SSO para a sua organização. {% data reusables.saml.when-you-enforce %} Aplicação remove todos os integrantes e administradores que não tenham efetuado a autenticação por meio do seu IdP da organização. {% data variables.product.company_short %} envia uma notificação de email para cada usuário removido. +{% data reusables.saml.ghec-only %} + {% data reusables.saml.removed-users-can-rejoin %} Se um usuário juntar-se à organização em três meses, os privilégios e configurações de acesso do usuário serão restaurados. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)". As contas de bots e serviços que não têm identidades externas configuradas no IdP da sua organização também serão removidas quando você aplicar o SAML SSO. Para obter mais informações sobre bots e contas de serviço, consulte "[Gerenciar bots e contas de serviço com logon único SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)". diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md index b060aaf98a..33ca86d2d6 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md @@ -25,3 +25,4 @@ children: shortTitle: Gerenciar logon único SAML --- +{% data reusables.saml.ghec-only %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index b1536856ea..f14f85ee8e 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -24,6 +24,8 @@ shortTitle: Gerenciar sincronização de equipe {% data reusables.identity-and-permissions.about-team-sync %} +{% data reusables.saml.ghec-only %} + {% data reusables.identity-and-permissions.supported-idps-team-sync %} {% data reusables.identity-and-permissions.sync-team-with-idp-group %} @@ -42,7 +44,7 @@ As etapas para habilitar a sincronização de equipe dependem do IdP que você d {% data reusables.identity-and-permissions.team-sync-required-permissions %} -Você deve habilitar o logon único SAML para sua organização e seu IdP compatível. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +Você deve habilitar o logon único SAML para sua organização e seu IdP compatível. Para obter mais informações, consulte "[Aplicar o logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". Você deve ter uma identidade SAML vinculada. Para criar uma identidade vinculada, você deve efetuar a autenticação na sua organização usando o SAML SSO e o IdP compatível pelo menos uma vez. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md index 0d1224270b..da8af79ed0 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -12,6 +12,8 @@ topics: shortTitle: Prepare-se para aplicar o SSO do SAML --- +{% data reusables.saml.ghec-only %} + {% data reusables.saml.when-you-enforce %} antes de aplicar o SAML SSO na sua organização, você deverá revisar a associação da organização, habilitar o SAML SSO e revisar o acesso SAML dos integrantes da organização. Para obter mais informações, consulte o seguinte. | Tarefa | Mais informações | diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index e02aaf924d..b15d87c8dc 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.private-pages %}' versions: fpt: '*' ghec: '*' -permissions: 'People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.' +permissions: 'People with admin access to a repository can change the visibility of a {% data variables.product.prodname_pages %} site.' redirect_from: - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site shortTitle: Alterar a visibilidade do site @@ -15,6 +15,12 @@ shortTitle: Alterar a visibilidade do site Com controle de acesso para {% data variables.product.prodname_pages %}, você pode restringir o acesso ao seu site {% data variables.product.prodname_pages %} publicando o site de forma privada. Um site publicado de forma privada só pode ser acessado por pessoas com acesso de leitura ao repositório a partir do qual o site é publicado. Você pode usar sites publicados de forma privada para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. +{% note %} + +**Note:** To publish a {% data variables.product.prodname_pages %} site privately, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} + Se sua empresa usar {% data variables.product.prodname_emus %}, todos os sites de {% data variables.product.prodname_pages %} serão publicados privadamente. Para obter mais informações sobre {% data variables.product.prodname_emus %}, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". Se a sua organização usar {% data variables.product.prodname_ghe_cloud %} sem {% data variables.product.prodname_emus %}, você poderá optar por publicar seus sites em particular ou publicamente para qualquer pessoa na internet. O controle de acesso está disponível para os sites de projeto publicados a partir de um repositório privado ou interno que pertencem à organização. Você não pode gerenciar o controle de acesso para um site da organização. Para obter mais informações sobre os tipos de sites do {% data variables.product.prodname_pages %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index b1003d7456..e32dd58bb6 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -18,12 +18,18 @@ topics:

O Octokit tem muitos sabores

Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.


-
Ruby → octokit.rb

+
Ruby → octokit.rb

.NET → octokit.net

JavaScript → octokit/octokit.js

+{% warning %} + +Warning: As of late October 2021, the offical Octokit libraries are not currently maintained. + +{% endwarning %} + # Bibliotecas de terceiros ### Clojure diff --git a/translations/pt-BR/data/features/job-hooks-for-runners.yml b/translations/pt-BR/data/features/job-hooks-for-runners.yml index cb0891fe9b..e3d995d4e1 100644 --- a/translations/pt-BR/data/features/job-hooks-for-runners.yml +++ b/translations/pt-BR/data/features/job-hooks-for-runners.yml @@ -4,3 +4,5 @@ versions: fpt: '*' ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6530' diff --git a/translations/pt-BR/data/reusables/organizations/ssh-ca-ghec-only.md b/translations/pt-BR/data/reusables/organizations/ssh-ca-ghec-only.md new file mode 100644 index 0000000000..e87e7ff46c --- /dev/null +++ b/translations/pt-BR/data/reusables/organizations/ssh-ca-ghec-only.md @@ -0,0 +1,8 @@ +{% ifversion fpt or ghec %} +{% note %} + +**Note:** To use SSH certificate authorities, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/saml/ghec-only.md b/translations/pt-BR/data/reusables/saml/ghec-only.md new file mode 100644 index 0000000000..dd0c53e196 --- /dev/null +++ b/translations/pt-BR/data/reusables/saml/ghec-only.md @@ -0,0 +1,7 @@ +{% ifversion ghec %} +{% note %} + +**Note:** To use SAML single sign-on, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md index 92f8aae8f5..9162eb6400 100644 --- a/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md +++ b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -1 +1 @@ -Atividade relacionada a alertas de varredura de segredo em um repositório. O tipo de atividade é especificado na propriedade ação do objeto da carga. For more information, see the "[secret scanning API](rest/reference/secret-scanning)." +Atividade relacionada a alertas de varredura de segredo em um repositório. O tipo de atividade é especificado na propriedade ação do objeto da carga. For more information, see the "[secret scanning API](/rest/reference/secret-scanning)."