github · Octomerger · May 24, 2022 · May 24, 2022 · May 24, 2022
diff --git a/...ns/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/...ns/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -369,6 +369,10 @@ runs:
 ```
 {% endif %}
 
+#### `runs.steps[*].continue-on-error`
+
+**Optional**  Prevents the action from failing when a step fails. Set to `true` to allow the action to pass when this step fails.
+
 ## `runs` for Docker container actions
 
 **Required** Configures the image used for the Docker container action.

diff --git a/...s/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/...s/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,7 +17,7 @@ versions:
 
 ## About re-running workflows and jobs
 
-Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.
+Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% if debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
 
 ## Re-running all the jobs in a workflow
 
@@ -35,6 +35,7 @@ Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses
 {% ifversion ghes < 3.5 or ghae %}
 1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。 ![[Re-run checks] ドロップダウンメニュー](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
 {% endif %}
+{% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
 
@@ -48,6 +49,15 @@ Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses
 gh run rerun <em>run-id</em>
 ```
 
+{% if debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun <em>run-id</em> --debug
+```
+
+{% endif %}
+
 ワークフロー実行の進行状況を表示するには、`run watch` サブコマンドを使用して、インタラクティブリストから実行を選択します。
 
 ```shell
@@ -68,6 +78,7 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
 {% 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)
+{% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
 
@@ -79,6 +90,14 @@ To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the
 gh run rerun <em>run-id</em> --failed
 ```
 
+{% if debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun <em>run-id</em> --failed --debug
+```
+
+{% endif %}
 {% endcli %}
 
 ## Re-running a specific job in a workflow
@@ -94,6 +113,7 @@ When you re-run a specific job in a workflow, a new workflow run will start for
 1. Next to the job that you want to re-run, click {% octicon "sync" aria-label="The re-run icon" %}. ![Re-run selected job](/assets/images/help/repository/re-run-selected-job.png)
 
    Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}. ![Re-run selected job](/assets/images/help/repository/re-run-single-job-from-log.png)
+{% data reusables.actions.enable-debug-logging %}
 
 {% endwebui %}
 
@@ -105,6 +125,14 @@ To re-run a specific job in a workflow run, use the `run rerun` subcommand with
 gh run rerun --job <em>job-id</em>
 ```
 
+{% if debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun --job <em>job-id</em> --debug
+```
+
+{% endif %}
 {% endcli %}
 
 {% endif %}

diff --git a/...tent/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/...tent/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -22,6 +22,12 @@ versions:
 
 シークレットの設定に関する詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
+{% if debug-reruns %}
+
+Additionally, anyone who has access to run a workflow can enable runner diagnostic logging and step debug logging for a workflow re-run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+ {% endif %}
+
 ## ランナーの診断ロギングの有効化
 
 ランナーの診断ログは、ランナーによるジョブの実行の様子に関する情報を含む追加のログファイルを提供します。 ログアーカイブには、2つのログファイルが追加されます。
@@ -35,7 +41,7 @@ versions:
 
 ## ステップのデバッグロギングの有効化
 
-ステップのデバッグロギングは、ジョブの実行の間と実行後のジョブのログの詳細度を高めます。
+酢鉄粉デバッグロギングは、ジョブの実行の間と実行後のジョブのログの詳細度を高めます。
 
 1. ステップのデバッグロギングを有効化するには、ワークフローを含むリポジトリで以下のシークレットを設定しなければなりません： `ACTIONS_STEP_DEBUG`を`true`にしてください。
 

diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
@@ -341,7 +341,7 @@ A workflow created in a repository can access the following number of secrets:
          - name: Decrypt large secret
            run: ./.github/scripts/decrypt_secret.sh
            env:
-             LARGE_SECRET_PASSPHRASE: {% raw %}${{ secrets. LARGE_SECRET_PASSPHRASE }}{% endraw %}
+             LARGE_SECRET_PASSPHRASE: {% raw %}${{ secrets.LARGE_SECRET_PASSPHRASE }}{% endraw %}
          # This command is just an example to show your secret being printed
          # Ensure you remove any print statements of your secrets. GitHub does
          # not hide secrets that use this workaround.

diff --git a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
@@ -198,6 +198,7 @@ When you call a reusable workflow, you can only use the following keywords in th
 * [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)
 * [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif)
 * [`jobs.<job_id>.permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions)
+* [`jobs.<job_id>.concurrency`](/actions/reference/workflow-syntax-for-github-actions#concurrency)
 
    {% note %}
 

diff --git a/...eviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/...eviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -1068,6 +1068,16 @@ topics:
 | `secret_scanning.disable` | An organization owner disabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |
 | `secret_scanning.enable`  | An organization owner enabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories.                                                                                                      |
 
+{% if secret-scanning-alert-audit-log %}
+### `secret_scanning_alert` category actions
+
+| アクション                           | 説明                                                                                                                                                                                                                                                                                                             |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret_scanning_alert.create`  | {% data variables.product.prodname_dotcom %} detected a secret and created a {% data variables.product.prodname_secret_scanning %} alert. 詳しい情報については、「[{% data variables.product.prodname_secret_scanning %} からのアラートを管理する](/code-security/secret-scanning/managing-alerts-from-secret-scanning)」を参照してください。 |
+| `secret_scanning_alert.reopen`  | A user reopened a {% data variables.product.prodname_secret_scanning %} alert.                                                                                                                                                                                                                               |
+| `secret_scanning_alert.resolve` | A user resolved a {% data variables.product.prodname_secret_scanning %} alert.                                                                                                                                                                                                                               |
+{% endif %}
+
 ### `secret_scanning_new_repos` カテゴリアクション
 
 | アクション                               | 説明                                                                                                                                                                                                                              |
@@ -1167,11 +1177,11 @@ topics:
 
 ### `team_discussions` カテゴリアクション
 
-| アクション                      | 説明                                                                                                                                                                                                                                                  |
-| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `team_discussions.clear`   | An organization owner cleared the setting to allow team discussions for an organization or enterprise.                                                                                                                                              |
-| `team_discussions.disable` | An organization owner disabled team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization)." |
-| `team_discussions.enable`  | An organization owner enabled team discussions for an organization.                                                                                                                                                                                 |
+| アクション                      | 説明                                                                                                                                                                                                                          |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `team_discussions.clear`   | An organization owner cleared the setting to allow team discussions for an organization or enterprise.                                                                                                                      |
+| `team_discussions.disable` | An organization owner disabled team discussions for an organization. 詳しい情報については [Organization の Team ディスカッションの無効化](/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization)を参照してください。 |
+| `team_discussions.enable`  | An organization owner enabled team discussions for an organization.                                                                                                                                                         |
 
 {%- ifversion ghec %}
 ### `team_sync_tenant` category actions

diff --git a/...it-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/...it-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -19,6 +19,8 @@ You can export the audit log by downloading a JSON or CSV file from your enterpr
 
 You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface.
 
+{% data reusables.audit_log.git-events-export-limited %}
+
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
 As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."

diff --git a/...your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/...your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -269,6 +269,15 @@ on:
 この種のマージコミットは{% data variables.product.prodname_dependabot %}によって作成されるので、このコミットで実行されるワークフローは読み取りのみの権限を持つことになります。 {% data variables.product.prodname_code_scanning %}と{% data variables.product.prodname_dependabot %}のセキュリティ更新またはバージョン更新をリポジトリで有効化した場合は、{% data variables.product.prodname_dependabot %}の`@dependabot squash and merge`コマンドは使わないことをおすすめします。 その代わりに、リポジトリで自動マージを有効化できます。 これは、すべての必須レビューが満たされ、ステータスチェックをパスしたら、Pyll Requestは自動的にマージされるということです。 自動マージの有効化に関する詳しい情報については「[Pull Requestの自動マージ](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)」を参照してください。
 {% endif %}
 
+## Error: "is not a .ql file, .qls file, a directory, or a query pack specification"
+
+You will see this error if CodeQL is unable to find the named query, query suite, or query pack at the location requested in the workflow. There are two common reasons for this error.
+
+- There is a typo in the workflow.
+- A resource the workflow refers to by path was renamed, deleted, or moved to a new location.
+
+After verifying the location of the resource, you can update the workflow to specify the correct location. If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository.
+
 ## Warning: "git checkout HEAD^2 is no longer necessary"
 
 古い{% data variables.product.prodname_codeql %}ワークフローを使っていると、"Initialize {% data variables.product.prodname_codeql %}"アクションからの出力に以下の警告が含まれていることがあります。

diff --git a/...-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/...-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -33,25 +33,6 @@ For more information about personal accounts on {% data variables.product.produc
 {% data reusables.education.plan-to-use-github %}
 {% data reusables.education.submit-application %}
 
-## Organization をアップグレードする
-
-教育者もしくは研究者割引のリクエストが承認されると、学習コミュニティで利用する Organization を {% data variables.product.prodname_team %} にアップグレードできます。これで、無料で無制限のユーザとプライベートリポジトリの全ての機能が利用できるようになります。 既存の Organization をアップグレードするか、アップグレードする新しい Organization を作成できます。
-
-### 既存の Organization をアップグレードする
-
-{% data reusables.education.upgrade-page %}
-{% data reusables.education.upgrade-organization %}
-
-### 新しい Organization をアップグレードする
-
-{% data reusables.education.upgrade-page %}
-1. [{% octicon "plus" aria-label="The plus symbol" %} **Create an organization**] をクリックします。 ![[Create an organization] ボタン](/assets/images/help/education/create-org-button.png)
-3. 情報を読んで、[**Create organization**] をクリックします。 ![[Create organization] ボタン](/assets/images/help/education/create-organization-button.png)
-4. [Choose a plan] の下で、[**Choose {% data variables.product.prodname_free_team %}**] をクリックします。
-5. プロンプトに従って Organization を作成します。
-{% data reusables.education.upgrade-page %}
-{% data reusables.education.upgrade-organization %}
-
 ## 参考リンク
 
 - [教育者あるいは研究者割引が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)

diff --git a/...ed-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/...ed-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -149,14 +149,19 @@ For more information, see "[Relative Links](#relative-links)."
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5559 %}
 ### Specifying the theme an image is shown to
 
-You can specify the theme an image is displayed to by appending `#gh-dark-mode-only` or `#gh-light-mode-only` to the end of an image URL, in Markdown.
+You can specify the theme an image is displayed for in Markdown by using the HTML `<picture>` element in combination with the `prefers-color-scheme` media feature. We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
 
-We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
+For example, the following code displays a sun image for light themes and a moon for dark themes:
 
-| コンテキスト      | URL                                                                      |
-| ----------- | ------------------------------------------------------------------------ |
-| Dark Theme  | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
-| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)`  |
+```HTML
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://user-images.githubusercontent.com/25423296/163456776-7f95b81a-f1ed-45f7-b7ab-8fa810d529fa.png">
+  <source media="(prefers-color-scheme: light)" srcset="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
+  <img alt="Shows an illustrated sun in light color mode and a moon with stars in dark color mode." src="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
+</picture>
+```
+
+The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
 {% endif %}
 
 ## リスト

diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md
@@ -32,14 +32,14 @@ GraphQLサーバーと通信するには、適切なスコープを持つOAuth
 
 
 ```
-user{% ifversion not ghae %}
-public_repo{% endif %}
 repo
-repo_deployment
 repo:status
-read:repo_hook
+repo_deployment{% ifversion not ghae %}
+public_repo{% endif %}
 read:org
 read:public_key
+read:repo_hook
+user
 read:gpg_key
 ```