jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 03:01:36 -05:00
Code Issues Projects Releases Wiki Activity

New translation batch for ja (#29501)

Browse Source 
* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja

* run script/i18n/reset-known-broken-translation-files.js

* Check in ja CSV report

Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com>
This commit is contained in:
docubot
2022-07-30 19:46:15 -04:00
committed by GitHub
parent 8c410ad0a1
commit 1422a8755b
7 changed files with 41 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
View File

@@ -22,9 +22,9 @@ Organization については、Organization のオーナーと支払いマネー
{% data reusables.organizations.billing-settings %}
{% data reusables.dotcom_billing.codespaces-minutes %}
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
1. レポートをフィルタして、`Product`フィールドで"Codespaces"をメンションしている行だけを表示させてください。
![A usage report filtered for Codespaces](/assets/images/help/codespaces/CSV-usage-report.png)
![Codespacesでフィルターされた使用状況レポート](/assets/images/help/codespaces/CSV-usage-report.png)
{% ifversion ghec %}
## Enterprise アカウントの {% data variables.product.prodname_codespaces %} の使用状況を表示する

14
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
View File

@@ -60,9 +60,9 @@ topics:
| ------------------ | -- | -------------------------------------------------------------------------------------------------------- |
| `fail-on-severity` | 任意 | 重要度(`low`、`moderate`、`high`、`critical`)の閾値を定義します。</br>指定された重要度以上の脆弱性を導入するPull Requestについて、このアクションは失敗します。 |
{%- ifversion dependency-review-action-licenses %}
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
| `allow-licenses` | 任意| 許可されたライセンスのリストを含みます。 このパラメータで利用できる値は、APIドキュメンテーションの[Licenses](/rest/licenses)ページにあります。</br>このリストにマッチしないライセンスを持つ依存関係を導入するPull Requestについて、このアクションは失敗します。{% endif %}
{%- ifversion dependency-review-action-licenses %}
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}
| `deny-licenses` | 任意| 禁止されているライセンスのリストを含みます。 このパラメータで利用できる値は、APIドキュメンテーションの[Licenses](/rest/licenses)ページにあります。</br>このリストにマッチするライセンスを持つ依存関係を導入するPull Requestについて、このアクションは失敗します。{% endif %}
{% ifversion dependency-review-action-licenses %}
{% tip %}
@@ -93,14 +93,14 @@ jobs:
# Possible values: "critical", "high", "moderate", "low"
fail-on-severity: critical
{% ifversion dependency-review-action-licenses %}
# You can only can only include one of these two options: `allow-licenses` and `deny-licences`
# ([String]). これらのライセンスだけを許可 (オプション)
# `allow-licenses`及び`deny-licences`という2つのオプションのいずれかのみを含めることができます
# ([String])。 これらのライセンスだけを許可 (オプション)
# 取り得る値: https://docs.github.com/en/rest/licensesからの任意の`spdx_id`値
# 許可ライセンス: GPL-3.0, BSD-3-Clause, MIT
# ([String]). Block the pull request on these licenses (optional)
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
# deny-licenses: LGPL-2.0, BSD-2-Clause
# ([String]). これらのライセンスでPull Requestはブロック (オプション)
# 取り得る値: https://docs.github.com/en/rest/licensesからの任意の`spdx_id`値
# 拒否ライセンス: LGPL-2.0, BSD-2-Clause
{% endif %}
```

20
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
View File

@@ -1,6 +1,6 @@
---
title: 'About automation for {% data variables.product.prodname_projects_v1 %}'
intro: 'You can configure automatic workflows to keep the status of {% data variables.projects.projects_v1_board %} cards in sync with the associated issues and pull requests.'
title: '{% data variables.product.prodname_projects_v1 %}の自動化について'
intro: '{% data variables.projects.projects_v1_board %}カードのステータスと、関連するIssue及びPull Requestとの同期を保つための自動化ワークフローを設定できます。'
redirect_from:
- /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards
- /articles/about-automation-for-project-boards
@@ -9,21 +9,21 @@ versions:
feature: projects-v1
topics:
- Pull requests
shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
shortTitle: '{% data variables.product.prodname_projects_v1 %}の自動化'
allowTitleToDifferFromFilename: true
---
{% data reusables.projects.project_boards_old %}
{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[{% data variables.product.prodname_projects_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
{% data reusables.project-management.automate-project-board-permissions %} 詳しい情報については[Organizationの{% data variables.product.prodname_projects_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。
You can automate actions based on triggering events for {% data variables.projects.projects_v1_board %} columns. This eliminates some of the manual tasks in managing a {% data variables.projects.projects_v1_board %}. For example, you can configure a "To do" column, where any new issues or pull requests you add to a {% data variables.projects.projects_v1_board %} are automatically moved to the configured column. For more information, see "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)."
アクションを、{% data variables.projects.projects_v1_board %}の列に対するイベントによるトリガーに基づいて自動化できます。 これによって、{% data variables.projects.projects_v1_board %}の管理のための主導のタスクの一部を削減できます。 例えば、{% data variables.projects.projects_v1_board %}に対して新しいIssueやPull Requestを追加する"To do"列が、自動的に設定された列に移動されるように設定できます。 詳しい情報については「[{% data variables.product.prodname_projects_v1 %}の自動化の設定](/articles/configuring-automation-for-project-boards)」を参照してください。
{% data reusables.project-management.use-automated-template %}
{% data reusables.project-management.copy-project-boards %}
{% data variables.projects.projects_v1_board_caps %} automation can also help teams develop a shared understanding of a {% data variables.projects.projects_v1_board %}'s purpose and the team's development process by creating a standard workflow for certain actions.
{% data variables.projects.projects_v1_board_caps %}の自動化は、特定のアクションに対する標準化されたワークフローを作成することによって、Teamが{% data variables.projects.projects_v1_board %}の目的とTeamの開発プロセスの共通理解を促進するための役にも立ちます。
{% data reusables.project-management.resync-automation %}
@@ -37,10 +37,10 @@ You can automate actions based on triggering events for {% data variables.projec
## プロジェクトの進捗の追跡
You can track the progress on your {% data variables.projects.projects_v1_board %}. [To do]、[In progress]、または [Done] 列のカードの数は、プロジェクトの進捗全体にカウントされます。 {% data reusables.project-management.project-progress-locations %}
{% data variables.projects.projects_v1_board %}の進捗を追跡できます。 [To do]、[In progress]、または [Done] 列のカードの数は、プロジェクトの進捗全体にカウントされます。 {% data reusables.project-management.project-progress-locations %}
For more information, see "[Tracking progress on your {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
詳しい情報については「[{% data variables.product.prodname_project_v1 %}の進捗の追跡](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)」を参照してください。
## 参考リンク
- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
- 「[{% data variables.product.prodname_projects_v1 %}の自動化の設定](/articles/configuring-automation-for-project-boards)」{% ifversion fpt or ghec %}
- 「[{% data variables.product.prodname_project_v1 %}のコピー](/articles/copying-a-project-board)」{% endif %}

34
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
View File

@@ -1,5 +1,5 @@
---
title: '{% data variables.product.prodname_projects_v1 %}について'
title: About {% data variables.product.prodname_projects_v1 %}
intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
redirect_from:
- /github/managing-your-work-on-github/managing-project-boards/about-project-boards
@@ -7,7 +7,7 @@ redirect_from:
- /articles/about-project-boards
- /github/managing-your-work-on-github/about-project-boards
versions:
feature: projects-v1
feature: "projects-v1"
topics:
- Pull requests
allowTitleToDifferFromFilename: true
@@ -15,17 +15,17 @@ allowTitleToDifferFromFilename: true
{% data reusables.projects.project_boards_old %}
{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. 列内のカードの並び替え、列から列へのカードの移動、および列の順序の変更には、ドラッグアンドドロップまたはキーボードショートカットが利用できます。
{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. ノートでは要求を満たせない場合、ノートを Issue に変換することができます。 For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
プロジェクトボードには以下の種類があります:
Types of project boards:
- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository.
- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. 他のリポジトリの Issue やプルリクエストを参照するノートも含まれます。
- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
## Creating and viewing {% data variables.projects.projects_v1_boards %}
@@ -33,7 +33,7 @@ To create a {% data variables.projects.projects_v1_board %} for your organizatio
If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. アクティビティビューにアクセスするには、[**Menu**] をクリックしてスクロールダウンします。
The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)."
@@ -47,14 +47,14 @@ You can also [disable {% data variables.projects.projects_v1_boards %} in a repo
## Templates for {% data variables.projects.projects_v1_boards %}
You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. また、自動化が設定済みのテンプレートを選択することもできます。
You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. You can also choose a template with automation already configured.
| テンプレート | 説明 |
| ---------------------------- | ------------------------------------------------------------------------------ |
| Basic kanban | [To do]、[In progress]、[Done] 列でタスクを追跡します。 |
| Automated kanban | カードは自動的に [To do]、[In progress]、[Done] の列間を移動します。 |
| Automated kanban with review | プルリクエストレビューのステータスのための追加のトリガーで、カードは [To do]、[In progress]、[Done] 列の間を自動的に移動します。 |
| Bug triage | [To do]、[High priority]、[Low priority]、[Closed] 列でバグのトリアージと優先順位付けをします。 |
| Template | Description |
| --- | --- |
| Basic kanban | Track your tasks with To do, In progress, and Done columns |
| Automated kanban | Cards automatically move between To do, In progress, and Done columns |
| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status |
| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns |
For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
@@ -62,11 +62,11 @@ For more information on automation for {% data variables.product.prodname_projec
{% data reusables.project-management.copy-project-boards %}
## 参考リンク
## Further reading
- [{% data variables.product.prodname_project_v1 %}を作成する](/articles/creating-a-project-board)
- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
- [キーボードショートカット](/articles/keyboard-shortcuts/#project-boards)
- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)"

2
translations/ja-JP/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md
View File

@@ -174,7 +174,7 @@ GitHub, Inc. c/o Corporation Service Company
Sacramento, CA 95833-3505
```
legal@support.github.com に CC を送信することもできます。
Courtesy copies may be emailed to legal-support@github.com
要求を送る際は、次の情報を含めて、できるだけ具体的かつ範囲を絞った内容にしてください。

