Merge pull request #21356 from github/repo-sync

repo sync

content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md

@@ -749,7 +749,9 @@ Key | Type | Description
 `merge_group`|`object` | The merge group.
 `merge_group[head_sha]`|`string` | The SHA of the merge group.
 `merge_group[head_ref]`|`string` | The full ref of the merge group.
+`merge_group[base_sha]`|`string` | The SHA of the merge group's parent commit.
 `merge_group[base_ref]`|`string` | The full ref of the branch the merge group will be merged into.
+`merge_group[head_commit]`|`object` | An expanded representation of the `head_sha` commit.
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}

lib/webhooks/static/dotcom/merge_group.checks_requested.payload.json

@@ -3,7 +3,22 @@
   "merge_group": {
     "head_sha": "2ffea6db159f6b6c47a24e778fb9ef40cf6b1c7d",
     "head_ref": "refs/heads/gh-readonly-queue/main/pr-104-929f8209d40f77f4abc622a499c93a83babdbe64",
-    "base_ref": "refs/heads/main"
+    "base_sha": "380387fbc80638b734a49e1be1c4dfec1c01b33c",
+    "base_ref": "refs/heads/main",
+    "head_commit": {
+      "id": "ec26c3e57ca3a959ca5aad62de7213c562f8c821",
+      "tree_id": "31b122c26a97cf9af023e9ddab94a82c6e77b0ea",
+      "message": "Merge pull request #2048 from octo-repo/update-readme\n\nUpdate README.md",
+      "timestamp": "2019-05-15T15:20:30Z",
+      "author": {
+        "name": "Codertocat",
+        "email": "21031067+Codertocat@users.noreply.github.com"
+      },
+      "committer": {
+        "name": "Codertocat",
+        "email": "21031067+Codertocat@users.noreply.github.com"
+      }
+    }
   },
   "repository": {
     "id": 17273051,
@@ -137,4 +152,4 @@
     "id": 1,
     "node_id": "MDEyOk9yZ2FuaXphdGlvbjY4MTE2NzI="
   }
-}
+}

translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md

@@ -1,5 +1,5 @@
 ---
-title: ユーザを Organization に変換する
+title: Converting a user into an organization
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
@@ -8,7 +8,7 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
-intro: 個人アカウントを Organization に変換できます。 これにより、Organization に属するリポジトリに対して、より細かく権限を設定できます。
+intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,60 +17,58 @@ versions:
 topics:
   - Accounts
 shortTitle: User into an organization
-ms.openlocfilehash: 8b99bd119a9fa061c025a4fcc299d7ace31d23eb
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147687128'
 ---
 {% warning %}
 
-**警告**: ユーザーを Organization に変換する前に、以下の点にご注意ください。
+**Warning**: Before converting a user into an organization, keep these points in mind.
 
-* 変換した個人アカウントには、サインイン **できなくなります**。
-* 変換した個人アカウントが所有していた gist を作成や変更することが **できなくなります**。
-* Organization からユーザーに変換 **することはできません**。
-* SSH キー、OAuth トークン、ジョブ プロフィール、リアクション、関連するユーザー情報は、Organization に移譲 **されません**。 これは、変換された個人アカウントのみに該当し、個人アカウントのコラボレーターには該当しません。
-* 変換した個人アカウントによるコミットは、アカウントに **リンクされなくなります**。 コミット自体はそのまま **残ります**。
-* 変換した個人アカウントによるあらゆる既存のコメントは、アカウントに **リンクされなくなります**。 コメント自体はそのまま **残ります** が、`ghost` ユーザーに関連付けられます。
-* 変換された個人アカウントで作成されたプライベート リポジトリのフォークはすべて削除されます。
+* You will **no longer** be able to sign into the converted personal account.
+* You will **no longer** be able to create or modify gists owned by the converted personal account.
+* An organization **cannot** be converted back to a user.
+* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
+* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
+* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
+* Any forks of private repositories made with the converted personal account will be deleted.
 {% endwarning %}
 
 {% ifversion fpt or ghec or ghes %}
-## 個人アカウントを保ち、新しい組織を手動で作成する
+## Keep your personal account and create a new organization manually
 
-組織の名前を、個人アカウントが使用しているものと同じにしたい場合や、個人のアカウント情報をそのまま残しておきたい場合は、個人アカウントを組織に変換するのではなく、新しい組織を作成して、そこへリポジトリを移譲する必要があります。
+If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
 
-1. 現在の個人アカウント名を個人的に使いたい場合は、[個人アカウント名を変更し](/articles/changing-your-github-username)、新しくて素敵な名前を付けましょう。
-2. 個人アカウントの元の名前で[新しい組織を作成](/articles/creating-a-new-organization-from-scratch)します。
-3. 新しい Organization アカウントに[リポジトリを転送します](/articles/transferring-a-repository)。{% endif %}
+1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
+2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
+3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
 
-## 個人アカウントを Organization に自動で変換する
+## Convert your personal account into an organization automatically
 
-個人アカウントを組織に直接変換することも可能です。 アカウントを変換すると、以下のことが起こります:
- - リポジトリはそのまま保持されます。他のアカウントに手動で移譲する必要はありません。
- - コラボレーターを、Team に自動的に招待します。コラボレーターの権限は、以前のものがそのまま引き継がれます。{% ifversion fpt or ghec %}- {% data variables.product.prodname_pro %} の個人アカウントでは、いつでも支払い情報の再入力、支払いサイクルの調整、二重支払いをすることなく、自動的に[有料 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) に移行できます。{% endif %}
+You can also convert your personal account directly into an organization. Converting your account:
+ - Preserves the repositories as they are without the need to transfer them to another account manually
+ - Automatically invites collaborators to teams with permissions equivalent to what they had before
+ {% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
 
-1. GitHub にサインインし、変換後に Organization やリポジトリにアクセスするために使う、新しい個人アカウントを作成します。
-2.  変換する個人アカウントが参加している[組織は、そのままにしておきます](/articles/removing-yourself-from-an-organization)。
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
-5. [アカウントの変換] で、 **[<username> を組織に変換]** をクリックします。
-    ![Organization 変換ボタン](/assets/images/help/settings/convert-to-organization.png)
-6. [Account Transformation Warning] ダイアログボックスで、変換に関する情報を読み、変換を確定します。 このボックスに記載されている情報は、この記事で上述したものと同じです。
-    ![変換に関する警告](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. [Transform your user into an organization] ページの、[Choose an organization owner] で、前のセクションで作成したセカンダリの個人アカウントか、Organization の管理を信頼して任せられる他のユーザを選択します。
-    ![Organization オーナーの追加ページ](/assets/images/help/organizations/organization-add-owner.png)
-8. 入力を求められた場合、Organization の新しいプランを選択し、支払い情報を入力します。
-9. **[Organization の作成]** をクリックします。
-10. ステップ 1 で作成した、新しい個人アカウントにサインインし、コンテキスト スイッチャーを使って新しい組織にアクセスします。
+1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
+2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+5. Under "Transform account", click **Turn <username> into an organization**.
+ 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
+6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
+ 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
+ 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
+8. Choose your new organization's subscription and enter your billing information if prompted.
+9. Click **Create Organization**.
+10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
 
 {% tip %}
 
-**ヒント**: ユーザー アカウントを組織に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい組織に *外部コラボレーター* として追加されます。 希望する場合は、*外部コラボレーター* を招待して新しい Organization のメンバーにすることができます。 詳細については、「[Organization のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)」を参照してください。
+**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% endtip %}
 
-## 参考資料
-- 「[Team の設定](/articles/setting-up-teams)」 {% ifversion fpt or ghec %}- [Organization にユーザーを招待する](/articles/inviting-users-to-join-your-organization){% endif %}
-- [Organization へのアクセス](/articles/accessing-an-organization)
+## Further reading
+- "[Setting up teams](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Accessing an organization](/articles/accessing-an-organization)"

translations/ja-JP/content/actions/learn-github-actions/contexts.md

@@ -791,7 +791,7 @@ jobs:
 {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 ## `inputs` context
 
-The `inputs` context contains input properties passed to a reusable workflow{% ifversion actions-unified-inputs %} or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
+The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
 
 There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
 

translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md

@@ -1,50 +1,65 @@
 ---
-title: ワークフローの無効化と有効化
-intro: '{% data variables.product.prodname_dotcom %} UI、REST API、または {% data variables.product.prodname_cli %} を使用して、ワークフローを無効化したり再度有効化したりすることができます。'
+title: Disabling and enabling a workflow
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Disable & enable a workflow
-ms.openlocfilehash: 1c0ebc0f56ba8c337648670e0f07d8a56e2fc326
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145125949'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-ワークフローを一時的に無効にすると、多くのシナリオで役立つことがあります。 以下は、ワークフローを無効すると便利な場合の例の一部です。
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
-- リクエストが多すぎるまたは間違っていて、外部サービスに悪影響を与えるワークフローエラー。
-- 重要ではないが、アカウントの時間を消費しすぎるワークフロー。
-- ダウンしているサービスにリクエストを送信するワークフロー。
-- フォークされたリポジトリ上の不要なワークフロー（スケジュールされたワークフローなど）。
+Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+
+- A workflow error that produces too many or wrong requests, impacting external services negatively.
+- A workflow that is not critical and is consuming too many minutes on your account.
+- A workflow that sends requests to a service that is down.
+- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
 
 {% warning %}
 
-**警告:** {% data reusables.actions.scheduled-workflows-disabled %}
+**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しくは、[Actions REST API](/rest/reference/actions#workflows) に関する記事をご覧ください。
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
 
-## ワークフローの無効化
+## Disabling a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 左サイドバーで、無効にするワークフローをクリックします。
-![アクション選択ワークフロー](/assets/images/actions-select-workflow.png)
-1. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。
-![アクション ケバブ メニュー](/assets/images/help/repository/actions-workflow-menu-kebab.png)
-1. **[Disable workflow]\(ワークフローを無効にする\)** をクリックします。
-![アクション無効ワークフロー](/assets/images/help/repository/actions-disable-workflow.png) 無効なワークフローは、その状態を示す {% octicon "stop" aria-label="The stop icon" %} でマークされます。
-![無効なワークフローをリストするアクション](/assets/images/help/repository/actions-find-disabled-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to disable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab-2022.png)
+   {%- else -%}
+   ![Actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
+   {%- endif %}
+1. Click **Disable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow-2022.png)
+   {%- else -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)
+
+   The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
+
+   ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
@@ -52,34 +67,45 @@ REST API を使用して、ワークフローを無効化または有効化す
 
 {% data reusables.cli.cli-learn-more %}
 
-ワークフローを無効にするには、`workflow disable` サブコマンドを使います。 `workflow` を、無効にするワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow disable <em>workflow</em>
+gh workflow disable WORKFLOW
 ```
 
 {% endcli %}
 
-## ワークフローの有効化
+## Enabling a workflow
 
 {% webui %}
 
-以前、無効化したワークフローを再度有効化することができます。
+You can re-enable a workflow that was previously disabled.
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 左サイドバーで、有効にするワークフローをクリックします。
-![無効なワークフローを選択するアクション](/assets/images/help/repository/actions-select-disabled-workflow.png)
-1. **[Enable workflow]\(ワークフローを有効にする\)** をクリックします。
-![ワークフローを有効にするアクション](/assets/images/help/repository/actions-enable-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to enable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow-2022.png)
+   {%- else -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
+   {%- endif %}
+1. Click **Enable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow-2022.png)
+   {%- else -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
 {% cli %}
 
-ワークフローを有効にするには、`workflow enable` サブコマンドを使います。 `workflow` を、有効にするワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow enable <em>workflow</em>
+gh workflow enable WORKFLOW
 ```
 
 {% endcli %}

translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md

@@ -1,38 +1,40 @@
 ---
-title: ワークフローの手動実行
-intro: 'ワークフローが `workflow_dispatch` イベントで実行されるように設定されている場合、{% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %}、または REST API の [Actions]\(アクション\) タブを使用してワークフローを実行できます。'
+title: Manually running a workflow
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Manually run a workflow
-ms.openlocfilehash: 22717c31a6bc2599f066b0e870f0aa652c18cc6f
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145117181'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## ワークフローを手動実行する設定
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-ワークフローを手動で実行するには、`workflow_dispatch` イベントで実行するようにワークフローを設定する必要があります。 `workflow_dispatch` イベントをトリガーするには、ワークフローが既定のブランチに存在する必要があります。 `workflow_dispatch` イベントの構成の詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
+## Configuring a workflow to run manually
+
+To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## ワークフローの実行
+## Running a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 左のサイドバーで、実行したいワークフローをクリックしてください。
-![アクション選択ワークフロー](/assets/images/actions-select-workflow.png)
-1. ワークフロー実行の一覧の上にある **[ワークフローの実行]** を選択します。
-![アクション ワークフローのディスパッチ](/assets/images/actions-workflow-dispatch.png)
-1. **[分岐]** ドロップダウンを使用してワークフローのブランチを選択し、入力パラメーターを入力します。 **[ワークフローの実行]** をクリックします。
-![ワークフローを手動で実行するアクション](/assets/images/actions-manually-run-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to run.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Above the list of workflow runs, select **Run workflow**.
+![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
+1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
+![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -40,31 +42,31 @@ ms.locfileid: '145117181'
 
 {% data reusables.cli.cli-learn-more %}
 
-ワークフローを実行するには、`workflow run` サブコマンドを使用します。 `workflow` パラメーターを、実行するワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow run <em>workflow</em>
+gh workflow run WORKFLOW
 ```
 
-ワークフローに入力可能な場合、{% data variables.product.prodname_cli %} は入力を求めるプロンプトを表示します。 または、`-f` または `-F` を使用して `key=value` 形式の入力を追加できます。 `-F` を使用してファイルから読み取ります。
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
 
 ```shell
 gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
 ```
 
-標準入力を使用して、入力を JSON として渡すこともできます。
+You can also pass inputs as JSON by using standard input.
 
 ```shell
 echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
 ```
 
-リポジトリの既定のブランチ以外のブランチでワークフローを実行するには、`--ref` フラグを使用します。
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
 
 ```shell
-gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+gh workflow run WORKFLOW --ref BRANCH
 ```
 
-ワークフロー実行の進行状況を表示するには、`run watch` サブコマンドを使用して、インタラクティブ リストから実行を選択します。
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
 
 ```shell
 gh run watch
@@ -72,14 +74,14 @@ gh run watch
 
 {% endcli %}
 
-## REST API を使用してワークフローを実行する
+## Running a workflow using the REST API
 
-REST API を使用する場合は、要求本文パラメーターとして `inputs` と `ref` を構成します。 入力を省略すると、ワークフロー ファイルで定義されているデフォルト値が使用されます。
+When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
 
 {% note %}
 
-**注:** 1 つの `workflow_dispatch` イベントに対して最大 10 個の `inputs` を定義できます。
+**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event.
 
 {% endnote %}
 
-REST API の使用の詳細については、「[ワークフロー ディスパッチ イベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」を参照してください。
+For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."

translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md

@@ -28,16 +28,18 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-{% ifversion fpt or ghes > 3.4 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.4 or ghae or ghec -%}
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run all jobs**.
+
+   If no jobs failed, you will not see the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+{%- endif %}
+{% ifversion ghes < 3.5 or ghae -%}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
 
-   If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
-{% endif %}
-{% ifversion ghes < 3.5 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
-{% endif %}
+   ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+{%- endif %}
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
@@ -80,8 +82,9 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
-    ![Re-run failed jobs drop-down menu](/assets/images/help/repository/rerun-failed-jobs-drop-down.png)
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}

translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md

@@ -1,29 +1,29 @@
 ---
-title: ジョブの実行時間を表示する
-intro: ジョブの実行時間 (ジョブの発生した支払対象の分を含む) を表示できます。
+title: Viewing job execution time
+shortTitle: View job execution time
+intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
-ms.openlocfilehash: 8293c36519dd727942d7cec0e1c1a2fa430ce112
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145121221'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-請求可能なジョブ実行時間 (分) は、{% data variables.product.prodname_dotcom %} ホストランナーを使用するプライベートリポジトリで実行されるジョブに対してのみ表示され、次の分に切り上げられます。 パブリックリポジトリで {% data variables.product.prodname_actions %} を使用する場合、またはセルフホストランナーで実行されるジョブの場合、請求対象となる実行時間はありません。
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
-1. ジョブの概要の下で、ジョブの実行時間を表示できます。 請求可能なジョブの実行時間に関する詳細を表示するには、 **[請求可能な時間]** の下の時間をクリックしてください。
-   ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png)
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
+
+   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
-   **注:** 表示された課金対象時間には分乗数は含まれません。 分乗数を含む、{% data variables.product.prodname_actions %} 使用状況の合計を表示するには、「[{% data variables.product.prodname_actions %} 使用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)」を参照してください。
-   
+
+   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
+
    {% endnote %}

translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md

@@ -61,7 +61,7 @@ If you use {% data variables.product.prodname_codeql %} {% data variables.produc
 {% ifversion ghes %}
 If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
 
-The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If both {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} and your {% data variables.product.prodname_actions %} runner have access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
 
 You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
 

translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md

@@ -41,6 +41,10 @@ You can make extra features for code security available to users by buying and u
 
 {% data reusables.advanced-security.license-overview %}
 
+{% ifversion ghes %}
+You can determine how many licenses you'll need for {% data variables.product.prodname_GH_advanced_security %} by generating a count of your instance's active committers in the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+{% endif %}
+
 To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
 
 ## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}

translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md

@@ -1,6 +1,6 @@
 ---
-title: ユーザごとの価格付けについて
-intro: '{% ifversion fpt or ghec %}Organization{% ifversion ghec %} と Enterprise{% endif %} の場合、{% else %}{% endif %}課金はお客様が選んだライセンス シートの数から始まります。'
+title: About per-user pricing
+intro: '{% ifversion fpt or ghec %}For organizations{% ifversion ghec %} and enterprises{% endif %}, your {% else %}Your {% endif %}bill begins with the number of licensed seats you choose.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
   - /articles/about-per-user-pricing
@@ -15,109 +15,138 @@ topics:
   - Enterprise
   - Licensing
   - Organizations
-ms.openlocfilehash: 037e0e0cfbb04552a370cf8fd0f3e05c2e09423f
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145910839'
 ---
-## ユーザごとの価格付けについて
 
-{% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %} 上の新しい Organization は、{% data variables.product.prodname_free_team %} でパブリックのオープンソース プロジェクトを構築するか、ユーザーごとに料金がかかる有料製品にアップグレードすることができます。 詳細については、「[{% data variables.product.company_short %} の製品](/get-started/learning-about-github/githubs-products)」および「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
+## About per-user pricing
 
-2016 年 5 月 11 日以前に有料プランを使っていた Organization は、既存のリポジトリ単位のプランに留まるか、ユーザごとの価格付けに切り替えることができます。 {% data variables.product.company_short %}は、プランへの強制的な変更の前に12ヶ月間通知します。 サブスクリプションの切り替えに関する詳細については、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
+{% ifversion fpt %}
+
+New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
+
+Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
 
 {% else %}
 
-課金の基になるのは、お客様が{% ifversion ghec %} Organization または{% endif %} Enterprise に対して選んだ標準ライセンス シートの数です。
+The foundation of your bill is the number of standard licensed seats that you choose for your{% ifversion ghec %} organization or{% endif %} enterprise.
 
 {% data reusables.enterprise-licensing.unique-user-licensing-model %}
 
-同じユーザーが複数の Enterprise デプロイで複数のライセンスを使わないようにするには、{% data variables.product.prodname_ghe_server %} 環境と {% data variables.product.prodname_ghe_cloud %} 環境の間でライセンスの使用状況を同期できます。 詳しくは、「[GitHub Enterprise のライセンスについて](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)」をご覧ください。
+To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. For more information, see "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
 
-ライセンス シートに加えて、課金には {% data variables.product.prodname_GH_advanced_security %} などの他の料金が含まれる場合があります。 詳しくは、「[Enterprise の支払いについて](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)」をご覧ください。
+In addition to licensed seats, your bill may include other charges, such as {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
 {% endif %}
 
-## ライセンスを使用するユーザー
+## People that consume a license
 
-各ユーザーは 1 つのライセンスを使い、{% data variables.product.company_short %} はプライマリ メール アドレスによって個人を識別します。
+{% ifversion fpt %}
 
-{% data variables.product.company_short %} は、次のユーザーに課金します。
+{% data variables.product.company_short %} bills for the following people:
 
-{%- ifversion ghec %}
-- エンタープライズ内の少なくとも 1 つの組織のメンバーまたは所有者である Enterprise 所有者 {%- endif %}
-- 所有者を含む組織のメンバー
-- フォークを除く、組織が所有するプライベート{% ifversion ghec %}または内部{% endif %}のリポジトリでの外部コラボレーター
-- 組織の所有者かメンバーになるための保留中の招待があるユーザー
-- フォークを除く、組織が所有するプライベート{% ifversion ghec %}または内部{% endif %}のリポジトリで、外部コラボレーターになるための保留中の招待があるユーザー{%- ifversion ghec %}
-- デプロイした {% data variables.product.prodname_ghe_server %} インスタンス上の各ユーザー{%- endif %}
-- 休眠ユーザ
-
-{% data variables.product.company_short %} は、次のどのユーザーに対しても課金しません。
-
-{%- ifversion ghec %}
-- エンタープライズ内の少なくとも 1 つの組織のメンバーまたは所有者でない Enterprise 所有者
-- Enterprise 課金マネージャー{%- endif %}
-- {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %} 上の個々の{% endif %}組織の課金マネージャー
-- {% ifversion ghec %}エンタープライズまたは{% endif %}組織の課金マネージャーになるための保留中の招待があるユーザー
-- Organization が所有するパブリック リポジトリの外部コラボレーターになるための保留中の招待があるユーザー {%- ifversion ghes %}
-- 停止されたユーザー {%- endif %}
+- Organization members, including owners
+- Outside collaborators on private repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
 
 {% note %}
 
-**注**: {% data reusables.organizations.org-invite-scim %}
+**Notes:** 
+- {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
+- {% data reusables.organizations.org-invite-scim %}
 
 {% endnote %}
 
-詳しくは、{% ifversion not fpt %}「[Enterprise でのロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」または{% endif %}「[Organization でのロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」をご覧ください。
+{% data variables.product.company_short %} does not bill for the following people:
 
-ユーザー アカウントが {% ifversion not fpt %}Enterprise 内の複数の Organization のメンバーになっているか、または {% endif %}Organization によって所有される複数のリポジトリにアクセスできる場合であっても、{% data variables.product.company_short %} では、各{% ifversion not fpt %}メンバーまたは{% endif %}外部コラボレーターが課金のためにカウントされるのは 1 回だけです。 外部コラボレーターの詳細については、「[外部のコラボレータを Organization のリポジトリに追加する](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)」を参照してください。
-
-{% ifversion ghes %}停止されているユーザーは、シートを使用しているライセンス ユーザーの数を計算するときにカウントされません。 詳しくは、「[ユーザーの一時停止と一時停止解除](/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users)」をご覧ください。{% endif %}
-
-休眠ユーザーは、シート ライセンスを占有します。{% ifversion ghes %}そのため、休眠ユーザーを停止してユーザー ライセンスを解放することができます。{% endif %}詳しくは、「[休眠ユーザーの管理](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)」をご覧ください。
-
-## プランの変更について
-
-{% ifversion fpt %}
-
-{% data variables.product.prodname_dotcom %}プランは、いつでも変更できます。
-
-### ユーザごとのプランのOrganizationでの変更について
-
-{% endif %}
-
-いつでも、{% ifversion fpt or ghec %}Organization{% endif %}{% ifversion ghec %} または {% endif %}{% ifversion ghec or ghes %}Enterprise{% endif %} にライセンス シートを追加できます。 使われている数より多くのシートに支払っている場合は、シートの数を減らすこともできます。{% ifversion fpt %}詳しくは、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」と「[{% data variables.product.prodname_dotcom %} サブスクリプションのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」をご覧ください。
-
-プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
-
-チームのコラボレーション機能をさらにサポートするために、SAML シングル サインオンや高度な監査のような機能を含む {% data variables.product.prodname_ghe_cloud %} にアップグレードできます。 {% data reusables.enterprise.link-to-ghec-trial %}
-
-ユーザー 1 人あたりの {% data variables.product.prodname_ghe_cloud %} の支払い関する詳細については、[{% data variables.product.prodname_ghe_cloud %} ドキュメント](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)を参照してください。
+- Billing managers
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
 
 {% else %}
 
-{% data variables.product.prodname_dotcom_the_website %}でEnterpriseアカウントを使用しており、プランの変更に関する疑問がある場合は、{% data variables.contact.contact_enterprise_sales %}にお問い合わせください。
+{% data variables.product.company_short %} bills for the following accounts for each deployment of {% data variables.product.prodname_enterprise %}.
 
-{% endif %} {% ifversion ghec %}
+### Accounts that consume a license on {% data variables.product.prodname_ghe_cloud %}
 
-{% data variables.product.prodname_ghe_cloud %}上の個々のOrganizationを使っている場合は、プランをアップグレードもしくはダウングレードできます。 詳細については、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」または「[{% data variables.product.prodname_dotcom %} サブスクリプションのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」を参照してください。 プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
+{% data variables.product.company_short %} bills for each of the following accounts on {% data variables.product.prodname_ghe_cloud %}:
+
+- Enterprise owners who are a member or owner of at least one organization in the enterprise
+- Organization members, including owners
+- Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an organization owner or member
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+{% note %}
+
+**Notes:** 
+  - {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
+  - {% data reusables.organizations.org-invite-scim %}
+
+{% endnote %}
+
+{% data variables.product.company_short %} does not bill for any of the following accounts:
+
+- {% data variables.product.prodname_managed_users_caps %} that are suspended
+- Enterprise owners who are not a member or owner of at least one organization in the enterprise
+- Enterprise billing managers
+- Billing managers for individual organizations
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
+
+Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
+
+Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+{% endif %}
+
+## About changes to your subscription
+
+{% ifversion fpt %}
+
+You can change your {% data variables.product.prodname_dotcom %} subscription at any time.
+
+### About changes for organizations on per-user plans
+
+{% endif %}
+
+You can add more licensed seats to your {% ifversion fpt or ghec %} organization{% endif %}{% ifversion ghec %} or{% endif %}{% ifversion ghec or ghes %} enterprise{% endif %} at any time. If you pay for more seats than are being used, you can also reduce the number of seats.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+
+If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
+
+To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like SAML single sign-on and advanced auditing. {% data reusables.enterprise.link-to-ghec-trial %}
+
+For more information about per-user pricing for {% data variables.product.prodname_ghe_cloud %}, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
+
+{% else %}
+
+If you use an enterprise account on {% data variables.product.prodname_dotcom_the_website %} and have questions about changes to your subscription, contact {% data variables.contact.contact_enterprise_sales %}.
+
+{% endif %}
+{% ifversion ghec %}
+
+If you use an individual organization on {% data variables.product.prodname_ghe_cloud %}, you can upgrade or downgrade your subscription. For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" or "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)." If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
 
 {% endif %}
 
 {% ifversion fpt %}
 
-### リポジトリごとのプランのOrganizationの変更について
+### About changes for organizations on per-repository plans
 
-レガシーの有料プラン間でのアップグレード及びダウングレードは、Organizationの支払い設定から行えます。 より多くのプライベートリポジトリを持つプランにアップグレードするなら、{% data variables.product.company_short %}は即座にアカウントを新しいプランに移行し、支払いサイクル中に残っている日数に比例した価格の差異を課金します。
+You can upgrade or downgrade between legacy paid plans in your organization's billing settings. When you upgrade to a plan with more private repositories, {% data variables.product.company_short %} immediately moves your account to your new plan and bills you for the difference in price, prorated for the number of days left in your billing cycle.
 
-プライベートリポジトリ数が少ないレガシーの有料プランにダウングレードする場合、新しいプランは次の支払日に有効になります。 新しいプランで利用できる以上のプライベートリポジトリを持っている場合、新しいプランが有効になった時点でプライベートリポジトリはロックされます。 プライベートリポジトリの数を減らすには、プライベートリポジトリの一部をパブリックにするか、プライベートリポジトリをローカルにクローンして {% data variables.product.prodname_dotcom %} 上のコピーを削除します。
+When you downgrade to a legacy paid plan with fewer private repositories, your new plan will take effect on your next billing date. If you have more private repositories than your new plan allows for, your private repositories will be locked when your new plan takes effect. To reduce your number of private repositories, you can make some of your private repositories public, or you can clone your private repositories locally and delete the copies on {% data variables.product.prodname_dotcom %}.
 
 {% endif %}
 
-## 参考資料
+## Further reading
 
 {%- ifversion not fpt %}
-- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」 {%- endif %}
-- 「[リポジトリについて](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)」
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
+{%- endif %}
+- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."

translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md

@@ -32,7 +32,7 @@ Only repository owners and administrators can edit repository-level security adv
    
    ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
 
-1. In the contribution form, make the desired improvements. You can edit or add any detail.{% ifversion security-advisories-reason-for-change %}
+1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
 1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
    
    ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}

translations/ja-JP/content/code-security/guides.md

@@ -63,6 +63,7 @@ includeGuides:
   - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
   - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
   - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
+  - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
   - /code-security/security-overview/about-the-security-overview
   - /code-security/security-overview/filtering-alerts-in-the-security-overview
   - /code-security/security-overview/viewing-the-security-overview

translations/ja-JP/content/code-security/repository-security-advisories/index.md

@@ -25,6 +25,7 @@ children:
   - /publishing-a-repository-security-advisory
   - /editing-a-repository-security-advisory
   - /withdrawing-a-repository-security-advisory
+  - /best-practices-for-writing-repository-security-advisories
 ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
 ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
 ms.translationtype: HT

translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md

@@ -68,7 +68,7 @@ You cannot change the configuration of {% data variables.product.prodname_secret
 ## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
 {% endif %}
 
-{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
+{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} will also periodically run a full git history scan of existing content in {% data variables.product.prodname_GH_advanced_security %} repositories where {% data variables.product.prodname_secret_scanning %} is enabled, and send alert notifications following the {% data variables.product.prodname_secret_scanning %} alert notification settings. {% endif %}For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
 
 If you're a repository administrator you can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, including archived repositories{% endif %}. Organization owners can also enable {% data variables.product.prodname_secret_scanning_GHAS %} for all repositories or for all new repositories within an organization. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
@@ -76,7 +76,7 @@ If you're a repository administrator you can enable {% data variables.product.pr
 {% endif %}
 ### About {% data variables.product.prodname_secret_scanning %} alerts
 
-When you push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. 
+When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%}
 
 If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.
 

translations/log/msft-cn-resets.csv

@@ -250,6 +250,7 @@ translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-pers
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
 translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
 translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
 translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -277,7 +278,10 @@ translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
 translations/zh-CN/content/actions/learn-github-actions/expressions.md,rendering error
 translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
 translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
+translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
 translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
+translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
 translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,rendering error
 translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
 translations/zh-CN/content/actions/quickstart.md,rendering error

translations/log/msft-ja-resets.csv

@@ -267,6 +267,7 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
 translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
 translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
 translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
@@ -294,7 +295,10 @@ translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
 translations/ja-JP/content/actions/learn-github-actions/expressions.md,rendering error
 translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
 translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
+translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
 translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
+translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
 translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md,rendering error
 translations/ja-JP/content/actions/quickstart.md,broken liquid tags
 translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,rendering error
@@ -347,6 +351,7 @@ translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managi
 translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags
+translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,broken liquid tags
 translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
@@ -499,12 +504,12 @@ translations/ja-JP/content/organizations/managing-peoples-access-to-your-organiz
 translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
 translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,broken liquid tags
 translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,broken liquid tags
-translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md,broken liquid tags
+translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
 translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
 translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
-translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md,broken liquid tags
-translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
+translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
+translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md,rendering error
+translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
 translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
 translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
 translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags

translations/log/msft-pt-resets.csv

@@ -255,6 +255,7 @@ translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-pers
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
+translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
 translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
 translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
 translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
@@ -281,7 +282,10 @@ translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
 translations/pt-BR/content/actions/learn-github-actions/expressions.md,rendering error
 translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
 translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
+translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
 translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
+translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
 translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md,rendering error
 translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
 translations/pt-BR/content/actions/quickstart.md,broken liquid tags
@@ -349,6 +353,7 @@ translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managi
 translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
 translations/pt-BR/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
 translations/pt-BR/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags
+translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,broken liquid tags
 translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
@@ -509,9 +514,9 @@ translations/pt-BR/content/organizations/restricting-access-to-your-organization
 translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
 translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
 translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
 translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md,rendering error
-translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
+translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
 translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
 translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error

translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md

@@ -1,5 +1,5 @@
 ---
-title: Converter um usuário em uma organização
+title: Converting a user into an organization
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
@@ -8,7 +8,7 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
-intro: Você pode converter sua conta pessoal em uma organização. Isso permite permissões mais granulares para repositórios que pertencem à organização.
+intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,60 +17,58 @@ versions:
 topics:
   - Accounts
 shortTitle: User into an organization
-ms.openlocfilehash: 8b99bd119a9fa061c025a4fcc299d7ace31d23eb
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147687065'
 ---
 {% warning %}
 
-**Aviso**: antes de converter um usuário em uma organização, tenha em mente os pontos a seguir.
+**Warning**: Before converting a user into an organization, keep these points in mind.
 
-* Você **não poderá mais** entrar na conta pessoal convertida.
-* Você **não poderá mais** criar nem modificar gists pertencentes à conta pessoal convertida.
-* Uma organização **não poderá** ser convertida novamente em um usuário.
-* As chaves SSH, os tokens OAuth, os perfil de trabalho, as reações e as informações de usuário associadas **não** serão transferidas para a organização. Isso só vale para a conta pessoal que está sendo convertida, não para os colaboradores da conta pessoal.
-* Todos os commits feitos com a conta pessoal convertida **não serão mais vinculados** a essa conta. Os commits em si **permanecerão** intactos.
-* Todos os comentários feitos com a conta pessoal convertida **não serão mais vinculados** a essa conta. Os comentários em si **permanecerão** intactos, mas serão associados ao usuário `ghost`.
-* Todas as bifurcações de repositórios privados feitas com a conta pessoal convertida serão excluídas.
+* You will **no longer** be able to sign into the converted personal account.
+* You will **no longer** be able to create or modify gists owned by the converted personal account.
+* An organization **cannot** be converted back to a user.
+* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
+* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
+* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
+* Any forks of private repositories made with the converted personal account will be deleted.
 {% endwarning %}
 
 {% ifversion fpt or ghec or ghes %}
-## Mantenha sua conta pessoal e crie uma organização manualmente
+## Keep your personal account and create a new organization manually
 
-Se você quiser que sua organização tenha o mesmo nome que você está usando atualmente para sua conta pessoal ou se quiser manter as informações de sua conta pessoal intactas, crie uma organização e transfira seus repositórios para ela em vez de converter sua conta pessoal em uma organização.
+If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
 
-1. Para manter o nome da conta pessoal atual para uso pessoal, [altere o nome da sua conta pessoal](/articles/changing-your-github-username) para algo novo e interessante.
-2. [Crie uma organização](/articles/creating-a-new-organization-from-scratch) com o nome original de sua conta pessoal.
-3. [Transfira seus repositórios](/articles/transferring-a-repository) para a nova conta de organização.{% endif %}
+1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
+2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
+3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
 
-## Converter sua conta pessoal em uma organização automaticamente
+## Convert your personal account into an organization automatically
 
-Você também pode converter sua conta pessoal diretamente em uma organização. A conversão da conta:
- - Preserva os repositórios como estão sem a necessidade de transferi-los para outra conta manualmente
- - Convida automaticamente colaboradores para equipes com permissões equivalentes ao que tinham antes de {% ifversion fpt or ghec %}- Para contas pessoais no {% data variables.product.prodname_pro %}, faz a transição automática da cobrança para [os {% data variables.product.prodname_team %} pagos](/articles/about-billing-for-github-accounts) sem a necessidade de inserir novamente as informações de pagamento, ajustar o ciclo de cobrança ou pagar em duplicidade a qualquer momento{% endif %}
+You can also convert your personal account directly into an organization. Converting your account:
+ - Preserves the repositories as they are without the need to transfer them to another account manually
+ - Automatically invites collaborators to teams with permissions equivalent to what they had before
+ {% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
 
-1. Crie uma conta pessoal, que você usará para entrar no GitHub e acessar a organização e seus repositórios após conversão.
-2.  [Saia de todas as organizações](/articles/removing-yourself-from-an-organization) em que a conta pessoa que você está convertendo tenha ingressado.
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
-5. Em "Transformar conta", clique em **Transformar <username> em uma organização**.
-    ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png)
-6. Na caixa de diálogo Account Transformation Warning (Aviso de transformação da conta), revise e confirme a conversão. Observe que as informações nessa caixa são as mesmas do aviso no início deste artigo.
-    ![Aviso de conversão](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. Na página "Transform your user into an organization" (Transformar usuário em uma organização), em "Choose an organization owner" (Escolher um proprietário da organização), escolha a conta pessoal secundária que você criou na seção anterior ou outro usuário em que confia para gerenciar a organização.
-    ![Página Adicionar proprietário da organização](/assets/images/help/organizations/organization-add-owner.png)
-8. Escolha a assinatura da nova organização e insira as informações de cobrança se solicitado.
-9. Clique em **Criar Organização**.
-10. Entre na nova conta pessoal que você criou na etapa um e use alternância de contexto para acessar sua nova organização.
+1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
+2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+5. Under "Transform account", click **Turn <username> into an organization**.
+ 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
+6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
+ 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
+ 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
+8. Choose your new organization's subscription and enter your billing information if prompted.
+9. Click **Create Organization**.
+10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
 
 {% tip %}
 
-**Dica**: ao converter uma conta pessoal em uma organização, adicionaremos colaboradores em repositórios que pertencem à conta da nova organização como *colaboradores externos*. Em seguida, você poderá convidar *colaboradores externos* para se tornarem membros da sua nova organização, se desejar. Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
+**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% endtip %}
 
-## Leitura adicional
-- "[Como configurar equipes](/articles/setting-up-teams)" {% ifversion fpt or ghec %}– "[Como convidar usuários para ingressar na sua organização](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Como acessar uma organização](/articles/accessing-an-organization)"
+## Further reading
+- "[Setting up teams](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Accessing an organization](/articles/accessing-an-organization)"

translations/pt-BR/content/actions/learn-github-actions/contexts.md

@@ -791,7 +791,7 @@ jobs:
 {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 ## `inputs` context
 
-The `inputs` context contains input properties passed to a reusable workflow{% ifversion actions-unified-inputs %} or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
+The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
 
 There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
 

translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md

@@ -1,50 +1,65 @@
 ---
-title: Desabilitar e habilitar um fluxo de trabalho
-intro: 'Você pode desabilitar e habilitar novamente um fluxo de trabalho usando a interface do usuário de {% data variables.product.prodname_dotcom %}, a API REST, ou {% data variables.product.prodname_cli %}.'
+title: Disabling and enabling a workflow
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Disable & enable a workflow
-ms.openlocfilehash: 1c0ebc0f56ba8c337648670e0f07d8a56e2fc326
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145101379'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Desabilitar um fluxo de trabalho permite que você impeça que um fluxo de trabalho seja acionado sem ter de excluir o arquivo do repositório. Você pode facilmente reabilitar o fluxo de trabalho novamente em {% data variables.product.prodname_dotcom %}.
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-Desabilitar temporariamente um fluxo de trabalho pode ser útil em vários cenários. Estes são alguns exemplos em que desabilitar um fluxo de trabalho pode ser útil:
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
-- Um erro de fluxo de trabalho que produz muitas solicitações ou solicitações erradas, afetando negativamente os serviços externos.
-- Um fluxo de trabalho que não é crítico e está consumindo muitos minutos na sua conta.
-- Um fluxo de trabalho que envia solicitações para um serviço que não está ativo.
-- Fluxos de trabalho em um repositório bifurcado desnecessários (por exemplo, fluxos de trabalho agendados).
+Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+
+- A workflow error that produces too many or wrong requests, impacting external services negatively.
+- A workflow that is not critical and is consuming too many minutes on your account.
+- A workflow that sends requests to a service that is down.
+- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
 
 {% warning %}
 
-**Aviso:** {% data reusables.actions.scheduled-workflows-disabled %}
+**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-Também é possível desabilitar e habilitar um fluxo de trabalho usando a API REST. Para obter mais informações, confira a "[API REST do Actions](/rest/reference/actions#workflows)".
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
 
-## Desabilitar um fluxo de trabalho
+## Disabling a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja desabilitar.
-![selecionar fluxo de trabalho nas ações](/assets/images/actions-select-workflow.png)
-1. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-![menu de kebab das ações](/assets/images/help/repository/actions-workflow-menu-kebab.png)
-1. Clique em **Desabilitar fluxo de trabalho**.
-![desabilitar fluxo de trabalho nas ações](/assets/images/help/repository/actions-disable-workflow.png) O fluxo de trabalho desabilitado é marcado como {% octicon "stop" aria-label="The stop icon" %} para indicar o status dele.
-![fluxo de trabalho desabilitado na lista de ações](/assets/images/help/repository/actions-find-disabled-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to disable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab-2022.png)
+   {%- else -%}
+   ![Actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
+   {%- endif %}
+1. Click **Disable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow-2022.png)
+   {%- else -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)
+
+   The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
+
+   ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
@@ -52,34 +67,45 @@ Também é possível desabilitar e habilitar um fluxo de trabalho usando a API R
 
 {% data reusables.cli.cli-learn-more %}
 
-Para desabilitar um fluxo de trabalho, use o subcomando `workflow disable`. Substitua `workflow` pelo nome, pela ID ou pelo nome do arquivo de fluxo de trabalho que deseja desabilitar. Por exemplo, `"Link Checker"`, `1234567` ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow disable <em>workflow</em>
+gh workflow disable WORKFLOW
 ```
 
 {% endcli %}
 
-## Habilitar um fluxo de trabalho
+## Enabling a workflow
 
 {% webui %}
 
-Você pode habilitar novamente um fluxo de trabalho que foi desabilitado anteriormente.
+You can re-enable a workflow that was previously disabled.
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja habilitar.
-![selecionar fluxo de trabalho desabilitado nas ações](/assets/images/help/repository/actions-select-disabled-workflow.png)
-1. Clique em **Habilitar fluxo de trabalho**.
-![habilitar fluxo de trabalho nas ações](/assets/images/help/repository/actions-enable-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to enable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow-2022.png)
+   {%- else -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
+   {%- endif %}
+1. Click **Enable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow-2022.png)
+   {%- else -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
 {% cli %}
 
-Para habilitar um fluxo de trabalho, use o subcomando `workflow enable`. Substitua `workflow` pelo nome, pela ID ou pelo nome do arquivo de fluxo de trabalho que deseja habilitar. Por exemplo, `"Link Checker"`, `1234567` ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow enable <em>workflow</em>
+gh workflow enable WORKFLOW
 ```
 
 {% endcli %}

translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md

@@ -1,38 +1,40 @@
 ---
-title: Executar um fluxo de trabalho manualmente
-intro: 'Quando um fluxo de trabalho é configurado para ser executado no evento `workflow_dispatch`, você pode executar o fluxo de trabalho usando a guia Ações no {% data variables.product.prodname_dotcom %}, a {% data variables.product.prodname_cli %} ou a API REST.'
+title: Manually running a workflow
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Manually run a workflow
-ms.openlocfilehash: 22717c31a6bc2599f066b0e870f0aa652c18cc6f
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095093'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configurar um fluxo de trabalho para ser executado manualmente
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-Para executar um fluxo de trabalho manualmente, o fluxo de trabalho precisa ser configurado para ser executado no evento `workflow_dispatch`. Para disparar o evento `workflow_dispatch`, seu fluxo de trabalho precisa estar no branch padrão. Para obter mais informações sobre o evento `workflow_dispatch`, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+## Configuring a workflow to run manually
+
+To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Executando um fluxo de trabalho
+## Running a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja executar.
-![selecionar fluxo de trabalho nas ações](/assets/images/actions-select-workflow.png)
-1. Acima da lista de execuções de fluxo de trabalho, selecione **Executar fluxo de trabalho**.
-![expedição do fluxo de trabalho das ações](/assets/images/actions-workflow-dispatch.png)
-1. Use o menu suspenso **Branch** para selecionar o branch do fluxo de trabalho e digite os parâmetros de entrada. Clique em **Executar fluxo de trabalho**.
-![fluxo de trabalho da execução manual das ações](/assets/images/actions-manually-run-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to run.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Above the list of workflow runs, select **Run workflow**.
+![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
+1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
+![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -40,31 +42,31 @@ Para executar um fluxo de trabalho manualmente, o fluxo de trabalho precisa ser
 
 {% data reusables.cli.cli-learn-more %}
 
-Para executar um fluxo de trabalho, use o subcomando `workflow run`. Substitua o parâmetro `workflow` pelo nome, pela ID ou pelo nome do arquivo de fluxo de trabalho que deseja executar. Por exemplo, `"Link Checker"`, `1234567` ou `"link-check-test.yml"`. Se você não especificar um fluxo de trabalho, {% data variables.product.prodname_cli %} irá retornar um menu interativo para você escolher um fluxo de trabalho.
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow run <em>workflow</em>
+gh workflow run WORKFLOW
 ```
 
-Se o fluxo de trabalho aceitar entradas, {% data variables.product.prodname_cli %} solicitará que você os insira. Como alternativa, você pode usar `-f` ou `-F` para adicionar uma entrada no formato `key=value`. Use `-F` para fazer a leitura de um arquivo.
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
 
 ```shell
 gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
 ```
 
-Você também pode passar as entradas como JSON usando a entrada padrão.
+You can also pass inputs as JSON by using standard input.
 
 ```shell
 echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
 ```
 
-Para executar um fluxo de trabalho em um branch que não seja o branch padrão do repositório, use o sinalizador `--ref`.
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
 
 ```shell
-gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+gh workflow run WORKFLOW --ref BRANCH
 ```
 
-Para ver o progresso da execução do fluxo de trabalho, use o subcomando `run watch` e selecione a execução na lista interativa.
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
 
 ```shell
 gh run watch
@@ -72,14 +74,14 @@ gh run watch
 
 {% endcli %}
 
-## Executar um fluxo de trabalho usando a API REST
+## Running a workflow using the REST API
 
-Ao usar a API REST, você configura os parâmetros do corpo da solicitação `inputs` e `ref`. Se as entradas forem omitidas, serão usados os valores-padrão definidos no arquivo de fluxo de trabalho.
+When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
 
 {% note %}
 
-**Nota:** você pode definir até 10 `inputs` para um evento `workflow_dispatch`.
+**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event.
 
 {% endnote %}
 
-Para obter mais informações sobre como usar a API REST, confira "[Criar um evento de expedição de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)".
+For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."

translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md

@@ -28,16 +28,18 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-{% ifversion fpt or ghes > 3.4 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.4 or ghae or ghec -%}
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run all jobs**.
+
+   If no jobs failed, you will not see the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+{%- endif %}
+{% ifversion ghes < 3.5 or ghae -%}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
 
-   If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
-{% endif %}
-{% ifversion ghes < 3.5 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
-{% endif %}
+   ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+{%- endif %}
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
@@ -80,8 +82,9 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
-    ![Re-run failed jobs drop-down menu](/assets/images/help/repository/rerun-failed-jobs-drop-down.png)
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}

translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md

@@ -1,29 +1,29 @@
 ---
-title: Visualizar o tempo de execução do trabalho
-intro: 'Você pode visualizar o tempo de execução de um trabalho, incluindo os minutos faturáveis que um trabalho acumulou.'
+title: Viewing job execution time
+shortTitle: View job execution time
+intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
-ms.openlocfilehash: 8293c36519dd727942d7cec0e1c1a2fa430ce112
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145096103'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Os minutos de execução de um trabalho faturável são exibidos para trabalhos executados em repositórios privados que usam executores hospedados em {% data variables.product.prodname_dotcom %} e são arredondados para o próximo minuto. Não há minutos faturáveis ao usar {% data variables.product.prodname_actions %} nos repositórios públicos ou para trabalhos executados em executores auto-hospedados.
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
-1. No resumo do trabalho, você pode ver o tempo de execução do trabalho. Para ver os detalhes sobre o tempo de execução do trabalho faturável, clique no tempo abaixo do **Tempo faturável**.
-   ![Link com informações sobre o tempo faturável e a execução](/assets/images/help/repository/view-run-billable-time.png)
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
+
+   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
-   **Observação:** o tempo faturável exibido não inclui multiplicadores de minutos. Para ver o uso total do {% data variables.product.prodname_actions %}, incluindo multiplicadores de minutos, confira "[Exibindo seu uso do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)".
-   
+
+   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
+
    {% endnote %}

translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md

@@ -61,7 +61,7 @@ If you use {% data variables.product.prodname_codeql %} {% data variables.produc
 {% ifversion ghes %}
 If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
 
-The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If both {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} and your {% data variables.product.prodname_actions %} runner have access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
 
 You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
 

translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md

@@ -41,6 +41,10 @@ You can make extra features for code security available to users by buying and u
 
 {% data reusables.advanced-security.license-overview %}
 
+{% ifversion ghes %}
+You can determine how many licenses you'll need for {% data variables.product.prodname_GH_advanced_security %} by generating a count of your instance's active committers in the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+{% endif %}
+
 To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
 
 ## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}

translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md

@@ -1,6 +1,6 @@
 ---
-title: Sobre preços por usuário
-intro: '{% ifversion fpt or ghec %}Para organizações{% ifversion ghec %} e empresas{% endif %}, a {% else %}A {% endif %}cobrança começa com o número de estações licenciadas que você escolhe.'
+title: About per-user pricing
+intro: '{% ifversion fpt or ghec %}For organizations{% ifversion ghec %} and enterprises{% endif %}, your {% else %}Your {% endif %}bill begins with the number of licensed seats you choose.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
   - /articles/about-per-user-pricing
@@ -15,109 +15,138 @@ topics:
   - Enterprise
   - Licensing
   - Organizations
-ms.openlocfilehash: 037e0e0cfbb04552a370cf8fd0f3e05c2e09423f
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145910835'
 ---
-## Sobre preços por usuário
 
-{% ifversion fpt %} As novas organizações no {% data variables.product.prodname_dotcom_the_website %} podem criar projetos públicos e de código aberto com o {% data variables.product.prodname_free_team %} ou fazer a atualização para um produto pago com preços por usuário. Para obter mais informações, confira "[Produtos do {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)" e "[Como fazer upgrade da sua assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)".
+## About per-user pricing
 
-As organizações que usam uma assinatura paga realizada antes de 11 de maio de 2016 podem optar por permanecer no plano existente por repositório ou alternar para preços por usuário. {% data variables.product.company_short %} irá notificar você 12 meses antes de qualquer alteração obrigatória na sua assinatura. Para obter mais informações sobre como alternar sua assinatura, confira "[Como fazer upgrade da sua assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)".
+{% ifversion fpt %}
+
+New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
+
+Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
 
 {% else %}
 
-A base da conta é o número de estações licenciadas padrão que você escolhe para a{% ifversion ghec %} organização ou{% endif %} empresa.
+The foundation of your bill is the number of standard licensed seats that you choose for your{% ifversion ghec %} organization or{% endif %} enterprise.
 
 {% data reusables.enterprise-licensing.unique-user-licensing-model %}
 
-Para garantir que o mesmo usuário não esteja consumindo mais de uma licença de várias implantações empresariais, você pode sincronizar o uso de licença entre os ambientes do {% data variables.product.prodname_ghe_server %} e do {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Sobre as licenças do GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)".
+To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. For more information, see "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
 
-Além das estações licenciadas, a conta pode incluir outros encargos, como de {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, confira "[Sobre a cobrança para a empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)".
+In addition to licensed seats, your bill may include other charges, such as {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
 {% endif %}
 
-## Pessoas que consomem uma licença
+## People that consume a license
 
-Cada pessoa consome uma licença e o {% data variables.product.company_short %} identifica indivíduos por endereço de email primário.
+{% ifversion fpt %}
 
-O {% data variables.product.company_short %} gera cobrança para as pessoas a seguir.
+{% data variables.product.company_short %} bills for the following people:
 
-{%- ifversion ghec %}
-- Proprietários da empresa que são membros ou proprietários de, pelo menos, uma organização na empresa {%- endif %}
-- Membros da organização, incluindo proprietários
-- Colaboradores externos em repositórios privados{% ifversion ghec %} ou internos{% endif %} pertencentes à sua organização, excluindo forks
-- Qualquer pessoa com um convite pendente para se tornar proprietário ou membro da organização
-- Qualquer pessoa com um convite pendente para se tornar um colaborador externo em repositórios privados{% ifversion ghec %} ou internos{% endif %} pertencentes à sua organização, excluindo os forks {%- ifversion ghec %}
-- Cada usuário em um instância do {% data variables.product.prodname_ghe_server %} que você implanta {%- endif %}
-- Usuários inativos
-
-O {% data variables.product.company_short %} não gera cobrança para nenhuma das pessoas a seguir.
-
-{%- ifversion ghec %}
-- Proprietários da empresa que não são membros nem proprietários de, pelo menos, uma organização na empresa
-- Gerentes de cobrança da empresa {%- endif %}
-- Gerentes de cobrança da organização{% ifversion ghec %} para organizações individuais do {% data variables.product.prodname_ghe_cloud %}{% endif %}
-- Qualquer pessoa com um convite pendente para se tornar um gerente de cobrança{% ifversion ghec %} da empresa ou{% endif %} da organização
-- Qualquer pessoa com um convite pendente para se tornar colaborador externo em um repositório público pertencente à organização {%- ifversion ghes %}
-- Usuários suspensos {%- endif %}
+- Organization members, including owners
+- Outside collaborators on private repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
 
 {% note %}
 
-**Observação**: {% data reusables.organizations.org-invite-scim %}
+**Notes:** 
+- {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
+- {% data reusables.organizations.org-invite-scim %}
 
 {% endnote %}
 
-Para obter mais informações, confira {% ifversion not fpt %}"[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" ou {% endif %}"[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
+{% data variables.product.company_short %} does not bill for the following people:
 
-O {% data variables.product.company_short %} conta cada {% ifversion not fpt %}membro ou {% endif %}colaborador externo uma vez para fins de cobrança, mesmo que a conta de usuário tenha {% ifversion not fpt %}associação a várias organizações em uma empresa ou {% endif %}acesso a vários repositórios pertencentes à organização. Para obter mais informações sobre colaboradores externos, confira "[Como adicionar colaboradores externos aos repositórios da sua organização](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)".
-
-{% ifversion ghes %} Os usuários suspensos não são contados ao calcular o número de usuários licenciados que consomem estações. Para obter mais informações, confira "[Como suspender usuários e cancelar a suspensão deles](/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users)".{% endif %}
-
-Os usuários inativos usam uma licença de estação.{% ifversion ghes %} Portanto, você pode suspender usuários inativos para liberar licenças de usuário.{% endif %} Para obter mais informações, confira "[Como gerenciar usuários inativos](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)".
-
-## Sobre as alterações na sua assinatura
-
-{% ifversion fpt %}
-
-Você pode alterar a sua assinatura de {% data variables.product.prodname_dotcom %} a qualquer momento.
-
-### Sobre as alterações para organizações com planos por usuário
-
-{% endif %}
-
-Você pode adicionar mais estações licenciadas à {% ifversion fpt or ghec %} organização{% endif %}{% ifversion ghec %} ou{% endif %}{% ifversion ghec or ghes %} empresa{% endif %} a qualquer momento. Se você paga por mais estações do que usa, reduza também o número de estações.{% ifversion fpt %} Para obter mais informações, confira "[Como fazer upgrade da assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription) e "[Como fazer downgrade da assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)".
-
-Se você tiver dúvidas sobre a sua assinatura, entre em contato com {% data variables.contact.contact_support %}.
-
-Para ampliar o suporte às habilidades de colaboração da sua equipe, você pode fazer upgrade para {% data variables.product.prodname_ghe_cloud %}, que inclui funcionalidades como logon único do SAML e auditoria avançada. {% data reusables.enterprise.link-to-ghec-trial %}
-
-Para obter mais informações sobre os preços por usuário do {% data variables.product.prodname_ghe_cloud %}, confira [a documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
+- Billing managers
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
 
 {% else %}
 
-Se você usar uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} e tiver dúvidas sobre as alterações na sua assinatura, entre em contato com {% data variables.contact.contact_enterprise_sales %}.
+{% data variables.product.company_short %} bills for the following accounts for each deployment of {% data variables.product.prodname_enterprise %}.
 
-{% endif %} {% ifversion ghec %}
+### Accounts that consume a license on {% data variables.product.prodname_ghe_cloud %}
 
-Se você usar uma organização individual em {% data variables.product.prodname_ghe_cloud %}, você poderá atualizar ou fazer o downgrade da sua assinatura. Para obter mais informações, confira "[Como fazer upgrade da sua assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription) ou "[Como fazer downgrade da sua assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)". Se você tiver dúvidas sobre a sua assinatura, entre em contato com {% data variables.contact.contact_support %}.
+{% data variables.product.company_short %} bills for each of the following accounts on {% data variables.product.prodname_ghe_cloud %}:
+
+- Enterprise owners who are a member or owner of at least one organization in the enterprise
+- Organization members, including owners
+- Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an organization owner or member
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+{% note %}
+
+**Notes:** 
+  - {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
+  - {% data reusables.organizations.org-invite-scim %}
+
+{% endnote %}
+
+{% data variables.product.company_short %} does not bill for any of the following accounts:
+
+- {% data variables.product.prodname_managed_users_caps %} that are suspended
+- Enterprise owners who are not a member or owner of at least one organization in the enterprise
+- Enterprise billing managers
+- Billing managers for individual organizations
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
+
+Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
+
+Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+{% endif %}
+
+## About changes to your subscription
+
+{% ifversion fpt %}
+
+You can change your {% data variables.product.prodname_dotcom %} subscription at any time.
+
+### About changes for organizations on per-user plans
+
+{% endif %}
+
+You can add more licensed seats to your {% ifversion fpt or ghec %} organization{% endif %}{% ifversion ghec %} or{% endif %}{% ifversion ghec or ghes %} enterprise{% endif %} at any time. If you pay for more seats than are being used, you can also reduce the number of seats.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+
+If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
+
+To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like SAML single sign-on and advanced auditing. {% data reusables.enterprise.link-to-ghec-trial %}
+
+For more information about per-user pricing for {% data variables.product.prodname_ghe_cloud %}, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
+
+{% else %}
+
+If you use an enterprise account on {% data variables.product.prodname_dotcom_the_website %} and have questions about changes to your subscription, contact {% data variables.contact.contact_enterprise_sales %}.
+
+{% endif %}
+{% ifversion ghec %}
+
+If you use an individual organization on {% data variables.product.prodname_ghe_cloud %}, you can upgrade or downgrade your subscription. For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" or "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)." If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
 
 {% endif %}
 
 {% ifversion fpt %}
 
-### Sobre as alterações para organizações em planos de cada repositório
+### About changes for organizations on per-repository plans
 
-Você pode atualizar ou fazer downgrade entre planos pagos herdados nas configurações de cobrança da sua organização. Ao fazer a atualização para um plano com mais repositórios privados, {% data variables.product.company_short %} transfere imediatamente sua conta para o seu novo plano e cobra pela diferença de preço, rateado pelo número de dias restantes em seu ciclo de cobrança.
+You can upgrade or downgrade between legacy paid plans in your organization's billing settings. When you upgrade to a plan with more private repositories, {% data variables.product.company_short %} immediately moves your account to your new plan and bills you for the difference in price, prorated for the number of days left in your billing cycle.
 
-Quando você faz downgrade para um plano pago herdado com menos repositórios privados, o novo plano entra em vigor na data da próxima cobrança. Se você tiver mais repositórios privados do que permite o novo plano, eles serão bloqueados quando o novo plano entrar em vigor. Para reduzir o número de repositórios privados, você pode tornar públicos alguns deles ou pode cloná-los localmente e excluir as cópias no {% data variables.product.prodname_dotcom %}.
+When you downgrade to a legacy paid plan with fewer private repositories, your new plan will take effect on your next billing date. If you have more private repositories than your new plan allows for, your private repositories will be locked when your new plan takes effect. To reduce your number of private repositories, you can make some of your private repositories public, or you can clone your private repositories locally and delete the copies on {% data variables.product.prodname_dotcom %}.
 
 {% endif %}
 
-## Leitura adicional
+## Further reading
 
 {%- ifversion not fpt %}
-- "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)" {%- endif %}
-- "[Sobre os repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
+{%- endif %}
+- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."

translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md

@@ -32,7 +32,7 @@ Only repository owners and administrators can edit repository-level security adv
    
    ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
 
-1. In the contribution form, make the desired improvements. You can edit or add any detail.{% ifversion security-advisories-reason-for-change %}
+1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
 1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
    
    ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}

translations/pt-BR/content/code-security/guides.md

@@ -63,6 +63,7 @@ includeGuides:
   - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
   - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
   - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
+  - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
   - /code-security/security-overview/about-the-security-overview
   - /code-security/security-overview/filtering-alerts-in-the-security-overview
   - /code-security/security-overview/viewing-the-security-overview

translations/pt-BR/content/code-security/repository-security-advisories/index.md

@@ -25,6 +25,7 @@ children:
   - /publishing-a-repository-security-advisory
   - /editing-a-repository-security-advisory
   - /withdrawing-a-repository-security-advisory
+  - /best-practices-for-writing-repository-security-advisories
 ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
 ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
 ms.translationtype: HT

translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md

@@ -68,7 +68,7 @@ You cannot change the configuration of {% data variables.product.prodname_secret
 ## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
 {% endif %}
 
-{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
+{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} will also periodically run a full git history scan of existing content in {% data variables.product.prodname_GH_advanced_security %} repositories where {% data variables.product.prodname_secret_scanning %} is enabled, and send alert notifications following the {% data variables.product.prodname_secret_scanning %} alert notification settings. {% endif %}For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
 
 If you're a repository administrator you can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, including archived repositories{% endif %}. Organization owners can also enable {% data variables.product.prodname_secret_scanning_GHAS %} for all repositories or for all new repositories within an organization. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
@@ -76,7 +76,7 @@ If you're a repository administrator you can enable {% data variables.product.pr
 {% endif %}
 ### About {% data variables.product.prodname_secret_scanning %} alerts
 
-When you push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. 
+When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%}
 
 If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.
 

translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md

@@ -1,5 +1,5 @@
 ---
-title: 将用户转换为组织
+title: Converting a user into an organization
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
@@ -8,7 +8,7 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
-intro: 可以将个人帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。
+intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,60 +17,58 @@ versions:
 topics:
   - Accounts
 shortTitle: User into an organization
-ms.openlocfilehash: 8b99bd119a9fa061c025a4fcc299d7ace31d23eb
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147687079'
 ---
 {% warning %}
 
-警告：在将用户转换为组织之前，请记住以下几点。
+**Warning**: Before converting a user into an organization, keep these points in mind.
 
-* 你将无法再登录转换后的个人帐户。
-* 你将无法再创建或修改转换后的个人帐户所拥有的 Gist。
-* 组织无法转换回用户。
-* 不会将 SSH 密钥、OAuth 标记、作业配置文件、反应和关联的用户信息传输到组织。 这只适用于被转换的个人帐户，而不适用于该个人帐户的任何协作者。
-* 使用转换后的个人帐户所做的任何提交将不再链接到该帐户。 提交本身将保持不变。
-* 转换后的个人帐户所做的任何现有注释将不再链接至该帐户。 注释本身将保持不变，但会与 `ghost` 用户关联。
-* 将删除使用转换后的个人帐户创建的任何专用存储库的分支。
+* You will **no longer** be able to sign into the converted personal account.
+* You will **no longer** be able to create or modify gists owned by the converted personal account.
+* An organization **cannot** be converted back to a user.
+* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
+* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
+* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
+* Any forks of private repositories made with the converted personal account will be deleted.
 {% endwarning %}
 
 {% ifversion fpt or ghec or ghes %}
-## 保留个人帐户并手动创建新组织
+## Keep your personal account and create a new organization manually
 
-如果希望组织的名称与目前用于个人帐户的名称相同，或者要保留个人帐户的信息不变，则必须创建一个新组织，然后将存储库转让给该组织，而不是将个人帐户转换为组织。
+If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
 
-1. 要保留当前个人帐户名称以供个人使用，[请将个人帐户名称更改为](/articles/changing-your-github-username)一个好听的新名称。
-2. 使用个人帐户的原始名称[创建新组织](/articles/creating-a-new-organization-from-scratch)。
-3. [将存储库转移到](/articles/transferring-a-repository)新的组织帐户。{% endif %}
+1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
+2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
+3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
 
-## 自动将个人帐户转换为组织
+## Convert your personal account into an organization automatically
 
-也可以将个人帐户直接转换为组织。 转换帐户：
- - 按原样保留仓库，无需手动将其转让给另一个帐户
- - 自动邀请协作者加入具有与其之前相同权限的团队 {% ifversion fpt or ghec %}- 对于 {% data variables.product.prodname_pro %} 上的个人帐户，自动将计费转换到[付费的 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts)，无需重新输入付款信息、调整计费周期或随时双倍付款{% endif %}
+You can also convert your personal account directly into an organization. Converting your account:
+ - Preserves the repositories as they are without the need to transfer them to another account manually
+ - Automatically invites collaborators to teams with permissions equivalent to what they had before
+ {% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
 
-1. 创建新的个人帐户，转换后您将用它来登录 GitHub 以及访问组织和仓库。
-2.  [退出组织](/articles/removing-yourself-from-an-organization)（你要转换的个人帐户已加入的组织）。
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
-5. 在“转换帐户”下，单击“将 <username> 转换为组织”。
-    ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png)
-6. 在 Account Transformation Warning（帐户转换警告）对话框中，查看并确认转换。 请注意，此框中的信息与本文顶部的警告信息相同。
-    ![转换警告](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. 在“Transform your user into an organization（将用户转换为组织）”页面的“Choose an organization owner（选择组织所有者）”下，选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。
-    ![添加组织所有者页面](/assets/images/help/organizations/organization-add-owner.png)
-8. 选择新组织的订阅，并在提示时输入帐单信息。
-9. 单击“创建组织”。
-10. 登录在第一步中创建的新个人帐户，然后使用上下文切换器访问新组织。
+1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
+2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+5. Under "Transform account", click **Turn <username> into an organization**.
+ 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
+6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
+ 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
+ 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
+8. Choose your new organization's subscription and enter your billing information if prompted.
+9. Click **Create Organization**.
+10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
 
 {% tip %}
 
-提示：将个人帐户转换为组织时，我们会将属于该帐户的存储库中的协作者作为外部协作者添加到新组织。 然后，你可以根据需要邀请外部协作者成为新组织的成员。 有关详细信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。
+**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% endtip %}
 
-## 延伸阅读
-- [设置团队](/articles/setting-up-teams) {% ifversion fpt or ghec %}- [邀请用户加入组织](/articles/inviting-users-to-join-your-organization){% endif %}
-- [访问组织](/articles/accessing-an-organization)
+## Further reading
+- "[Setting up teams](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Accessing an organization](/articles/accessing-an-organization)"

translations/zh-CN/content/actions/learn-github-actions/contexts.md

@@ -791,7 +791,7 @@ jobs:
 {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 ## `inputs` context
 
-The `inputs` context contains input properties passed to a reusable workflow{% ifversion actions-unified-inputs %} or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
+The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
 
 There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
 

translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md

@@ -1,50 +1,65 @@
 ---
-title: 禁用和启用工作流
-intro: '您可以使用 {% data variables.product.prodname_dotcom %} UI、REST API 或 {% data variables.product.prodname_cli %} 禁用并重新启用工作流程。'
+title: Disabling and enabling a workflow
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Disable & enable a workflow
-ms.openlocfilehash: 1c0ebc0f56ba8c337648670e0f07d8a56e2fc326
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145109568'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-禁用工作流程允许您停止触发工作流程，而不必从仓库中删除文件。 您可以轻松地在 {% data variables.product.prodname_dotcom %} 上重新启用工作流程。
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-在许多情况下，暂时禁用工作流程可能很有用。 以下是禁用工作流程可能有帮助的几个例子：
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
 
-- 产生请求过多或错误的工作流程错误，对外部服务产生负面影响。
-- 不重要但会耗费您帐户上太多分钟数的工作流程。
-- 向已关闭的服务发送请求的工作流程。
-- 复刻仓库上不需要的工作流程（例如预定的工作流程）。
+Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+
+- A workflow error that produces too many or wrong requests, impacting external services negatively.
+- A workflow that is not critical and is consuming too many minutes on your account.
+- A workflow that sends requests to a service that is down.
+- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
 
 {% warning %}
 
-**警告**：{% data reusables.actions.scheduled-workflows-disabled %}
+**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-您也可以使用 REST API 禁用和启用工作流程。 有关详细信息，请参阅“[Actions REST API](/rest/reference/actions#workflows)”。
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
 
-## 禁用工作流程
+## Disabling a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 在左侧边栏中，单击您想要禁用的工作流程。
-![操作选择工作流](/assets/images/actions-select-workflow.png)
-1. 单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
-![操作烤肉串菜单](/assets/images/help/repository/actions-workflow-menu-kebab.png)
-1. 单击“禁用工作流”。
-![操作禁用工作流](/assets/images/help/repository/actions-disable-workflow.png) 禁用的工作流标记为 {% octicon "stop" aria-label="The stop icon" %} 以指示其状态。
-![操作列表禁用的工作流](/assets/images/help/repository/actions-find-disabled-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to disable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab-2022.png)
+   {%- else -%}
+   ![Actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
+   {%- endif %}
+1. Click **Disable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow-2022.png)
+   {%- else -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)
+
+   The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
+
+   ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
@@ -52,34 +67,45 @@ ms.locfileid: '145109568'
 
 {% data reusables.cli.cli-learn-more %}
 
-要禁用工作流，请使用 `workflow disable` 子命令。 将 `workflow` 替换为要禁用的工作流的名称、ID 或文件名。 例如，`"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow disable <em>workflow</em>
+gh workflow disable WORKFLOW
 ```
 
 {% endcli %}
 
-## 启用工作流程
+## Enabling a workflow
 
 {% webui %}
 
-您可以重新启用以前禁用过的工作流程。
+You can re-enable a workflow that was previously disabled.
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 在左侧边栏中，单击您想要启用的工作流程。
-![操作选择禁用的工作流](/assets/images/help/repository/actions-select-disabled-workflow.png)
-1. 单击“启用工作流”。
-![操作启用工作流](/assets/images/help/repository/actions-enable-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to enable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow-2022.png)
+   {%- else -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
+   {%- endif %}
+1. Click **Enable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow-2022.png)
+   {%- else -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+   {%- endif %}
 
 {% endwebui %}
 
 {% cli %}
 
-要启用工作流，请使用 `workflow enable` 子命令。 将 `workflow` 替换为要启用的工作流的名称、ID 或文件名。 例如，`"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow enable <em>workflow</em>
+gh workflow enable WORKFLOW
 ```
 
 {% endcli %}

translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md

@@ -1,38 +1,40 @@
 ---
-title: 手动运行工作流程
-intro: '当工作流配置为在发生 `workflow_dispatch` 事件时运行时，可以使用 {% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %} 或 REST API 上的“Actions”选项卡运行工作流。'
+title: Manually running a workflow
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 shortTitle: Manually run a workflow
-ms.openlocfilehash: 22717c31a6bc2599f066b0e870f0aa652c18cc6f
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099187'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 配置工作流程手动运行
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-要手动运行工作流，必须将工作流配置为在 `workflow_dispatch` 事件上运行。 要触发 `workflow_dispatch` 事件，工作流必须位于默认分支中。 有关配置 `workflow_dispatch` 事件的详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows#workflow_dispatch)”。
+## Configuring a workflow to run manually
+
+To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## 运行工作流程
+## Running a workflow
 
 {% webui %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
-1. 在左侧边栏中，单击您想要运行的工作流程。
-![操作选择工作流](/assets/images/actions-select-workflow.png)
-1. 在工作流运行列表上方，选择“运行工作流”。
-![操作工作流调度](/assets/images/actions-workflow-dispatch.png)
-1. 使用“分支”下拉菜单，选择工作流的分支，并键入输入参数。 单击“运行工作流”。
-![操作手动运行工作流](/assets/images/actions-manually-run-workflow.png)
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to run.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Above the list of workflow runs, select **Run workflow**.
+![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
+1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
+![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -40,31 +42,31 @@ ms.locfileid: '145099187'
 
 {% data reusables.cli.cli-learn-more %}
 
-要运行工作流，请使用 `workflow run` 子命令。 将 `workflow` 参数替换为要运行的工作流的名称、ID 或文件名。 例如，`"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
 
 ```shell
-gh workflow run <em>workflow</em>
+gh workflow run WORKFLOW
 ```
 
-如果您的工作流程接受输入，{% data variables.product.prodname_cli %} 将提示您输入它们。 或者，可以使用 `-f` 或 `-F` 添加 `key=value` 格式的输入。 使用 `-F` 从文件中读取。
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
 
 ```shell
 gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
 ```
 
-您也可以使用标准输入以 JSON 的身份传递输入。
+You can also pass inputs as JSON by using standard input.
 
 ```shell
 echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
 ```
 
-要在存储库的默认分支以外的分支上运行工作流，请使用 `--ref` 标记。
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
 
 ```shell
-gh workflow run <em>workflow</em> --ref <em>branch-name</em>
+gh workflow run WORKFLOW --ref BRANCH
 ```
 
-要查看工作流运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
 
 ```shell
 gh run watch
@@ -72,14 +74,14 @@ gh run watch
 
 {% endcli %}
 
-## 使用 REST API 运行工作流程
+## Running a workflow using the REST API
 
-使用 REST API 时，应将 `inputs` 和 `ref` 配置为请求正文参数。 如果忽略输入，则使用工作流程文件中定义的默认值。
+When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
 
 {% note %}
 
-注意：最多可为 `workflow_dispatch` 事件定义 10 个 `inputs`。
+**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event.
 
 {% endnote %}
 
-有关使用 REST API 的详细信息，请参阅“[创建工作流调度事件](/rest/reference/actions/#create-a-workflow-dispatch-event)”。
+For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."

translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md

@@ -28,16 +28,18 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-{% ifversion fpt or ghes > 3.4 or ghae or ghec %}
+{% ifversion fpt or ghes > 3.4 or ghae or ghec -%}
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run all jobs**.
+
+   If no jobs failed, you will not see the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+{%- endif %}
+{% ifversion ghes < 3.5 or ghae -%}
 1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
 
-   If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
-{% endif %}
-{% ifversion ghes < 3.5 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
-{% endif %}
+   ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+{%- endif %}
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
@@ -80,8 +82,9 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
-    ![Re-run failed jobs drop-down menu](/assets/images/help/repository/rerun-failed-jobs-drop-down.png)
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}

translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md

@@ -1,29 +1,29 @@
 ---
-title: 查看作业执行时间
-intro: 您可以查看作业的执行时间，包括某个作业累积的可计费分钟数。
+title: Viewing job execution time
+shortTitle: View job execution time
+intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
-ms.openlocfilehash: 8293c36519dd727942d7cec0e1c1a2fa430ce112
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145100197'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-计费作业执行分钟数仅显示在使用 {% data variables.product.prodname_dotcom %} 托管运行器的私有存储库上运行的作业，并四舍五入到下一分钟。 如果在公共仓库中使用 {% data variables.product.prodname_actions %}，或在自托管的运行器中运行作业时，将没有可计费分钟数。
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
-1. 在作业摘要下，您可以查看作业的执行时间。 若要查看有关计费作业执行时间的详细信息，请单击“计费时间”下的时间。
-   ![运行和计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png)
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
+
+   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
-   注意：显示的计费时间不包括任何分钟乘数。 若要查看 {% data variables.product.prodname_actions %} 总的使用情况，包括分钟乘数，请参阅“[查看你的 {% data variables.product.prodname_actions %} 使用情况](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)”。
-   
+
+   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
+
    {% endnote %}

translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md

@@ -61,7 +61,7 @@ If you use {% data variables.product.prodname_codeql %} {% data variables.produc
 {% ifversion ghes %}
 If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
 
-The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If both {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} and your {% data variables.product.prodname_actions %} runner have access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
 
 You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
 

translations/zh-CN/content/admin/overview/about-github-for-enterprises.md

@@ -1,6 +1,6 @@
 ---
 title: About GitHub for enterprises
-intro: "Businesses can use {% data variables.product.prodname_dotcom %}'s enterprise products to improve their entire software development lifecyle."
+intro: "Businesses can use {% data variables.product.prodname_dotcom %}'s enterprise products to improve their entire software development lifecycle."
 versions:
   ghec: '*'
   ghes: '*'
@@ -19,7 +19,7 @@ Developers can store and version control your source code in repositories, using
 
 When businesses adopt {% data variables.product.prodname_enterprise %}, their return on investment (ROI) is high. For example, their developers save 45 minutes per day, and onboarding and training time is reduced by 40%. For more information, see [The Total Economic Impact of {% data variables.product.prodname_enterprise %}](https://resources.github.com/downloads/TEI-of-GitHub-Enterprise.pdf).
 
-To simplify administration for all the stages in the software development lifecyle, we provide a single point of visibility and management called an enterprise account. Enterprise accounts enable you to manage billing and settings, enforce policy, and audit the people with access to your enterprise's resources. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+To simplify administration for all the stages in the software development lifecycle, we provide a single point of visibility and management called an enterprise account. Enterprise accounts enable you to manage billing and settings, enforce policy, and audit the people with access to your enterprise's resources. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 
 Optionally, you can add extra code security features with {% data variables.product.prodname_GH_advanced_security %}, and enhanced support options with {% data variables.contact.premium_support %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[About {% data variables.contact.premium_support %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/support/learning-about-github-support/about-github-premium-support){% ifversion ghae %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 

translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md

@@ -41,6 +41,10 @@ You can make extra features for code security available to users by buying and u
 
 {% data reusables.advanced-security.license-overview %}
 
+{% ifversion ghes %}
+You can determine how many licenses you'll need for {% data variables.product.prodname_GH_advanced_security %} by generating a count of your instance's active committers in the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+{% endif %}
+
 To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
 
 ## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}

translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md

@@ -20,6 +20,7 @@ topics:
 ## About per-user pricing
 
 {% ifversion fpt %}
+
 New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
 
 Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
@@ -37,48 +38,70 @@ In addition to licensed seats, your bill may include other charges, such as {% d
 
 ## People that consume a license
 
-Each person consumes one license, and {% data variables.product.company_short %} identifies individuals by primary email address.
+{% ifversion fpt %}
 
-{% data variables.product.company_short %} bills for the following people.
+{% data variables.product.company_short %} bills for the following people:
 
-{%- ifversion ghec %}
-- Enterprise owners who are a member or owner of at least one organization in the enterprise
-{%- endif %}
 - Organization members, including owners
-- Outside collaborators on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
-- Anyone with a pending invitation to become an organization owner or member
-- Anyone with a pending invitation to become an outside collaborator on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
-{%- ifversion ghec %}
-- Each user on any {% data variables.product.prodname_ghe_server %} instance that you deploy
-{%- endif %}
+- Outside collaborators on private repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
 - Dormant users
 
-{% data variables.product.company_short %} does not bill for any of the following people.
-
-{%- ifversion ghec %}
-- Enterprise owners who are not a member or owner of at least one organization in the enterprise
-- Enterprise billing managers
-{%- endif %}
-- Organization billing managers{% ifversion ghec %} for individual organizations on {% data variables.product.prodname_ghe_cloud %}{% endif %}
-- Anyone with a pending invitation to become an{% ifversion ghec %} enterprise or{% endif %} organization billing manager
-- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
-{%- ifversion ghes %}
-- Suspended users
-{%- endif %}
-
 {% note %}
 
-**Note**: {% data reusables.organizations.org-invite-scim %}
+**Notes:** 
+- {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
+- {% data reusables.organizations.org-invite-scim %}
 
 {% endnote %}
 
-For more information, see {% ifversion not fpt %}"[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" or {% endif %}"[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+{% data variables.product.company_short %} does not bill for the following people:
 
-{% data variables.product.company_short %} counts each {% ifversion not fpt %}member or {% endif %}outside collaborator once for billing purposes, even if the user account has {% ifversion not fpt %}membership in multiple organizations in an enterprise or {% endif %}access to multiple repositories owned by your organization. For more information about outside collaborators, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
+- Billing managers
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
 
-{% ifversion ghes %}Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users](/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users)."{% endif %}
+{% else %}
 
-Dormant users do occupy a seat license.{% ifversion ghes %} As such, you can choose to suspend dormant users to release user licenses.{% endif %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+{% data variables.product.company_short %} bills for the following accounts for each deployment of {% data variables.product.prodname_enterprise %}.
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_cloud %}
+
+{% data variables.product.company_short %} bills for each of the following accounts on {% data variables.product.prodname_ghe_cloud %}:
+
+- Enterprise owners who are a member or owner of at least one organization in the enterprise
+- Organization members, including owners
+- Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an organization owner or member
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+{% note %}
+
+**Notes:** 
+  - {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
+  - {% data reusables.organizations.org-invite-scim %}
+
+{% endnote %}
+
+{% data variables.product.company_short %} does not bill for any of the following accounts:
+
+- {% data variables.product.prodname_managed_users_caps %} that are suspended
+- Enterprise owners who are not a member or owner of at least one organization in the enterprise
+- Enterprise billing managers
+- Billing managers for individual organizations
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
+
+Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
+
+Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+{% endif %}
 
 ## About changes to your subscription
 
@@ -123,5 +146,7 @@ When you downgrade to a legacy paid plan with fewer private repositories, your n
 
 {%- ifversion not fpt %}
 - "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
 {%- endif %}
-- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
+- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."

translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md

@@ -32,7 +32,7 @@ Only repository owners and administrators can edit repository-level security adv
    
    ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
 
-1. In the contribution form, make the desired improvements. You can edit or add any detail.{% ifversion security-advisories-reason-for-change %}
+1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
 1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
    
    ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}

translations/zh-CN/content/code-security/guides.md

@@ -63,6 +63,7 @@ includeGuides:
   - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
   - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
   - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
+  - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
   - /code-security/security-overview/about-the-security-overview
   - /code-security/security-overview/filtering-alerts-in-the-security-overview
   - /code-security/security-overview/viewing-the-security-overview

translations/zh-CN/content/code-security/repository-security-advisories/index.md

@@ -25,6 +25,7 @@ children:
   - /publishing-a-repository-security-advisory
   - /editing-a-repository-security-advisory
   - /withdrawing-a-repository-security-advisory
+  - /best-practices-for-writing-repository-security-advisories
 ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
 ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
 ms.translationtype: HT

translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md

@@ -68,7 +68,7 @@ You cannot change the configuration of {% data variables.product.prodname_secret
 ## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
 {% endif %}
 
-{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
+{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} will also periodically run a full git history scan of existing content in {% data variables.product.prodname_GH_advanced_security %} repositories where {% data variables.product.prodname_secret_scanning %} is enabled, and send alert notifications following the {% data variables.product.prodname_secret_scanning %} alert notification settings. {% endif %}For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
 
 If you're a repository administrator you can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, including archived repositories{% endif %}. Organization owners can also enable {% data variables.product.prodname_secret_scanning_GHAS %} for all repositories or for all new repositories within an organization. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
@@ -76,7 +76,7 @@ If you're a repository administrator you can enable {% data variables.product.pr
 {% endif %}
 ### About {% data variables.product.prodname_secret_scanning %} alerts
 
-When you push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. 
+When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%}
 
 If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.