From 9030e7f769fa37edd50f7b54ef16bec18bd83285 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 24 May 2022 18:19:48 -0400 Subject: [PATCH] New translation batch for ja (#27963) * 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: Peter Bengtsson --- .../metadata-syntax-for-github-actions.md | 4 +++ .../re-running-workflows-and-jobs.md | 30 ++++++++++++++++++- .../enabling-debug-logging.md | 8 ++++- .../security-guides/encrypted-secrets.md | 2 +- .../using-workflows/reusing-workflows.md | 1 + .../audit-log-events-for-your-enterprise.md | 20 +++++++++---- ...-audit-log-activity-for-your-enterprise.md | 2 ++ .../troubleshooting-the-codeql-workflow.md | 9 ++++++ ...-for-an-educator-or-researcher-discount.md | 19 ------------ .../basic-writing-and-formatting-syntax.md | 17 +++++++---- .../guides/forming-calls-with-graphql.md | 8 ++--- ...ing-the-audit-log-for-your-organization.md | 15 ++++++++++ ...he-visibility-of-your-github-pages-site.md | 6 ++-- .../ja-JP/data/features/debug-reruns.yml | 8 +++++ .../secret-scanning-alert-audit-log.yml | 7 +++++ .../enterprise-server/3-3/0-rc1.yml | 14 +++++---- .../release-notes/enterprise-server/3-3/0.yml | 14 +++++---- .../actions/about-artifact-log-retention.md | 11 ++++--- .../actions/enable-debug-logging-cli.md | 1 + .../reusables/actions/enable-debug-logging.md | 3 ++ .../audit_log/git-events-export-limited.md | 7 +++++ .../code-scanning/run-additional-queries.md | 2 +- .../education/upgrade-organization.md | 1 - .../data/reusables/education/upgrade-page.md | 1 - .../support-holiday-availability.md | 2 +- .../pages/about-private-publishing.md | 2 +- translations/log/ja-resets.csv | 4 +-- 27 files changed, 156 insertions(+), 62 deletions(-) create mode 100644 translations/ja-JP/data/features/debug-reruns.yml create mode 100644 translations/ja-JP/data/features/secret-scanning-alert-audit-log.yml create mode 100644 translations/ja-JP/data/reusables/actions/enable-debug-logging-cli.md create mode 100644 translations/ja-JP/data/reusables/actions/enable-debug-logging.md create mode 100644 translations/ja-JP/data/reusables/audit_log/git-events-export-limited.md delete mode 100644 translations/ja-JP/data/reusables/education/upgrade-organization.md delete mode 100644 translations/ja-JP/data/reusables/education/upgrade-page.md diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 0f0fa998085d..10aeb29cce40 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/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/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md index 0bc5ed465458..6358065e834e 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md +++ b/translations/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 run-id ``` +{% if debug-reruns %} +{% data reusables.actions.enable-debug-logging-cli %} + +```shell +gh run rerun run-id --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 run-id --failed ``` +{% if debug-reruns %} +{% data reusables.actions.enable-debug-logging-cli %} + +```shell +gh run rerun run-id --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 job-id ``` +{% if debug-reruns %} +{% data reusables.actions.enable-debug-logging-cli %} + +```shell +gh run rerun --job job-id --debug +``` + +{% endif %} {% endcli %} {% endif %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 8bed56ad33b9..29e2f93898de 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/ja-JP/content/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 index 0b589159a29b..6ef5d0875d4d 100644 --- 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 index 081e7b88e5f6..82981a2585b7 100644 --- 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..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) * [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) * [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) +* [`jobs..concurrency`](/actions/reference/workflow-syntax-for-github-actions#concurrency) {% note %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 666c95f14ae3..e624f5982e16 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-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/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md index 1b4a948ab8df..f3f9076ae370 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-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/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 1df5c3487edc..da19598f2711 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-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/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md index 61e4ebed7943..c0ffed308141 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-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/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index d80af2b90db5..ab9ef1757ee6 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/get-started/writing-on-github/getting-started-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 `` 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 + + + + Shows an illustrated sun in light color mode and a moon with stars in dark color mode. + +``` + +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 index 6e623a049d97..c574b7e549bf 100644 --- 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 ``` diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 401665144c8c..64782150ba72 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -127,6 +127,9 @@ Using the qualifier `country`, you can filter events in the audit log based on t ## Exporting the audit log {% data reusables.audit_log.export-log %} + +{% data reusables.audit_log.git-events-export-limited %} + {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} @@ -737,7 +740,19 @@ For more information, see "[Managing the publication of {% data variables.produc |------------------|------------------- | `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. +{% endif %} +{% if secret-scanning-alert-audit-log %} +### `secret_scanning_alert` category actions + +| Action | Description +|------------------|------------------- +| `create` | Triggered when {% data variables.product.prodname_dotcom %} detects an exposed secret and creates a {% data variables.product.prodname_secret_scanning %} alert. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/managing-alerts-from-secret-scanning)." +| `reopen` | Triggered when a user reopens a {% data variables.product.prodname_secret_scanning %} alert. +| `resolve` | Triggered when a user resolves a {% data variables.product.prodname_secret_scanning %} alert. +{% endif %} + +{% ifversion ghec or ghes or ghae %} ### `secret_scanning_new_repos` category actions | Action | Description diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 93bdcf0bf14f..a6bfddb0d8f1 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -11,13 +11,15 @@ shortTitle: Change visibility of site ## About access control for {% data variables.product.prodname_pages %} sites -With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your project site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. {% data reusables.pages.privately-publish-ghec-only %} If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." -If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your project sites privately or publicly to anyone on the internet. + +Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." ## About subdomains for privately published sites diff --git a/translations/ja-JP/data/features/debug-reruns.yml b/translations/ja-JP/data/features/debug-reruns.yml new file mode 100644 index 000000000000..56cc29e45435 --- /dev/null +++ b/translations/ja-JP/data/features/debug-reruns.yml @@ -0,0 +1,8 @@ +--- +#Issue 6629 +#Enabling debug logging when re-running jobs or workflows +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6629' diff --git a/translations/ja-JP/data/features/secret-scanning-alert-audit-log.yml b/translations/ja-JP/data/features/secret-scanning-alert-audit-log.yml new file mode 100644 index 000000000000..90527b0a1f09 --- /dev/null +++ b/translations/ja-JP/data/features/secret-scanning-alert-audit-log.yml @@ -0,0 +1,7 @@ +--- +#Reference: #7046. +#Documentation for new audit log events for alerts for secret scanning. +versions: + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-7046' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml index 815a9f465e3a..12e6a71501b8 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -73,18 +73,20 @@ sections: - ボタンをクリックして、ファイルの生の内容をクリップボードにコピーできるようになりました。以前は、生のファイルを開き、すべてを選択し、コピーしなければなりませんでした。ファイルの内容をコピーするには、ファイルにアクセスし、ツールバーの{% octicon "copy" aria-label="The copy icon" %}をクリックしてください。この機能は現在、一部のブラウザでのみ利用可能であることに注意してください。 - 新しいリリースを作成する際に、タグをテキストフィールドで指定するのではなく、ドロップダウンセレクタを使ってタグを選択あるいは作成できるようになりました。詳しい情報については「[リポジトリのリリースの管理](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)」を参照してください。 - 双方向のUnicodeテキストを含むファイルを表示する際に、警告が表示されるようになりました。双方向のUnicodeテキストは、ユーザインターフェースで表示されるのとは異なるように解釈あるいはコンパイルされることがあります。たとえば、非表示の双方向Unicode文字を使ってテキストファイルのセグメントをスワップさせることがでいいます。これらの文字の置き換えに関する詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/)を参照してください。 - - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - '`CITATION.cff`ファイルを使って、自分の作品をどのように引用してほしいかを他者に知らせることができるようになりました。`CITATION.cff`ファイルはプレーンテキストファイルで、人間及び機会が読める引用情報を持ちます。{% data variables.product.prodname_ghe_server %}はこの情報を[APA](https://apastyle.apa.org)や[BibTeX](https://en.wikipedia.org/wiki/BibTeX)のような共通引用フォーマットにパースします。詳しい情報については「[CITATIONファイルについて](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)」を参照してください。' - heading: 'Markdownの変更' notes: - | - You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments. + Markdownファイル、Issue、Pull Request、コメント内での引用符やリストに、新しいキーボードショートカットが使えるようになりました。 - * To add quotes, use cmd shift . on Mac, or ctrl shift . on Windows and Linux. - * To add an ordered list, use cmd shift 7 on Mac, or ctrl shift 7 on Windows and Linux. - * To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux. + * 引用符を追加するには、Macではcmd shift . Windows及びLinuxではctrl shift .としてください。 - See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts. + * 順序付きリストを追加するには、Macではcmd shift 7 Windows及びLinuxではctrl shift 7としてください。 + + * 順序無しリストを追加するには、Macではcmd shift 8 Windows及びLinuxではctrl shift 8としてください。 + + 利用可能なショートカットの完全なリストについては「[キーボードショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。 - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."' - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)." diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml index fa6471c9777e..2e8df3ab315d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml @@ -65,18 +65,20 @@ sections: - ボタンをクリックして、ファイルの生の内容をクリップボードにコピーできるようになりました。以前は、生のファイルを開き、すべてを選択し、コピーしなければなりませんでした。ファイルの内容をコピーするには、ファイルにアクセスし、ツールバーの{% octicon "copy" aria-label="The copy icon" %}をクリックしてください。この機能は現在、一部のブラウザでのみ利用可能であることに注意してください。 - 新しいリリースを作成する際に、タグをテキストフィールドで指定するのではなく、ドロップダウンセレクタを使ってタグを選択あるいは作成できるようになりました。詳しい情報については「[リポジトリのリリースの管理](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)」を参照してください。 - 双方向のUnicodeテキストを含むファイルを表示する際に、警告が表示されるようになりました。双方向のUnicodeテキストは、ユーザインターフェースで表示されるのとは異なるように解釈あるいはコンパイルされることがあります。たとえば、非表示の双方向Unicode文字を使ってテキストファイルのセグメントをスワップさせることがでいいます。これらの文字の置き換えに関する詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/)を参照してください。 - - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - '`CITATION.cff`ファイルを使って、自分の作品をどのように引用してほしいかを他者に知らせることができるようになりました。`CITATION.cff`ファイルはプレーンテキストファイルで、人間及び機会が読める引用情報を持ちます。{% data variables.product.prodname_ghe_server %}はこの情報を[APA](https://apastyle.apa.org)や[BibTeX](https://en.wikipedia.org/wiki/BibTeX)のような共通引用フォーマットにパースします。詳しい情報については「[CITATIONファイルについて](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)」を参照してください。' - heading: 'Markdownの変更' notes: - | - You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments. + Markdownファイル、Issue、Pull Request、コメント内での引用符やリストに、新しいキーボードショートカットが使えるようになりました。 - * To add quotes, use cmd shift . on Mac, or ctrl shift . on Windows and Linux. - * To add an ordered list, use cmd shift 7 on Mac, or ctrl shift 7 on Windows and Linux. - * To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux. + * 引用符を追加するには、Macではcmd shift . Windows及びLinuxではctrl shift .としてください。 - See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts. + * 順序付きリストを追加するには、Macではcmd shift 7 Windows及びLinuxではctrl shift 7としてください。 + + * 順序無しリストを追加するには、Macではcmd shift 8 Windows及びLinuxではctrl shift 8としてください。 + + 利用可能なショートカットの完全なリストについては「[キーボードショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。 - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."' - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)." diff --git a/translations/ja-JP/data/reusables/actions/about-artifact-log-retention.md b/translations/ja-JP/data/reusables/actions/about-artifact-log-retention.md index 69137f4d460f..418f4013b6d0 100644 --- a/translations/ja-JP/data/reusables/actions/about-artifact-log-retention.md +++ b/translations/ja-JP/data/reusables/actions/about-artifact-log-retention.md @@ -1,9 +1,12 @@ -デフォルトでは、ワークフローによって生成された成果物とログファイルは、90日間保持された後自動的に削除されます。 この保持の期間は、リポジトリの種類によって調整できます。 +デフォルトでは、ワークフローによって生成された成果物とログファイルは、90日間保持された後自動的に削除されます。 + +{%- ifversion fpt or ghec %} +この保持の期間は、リポジトリの種類によって調整できます。 -{%- ifversion fpt or ghec or ghes %} - パブリックリポジトリの場合: この保持時間を1日から90日の間で変更できます。 +- For private{% ifversion ghec %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days. +{%- else %} +You can change this retention period to anywhere between 1 day or 400 days. {%- endif %} -- For private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days. - 保持期間をカスタマイズした場合、適用されるのは新しい成果物とログファイルに対してであり、既存のオブジェクトにさかのぼっては適用されません。 管理されたリポジトリ及びOrganizationについては、最大の保持期間は管理するOrganizationあるいはEnterpriseによって設定された上限を超えることはできません。 diff --git a/translations/ja-JP/data/reusables/actions/enable-debug-logging-cli.md b/translations/ja-JP/data/reusables/actions/enable-debug-logging-cli.md new file mode 100644 index 000000000000..1336bef7bd35 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enable-debug-logging-cli.md @@ -0,0 +1 @@ +To enable enable runner diagnostic logging and step debug logging for the re-run, use the `--debug` flag. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/enable-debug-logging.md b/translations/ja-JP/data/reusables/actions/enable-debug-logging.md new file mode 100644 index 000000000000..c82a497a1821 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/enable-debug-logging.md @@ -0,0 +1,3 @@ +{% if debug-reruns %} +1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**. ![Enable debug logging](/assets/images/help/repository/enable-debug-logging.png) +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/audit_log/git-events-export-limited.md b/translations/ja-JP/data/reusables/audit_log/git-events-export-limited.md new file mode 100644 index 000000000000..0dff88a4d484 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/git-events-export-limited.md @@ -0,0 +1,7 @@ +{% ifversion ghec %} +{% note %} + +**Note:** When you export Git events, events that were initiated via the web browser or the REST or GraphQL APIs are not included. For example, when a user merges a pull request in the web browser, changes are pushed to the base branch, but the Git event for that push is not included in the export. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md index ed87943a3db6..6052050a1d98 100644 --- a/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md +++ b/translations/ja-JP/data/reusables/code-scanning/run-additional-queries.md @@ -17,4 +17,4 @@ Any additional queries you want to run must belong to a 単一の _.ql_ ファイル、複数の _.ql_ ファイルを含むディレクトリ、_.qls_ クエリスイート定義ファイル、または任意の組み合わせを指定できます。 クエリスイートの定義に関する詳しい情報については「[{% data variables.product.prodname_codeql %}クエリスイートの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)」を参照してください。 {% endif %} -{% ifversion fpt or ghec %}`github/codeql/cpp/ql/src@main`というように、`github/codeql`リポジトリから直接クエリスイートを参照することはおすすめしません。 そういったクエリは、他のクエリで使われるのと同じ{% data variables.product.prodname_codeql %}のバージョンでコンパイルされているとは限らないので、分析の際にエラーが生じるかもしれません。{% endif %} +{% ifversion fpt or ghec %}We don't recommend referencing query suites directly from the `github/codeql` repository, for example, `github/codeql/cpp/ql/src@main`. Such queries would have to be recompiled, and may not be compatible with the version of {% data variables.product.prodname_codeql %} currently active on {% data variables.product.prodname_actions %}, which could lead to errors during analysis.{% endif %} diff --git a/translations/ja-JP/data/reusables/education/upgrade-organization.md b/translations/ja-JP/data/reusables/education/upgrade-organization.md deleted file mode 100644 index 22d44e5aa6e9..000000000000 --- a/translations/ja-JP/data/reusables/education/upgrade-organization.md +++ /dev/null @@ -1 +0,0 @@ -1. アップグレードしたいOrganizationのとなりの**Upgrade（アップグレード）**をクリックしてください。 ![アップグレードボタン](/assets/images/help/education/upgrade-org-button.png) diff --git a/translations/ja-JP/data/reusables/education/upgrade-page.md b/translations/ja-JP/data/reusables/education/upgrade-page.md deleted file mode 100644 index 3b7ff40d4367..000000000000 --- a/translations/ja-JP/data/reusables/education/upgrade-page.md +++ /dev/null @@ -1 +0,0 @@ -1. [Organization Upgrades（Organizationのアップグレード）](https://education.github.com/toolbox/offers/github-org-upgrades)ページ上の"Upgrade your organization（Organizationをアップグレードする）"に進んでください。 diff --git a/translations/ja-JP/data/reusables/enterprise_enterprise_support/support-holiday-availability.md b/translations/ja-JP/data/reusables/enterprise_enterprise_support/support-holiday-availability.md index 4475106f9862..2cd9e792600e 100644 --- a/translations/ja-JP/data/reusables/enterprise_enterprise_support/support-holiday-availability.md +++ b/translations/ja-JP/data/reusables/enterprise_enterprise_support/support-holiday-availability.md @@ -4,7 +4,7 @@ | Martin Luther King, Jr. Day | Third Monday in January | | Presidents' Day | Third Monday in February | | Memorial Day | Last Monday in May | -| Independence Day | July 5 | +| Independence Day | July 4 | | Labor Day | First Monday in September | | Veterans Day | November 11 | | Thanksgiving Day | Fourth Thursday in November | diff --git a/translations/ja-JP/data/reusables/pages/about-private-publishing.md b/translations/ja-JP/data/reusables/pages/about-private-publishing.md index 7072e6cb1d6c..cd9e54c71955 100644 --- a/translations/ja-JP/data/reusables/pages/about-private-publishing.md +++ b/translations/ja-JP/data/reusables/pages/about-private-publishing.md @@ -3,5 +3,5 @@ You can create {% data variables.product.prodname_pages %} sites that are publicly available on the internet. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also publish sites privately by managing access control for the site. {% elsif ghec %} Unless your enterprise uses -{% data variables.product.prodname_emus %}, you can choose to publish sites publicly or privately by managing access control for the site. +{% data variables.product.prodname_emus %}, you can choose to publish project sites publicly or privately by managing access control for the site. {% endif %} \ No newline at end of file diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index 93fdea6b65bf..a3a04f21f3cf 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -270,9 +270,9 @@ translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liqui translations/ja-JP/data/reusables/education/apply-for-team.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/actions-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,Listed in localization-support#489 -translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,rendering error +translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,Listed in localization-support#489 -translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,rendering error +translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/pages-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags