From 4076d5282787f7f5fe207522bf4f5a2df74d9ea7 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 26 Jul 2022 18:00:32 -0400 Subject: [PATCH] New translation batch for ja (#29362) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report --- .../managing-accessibility-settings.md | 41 ++- .../about-github-hosted-runners.md | 4 +- .../events-that-trigger-workflows.md | 4 +- ...g-server-statistics-for-your-enterprise.md | 2 - .../command-line-utilities.md | 14 + .../configuring-email-for-notifications.md | 14 +- ...configuring-host-keys-for-your-instance.md | 47 ++++ ...guring-ssh-connections-to-your-instance.md | 53 ++++ .../configuring-your-enterprise/index.md | 2 + .../initializing-github-ae.md | 1 + ...ucing-github-actions-to-your-enterprise.md | 2 +- translations/ja-JP/content/admin/guides.md | 2 + .../about-server-statistics.md | 2 - .../exporting-server-statistics.md | 4 +- ...ng-server-statistics-using-the-rest-api.md | 2 - ...about-the-audit-log-for-your-enterprise.md | 12 +- .../audit-log-events-for-your-enterprise.md | 14 +- ...aming-the-audit-log-for-your-enterprise.md | 24 +- .../ja-JP/content/admin/packages/index.md | 1 + ...ainer-registry-from-the-docker-registry.md | 85 +++++++ ...s-for-github-actions-in-your-enterprise.md | 1 + ...-management-policies-in-your-enterprise.md | 36 ++- .../ja-JP/content/admin/policies/index.md | 1 - .../index.md | 3 + .../viewing-people-in-your-enterprise.md | 4 + .../about-ssh.md | 6 +- ...ng-a-new-ssh-key-to-your-github-account.md | 25 +- .../checking-for-existing-ssh-keys.md | 10 + ...-ssh-key-and-adding-it-to-the-ssh-agent.md | 240 +++++++++--------- .../working-with-ssh-key-passphrases.md | 8 +- .../about-commit-signature-verification.md | 2 + ...isories-in-the-github-advisory-database.md | 165 ++++++------ ...isories-in-the-github-advisory-database.md | 18 +- .../end-to-end-supply-chain/securing-code.md | 2 +- .../about-the-dependency-graph.md | 4 +- ...disaster-recovery-for-github-codespaces.md | 2 +- .../security-in-github-codespaces.md | 2 +- ...ing-github-codespaces-for-pull-requests.md | 4 +- .../about-discussions.md | 11 +- ...ting-with-maintainers-using-discussions.md | 5 +- .../index.md | 3 +- .../participating-in-a-discussion.md | 5 +- ...s-for-community-conversations-on-github.md | 9 +- .../guides/finding-your-discussions.md | 6 +- ...-higher-permissions-to-top-contributors.md | 7 +- .../ja-JP/content/discussions/guides/index.md | 3 +- .../ja-JP/content/discussions/index.md | 5 +- .../index.md | 3 +- .../managing-categories-for-discussions.md | 9 +- .../managing-discussions.md | 7 +- .../moderating-discussions.md | 7 +- .../viewing-insights-for-your-discussions.md | 3 +- .../ja-JP/content/discussions/quickstart.md | 13 +- ...etting-started-with-your-github-account.md | 2 +- .../quickstart/communicating-on-github.md | 11 +- .../using-github/keyboard-shortcuts.md | 2 +- .../creating-and-highlighting-code-blocks.md | 2 +- .../creating-diagrams.md | 10 +- .../using-the-graphql-api-for-discussions.md | 3 +- .../about-issues.md | 3 +- .../creating-an-issue.md | 2 +- .../about-organizations.md | 16 +- ...ing-the-audit-log-for-your-organization.md | 2 + .../repository-roles-for-an-organization.md | 2 +- ...-github-discussions-for-an-organization.md | 3 +- .../managing-organization-settings/index.md | 1 + ...n-for-repositories-in-your-organization.md | 3 +- ...it-signoff-policy-for-your-organization.md | 25 ++ ...ay-of-member-names-in-your-organization.md | 3 + ...om-repository-roles-for-an-organization.md | 2 +- translations/ja-JP/content/packages/index.md | 3 +- ...-packages-access-control-and-visibility.md | 2 +- ...ainer-registry-from-the-docker-registry.md | 64 +++-- .../working-with-the-container-registry.md | 14 +- .../about-commits.md | 3 + ...ing-github-discussions-for-a-repository.md | 6 +- .../managing-repository-settings/index.md | 1 + ...mmit-signoff-policy-for-your-repository.md | 24 ++ .../managing-releases-in-a-repository.md | 2 +- .../working-with-non-code-files.md | 14 +- .../overview/resources-in-the-rest-api.md | 5 +- .../searching-discussions.md | 3 +- .../about-github-support.md | 2 + .../GH-advisory-db-erlang-support.yml | 7 + .../data/features/audit-log-streaming.yml | 5 + .../ja-JP/data/features/commit-signoffs.yml | 5 + .../ja-JP/data/features/discussions.yml | 4 + .../docker-ghcr-enterprise-migration.yml | 4 + .../data/features/ghas-enablement-webhook.yml | 2 +- .../ja-JP/data/features/motion-management.yml | 7 + .../data/features/pause-audit-log-stream.yml | 4 + .../data/features/require-tls-for-smtp.yml | 4 + .../security-advisories-ghes-ghae.yml | 4 + .../ja-JP/data/glossaries/internal.yml | 2 +- .../ghes-3.6/graphql_previews.enterprise.yml | 123 +++++++++ ...hql_upcoming_changes.public-enterprise.yml | 86 +++++++ .../enterprise-server/3-2/16.yml | 17 ++ .../enterprise-server/3-3/11.yml | 18 ++ .../release-notes/enterprise-server/3-4/2.yml | 2 +- .../release-notes/enterprise-server/3-4/3.yml | 2 +- .../release-notes/enterprise-server/3-4/5.yml | 2 +- .../release-notes/enterprise-server/3-4/6.yml | 20 ++ .../release-notes/enterprise-server/3-5/3.yml | 22 ++ .../enterprise-server/3-6/0-rc1.yml | 216 ++++++++++++++++ .../actions/supported-github-runners.md | 2 +- .../beta-malware-advisories.md | 4 +- .../audit_log/audit-log-action-categories.md | 2 +- .../code-scanning/alert-tracking-link.md | 2 +- .../code-scanning/beta-codeql-ml-queries.md | 2 +- .../code-scanning/beta-codeql-packs-cli.md | 2 +- .../choose-alert-dismissal-reason.md | 2 +- ...odeql-cli-context-for-third-party-tools.md | 2 +- .../code-scanning/codeql-languages-bullets.md | 4 +- .../codeql-languages-keywords.md | 2 +- .../codeql-query-suites-explanation.md | 2 +- .../deprecation-codeql-runner.md | 10 +- .../code-scanning/enabling-options.md | 4 +- .../false-positive-fix-codeql.md | 2 +- .../filter-non-default-branches.md | 2 +- .../github-issues-integration.md | 4 +- .../reusables/code-scanning/licensing-note.md | 6 +- .../code-scanning/run-additional-queries.md | 12 +- .../code-scanning/upload-sarif-alert-limit.md | 4 +- .../codespaces/about-port-forwarding.md | 2 +- .../data/reusables/codespaces/availability.md | 2 +- .../codespaces/billing-for-prebuilds.md | 8 +- .../codespaces/codespaces-api-beta-note.md | 2 +- .../codespaces/codespaces-billing.md | 12 +- .../codespaces-machine-type-availability.md | 2 +- .../codespaces/codespaces-machine-types.md | 4 +- .../codespaces/codespaces-org-policies.md | 6 +- .../codespaces/codespaces-policy-targets.md | 12 +- .../codespaces-spending-limit-requirement.md | 4 +- .../codespaces/command-palette-container.md | 4 +- .../reusables/codespaces/contact-support.md | 2 +- .../creating-a-codespace-in-vscode.md | 10 +- .../codespaces/customize-vcpus-and-ram.md | 4 +- .../deleting-a-codespace-in-vscode.md | 6 +- .../reusables/codespaces/exporting-changes.md | 2 +- .../codespaces/links-to-get-started.md | 2 +- .../codespaces/more-info-devcontainer.md | 2 +- .../codespaces/port-visibility-settings.md | 8 +- .../codespaces/prebuilds-crossreference.md | 2 +- .../codespaces/prebuilds-not-available.md | 2 +- .../reusables/codespaces/rebuild-command.md | 2 +- .../reusables/codespaces/recovery-mode.md | 2 +- .../codespaces/restrict-port-visibility.md | 2 +- .../data/reusables/codespaces/review-pr.md | 10 +- .../reusables/codespaces/secret-precedence.md | 2 +- .../codespaces/setup-custom-devcontainer.md | 2 +- .../your-codespaces-procedure-step.md | 4 +- .../reusables/command-palette/beta-note.md | 2 +- .../reusables/command-palette/change-scope.md | 8 +- .../reusables/command-palette/open-palette.md | 2 +- .../reusables/community/issue-forms-beta.md | 2 +- .../copilot/accept-or-reject-suggestion.md | 2 +- .../copilot/accept-suggestion-new-tab.md | 2 +- .../copilot/accept-suggestion-tab.md | 2 +- .../reusables/copilot/accept-suggestion.md | 2 +- .../copilot/alternative-suggestions.md | 2 +- .../copilot/close-suggestions-tab.md | 2 +- .../copilot/copilot-prerequisites.md | 4 +- .../data/reusables/copilot/create-c-file.md | 2 +- .../reusables/copilot/create-java-file.md | 2 +- .../data/reusables/copilot/create-js-file.md | 2 +- .../data/reusables/copilot/dotcom-settings.md | 6 +- .../enabling-disabling-in-jetbrains.md | 6 +- .../copilot/enabling-or-disabling-in-vsc.md | 8 +- .../copilot/enabling-or-disabling-vs.md | 5 +- .../generating-suggestions-from-comments.md | 2 +- .../copilot/install-copilot-in-neovim.md | 4 +- .../data/reusables/copilot/jetbrains-ides.md | 4 +- .../reusables/copilot/procedural-intro.md | 2 +- .../copilot/reject-suggestions-escape.md | 2 +- .../data/reusables/copilot/save-settings.md | 2 +- .../copilot/see-alternative-suggestions.md | 2 +- .../reusables/copilot/signup-procedure.md | 14 +- .../reusables/copilot/suggestions-new-tab.md | 2 +- .../reusables/copilot/supported-languages.md | 2 +- .../copilot/type-function-header-c.md | 2 +- .../copilot/windows-linux-next-suggestion.md | 2 +- .../dependabot/about-the-dependency-graph.md | 2 +- ...security-and-version-updates-onboarding.md | 2 +- .../beta-security-and-version-updates.md | 6 +- .../dependabot/configuration-options.md | 48 ++-- .../dependabot/dependabot-alerts-beta.md | 2 +- ...abot-alerts-dependency-graph-enterprise.md | 2 +- .../dependabot-alerts-dependency-scope.md | 22 +- .../about-organization-discussions.md | 2 +- .../enterprise-accounts/packages-tab.md | 1 + .../reusables/enterprise/about-ssh-ports.md | 5 + .../enterprise/apply-configuration.md | 12 + .../repository-caching-release-phase.md | 2 + .../ssh-into-instance.md | 9 +- .../disclaimer-for-git-read-access.md | 6 +- .../data/reusables/gated-features/copilot.md | 2 +- .../reusables/gated-features/discussions.md | 1 - .../container-registry-benefits.md | 1 + ...er-registry-ghes-migration-availability.md | 1 + ...container-registry-migration-namespaces.md | 1 + ...ainer-registry-replaces-docker-registry.md | 1 + .../verify_repository_field.md | 2 +- .../reusables/repositories/commit-signoffs.md | 10 + .../link-browsing-advisory-db.md | 6 +- .../server-statistics/release-phase.md | 5 - .../ja-JP/data/reusables/ssh/about-ssh.md | 1 + .../data/reusables/ssh/key-type-support.md | 19 +- .../rsa-sha-1-connection-failure-criteria.md | 2 + translations/ja-JP/data/ui.yml | 2 +- translations/ja-JP/data/variables/product.yml | 2 + .../data/variables/release_candidate.yml | 2 +- translations/log/ja-resets.csv | 6 +- 212 files changed, 1617 insertions(+), 611 deletions(-) create mode 100644 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md create mode 100644 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md create mode 100644 translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md create mode 100644 translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md create mode 100644 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md create mode 100644 translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml create mode 100644 translations/ja-JP/data/features/audit-log-streaming.yml create mode 100644 translations/ja-JP/data/features/commit-signoffs.yml create mode 100644 translations/ja-JP/data/features/discussions.yml create mode 100644 translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml create mode 100644 translations/ja-JP/data/features/motion-management.yml create mode 100644 translations/ja-JP/data/features/pause-audit-log-stream.yml create mode 100644 translations/ja-JP/data/features/require-tls-for-smtp.yml create mode 100644 translations/ja-JP/data/features/security-advisories-ghes-ghae.yml create mode 100644 translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml create mode 100644 translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml create mode 100644 translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml create mode 100644 translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml create mode 100644 translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml create mode 100644 translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml create mode 100644 translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml create mode 100644 translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md create mode 100644 translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md create mode 100644 translations/ja-JP/data/reusables/enterprise/apply-configuration.md delete mode 100644 translations/ja-JP/data/reusables/gated-features/discussions.md create mode 100644 translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md create mode 100644 translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md create mode 100644 translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md create mode 100644 translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md create mode 100644 translations/ja-JP/data/reusables/repositories/commit-signoffs.md delete mode 100644 translations/ja-JP/data/reusables/server-statistics/release-phase.md create mode 100644 translations/ja-JP/data/reusables/ssh/about-ssh.md create mode 100644 translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 72c2a7feb7..29c5772885 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -1,21 +1,50 @@ --- title: Managing accessibility settings -intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.' +shortTitle: Manage accessibility settings +intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.' versions: feature: keyboard-shortcut-accessibility-setting redirect_from: - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings +type: how_to +miniTocMaxHeadingLevel: 3 --- ## About accessibility settings -{% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible. +To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}. -All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as Control or Command. +## Managing accessibility settings -## Managing character key shortcuts +You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}the website for {% data variables.product.product_location %}{% endif %}, and you can control the display of animated images. + +### Managing keyboard shortcuts + +You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts. + +By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. 詳細は「[キーボードのショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %} -1. Select or deselect the **Enable character key shortcuts** checkbox. ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png) -2. [**Save**] をクリックします。 +1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts. + + - Optionally, to disable or enable shortcut keys that don't use modifiers keys like Control or Command, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key. +{%- ifversion command-palette %} + - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)." + {%- endif %} + +{% ifversion motion-management %} + +### Managing motion + +You can control how {% data variables.product.product_name %} displays animated images. + +By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system. + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.accessibility_settings %} +1. Under "Motion", manage settings for motion. + + - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**. + +{% endif %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index bbdcf5a7d3..eb6456168e 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -87,12 +87,12 @@ While the job runs, the logs and output can be viewed in the {% data variables.p ## サポートされているランナーとハードウェアリソース Windows および Linux 仮想マシンのハードウェア仕様: -- 2コアCPU +- 2-core CPU (x86_64) - 7 GB of RAM - 14 GB of SSD space macOS 仮想マシンのハードウェア仕様: -- 3-core CPU +- 3-core CPU (x86_64) - 14 GB of RAM - 14 GB of SSD space diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md index dca8e2341d..e68c00e3bc 100644 --- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md @@ -18,7 +18,7 @@ shortTitle: ワークフローをトリガーするイベント ## About events that trigger workflows -Workflow triggers are events that cause a workflow to run. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)." +ワークフロートリガーは、ワークフローの実行を引き起こすイベントです。 For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)." ## Available events @@ -185,7 +185,7 @@ on: deployment_status ``` -{% ifversion fpt or ghec %} +{% ifversion discussions %} ### `ディスカッション` | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md index a4bb148ac0..928ee92616 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -10,8 +10,6 @@ topics: shortTitle: Server Statistics --- -{% data reusables.server-statistics.release-phase %} - ## {% data variables.product.prodname_server_statistics %}について {% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 07e7034a3b..59f1280ecb 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -737,6 +737,20 @@ git-import-tfs-raw git-import-rewrite ``` +{% ifversion ghes > 3.3 %} + +## セキュリティ + +### ghe-find-insecure-git-operations + +This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %} + +```shell +ghe-find-insecure-git-operations +``` + +{% endif %} + ## サポート ### ghe-diagnostics diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index 364cbc347c..4c539b1e05 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -73,6 +73,18 @@ Enterprise オーナーは、通知用のメールを設定できます。 5. テストメールが成功したなら、ページの下部で**Save settings（設定の保存）**をクリックしてください。 ![設定保存のボタン](/assets/images/enterprise/management-console/save-settings.png) {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} +{% ifversion require-tls-for-smtp %} +## Enforcing TLS for SMTP connections + +You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement. + +{% data reusables.enterprise_site_admin_settings.email-settings %} +1. Under "Authentication," select **Enforce TLS auth (recommended)**. + + ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +{% endif %} + ## メール着信を許可する DNS とファイアウォールの設定 通知へのメールでの返信を許可したいなら、DNSを設定しなければなりません。 @@ -80,7 +92,7 @@ Enterprise オーナーは、通知用のメールを設定できます。 1. インスタンスのポート25がSMTPサーバにアクセスできることを確認してください。 2. `reply.[hostname]`を指すAレコードを作成してください。 DNSプロバイダとインスタンスのホスト設定によっては、 `*.[hostname]`を指す単一のAレコードを作成できる場合があります。 3. `reply.[hostname]`を指すMXレコードを作成して、このドメインへのメールがインスタンスにルーティングされるようにしてください。 -4. `noreply.[hostname]` が `[hostname]` を指すようにする MX レコードを作成し、 通知メールの `cc` アドレスへの返信がインスタンスにルーティングされるようにしてください。 詳しい情報については、{% ifversion ghes %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}」を参照してください。 +4. `noreply.[hostname]` が `[hostname]` を指すようにする MX レコードを作成し、 通知メールの `cc` アドレスへの返信がインスタンスにルーティングされるようにしてください。 For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}." ## メール配信のトラブルシューティング diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md new file mode 100644 index 0000000000..dd05637a5b --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md @@ -0,0 +1,47 @@ +--- +title: Configuring host keys for your instance +shortTitle: Configure host keys +intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.' +permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.' +versions: + ghes: '>= 3.6' +type: how_to +topics: + - Authentication + - Enterprise + - Infrastructure + - Networking + - Security + - SSH +--- + +## About host keys for your instance + +Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website. + +{% data reusables.enterprise.about-ssh-ports %} + +By default, {% data variables.product.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys. + +{% note %} + +**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm. + +{% endnote %} + +## Managing an Ed25519 host key + +To improve security for clients that connect to {% data variables.product.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to). + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. To enable generation and advertisement of the Ed25519 host key, enter the following command. + + ```shell + ghe-config app.babeld.host-key-ed25519 true + ``` +1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key. + + ```shell + ghe-config app.babeld.host-key-ed25519 false + ``` +{% data reusables.enterprise.apply-configuration %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md new file mode 100644 index 0000000000..88bb5ce695 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md @@ -0,0 +1,53 @@ +--- +title: Configuring SSH connections to your instance +shortTitle: Configure SSH connections +intro: 'You can increase the security of {% data variables.product.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.' +permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.' +versions: + ghes: '>= 3.6' +type: how_to +topics: + - Authentication + - Enterprise + - Infrastructure + - Networking + - Security + - SSH +--- + +## About SSH connections to your instance + +{% data reusables.enterprise.about-ssh-ports %} + +To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.product.product_location %} will accept. + +## Configuring SSH connections with RSA keys + +When users perform Git operations on {% data variables.product.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia. + +By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail. + +{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %} + +You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function. + +Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function. + +If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. 詳しい情報については「[SSH認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)」を参照してください。 + +詳細は [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server) を参照してください。 + +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. 詳しい情報については、「[コマンドラインユーティリティ](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)」を参照してください。 +1. To configure a cutoff date after which {% data variables.product.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website. + + 
+   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
+
+ +1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command. + + ```shell + ghe-config app.gitauth.rsa-sha1 false + ``` +{% data reusables.enterprise.apply-configuration %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md index 74891cb4a8..b59bf2c78b 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md @@ -25,6 +25,7 @@ children: - /site-admin-dashboard - /enabling-private-mode - /managing-github-mobile-for-your-enterprise + - /configuring-ssh-connections-to-your-instance - /configuring-email-for-notifications - /verifying-or-approving-a-domain-for-your-enterprise - /configuring-rate-limits @@ -34,6 +35,7 @@ children: - /command-line-utilities - /restricting-network-traffic-to-your-enterprise - /configuring-github-pages-for-your-enterprise + - /configuring-host-keys-for-your-instance - /configuring-the-referrer-policy-for-your-enterprise - /configuring-custom-footers - /configuring-web-commit-signing diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md index 40f97d05e0..a3c095be52 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md @@ -8,6 +8,7 @@ topics: - Enterprise redirect_from: - /admin/configuration/initializing-github-ae + - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae --- ## About initialization diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index f425311c63..5368353b1d 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." {% endif %} -You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit 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 %} +You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[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)" 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)."{% else %}{% ifversion audit-log-streaming %}"[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 {% endif %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %} ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png) diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md index 4724e3deb3..67e3be6efe 100644 --- a/translations/ja-JP/content/admin/guides.md +++ b/translations/ja-JP/content/admin/guides.md @@ -52,6 +52,8 @@ includeGuides: - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud + - /admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance + - /admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise - /admin/configuration/enabling-private-mode diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index 35436eba62..2bd37c0db0 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -10,8 +10,6 @@ topics: - Enterprise --- -{% data reusables.server-statistics.release-phase %} - ## About the benefits of {% data variables.product.prodname_server_statistics %} {% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md index 74f6367abd..02ce06f5c7 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md @@ -8,8 +8,6 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics --- -{% data reusables.server-statistics.release-phase %} - You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 @@ -20,7 +18,7 @@ To download these metrics, you must be an enterprise owner or organization owner - If {% data variables.product.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)." - If {% data variables.product.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)." -To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." +{% data variables.product.prodname_github_connect %}についてさらに学ぶには、「[{% data variables.product.prodname_github_connect %}について](/admin/configuration/configuring-github-connect/about-github-connect)」を参照してください。 ## Downloading metrics from your enterprise account diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md index 5bb42fb99d..5b18a392c4 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md @@ -8,8 +8,6 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api --- -{% data reusables.server-statistics.release-phase %} - You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md index 28afdf0355..5b072d3d57 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -39,9 +39,10 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you {%- ifversion enterprise-audit-log-ip-addresses %} - You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)." {%- endif %} -{%- ifversion ghec %} +{%- ifversion audit-log-streaming %} - You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[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 %} +{%- endif %} +{%- ifversion ghes %} - 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 %} @@ -50,13 +51,6 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you 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 %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index da858662b4..04345ecf20 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -59,7 +59,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe | ------------------ | --------------------------------------------- | | `artifact.destroy` | A workflow run artifact was manually deleted. | -{%- ifversion ghec %} +{%- ifversion audit-log-streaming %} ## `audit_log_streaming` category actions | アクション | 説明 | @@ -756,12 +756,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe ## `prebuild_configuration` category actions -| アクション | 説明 | -| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | -| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | -| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | -| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | +| アクション | 説明 | +| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。 | +| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。 | +| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。 | +| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。 | {%- endif %} {%- ifversion ghes %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index 26668f9a20..817fb15c5f 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -3,7 +3,7 @@ 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: - ghec: '*' + feature: audit-log-streaming type: tutorial topics: - Auditing @@ -17,6 +17,14 @@ redirect_from: permissions: Enterprise owners can configure audit log streaming. --- +{% ifversion ghes %} +{% note %} + +**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change. + +{% endnote %} +{% endif %} + ## 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: @@ -24,11 +32,11 @@ To help protect your intellectual property and maintain compliance for your orga 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 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.{% ifversion pause-audit-log-stream %} +* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %} * **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. +Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise. ## Setting up audit log streaming @@ -170,7 +178,7 @@ To configure the stream in {% data variables.product.prodname_dotcom %} you need 1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint. - ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png) + ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} @@ -213,7 +221,7 @@ You need two pieces of information about your event hub: its instance name and t 1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint. - ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png) + ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} @@ -269,9 +277,10 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma 1. Leave the **Enable SSL verification** check box selected. Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled. -1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png) +1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![エンドポイントのチェック](/assets/images/help/enterprises/audit-stream-check-splunk.png) {% data reusables.enterprise.verify-audit-log-streaming-endpoint %} +{% ifversion pause-audit-log-stream %} ## Pausing audit log streaming Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. @@ -284,6 +293,7 @@ Pausing the stream allows you to perform maintenance on the receiving applicatio 1. A confirmation message is displayed. Click **Pause stream** to confirm. When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs. +{% endif %} ## Deleting the audit log stream diff --git a/translations/ja-JP/content/admin/packages/index.md b/translations/ja-JP/content/admin/packages/index.md index 47935bee18..66f2d55667 100644 --- a/translations/ja-JP/content/admin/packages/index.md +++ b/translations/ja-JP/content/admin/packages/index.md @@ -14,6 +14,7 @@ children: - /enabling-github-packages-with-minio - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages - /configuring-package-ecosystem-support-for-your-enterprise + - /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry shortTitle: Manage GitHub Packages --- diff --git a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md new file mode 100644 index 0000000000..5b6feb7966 --- /dev/null +++ b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md @@ -0,0 +1,85 @@ +--- +title: Migrating your enterprise to the Container registry from the Docker registry +intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.' +versions: + feature: docker-ghcr-enterprise-migration +shortTitle: コンテナレジストリへの移行 +topics: + - Containers + - Docker + - Migration +--- + +{% data reusables.package_registry.container-registry-ghes-beta %} + +## {% data variables.product.prodname_container_registry %} について + +{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." + +For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." + +## About migration from the Docker registry + +{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}. + +{% ifversion ghes %} + +{% note %} + +**注釈**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} + +{% endnote %} + +{% endif %} + +{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)." + +## Migrating organizations to the {% data variables.product.prodname_container_registry %} + +You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}. + +If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.product.product_location %}, you will receive an email after the migration is complete. 詳しい情報については、「[通知のためのメールを設定する](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)」を参照してください。 + +{% note %} + +**{% ifversion ghes %}注釈{% elsif ghae %}注釈{% endif %}**: + +{%- ifversion ghes %} +- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity. +{%- endif %} +{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration. +{%- ifversion ghes %} +- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete. + +For more information about monitoring the performance and storage of {% data variables.product.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)." +{% endif %} + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. 左のサイドバーで**Packages**をクリックしてください。 +1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. + +After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure. + +## Re-running a failed organization migration + +Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail. + +1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)」を参照してください。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.packages-tab %} +1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. +1. If the migration fails again, start from step 1 and re-run the migration. + +{% ifversion ghes %} + +## Monitoring traffic to the registries + +You can use visualize traffic to the Docker registry and {% data variables.product.prodname_container_registry %} from {% data variables.product.product_location %}'s monitor dashboard. The "GitHub Container Package Registry" graph can help you confirm that you've successfully migrated all images to the {% data variables.product.prodname_container_registry %}. In the graph, "v1" represents traffic to the Docker registry, and "v2" represents traffic to the {% data variables.product.prodname_container_registry %}. 詳しい情報については、「[モニターダッシュボードへのアクセス](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)」を参照してください。 + +{% endif %} diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index dbca32c4a6..31b5f31638 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -13,6 +13,7 @@ redirect_from: - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise - /github/setting-up-and-managing-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account versions: ghec: '*' ghes: '*' diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 78eafe20e7..4edafc779b 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -203,6 +203,28 @@ Across all organizations owned by your enterprise, you can allow members with ad 4. [Repository upload limit] で、ドロップダウンメニューを使用して最大オブジェクトサイズをクリックします。 ![最大オブジェクトサイズのオプションを備えたドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png) 5. 必要に応じて、すべてのリポジトリにアップロードの最大制限を適用するには [**Enforce on all repositories**] を選択します。 ![すべてのリポジトリにオブジェクトの最大サイズを適用するオプション](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) +{% ifversion profile-name-enterprise-setting %} + +## Enforcing a policy for the display of member names in your repositories + +Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories. + +![コメントに表示されたコメント作者の名前](/assets/images/help/issues/commenter-full-name.png) + +{% note %} + +**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)". + +{% endnote %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.options-tab %} +4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. ![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png) +5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. ![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png) + +{% endif %} + ## リポジトリ間のプルリクエストのためのマージコンフリクトエディタを設定する ユーザが自分のコンピュータ上でローカルにマージコンフリクトを解決するように要求すれば、うっかりフォークから上流のリポジトリに書き込んでしまうことを回避できます。 @@ -265,10 +287,22 @@ Each repository inherits a default force push setting from the settings of the u {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} -{% ifversion ghes %} Enterprise で[プライベートモードを有効化](/enterprise/admin/configuration/enabling-private-mode)している場合は、{% else %}{% endif %}リポジトリ管理者がパブリックリポジトリへの匿名 Git 読み取りアクセスを有効化できるようにすることができます。 +If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories. 匿名 Git 読み取りアクセスを有効化すると、ユーザは Enterprise 上のカスタムツールの認証をバイパスできるようになります。 あなたもしくはリポジトリ管理者がこのアクセス設定をリポジトリで有効化すると、認証を受けていない Git の操作 (そして {% data variables.product.product_name %} へのネットワークアクセスができる人はだれでも) は、認証なしでリポジトリに読み取りアクセスできることになります。 +Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error. + +``` +The unauthenticated git protocol on port 9418 is no longer supported. +``` + +If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. 詳細は [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server) を参照してください。 + +{% endif %} + + + 必要に応じて、リポジトリのアクセス設定をロックすることで、リポジトリ管理者が Enterprise のリポジトリの匿名 Git アクセス設定を変更不可にすることができます。 リポジトリのGit読み取りアクセス設定をロックすると、サイト管理者だけがこの設定を変更できるようになります。 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} diff --git a/translations/ja-JP/content/admin/policies/index.md b/translations/ja-JP/content/admin/policies/index.md index b716198582..5c358faa49 100644 --- a/translations/ja-JP/content/admin/policies/index.md +++ b/translations/ja-JP/content/admin/policies/index.md @@ -4,7 +4,6 @@ intro: '{% data variables.product.product_name %} でポリシーを設定する redirect_from: - /enterprise/admin/developer-workflow - /enterprise/admin/policies - - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account versions: ghec: '*' ghes: '*' diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index a5784ea28a..2341764599 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -9,6 +9,9 @@ redirect_from: - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise + - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account intro: 'Organizationは企業内で、部署や同様のプロジェクトで作業を行うグループなど、個別のユーザグループを作成する素晴らしい手段です。 {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.' versions: ghec: '*' diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 831c946e65..707e3121e6 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -25,6 +25,10 @@ You can see all current enterprise members and enterprise administrators{% ifver You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name. +{% ifversion ghes > 3.5 %} +Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. 詳細は「[サイト管理者の昇格あるいは降格](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)」を参照してください。 +{% endif %} + {% ifversion not ghae %} You can also remove an administrator. 詳しい情報について。 see "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#removing-an-enterprise-administrator-from-your-enterprise-account)." {% endif %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 0c9d480028..e64b6f397c 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -14,7 +14,11 @@ topics: - SSH --- -When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." +## SSH について + +{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. + +When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。 diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index 8fff34f4e4..e00b4bd018 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -15,9 +15,20 @@ topics: shortTitle: Add a new SSH key --- -Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you should have: -* [既存の SSH キーの確認](/articles/checking-for-existing-ssh-keys) -* [新しい SSH キーを生成して ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +## About addition of SSH keys to your account + +{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." + +After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account. + +## 必要な環境 + +Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps. + +1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)." +1. Generate a new SSH key and add it to your machine's SSH agent. 詳しい情報については、「[新しい SSH キーを生成して ssh-agent に追加する](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 + +## Adding a new SSH key to your account After adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. 詳しい情報については[リモート URL の HTTPS から SSH への切り替え](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)を参照してください。 @@ -45,7 +56,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png) -5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。 +5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) {% data reusables.user-settings.sudo-mode-popup %} @@ -76,7 +87,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png) -5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。 +5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) 8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) @@ -108,7 +119,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} 4. [**New SSH key**] または [**Add SSH key**] をクリックします。 ![SSH キーボタン](/assets/images/help/settings/ssh-add-ssh-key.png) -5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば個人の Mac を使っている場合、このキーを "Personal MacBook Air" などと呼ぶことが考えられます。 +5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) 8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) @@ -146,5 +157,5 @@ gh ssh-key add ~/.ssh/id_ed25519.pub {% ifversion fpt or ghec %} ## 参考リンク -- [SAML シングルサインオンで使うためにSSHキーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on) +- [SAMLシングルサインオンで使うためにSSHキーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on) {% endif %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index 4a430ae839..1939f7202a 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -15,6 +15,16 @@ topics: shortTitle: Check for existing SSH key --- +## About SSH keys + +You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. 詳しい情報については「[SSHについて](/authentication/connecting-to-github-with-ssh/about-ssh)」を参照してください。 + +If you have an existing SSH key, you can use the key to authenticate Git operations over SSH. + +## 既存の SSH キーの確認 + +Before you generate a new SSH key, you should check your local machine for existing keys. + {% data reusables.ssh.key-type-support %} {% data reusables.command_line.open_the_multi_os_terminal %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index de0b97d03e..25cbb1a35f 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -17,72 +17,78 @@ topics: shortTitle: Generate new SSH key --- -## About SSH key generation +## About SSH key passphrases + +{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." + +When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase. If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). -If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase. - ## 新しい SSH キーを生成する +You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH. + +{% data reusables.ssh.key-type-support %} + {% data reusables.command_line.open_the_multi_os_terminal %} 2. 以下のテキストを貼り付けます。メールアドレスは自分の {% data variables.product.product_name %} メールアドレスに置き換えてください。 - {% ifversion ghae %} + {%- ifversion ghae %} - ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" - ``` - {% else %} - ```shell - $ ssh-keygen -t ed25519 -C "your_email@example.com" - ``` - {% note %} + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {%- else %} + ```shell + $ ssh-keygen -t ed25519 -C "your_email@example.com" + ``` + {% note %} - **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。 - ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" - ``` + **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。 + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` - {% endnote %} - {% endif %} + {% endnote %} + {%- endif %} - This creates a new SSH key, using the provided email as a label. - ```shell - > Generating public/private algorithm key pair. - ``` + This creates a new SSH key, using the provided email as a label. + ```shell + > Generating public/private algorithm key pair. + ``` 3. 「Enter a file in which to save the key」というメッセージが表示されたら、Enter キーを押します。 これにより、デフォルトのファイル場所が受け入れられます。 - {% mac %} + {% mac %} - ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] - ``` + ```shell + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] + ``` - {% endmac %} + {% endmac %} - {% windows %} + {% windows %} - ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] - ``` + ```shell + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] + ``` - {% endwindows %} + {% endwindows %} - {% linux %} + {% linux %} - ```shell - > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] - ``` + ```shell + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] + ``` - {% endlinux %} + {% endlinux %} 4. プロンプトで、安全なパスフレーズを入力します。 For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)." - ```shell - > Enter passphrase (empty for no passphrase): [Type a passphrase] - > Enter same passphrase again: [Type passphrase again] - ``` + ```shell + > Enter passphrase (empty for no passphrase): [Type a passphrase] + > Enter same passphrase again: [Type passphrase again] + ``` ## SSH キーを ssh-agent に追加する @@ -94,66 +100,55 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav 2. macOS Sierra 10.12.2 以降を使用している場合は、`~/.ssh/config` ファイルを修正して、キーが自動で ssh-agent に読み込まれ、キーチェーンにパスフレーズが記憶されるようにする必要があります。 - * まず、`~/.ssh/config` ファイルがデフォルトの場所にあるかどうかを確認します。 + * まず、`~/.ssh/config` ファイルがデフォルトの場所にあるかどうかを確認します。 - ```shell - $ open ~/.ssh/config - > The file /Users/you/.ssh/config does not exist. - ``` + ```shell + $ open ~/.ssh/config + > The file /Users/you/.ssh/config does not exist. + ``` - * ファイルがない場合は、ファイルを作成します。 + * ファイルがない場合は、ファイルを作成します。 - ```shell - $ touch ~/.ssh/config - ``` + ```shell + $ touch ~/.ssh/config + ``` - * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。 + * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。 - ``` - Host * - AddKeysToAgent yes - UseKeychain yes - IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} - ``` + ``` + Host * + AddKeysToAgent yes + UseKeychain yes + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} + ``` {% note %} - **注釈:** キーにパスフレーズを追加しない場合は、`UseKeychain` 行を省略してください。 + **ノート:** + - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line. + + - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section. + + ``` + Host * + IgnoreUnknown UseKeychain + ``` {% endnote %} - {% mac %} - {% note %} - - **Note:** If you see an error like this - - ``` - /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain - ``` - - add an additional config line to your `Host *` section: - - ``` - Host * - IgnoreUnknown UseKeychain - ``` - - {% endnote %} - {% endmac %} - 3. SSH 秘密鍵を ssh-agent に追加して、パスフレーズをキーチェーンに保存します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} - ``` - {% note %} + ``` + {% note %} - **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。 + **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。 - Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。 + Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。 - In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. + In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. - {% endnote %} + {% endnote %} 4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." @@ -164,11 +159,11 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav {% data reusables.desktop.windows_git_bash %} 1. ssh-agent が実行されていることを確認します. 「[SSH キーパスフレーズで操作する](/articles/working-with-ssh-key-passphrases)」の「ssh-agent を自動起動する」の手順を使用するか、手動で開始できます。 - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - ``` + ```shell + # start the ssh-agent in the background + $ eval "$(ssh-agent -s)" + > Agent pid 59566 + ``` 2. SSH プライベートキーを ssh-agent に追加します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %} {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} @@ -195,59 +190,50 @@ If you are using macOS or Linux, you may need to update your SSH client or insta 1. Insert your hardware security key into your computer. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. - ```shell - $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" - ``` + ```shell + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" + ``` - {% ifversion not ghae %} - {% note %} + {%- ifversion not ghae %} + {% note %} - **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. - ```shell - $ ssh-keygen -t ecdsa-sk -C "your_email@example.com" - ``` + **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. + ```shell + $ ssh-keygen -t ecdsa-sk -C "your_email@example.com" + ``` - {% endnote %} - {% endif %} + {% endnote %} + {%- endif %} 4. When you are prompted, touch the button on your hardware security key. 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. - {% mac %} + {% mac %} - ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] - ``` + ```shell + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] + ``` - {% endmac %} + {% endmac %} - {% windows %} + {% windows %} - ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] - ``` + ```shell + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] + ``` - {% endwindows %} + {% endwindows %} - {% linux %} + {% linux %} - ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] - ``` + ```shell + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] + ``` - {% endlinux %} + {% endlinux %} 6. When you are prompted to type a passphrase, press **Enter**. - ```shell - > Enter passphrase (empty for no passphrase): [Type a passphrase] - > Enter same passphrase again: [Type passphrase again] - ``` + ```shell + > Enter passphrase (empty for no passphrase): [Type a passphrase] + > Enter same passphrase again: [Type passphrase again] + ``` 7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." - - -## 参考リンク - -- 「[SSHについて](/articles/about-ssh)」 -- [SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases) -{%- ifversion fpt or ghec %} -- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %} -{%- endif %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md index 62764f2a15..8b2b0784c7 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md @@ -17,7 +17,9 @@ topics: shortTitle: SSH key passphrases --- -SSH キーにより、誰かがあなたのコンピュータにアクセスすると、そのキーを使用するすべてのシステムにもアクセスすることになります。 セキュリティをさらに強化するには、SSH キーにパスフレーズを追加します。 パスフレーズを安全に保存するために `ssh-agent` を使用すると、パスフレーズを再入力する必要がありません。 +## About passphrases for SSH keys + +With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. セキュリティをさらに強化するには、SSH キーにパスフレーズを追加します。 To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent. ## パスフレーズを追加または変更する @@ -105,7 +107,3 @@ OS X El Capitan を介する Mac OS X Leopard では、これらのデフォル それ以外の場合は、鍵を ssh-agent に追加するときに、パスフレーズをキーチェーンに格納できます。 詳細は「[SSH キーを ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)」を参照してください。 {% endmac %} - -## 参考リンク - -- 「[SSHについて](/articles/about-ssh)」 diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index 6f05b9af2a..adb05a61f9 100644 --- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -28,6 +28,8 @@ Commits and tags have the following verification statuses, depending on whether {% data reusables.identity-and-permissions.vigilant-mode-beta-note %} +Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." + ### Default statuses | Status | Description | diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md index a8a23d4df4..da469b1639 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md @@ -1,7 +1,7 @@ --- -title: Browsing security advisories in the GitHub Advisory Database -intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.' -shortTitle: Browse Advisory Database +title: GitHub Advisory Databaseのセキュリティアドバイザリの閲覧 +intro: '{% data variables.product.prodname_advisory_database %}を閲覧して、{% data variables.product.company_short %}でホストされているオープンソースプロジェクトのセキュリティリスクに対するアドバイザリを見つけることができます。' +shortTitle: Advisory Databaseの参照 miniTocMaxHeadingLevel: 3 redirect_from: - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database @@ -11,6 +11,8 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '*' + ghae: '*' type: how_to topics: - Security advisories @@ -19,126 +21,147 @@ topics: - Vulnerabilities - CVEs --- + -## About the {% data variables.product.prodname_advisory_database %} +## {% data variables.product.prodname_advisory_database %} について -The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities and malware, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories. +The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories. {% data reusables.repositories.tracks-vulnerabilities %} -## About types of security advisories +## セキュリティアドバイザリのタイプについて {% data reusables.advisory-database.beta-malware-advisories %} -Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects or for malicious open source software. +Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. -{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available. +通常、コード内の{% data reusables.repositories.a-vulnerability-is %}の脆弱性は、偶然に導入され、発見されるとすぐに修正されます。 依存関係の修正されたバージョンを使うよう、コードはできるかぎり早く更新しなければなりません。 -In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency. +{% ifversion GH-advisory-db-supports-malware %} -### {% data variables.product.company_short %}-reviewed advisories +対照的に、悪意のあるソフトウェア、またはマルウェアは、意図的に望ましくない、もしくは有害な機能を実行するように設計されたものです。 マルウェアは、ハードウェア、ソフトウェア、機密データ、あるいはマルウェアを使うアプリケーションのユーザを標的にする可能性があります。 マルウェアはプロジェクトから取り除き、その依存関係の安全な代替物を見つけなければなりません。 -{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities or malware that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information. +{% endif %} -Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry. +### {% data variables.product.company_short %}がレビューしたアドバイザリ -- Composer (registry: https://packagist.org/) -- Erlang (registry: https://hex.pm/) -- Go (registry: https://pkg.go.dev/) -- Maven (registry: https://repo1.maven.org/maven2/org/) -- npm (registry: https://www.npmjs.com/) -- NuGet (registry: https://www.nuget.org/) -- pip (registry: https://pypi.org/) -- RubyGems (registry: https://rubygems.org/) -- Rust (registry: https://crates.io/) +{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. 各アドバイザリの有効性は慎重にレビューされ、完全な説明が成されており、エコシステムとパッケージの両方の情報が含まれていることが保証されています。 -If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion. +一般的に、サポートされているエコシステムはソフトウェアプログラミング言語の関連するパッケージレジストリにちなんで名付けられています。 アドバイザリは、サポートされているレジストリから来たパッケージ内の脆弱性に対するものであれば、レビューが行われます。 -If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability or malware for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %} +- Erlang (registry: https://hex.pm/){% endif %} +- Go (レジストリ: https://pkg.go.dev/) +- Maven (レジストリ: https://repo1.maven.org/maven2/org/) +- npm (レジストリ: https://www.npmjs.com/) +- NuGet (レジストリ: https://www.nuget.org/) +- pip (レジストリ: https://pypi.org/) +- RubyGems (レジストリ: https://rubygems.org/) +- Rust (レジストリ: https://crates.io/) -### Unreviewed advisories +サポートすべき新しいエコシステムの提案がある場合は、議論のための[Issue](https://github.com/github/advisory-database/issues)をオープンしてください。 -Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. +If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 -{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion. +### レビューされていないアドバイザリ -## About information in security advisories +レビューされていないアドバイザリは、自動的にNational Vulnerability Databaseフィードから直接{% data variables.product.prodname_advisory_database %}へ展開されたセキュリティ脆弱性です。 -Each security advisory contains information about the vulnerability or malware, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology. +この種のアドバイザリは妥当性あるいは完全性がチェックされていないので、レビューされていないアドバイザリに対して{% data variables.product.prodname_dependabot %}は{% data variables.product.prodname_dependabot_alerts %}を生成しません。 -The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)." +## セキュリティアドバイザリ内の情報について + +Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. さらに、National Vulnerability Database リストのアドバイザリには、CVE レコードへのリンクが含まれており、脆弱性、その CVSS スコア、その定性的な重要度レベルの詳細を確認できます。 詳しい情報については、アメリカ国立標準技術研究所の「[National Vulnerability Database](https://nvd.nist.gov/)"」を参照してください。 + +重大度レベルは「[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)」で定義されている 4 つのレベルのいずれかです。 - Low - Medium/Moderate - High - Critical -The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1. +{% data variables.product.prodname_advisory_database %} は、上記の CVSS レベルを使用します。 {% data variables.product.company_short %} が CVE を取得した場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.1 を使用します。 CVE がインポートされた場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.0 と 3.1 の両方をサポートします。 {% data reusables.repositories.github-security-lab %} -## Accessing an advisory in the {% data variables.product.prodname_advisory_database %} +## {% data variables.product.prodname_advisory_database %} のアドバイザリにアクセスする -1. Navigate to https://github.com/advisories. -2. Optionally, to filter the list, use any of the drop-down menus. - ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png) +1. Https://github.com/advisories にアクセスします。 +2. 必要に応じて、リストをフィルタするには、ドロップダウンメニューを使用します。 ![ドロップダウンフィルタ](/assets/images/help/security/advisory-database-dropdown-filters.png) {% tip %} - **Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately. + **参考:** 左側のサイドバーを使って、{% data variables.product.company_short %}がレビューしたアドバイザリとレビューされていないアドバイザリを個別に調べることができます。 {% endtip %} -3. Click on any advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar. +3. Click an advisory to view details. デフォルトでは、セキュリティ脆弱性に対する{% data variables.product.company_short %}がレビューしたアドバイザリが表示されます。 {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %} {% note %} -The database is also accessible using the GraphQL API. By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)." +データベースは、GraphQL API を使用してアクセスすることもできます。 {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)." {% endnote %} -## Editing an advisory in the {% data variables.product.prodname_advisory_database %} -You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." +## {% data variables.product.prodname_advisory_database %}中のアドバイザリの編集 +{% data variables.product.prodname_advisory_database %}のアドバイザリには、改善を提案できます。 詳しい情報については「[{% data variables.product.prodname_advisory_database %}中のセキュリティアドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。 -## Searching the {% data variables.product.prodname_advisory_database %} +## {% data variables.product.prodname_advisory_database %} を検索する -You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. +データベースを検索し、修飾子を使用して検索を絞り込むことができます。 たとえば、特定の日付、特定のエコシステム、または特定のライブラリで作成されたアドバイザリを検索できます。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Example | -| ------------- | ------------- | -| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. | -| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. | -| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. | -| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | -| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | -| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | -| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | -| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | -| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | -| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | -| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | -| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | -| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | -| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | -| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | -| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | -| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | +| 修飾子 | サンプル | +| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed)は、セキュリティ脆弱性に対する{% data variables.product.company_short %}がレビューしたアドバイザリを表示します。 | +{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. | +{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. | +| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | -## Viewing your vulnerable repositories +## 脆弱性のあるリポジトリを表示する -For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability or malware. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." +For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 脆弱性のあるリポジトリを確認するには、そのリポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできる必要があります。 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。 -1. Navigate to https://github.com/advisories. -2. Click an advisory. -3. At the top of the advisory page, click **Dependabot alerts**. - ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) -4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). - ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) -5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name. +1. Https://github.com/advisories にアクセスします。 +2. アドバイザリをクリックします。 +3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabotアラート](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. 必要に応じて、リストをフィルタするには、検索バーまたはドロップダウンメニューを使用します。 [Organization] ドロップダウンメニューを使用すると、オーナー（Organization またはユーザ）ごとに {% data variables.product.prodname_dependabot_alerts %} をフィルタできます。 ![アラートをフィルタするための検索バーとドロップダウンメニュー](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. アドバイザリに関する詳細、そして脆弱性のあるリポジトリの修正方法に関するアドバイスについては、リポジトリ名をクリックしてください。 -## Further reading +{% ifversion security-advisories-ghes-ghae %} +## Accessing the local advisory database on {% data variables.product.product_location %} -- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability) +If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. 詳しい情報については「[{% data variables.product.prodname_github_connect %}について](/admin/configuration/configuring-github-connect/about-github-connect)」を参照してください。 + +You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. + +1. Navigate to `https://HOSTNAME/advisories`. +2. 必要に応じて、リストをフィルタするには、ドロップダウンメニューを使用します。 ![ドロップダウンフィルタ](/assets/images/help/security/advisory-database-dropdown-filters.png) + {% note %} + + **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". + + {% endnote %} +3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %} + +You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". + +### Viewing vulnerable repositories for {% data variables.product.product_location %} + +{% data reusables.repositories.enable-security-alerts %} + +In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 脆弱性のあるリポジトリを確認するには、そのリポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできる必要があります。 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。 + +1. Navigate to `https://HOSTNAME/advisories`. +2. アドバイザリをクリックします。 +3. アドバイザリページの上部にある [**Dependabot alerts**] をクリックします。 ![Dependabotアラート](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. 必要に応じて、リストをフィルタするには、検索バーまたはドロップダウンメニューを使用します。 [Organization] ドロップダウンメニューを使用すると、オーナー（Organization またはユーザ）ごとに {% data variables.product.prodname_dependabot_alerts %} をフィルタできます。 ![アラートをフィルタするための検索バーとドロップダウンメニュー](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. アドバイザリに関する詳細、そして脆弱性のあるリポジトリの修正方法に関するアドバイスについては、リポジトリ名をクリックしてください。 + +{% endif %} + +## 参考リンク + +- MITREの[「脆弱性」の定義](https://www.cve.org/ResourcesSupport/Glossary#vulnerability) diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md index d0242bc452..85e085d51b 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md @@ -7,6 +7,8 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '*' + ghae: '*' type: how_to topics: - Security advisories @@ -19,8 +21,9 @@ shortTitle: Advisory Databaseの編集 ## {% data variables.product.prodname_advisory_database %}内のアドバイザリの編集について [github.com/advisories](https://github.com/advisories)にある{% data variables.product.prodname_advisory_database %}中のセキュリティアドバイザリは、グローバルなアドバイザリとみなされています。 {% data variables.product.prodname_advisory_database %}中のグローバルなセキュリティアドバイザリには、誰でも改善を提案できます。 追加で影響を受けるエコシステム、重要度、影響を受ける人の説明を含む、いかなる詳細も編集や追加ができます。 {% data variables.product.prodname_security %}のキュレーションチームは提案された改善をレビューし、受理されればそれらを{% data variables.product.prodname_advisory_database %}上に公開します。 +{% ifversion fpt or ghec %} +リポジトリレベルのセキュリティアドバイザリを編集できるのは、リポジトリのオーナーと管理者のみです。 For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %} -リポジトリレベルのセキュリティアドバイザリを編集できるのは、リポジトリのオーナーと管理者のみです。 詳しい情報については、「[リポジトリのセキュリティアドバイザリの編集](/code-security/security-advisories/editing-a-security-advisory)」を参照してください。 ## GitHub Advisory Database中のアドバイザリの編集 1. Https://github.com/advisories にアクセスします。 @@ -30,4 +33,15 @@ shortTitle: Advisory Databaseの編集 5. アドバイザリの編集を終えたら、**Submit improvements（改善を提案）**をクリックしてください。 6. 改善を提案したら、その変更を含むPull Requestが{% data variables.product.prodname_security %}キュレーションチームによって[github/advisory-database](https://github.com/github/advisory-database)内にレビューのために作成されます。 そのアドバイザリの発生元が{% data variables.product.prodname_dotcom %}リポジトリなら、オプションのコメントのためにオリジナルの公開者をタグ付けします。 あなたはこのPull Requestを見ることができ、このPull Requestが更新されるかクローズされると通知を受けます。 -[github/advisory-database](https://github.com/github/advisory-database)リポジトリ中のアドバイザリファイルに対して直接Pull Requestをオープンすることもできます。 詳しい情報については[コントリビューションのガイドライン](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)を参照してください。 +[github/advisory-database](https://github.com/github/advisory-database)リポジトリ中のアドバイザリファイルに対して直接Pull Requestをオープンすることもできます。 詳しい情報については[コントリビューションのガイドライン](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)を参照してください。 + +{% ifversion security-advisories-ghes-ghae %} +## Editing advisories from {% data variables.product.product_location %} + +If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. + +1. Navigate to `https://HOSTNAME/advisories`. +2. コントリビュートしたいセキュリティアドバイザリを選択してください。 +3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. ![改善提案リンク](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png) +4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above. +{% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md index f32ea8da46..dc4ff2dc9e 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md @@ -57,7 +57,7 @@ topics: ## 通信トークンの保護 -コードはしばしば、ネットワークを介して他のシステムと通信しなければならず、認証のためのシークレット（パスワードやAPIキーなど）を必要とします。 システムが実行されるためにはそれらのシークレットにアクセスできなければなりませんが、それらをソースコードには含めないのがベストプラクティスです。 これは特にパブリックリポジトリで重要ですが、多くの人々がアクセスするかもしれないプライベートリポジトリでも重要です。 +コードはしばしば、ネットワークを介して他のシステムと通信しなければならず、認証のためのシークレット（パスワードやAPIキーなど）を必要とします。 システムが実行されるためにはそれらのシークレットにアクセスできなければなりませんが、それらをソースコードには含めないのがベストプラクティスです。 これは特に、多くの人がアクセスするかもしれないリポジトリで重要で{% ifversion not ghae %}あり、パブリックリポジトリではきわめて重要で{% endif %}す。 ### リポジトリのコミットされたシークレットの自動検出 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index ed9358a0c2..7d3517de96 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -70,7 +70,7 @@ The recommended formats explicitly define which versions are used for all direct | Package manager | Languages | Recommended formats | All supported formats | | --- | --- | --- | ---| {%- ifversion dependency-graph-rust-support %} -| Cargo[*] | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | +| Cargo{% ifversion ghes = 3.6 or ghae-issue-7563 %}[*]{% endif %} | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | {%- endif %} | Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | | NuGet | .NET languages (C#, F#, VB), C++ | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | @@ -91,7 +91,7 @@ The recommended formats explicitly define which versions are used for all direct | RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | -{% ifversion dependency-graph-rust-support %} +{% ifversion ghes = 3.6 or ghae-issue-7563 %} [*] For the initial release of Rust support, dependency graph does not have the metadata and mappings required to detect transitive dependencies. Dependency graph displays transitive dependencies, one level deep, when they are defined in a `Cargo.lock` file. {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are available for vulnerable dependencies defined in the `Cargo.lock` file. {% endif %} diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md index 4fa92e8d97..9a7ab09688 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md @@ -28,7 +28,7 @@ redirect_from: In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. この新しい codespace には、{% data variables.product.prodname_dotcom %} への最後のプッシュ時点までのすべての変更が含まれます。 For information on manually setting another region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)." -You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." +You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. 詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。 ## オプション 2: リカバリを待つ diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md index 29dd25e8ae..d854370012 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -58,7 +58,7 @@ If you need to allow external access to services running on a codespace, you can If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet. -Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." +Organizationのオーナーは、ポートのフォワードをパブリックに、あるいはOrganization内で利用できるようにする機能を制限できます。 For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." **Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}. diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md index 9b94956da9..7446407522 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md @@ -29,7 +29,7 @@ redirect_from: 2. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}. 3. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. -4. In the {% data variables.product.prodname_codespaces %} tab, click **Create codespace on BRANCH**. ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) +4. In the {% data variables.product.prodname_codespaces %} tab, click **Create codespace on BRANCH**. ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/open-with-codespaces-pr.png) ## Reviewing a pull request in {% data variables.product.prodname_codespaces %} @@ -41,4 +41,4 @@ For more information on reviewing a pull request, see "[Reviewing proposed chang Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. - ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png) + ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/incorporating-codespaces.png) diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index a565155d35..78c502e971 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -2,8 +2,7 @@ title: ディスカッションについて intro: 'ディスカッションでは、質問、質問への回答、情報の共有、発表、{% data variables.product.product_name %} 上のプロジェクトについて会話を実施したり参加したりすることができます。' versions: - fpt: '*' - ghec: '*' + feature: discussions --- @@ -22,7 +21,7 @@ You might use repository discussions to discuss topics that are specific to the Issue やプルリクエストをクローズするように、ディスカッションをクローズする必要はありません。 -If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion. +If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who has access to the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion. リポジトリ管理者とプロジェクトメンテナは、リポジトリ内のディスカッションとディスカッションカテゴリを管理し、ディスカッションを固定してディスカッションの可視性を高めることができます。 モデレータとコラボレータは、コメントを回答としてマークしたり、ディスカッションをロックしたり、Issue をディスカッションに変換したりすることができます。 Similarly, for organization discussions, the role of a user in the source repository determines how a user can interact with organization discussions. 詳しい情報については「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。 @@ -30,7 +29,7 @@ For more information about management of discussions, see "[Managing discussions ## About polls -You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results. Logged out users can view the results of polls in public repositories. +You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results.{% ifversion fpt or ghec %} Signed out users can view the results of polls in public repositories.{% endif %} Polls require a question and at least two options. You can add a maximum of eight options and the options can contain a maximum of 128 characters. @@ -71,5 +70,5 @@ For more information, see "[Managing categories for discussions](/discussions/ma - 「[{% data variables.product.prodname_dotcom %} での書き方と書式設定について](/github/writing-on-github/about-writing-and-formatting-on-github)」 - 「[ディスカッションを検索する](/search-github/searching-on-github/searching-discussions)」 - 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」 -- [コメントと会話の管理](/communities/moderating-comments-and-conversations) -- 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/communities/maintaining-your-safety-on-github)」 +- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"{% ifversion fpt or ghec %} +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"{% endif %} diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index ce9ee36260..3003a7986a 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -4,8 +4,7 @@ shortTitle: メンテナとコラボレーションする intro: 'ディスカッションでプロジェクトのメンテナと連絡を取り合うことにより、{% data variables.product.product_name %} でプロジェクトの目標、計画、健全性、およびコミュニティに貢献できます。' permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: - fpt: '*' - ghec: '*' + feature: discussions --- @@ -53,4 +52,6 @@ You can search for discussions and filter the list of discussions in a repositor ## 参考リンク - 「[{% data variables.product.prodname_dotcom %} での書き方と書式設定について](/github/writing-on-github/about-writing-and-formatting-on-github)」 +{%- ifversion fpt or ghec %} - 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/communities/maintaining-your-safety-on-github)」 +{%- endif %} diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md index a486627af1..c2e15ed5cc 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -3,8 +3,7 @@ title: ディスカッションを使用してコミュニティとコラボレ shortTitle: ディスカッションを使用してコラボレーションする intro: コミュニティメンバーや他のメンテナと集まってプロジェクトについてディスカッションしましょう。 versions: - fpt: '*' - ghec: '*' + feature: discussions children: - /about-discussions - /participating-in-a-discussion diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index aafa78e79a..5630ff6f95 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -3,8 +3,7 @@ title: ディスカッションに参加する intro: '{% data variables.product.product_name %} のプロジェクトのリポジトリ内のフォーラムで、コミュニティやメンテナと会話することができます。' permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: Participate in discussion --- @@ -15,7 +14,7 @@ shortTitle: Participate in discussion In addition to starting or viewing discussions and polls, you can comment in response to the original comment from the author of the discussion. また、ディスカッション内で別のコミュニティメンバーが行った個々のコメントに返信してコメントスレッドを作成し、絵文字でコメントにリアクションすることもできます。 -{% data variables.product.product_name %} で、ユーザをブロックし、破壊的なコンテンツを報告して、安全で快適な環境を維持できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} での安全を維持する](/communities/maintaining-your-safety-on-github)」を参照してください。 +{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %} ## 必要な環境 diff --git a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 37a870574f..6e0bc950d2 100644 --- a/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -1,10 +1,9 @@ --- title: GitHub におけるコミュニティの会話のベストプラクティス shortTitle: コミュニティの会話のベストプラクティス -intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.' +intro: ディスカッションを使用してチームとブレインストーミングを行い、作業を確認する状況が整ったら、最終的に会話を Issue に移すことができます。 versions: - fpt: '*' - ghec: '*' + feature: discussions --- @@ -22,7 +21,7 @@ Issue のオープンおよびディスカッションの相互参照につい 希望する会話のタイプに応じて、ディスカッション、Issue、プルリクエストを作成して参加できます。 -You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams if: +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios. - You are in the discovery phase of a project and are still learning which direction your team wants to go in - より広いコミュニティからプロジェクトについてのフィードバックを収集する必要がある場合 - バグ修正、機能リクエスト、一般的な会話を別々に保持する必要がある場合 @@ -34,7 +33,7 @@ Issueは、バグレポートや計画された改善など、プロジェクト ## コントリビューションガイドラインに従う -Before you open a discussion in an open source repository, check to see if the repository has contributing guidelines. CONTRIBUTING ファイルには、リポジトリメンテナがプロジェクトにアイデアを提供する方法に関する情報が含まれています。 +Before you open a discussion in a repository, check to see if the repository has contributing guidelines. CONTRIBUTING ファイルには、リポジトリメンテナがプロジェクトにアイデアを提供する方法に関する情報が含まれています。 詳しい情報については、「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。 diff --git a/translations/ja-JP/content/discussions/guides/finding-your-discussions.md b/translations/ja-JP/content/discussions/guides/finding-your-discussions.md index dd71f0eb48..59e9b65698 100644 --- a/translations/ja-JP/content/discussions/guides/finding-your-discussions.md +++ b/translations/ja-JP/content/discussions/guides/finding-your-discussions.md @@ -2,8 +2,7 @@ title: Finding your discussions intro: You can easily access every discussion you've created or participated in. versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: Find discussions redirect_from: - /discussions/guides/finding-discussions-across-multiple-repositories @@ -12,8 +11,7 @@ redirect_from: ## ディスカッションを検索する -1. {% data variables.product.prodname_dotcom_the_website %}に移動します。 -1. {% data variables.product.prodname_dotcom_the_website %} の右上隅にあるプロフィール画像をクリックしてから、[**Your discussions**] をクリックします。 ![{% data variables.product.product_name %} のプロフィール画像のドロップダウンメニューにある [Your discussions]](/assets/images/help/discussions/your-discussions.png) +1. {% data variables.product.product_location %} の右上隅にあるプロフィール画像をクリックしてから、[**Your discussions**] をクリックします。 ![{% data variables.product.product_name %} のプロフィール画像のドロップダウンメニューにある [Your discussions]](/assets/images/help/discussions/your-discussions.png) 1. [**Created**] と [**Commented**] を切り替えて、作成または参加したディスカッションを表示します。 ## 参考リンク diff --git a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 3b7b1d0d22..dbd4b46d2c 100644 --- a/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -2,8 +2,7 @@ title: 上位コントリビューターにより高い権限を付与する intro: リポジトリ管理者は、コミュニティメンバーをモデレータおよびメンテナに昇格させることができます。 versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: Grant higher permissions --- @@ -16,11 +15,11 @@ shortTitle: Grant higher permissions {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} -1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. +1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. ![Screenshot of most helpful contributors](/assets/images/help/discussions/most-helpful.png) ## Step 2: Review permission levels for {% data variables.product.prodname_discussions %} -People with triage permissions for a repository can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, people with triage permissions for the source repository for organization discussions can moderate the organization's discussions. 詳しい情報については、「[ ディスカッションをモデレートする](/discussions/managing-discussions-for-your-community/moderating-discussions)」を参照してください。 +People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, people with triage permissions for the source repository for organization discussions can moderate the organization's discussions. 詳しい情報については、「[ ディスカッションをモデレートする](/discussions/managing-discussions-for-your-community/moderating-discussions)」を参照してください。 リポジトリの権限レベルおよび {% data variables.product.prodname_discussions %} に関する詳しい情報については、「[Organization のリポジトリの権限レベル](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)」を参照してください。 diff --git a/translations/ja-JP/content/discussions/guides/index.md b/translations/ja-JP/content/discussions/guides/index.md index bad942ecd6..90b71e25ff 100644 --- a/translations/ja-JP/content/discussions/guides/index.md +++ b/translations/ja-JP/content/discussions/guides/index.md @@ -3,8 +3,7 @@ title: ディスカッションガイド shortTitle: ガイド intro: コミュニティのディスカッションに参加したりモニタリングしたりするための最初のステップやベストプラクティスを学びましょう。 versions: - fpt: '*' - ghec: '*' + feature: discussions children: - /best-practices-for-community-conversations-on-github - /finding-your-discussions diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md index a6945f78ce..c758d50bbc 100644 --- a/translations/ja-JP/content/discussions/index.md +++ b/translations/ja-JP/content/discussions/index.md @@ -1,7 +1,7 @@ --- title: GitHub Discussions のドキュメント shortTitle: GitHub Discussions -intro: '{% data variables.product.prodname_discussions %} は、オープンソースプロジェクトに関するコミュニティ向けの共同コミュニケーションフォーラムです。 コミュニティメンバーは、質問をしたり、質問に答えたり、最新情報を共有したり、自由形式の会話をしたり、コミュニティの動向に影響を与える決定をフォローしたりすることができます。' +intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. コミュニティメンバーは、質問をしたり、質問に答えたり、最新情報を共有したり、自由形式の会話をしたり、コミュニティの動向に影響を与える決定をフォローしたりすることができます。' introLinks: quickstart: /discussions/quickstart featuredLinks: @@ -27,8 +27,7 @@ examples_source: data/product-examples/discussions/community-examples.yml product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk' layout: product-landing versions: - fpt: '*' - ghec: '*' + feature: discussions communityRedirect: name: Provide GitHub Feedback href: 'https://github.com/github/feedback/discussions/categories/discussions-feedback' diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md index bcf178bdca..79a8c1d66d 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md @@ -3,8 +3,7 @@ title: コミュニティのディスカッションを管理する shortTitle: ディスカッションを管理する intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' versions: - fpt: '*' - ghec: '*' + feature: discussions children: - /managing-discussions - /managing-categories-for-discussions diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md index 5c272e063b..1c9269cf27 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md @@ -3,8 +3,7 @@ title: Managing categories for discussions intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.' permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization. versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: Manage categories redirect_from: - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository @@ -23,7 +22,7 @@ redirect_from: | カテゴリ | 目的 | Format | |:--------------- |:--------------------------------------------------------------------- |:--------------- | -| 📣 Announcements | Updates and news from project maintainers | Announcement | +| 📣 Announcements | Updates and news from project maintainers | アナウンス | | #️⃣ 全般 | プロジェクトに関連するすべての事柄 | 自由回答形式のディスカッション | | 💡 Ideas | プロジェクトを変更または改善するためのアイデア | 自由回答形式のディスカッション | | 🗳 Polls | Polls with multiple options for the community to vote for and discuss | Polls | @@ -43,7 +42,7 @@ redirect_from: カテゴリを編集して、カテゴリの絵文字、タイトル、説明、およびディスカッション形式を変更できます。 -1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category. +1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to edit a category. {% data reusables.discussions.discussions-tab %} 1. リストのカテゴリの右側にある {% octicon "pencil" aria-label="The pencil icon" %} をクリックします ![リポジトリのカテゴリリストのカテゴリの右側にある [Edit] ボタン](/assets/images/help/discussions/click-edit-for-category.png) 1. {% data reusables.discussions.edit-category-details %} @@ -54,7 +53,7 @@ redirect_from: カテゴリを削除すると、{% data variables.product.product_name %} は、削除されたカテゴリのすべてのディスカッションを、選択した既存のカテゴリに移動します。 -1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category. +1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to delete a category. {% data reusables.discussions.discussions-tab %} 1. リストのカテゴリの右側にある {% octicon "trash" aria-label="The trash icon" %} をクリックします ![リポジトリのカテゴリリストのカテゴリの右側にある [Trash] ボタン](/assets/images/help/discussions/click-delete-for-category.png) 1. ドロップダウンメニューを使用して、削除するカテゴリのディスカッションの新しいカテゴリを選択します。 ![既存のカテゴリを削除するときに新しいカテゴリを選択するためのドロップダウンメニュー](/assets/images/help/discussions/choose-new-category.png) diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 05efb78422..5e7528c51f 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -3,8 +3,7 @@ title: ディスカッションを管理する intro: 'You can categorize, spotlight, transfer, or delete the discussions.' permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization. versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: Manage discussions redirect_from: - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository @@ -17,7 +16,7 @@ redirect_from: Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. 詳しい情報については、「[Organization 内のリポジトリのディスカッションの作成を管理する](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)」を参照してください。 -ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 コラボレータが従う行動規範またはコントリビューションガイドラインを作成することは、協力的で生産的なフォーラムを促進するのに役立ちます。 コミュニティリソースの作成について詳しくは、「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および 「[リポジトリコントリビューター向けのガイドラインを設定する](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。 +ディスカッションのメンテナとして、コミュニティリソースを作成して、プロジェクト全体の目標に沿ったディスカッションを促し、コラボレータのための親しみやすいオープンフォーラムを維持できます。 Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)」を参照してください。 @@ -75,7 +74,7 @@ You can pin up to four important discussions above the list of discussions for t ## ディスカッションを移譲する -ディスカッションを移譲するには、ディスカッションを移譲するリポジトリにディスカッションを作成する権限が必要です。 If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private repository to a public repository. +ディスカッションを移譲するには、ディスカッションを移譲するリポジトリにディスカッションを作成する権限が必要です。 If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository. {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md index 7836edd013..85a48e2119 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -1,16 +1,15 @@ --- title: ディスカッションをモデレートする -intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct.' +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.' permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization. versions: - fpt: '*' - ghec: '*' + feature: discussions --- ## ディスカッションのモデレートについて -{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization. +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization. ## コメントを回答としてマークする diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md index fbb5d13ed5..0a465b1ced 100644 --- a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md @@ -3,8 +3,7 @@ title: Viewing insights for your discussions intro: 'Discussions insights provide data about your discussions'' activity, views, and contributors.' permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization. versions: - fpt: '*' - ghec: '*' + feature: discussions topics: - Discussions shortTitle: View discussions insights diff --git a/translations/ja-JP/content/discussions/quickstart.md b/translations/ja-JP/content/discussions/quickstart.md index 33566f3d4a..c24ed0dcb2 100644 --- a/translations/ja-JP/content/discussions/quickstart.md +++ b/translations/ja-JP/content/discussions/quickstart.md @@ -3,21 +3,20 @@ title: GitHub Discussions のクイックスタート intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.' allowTitleToDifferFromFilename: true versions: - fpt: '*' - ghec: '*' + feature: discussions shortTitle: クイックスタート --- ## はじめに -{% data variables.product.prodname_discussions %} は、オープンソースプロジェクトに関するコミュニティ向けの共同コミュニケーションフォーラムです。 Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions により、公開フォーラムで流動的でオープンな会話ができるようになります。 +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions により、公開フォーラムで流動的でオープンな会話ができるようになります。 Discussions では、より協力的な会話ができるように、情報に接続して検索するためのより一元的なエリアを提供しています。 ## リポジトリの {% data variables.product.prodname_discussions %} を有効化する -Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public and private repositories. +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in. When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. @@ -29,7 +28,7 @@ When you first enable {% data variables.product.prodname_discussions %}, you wil ## Enabling {% data variables.product.prodname_discussions %} on your organization -Organization owners can enable {% data variables.product.prodname_discussions %} for their organization. +Organizationのオーナーは、自分のOrganizationで{% data variables.product.prodname_discussions %}を有効化できます。 {% data reusables.discussions.about-organization-discussions %} @@ -42,7 +41,7 @@ You can welcome your community and introduce a new way to communicate in a repos ## コントリビューター向けのコミュニティガイドラインを設定する -For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. リポジトリの README を更新して、コラボレータが Issue やディスカッションをオープンするタイミングを伝えることもできます。 プロジェクトのガイドラインの提供方法の詳細については、「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および 「[健全なコントリビューションのためのプロジェクトの設定](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。 +For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. リポジトリの README を更新して、コラボレータが Issue やディスカッションをオープンするタイミングを伝えることもできます。 For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." For organization discussions, you share information about how to engage with your organization by creating an organization profile README. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)." @@ -62,7 +61,7 @@ Any authenticated user who can view a repository can create a poll. Similarly, s Repository owners and people with write access to the repository can create new categories to keep discussions organized. Similarly, since organization discussions are based on a source repository, repository owners and people with write access to the source repository can create new categories for organization discussions. -参加しているコラボレータが新しいディスカッションを作成する場合、ディスカッションを最も関連性の高い既存のカテゴリにグループ化できます。 ディスカッションは、作成後に再分類することもできます。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." +Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. ディスカッションは、作成後に再分類することもできます。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." {% data reusables.discussions.you-can-label-discussions %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md index e741ab09ae..6fd7923662 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -136,7 +136,7 @@ Notifications provide updates about the activity on {% data variables.product.pr ### 8. {% data variables.product.prodname_pages %} の活用 You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。 -{% ifversion fpt or ghec %} +{% ifversion discussions %} ### 9. {% data variables.product.prodname_discussions %}を使用する You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md index 7f7636461a..e95b28ed6b 100644 --- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md +++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md @@ -24,10 +24,9 @@ topics: {% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs. -{% ifversion fpt or ghec %} +{% ifversion discussions %} You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have. -{% endif %} -{% ifversion ghes or ghae %} +{% else %} You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have. {% endif %} @@ -100,7 +99,7 @@ The **Files changed** tab of the pull request shows the implemented fix. - The user creates a pull request with the fix. - A repository maintainer reviews the pull request, comments on it, and merges it. -{% ifversion fpt or ghec %} +{% ifversion discussions %} ### Scenarios for {% data variables.product.prodname_discussions %} - I have a question that's not necessarily related to specific files in the repository. @@ -147,8 +146,8 @@ For issues, for example, you can tag issues with labels for quicker searching an For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)を参照してください。 -{% ifversion fpt or ghec %} -For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 +{% ifversion discussions %} +For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 {% endif %} For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)を参照してください。 diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md index 25ea9223f6..267a791258 100644 --- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md @@ -47,7 +47,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a | G P | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。"{% ifversion fpt or ghes or ghec %} | G A | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %} | G B | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | -| G W | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %} +| G W | [**Wiki**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %} | G G | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %} ## ソースコード編集 diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md index 42bc9af90d..e536c4a135 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md @@ -69,7 +69,7 @@ Look! You can see my backticks. {% ifversion mermaid %} ## Creating diagrams -You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, geoJSON, topoJSON, and ASCII STL syntax. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)." +You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, GeoJSON, TopoJSON, and ASCII STL syntax. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)." {% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index 58b21e3a35..edda6cad81 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -38,11 +38,11 @@ graph TD; {% endnote %} -## Creating geoJSON and topoJSON maps +## Creating GeoJSON and TopoJSON maps -You can use geo/topoJSON syntax to create interactive maps. To create a map, add geoJSON or topoJSON inside a fenced code block with the `geojson` or `topojson` syntax identifier. 詳しい情報については[コードブロックの作成とハイライト](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)を参照してください。 +You can use GeoJSON/TopoJSON syntax to create interactive maps. To create a map, add GeoJSON or TopoJSON inside a fenced code block with the `geojson` or `topojson` syntax identifier. 詳しい情報については[コードブロックの作成とハイライト](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)を参照してください。 -### Using geoJSON +### Using GeoJSON For example, you can create a simple map: @@ -77,9 +77,9 @@ For example, you can create a simple map: ![Rendered map](/assets/images/help/writing/fenced-geojson-rendered-map.png) -### Using topoJSON +### Using TopoJSON -For example, you can create a simple topoJSON map: +For example, you can create a simple TopoJSON map: 
 ```topojson
diff --git a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
index e21bc40ca8..8ee52758f5 100644
--- a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
+++ b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -2,8 +2,7 @@
 title: ディスカッションでのGraphQL APIの利用
 intro: '{% data variables.product.prodname_discussions %} GraphQL APIの使い方を学んでください。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 shortTitle: ディスカッションでのGraphQLの利用
 ---
 
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
index f557123324..b3cfff4f1d 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -48,7 +48,8 @@ Issueの最新のコメントの情報を得ておきたい場合には、Issue
 
 コメントに注意してもらうために、Issue内でリポジトリにアクセスできるコラボレータを@メンションできます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 責任を伝えるために、Issueを割り当てることができます。 同じコメントを頻繁に入力しているなら、返信テンプレートを利用できます。
 {% ifversion fpt or ghec %}詳しい情報については「[基本的な記述とフォーマットの構文](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)」及び「[他のGitHubユーザへのIssueやPull Requestの割り当て](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)」を参照してください。
-
+{% endif %}
+{% ifversion discussions %}
 ## Issueとディスカッションの比較
 
 会話の中には、{% data variables.product.prodname_discussions %}に適しているものもあります。 {% data reusables.discussions.you-can-use-discussions %} Issueあるいはディスカッションを使う場合のガイダンスについては「[GitHubでのコミュニケーション](/github/getting-started-with-github/quickstart/communicating-on-github)」を参照してください。
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index 3f53ee62f6..82eb0413cf 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -90,7 +90,7 @@ IssueもしくはPull Requestのコメントから、新しいIssueをオープ
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-{% ifversion fpt or ghec %}
+{% ifversion discussions %}
 
 ## ディスカッションからのIssueの作成
 
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index 0ec5668834..549f88e937 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
 title: Organizationについて
-intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
+intro: Organizationは、洗練されたセキュリティと管理機能を備えた、企業とオープンソースプロジェクトが多くのプロジェクトに渡って協力しあえる共有アカウントです。
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -18,20 +18,20 @@ topics:
 
 {% data reusables.organizations.about-organizations %} アカウントの種類に関する詳しい情報については「[{% data variables.product.prodname_dotcom %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。
 
-You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. 詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」を参照してください。
+組織に参加してもらうよう、人数に制限無く招待をして、それらのOrganizationメンバーに、Organizationとそのデータに対して様々なレベルのアクセスを付与する様々なロールを与えることができます。 詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」を参照してください。
 
-In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
+Organizationそのものへのアクセスの管理に加え、別個にOrganizationのリポジトリ、プロジェクトボード、アプリケーションへのアクセスも管理できます。 詳しい情報については「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」、「[Organizationのプロジェクトボードの権限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)」、「[Organizationのアプリケーションへのアクセス管理](/organizations/managing-access-to-your-organizations-apps)」を参照してください。
 
-To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
+アクセス管理をシンプルにし、コラボレーションを拡大するために、カスケードされた権限とメンションを持つ、グループの構造を反映した入れ子チームを作成できます。 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
-You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
+メンバーが作成できるリポジトリの種類の制限などの設定を管理することによって、自分のグループ特有の要求を満たすようにOrganizationを設定できます。 詳しい情報については「[Organizationの設定の管理](/organizations/managing-organization-settings)」を参照してください。
 
-To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+Organizationのセキュリティを強化するために、セキュリティの要件を適用し、OrganizationのAudit logをレビューできます。 詳しい情報については「[Organizationをセキュアに保つ](/organizations/keeping-your-organization-secure)」を参照してください。
 
 {% data reusables.organizations.org-ownership-recommendation %}詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。
 
 {% ifversion fpt or ghec %}
-## About feature availability
+## 利用できる機能について
 
 {% data reusables.organizations.organization-plans %}
 {% endif %}
@@ -44,7 +44,7 @@ Enterpriseアカウントは、オーナーが複数のOrganizationのポリシ
 {% ifversion ghec %}Enterpriseアカウントに属するOrganizationでは、支払いはEnterpriseアカウントのレベルで管理され、支払い設定はOrganizationレベルでは利用できません。{% endif %}EnterpriseオーナーはEnterpriseアカウント内のすべてのOrganizationに対するポリシーを設定するか、OrganizationのオーナーにOrganizationレベルでポリシーを設定できるよう許可することができます。 Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。
 
 {% ifversion ghec %}
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+{% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。
 
 {% data reusables.enterprise-accounts.invite-organization %}
 {% endif %}
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 4aa44e907a..219fb4280e 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -816,4 +816,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 ## Further reading
 
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %}
+{%- ifversion fpt or ghec %}
 - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
+{%- endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 0d9d079b7d..ba946be185 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -140,7 +140,7 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ
 | [リポジトリのアーカイブ](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                            |       |        |       |          |                 **X** |{% ifversion fpt or ghec %}
 | スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                                                                                                                                                               |       |        |       |          |                         **X** 
 {% endif %}
-| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。                                                                                                                                                                                                                                                                                               |       |        |       |          |                 **X** |{% ifversion fpt or ghec %}
+| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。                                                                                                                                                                                                                                                                                               |       |        |       |          |                 **X** |{% ifversion discussions %}
 | リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                                    |       |        |       |  **X**   |                                **X**                                |
 | {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)                                                                                                                                                                                                                                                                      |       |        |       |  **X**   |                                **X**                                |
 | [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                |       |        | **X** |  **X**   |                                **X**                                |
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
index 1f35a4a9fb..70895a13ef 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -3,8 +3,7 @@ title: OrganizationでのGitHub Discussionsの有効化もしくは無効化
 intro: 'Organization内の1つのリポジトリに限定されない会話をするための場所として、{% data variables.product.prodname_discussions %}をOrganizationで利用できます。'
 permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
 shortTitle: Organizationのディスカッション
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
index 2f977fef8e..3981302429 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/index.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
@@ -27,6 +27,7 @@ children:
   - /allowing-people-to-delete-issues-in-your-organization
   - /enabling-or-disabling-github-discussions-for-an-organization
   - /managing-discussion-creation-for-repositories-in-your-organization
+  - /managing-the-commit-signoff-policy-for-your-organization
   - /setting-team-creation-permissions-in-your-organization
   - /managing-scheduled-reminders-for-your-organization
   - /managing-the-default-branch-name-for-repositories-in-your-organization
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 5d7d1bcafb..dc3e754f07 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -5,8 +5,7 @@ redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
 permissions: Organization owners can manage discussion creation for repositories owned by the organization.
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Organizations
   - Teams
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
new file mode 100644
index 0000000000..66928608d1
--- /dev/null
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
+topics:
+  - Organizations
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Managing compulsory commit signoffs for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
index 27fb80e687..64d36defce 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -22,6 +22,9 @@ Organization のオーナーは、Organization 内のメンバー名表示を管
 
 Organization の各メンバーは、自分のプロフィール名を設定で選択します。 詳細は「[プロフィールをパーソナライズする](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)」を参照してください。
 
+{% ifversion profile-name-enterprise-setting %}
+You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)」を参照してください。{% endif %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index c0947122b6..8e453b64f0 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -49,7 +49,7 @@ Organization内では、ロールをOrganization、Team、リポジトリのレ
 
 継承されたロールにまだ含まれていない場合にのみ、追加の権限を選択できます。 たとえば、継承されたロールがリポジトリへの**Write**アクセスを提供しているなら、"Close a pull request"権限は継承されたロールに既に含まれています。
 
-{% ifversion ghec %}
+{% ifversion discussions %}
 ### Discussions
 
 - **Create a discussion category（ディスカッションカテゴリの作成）**: 新しいディスカッションカテゴリを作成できる。 詳しい情報については「[新しいディスカッションカテゴリの作成](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)」を参照してください。
diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md
index a03b3d8bbe..df29da2cf1 100644
--- a/translations/ja-JP/content/packages/index.md
+++ b/translations/ja-JP/content/packages/index.md
@@ -12,10 +12,11 @@ featuredLinks:
     - /packages/learn-github-packages/installing-a-package
   popular:
     - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
-    - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - /packages/learn-github-packages
     - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
   guideCards:
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
     - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
     - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry
 changelog:
diff --git a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
index 360f84b646..91da35239e 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -16,7 +16,7 @@ shortTitle: アクセスコントロールと可視性
 
 詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
 
-現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 詳細な権限は、npmレジストリなど他のパッケージレジストリではサポートされていません。
+現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 Granular permissions are not supported in our other package registries, such as the npm registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
 
 リポジトリをスコープとするパッケージの権限や、PATに関するパッケージ関連のスコープ、Actionsのワークフローの権限の管理についての詳しい情報は、「[GitHub Packagesの権限について](/packages/learn-github-packages/about-permissions-for-github-packages)」を参照してください。
 
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index eca15605e1..c8b05d49f1 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -1,6 +1,6 @@
 ---
 title: Dockeerレジストリからコンテナレジストリへの移行
-intro: '以前はDockerレジストリに保存されていたDockerイメージは、自動的に{% data variables.product.prodname_container_registry %}に移行されます。'
+intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.product.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
@@ -9,35 +9,61 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: コンテナレジストリへの移行
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migration to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
 ---
 
-{% data variables.product.prodname_dotcom %}のDockerレジストリは、{% data variables.product.prodname_container_registry %}で置き換えられました。 DockerイメージをDockerレジストリに保存していたなら、それらは自動的に{% data variables.product.prodname_container_registry %}に移されます。 あなたは何もする必要がありません。 Dockerレジストリ(`docker.pkg.github.com`) に名前空間を使っていたスクリプトや{% data variables.product.prodname_actions %}のワークフローは、{% data variables.product.prodname_container_registry %}(`ghcr.io`)への移行後も動作し続けます。
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-移行は一度にではなく、徐々に行われます。 まだイメージが移動されていなければ、待ち続けてください。遠からずそれらは移行されます。
+## {% data variables.product.prodname_container_registry %} について
 
-## イメージが移行されたかはどうすれば分かりますか？
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
 
-Dockerイメージが{% data variables.product.prodname_container_registry %}に移行されると、そのパッケージの詳細ページに以下の変更が示されます。
+## About migration from the Docker registry
 
-* 以前はDockerロゴだったアイコンは{% data variables.product.prodname_container_registry %}ロゴになります。
-* 以前は`docker.pkg.github.com`だったプルURL内のドメインは、`ghcr.io`になります。
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
 
-![{% data variables.product.prodname_container_registry %}詳細ページ](/assets/images/help/package-registry/container-registry-details-page.png)
+{% ifversion docker-ghcr-enterprise-migration %}
 
-## {% data variables.product.prodname_container_registry %}とDockerレジストリの主な違い
+{% note %}
 
-{% data variables.product.prodname_container_registry %}は、コンテナに固有の要求をサポートするために最適化されています。
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
 
-{% data variables.product.prodname_container_registry %}を使うと、以下のことができます。
-- コンテナイメージをOrganizationや個人アカウント内に保存するか、リポジトリに接続する。
-- 権限をリポジトリから継承するか、リポジトリとは独立に詳細な権限を設定するかを選択する。
-- 匿名でパブリックなコンテナイメージにアクセスする。
+{% endnote %}
 
-### Dockerイメージの詳細に関するAPIクエリ
+{% endif %}
 
-移行後は、GraphQL APIを使って`PackageType` "DOCKER"のパッケージに対するクエリを実行することはできなくなります。 その代わりに、REST APIを使って`package_type` "container"のパッケージに対するクエリを実行できるようになります。 詳しい情報については、REST APIの記事「[パッケージ](/rest/reference/packages)」を参照してください。
+After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
 
-## 支払い
+- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
 
-{% data variables.product.prodname_container_registry %}に対する支払に関する詳しい情報については「[{% data variables.product.prodname_registry %}の支払について](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。
+{% ifversion fpt or ghec %}
+
+![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %}
+
+{% ifversion fpt or ghec %}
+
+After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation.
+
+## {% data variables.product.prodname_container_registry %}の支払いについて
+
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+## 参考リンク
+
+- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)"
+
+{% endif %}
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
index 72fcea30ab..02708a404d 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -18,19 +18,19 @@ versions:
   ghes: '>= 3.5'
 shortTitle: Container registry
 ---
-{% ifversion ghes > 3.4 %}
-{% note %}
 
-**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change.
+{% data reusables.package_registry.container-registry-ghes-beta %}
 
-{% endnote %}
-{% endif %}
+## About the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %}
 
 {% ifversion ghes > 3.4 %}
-## Prerequisites
 
-To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+
 {% endif %}
+
 ## About {% data variables.product.prodname_container_registry %} support
 
 The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
index 83cca63e32..cd875e1de0 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -18,6 +18,9 @@ versions:
 
 {% data reusables.commits.about-commits %}
 
+{% ifversion commit-signoffs %}
+If the repository you are committing to has compulsory commit signoffs enabled, and you are committing via the web interface, you will automatically sign off on the commit as part of the commit process. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." {% endif %}
+
 共同作業しているコミットに共作者を追加できます。 詳しい情報については、「[複数の作者を持つコミットを作成する](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)」を参照してください。
 
 {% ifversion fpt or ghec %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 0b958cd325..09a01f0cad 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -1,11 +1,9 @@
 ---
 title: リポジトリの GitHub Discussions を有効化または無効化する
 intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.'
-product: '{% data reusables.gated-features.discussions %}'
 permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - Repositories
 redirect_from:
@@ -19,7 +17,7 @@ shortTitle: Discussions
 {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
 1. Discussions を無効化するには、[Features] で [**Discussions**] の選択を解除します。
 
-You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. 詳しい情報については「[OrganizationでのGitHub Discussionsの有効化もしくは無効化](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)」を参照してください。
 
 ## 参考リンク
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
index b22a9ce9ea..a85fb3b0fc 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
@@ -13,6 +13,7 @@ children:
   - /managing-teams-and-people-with-access-to-your-repository
   - /managing-the-forking-policy-for-your-repository
   - /managing-pull-request-reviews-in-your-repository
+  - /managing-the-commit-signoff-policy-for-your-repository
   - /managing-git-lfs-objects-in-archives-of-your-repository
   - /enabling-anonymous-git-read-access-for-a-repository
   - /about-email-notifications-for-pushes-to-your-repository
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
new file mode 100644
index 0000000000..0e76db15bc
--- /dev/null
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -0,0 +1,24 @@
+---
+title: Managing the commit signoff policy for your repository
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
+topics:
+  - Repositories
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.product.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.product.product_location %}'s web interface will automatically be signed off on by the commit author.
+
+Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Enabling or disabling compulsory commit signoffs for your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Select **Require contributors to sign off on web-based commits**. ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index e18e4e9f73..709ad63c9b 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -63,7 +63,7 @@ You can create new releases with release notes, @mentions of contributors, and l
 ![Releases description](/assets/images/enterprise/3.5/releases/releases_description_auto.png){% endif %}
 1. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif)
 2. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt or ghec %}
+{%- ifversion discussions %}
 1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 9. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png)
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 61d4e1203f..6ec81c8e7f 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -233,9 +233,9 @@ HTML ドキュメントへのコミットのレンダリング済みビューは
 
 通常、埋め込み HTML を含むドキュメントへの変更のレンダリング済みビューでは、{% data variables.product.product_name %} のドキュメントのビューでサポートされている要素への変更を表示します。 埋め込み HTML を含むドキュメントへの変更のレビューは、完全を期して、常にレンダリング済みとソースの両方のビューで行う必要があります。
 
-## Mapping geoJSON files on {% data variables.product.prodname_dotcom %}
+## Mapping GeoJSON/TopoJSON files on {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.product_name %} は、{% data variables.product.product_name %} リポジトリでの geoJSON および topoJSON マップ ファイルのレンダリングをサポートしています。 `.geojson` または `.topojson` 拡張子を使って、通常と同じようにファイルをコミットするだけです。 `.json` 拡張子の付いたファイルもサポートされますが、`type` が `FeatureCollection`、`GeometryCollection`、または `topology` に設定されている場合に限られます。 コミット後、GitHub.com で geoJSON ファイルのパスに移動してください。
+{% data variables.product.product_name %} supports rendering GeoJSON and TopoJSON map files within {% data variables.product.product_name %} repositories. `.geojson` または `.topojson` 拡張子を使って、通常と同じようにファイルをコミットするだけです。 `.json` 拡張子の付いたファイルもサポートされますが、`type` が `FeatureCollection`、`GeometryCollection`、または `topology` に設定されている場合に限られます。 Then, navigate to the path of the GeoJSON/TopoJSON file on GitHub.com.
 
 右側にある紙アイコンをクリックすると、そのファイル ドキュメントに加えられた変更も、コミットの一部として表示されます。
 
@@ -243,12 +243,12 @@ HTML ドキュメントへのコミットのレンダリング済みビューは
 
 ### Geometry types
 
-{% data variables.product.product_name %} のマップは [Leaflet.js](http://leafletjs.com) を使用し、[geoJSON の仕様](http://www.geojson.org/geojson-spec.html) (Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon、GeometryCollection) に概要が示されているジオメトリのタイプをすべてサポートしています。 TopoJSON ファイルは "Topology" タイプで、[topoJSON の仕様](https://github.com/mbostock/topojson/wiki/Specification)に従っている必要があります。
+{% data variables.product.product_name %} のマップは [Leaflet.js](http://leafletjs.com) を使用し、[geoJSON の仕様](http://www.geojson.org/geojson-spec.html) (Point、LineString、Polygon、MultiPoint、MultiLineString、MultiPolygon、GeometryCollection) に概要が示されているジオメトリのタイプをすべてサポートしています。 TopoJSON files should be type "Topology" and adhere to the [TopoJSON spec](https://github.com/mbostock/topojson/wiki/Specification).
 
 {% ifversion geoJSON-with-MapBox %}
 ### フィーチャーのスタイリング
 
-GeoJSON オブジェクトのプロパティで追加のメタデータを渡すと、特定の色を指定する、説明アイコンを追加するなど、フィーチャーの表示方法をカスタマイズすることができます。 オプションは次のとおりです:
+You can customize the way features are displayed, such as specifying a particular color or adding a descriptive icon, by passing additional metadata within the GeoJSON object's properties. オプションは次のとおりです:
 
 * `marker-size` - `small`、`medium`、または `large`
 * `marker-color` - 有効な RGB 16 進カラー
@@ -264,7 +264,7 @@ GeoJSON オブジェクトのプロパティで追加のメタデータを渡す
 
 ### マップを他の場所に埋め込む
 
-GeoJSON マップを {% data variables.product.product_name %} 以外の場所で使用するには、 次のテンプレートを修正し、JavaScript をサポートしている任意の HTML ページに貼り付けてください (例: [{% data variables.product.prodname_pages %}](http://pages.github.com))。
+Want to make your GeoJSON map available someplace other than {% data variables.product.product_name %}? Simply modify this template, and place it in any HTML page that supports JavaScript (e.g., [{% data variables.product.prodname_pages %}](http://pages.github.com)):
 
 ```html
 
@@ -287,7 +287,7 @@ GeoJSON マップを {% data variables.product.product_name %} 以外の場所
 {% ifversion mermaid %}
 ### Mapping in Markdown
 
-You can embed geoJSON and topoJSON directly in Markdown. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)."
+You can embed GeoJSON and TopoJSON directly in Markdown. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)."
 {% endif %}
 
 ### クラスタリング
@@ -300,7 +300,7 @@ You can embed geoJSON and topoJSON directly in Markdown. For more information, s
 
 ### トラブルシューティング
 
-geoJSON ファイルのレンダリングに問題がある場合は、[geoJSON 文法チェッカー](http://geojsonlint.com/)でそのファイルを実行し、有効な geoJSON ファイルであることを確認してください。 ポイントが、意図しない場所 (海の中など) にある場合、そのデータには、現在サポートされていない投影法が使われている可能性があります。 現在、{% data variables.product.product_name %}でサポートされているのは `urn:ogc:def:crs:OGC:1.3:CRS84` 投影だけです。
+If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). ポイントが、意図しない場所 (海の中など) にある場合、そのデータには、現在サポートされていない投影法が使われている可能性があります。 現在、{% data variables.product.product_name %}でサポートされているのは `urn:ogc:def:crs:OGC:1.3:CRS84` 投影だけです。
 
 また、10 MB を超えるような大きな `.geojson` ファイルは、ブラウザではレンダリングできません。 その場合は通常、次のようなメッセージが表示されます:
 
diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
index 5f05d74dbb..a0fd80932c 100644
--- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
@@ -355,6 +355,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 56
+> x-ratelimit-used: 4
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -362,6 +363,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 | ----------------------- | ----------------------------------------------------------------------------- |
 | `x-ratelimit-limit`     | 1 時間あたりのリクエスト数の上限。                                                            |
 | `x-ratelimit-remaining` | 現在のレート制限ウィンドウに残っているリクエストの数。                                                   |
+| `x-ratelimit-used`      | 現在のレート制限ウィンドウ内で発行したリクエスト数。                                                    |
 | `x-ratelimit-reset`     | 現在のレート制限ウィンドウが [UTC エポック秒](http://en.wikipedia.org/wiki/Unix_time)でリセットされる時刻。 |
 
 時刻に別の形式を使用する必要がある場合は、最新のプログラミング言語で作業を完了できます。 たとえば、Web ブラウザでコンソールを開くと、リセット時刻を JavaScript の Date オブジェクトとして簡単に取得できます。
@@ -378,6 +380,7 @@ new Date(1372700873 * 1000)
 > Date: Tue, 20 Aug 2013 14:50:41 GMT
 > x-ratelimit-limit: 60
 > x-ratelimit-remaining: 0
+> x-ratelimit-used: 60
 > x-ratelimit-reset: 1377013266
 
 > {
@@ -396,6 +399,7 @@ $ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre
 > Date: Mon, 01 Jul 2013 17:27:06 GMT
 > x-ratelimit-limit: 5000
 > x-ratelimit-remaining: 4966
+> x-ratelimit-used: 34
 > x-ratelimit-reset: 1372700873
 ```
 
@@ -639,4 +643,3 @@ $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_ur
 [uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
-
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
index 1ea1c006ba..17f02430d0 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
@@ -2,8 +2,7 @@
 title: ディスカッションを検索する
 intro: '{% data variables.product.product_name %} 上のディスカッションを検索し、検索修飾子を使用して検索結果を絞り込むことができます。'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: discussions
 topics:
   - GitHub search
 redirect_from:
diff --git a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
index 7e32fc51c4..0beba8ec7a 100644
--- a/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
+++ b/translations/ja-JP/content/support/learning-about-github-support/about-github-support.md
@@ -17,6 +17,8 @@ redirect_from:
   - /github/working-with-github-support/github-enterprise-cloud-support
   - /articles/business-plan-support
   - /articles/github-business-cloud-support
+  - /admin/enterprise-support/about-support-for-advanced-security
+  - /enterprise-server/admin/enterprise-support/about-support-for-advanced-security
 topics:
   - Support
 ---
diff --git a/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml b/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..bfb6aa0a58
--- /dev/null
+++ b/translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+#Reference: Issue #6207.
+#We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6207'
diff --git a/translations/ja-JP/data/features/audit-log-streaming.yml b/translations/ja-JP/data/features/audit-log-streaming.yml
new file mode 100644
index 0000000000..1ff0517353
--- /dev/null
+++ b/translations/ja-JP/data/features/audit-log-streaming.yml
@@ -0,0 +1,5 @@
+#Reference: #7055
+#Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
diff --git a/translations/ja-JP/data/features/commit-signoffs.yml b/translations/ja-JP/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..26fe611963
--- /dev/null
+++ b/translations/ja-JP/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6049'
diff --git a/translations/ja-JP/data/features/discussions.yml b/translations/ja-JP/data/features/discussions.yml
new file mode 100644
index 0000000000..66a3bb8592
--- /dev/null
+++ b/translations/ja-JP/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
diff --git a/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml b/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..48c1b97cc9
--- /dev/null
+++ b/translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+#Reference: #7360
+#Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3.6'
diff --git a/translations/ja-JP/data/features/ghas-enablement-webhook.yml b/translations/ja-JP/data/features/ghas-enablement-webhook.yml
index cbb4509714..83f8a995bc 100644
--- a/translations/ja-JP/data/features/ghas-enablement-webhook.yml
+++ b/translations/ja-JP/data/features/ghas-enablement-webhook.yml
@@ -2,5 +2,5 @@
 #docs-content 7314. GHAS enablement webhook
 versions:
   ghec: '*'
-  ghes: '>3.6'
+  ghes: '>= 3.6'
   ghae: 'issue-7314'
diff --git a/translations/ja-JP/data/features/motion-management.yml b/translations/ja-JP/data/features/motion-management.yml
new file mode 100644
index 0000000000..573307aac2
--- /dev/null
+++ b/translations/ja-JP/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+#Issue 6523
+#Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'
diff --git a/translations/ja-JP/data/features/pause-audit-log-stream.yml b/translations/ja-JP/data/features/pause-audit-log-stream.yml
new file mode 100644
index 0000000000..59bcda81d5
--- /dev/null
+++ b/translations/ja-JP/data/features/pause-audit-log-stream.yml
@@ -0,0 +1,4 @@
+#Reference #4640
+#Documentation for pausing an audit log stream
+versions:
+  ghec: '*'
diff --git a/translations/ja-JP/data/features/require-tls-for-smtp.yml b/translations/ja-JP/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..dd1f0d2c78
--- /dev/null
+++ b/translations/ja-JP/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+#Reference 7394
+#Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+  ghes: '>=3.6'
diff --git a/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml b/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..c4d8f488a5
--- /dev/null
+++ b/translations/ja-JP/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+#Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6982'
diff --git a/translations/ja-JP/data/glossaries/internal.yml b/translations/ja-JP/data/glossaries/internal.yml
index f3d1b6cc70..9ea579ed43 100644
--- a/translations/ja-JP/data/glossaries/internal.yml
+++ b/translations/ja-JP/data/glossaries/internal.yml
@@ -665,7 +665,7 @@
   description: >-
     パスワードの代わりに使用できます。トークンには、個人アクセストークン、OAuth トークン、API トークンがあります。
 - 
-  term: topoJSON
+  term: TopoJSON
   description: GeoJSON の機能拡張版。トポロジをエンコードします。
 - 
   term: TOTPアプリケーション
diff --git a/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
new file mode 100644
index 0000000000..a9f2bdc09d
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.6/graphql_previews.enterprise.yml
@@ -0,0 +1,123 @@
+- 
+  title: パッケージのバージョン削除へのアクセス
+  description: >-
+    このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。
+  toggled_by: ':package-deletes-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.deletePackageVersion
+  owning_teams:
+    - '@github/pe-package-registry'
+- 
+  title: デプロイメント
+  description: >-
+    このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。
+  toggled_by: ':flash-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - DeploymentStatus.environment
+    - Mutation.createDeploymentStatus
+    - CreateDeploymentStatusInput
+    - CreateDeploymentStatusPayload
+    - Mutation.createDeployment
+    - CreateDeploymentInput
+    - CreateDeploymentPayload
+  owning_teams:
+    - '@github/c2c-actions-service'
+- 
+  title: >-
+    >- MergeInfoPreview - Pull Requestのマージ状態に関する詳細な情報。
+  description: >-
+    このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。
+  toggled_by: ':merge-info-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - PullRequest.canBeRebased
+    - PullRequest.mergeStateStatus
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。
+  description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。
+  toggled_by: ':update-refs-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateRefs
+    - GitRefname
+    - RefUpdate
+    - UpdateRefsInput
+    - UpdateRefsPayload
+  owning_teams:
+    - '@github/reponauts'
+- 
+  title: プロジェクトイベントの詳細
+  description: >-
+    このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。
+  toggled_by: ':starfox-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - AddedToProjectEvent.project
+    - AddedToProjectEvent.projectCard
+    - AddedToProjectEvent.projectColumnName
+    - ConvertedNoteToIssueEvent.project
+    - ConvertedNoteToIssueEvent.projectCard
+    - ConvertedNoteToIssueEvent.projectColumnName
+    - MovedColumnsInProjectEvent.project
+    - MovedColumnsInProjectEvent.projectCard
+    - MovedColumnsInProjectEvent.projectColumnName
+    - MovedColumnsInProjectEvent.previousProjectColumnName
+    - RemovedFromProjectEvent.project
+    - RemovedFromProjectEvent.projectColumnName
+  owning_teams:
+    - '@github/github-projects'
+- 
+  title: ラベルのプレビュー
+  description: >-
+    このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。
+  toggled_by: ':bane-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.createLabel
+    - CreateLabelPayload
+    - CreateLabelInput
+    - Mutation.deleteLabel
+    - DeleteLabelPayload
+    - DeleteLabelInput
+    - Mutation.updateLabel
+    - UpdateLabelPayload
+    - UpdateLabelInput
+  owning_teams:
+    - '@github/pe-pull-requests'
+- 
+  title: プロジェクトのインポート
+  description: このプレビューは、プロジェクトのインポートのサポートを追加します。
+  toggled_by: ':slothette-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.importProject
+  owning_teams:
+    - '@github/pe-issues-projects'
+- 
+  title: Teamレビューの割り当てプレビュー
+  description: >-
+    このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します
+  toggled_by: ':stone-crop-preview'
+  announcement: null
+  updates: null
+  toggled_on:
+    - Mutation.updateTeamReviewAssignment
+    - UpdateTeamReviewAssignmentInput
+    - TeamReviewAssignmentAlgorithm
+    - Team.reviewRequestDelegationEnabled
+    - Team.reviewRequestDelegationAlgorithm
+    - Team.reviewRequestDelegationMemberCount
+    - Team.reviewRequestDelegationNotifyTeam
+  owning_teams:
+    - '@github/pe-pull-requests'
diff --git a/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
new file mode 100644
index 0000000000..5485c04839
--- /dev/null
+++ b/translations/ja-JP/data/graphql/ghes-3.6/graphql_upcoming_changes.public-enterprise.yml
@@ -0,0 +1,86 @@
+---
+upcoming_changes:
+  - 
+    location: LegacyMigration.uploadUrlTemplate
+    description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。'
+    reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。'
+    date: '2019-04-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: AssignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: UnassignedEvent.user
+    description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。'
+    reason: アサインされた人を、マネキンにできるようになりました。
+    date: '2020-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: tambling
+  - 
+    location: Issue.timeline
+    description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: PullRequest.timeline
+    description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。'
+    reason: '`timeline`は削除されます。'
+    date: '2020-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: mikesea
+  - 
+    location: MergeStateStatus.DRAFT
+    description: '`DRAFT`は削除されます。代わりにPullRequest.isDraftを使ってください。'
+    reason: DRAFTの状態はこのenumから削除されるので、代わりに`isDraft`を使わなければなりません。
+    date: '2021-01-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: nplasterer
+  - 
+    location: PackageType.DOCKER
+    description: '`DOCKER`は削除されます。'
+    reason: DOCKERは、Packages REST APIでのみ使われるように移行されるので、このenumから削除されます。
+    date: '2021-06-21'
+    criticality: 破壊的
+    owner: reybard
+  - 
+    location: ReactionGroup.users
+    description: '`users`は削除されます。代わりに`reactors`フィールドを使ってください。'
+    reason: リアクターは、マネキン、ボット、Organizationになることができます。
+    date: '2021-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: synthead
+  - 
+    location: Repository.defaultMergeQueue
+    description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。'
+    reason: '`defaultMergeQueue`は削除されます。'
+    date: '2022-04-01'
+    criticality: 破壊的
+    owner: colinshum
+  - 
+    location: AddPullRequestToMergeQueueInput.branch
+    description: '`branch`は削除されます。'
+    reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jhunschejones
+  - 
+    location: Enterprise.userAccounts
+    description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。'
+    reason: '`Enterprise.userAccounts`フィールドは削除されています。'
+    date: '2022-07-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jdennes
+  - 
+    location: RemovePullRequestFromMergeQueueInput.branch
+    description: '`branch`は削除されます。'
+    reason: PRはベースブランチのマージキューから削除され、引数`branch`はno-opになりました。
+    date: '2022-10-01T00:00:00+00:00'
+    criticality: 破壊的
+    owner: jhunschejones
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml
new file mode 100644
index 0000000000..fac1c2578d
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/16.yml
@@ -0,0 +1,17 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 成果物のzipアーカイブ中のファイルが、unzipツールを使って展開されたときに000の権限を持つ問題を修正しました。GitHub.comでの動作と同じように、それらのファイルの権限には644が設定されるようになりました。
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml
new file mode 100644
index 0000000000..0b34fa85fa
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/11.yml
@@ -0,0 +1,18 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - 成果物のzipアーカイブ中のファイルが、unzipツールを使って展開されたときに000の権限を持つ問題を修正しました。GitHub.comでの動作と同じように、それらのファイルの権限には644が設定されるようになりました。
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
index 69416e0428..dece67887a 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml
@@ -28,7 +28,7 @@ sections:
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
     - |
       セルフホストランナーを--ephemeral`パラメータ付きで複数レベル（たとえばEnterpriseとOrganizationというように）に登録したあと、ランナーがアイドル状態で停止し、再登録が必要になることがあります。[更新: 2022年6月17日]
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
   deprecations:
     - 
       heading: GitHub Enterprise Server 3.0の非推奨化
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
index 3ea8c95caa..eec8741756 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml
@@ -37,4 +37,4 @@ sections:
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
     - |
       セルフホストランナーを--ephemeral`パラメータ付きで複数レベル（たとえばEnterpriseとOrganizationというように）に登録したあと、ランナーがアイドル状態で停止し、再登録が必要になることがあります。[更新: 2022年6月17日]
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
index f30e685273..a8ceb142f4 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/5.yml
@@ -32,4 +32,4 @@ sections:
       この問題を回避するためには、以下の2つの方法のいずれかを取ることができます。
       - `WantAssertionsEncrypted`属性なしのSAMLメタデータの静的なコピーをアップロードして、IdPを再設定する。
       - SAMLメタデータをコピーし、`WantAssertionsEncrypted`を削除し、それをWebサーバーでホストして、そのURLを指してIdPを再設定する。
-    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
+    - '{% data variables.product.prodname_ghe_server %} 3.4にアップグレードしたあと、リリースがリポジトリから失われたように見えることがあります。これは、必要なElasticsearchのインデックスの移行が成功終了していない場合に起こります。'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml
new file mode 100644
index 0000000000..7f7a43d706
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/6.yml
@@ -0,0 +1,20 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+    - スケジュールされたGitHub Actionsワークフローが無効化されることがありました。
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、ページネーションに関する情報を提供するために`Link`ヘッダを返すようになりました。'
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、正しいコミッターの総数を返すようになりました。'
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml
new file mode 100644
index 0000000000..325d553e3c
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/3.yml
@@ -0,0 +1,22 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**中**: サーバーサイドリクエストフォージェリ（SSRF）が、任意のデータをMemcachedをインジェクションすることによってSubversion（SVN）ブリッジにリモートコードを実行させうる攻撃を防ぎます。"
+    - "**中**: 攻撃者が、GitHub Enterprise ServerのWebインターフェース内のドロップダウンUI要素のクロスサイトスクリプティング（XSS）脆弱性を悪用することによってJavascriptのコードを実行することを防ぎます。"
+    - Grafanaをバージョン7.5.17にアップデートします。このバージョンは [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9)及び[CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)を含む様々なセキュリティ脆弱性に対処しています。
+    - パッケージは最新のセキュリティバージョンにアップデートされました。
+  bugs:
+    - collectdデーモンが過剰にメモリを消費することがありました。
+    - ローテーとされたログファイルのバックアップが蓄積され、過剰にストレージを消費することがありました。
+    - 新しい機能リリースへのアップグレードとそれに続く設定の実行後、Elasticsearchがインデックスの再構築の間に過剰な例外を記録することがありました。
+    - 保護されたブランチが1つ以上の承認レビューを要求する場合に、Pull Requestが必要な承認レビュー数よりも少ないレビュー数でマージできてしまうことがありました。
+    - GitHub Enterprise Importerは、リポジトリ内のプロジェクトの設定を正しく移行しませんでした。
+    - LDAP認証を使用しているインスタンスで、sudoモードに対する認証プロンプトにおいてユーザ名とパスワードに対するテキストフィールドがどちらも見えている場合に、誤ってカーソルがデフォルトでパスワードフィールドに置かれてしまいました。
+    - サイトアドミンのダッシュボードに、休眠ユーザをリストするレポートをエクスポートするオプションが誤って含まれていました。
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、ページネーションに関する情報を提供するために`Link`ヘッダを返すようになりました。'
+    - 'Billing APIの"[OrganizationのGitHub Advanced Securityのアクティブなコミッターの取得](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)"エンドポイントは、正しいコミッターの総数を返すようになりました。'
+    - Organizationの設定のサイドバーで、**Archive**ナビゲーションアイテムが子を含みませんでした。
+  changes:
+    - '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
+    - バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
+    - データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..7beaf78a0f
--- /dev/null
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,216 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: false
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - 
+      heading: Infrastructure
+      notes:
+        - |
+          Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+    - 
+      heading: Instance security
+      notes:
+        - |
+          GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+          - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+          - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+          - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+        - |
+          You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+    - 
+      heading: 監査ログ
+      notes:
+        - |
+          You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. 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)."
+    - 
+      heading: GitHub Connect
+      notes:
+        - |
+          Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+    - 
+      heading: Administrator experience
+      notes:
+        - |
+          Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+        - |
+          Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+    - 
+      heading: GitHub Advanced Security
+      notes:
+        - |
+          Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+
+          - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+          - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)"
+          - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+        - |
+          Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+        - |
+          On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+        - |
+          Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+
+          - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+          - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+          - "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#secret_scanning_push_protection-category-actions)"
+          - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+        - |
+          Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+        - |
+          Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+
+          - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+          - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+          - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+          - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+        - |
+          The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+    - 
+      heading: Dependabot
+      notes:
+        - |
+          Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+        - |
+          Dependabot alerts show users if repository code calls vulnerable functions. Individual alerts display a "vulnerable call" label and code snippet, and users can filter search by `has:vulnerable-calls`. Vulnerable functions are curated during publication to the [GitHub Advisory Database](https://github.com/advisories). New incoming Python advisories will be supported, and GitHub is backfilling known vulnerable functions for historical Python advisories. After beta testing with Python, GitHub will add support for other ecosystems. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
+        - |
+          Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+        - |
+          Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+    - 
+      heading: コードセキュリティ
+      notes:
+        - |
+          GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+        - |
+          The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+        - |
+          If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+
+          - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+          - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+          - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+          - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+    - 
+      heading: GitHub Actions
+      notes:
+        - |
+          Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+        - |
+          When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+          - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"
+        - |
+          Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility.  For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+        - |
+          To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+        - |
+          To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+        - |
+          If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+    - 
+      heading: GitHub Packages
+      notes:
+        - |
+          Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+
+          - Improves the sharing of containers within an organization
+          - Allows the application of granular access permissions
+          - Permits the anonymous sharing of public container images
+          - Implements OCI standards for hosting Docker images
+
+          The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+    - 
+      heading: Community experience
+      notes:
+        - |
+          GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+        - |
+          Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+    - 
+      heading: Organization
+      notes:
+        - |
+          Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+        - |
+          Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+    - 
+      heading: リポジトリ
+      notes:
+        - |
+          While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+        - |
+          Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see
+          "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+        - |
+          Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+        - |
+          Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+        - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+        - |
+          Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+        - |
+          Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+        - |
+          Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+    - 
+      heading: コミット
+      notes:
+        - |
+          For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+        - |
+          To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+    - 
+      heading: プルリクエスト
+      notes:
+        - |
+          Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+        - |
+          Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+    - 
+      heading: リリース
+      notes:
+        - |
+          When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+        - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+    - 
+      heading: Markdown
+      notes:
+        - |
+          Editing Markdown in the web interface has been improved.
+
+          - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+          - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+          - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+          For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+        - |
+          When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+  changes:
+    - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+    - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+  known_issues:
+    - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。
+    - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
+    - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
+    - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
+    - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
+    - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
+    - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
+    - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
index fd3c94594d..68b601bbc8 100644
--- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md
+++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md
@@ -84,7 +84,7 @@ macOS Catalina 10.15 [deprecated]
 macos-10.15
 
 
-Migrate to macOS-11 or macOS-12. For more information, see this GitHub blog post.
+macOS-11もしくはmacOS-12に移行してください。 詳しい情報についてはGitHubブログのポストを参照してください。
 
 
 
diff --git a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
index 37446f2df5..acfc210be9 100644
--- a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
+++ b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md
@@ -1,5 +1,5 @@
-{% note %}
+{% ifversion GH-advisory-db-supports-malware %}{% note %}
 
 **ノート:** マルウェアのアドバイザリは現在ベータであり、変更されることがあります。
 
-{% endnote %}
+{% endnote %}{% endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
index 4b3cdb42c8..48be014db5 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
@@ -5,7 +5,7 @@
 | `advisory_credit`   | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 {%- endif %}
 | `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
-{%- ifversion ghec %}
+{%- ifversion audit-log-streaming %}
 | `audit_log_streaming`  | Contains activities related to streaming audit logs for organizations in an enterprise account.
 {%- endif %}
 {%- ifversion fpt or ghec %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md b/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
index 25b7b94f3b..0400806e7e 100644
--- a/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
+++ b/translations/ja-JP/data/reusables/code-scanning/alert-tracking-link.md
@@ -1,2 +1,2 @@
 
-For more information about creating issues to track {% data variables.product.prodname_code_scanning %} alerts, see "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)."
+{% data variables.product.prodname_code_scanning %}アラートを追跡するためのIssueの作成に関する詳しい情報については「[タスクリストを使用したIssue内の{% data variables.product.prodname_code_scanning %}アラートの追跡](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
index 57004ecc5c..00dc1d76b9 100644
--- a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Experimental alerts for {% data variables.product.prodname_code_scanning %} are created using experimental technology in the {% data variables.product.prodname_codeql %} action. This feature is currently available as a beta release for JavaScript code and is subject to change.
+**ノート:**{% data variables.product.prodname_code_scanning %}の実験的アラートは、{% data variables.product.prodname_codeql %}アクションの実験的な技術を使って作成されます。 この機能は現在JavaScriptのコードに対してベータとして利用可能であり、変更されることがあります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
index dff81e1499..d16f7fe5a5 100644
--- a/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
+++ b/translations/ja-JP/data/reusables/code-scanning/beta-codeql-packs-cli.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** The {% data variables.product.prodname_codeql %} package management functionality, including {% data variables.product.prodname_codeql %} packs, is currently in beta and subject to change.
+**ノート:** {% data variables.product.prodname_codeql %}を含む{% data variables.product.prodname_codeql %}パッケージ管理の機能は、現在ベータであり、変更されることがあります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md b/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
index 6ae84d6029..56af6cc51d 100644
--- a/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
+++ b/translations/ja-JP/data/reusables/code-scanning/choose-alert-dismissal-reason.md
@@ -1,3 +1,3 @@
 クエリが将来の分析に含まれ続けるかに影響することがあるので、ドロップダウンメニューから適切な理由を選択することは重要です。
-{% ifversion comment-dismissed-code-scanning-alert %}Optionally, you can comment on a dismissal to record the context of an alert dismissal. The dismissal comment is added to the alert timeline and can be used as justification during auditing and reporting. You can retrieve or set a comment by using the code scanning REST API. The comment is contained in `dismissed_comment` for the `alerts/{alert_number}` endpoint. For more information, see "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)."
+{% ifversion comment-dismissed-code-scanning-alert %}あるいは、アラートの却下に関するコンテキストを記録するために、却下の際にコメントすることができます。 却下のコメントはアラートのタイムラインに追加され、監査とレポートの際の正当性として利用できます。 コードスキャンニングのREST APIを使用して、コメントの取得や設定ができます。 コメントは、`alerts/{alert_number}`エンドポイントの`dismissed_comment`に含まれています。 詳しい情報については「[Code scanning](/rest/code-scanning#update-a-code-scanning-alert)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md b/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
index 33af00e09c..2bc7959ce5 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
@@ -1 +1 @@
-{% data variables.product.prodname_codeql_cli %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。 For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+{% data variables.product.prodname_codeql_cli %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。 詳しい情報については「[CIシステムでのCodeQLコードスキャンニングについて](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
index 5025b325d7..d2d013daa8 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -9,9 +9,9 @@
 
 {% note %}
 
-**Note**: {% data variables.product.prodname_codeql %} analysis for Ruby is currently in beta. During the beta, analysis of Ruby will be less comprehensive than {% data variables.product.prodname_codeql %} analysis of other languages.
+**ノート**: Rubyの{% data variables.product.prodname_codeql %}分析は現在ベータです。 このベータの間、Rubyの分析は他の言語の{% data variables.product.prodname_codeql %}分析よりも包括的ではありません。
 
 {% endnote %}
 
-For more information, see the documentation on the {% data variables.product.prodname_codeql %} website: "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)."
+詳しい情報については{% data variables.product.prodname_codeql %} Webサイトのドキュメンテーション「[サポートされている言語とフレームワーク](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
index 946b677788..fd7dd22c50 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -1 +1 @@
-`cpp`, `csharp`, `go`, `java`, `javascript`,{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %} `python`, and `ruby`{% else %} and `python`{% endif %}
+`cpp`、`csharp`、`go`、`java`、`javascript`、{% ifversion fpt or ghes > 3.3 or ghae-issue-5017 %} `python`、`ruby`{% else %}、`python`{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
index 60edba44d6..e1e345fff2 100644
--- a/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
+++ b/translations/ja-JP/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -2,4 +2,4 @@
 
 {% data reusables.code-scanning.codeql-query-suites %}
 
-When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the default set of queries and any extra queries defined in the additional query suite. {% ifversion codeql-ml-queries %}The `security-extended` and `security-and-quality` query suites for JavaScript contain experimental queries. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% endif %}
+クエリスイートを指定した場合、{% data variables.product.prodname_codeql %}分析エンジンはクエリのデフォルトセットと、追加のクエリスイートで定義された追加のクエリを実行します。 {% ifversion codeql-ml-queries %}JavaScriptの`security-extended`及び`security-and-quality`は実験的なクエリを含みます。 詳しい情報については「[{% data variables.product.prodname_code_scanning %}アラートについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
index 2ed52c32ff..84b1da296a 100644
--- a/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
+++ b/translations/ja-JP/data/reusables/code-scanning/deprecation-codeql-runner.md
@@ -2,22 +2,22 @@
 
 {% ifversion fpt or ghec %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} is deprecated. On {% data variables.product.product_name %}, the {% data variables.product.prodname_codeql_runner %} was supported until March 2022. You should upgrade to the latest version of [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 {% data variables.product.product_name %}では、{% data variables.product.prodname_codeql_runner %}は2022年3月までサポートされていました。 最新バージョンの[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)にアップグレードしてください。
 
 {% elsif ghes > 3.3 %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated and is not included in {% data variables.product.prodname_ghe_server %} 3.4. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.7.6.
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になっており、{% data variables.product.prodname_ghe_server %} 3.4には含まれていません。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) 2.7.6に移行してください。
 
 {% elsif ghes < 3.4 %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. On {% data variables.product.prodname_ghe_server %} 3.0 and greater, you can install [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.6.3 to replace {% data variables.product.prodname_codeql_runner %}.
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 {% data variables.product.prodname_ghe_server %} 3.0移行では、[{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)バージョン2.6.3をインストールして{% data variables.product.prodname_codeql_runner %}を置き換えることができます。
 
 {% elsif ghae %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} has been deprecated. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+**ノート:** {% data variables.product.prodname_codeql_runner %}は非推奨になりました。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases)に移行してください。
 
 {% endif %}
 
-For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). {% data variables.product.prodname_codeql_cli %}への移行に関する情報については「[CodeQLランナーからCodeQL CLIへの移行](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。
+詳しい情報については[CodeQLランナーの非推奨化](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/)を参照してください。 {% data variables.product.prodname_codeql_cli %}への移行に関する情報については「[CodeQLランナーからCodeQL CLIへの移行](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
index cddfdc8dc4..dec3cc7fa0 100644
--- a/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
+++ b/translations/ja-JP/data/reusables/code-scanning/enabling-options.md
@@ -15,7 +15,7 @@
     
     
     
-      Using {% data variables.product.prodname_actions %} (see "Setting up {% data variables.product.prodname_code_scanning %} using actions") or running {% data variables.product.prodname_codeql %} analysis in a third-party continuous integration (CI) system (see "About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system").
+      {% data variables.product.prodname_actions %}の利用（「アクションを使った{% data variables.product.prodname_code_scanning %}のセットアップ」参照）もしくはサードパーティの継続的インテグレーション（CI）システムでの{% data variables.product.prodname_codeql %}分析の実行（「CIシステムでの{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}について」参照）。
     
   
   
@@ -25,7 +25,7 @@
     
     
     
-      Using {% data variables.product.prodname_actions %} (see "Setting up {% data variables.product.prodname_code_scanning %} using actions") or generated externally and uploaded to {% data variables.product.product_name %} (see "Uploading a SARIF file to {% data variables.product.prodname_dotcom %}").
+      {% data variables.product.prodname_actions %}の利用（「アクションを使う{% data variables.product.prodname_code_scanning %}のセットアップ」）あるいは外部で生成して{% data variables.product.product_name %}へアップロード（「{% data variables.product.prodname_dotcom %}へのSARIFファイルのアップロード」）。
     
   
 
diff --git a/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md b/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
index 73aa156fef..ea34cc759d 100644
--- a/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
+++ b/translations/ja-JP/data/reusables/code-scanning/false-positive-fix-codeql.md
@@ -1 +1 @@
-If you dismiss a {% data variables.product.prodname_codeql %} alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the {% data variables.product.prodname_codeql %} repository and improving the analysis. {% data variables.product.prodname_codeql %}に関する詳しい情報については「[{% data variables.product.prodname_codeql %}に貢献する](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)」を参照してください。
+{% data variables.product.prodname_codeql %}のアラートを、たとえばコードがサポートされていないサニタイズのライブラリを使っているといった理由で偽陽性の結果として却下する場合、{% data variables.product.prodname_codeql %}リポジトリに貢献して分析を改善することを検討してください。 {% data variables.product.prodname_codeql %}に関する詳しい情報については「[{% data variables.product.prodname_codeql %}に貢献する](https://github.com/github/codeql/blob/main/CONTRIBUTING.md)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md b/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
index 6d8d85de0b..0abe36f5a2 100644
--- a/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
+++ b/translations/ja-JP/data/reusables/code-scanning/filter-non-default-branches.md
@@ -1 +1 @@
-Please note that if you have filtered for alerts on a non-default branch, but the same alerts exist on the default branch, the alert page for any given alert will still only reflect the alert's status on the default branch, even if that status conflicts with the status on a non-default branch. For example, an alert that appears in the "Open" list in the summary of alerts for `branch-x` could show a status of "Fixed" on the alert page, if the alert is already fixed on the default branch. You can view the status of the alert for the branch you filtered on in the  **Affected branches** section on the right side of the alert page.
+デフォルトではないブランチ上のアラートをフィルタリングしたものの、同じアラートがデフォルトブランチにも存在している場合、どのアラートのアラートページも、デフォルトではないブランチ上のステータスとの差異があっても、デフォルトブランチ上のアラートのステータスだけが反映されることに注意してください。 たとえば、`branch-x`に対するアラートのサマリ中の"Open"リストに表示されるアラートは、そのアラートが既にデフォルトブランチで修復されているなら、そのアラートページでは"Fixed"というステータスで表示されます。 フィルタしたブランチに対するアラートのステータスは、アラートページの右側の**Affected branches（影響されたブランチ）**セクションで見ることができます。
diff --git a/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md b/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
index 5cd2ea59ec..bb6c0b86f7 100644
--- a/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
+++ b/translations/ja-JP/data/reusables/code-scanning/github-issues-integration.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_code_scanning_capc %} alerts integrate with task lists in {% data variables.product.prodname_github_issues %} to make it easy for you to prioritize and track alerts with all your development work. Issue に関する詳しい情報については「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
+{% data variables.product.prodname_code_scanning_capc %}アラートは、{% data variables.product.prodname_github_issues %}でタスクリストと統合されており、開発作業全体の中でアラートを優先順位付けして追跡しやすくします。 Issue に関する詳しい情報については「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
 
-To track a code scanning alert in an issue, add the URL for the alert as a task list item in the issue. For more information about task lists, see "[About tasks lists](/issues/tracking-your-work-with-issues/about-task-lists)."
+Issue内でCode scanningアラートを追跡するには、アラートのURLをタスクリストのアイテムとしてIssueに追加してください。 タスクリストに関する詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/about-task-lists)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/code-scanning/licensing-note.md b/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
index 71ac760b15..8a1df37865 100644
--- a/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
+++ b/translations/ja-JP/data/reusables/code-scanning/licensing-note.md
@@ -1,8 +1,8 @@
 {% note %}
 
-**Note:** {% ifversion fpt %}
-The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories. The {% data variables.product.prodname_codeql_cli %} is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
-{%- elsif ghec %} The {% data variables.product.prodname_codeql_cli %} is free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+**ノート:** {% ifversion fpt %}
+{% data variables.product.prodname_codeql_cli %}はパブリックリポジトリでは無料で使用できます。 {% data variables.product.prodname_codeql_cli %}は、{% data variables.product.prodname_ghe_cloud %}を使用し、{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているOrganizationが所有するプライベートリポジトリでも使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
+{%- elsif ghec %}{% data variables.product.prodname_codeql_cli %}は{% data variables.product.prodname_dotcom_the_website %}でメンテナンスされているパブリックリポジトリでは無料で使用でき、{% data variables.product.prodname_advanced_security %}ライセンスを持っているお客様が所有するプライベートリポジトリでも使用できます。 詳細については「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}の利用規約](https://securitylab.github.com/tools/codeql/license)」及び「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
 {%- elsif ghes or ghae %}{% data variables.product.prodname_codeql_cli %}は、{% data variables.product.prodname_advanced_security %}ライセンスを持つお客様にご利用いただけます。
 {% endif %}
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
index 07f444ca8d..3f25bd67d1 100644
--- a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
+++ b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md
@@ -1,20 +1,18 @@
-コードをスキャンするために{% data variables.product.prodname_codeql %}を使う場合、{% data variables.product.prodname_codeql %}分析エンジンはコードからデータベースを生成し、それに対してクエリを実行します。 {% data variables.product.prodname_codeql %}の分析はデフォルトのクエリセットを使いますが、デフォルトのクエリに加えてもっと多くのクエリを実行するよう指定することもできます。
+When you use {% data variables.product.prodname_codeql %} to scan code, the {% data variables.product.prodname_codeql %} analysis engine generates a database from the code and runs queries on it. {% data variables.product.prodname_codeql %} analysis uses a default set of queries, but you can specify more queries to run, in addition to the default queries.
 
 {% ifversion codeql-packs %}
-You can run extra queries if they are part of a
-{% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+You can run extra queries if they are part of a {% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
 
 The options available to specify the additional queries you want to run are:
 
 - `packs` to install one or more {% data variables.product.prodname_codeql %} query packs (beta) and run the default query suite or queries for those packs.
-- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. クエリスイートの定義に関する詳しい情報については「[{% data variables.product.prodname_codeql %}クエリスイートの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)」を参照してください。
+- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
 
 You can use both `packs` and `queries` in the same workflow.
 {% else %}
-Any additional queries you want to run must belong to a
-{% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+Any additional queries you want to run must belong to a {% data variables.product.prodname_ql %} pack in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
 
-単一の _.ql_ ファイル、複数の _.ql_ ファイルを含むディレクトリ、_.qls_ クエリスイート定義ファイル、または任意の組み合わせを指定できます。 クエリスイートの定義に関する詳しい情報については「[{% data variables.product.prodname_codeql %}クエリスイートの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)」を参照してください。
+You can specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)."
 {% endif %}
 
 {% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, for example, `github/codeql/cpp/ql/src@main`. Such queries would have to be recompiled, and may not be compatible with the version of {% data variables.product.prodname_codeql %} currently active on {% data variables.product.prodname_actions %}, which could lead to errors during analysis.{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
index a2888bdc46..7ddce88f51 100644
--- a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
+++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -1,8 +1,8 @@
 {% note %}
 
 **ノート:**
-- SARIF upload supports a maximum of 5000 results per upload. この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
+- SARIFアップロードは、アップロードごとに最大5000件の結果をサポートします。 この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。
 
- - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries.
+ - アップロードごとに、SARIFアップロードは最大10MBの`gzip`圧縮されたSARIFファイルをサポートします。 この制限を超えるアップロードは拒否されます。 結果が多すぎてSARIFファイルが大きすぎる場合、設定ファイルを更新して最も重要なルールやクエリに結果を集中させるようにすべきです。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
index 3701caf95d..ad3e50ede9 100644
--- a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
+++ b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md
@@ -1 +1 @@
-アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。 You can also manage the port protocol and share the port within your organization or publicly.
+アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。 ポートプロトコルを管理し、Organization内で、もしくはパブリックにポートを共有することもできます。
diff --git a/translations/ja-JP/data/reusables/codespaces/availability.md b/translations/ja-JP/data/reusables/codespaces/availability.md
index df1d8f27be..6e70aae964 100644
--- a/translations/ja-JP/data/reusables/codespaces/availability.md
+++ b/translations/ja-JP/data/reusables/codespaces/availability.md
@@ -1 +1 @@
-Codespaces are available for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.
+Codespacesは、{% data variables.product.prodname_team %}及び{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有するリポジトリで利用できます。
diff --git a/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
index ab80f5c0e1..a8f0fc5047 100644
--- a/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
+++ b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md
@@ -1,7 +1,7 @@
-By default, a {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+デフォルトでは、{% data variables.product.prodname_actions %}ワークフローは事前ビルドされたテンプレートを作成あるいは更新するたび、あるいは事前ビルドが有効化されたブランチにプッシュするたびにトリガーされます。 他のワークフローと同じように、事前ビルドされたワークフローはアカウントに含まれるActionsの分があればその一部を消費し、そうでない場合はActionsの分に対する課金を生じさせます。 Actionsの分の価格に関する詳しい情報については「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 
-Alongside {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuild templates associated with each prebuild configuration for a given repository and region. Storage of prebuild templates is billed at the same rate as storage of codespaces. For more information, see "[Calculating storage usage](#calculating-storage-usage)."
+{% data variables.product.prodname_actions %}の分と合わせて、指定されたリポジトリとリージョンについて、それぞれの事前ビルドされた設定と関連づけられた事前ビルドテンプレートのストレージに対しても課金されます。 事前ビルドされたテンプレートのストレージは、Codespacesのストレージと同じレートで課金されます。 詳しい情報については「[ストレージの利用の計算](#calculating-storage-usage)」を参照してください。
 
-To reduce consumption of Actions minutes, you can set a prebuild template to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of template versions to be retained for your prebuild configurations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
+Actionsの分の消費を削減するために、開発コンテナ設定ファイルを変更したときにのみ、あるいはカスタムのスケジュールだけに従って事前ビルドされたテンプレートが更新されるように設定できます。 また、事前ビルドされた設定に対して保持されるテンプレートのバージョン数を調整することによって、ストレージの使用量を管理することもできます。 詳しい情報については「[事前ビルドの設定](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)」を参照してください。
 
-If you are an organization owner, you can track usage of prebuild workflows and storage by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." 詳しい情報については「[{% data variables.product.prodname_actions %}の利用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)」を参照してください。
+Organizationのオーナーは、事前ビルドされたワークフローとストレージの使用状況を、Organizationの{% data variables.product.prodname_actions %}使用状況レポートをダウンロードして追跡できます。 事前ビルドに対するワークフローの実行は、CSVの出力を"Create Codespaces Prebuilds"というワークフローだけが含まれるようにフィルタリングすれば、特定できます。 詳しい情報については「[{% data variables.product.prodname_actions %}の利用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md b/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
index 3bd6971a87..4141967f7b 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note**: The {% data variables.product.prodname_codespaces %} API is currently in public beta and subject to change.
+**ノート**: {% data variables.product.prodname_codespaces %} APIは現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
index 0be4a46707..6f7db70036 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md
@@ -1,9 +1,9 @@
-{% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage.
+{% data variables.product.prodname_codespaces %}は、コンピュートとストレージの使用量に応じて米ドル（USD）で課金されます。
 
-### Calculating compute usage
-Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_github_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly.
+### コンピュートの使用量の計算
+コンピュートの使用量は、{% data variables.product.prodname_github_codespaces %}インスタンスがアクティブな稼働時間の分の合計として定義されます。 コンピュートの使用量は、すべてのCodespacesが使用した実際の分数を合計することによって計算されます。 それらの合計は、日次で支払いサービスに報告され、月次で課金されます。
 
-Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)".
+稼働時間はcodespaceを停止することによって制御でき、この停止は手動で行うことも、あるいは開発者が非アクティブな期間を指定したあとで自動的に行うこともできます。 詳しい情報については「[codespaceのクローズもしくは停止](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)」を参照してください。
 
-### Calculating storage usage
-For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 
+### ストレージの使用量の計算
+{% data variables.product.prodname_github_codespaces %}の支払いにおいては、アカウントのすべてのCodespacesが使用するすべてのストレージが含まれます。 これには、Codespacesが使うあらゆるファイル、中でもクローンされたリポジトリ、設定ファイル、機能拡張などが含まれます。 それらの合計は、日次で支払いサービスに報告され、月次で課金されます。 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
index 557b845f10..d167ae1bc4 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -1 +1 @@
-Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+利用可能なマシンタイプの選択は、Organizationで設定されたポリシーによって、あるいはリポジトリのマシンタイプの最小仕様によって制限されていることがあります。 詳しい情報については「[マシンタイプへのアクセスの制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」及び「[codespaceマシンの最小仕様の設定](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
index 53aecddf17..608b5ef7c1 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md
@@ -1,3 +1,3 @@
-Typically, you can run your codespace on a choice of remote machine, from 2 cores to 32 cores. これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 For information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+通常、codespaceは2コアから32コアでリモートのマシンを選択して実行できます。 これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)」を参照してください。
 
-By default the machine type with the lowest valid resources is used when you create a codespace. 
+codespaceを作成したとき、デフォルトでは有効な最小リソースを持つマシンタイプが使われます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
index ccf956a015..79c395d216 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies.md
@@ -1,3 +1,3 @@
-1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
-1. On the "Codespace policies" page, click **Create Policy**.
-1. Enter a name for your new policy.
+1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}**を選択し、続いて** Policies（ポリシー）**をクリックしてください。
+1. "Codespace policies（ Codespaceのポリシー）"ページで、**Create Policy（ポリシーの作成）**をクリックしてください。
+1. 新しいポリシーの名前を入力してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
index 04e4a9bfda..e9c2d3a2a9 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md
@@ -1,11 +1,11 @@
-1. In the "Change policy target" area, click the dropdown button.
-1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. "Change policy target（ポリシーターゲットの変更）"のエリアで、ドロップダウンボタンをクリックしてください。
+1. **All repositories（すべてのリポジトリ）**もしくは**Selected repositories（選択したリポジトリ）**を選択し、ポリシーを適用するリポジトリを決定してください。
 1. [**Selected repositories**] を選択した場合、以下の手順に従います。
    1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。
 
-      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+      ![ポリシー設定の編集](/assets/images/help/codespaces/policy-edit.png)
 
-   2. Select the repositories you want this policy to apply to.
-   3. At the bottom of the repository list, click **Select repositories**.
+   2. ポリシーを適用したいリポジトリを選択してください。
+   3. リポジトリリストの下部で、**Select repositories（リポジトリの選択）**をクリックしてください。
 
-      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+      ![このポリシーのリポジトリを選択](/assets/images/help/codespaces/policy-select-repos.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
index 61e7031435..8f72ade561 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md
@@ -1,9 +1,9 @@
 {% note %}
 
-**Note:** You must set a spending limit before you can use {% data variables.product.prodname_codespaces %}.
+**ノート:** {% data variables.product.prodname_codespaces %}を利用するには、利用上限を設定しなければなりません。
 
 {% endnote %}
 
-By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0.
+デフォルトでは、OrganizationもしくはEnterpriseは$0の{% data variables.product.prodname_github_codespaces %}の利用上限を持っており、これは新しいcodespaceの作成や、既存のcodespaceのオープンを禁止します。 Organiationでユーザがcodespaceを作成できるようにするには、この上限を$0よりも大きな値に設定してください。
 
 {% data reusables.billing.overages-billed-monthly %}
diff --git a/translations/ja-JP/data/reusables/codespaces/command-palette-container.md b/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
index 0a3b03efb3..efad9c25b4 100644
--- a/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
+++ b/translations/ja-JP/data/reusables/codespaces/command-palette-container.md
@@ -1,3 +1,3 @@
-1. Access the {% data variables.product.prodname_vscode_command_palette %} (Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)), then start typing "dev container". **Codespaces: Add Development Container Configuration Files...（Codespaces: 開発コンテナ設定ファイルを追加...）**を選択してください。
+1. {% data variables.product.prodname_vscode_command_palette %}にアクセスし(Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux))、 "dev container"と入力し始めてください。 **Codespaces: Add Development Container Configuration Files...（Codespaces: 開発コンテナ設定ファイルを追加...）**を選択してください。
 
-   !["Codespaces: Add Development Container Configuration Files..." in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+   ![{% data variables.product.prodname_vscode_command_palette %}での"Codespaces: Add Development Container Configuration Files..."](/assets/images/help/codespaces/add-prebuilt-container-command.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/contact-support.md b/translations/ja-JP/data/reusables/codespaces/contact-support.md
index b3ea0615e1..ea14af60a8 100644
--- a/translations/ja-JP/data/reusables/codespaces/contact-support.md
+++ b/translations/ja-JP/data/reusables/codespaces/contact-support.md
@@ -1 +1 @@
-you may need to contact support. For more information, see "[Working with support](/codespaces/troubleshooting/working-with-support-for-codespaces)."
+サポートに連絡する必要があるかもしれません。 詳しい情報については「[サポートとの作業](/codespaces/troubleshooting/working-with-support-for-codespaces)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index c6b3a9fde2..6ad33181dd 100644
--- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -1,17 +1,17 @@
-After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+{% data variables.product.product_location %}上のアカウントを{% data variables.product.prodname_github_codespaces %}の機能拡張に接続すると、新しいcodespaceを作成できます。 {% data variables.product.prodname_github_codespaces %}の機能拡張に関する詳しい情報については[{% data variables.product.prodname_vs_marketplace_shortname %} Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)を参照してください。
 
 {% note %}
 
-**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page.
+**ノート**: 現在、{% data variables.product.prodname_vscode_shortname %}ではcodespaceの作成時に開発コンテナの設定を選択することはできません。 特定の開発コンテナの設定を選択したい場合、{% data variables.product.prodname_dotcom %} Webインターフェースを使ってcodespaceを作成してください。 詳しい情報については、このページの上部の**Web browser（Webブラウザ）**タブをクリックしてください。
 
 {% endnote %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
+2. 追加アイコン {% octicon "plus" aria-label="The plus icon" %} をクリックしてください。
 
    ![{% data variables.product.prodname_codespaces %} の [Create New Codespace] オプション](/assets/images/help/codespaces/create-codespace-vscode.png)
 
-3. Type the name of the repository you want to develop in, then select it.
+3. 開発を行いたいリポジトリ名を入力し、選択してください。
 
    ![新しい {% data variables.product.prodname_codespaces %} を作成するためのリポジトリを検索する](/assets/images/help/codespaces/choose-repository-vscode.png)
 
@@ -19,7 +19,7 @@ After you connect your account on {% data variables.product.product_location %}
 
    ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png)
 
-5. Click the machine type you want to use.
+5. 使用したいマシンタイプをクリックしてください。
 
    ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png)
 
diff --git a/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md b/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
index f215b74e73..add53f86da 100644
--- a/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
+++ b/translations/ja-JP/data/reusables/codespaces/customize-vcpus-and-ram.md
@@ -1,5 +1,5 @@
 vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to configure the development container that you use when you work in a codespace. Each repository can contain one or more  `devcontainer.json` files, to give you exactly the development environment you need to work on your code in a codespace.
+{% data variables.product.prodname_codespaces %}は`devcontainer.json`というファイルを使って、codespaceで作業する際に使用する開発コンテナを設定します。 それぞれのリポジトリには1つ以上の`devcontainer.json`ファイルを含めて、codespaceでコードの作業をするのに必要なとおりの開発環境を提供できます。
 
-On launch, {% data variables.product.prodname_codespaces %} uses a `devcontainer.json` file, and any dependent files that make up the dev container configuration, to install tools and runtimes, and perform other setup tasks that the project requires. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+起動時に{% data variables.product.prodname_codespaces %}は`devcontainer.json`ファイルと開発コンテナの設定を構成する依存ファイルを使い、ツールやランタイムをンストールし、プロジェクトが必要とするその他のセットアップタスクを行います。 詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
index 11feb3a8f3..1119abf9e8 100644
--- a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
@@ -1,7 +1,7 @@
-You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace.
+codespaceで作業をしていないときは、{% data variables.product.prodname_vscode_shortname %}内からcodespaceを削除できます。
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-1. Under "GITHUB CODESPACES", right-click the codespace you want to delete.
-1. Click **Delete Codespace**.
+1. "GITHUB CODESPACES"の下で、削除したいcodespaceを右クリックしてください。
+1. **Delete Codespace（Codespaceを削除）**をクリックしてください。
 
    ![{% data variables.product.prodname_dotcom %} で Codespaces を削除する](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/exporting-changes.md b/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
index f2c0e5a6e3..ca43afc318 100644
--- a/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
+++ b/translations/ja-JP/data/reusables/codespaces/exporting-changes.md
@@ -1 +1 @@
-If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still [export any work in progress changes to a new branch](/codespaces/troubleshooting/exporting-changes-to-a-branch). 
+利用上限に達すると、codespaceを作成したり再開したりすることはできなくなります。 ただし[進行中の変更を新しいブランチにエクスポート](/codespaces/troubleshooting/exporting-changes-to-a-branch)することはできます。 
diff --git a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
index d4e5abc125..d6e5aa5ebc 100644
--- a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
+++ b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
@@ -1 +1 @@
-To get started with {% data variables.product.prodname_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
+{% data variables.product.prodname_codespaces %}を使い始めるには、「[{% data variables.product.prodname_github_codespaces %}のクイックスタート](/codespaces/getting-started/quickstart)」を参照してください。 {% data variables.product.prodname_codespaces %}がどのように動作するのか、詳しく学ぶには「[{% data variables.product.prodname_github_codespaces %}を深く掘り下げる](/codespaces/getting-started/deep-dive)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
index 0980b3abc4..688c7f5842 100644
--- a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
+++ b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md
@@ -1 +1 @@
-For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+`devcontainer.json`ファイルで可能な設定とプロパティについては、{% data variables.product.prodname_vscode_shortname %} ドキュメントの 「[devcontainer.json リファレンス](https://aka.ms/vscode-remote/devcontainer.json)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md b/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
index 9879723104..9bb16553fd 100644
--- a/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
+++ b/translations/ja-JP/data/reusables/codespaces/port-visibility-settings.md
@@ -1,5 +1,5 @@
-There are three visibility settings:
+可視性の設定は3つあります:
 
-* `private` - Visible only to you. This is the default setting when you forward a port.
-* `org` - Visible to members of the organization that owns the repository.
-* `public` - Visible to anyone who knows the URL and port number.
+* `private` - 自分にだけ見えます。 これはポートをフォワードする際のデフォルト設定です。
+* `org` - リポジトリを所有するOrganizationのメンバーに見えます。
+* `public` - URLとポート番号を知っている人なら誰にでも見えます。
diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
index 68d9b051fd..ef98855a91 100644
--- a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
+++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md
@@ -1 +1 @@
-To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+codespaceの作成を高速化するために、リポジトリの管理者はリポジトリで{% data variables.product.prodname_codespaces %}の事前ビルドを有効化できます。 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の事前ビルドについて](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
index c82899edb6..632cb4a61c 100644
--- a/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
+++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md
@@ -1 +1 @@
-Prebuilds are not available if you choose to use a `devcontainer.json` file from a `.devcontainer/SUBDIRECTORY` location when you create a codespace. For information about choosing a `devcontainer.json` file, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
+codespaceを作成する際に`.devcontainer/SUBDIRECTORY`という場所から`devcontainer.json`ファイルを使うよう選択した場合、事前ビルドは利用できません。 `devcontainer.json`ファイルを選択することに関する情報については「[codespaceの作成](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
index ebdc1b5c0e..9e79fd326b 100644
--- a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
+++ b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md
@@ -1,4 +1,4 @@
-1. Access the {% data variables.product.prodname_vscode_command_palette %} (Shift + Command + P / Ctrl + Shift + P), then start typing "rebuild". **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。
+1. {% data variables.product.prodname_vscode_command_palette %}にアクセスし(Shift + Command + P / Ctrl + Shift + P)、"rebuild"と入力し始めてください。 **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。
 
     ![コンテナリビルドの選択肢](/assets/images/help/codespaces/codespaces-rebuild.png)
     
diff --git a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
index bc0a55a9cc..07d3a26e26 100644
--- a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
+++ b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md
@@ -1 +1 @@
-If changes to your dev container configuration cause a container error, your codespace will run in recovery mode, and you will see an error message.
+開発コンテナの設定の変更でコンテナエラーが生じた場合、codespaceはリカバリモードで動作し、エラーメッセージが表示されます。
diff --git a/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md b/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
index ca60cbd5a4..1bbb289023 100644
--- a/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
+++ b/translations/ja-JP/data/reusables/codespaces/restrict-port-visibility.md
@@ -1 +1 @@
-Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+Organizationのオーナーは、ポートのフォワードをパブリックに、あるいはOrganization内で利用できるようにする機能を制限できます。 詳しい情報については「[フォワードされたポートの可視性の制限](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/review-pr.md b/translations/ja-JP/data/reusables/codespaces/review-pr.md
index cf263511e8..f7305af917 100644
--- a/translations/ja-JP/data/reusables/codespaces/review-pr.md
+++ b/translations/ja-JP/data/reusables/codespaces/review-pr.md
@@ -1,5 +1,5 @@
-1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)."
-2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png)
-3. To review a specific file, click the **Open File** icon in the Side Bar. ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png)
-4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png)
-5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png)
+1. 「[Pull Requestのオープン](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)」の説明に従って、codespaceでPull Requestをオープンしてください。
+2. アクティビティバーで、**GitHub Pull Request**ビューをクリックしてください。 このビューは、codespaceでPull Requestをオープンした場合にのみ表示されます。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/github-pr-view.png)
+3. 特定のファイルをレビューするには、サイドバーの**Open File（ファイルをオープン）**アイコンをクリックしてください。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/changes-in-files.png)
+4. レビューコメントを追加するには、行番号の隣の**+**をクリックしてください。 レビューコメントを入力し、**Start Review（レビューを開始）**をクリックしてください。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/start-review.png)
+5. レビューコメントの追加を完了したら、コメントをサブミットするか、変更を承認するか、変更をリクエストするかをサイドバーから選択できます。 ![codespace内のPRのオープンのオプション](/assets/images/help/codespaces/submit-review.png)
diff --git a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
index ff45e6dc04..23562721a3 100644
--- a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
+++ b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md
@@ -1 +1 @@
-If a secret with the same name exists at multiple levels, the secret at the lowest level takes precedence. たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。
+複数のレベルで同じ名前のシークレットが存在する場合、最も低いレベルのシークレットが優先されます。 たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。
diff --git a/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md b/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
index 5a973ebb51..6f32bfdd0d 100644
--- a/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
+++ b/translations/ja-JP/data/reusables/codespaces/setup-custom-devcontainer.md
@@ -1 +1 @@
-To set up your repository to use a custom dev container, you will need to create one or more `devcontainer.json` files. You can add these either from a template, in {% data variables.product.prodname_vscode %}, or you can write your own. For more information on dev container configurations, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+カスタムの開発コンテナを使うようにリポジトリをセットアップするには、1つ以上の`devcontainer.json`ファイルを作成しなければなりません。 これらは{% data variables.product.prodname_vscode %}内でテンプレートから追加することも、独自に書くこともできます。 開発コンテナの設定に関する詳しい情報については「[開発コンテナの紹介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
index f93d8ed377..a9a658277a 100644
--- a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
+++ b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -1,3 +1,3 @@
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Your codespaces**.
+1. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}の右上から、プロフィール写真をクリックし、続いて**Your codespaces（あなたのcodespaces）**をクリックしてください。
 
-  !['自分のcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png)
+  !['あなたのcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png)
diff --git a/translations/ja-JP/data/reusables/command-palette/beta-note.md b/translations/ja-JP/data/reusables/command-palette/beta-note.md
index a6681190ee..f27f91ba18 100644
--- a/translations/ja-JP/data/reusables/command-palette/beta-note.md
+++ b/translations/ja-JP/data/reusables/command-palette/beta-note.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** The {% data variables.product.prodname_command_palette %} is currently in public beta and is subject to change.
+**ノート:** {% data variables.product.prodname_command_palette %}は現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/command-palette/change-scope.md b/translations/ja-JP/data/reusables/command-palette/change-scope.md
index 4cf46c21a4..2823401a3b 100644
--- a/translations/ja-JP/data/reusables/command-palette/change-scope.md
+++ b/translations/ja-JP/data/reusables/command-palette/change-scope.md
@@ -1,5 +1,5 @@
-1. Optionally, narrow, expand, or completely change the scope for suggestions by editing the path in the command palette's text field.
+1. あるいは、コマンドパレットのテキストフィールド内のパスを編集することによって、候補のスコープを狭めたり、広げたり、完全に変更したりしてください。
 
-   - To narrow the scope within a user or organization account, highlight a repository then use Tab to add it to the scope.
-   - To expand the scope, highlight and remove an item in the scope using the Backspace or delete key.
-   - To clear the scope and text box, click **Clear** or use CtrlBackspace (Windows and Linux) or ⌘Backspace (Mac).
+   - スコープをユーザもしくはOragnizationアカウント内に狭めるには、リポジトリをハイライトしてからTabを使ってそのリポジトリをスコープに追加してください。
+   - スコープを広げるには、スコープ内のアイテムをハイライトしてからバックスペースもしくは削除キーを使って削除してください。
+   - スコープとテキストボックスをクリアするには、**Clear（クリア）**をクリックするか、CtrlBackspace (Windows and Linux)もしくは⌘Backspace (Mac)を使ってください。
diff --git a/translations/ja-JP/data/reusables/command-palette/open-palette.md b/translations/ja-JP/data/reusables/command-palette/open-palette.md
index 46636e2c25..3b189abfb4 100644
--- a/translations/ja-JP/data/reusables/command-palette/open-palette.md
+++ b/translations/ja-JP/data/reusables/command-palette/open-palette.md
@@ -1 +1 @@
-1. Use Ctrl+K (Windows/Linux) or Command+K (Mac) to open the command palette with a scope determined by your current location in the UI. 
+1. Ctrl+K (Windows/Linux)もしくはCommand+K (Mac) を使い、UI中の現在の場所で決まるスコープでコマンドパレットをオープンしてください。 
diff --git a/translations/ja-JP/data/reusables/community/issue-forms-beta.md b/translations/ja-JP/data/reusables/community/issue-forms-beta.md
index 9c912118dd..36dea274ae 100644
--- a/translations/ja-JP/data/reusables/community/issue-forms-beta.md
+++ b/translations/ja-JP/data/reusables/community/issue-forms-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Issue forms are currently in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %} only.
+**ノート:** Issue フォームは、現在ベータとして{% data variables.product.prodname_dotcom_the_website %} の公開リポジトリでのみ利用できます。
 
 {% endnote %}
diff --git a/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md b/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
index 56cc4ec30a..707e856d4d 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-or-reject-suggestion.md
@@ -1 +1 @@
-1. To accept a suggestion, press Tab. To reject all suggestions, press Esc.
+1. 提案を受け入れるにはタブを押してください。 すべての提案を拒否するにはEscを押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
index 183cf25da8..332c0c13ae 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion-new-tab.md
@@ -1 +1 @@
-1. To accept a suggestion from the new tab, above the suggestion you want to accept, click **Accept solution**.
+1. 新しいタブからの提案を受け入れるには、受け入れたい提案の上の**Accept solution（ソリューションを受け入れる）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
index 5bee724a53..a64b405d1d 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion-tab.md
@@ -1 +1 @@
-1. If {% data variables.product.prodname_copilot %} offers a suggestion you want to accept, press Tab.
+1. {% data variables.product.prodname_copilot %}が受け入れたい提案をしてきたら、タブを押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/accept-suggestion.md b/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
index 4882c5d748..a972f3e690 100644
--- a/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/accept-suggestion.md
@@ -1 +1 @@
-1. To accept the suggestion, press Tab.
+1. 提案を受け入れるにはタブを押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md b/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
index a92c9879c7..ea13525d1d 100644
--- a/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
+++ b/translations/ja-JP/data/reusables/copilot/alternative-suggestions.md
@@ -1 +1 @@
-For any given input, {% data variables.product.prodname_copilot %} may offer multiple suggestions. You can select which suggestion to use, or reject all suggestions.
+任意の入力に対して{% data variables.product.prodname_copilot %}は複数の提案をすることがあります。 使用する提案を選択したり、すべての提案を拒否したりすることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md b/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
index 22b4ce4d82..1827274313 100644
--- a/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/close-suggestions-tab.md
@@ -1 +1 @@
-1. Alternatively, to reject all suggestions, close the suggestions tab.
+1. あるいは、すべての提案を拒否するには、提案のタブを閉じてください。
diff --git a/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md b/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
index a3436c556e..bcec9ba4ed 100644
--- a/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
+++ b/translations/ja-JP/data/reusables/copilot/copilot-prerequisites.md
@@ -1,2 +1,2 @@
-- {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers.
-- If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. You must provide billing information in order to start a free trial. 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
+- {% data variables.product.prodname_copilot %}は、検証済みの学生やオープンソースのメンテナなら無料で使用できます。
+- 学生やオープンソースのメンテナではない人は、1回60日のトライアルで{% data variables.product.prodname_copilot %}を無料で試すことができます。 無料のトライアルが終わったあと、継続して使うには有料プランが必要になります。 無料トライアルを始めるには、支払い情報を提供しなければなりません。 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-c-file.md b/translations/ja-JP/data/reusables/copilot/create-c-file.md
index 9a40edc6ce..724d84084c 100644
--- a/translations/ja-JP/data/reusables/copilot/create-c-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-c-file.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vs %}, create a new C# (_*.cs_) file.
+1. {% data variables.product.prodname_vs %}で、新しいC#(_*.cs_) のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-java-file.md b/translations/ja-JP/data/reusables/copilot/create-java-file.md
index d38696a1dd..b8a6abde9c 100644
--- a/translations/ja-JP/data/reusables/copilot/create-java-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-java-file.md
@@ -1 +1 @@
-1. In your JetBrains IDE, create a new Java (_*.java_) file.
+1. JetBrains IDEで、新しいJava (_*.java_) のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/create-js-file.md b/translations/ja-JP/data/reusables/copilot/create-js-file.md
index 38946eaa58..530fb6757f 100644
--- a/translations/ja-JP/data/reusables/copilot/create-js-file.md
+++ b/translations/ja-JP/data/reusables/copilot/create-js-file.md
@@ -1 +1 @@
-1. In {% data variables.product.prodname_vscode %}, create a new JavaScript (_*.js_) file.
+1. {% data variables.product.prodname_vscode %}で、新しいJavaScript(_*.js_)のファイルを作成してください。
diff --git a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
index 80318ab8a0..49c4afdfd7 100644
--- a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
+++ b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
@@ -6,7 +6,8 @@ Once you have an active {% data variables.product.prodname_copilot %} trial or s
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
-1. Under **Suggestions matching public code**, select the dropdown menu, then click **Allow** to allow suggestions matching public code, or **Block** to block suggestions matching public code. ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
+1. Under **Suggestions matching public code**, select the dropdown menu, then click **Allow** to allow suggestions matching public code, or **Block** to block suggestions matching public code.
+  ![Screenshot of duplication detection option](/assets/images/help/copilot/duplication-detection.png)
 {% data reusables.copilot.save-settings %}
 
 ### Enabling or disabling telemetry
@@ -15,5 +16,6 @@ You can configure how {% data variables.product.prodname_copilot %} uses your da
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.copilot-settings %}
-1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**. ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
+1. To allow or prevent {% data variables.product.prodname_dotcom %} using your telemetry data, select or deselect **Allow {% data variables.product.prodname_dotcom %} to use my code snippets for product improvements**.
+  ![Screenshot of telemetry option](/assets/images/help/copilot/telemetry-option.png)
 {% data reusables.copilot.save-settings %}
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md b/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
index 51edb37e07..a381d0e1a3 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-disabling-in-jetbrains.md
@@ -1,6 +1,6 @@
 ## {% data variables.product.prodname_copilot %} の有効化または無効化
 
-You can enable or disable {% data variables.product.prodname_copilot %} from within JetBrains. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the JetBrains window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
+{% data variables.product.prodname_copilot %}は、JetBrainsから有効化あるいは無効化できます。 JetBrainsウィンドウの下部のパネルの{% data variables.product.prodname_copilot %}ステータスアイコンは、{% data variables.product.prodname_copilot %}が有効化されているか、無効化されているかを示します。 有効化されている場合、このアイコンはハイライトされています。 無効化されている場合、このアイコンは灰色になります。
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window. ![Screenshot of status icon in JetBrains](/assets/images/help/copilot/status-icon-jetbrains.png)
-2. If you are disabling {% data variables.product.prodname_copilot %}, JetBrains will ask whether you want to disable the feature globally, or for the language of the file you are currently editing. To disable globally, click **Disable Completions**. Alternatively, click the button to disable completions for the language of the file you are currently editing. ![Screenshot of options to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
+1. {% data variables.product.prodname_copilot %}を有効化あるいは無効化するには、JetBrainsウィンドウの下部のパネルでステータスアイコンをクリックしてください。 ![JetBrainsのステータスアイコンのスクリーンショット](/assets/images/help/copilot/status-icon-jetbrains.png)
+2. {% data variables.product.prodname_copilot %}を無効化しようとしている場合、JetBrainsはこの機能をグローバルに無効化したいのか、あるいは現在編集中の言語のファイルで無効化したいのかを尋ねてきます。 グローバルに無効化する場合は**Disable Completions（補完の無効化）**をクリックしてください。 あるいは、現在編集中のファイルの言語に対する補完の無効化のボタンをクリックしてください。 ![グローバルもしくは現在の言語に対する{% data variables.product.prodname_copilot %}の無効化のオプションのスクリーンショット](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
index 2072011e5d..de3cc41cc8 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md
@@ -1,9 +1,11 @@
-## {% data variables.product.prodname_copilot %} の有効化または無効化
+## Enabling or disabling {% data variables.product.prodname_copilot %}
 
 You can enable or disable {% data variables.product.prodname_copilot %} from within {% data variables.product.prodname_vscode %}. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the background color of the icon will match the color of the status bar. When disabled, the background color of the icon will contrast with the color of the status bar.
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window. ![Screenshot of the status icon in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/status-icon-visual-studio-code.png)
+1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the {% data variables.product.prodname_vscode %} window.
+   ![Screenshot of the status icon in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/status-icon-visual-studio-code.png)
 2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable suggestions globally, or for the language of the file you are currently editing.
 
    - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Globally**.
-   - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable for _LANGUAGE_**. ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage.png)
+   - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable for _LANGUAGE_**.
+   ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage.png)
diff --git a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
index 50b19449a3..934ca3c637 100644
--- a/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
+++ b/translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md
@@ -1,8 +1,9 @@
-## {% data variables.product.prodname_copilot %} の有効化または無効化
+## Enabling or disabling {% data variables.product.prodname_copilot %}
 
 The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the {% data variables.product.prodname_vs %} window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the background color of the icon will match the color of the status bar. When disabled, it will have a diagonal line through it.
 
-1. To enable or disable {% data variables.product.prodname_copilot %}, click the {% data variables.product.prodname_copilot %} icon in the bottom panel of the {% data variables.product.prodname_vs %} window. ![Screenshot of editor margin in Visual Studio with the GitHub Copilot icon emphasized](/assets/images/help/copilot/editor-margin-visual-studio.png)
+1. To enable or disable {% data variables.product.prodname_copilot %}, click the {% data variables.product.prodname_copilot %} icon in the bottom panel of the {% data variables.product.prodname_vs %} window.
+  ![Screenshot of editor margin in Visual Studio with the GitHub Copilot icon emphasized](/assets/images/help/copilot/editor-margin-visual-studio.png)
 2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable suggestions globally, or for the language of the file you are currently editing.
 
    - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Enable Globally**.
diff --git a/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md b/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
index ad62637674..0437723ca4 100644
--- a/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
+++ b/translations/ja-JP/data/reusables/copilot/generating-suggestions-from-comments.md
@@ -1 +1 @@
-You can describe something you want to do using natural language within a comment, and {% data variables.product.prodname_copilot %} will suggest the code to accomplish your goal.
+やりたいことは自然言語でコメント内に記述でき、{% data variables.product.prodname_copilot %}はその目的を達成するためのコードを提案します。
diff --git a/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md b/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
index d2de9c1036..51937e45af 100644
--- a/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
+++ b/translations/ja-JP/data/reusables/copilot/install-copilot-in-neovim.md
@@ -1,2 +1,2 @@
-1. To use {% data variables.product.prodname_copilot %} in Neovim, install the {% data variables.product.prodname_copilot %} plugin. You can either install the plugin from a plugin manager or directly.
-   - If you use a plugin manager like vim-plug or packer.nvim, use the plugin manager to install `github/copilot.vim`. For more information, see the documentation for the plugin manager. For example, you can see the documentation for [vim-plug](https://github.com/junegunn/vim-plug) or [packer.nvim](https://github.com/wbthomason/packer.nvim).
+1. {% data variables.product.prodname_copilot %}をNeovimで使うには、{% data variables.product.prodname_copilot %}プラグインをインストールしてください。 プラグインは、プラグインマネージャーから、もしくは直接にインストールできます。
+   - vim-plugあるいはpacker.nvimのようなプラグインマネージャーを使っているなら、そのプラグインマネージャーを使って`github/copilot.vim`をインストールしてください。 詳しい情報についてはプラグインマネージャーのドキュメンテーションを参照してください。 たとえば[vim-plug](https://github.com/junegunn/vim-plug)あるいは[packer.nvim](https://github.com/wbthomason/packer.nvim)のドキュメンテーションが参照できます。
diff --git a/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md b/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
index 8beae81654..cc7011c2cb 100644
--- a/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
+++ b/translations/ja-JP/data/reusables/copilot/jetbrains-ides.md
@@ -1,4 +1,4 @@
-To use {% data variables.product.prodname_copilot %} in JetBrains, you must have a compatible JetBrains IDE installed. {% data variables.product.prodname_copilot %} is compatible with the following IDEs.
+{% data variables.product.prodname_copilot %}をJetBrainsで使うには、互換性のあるJetBrains IDEをインストールしていなければなりません。 {% data variables.product.prodname_copilot %}は以下のIDEと互換性があります。
 
 - IntelliJ IDEA (Ultimate, Community, Educational)
 - Android Studio
@@ -16,4 +16,4 @@ To use {% data variables.product.prodname_copilot %} in JetBrains, you must have
 - RubyMine
 - WebStorm
 
-For more information, see the [JetBrains IDEs](https://www.jetbrains.com/products/) tool finder.
+詳しい情報については[JetBrains IDEs](https://www.jetbrains.com/products/)ツールファインダーを参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/procedural-intro.md b/translations/ja-JP/data/reusables/copilot/procedural-intro.md
index 4c4cd6306d..5cb3b7e996 100644
--- a/translations/ja-JP/data/reusables/copilot/procedural-intro.md
+++ b/translations/ja-JP/data/reusables/copilot/procedural-intro.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} provides autocomplete-style suggestions from an AI pair programmer as you code. For more information, see "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)".
+{% data variables.product.prodname_copilot %}は、コーディング中にAIペアプログラマから自動補完スタイルの提案を提供します。 詳しい情報については「[{% data variables.product.prodname_copilot %}について](/copilot/overview-of-github-copilot/about-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md b/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
index 6d7bfe5886..4677df4289 100644
--- a/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
+++ b/translations/ja-JP/data/reusables/copilot/reject-suggestions-escape.md
@@ -1 +1 @@
-1. Alternatively, to reject all suggestions, press Esc.
+1. あるいは、すべての提案を拒否するにはEscを押してください。
diff --git a/translations/ja-JP/data/reusables/copilot/save-settings.md b/translations/ja-JP/data/reusables/copilot/save-settings.md
index 9bfed3a0d8..6adfe4cb16 100644
--- a/translations/ja-JP/data/reusables/copilot/save-settings.md
+++ b/translations/ja-JP/data/reusables/copilot/save-settings.md
@@ -1 +1 @@
-1. To confirm your new settings, click **Save**.
+1. 新しい設定を決定するには**Save（保存）**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md b/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
index 4e39f7b40b..efe53a231d 100644
--- a/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
+++ b/translations/ja-JP/data/reusables/copilot/see-alternative-suggestions.md
@@ -1 +1 @@
-1. Optionally, you can see alternative suggestions, if any are available.
+1. あるいは、代替提案が利用できる場合は、それらを見ることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/signup-procedure.md b/translations/ja-JP/data/reusables/copilot/signup-procedure.md
index 139ac25221..7ecea862a5 100644
--- a/translations/ja-JP/data/reusables/copilot/signup-procedure.md
+++ b/translations/ja-JP/data/reusables/copilot/signup-procedure.md
@@ -1,17 +1,17 @@
 {% data variables.product.prodname_copilot %}を使い始めるには、無料の試用もしくはプランのセットアップが必要です。
 
 {% data reusables.user-settings.access_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**.
-1. On the {% data variables.product.prodname_copilot %} settings page, click **Enable {% data variables.product.prodname_copilot %}**.
+1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**をクリックしてください。
+1. {% data variables.product.prodname_copilot %}の設定ページで**Enable {% data variables.product.prodname_copilot %}**をクリックしてください。
 
-   ![Screenshot of GitHub Copilot settings with Enable {% data variables.product.prodname_copilot %} button emphasized](/assets/images/help/copilot/copilot-settings-enable-button.png)
+   ![{% data variables.product.prodname_copilot %}の有効化ボタンが強調されたGitHub Copilotの設定のスクリーンショット](/assets/images/help/copilot/copilot-settings-enable-button.png)
 1. 支払いを月次でするか年次でするかを選択し、 **Continue to get access to Copilot（Copilotへのアクセスを継続）**をクリックしてください。
-   - If your personal account meets the criteria for a free {% data variables.product.prodname_copilot %} subscription instead of a trial, you will automatically be taken to step 6.
+   - 個人アカウントがトライアルの代わりに無料の{% data variables.product.prodname_copilot %}分の基準を満たしている場合、自動的にステップ6に進みます。
 
    ![Copilotへのアクセスを継続のボタンが強調された試用のセットアップのスクリーンショット](/assets/images/help/copilot/copilot-billing-cycle.png)
-1. Follow the steps to confirm your payment details, then click **Submit**.
+1. 手順にしたがって支払いの詳細を確認し、**Submit（サブミット）**をクリックしてください。
 1. 設定を選択し、**Save and get started（保存して使用を開始）**をクリックしてください。
 
-   ![Screenshot of GitHub Copilot settings with Save and get started button](/assets/images/help/copilot/copilot-signup-preferences.png)
+   ![保存と開始ボタンがあるGitHub Copilotの設定のスクリーンショット](/assets/images/help/copilot/copilot-signup-preferences.png)
 
-   You can change these preferences at a later time by returning to your {% data variables.product.prodname_copilot %} settings. For more information, see "[Configuring GitHub Copilot in Visual Studio Code](/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code#configuring-github-copilot-settings-on-githubcom)."
+   これらの設定は、{% data variables.product.prodname_copilot %}の設定に戻れば後ほど変更できます。 詳しい情報については「[Visual Studio CodeでのGitHub Copilotの設定](/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code#configuring-github-copilot-settings-on-githubcom)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md b/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
index 7f89c6b13f..4a4375ed2e 100644
--- a/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
+++ b/translations/ja-JP/data/reusables/copilot/suggestions-new-tab.md
@@ -1 +1 @@
-You may not want any of the initial suggestions {% data variables.product.prodname_copilot %} offers. You can use a keyboard shortcut to prompt {% data variables.product.prodname_copilot %} to show you multiple suggestions in a new tab.
+{% data variables.product.prodname_copilot %}による最初の提案は受け入れられないかもしれません。 キーボードショートカットを使って、{% data variables.product.prodname_copilot %}に複数の提案を新しいタブに表示させるようにすることができます。
diff --git a/translations/ja-JP/data/reusables/copilot/supported-languages.md b/translations/ja-JP/data/reusables/copilot/supported-languages.md
index 3568cc314a..ed51adfa44 100644
--- a/translations/ja-JP/data/reusables/copilot/supported-languages.md
+++ b/translations/ja-JP/data/reusables/copilot/supported-languages.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} provides suggestions for numerous languages and a wide variety of frameworks, but works especially well for Python, JavaScript, TypeScript, Ruby, Go, C# and C++.
+{% data variables.product.prodname_copilot %}は多くの言語と幅広いフレームワークに対して提案を行いますが、特にPython、JavaScript、TypeScript、Ruby、Go、C#、C++でうまく機能します。
diff --git a/translations/ja-JP/data/reusables/copilot/type-function-header-c.md b/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
index 5e8a63d0f4..be413b54a9 100644
--- a/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
+++ b/translations/ja-JP/data/reusables/copilot/type-function-header-c.md
@@ -1,4 +1,4 @@
-1. In the C# file, type the following function header.
+1. C#のファイルで、以下の関数ヘッダを入力してください。
 
     ```csharp{:copy}
     function calculateDaysBetweenDates(begin, end) {
diff --git a/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md b/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
index b4eb718d8f..48e4125fa2 100644
--- a/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
+++ b/translations/ja-JP/data/reusables/copilot/windows-linux-next-suggestion.md
@@ -1 +1 @@
-- On Windows or Linux, press Alt+] for the next suggestion, or Alt+[ for the previous suggestion.
+- WindowsまたはLinuxでは、Alt+]を押せば次の提案に、Alt+[を押せば前の提案に移ります。
diff --git a/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md b/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
index 2f18d3737b..571842fb79 100644
--- a/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
+++ b/translations/ja-JP/data/reusables/dependabot/about-the-dependency-graph.md
@@ -1,4 +1,4 @@
-The dependency graph is a summary of the manifest and lock files stored in a repository{% ifversion dependency-submission-api %} and any dependencies that are submitted for the repository using the Dependency submission API (beta){% endif %}. それぞれのリポジトリにおいて、依存関係グラフは以下を表示します。{% ifversion fpt or ghec %}
+依存関係グラフは、リポジトリに保存されているマニフェスト及びロックファイル{% ifversion dependency-submission-api %}及びDependency submission API（ベータ）を使ってリポジトリにサブミットされた依存関係{% endif %}のまとめです。 それぞれのリポジトリにおいて、依存関係グラフは以下を表示します。{% ifversion fpt or ghec %}
 
 - リポジトリが依存している依存関係、エコシステム、パッケージ
 - リポジトリに依存する対象、リポジトリ、パッケージ{% else %}依存関係、すなわちリポジトリが依存するエコシステムとパッケージ。 {% data variables.product.product_name %}は、リポジトリに依存する対象、リポジトリ、パッケージに関する情報を計算しません。{% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
index f50ef78f03..0e6b435b8f 100644
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
+++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Dependabot security updates and version updates are currently available for {% data variables.product.prodname_ghe_cloud %} and in beta for {% data variables.product.prodname_ghe_server %} 3.3. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates.
+**ノート:** Dependabotのセキュリティアップデート及びバージョンアップデートは、現在{% data variables.product.prodname_ghe_cloud %}で利用可能であり、{% data variables.product.prodname_ghe_server %} 3.3でベータです。 Dependabotアップデートの有効化の手順については[営業チームに連絡](https://enterprise.github.com/contact)してください。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
index 948349fcb4..81c29fbb0c 100644
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
+++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
@@ -2,9 +2,9 @@
 
 {% note %}
 {% ifversion ghes = 3.4 %}
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在パブリックベータであり、変更されることがあります。
 {% else %}
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in private beta and subject to change. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在プライベートベータであり、変更されることがあります。 Dependabotアップデートの有効化の手順については[営業チームに連絡](https://enterprise.github.com/contact)してください。
 {% endif %}
 
 {% endnote %}
@@ -15,7 +15,7 @@
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+**ノート:** {% data variables.product.prodname_dependabot %}セキュリティ及びバージョンアップデートは現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/configuration-options.md b/translations/ja-JP/data/reusables/dependabot/configuration-options.md
index 9ab6ec3a2f..5753ce531d 100644
--- a/translations/ja-JP/data/reusables/dependabot/configuration-options.md
+++ b/translations/ja-JP/data/reusables/dependabot/configuration-options.md
@@ -1,25 +1,25 @@
-| オプション                                                                                                                                                                            |  必須   | Security Updates | Version Updates | 説明                                                                      |
-|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:----------------:|:---------------:|:----------------------------------------------------------------------- |
-| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)                                  | **X** |                  |        X        | 使用するパッケージマネージャー                                                         |
-| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory)                                                  | **X** |                  |        X        | パッケージマニフェストの場所                                                          |
-| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval)                                   | **X** |                  |        X        | 更新を確認する頻度                                                               |
-| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)                                                          |       |        X         |        X        | 許可する更新をカスタマイズする                                                         |
-| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees)                                                  |       |        X         |        X        | プルリクエストのアサイン担当者                                                         |
-| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message)                                        |       |        X         |        X        | コミットメッセージの設定                 |{% ifversion fpt or ghec or ghes > 3.4 %}
-| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)                        |       |                  |        X        | ベータレベルのサポートがあるエコシステムを有効にする 
+| オプション                                                                                                                                                                            |  必須   | セキュリティアップデート | バージョンアップデート | 説明                                                                      |
+|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------:|:-----------:|:----------------------------------------------------------------------- |
+| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)                                  | **X** |              |      X      | 使用するパッケージマネージャー                                                         |
+| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory)                                                  | **X** |              |      X      | パッケージマニフェストの場所                                                          |
+| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval)                                   | **X** |              |      X      | 更新を確認する頻度                                                               |
+| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)                                                          |       |      X       |      X      | 許可する更新をカスタマイズする                                                         |
+| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees)                                                  |       |      X       |      X      | プルリクエストのアサイン担当者                                                         |
+| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message)                                        |       |      X       |      X      | コミットメッセージの設定                 |{% ifversion fpt or ghec or ghes > 3.4 %}
+| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)                        |       |              |      X      | ベータレベルのサポートがあるエコシステムを有効にする 
 {% endif %}
-| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)                                                        |       |        X         |        X        | 特定の依存関係またはバージョンを無視する                                                    |
-| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution)    |       |                  |        X        | マニフェストファイル内でコードの実行を許可または拒否する                                            |
-| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels)                                                        |       |        X         |        X        | プルリクエストに設定するラベル                                                         |
-| [`マイルストーン`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone)                                                    |       |        X         |        X        | プルリクエストに設定するマイルストーン                                                     |
-| [`open-pull-requests-limit`](#open-pull-requests-limit)                                                                                                                          |       |        X         |        X        | バージョン更新時のオープンなプルリクエスト数を制限する                                             |
-| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) |       |        X         |        X        | プルリクエストブランチ名の区切り文字を変更する                                                 |
-| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy)                                      |       |        X         |        X        | 自動リベースを無効にする                                                            |
-| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries)                                                |       |                  |        X        | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ    |
-| [`レビュー担当者`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers)                                                    |       |        X         |        X        | プルリクエストのレビュー担当者                                                         |
-| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday)                                             |       |                  |        X        | 更新を確認する曜日                                                               |
-| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime)                                           |       |                  |        X        | 更新を確認する時刻 (hh:mm)                                                       |
-| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone)                                   |       |                  |        X        | 時刻のタイムゾーン（ゾーン識別子）                                                       |
-| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch)                                          |       |                  |        X        | プルリクエストを作成するブランチ                                                        |
-| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor)                                                        |       |                  |        X        | ベンダーまたはキャッシュされた依存関係を更新する                                                |
-| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy)                              |       |        X         |        X        | マニフェストのバージョン要件の更新方法                                                     |
+| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)                                                        |       |      X       |      X      | 特定の依存関係またはバージョンを無視する                                                    |
+| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution)    |       |              |      X      | マニフェストファイル内でコードの実行を許可または拒否する                                            |
+| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels)                                                        |       |      X       |      X      | プルリクエストに設定するラベル                                                         |
+| [`マイルストーン`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone)                                                    |       |      X       |      X      | プルリクエストに設定するマイルストーン                                                     |
+| [`open-pull-requests-limit`](#open-pull-requests-limit)                                                                                                                          |       |      X       |      X      | バージョン更新時のオープンなプルリクエスト数を制限する                                             |
+| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) |       |      X       |      X      | プルリクエストブランチ名の区切り文字を変更する                                                 |
+| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy)                                      |       |      X       |      X      | 自動リベースを無効にする                                                            |
+| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries)                                                |       |              |      X      | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ    |
+| [`レビュー担当者`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers)                                                    |       |      X       |      X      | プルリクエストのレビュー担当者                                                         |
+| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday)                                             |       |              |      X      | 更新を確認する曜日                                                               |
+| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime)                                           |       |              |      X      | 更新を確認する時刻 (hh:mm)                                                       |
+| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone)                                   |       |              |      X      | 時刻のタイムゾーン（ゾーン識別子）                                                       |
+| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch)                                          |       |              |      X      | プルリクエストを作成するブランチ                                                        |
+| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor)                                                        |       |              |      X      | ベンダーまたはキャッシュされた依存関係を更新する                                                |
+| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy)                              |       |      X       |      X      | マニフェストのバージョン要件の更新方法                                                     |
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
index c2bfc45615..2c5c4d6883 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md
@@ -1,7 +1,7 @@
 {% ifversion ghae %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change.
+**ノート:** {% data variables.product.prodname_dependabot_alerts %}は現在ベータであり、変更されることがあります。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
index 367cbb25f8..6010e6221c 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
@@ -1,3 +1,3 @@
 {% ifversion ghes or ghae %}
-Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。
+Enterpriseのオーナーは、{% ifversion ghes %}依存関係グラフと{% endif %}{% data variables.product.prodname_dependabot_alerts %}をEnterpriseで設定できます。 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。
 {% endif %} 
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
index b7461e93c5..6716e3b0ad 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
@@ -1,13 +1,13 @@
-The table below summarizes whether dependency scope is supported for various ecosystems and manifests, that is, whether {% data variables.product.prodname_dependabot %} can identify if a dependency is used for development or production.
+以下の表は、依存関係のスコープが様々なエコシステム及びマニフェストでサポートされているか、すなわち{% data variables.product.prodname_dependabot %}が依存関係が開発もしくは実働で利用されているかを特定できるかをまとめたものです。
 
-| **言語**                  |   **エコシステム**   |          **Manifest file**           | **Dependency scope supported**                                                      |
+| **言語**                  |   **エコシステム**   |            **マニフェストファイル**            | **依存関係スコープがサポートされているか**                                                             |
 |:----------------------- |:--------------:|:------------------------------------:|:----------------------------------------------------------------------------------- |
-| Go                      |    Goモジュール     |                go.mod                | No, defaults to runtime                                                             |
-| Go                      |    Goモジュール     |                go.sum                | No, defaults to runtime                                                             |
-| Java                    |     Maven      |               pom.xml                | ✔ `test` maps to development, else scope defaults to runtime                        |
+| Go                      |    Goモジュール     |                go.mod                | いいえ。デフォルトはランタイム                                                                     |
+| Go                      |    Goモジュール     |                go.sum                | いいえ。デフォルトはランタイム                                                                     |
+| Java                    |     Maven      |               pom.xml                | ✔ `test`は開発にマップされ、そうでなければスコープはデフォルトでランタイム                                           |
 | JavaScript              |      npm       |             package.json             | ✔                                                                                   |
 | JavaScript              |      npm       |          package-lock.json           | ✔                                                                                   |
-| JavaScript              |    yarn v1     |              yarn.lock               | No, defaults to runtime                                                             |
+| JavaScript              |    yarn v1     |              yarn.lock               | いいえ。デフォルトはランタイム                                                                     |
 | PHP                     |    Composer    |            composer.json             | ✔                                                                                   |
 | PHP                     |    Composer    |            composer.lock             | ✔                                                                                   |
 | Python                  |     Poetry     |             poetry.lock              | ✔                                                                                   |
@@ -16,10 +16,10 @@ The table below summarizes whether dependency scope is supported for various eco
 | Python                  |      pip       |             pipfile.lock             | ✔                                                                                   |
 | Python                  |      pip       |               pipfile                | ✔                                                                                   |
 | Ruby                    |    RubyGems    |               Gemfile                | ✔                                                                                   |
-| Ruby                    |    RubyGems    |             Gemfile.lock             | No, defaults to runtime                                                             |
+| Ruby                    |    RubyGems    |             Gemfile.lock             | いいえ。デフォルトはランタイム                                                                     |
 | Rust                    |     Cargo      |              Cargo.toml              | ✔                                                                                   |
-| Rust                    |     Cargo      |              Cargo.lock              | No, defaults to runtime                                                             |
-| YAML                    | GitHub Actions |                  -                   | No, defaults to runtime                                                             |
-| .NET (C#, F#, VB, etc.) |     NuGet      | .csproj / .vbproj .vcxproj / .fsproj | No, defaults to runtime                                                             |
-| .NET                    |     NuGet      |           packages.config            | No, defaults to runtime                                                             |
+| Rust                    |     Cargo      |              Cargo.lock              | いいえ。デフォルトはランタイム                                                                     |
+| YAML                    | GitHub Actions |                  -                   | いいえ。デフォルトはランタイム                                                                     |
+| .NET (C#, F#, VB, etc.) |     NuGet      | .csproj / .vbproj .vcxproj / .fsproj | いいえ。デフォルトはランタイム                                                                     |
+| .NET                    |     NuGet      |           packages.config            | いいえ。デフォルトはランタイム                                                                     |
 | .NET                    |     NuGet      |               .nuspec                | ✔ When the tag != runtime                                                           |
diff --git a/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md b/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
index c9964a9b33..08628cb121 100644
--- a/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
+++ b/translations/ja-JP/data/reusables/discussions/about-organization-discussions.md
@@ -1,5 +1,5 @@
 When you enable organization discussions, you will choose a repository in the organization to be the source repository for your organization discussions. You can use an existing repository or create a repository specifically to hold your organization discussions. Discussions will appear both on the discussions page for the organization and on the discussion page for the source repository.
 
-Permission to participate in or manage discussion in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
+Permission to participate in or manage discussions in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
 
 You can change the source repository at any time. If you change the source repository, discussions are not transferred to the new source repository.
diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md
new file mode 100644
index 0000000000..e5656496c5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise-accounts/packages-tab.md
@@ -0,0 +1 @@
+1. 左のサイドバーで**Packages**をクリックしてください。
diff --git a/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md b/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md
new file mode 100644
index 0000000000..f7cba5e6b2
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise/about-ssh-ports.md
@@ -0,0 +1,5 @@
+Each {% data variables.product.product_name %} instance accepts SSH connections over two ports. Site administrators can access the administrative shell via SSH, then run command-line utilities, troubleshoot, and perform maintenance. Users can connect via SSH to access and write Git data in the instance's repositories. Users do not have shell access to your instance. 詳しい情報については、次の記事を参照してください。
+
+- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
+- "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)"
+- 「[SSHについて](/authentication/connecting-to-github-with-ssh/about-ssh)」
diff --git a/translations/ja-JP/data/reusables/enterprise/apply-configuration.md b/translations/ja-JP/data/reusables/enterprise/apply-configuration.md
new file mode 100644
index 0000000000..b436efa0a1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise/apply-configuration.md
@@ -0,0 +1,12 @@
+1. To apply the configuration, enter the following command.
+
+   {% note %}
+
+   **Note**: During a configuration run, services on {% data variables.product.product_location %} may restart, which can cause brief downtime for users.
+
+   {% endnote %}
+
+    ```shell
+    ghe-config-apply
+    ```
+1. 設定が完了するのを待ってください。
diff --git a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
index a6035dfd4f..33783192a4 100644
--- a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,5 +1,7 @@
+{% ifversion ghes < 3.6 %}
 {% note %}
 
 **Note:** Repository caching is currently in beta and subject to change.
 
 {% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
index 1811645d3b..2878e9c49b 100644
--- a/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
+++ b/translations/ja-JP/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -1,4 +1,5 @@
-1. {% data variables.product.product_location %}にSSHでアクセスしてください。 詳しい情報については「[管理シェル（SSH）にアクセスする](/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。
-```shell
-$ ssh -p 122 admin@HOSTNAME
-```
+1. {% data variables.product.product_location %}にSSHでアクセスしてください。 If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   ```shell
+   $ ssh -p 122 admin@HOSTNAME
+   ```
diff --git a/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
index e989e63cdf..a11b1fb4f4 100644
--- a/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
+++ b/translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
@@ -1,5 +1,9 @@
 {% warning %}
 
-**ノート:** 匿名Gitアクセスを有効にする場合、この機能のすべてのアクセスと利用に責任を負うことになります。 {% data variables.product.company_short %}は、この機能のあらゆる意図しないアクセスや悪用に対して責任を負いません。 また、弊社から購入したユーザライセンス数の制限を含む{% data variables.product.company_short %}のライセンスに違反するためにこの機能を使うことはできません。
+**警告:**
+
+- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol.
+- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature.
+- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.product.product_location %}.
 
 {% endwarning %}
diff --git a/translations/ja-JP/data/reusables/gated-features/copilot.md b/translations/ja-JP/data/reusables/gated-features/copilot.md
index 0a9cd66858..f3dcf72768 100644
--- a/translations/ja-JP/data/reusables/gated-features/copilot.md
+++ b/translations/ja-JP/data/reusables/gated-features/copilot.md
@@ -1 +1 @@
-{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %} is free to use for verified students and open source maintainers. If you are not a student or open source maintainer, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
+{% data variables.product.prodname_copilot %} is available to {% data variables.product.company_short %} customers with a personal account on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_copilot %}は、検証済みの学生やオープンソースのメンテナなら無料で使用できます。 学生やオープンソースのメンテナではない人は、1回60日のトライアルで{% data variables.product.prodname_copilot %}を無料で試すことができます。 無料のトライアルが終わったあと、継続して使うには有料プランが必要になります。 詳しい情報については、「[{% data variables.product.prodname_copilot %}の支払いについて](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/gated-features/discussions.md b/translations/ja-JP/data/reusables/gated-features/discussions.md
deleted file mode 100644
index 65d9afd325..0000000000
--- a/translations/ja-JP/data/reusables/gated-features/discussions.md
+++ /dev/null
@@ -1 +0,0 @@
-{% data variables.product.prodname_discussions %} is available for public and private repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %}
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md b/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md
new file mode 100644
index 0000000000..079a514846
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-benefits.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} stores container images within your organization or personal account, and allows you to associate an image with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. You can also access public container images anonymously.
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
new file mode 100644
index 0000000000..5d685d5f4f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %} 3.6 supports migration for Docker images stored in organizations. A future release will support migration of user-owned images.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md b/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md
new file mode 100644
index 0000000000..9d7d0dc5e0
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-migration-namespaces.md
@@ -0,0 +1 @@
+Any scripts or {% data variables.product.prodname_actions %} workflows that use the namespace for the Docker registry, {% data variables.product.prodname_docker_registry_namespace %}, will continue to work after migration to the {% data variables.product.prodname_container_registry %} at {% data variables.product.prodname_container_registry_namespace %}.
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md b/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md
new file mode 100644
index 0000000000..5b6ed35c4f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-replaces-docker-registry.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_container_registry %} replaces {% data variables.product.company_short %}'s Docker registry.
diff --git a/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md b/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
index b276a52455..a698129aaa 100644
--- a/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
+++ b/translations/ja-JP/data/reusables/package_registry/verify_repository_field.md
@@ -1 +1 @@
-1. プロジェクトの*package.json*中の`repository`フィールドを検証してください。 `repository`フィールドは、{% data variables.product.prodname_dotcom %}リポジトリのURLと一致していなければなりません。 たとえば、あなたのリポジトリのURLが`github.com/my-org/test`なら、repositoryフィールドは`git://github.com/my-org/test.git`でなければなりません。
+1. プロジェクトの*package.json*中の`repository`フィールドを検証してください。 `repository`フィールドは、{% data variables.product.prodname_dotcom %}リポジトリのURLと一致していなければなりません。 For example, if your repository URL is `github.com/my-org/test` then the repository field should be `https://github.com/my-org/test.git`.
diff --git a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
new file mode 100644
index 0000000000..1de17f89af
--- /dev/null
+++ b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
@@ -0,0 +1,10 @@
+Compulsory commit signoffs only apply to commits made via the web interface. For commits made via the Git command line interface, the commit author must sign off on the commit using the `--signoff` option. For more information, see the [Git documentation](https://git-scm.com/docs/git-commit).
+
+
+You can determine whether a repository you are contributing to has compulsory commit signoffs enabled by checking the header of the commit form at the bottom of the file you are editing. After compulsory commit signoff has been enabled, the header will read "Sign off and commit changes."
+
+![Screenshot of commit commit form with compulsory signoff enabled](/assets/images/help/commits/commit-form-with-signoff-enabled.png)
+
+Before signing off on a commit, you should ensure that your commit is in compliance with the rules and licensing governing the repository you're committing to. The repository may use a sign off agreement, such as the Developer Certificate of Origin from the Linux Foundation. For more information, see the [Developer Certificate of Origin](https://developercertificate.org/).
+
+Signing off on a commit differs from signing a commit. For more information about signing a commit, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
index 7a23691721..c2dc16ef62 100644
--- a/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
+++ b/translations/ja-JP/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -1,5 +1 @@
-{% ifversion fpt or ghec %}
-For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)."
-{% else %}
-For more information about advisory data, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/free-pro-team@latest/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
-{% endif %}
+詳しい情報については、「[{% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリを参照する](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/server-statistics/release-phase.md b/translations/ja-JP/data/reusables/server-statistics/release-phase.md
deleted file mode 100644
index 17f100fd26..0000000000
--- a/translations/ja-JP/data/reusables/server-statistics/release-phase.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** {% data variables.product.prodname_server_statistics %} is in public beta and subject to change.
-
-{% endnote %}
diff --git a/translations/ja-JP/data/reusables/ssh/about-ssh.md b/translations/ja-JP/data/reusables/ssh/about-ssh.md
new file mode 100644
index 0000000000..b4c0c5361a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/ssh/about-ssh.md
@@ -0,0 +1 @@
+You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine.
diff --git a/translations/ja-JP/data/reusables/ssh/key-type-support.md b/translations/ja-JP/data/reusables/ssh/key-type-support.md
index f2a03a9ed5..85ace1b53c 100644
--- a/translations/ja-JP/data/reusables/ssh/key-type-support.md
+++ b/translations/ja-JP/data/reusables/ssh/key-type-support.md
@@ -8,4 +8,21 @@ As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add ne
 RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures.
 
 {% endnote %}
-{% endif %}
+
+{% elsif ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
+
+

+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
new file mode 100644
index 0000000000..d2c95da8a5
--- /dev/null
+++ b/translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
@@ -0,0 +1,2 @@
+- The RSA key was added to a user account on {% data variables.product.product_location %} after the cutoff date of midnight UTC on August 1, 2022.
+- The SSH client signs the connection attempt with the SHA-1 hash function.
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 698b07d89a..84da4d68e8 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -179,7 +179,7 @@ product_landing:
   try_another: 他のフィルタを試すか、あなたのコードサンプルを追加してください。
   no_result: 申し訳ありませんが、指定されたフィルタにマッチするガイドはありません。
   learn: コードサンプルの追加方法を学ぶ
-  communities_using_discussions: ディスカッションを使用しているコミュニティ
+  communities_using_discussions: Communities on GitHub.com using discussions
   add_your_community: コミュニティを追加する
   sponsor_community: GitHub Sponsorsコミュニティ
   supported_releases: サポートされているリリース
diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml
index 4379a0d442..512d0a26c3 100644
--- a/translations/ja-JP/data/variables/product.yml
+++ b/translations/ja-JP/data/variables/product.yml
@@ -100,6 +100,8 @@ prodname_github_issues: 'GitHubのIssue'
 #GitHub Packages
 prodname_registry: 'GitHub Packages'
 prodname_container_registry: 'コンテナレジストリ'
+prodname_docker_registry_namespace: '{% ifversion fpt or ghec %}`docker.pkg.github.com`{% elsif ghes or ghae %}docker.HOSTNAME{% endif %}'
+prodname_container_registry_namespace: '{% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes or ghae %}containers.HOSTNAME{% endif %}'
 #GitHub Insights
 prodname_insights: 'GitHub Insights'
 #GitHub Sponsors
diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml
index ec65ef6f94..d39e7c0f8d 100644
--- a/translations/ja-JP/data/variables/release_candidate.yml
+++ b/translations/ja-JP/data/variables/release_candidate.yml
@@ -1,2 +1,2 @@
 ---
-version: ''
+version: enterprise-server@3.6
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 38ba73cf86..7fe44f1a7a 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -111,7 +111,6 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,broken liquid tags
-translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,broken liquid tags
@@ -281,10 +280,15 @@ translations/ja-JP/data/reusables/apps/user-to-server-rate-limits-ghec.md,broken
 translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags
 translations/ja-JP/data/reusables/billing/ghes-with-no-enterprise-account.md,broken liquid tags
 translations/ja-JP/data/reusables/classroom/classroom-codespaces-link.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/beta-alert-tracking-in-issues.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/upload-sarif-ghas.md,broken liquid tags
 translations/ja-JP/data/reusables/community/report-content.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/dotcom-settings.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/enabling-or-disabling-in-vsc.md,broken liquid tags
+translations/ja-JP/data/reusables/copilot/enabling-or-disabling-vs.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags
 translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liquid tags