New translation batch for ja (#33238)

Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com>

translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md

@@ -14,7 +14,7 @@ shortTitle: Server Statistics
 
 {% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.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 %}. 
 
-{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
 
 By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
 

translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md

@@ -25,7 +25,7 @@ By default, authorized users can access your enterprise from any IP address. You
 
 {% ifversion ghec %}
 
-If your enterprise uses {% data variables.product.prodname_emus %} with OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with OIDC, you can use {% data variables.product.company_short %}'s allow list feature. 
+If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature. 
 
 {% elsif ghae %}
 
@@ -47,7 +47,7 @@ You can use {% data variables.product.company_short %}'s IP allow list to contro
 
 ## About your IdP's allow list
 
-If you are using {% data variables.product.prodname_emus %} with OIDC, you can use your IdP's allow list. 
+If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
 
 Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists. 
 
@@ -124,7 +124,11 @@ To ensure seamless use of the OIDC CAP while still applying the policy to user-t
 
 ## Using your identity provider's allow list
 
-You can use your IdP's allow list if you use {% data variables.product.prodname_emus %} with OIDC.
+{% note %}
+
+**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC. 
+
+{% endnote %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}

translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md

@@ -1,6 +1,6 @@
 ---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: GitHub の SSH キーフィンガープリント
+intro: パブリックキーフィンガープリントを使用して、リモートサーバへの接続を有効にすることができます。
 redirect_from:
   - /articles/what-are-github-s-ssh-key-fingerprints
   - /articles/github-s-ssh-key-fingerprints
@@ -14,15 +14,21 @@ topics:
   - Identity
   - Access management
 shortTitle: SSH key fingerprints
+ms.openlocfilehash: 153c1b4ac8be917cf111fe8998ac8df8bd1bc7ed
+ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190331'
 ---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+{% data variables.product.prodname_dotcom %} の公開鍵のフィンガープリントは次のとおりです。
 
 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
-- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
+- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - 非推奨)
 - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
 - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
 
-You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
+`~.ssh/known_hosts` ファイルに次の ssh キー エントリを追加して、{% data variables.product.prodname_dotcom %} ホストの手動による検証を回避できます。
 
 ```text
 github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
@@ -30,4 +36,4 @@ github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAA
 github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
 ```
 
-For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."
+詳しくは、「[{% data variables.product.prodname_dotcom %} のメタ情報を取得する](/rest/meta#get-github-meta-information)」をご覧ください。

translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md

@@ -1,6 +1,6 @@
 ---
-title: Using SSH over the HTTPS port
-intro: 'Sometimes, firewalls refuse to allow SSH connections entirely.  If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port.  Most firewall rules should allow this, but proxy servers may interfere.'
+title: HTTPS ポートを介して SSH を使用する
+intro: '時々、ファイアウォールは SSH 接続を完全に許可することを拒否します。  [認証情報キャッシュを使用した HTTPS クローニング](/github/getting-started-with-github/caching-your-github-credentials-in-git) を使用することが選べない場合は、HTTPS ポート経由の SSH 接続を使用してクローンの作成を試みることができます。  ほとんどのファイアウォールルールでこれを許可する必要がありますが、プロキシサーバーが干渉する可能性があります。'
 redirect_from:
   - /articles/using-ssh-over-the-https-port
   - /github/authenticating-to-github/using-ssh-over-the-https-port
@@ -11,14 +11,20 @@ versions:
 topics:
   - SSH
 shortTitle: Use SSH over HTTPS port
+ms.openlocfilehash: 24a56147129e68c674eaf8dc733a203e2b03348a
+ms.sourcegitcommit: 8c8d8598beeaa4f83b3f30cb160a5288fdb4ef9a
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 12/02/2022
+ms.locfileid: '148190323'
 ---
 {% tip %}
 
-**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
+**{% data variables.product.prodname_ghe_server %} ユーザー**: HTTPS ポートを介した SSH 経由での {% data variables.product.prodname_ghe_server %} へのアクセスは現在サポートされていません。
 
 {% endtip %}
 
-To test if SSH over the HTTPS port is possible, run this SSH command:
+HTTPS ポート経由の SSH が可能かどうかをテストするには、次の SSH コマンドを実行します:
 
 ```shell
 $ ssh -T -p 443 git@ssh.github.com
@@ -28,23 +34,23 @@ $ ssh -T -p 443 git@ssh.github.com
 
 {% note %}
 
-**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
+**注**: ポート 443 のホスト名は、`{% data variables.command_line.backticks %}` ではなく `ssh.{% 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).
+うまく機能すれば、素晴らしいことです。 そうでない場合は、[トラブルシューティング ガイドに従って](/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
+## HTTPS を介した SSH 接続を有効化する
 
-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.
+ポート 443 経由で `git@ssh.{% data variables.command_line.backticks %}` に SSH 接続できる場合は、SSH の設定をオーバーライドして、{% data variables.location.product_location %} への接続をそのサーバーとポートを通して実行するように強制できます。
 
-To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
+SSH 構成ファイルでこれを設定するには、`~/.ssh/config` でファイルを編集し、次のセクションを追加します。
 
 ```
 Host {% data variables.command_line.codeblock %}
@@ -53,7 +59,7 @@ Port 443
 User git
 ```
 
-You can test that this works by connecting once more to {% data variables.location.product_location %}:
+{% data variables.location.product_location %} にもう一度接続することで、これが機能することをテストできます。
 
 ```shell
 $ ssh -T git@{% data variables.command_line.codeblock %}
@@ -61,10 +67,9 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
 > 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.
+ポート 443 に切り替えた後で GitHub を初めて使うときに、`known_hosts` でホストが見つからなかったか、別の名前で見つかったことを示す警告メッセージが、表示されることがあります。
 
 ```ShellSession
 > The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
@@ -74,5 +79,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
 > 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 the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
+SSH のフィンガープリントが公開されている GitHub のフィンガープリントのいずれかと一致するなら、この質問に "はい" と答えても安全です。 フィンガープリントの一覧については、「[GitHub の SSH キーフィンガープリント](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)」をご覧ください。

translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md

@@ -16,9 +16,11 @@ topics:
 
 ## About forking
 
-After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
+If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow. 
 
-Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+{% data reusables.repositories.fork-definition-long %}
+
+You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
 
 ## Forking a repository
 
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
    ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
+4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further. 
    ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
 5. Optionally, add a description of your fork.
    ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 
 {% note %}
 
-**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. 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)."
+**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. 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)."
 
 {% endnote %}
 {% endif %}
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
 
 ## Managing feedback
 
-Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
+Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
 
 ## Finding projects
 

translations/ja-JP/content/get-started/quickstart/fork-a-repo.md

@@ -6,7 +6,7 @@ redirect_from:
   - /articles/fork-a-repo
   - /github/getting-started-with-github/fork-a-repo
   - /github/getting-started-with-github/quickstart/fork-a-repo
-intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
+intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
 permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
 versions:
   fpt: '*'
@@ -21,7 +21,7 @@ topics:
 ---
 ## About forks
 
-Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
+{% data reusables.repositories.fork-definition-long %}  For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
 
 ### Propose changes to someone else's project
 
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
 
 ## Prerequisites
 
-If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
+If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
 
 ## Forking a repository
 
 {% webui %}
 
-You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
+You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 2. In the top-right corner of the page, click **Fork**.
    ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
+4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further. 
    ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
 5. Optionally, add a description of your fork.
    ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 {% note %}
 
-**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. 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)."{% endnote %}{% endif %}
+**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. 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)."{% endnote %}{% endif %}
 
 {% endwebui %}
 
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
 
 {% enddesktop %}
 
