New translation batch for ja (#31958)

2026-01-09 06:03:09 -05:00 · 2022-10-21 10:35:39 -07:00
parent fe1a667b9e
commit f348c211eb
9 changed files with 53 additions and 26 deletions
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -146,7 +146,7 @@ When you set your status, you can also let people know that you have limited ava

 If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."

-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 **Set your status** or, if you already have a status set, click your current status.
+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 **Set status** or, if you already have a status set, click your current status.
  ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png)
 2. To add custom text to your status, click in the text field and type a status message.
  ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png)
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
@@ -51,7 +51,7 @@ To ensure that commits are attributed to you and appear in your contributions gr

 {% note %}

-**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of <code>ID+USERNAME@users.noreply.github.com</code>. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is <code>USERNAME@users.noreply.github.com</code>. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is an ID number and your username in the form of <code>ID+USERNAME@users.noreply.github.com</code>. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is <code>USERNAME@users.noreply.github.com</code>. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.

 {% endnote %}

--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
@@ -105,7 +105,8 @@ To use a {% data variables.product.pat_generic %} or SSH key to access resources

 | Token type | Prefix | More information |
 | :- | :- | :- |
-| {% data variables.product.pat_generic_caps %} | `ghp_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" |
+| {% data variables.product.pat_v1_caps %} | `ghp_` | {% ifversion pat-v2 %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-personal-access-token-classic)"{% else %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)"{% endif %}  |{% ifversion pat-v2 %}
+| {% data variables.product.pat_v2_caps %} | `github_pat_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token)" |{% endif %}
 | OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" |
 | User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
 | Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" |