6
translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml
View File

@@ -112,11 +112,11 @@ sections:
- 「[OrganizationでのGitHub Actionsの無効化もしくは制限](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)」
- 「[リポジトリでのGitHub Actionsの設定の管理](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)」
- |
Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility. For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
ユーザは、`workflow_dispatch`及び`workflow_call`でトリガーされる単一のワークフローを書き、`inputs`コンテキストで入力値にアクセスできます。以前は`workflow_dispatch`の入力はイベントのペイロードで、再利用可能かつ手動でトリガーされる1つのワークフローを書きたいワークフローの作者には困難が増していました。`workflow_dispatch`でトリガーされるワークフローでは、互換性を保つために引き続き`github.event.inputs`コンテキストで入力が利用できます。詳しい情報については「[コンテキスト](/actions/learn-github-actions/contexts#inputs-context)」を参照してください。
- |
To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
ジョブの結果をまとめるために、ユーザはMarkdownを生成し、そのコンテンツをジョブのまとめとして公開できます。たとえば、GitHub Actionsでテストを実行したあと、まとめはテストのパス、失敗、スキップの概要を提供でき、ログのアウトプットを完全にレビューする必要を下げてくれるかもしれません。詳しい情報については「[GitHub Actionsのワークフローコマンド](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)」を参照してください。
- |
To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
ワークフローの再実行の際のジョブの実行の失敗の診断をやりやすくするために、ユーザはジョブの実行と環境に関する情報を出力するデバッグロギングを有効化できます。詳しい情報については「[ワークフローとジョブの再実行](/actions/managing-workflow-runs/re-running-workflows-and-jobs)」及び[ワークフローの実行ログの利用](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)」を参照してください。
- |
If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
-

1
translations/log/ja-resets.csv
View File

@@ -173,6 +173,7 @@ translations/ja-JP/content/get-started/learning-about-github/about-github-advanc
translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md,broken liquid tags
translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags
translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags
translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,broken liquid tags
translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489
1 file reason
173 translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md broken liquid tags
174 translations/ja-JP/content/get-started/using-github/github-mobile.md broken liquid tags
175 translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md broken liquid tags
176 translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md broken liquid tags
177 translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md broken liquid tags
178 translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md broken liquid tags
179 translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md Listed in localization-support#489