-## Configuring Git to sync your fork with the original repository
+## Configuring Git to sync your fork with the upstream repository
 
-When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
+When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
 
 {% webui %}
 
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
   $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
   ```
 
-7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
+7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
   ```shell
   $ git remote -v
   > origin    https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
 You can make any changes to a fork, including:
 
 - **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
-- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
 
 ## Find another repository to fork
 Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}

translations/ja-JP/content/rest/overview/libraries.md

@@ -11,12 +11,12 @@ versions:
   ghec: '*'
 topics:
   - API
-ms.openlocfilehash: 4560ae5e63f8a607f068bb24e84f1a014f44885c
-ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
+ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
+ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 11/21/2022
-ms.locfileid: '148179737'
+ms.lasthandoff: 12/01/2022
+ms.locfileid: '148190062'
 ---
 ![Gundamcat](/assets/images/gundamcat.png)
 
@@ -24,7 +24,6 @@ ms.locfileid: '148179737'
 
 公式の Octokit ライブラリを使用するか、利用可能なサードパーティライブラリのいずれかを選択します。
 
-- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
 - **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
 - **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
 - **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
@@ -131,6 +130,7 @@ ms.locfileid: '148179737'
 |**github-flask**|[github-flask (公式 Web サイト)](http://github-flask.readthedocs.org)|
 |**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
 |**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
+|**octokit.py**|[khornberg/octokit.py](https://github.com/khornberg/octokit.py)|
 
 ### Ruby
 

translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md

@@ -1 +1 @@
-{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
+{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise. {% data variables.enterprise.prodname_managed_users_caps %} can fork private or internal repositories owned by organizations in the enterprise into their user account namespace or other organizations owned by the enterprise, as specified by enterprise policy.

translations/log/msft-ja-resets.csv

@@ -664,7 +664,6 @@ translations/ja-JP/content/authentication/connecting-to-github-with-ssh/testing-
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
 translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
@@ -684,7 +683,6 @@ translations/ja-JP/content/authentication/securing-your-account-with-two-factor-
 translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
 translations/ja-JP/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
 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,rendering error
 translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
 translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error