New translation batch for ja (github#25639)

translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -479,16 +479,46 @@ branding:
 
 ### `branding.icon`
 
-利用する[Feather](https://feathericons.com/)アイコンの名前。 <!-- 
+The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand icons are omitted as well as the following:
+
+<table>
+<tr>
+<td>coffee</td>
+<td>カラム</td>
+<td>divide-circle</td>
+<td>divide-square</td>
+</tr>
+<tr>
+<td>divide</td>
+<td>frown</td>
+<td>hexagon</td>
+<td>key</td>
+</tr>
+<tr>
+<td>meh</td>
+<td>mouse-pointer</td>
+<td>smile</td>
+<td>ツール</td>
+</tr>
+<tr>
+<td>x-octagon</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</table>
+
+Here is an exhaustive list of all currently supported icons:
+
+
+<!-- 
   This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
-  This table does not match the latest version the feather library. 
-  (Brand icons are omitted, and our supported list is not necessarily up-to-date with the latest version of the feather icon library.)
   To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo. 
 -->
 
 <table>
 <tr>
-<td>activity</td>
+<td>アクティビティ</td>
 <td>airplay</td>
 <td>alert-circle</td>
 <td>alert-octagon</td>
@@ -503,7 +533,7 @@ branding:
 <td>align-right</td>
 <td>anchor</td>
 <td>aperture</td>
-<td>archive</td>
+<td>アーカイブ</td>
 </tr>
 <tr>
 <td>arrow-down-circle</td>
@@ -582,10 +612,10 @@ branding:
 <td>cloud-rain</td>
 <td>cloud-snow</td>
 <td>cloud</td>
-<td>code</td>
+<td>コード</td>
 </tr>
 <tr>
-<td>command</td>
+<td>コマンド</td>
 <td>compass</td>
 <td>copy</td>
 <td>corner-down-left</td>
@@ -635,12 +665,12 @@ branding:
 <tr>
 <td>file-plus</td>
 <td>file-text</td>
-<td>file</td>
+<td>ファイル</td>
 <td>film</td>
 </tr>
 <tr>
 <td>filter</td>
-<td>flag</td>
+<td>フラグ</td>
 <td>folder-minus</td>
 <td>folder-plus</td>
 </tr>
@@ -658,7 +688,7 @@ branding:
 </tr>
 <tr>
 <td>hard-drive</td>
-<td>hash</td>
+<td>ハッシュ</td>
 <td>headphones</td>
 <td>heart</td>
 </tr>
@@ -760,13 +790,13 @@ branding:
 </tr>
 <tr>
 <td>repeat</td>
-<td>rewind</td>
+<td>巻き戻し</td>
 <td>rotate-ccw</td>
 <td>rotate-cw</td>
 </tr>
 <tr>
 <td>rss</td>
-<td>save</td>
+<td>保存</td>
 <td>scissors</td>
 <td>search</td>
 </tr>
@@ -785,7 +815,7 @@ branding:
 <tr>
 <td>shopping-cart</td>
 <td>shuffle</td>
-<td>sidebar</td>
+<td>サイドバー</td>
 <td>skip-back</td>
 </tr>
 <tr>
@@ -807,7 +837,7 @@ branding:
 <td>tablet</td>
 </tr>
 <tr>
-<td>tag</td>
+<td>タグ</td>
 <td>target</td>
 <td>terminal</td>
 <td>thermometer</td>
@@ -837,14 +867,14 @@ branding:
 <td>upload-cloud</td>
 </tr>
 <tr>
-<td>upload</td>
+<td>アップロード</td>
 <td>user-check</td>
 <td>user-minus</td>
 <td>user-plus</td>
 </tr>
 <tr>
 <td>user-x</td>
-<td>user</td>
+<td>ユーザ</td>
 <td>users</td>
 <td>video-off</td>
 </tr>

translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md

@@ -15,6 +15,13 @@ miniTocMaxHeadingLevel: 3
 
 ## Monitoring your workflows
 
+{% if github-runner-dashboard %}
+### Monitoring your current jobs in your organization or enterprise
+
+{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+
+{% endif %}
+
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
 ### 視覚化グラフの利用

translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md

@@ -86,7 +86,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | checks        | read/write  | none | read |
 | contents      | read/write  | read | read |
 | deployments   | read/write  | none | read |{% ifversion fpt or ghec %}
-| id-token      | read/write  | none | read |{% endif %}
+| id-token      | none        | none | read |{% endif %}
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |

translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md

@@ -141,6 +141,16 @@ In this example, the attempted script injection is unsuccessful:
 
 With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}.
 
+{% ifversion fpt or ghec %}
+### Using starter workflows for code scanning
+
+{% data reusables.advanced-security.starter-workflows-beta %}
+{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available.
+
+For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."
+
+{% endif %}
+
 ### Restricting permissions for tokens
 
 To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."

translations/ja-JP/content/actions/using-github-hosted-runners/index.md

@@ -7,6 +7,7 @@ versions:
   ghes: '*'
 children:
   - /about-github-hosted-runners
+  - /monitoring-your-current-jobs
   - /customizing-github-hosted-runners
 shortTitle: Use GitHub-hosted runners
 ---

translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md

@@ -0,0 +1,30 @@
+---
+title: Monitoring your current jobs
+intro: 'Monitor how {% data variables.product.prodname_dotcom %}-hosted runners are processing jobs in your organization or enterprise, and identify any related constraints.'
+versions:
+  feature: github-runner-dashboard
+shortTitle: Monitoring your current jobs
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Viewing active jobs in your organization or enterprise
+
+You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
+
+{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.github-hosted-runners-table-entry %}
+1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
+
+  ![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png)
+
+## Viewing queued jobs in your organization or enterprise
+
+{% data variables.product.prodname_dotcom %}-hosted runners allow you to run jobs concurrently, and the maximum number of concurrent jobs will vary depending on your plan. If you reach the maximum number of concurrent jobs, any new jobs will start to enter a queue. To find out more about the number of concurrent jobs available to your plan, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration)."
+
+The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
+
+{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.github-hosted-runners-table-entry %}
+1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. ![Screenshot of the maximum jobs for an account](/assets/images/help/settings/github-hosted-runners-max-jobs.png)

translations/ja-JP/content/actions/using-jobs/using-concurrency.md

@@ -17,3 +17,8 @@ miniTocMaxHeadingLevel: 4
 
 {% data reusables.actions.jobs.section-using-concurrency-jobs %}
 
+{% if github-runner-dashboard %}
+## Monitoring your current jobs in your organization or enterprise
+
+{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% endif %}

translations/ja-JP/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md

@@ -24,6 +24,8 @@ topics:
 
 {% data reusables.actions.workflow-organization-templates %}
 
+{% data reusables.actions.starter-workflow-categories %}
+
 ## Creating a starter workflow
 
 Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.

translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md

@@ -685,6 +685,25 @@ on:
 
 {% endnote %}
 
+#### Running your workflow when a pull request merges
+
+When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
+
+```yaml
+on:
+  pull_request:
+    types:
+      - closed
+
+jobs:
+  if_merged:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+    - run: |
+        echo The PR was merged
+```
+
 {% data reusables.developer-site.pull_request_forked_repos_link %}
 
 ### `pull_request_comment` (use `issue_comment`)
@@ -869,6 +888,25 @@ on:
 
 {% endnote %}
 
+#### Running your workflow when a pull request merges
+
+When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request_target` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
+
+```yaml
+on:
+  pull_request_target:
+    types:
+      - closed
+
+jobs:
+  if_merged:
+    if: github.event.pull_request_target.merged == true
+    runs-on: ubuntu-latest
+    steps:
+    - run: |
+        echo The PR was merged
+```
+
 ### `プッシュ`
 
 | webhook イベントのペイロード                                                                   | アクティビティタイプ | `GITHUB_SHA`                                  | `GITHUB_REF` |

translations/ja-JP/content/actions/using-workflows/using-starter-workflows.md

@@ -28,6 +28,8 @@ topics:
 
 {% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %}
 
+{% data reusables.actions.starter-workflow-categories %}
+
 You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
 ## Using starter workflows

translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md

@@ -52,12 +52,6 @@ topics:
 
 {% data reusables.enterprise-accounts.dormant-user-release-phase %}
 
-{% warning %}
-
-**Note:** During the private beta, ongoing improvements to the report download feature may limit its availability.
-
-{% endwarning %}
-
 ## Downloading the dormant users report from your enterprise account
 
 {% data reusables.enterprise-accounts.access-enterprise %}

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

@@ -40,6 +40,12 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
 
 {% data reusables.dotcom_billing.pricing_cal %}
 
+### Billing for {% data variables.product.prodname_codespaces %} prebuilds
+
+{% data reusables.codespaces.prebuilds-beta-note %}
+
+{% data reusables.codespaces.billing-for-prebuilds %}
+
 ## Setting a spending limit
 
 {% data reusables.codespaces.codespaces-spending-limit-requirement %}