--- 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
@@ -87,7 +87,7 @@ To sign commits using GPG and have those commits verified on {% data variables.p
 {% ifversion ssh-commit-verification %}
 ## SSH commit signature verification

-You can use SSH to sign commits with an SSH public key that you generate yourself. If you already use an SSH key to authenticate with {% data variables.product.product_name %},
+You can use SSH to sign commits with an SSH key that you generate yourself. For more information, see the [Git reference documentation](https://git-scm.com/docs/git-config#Documentation/git-config.txt-usersigningKey)  for `user.Signingkey`. If you already use an SSH key to authenticate with {% data variables.product.product_name %},
 you can also upload that same key again for use as a signing key. There's no limit on the number of signing keys you can add to your account.

 {% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -1,6 +1,6 @@
 ---
-title: SSH キーのパスフレーズのリカバリ
-intro: SSH キーのパスフレーズをなくした場合、ご使用のオペレーティングシステムによって、リカバリができることもあれば、SSH キーのパスフレーズを新たに生成することが必要なこともあります。
+title: Recovering your SSH key passphrase
+intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
 redirect_from:
  - /articles/how-do-i-recover-my-passphrase
  - /articles/how-do-i-recover-my-ssh-key-passphrase
@@ -15,36 +15,30 @@ versions:
 topics:
  - SSH
 shortTitle: Recover SSH key passphrase
-ms.openlocfilehash: 28d768e81f3076898c23b2b1668314ae5573ec5c
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145088163'
 ---
 {% mac %}

-[macOS キーチェーンを使用して SSH パスフレーズを構成](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)した場合は、リカバリできる場合があります。
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.

-1. Finder で、**キーチェーン アクセス** アプリを検索します。
-   ![スポットライト検索バー](/assets/images/help/setup/keychain-access.png)
-2. キーチェーン アクセスで、**SSH** を検索します。
-3. SSH キーのエントリをダブルクリックして、新しいダイアログボックスを開きます。
-4. 左下隅で、 **[パスワードを表示]** を選択します。
-   ![キーチェーン アクセス ダイアログ](/assets/images/help/setup/keychain_show_password_dialog.png)
-5. 管理者パスワードを入力するようプロンプトが表示されます。 [Keychain Access] ダイアログボックスに入力します。
-6. パスワードのマスクが解除されます。
+1. In Finder, search for the **Keychain Access** app.
+   ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
+2. In Keychain Access, search for **SSH**.
+3. Double click on the entry for your SSH key to open a new dialog box.
+4. In the lower-left corner, select **Show password**.
+   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
+6. Your password will be revealed.

 {% endmac %}

 {% windows %}

-SSH キーパスフレーズをなくした場合、リカバリの方法はありません。 代わりに GitHub パスワードを使用できるように、[新しい SSH キーペアを生成](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)するか、[HTTPS 複製に切り替える](/github/getting-started-with-github/managing-remote-repositories)必要があります。
+If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.

 {% endwindows %}

 {% linux %}

-SSH キーパスフレーズをなくした場合、リカバリの方法はありません。 代わりに GitHub パスワードを使用できるように、[新しい SSH キーペアを生成](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)するか、[HTTPS 複製に切り替える](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)必要があります。
+If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.

 {% endlinux %}
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -26,8 +26,20 @@ $ ssh -T -p 443 git@ssh.github.com
 > provide shell access.
 ```

+{% note %}
+
+**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
+
+{% endnote %} 
+
 If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).

+Now, to clone the repository, you can run the following command:
+
+```
+$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
+```
+
 ## Enabling SSH connections over HTTPS

 If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
@@ -48,3 +60,19 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > Hi USERNAME! You've successfully authenticated, but GitHub does not
 > provide shell access.
 ```
+
+## Updating known hosts
+
+The first time you interact with GitHub after switching to port 443, you may get a warning message
+that the host wasn't found in `known_hosts`, or that it was found by another name.
+
+```ShellSession
+> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
+> ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
+> This host key is known by the following other names/addresses:
+>     ~/.ssh/known_hosts:32: github.com
+> Are you sure you want to continue connecting (yes/no/[fingerprint])? 
+```
+
+It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches
+one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
--- a/translations/ja-JP/content/get-started/using-github/troubleshooting-connectivity-problems.md
+++ b/translations/ja-JP/content/get-started/using-github/troubleshooting-connectivity-problems.md
@@ -32,6 +32,8 @@ If you're unable to verify with the captcha:

 Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve connectivity. For more information, see "[Troubleshooting cloning errors](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)."

+If you prefer to use SSH but the port is blocked, you can use an alternative port. For more information, see "[Using SSH over the HTTPS port](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port)".
+
 If you're encountering timeouts with SSH, see "[Error: Bad file number](/articles/error-bad-file-number)."

 ## Troubleshooting slow downloads and intermittent slow connections
--- 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
@@ -14,6 +14,7 @@ children:
  - /managing-the-forking-policy-for-your-repository
  - /managing-pull-request-reviews-in-your-repository
  - /managing-the-commit-signoff-policy-for-your-repository
+  - /managing-the-push-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
--- a/translations/log/msft-ja-resets.csv
+++ b/translations/log/msft-ja-resets.csv
@@ -544,6 +544,7 @@ translations/ja-JP/content/authentication/securing-your-account-with-two-factor-
 translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
 translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
 translations/ja-JP/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
+translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
 translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
@@ -605,8 +606,8 @@ translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.m
 translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
 translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
-translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,broken liquid tags
-translations/ja-JP/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,broken liquid tags
+translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error
+translations/ja-JP/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
 translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md,rendering error
 translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
 translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
@@ -1027,7 +1028,7 @@ translations/ja-JP/data/reusables/dependabot/default-dependencies-allow-ignore.m
 translations/ja-JP/data/reusables/dependabot/dependabot-alerts-filters.md,rendering error
 translations/ja-JP/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
 translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md,rendering error
-translations/ja-JP/data/reusables/dependabot/supported-package-managers.md,broken liquid tags
+translations/ja-JP/data/reusables/dependabot/supported-package-managers.md,rendering error
 translations/ja-JP/data/reusables/desktop/get-an-account.md,rendering error
 translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
 translations/ja-JP/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags