jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 03:01:36 -05:00
Code Issues Projects Releases Wiki Activity

New translation batch for ja (#26751)

Browse Source
This commit is contained in:
docubot
2022-04-07 11:34:31 -07:00
committed by GitHub
parent abb696f4bf
commit cfefcaa036
69 changed files with 2382 additions and 713 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
View File

@@ -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 %}
### シークレット管理のイベント

4
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
View File

@@ -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

2
translations/ja-JP/content/admin/enterprise-management/index.md
View File

@@ -13,6 +13,6 @@ children:
- /configuring-clustering
- /configuring-high-availability
- /caching-repositories
shortTitle: 'Monitor, manage & update'
shortTitle: 'Monitor, manage, and update your appliance'
---

62
translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md Normal file
View File

@@ -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)

1
translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md
View File

@@ -16,6 +16,7 @@ children:
- /setting-up-external-monitoring
- /configuring-collectd
- /monitoring-using-snmp
- /about-system-logs
- /generating-a-health-check-for-your-enterprise
---

2
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
View File

@@ -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)

18
translations/ja-JP/content/admin/guides.md
View File

@@ -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

35
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md
View File

@@ -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)

1
translations/ja-JP/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md
View File

@@ -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
---

5
translations/ja-JP/content/admin/index.md
View File

@@ -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

1
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md → translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
View File

@@ -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: '*'

17
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md Normal file
View File

@@ -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
---

1
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md → translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
View File

@@ -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: '*'

100
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md Normal file
View File

@@ -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)

3
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md → translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
View File

@@ -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 <em>コードオーナー</em>/<em>リポジトリ</em> -c "less audit_log"
ghe-repo <em>owner</em>/<em>repository</em> -c "cat audit_log"
```
{% endif %}

17
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md Normal file
View File

@@ -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
---

61
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md Normal file
View File

@@ -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 %}

27
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md Normal file
View File

@@ -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 %}

1210
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md Normal file
View File

File diff suppressed because it is too large Load Diff

51
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md Normal file
View File

@@ -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
```

20
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md Normal file
View File

@@ -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
---

130
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md Normal file
View File

@@ -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.<br/>- When a user account or repository was added or removed from a team<br/>- When a team maintainer was promoted or demoted<br/>- When a team was deleted |
| `Repository management` | All actions for repository management.<br/>- When a repository was created or deleted<br/>- When the repository visibility was changed<br/>- 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"` はアメリカ合衆国で発生したすべてのイベントを検索します。

22
translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md → translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
View File

@@ -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.

143
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 Normal file
View File

@@ -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 <em>TOKEN</em>" \
--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 <em>TOKEN</em>" \
--request GET \
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
```
{% endif %}

36
translations/ja-JP/content/admin/overview/system-overview.md
View File

@@ -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

3
translations/ja-JP/content/admin/user-management/index.md
View File

@@ -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
---

2
translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
View File

@@ -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

36
translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
View File

@@ -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 %}

2
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
View File

@@ -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)".
| カテゴリ名 | 説明 |
| ------ | -------------------------------------------- |

82
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
View File

@@ -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 %}

2
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
View File

@@ -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

48
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
View File

@@ -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 %}

200
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
View File

@@ -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

23
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md
View File

@@ -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
---

87
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
View File

@@ -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)

51
translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
View File

@@ -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)

94
translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
View File

@@ -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 %}

8
translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
View File

@@ -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

14
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
View File

@@ -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 %}

8
translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
View File

@@ -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 %}

4
translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
View File

@@ -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)."

2
translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
View File

@@ -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

25
translations/ja-JP/content/get-started/using-github/supported-browsers.md
View File

@@ -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 の最新バージョンが必要です。
## ベータ版および開発者版

2
translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
View File

@@ -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 %}

25
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
View File

@@ -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 %}

4
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
View File

@@ -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 %}

16
translations/ja-JP/content/rest/reference/dependency-graph.md Normal file
View File

@@ -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
---
<!--
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/dependency-graph
-->

1
translations/ja-JP/content/rest/reference/index.md
View File

@@ -22,6 +22,7 @@ children:
- /collaborators
- /commits
- /dependabot
- /dependency-graph
- /deploy_keys
- /deployments
- /emojis

2
translations/ja-JP/content/site-policy/github-terms/github-corporate-terms-of-service.md
View File

@@ -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 はそれらを削除または回収する義務を負いません。

4
translations/ja-JP/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
View File

@@ -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)に同意する必要があります。

2
translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md
View File

@@ -89,7 +89,7 @@ $ ssh -p122 admin@<em>hostname</em> -- '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)」を参照してください。

155
translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md Normal file
View File

@@ -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 %}

9
translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md Normal file
View File

@@ -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 %}

11
translations/ja-JP/data/reusables/audit_log/audit-log-search-by-operation.md Normal file
View File

@@ -0,0 +1,11 @@
### 操作に基づく検索
`operation`修飾子は、アクションを特定の操作の種類に限定するときに使ってください。 例:
* `operation:access`は、リソースがアクセスされたすべてのイベントを見つけます。
* `operation:authentication`は認証イベントが生じたすべてのイベントを見つけます。
* `operation:create`は、リソースが作成されたすべてのイベントを見つけます。
* `operation:modify`は、リソースが修正されたすべてのイベントを見つけます。
* `operation:remove`は、既存のリソースが削除されたすべてのイベントを見つけます。
* `operation:restore`は、既存のリソースがリストアされたすべてのイベントを見つけます。
* `operation:transfer`は既存のリソースが移譲されたすべてのイベントを見つけます。

9
translations/ja-JP/data/reusables/audit_log/audit-log-search-by-repo.md Normal file
View File

@@ -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` だけを検索しても機能しません。

9
translations/ja-JP/data/reusables/audit_log/audit-log-search-by-user.md Normal file
View File

@@ -0,0 +1,9 @@
### ユーザーに基づく検索
`actor`修飾子は、アクションを実行した人に基づいてイベントの範囲を指定できます。 例:
* `actor:octocat`は`octocat`が行ったすべてのイベントを検索します。
* `actor:octocat actor:hubot`は、`octocat`及び`hubot`が行ったすべてのイベントを検索します。
* `-actor:hubot`は、`hubot`が行ったすべてのイベントを除外します。
使用できるのは {% data variables.product.product_name %} のユーザー名のみであり、個人の実名ではないことに注意してください。

11
translations/ja-JP/data/reusables/audit_log/audit-log-search-list-info-about-action.md Normal file
View File

@@ -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
- アクションの対象となったリポジトリ
- 実行されたアクション
- アクションが実行された国
- アクションが発生した日時

40
translations/ja-JP/data/reusables/audit_log/audit-log-search.md
View File

@@ -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 %}

2
translations/ja-JP/data/reusables/audit_log/audited-data-list.md
View File

@@ -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 %}

13
translations/ja-JP/data/reusables/audit_log/exported-git-log-keys-and-values.md Normal file
View File

@@ -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 |

32
translations/ja-JP/data/reusables/audit_log/exported-log-keys-and-values.md
View File

@@ -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 |

3
translations/ja-JP/data/reusables/audit_log/retention-periods.md Normal file
View File

@@ -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 %}

56
translations/ja-JP/data/reusables/dependabot/supported-package-managers.md
View File

@@ -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（バージョンなし）<sup>[1]</sup> | **✓** | **✓** | |
| Maven | `maven` | N/A（バージョンなし）<sup>[2]</sup> | **✓** | **✓** | |
| npm | `npm` | v6, v7, v8 | **✓** | **✓** | |
| NuGet | `nuget` | <= 4.8<sup>[3]</sup> | **✓** | **✓** | |
| 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（バージョンなし）<sup>[1]</sup> | **✓** | **✓** | |
| Maven | `maven` | N/A（バージョンなし）<sup>[2]</sup> | **✓** | **✓** | |
| npm | `npm` | v6, v7, v8 | **✓** | **✓** | |
| NuGet | `nuget` | <= 4.8<sup>[3]</sup> | **✓** | **✓** | |
| 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 <sup>[4]</sup> | | |
{% 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 %}

5
translations/ja-JP/data/reusables/dependency-review/dependency-review-action-beta-note.md Normal file
View File

@@ -0,0 +1,5 @@
{% note %}
**Note**: The Dependency Review GitHub Action is currently in public beta and subject to change.
{% endnote %}

5
translations/ja-JP/data/reusables/dependency-review/dependency-review-api-beta-note.md Normal file
View File

@@ -0,0 +1,5 @@
{% note %}
**Note**: The Dependency Review API is currently in public beta and subject to change.
{% endnote %}

1
translations/ja-JP/data/reusables/enterprise/link-to-ghe-trial.md Normal file
View File

@@ -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)."

2
translations/ja-JP/data/reusables/gated-features/more-info-org-products.md
View File

@@ -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 %}

5
translations/ja-JP/data/reusables/rest-reference/dependency-graph/dependency-review.md Normal file
View File

@@ -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)."

2
translations/log/ja-resets.csv
View File

@@ -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
1 file reason
53 translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md broken liquid tags
54 translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md broken liquid tags
55 translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md broken liquid tags
56 translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md rendering error
57 translations/ja-JP/content/admin/overview/system-overview.md broken liquid tags
58 translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md broken liquid tags
59 translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md broken liquid tags
67 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
68 translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md broken liquid tags
69 translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md broken liquid tags
70 translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md rendering error
71 translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md broken liquid tags
72 translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md rendering error
73 translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md broken liquid tags