From 954aca0d7a1a2a5b5d9df7f89d02416586a2632b Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 17 May 2022 19:04:32 -0400 Subject: [PATCH] New translation batch for ja (#27765) * 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: Grace Park --- .../configuring-notifications.md | 8 +- .../managing-notifications-from-your-inbox.md | 34 ++-- .../viewing-contributions-on-your-profile.md | 3 - .../managing-your-theme-settings.md | 6 +- ...on-levels-for-a-user-account-repository.md | 2 +- .../metadata-syntax-for-github-actions.md | 8 +- .../about-self-hosted-runners.md | 2 +- .../autoscaling-with-self-hosted-runners.md | 2 +- .../events-that-trigger-workflows.md | 2 +- .../workflow-commands-for-github-actions.md | 22 +- .../content/admin/code-security/index.md | 4 +- ...pply-chain-security-for-your-enterprise.md | 4 +- .../index.md | 2 +- ...-vulnerability-data-for-your-enterprise.md | 2 +- .../about-github-connect.md | 50 ++--- ...enabling-dependabot-for-your-enterprise.md | 2 +- ...self-hosted-runners-for-your-enterprise.md | 4 +- ...-githubcom-actions-using-github-connect.md | 2 +- ...manually-syncing-actions-from-githubcom.md | 2 +- ...version-of-the-official-bundled-actions.md | 2 +- .../audit-log-events-for-your-enterprise.md | 6 +- ...s-for-github-actions-in-your-enterprise.md | 6 +- .../about-authentication-to-github.md | 11 +- .../creating-a-personal-access-token.md | 4 +- .../reviewing-your-security-log.md | 12 +- .../token-expiration-and-revocation.md | 4 +- ...updating-your-github-access-credentials.md | 2 +- .../about-billing-for-github-actions.md | 2 +- .../about-billing-for-github-packages.md | 4 +- .../configuring-code-scanning.md | 4 +- ...tting-up-code-scanning-for-a-repository.md | 8 +- ...g-code-scanning-alerts-in-pull-requests.md | 4 +- .../about-dependabot-alerts.md | 2 +- .../configuring-dependabot-alerts.md | 2 +- ...ing-notifications-for-dependabot-alerts.md | 4 +- .../dependabot/dependabot-alerts/index.md | 2 +- .../viewing-and-updating-dependabot-alerts.md | 6 +- .../about-dependabot-version-updates.md | 2 +- .../content/code-security/dependabot/index.md | 2 +- ...he-detection-of-vulnerable-dependencies.md | 4 +- .../github-security-features.md | 10 +- .../securing-your-organization.md | 6 +- .../securing-your-repository.md | 6 +- .../about-the-security-overview.md | 10 +- ...ltering-alerts-in-the-security-overview.md | 6 +- .../code-security/security-overview/index.md | 2 +- .../viewing-the-security-overview.md | 10 +- .../supply-chain-security/index.md | 2 +- .../about-dependency-review.md | 2 +- .../about-supply-chain-security.md | 2 +- .../about-the-dependency-graph.md | 2 +- .../configuring-dependency-review.md | 2 +- .../configuring-the-dependency-graph.md | 2 +- ...loring-the-dependencies-of-a-repository.md | 2 +- .../index.md | 2 +- .../troubleshooting-the-dependency-graph.md | 4 +- .../about-issue-and-pull-request-templates.md | 2 - ...ing-issue-templates-for-your-repository.md | 6 - ...ating-a-github-app-using-url-parameters.md | 2 +- ...g-and-authorizing-users-for-github-apps.md | 14 +- .../authorizing-oauth-apps.md | 2 +- .../getting-started-with-apps/about-apps.md | 2 +- .../webhooks/securing-your-webhooks.md | 2 +- .../webhooks/webhook-events-and-payloads.md | 28 ++- .../about-remote-repositories.md | 4 - .../about-github-advanced-security.md | 4 +- .../quickstart/communicating-on-github.md | 3 - .../get-started/using-github/github-mobile.md | 5 +- .../using-github/keyboard-shortcuts.md | 41 ++-- .../creating-gists.md | 2 - .../basic-writing-and-formatting-syntax.md | 5 +- ...ng-keywords-in-issues-and-pull-requests.md | 2 +- .../filtering-cards-on-a-project-board.md | 4 +- .../about-issues.md | 4 +- ...and-pull-requests-to-other-github-users.md | 4 +- ...-and-searching-issues-and-pull-requests.md | 13 +- .../linking-a-pull-request-to-an-issue.md | 10 +- ...ng-all-of-your-issues-and-pull-requests.md | 2 +- .../about-your-organization-dashboard.md | 2 +- .../about-team-discussions.md | 4 +- ...analysis-settings-for-your-organization.md | 2 +- ...ing-the-audit-log-for-your-organization.md | 18 +- .../repository-roles-for-an-organization.md | 28 +-- .../roles-in-an-organization.md | 2 +- ...e-team-maintainer-role-to-a-team-member.md | 5 +- translations/ja-JP/content/pages/index.md | 29 ++- .../changing-the-stage-of-a-pull-request.md | 8 +- .../requesting-a-pull-request-review.md | 2 +- .../about-pull-request-reviews.md | 2 +- ...ng-dependency-changes-in-a-pull-request.md | 2 +- .../comparing-commits.md | 4 +- .../about-merge-methods-on-github.md | 3 +- .../troubleshooting-required-status-checks.md | 3 - .../creating-a-new-repository.md | 6 +- .../creating-a-repository-from-a-template.md | 8 +- .../creating-a-template-repository.md | 4 +- ...ithub-actions-settings-for-a-repository.md | 4 +- ...fications-for-pushes-to-your-repository.md | 9 +- .../about-releases.md | 2 +- ...wing-your-repositorys-releases-and-tags.md | 2 - ...anding-connections-between-repositories.md | 2 +- .../getting-started-with-the-checks-api.md | 5 +- .../getting-started-with-the-rest-api.md | 4 +- .../overview/resources-in-the-rest-api.md | 2 +- .../understanding-the-search-syntax.md | 2 - .../searching-issues-and-pull-requests.md | 50 +++-- .../ja-JP/data/features/security-managers.yml | 2 +- ...y-overview-feature-specific-alert-page.yml | 8 + .../enterprise-server/3-2/11.yml | 4 +- .../enterprise-server/3-2/12.yml | 2 +- .../release-notes/enterprise-server/3-3/7.yml | 2 +- .../github-ae/2021-06/2021-12-06.yml | 2 +- .../github-ae/2022-05/2022-05-17.yml | 190 ++++++++++++++++++ .../actions/allow-specific-actions-intro.md | 4 +- .../actions/jobs/using-matrix-strategy.md | 2 +- .../reusables/actions/message-parameters.md | 2 +- .../deprecating_auth_with_query_parameters.md | 2 - .../audit_log/audit-log-action-categories.md | 6 +- .../filter-issues-and-pull-requests-tip.md | 2 - .../data/reusables/code-scanning/beta.md | 2 +- .../dependabot/dependabot-alerts-beta.md | 2 +- ...abot-alerts-dependency-graph-enterprise.md | 4 +- .../gated-features/dependency-review.md | 6 +- ...ification-delivery-method-customization.md | 2 +- ...nerable-dependency-notification-options.md | 4 +- ...security-overview-feature-specific-page.md | 1 + .../organizations/team_maintainers_can.md | 4 +- .../close-issues-using-keywords.md | 2 +- .../repositories/default-issue-templates.md | 3 +- .../repositories/dependency-review.md | 2 +- .../repositories/enable-security-alerts.md | 2 +- ...quash-and-rebase-linear-commit-hisitory.md | 2 +- .../repositories/start-line-comment.md | 2 +- .../reusables/repositories/suggest-changes.md | 2 +- .../data/reusables/secret-scanning/beta.md | 2 +- .../partner-secret-list-private-repo.md | 44 ++-- .../reusables/security-center/permissions.md | 1 + .../removes-personal-access-tokens.md | 2 +- .../webhooks/check_run_properties.md | 24 +-- .../webhooks/check_suite_properties.md | 20 +- .../webhooks/installation_properties.md | 2 +- translations/log/ja-resets.csv | 1 + 142 files changed, 606 insertions(+), 457 deletions(-) create mode 100644 translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml create mode 100644 translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml create mode 100644 translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md create mode 100644 translations/ja-JP/data/reusables/security-center/permissions.md diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fed0..9f48a72b7c27 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: | -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 42aacb7562c2..e63fea17575c 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ shortTitle: Manage from your inbox - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} @@ -133,20 +133,20 @@ For information about reducing noise from notifications for {% data variables.pr 更新を受信した理由で通知をフィルタするには、`reason:` クエリを使用できます。 たとえば、自分 (または自分が所属する Team) がプルリクエストのレビューをリクエストされたときに通知を表示するには、`reason:review-requested` を使用します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)」を参照してください。 -| クエリ | 説明 | -| ------------------------- | ----------------------------------------------------------------------------------------------------- | -| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | -| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | -| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | -| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | -| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | -| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | -| `reason:mention` | 直接@メンションされたとき。 | -| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| クエリ | 説明 | +| ------------------------- | ------------------------------------------------------------------------------------------ | +| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | +| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | +| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | +| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | +| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | +| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | +| `reason:mention` | 直接@メンションされたとき。 | +| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | リポジトリに対してセキュリティアラートが発行されたとき。{% endif %} -| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | -| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | -| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | +| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | +| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | +| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | {% ifversion fpt or ghec %} ### サポートされている `author:` クエリ @@ -161,7 +161,7 @@ Organization ごとに通知をフィルタするには、`org:` クエリを使 {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot %}カスタムフィルタ {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende {% data variables.product.prodname_dependabot %} の詳細については、「[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 78f74ca3f76a..c00c16fcab49 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -91,10 +91,7 @@ The contribution activity section includes a detailed timeline of your work, inc ![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." -{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index b862302ca957..bb0ba41aa2ea 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -18,7 +18,7 @@ shortTitle: Manage theme settings You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. +{% ifversion fpt or ghes > 3.2 or ghae or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% endif %} @@ -31,10 +31,10 @@ You may want to use a dark theme to reduce power consumption on certain devices, 1. 使いたいテーマをクリックしてください。 - If you chose a single theme, click a theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - If you chose to follow your system settings, click a day theme and a night theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 7c611a4533a6..d1656f5c76e3 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -43,7 +43,7 @@ The repository owner has full control of the repository. In addition to the acti | Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %} | Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %} | Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %} | Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %} 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 ffd131d0b36a..33e887c14b7a 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 @@ -223,7 +223,7 @@ runs: ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps. {% else %} **Required** The steps that you plan to run in this action. @@ -231,7 +231,7 @@ runs: #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The command you want to run. これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。 {% else %} **必須** 実行するコマンド。 これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。 @@ -261,7 +261,7 @@ runs: #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The shell where you want to run the command. [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set. {% else %} **必須** コマンドを実行するシェル。 [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set. @@ -314,7 +314,7 @@ steps: **オプション** コマンドを実行する作業ディレクトリを指定します。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` **Optional** Selects an action to run as part of a step in your job. アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されているDockerコンテナイメージ](https://hub.docker.com/)と同じリポジトリで定義されているアクションを使用できます。 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index c1e1ea251501..3c82ac9aa4e6 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources. * If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 502e37383f74..143e04db7988 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: issue-4462 + ghae: '*' type: overview --- diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md index 015ad4b13d45..a26c9bd19517 100644 --- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md @@ -24,7 +24,7 @@ Workflow triggers are events that cause a workflow to run. For more information Some events have multiple activity types. For these events, you can specify which activity types will trigger a workflow run. For more information about what each activity type means, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." Note that not all webhook events trigger workflows. -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md index 4657d2edc351..83f9e9745c45 100644 --- a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -99,18 +99,18 @@ core.setOutput('SELECTED_COLOR', 'green'); 以下の表は、ワークフロー内で使えるツールキット関数を示しています。 -| ツールキット関数 | 等価なワークフローのコマンド | -| --------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Accessible using environment file `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| ツールキット関数 | 等価なワークフローのコマンド | +| --------------------- | ---------------------------------------------------------- | +| `core.addPath` | Accessible using environment file `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` {% endif %} -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | -| `core.getInput` | 環境変数の`INPUT_{NAME}`を使ってアクセス可能 | -| `core.getState` | 環境変数の`STATE_{NAME}`を使ってアクセス可能 | -| `core.isDebug` | 環境変数の`RUNNER_DEBUG`を使ってアクセス可能 | +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | +| `core.getInput` | 環境変数の`INPUT_{NAME}`を使ってアクセス可能 | +| `core.getState` | 環境変数の`STATE_{NAME}`を使ってアクセス可能 | +| `core.isDebug` | 環境変数の`RUNNER_DEBUG`を使ってアクセス可能 | {%- if actions-job-summaries %} | `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` | {%- endif %} @@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## Setting a notice message diff --git a/translations/ja-JP/content/admin/code-security/index.md b/translations/ja-JP/content/admin/code-security/index.md index ae196fb959e8..970c4013fb7f 100644 --- a/translations/ja-JP/content/admin/code-security/index.md +++ b/translations/ja-JP/content/admin/code-security/index.md @@ -1,11 +1,11 @@ --- title: Managing code security for your enterprise shortTitle: Manage code security -intro: "You can build security into your developers' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain." +intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.' versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 55f6a3e42eec..83eaa9f80500 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -1,11 +1,11 @@ --- title: About supply chain security for your enterprise intro: You can enable features that help your developers understand and update the dependencies their code relies on. -shortTitle: About supply chain security +shortTitle: サプライチェーンのセキュリティについて permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index 4373e5a5e594..d1173126569d 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -4,7 +4,7 @@ shortTitle: サプライチェーンのセキュリティ intro: 'You can visualize, maintain, and secure the dependencies in your developers'' software supply chain.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 11620acda69c..dbd92d70c498 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: View vulnerability data permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md index 082bd40e29cd..54d17c56d4e9 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -10,9 +10,9 @@ topics: - GitHub Connect --- -## {% data variables.product.prodname_github_connect %} について +## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." @@ -26,22 +26,22 @@ After enabling {% data variables.product.prodname_github_connect %}, you will be After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. -| 機能 | 説明 | 詳細情報 | -| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -| Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | -| Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | +Feature | Description | More information | +------- | ----------- | ---------------- |{% ifversion ghes %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} +{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} +{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} +{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} +Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" +Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" -## Data transmission for {% data variables.product.prodname_github_connect %} +## Data transmission for {% data variables.product.prodname_github_connect %} When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection. {% ifversion ghes %} -- {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分 -- {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ -- {% data variables.product.prodname_ghe_server %} ライセンスの顧客名 +- The public key portion of your {% data variables.product.prodname_ghe_server %} license +- A hash of your {% data variables.product.prodname_ghe_server %} license +- The customer name on your {% data variables.product.prodname_ghe_server %} license - The version of {% data variables.product.product_location_enterprise %}{% endif %} - The hostname of {% data variables.product.product_location %} - The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.product.product_location %} @@ -62,16 +62,16 @@ When you enable {% data variables.product.prodname_github_connect %} or specific Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}. -| 機能 | Data | Which way does the data flow? | Where is the data used? | -| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} -| {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} -| Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} - -## 参考リンク +Feature | Data | Which way does the data flow? | Where is the data used? | +------- | ---- | --------- | ------ |{% ifversion ghes %} +Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} +{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} +{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} +{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} +{% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} +Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | +Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} | + +## Further reading - "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 2fe23408f4ac..0b56b432377e 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 97e1185a517e..fe6eedf9c634 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host 1. Deploy a self-hosted runner for your enterprise 1. Create a group to manage access to the runners available to your enterprise 1. Optionally, further restrict the repositories that can use the runner -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners {% endif %} @@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Automatically scale your self-hosted runners diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f539aeca8d38..7ea2bb0b09e9 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 1af5a98dfd73..3f5f8729685c 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 97e81a35467d..5d4d77063198 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." 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 6dbde9bee497..507b8550d5eb 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 @@ -188,7 +188,7 @@ topics: | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. | {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` カテゴリアクション | アクション | 説明 | @@ -226,7 +226,7 @@ topics: | `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `dependency_graph` カテゴリアクション | アクション | 説明 | @@ -1014,7 +1014,7 @@ topics: | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. | -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `repository_vulnerability_alert` カテゴリアクション | アクション | 説明 | diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 12de91d23eab..356faf8cfb9a 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -66,7 +66,7 @@ Enterprise 内のすべての Organization に対して {% data variables.produc 1. "Policies（ポリシー）"の下で、{% data reusables.actions.policy-label-for-select-actions-workflows %}を選択し、必要なアクション{% if actions-workflow-policy %}と再利用可能なワークフロー{% endif %}をリストに追加してください。 {% if actions-workflow-policy %} ![許可リストへのアクションと再利用可能なワークフローの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![許可リストへのアクションの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![許可リストへのアクションの追加](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) @@ -134,13 +134,13 @@ By default, when you create a new enterprise, `GITHUB_TOKEN` only has read acces {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. [Workflow permissions]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. **Save（保存）**をクリックして、設定を適用してください。 {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### {% data variables.product.prodname_actions %}がPull Requestの作成もしくは承認をできないようにする {% data reusables.actions.workflow-pr-approval-permissions-intro %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 71706449ff14..75df940d02b8 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub --- ## About authentication to {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} @@ -48,8 +48,8 @@ You can authenticate to {% data variables.product.product_name %} in your browse - **Username and password only** - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - - After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Two-factor authentication (2FA)** (recommended) - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} @@ -61,14 +61,13 @@ You can authenticate to {% data variables.product.product_name %} in your browse {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} - You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ## Authenticating with the API You can authenticate with the API in different ways. -- **Personal access tokens** +- **Personal access tokens** - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - **Web application flow** - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." @@ -81,7 +80,7 @@ You can access repositories on {% data variables.product.product_name %} from th ### HTTPS -You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 8c4e01f2edd2..84f1366ddc90 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -44,7 +44,7 @@ A token with no assigned scopes can only access public information. トークン {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. トークンにわかりやすい名前を付けます。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +5. トークンにわかりやすい名前を付けます。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. このトークンに付与するスコープ、すなわち権限を選択します。 トークンを使用してコマンドラインからリポジトリにアクセスするには、[**repo**] を選択します。 {% ifversion fpt or ghes or ghec %} @@ -80,5 +80,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac ## 参考リンク -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index 7997cdc75579..780d475eb6ad 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -28,15 +28,11 @@ The security log lists all actions performed within the last 90 days. 1. ユーザ設定サイドバーで [**Security log**] をクリックします。 ![セキュリティログのタブ](/assets/images/help/settings/audit-log-tab.png) {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## セキュリティログを検索する {% data reusables.audit_log.audit-log-search %} ### 実行されたアクションに基づく検索 -{% else %} -## セキュリティログでのイベントを理解する -{% endif %} セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。 @@ -109,10 +105,10 @@ The security log lists all actions performed within the last 90 days. ### `oauth_authorization` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | -| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| アクション | 説明 | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 0f1543d81307..16ff6d99c074 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -When a token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. +When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. @@ -24,7 +24,7 @@ This article explains the possible reasons your {% data variables.product.produc {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Token revoked after reaching its expiration date When you create a personal access token, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index e1fbc4ab741d..e7d54494fe74 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -58,7 +58,7 @@ See "[Reviewing your authorized integrations](/articles/reviewing-your-authorize {% ifversion not ghae %} -If you have reset your account password and would also like to trigger a sign-out from the GitHub Mobile app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." {% endif %} diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index 8f7438dd1ec2..1d0e9ef81755 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -48,7 +48,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e リポジトリが使用するストレージは、{% data variables.product.prodname_actions %}の成果物と{% data variables.product.prodname_registry %}の消費の合計のストレージです。 ストレージのコストは、アカウントが所有するすべてのリポジトリの合計の使用量です。 {% data variables.product.prodname_registry %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_registry %}の支払いについて](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。 - アカウントによる利用がこれらの制限を超え、消費の限度を0米ドル以上に設定しているなら、月あたりストレージのGBごとに0.25米ドル、そして{% data variables.product.prodname_dotcom %}ホストランナーが使用するオペレーティングシステムに応じた分の使用量ごとに支払うことになります。 {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。 + If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。 {% note %} diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index d9247cd9649e..1bbe77f65345 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage and $0.50 USD per GB of data transfer. +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index cccde8bdecc3..a462055e5afc 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 7649b34387fc..990c6e03c74b 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. @@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Reasons for the "Analysis not found" message {% else %} ### Reasons for the "Missing analysis" message {% endif %} -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 0facaadb22c4..66507b8e68ee 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,7 +28,7 @@ topics: ## About {% data variables.product.prodname_code_scanning %} results on pull requests In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} @@ -42,7 +42,7 @@ There are many options for configuring {% data variables.product.prodname_code_s For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 233364f4bf75..b73490579e06 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 86404653d84d..0694e287c817 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: Dependabotアラートの設定 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index 25dfe7bb325d..4cfb0647e318 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -31,7 +31,7 @@ topics: {% ifversion fpt or ghec %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)」を参照してください。 {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} デフォルトでは、EnterpriseのオーナーがEnterpriseにおいて通知のためのメールを設定していれば、あなたはメールで{% data variables.product.prodname_dependabot_alerts %}を受け取ることになります。 Enterpriseオーナーは、通知なしで{% data variables.product.prodname_dependabot_alerts %}を有効化することもできます。 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md index b57517edf796..4bbf2a61ca33 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index 6063d726f1cb..f3ac7bdeeeae 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -11,7 +11,7 @@ shortTitle: Dependabotアラートの表示 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ topics: {% note %} -**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 GitHubは、さらなる過去のPythonアドバイザリにさかのぼってデータを加えていっています。これは、随時追加されていっています。 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。 +**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。 {% endnote %} @@ -65,7 +65,7 @@ topics: 脆弱性のある呼び出しが検出されたアラートについては、アラートの詳細ページに追加情報が表示されます。 -- 関数が使われている場所、もしくは複数の呼び出しがある場合には最初の呼び出しがあるコードブロック。 +- One or more code blocks showing where the function is used. - 関数自体をリストしているアノテーション。関数が呼ばれている行へのリンク付きで。 !["Vulnerable call"ラベルの付いたアラートのアラート詳細ページを表示しているスクリーンショット](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 094cdaade53b..152a7623fc16 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Dependabotバージョンアップデート {% data variables.product.prodname_dependabot %} は、依存関係を維持する手間を省きます。 これを使用して、リポジトリが依存するパッケージおよびアプリケーションの最新リリースに自動的に対応できるようにすることができます。 -a _dependabot.yml_configurationファイルをリポジトリにチェックインすることにより、{% data variables.product.prodname_dependabot_version_updates %} を有効化します。 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 {% data variables.product.prodname_dependabot %} が古い依存関係を特定すると、プルリクエストを発行して、マニフェストを依存関係の最新バージョンに更新します。 ベンダーの依存関係の場合、{% data variables.product.prodname_dependabot %} はプルリクエストを生成して、古い依存関係を新しいバージョンに直接置き換えます。 テストに合格したことを確認し、プルリクエストの概要に含まれている変更履歴とリリースノートを確認して、マージします。 詳しい情報については「[{% data variables.product.prodname_dependabot %}のバージョンアップデートの設定](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/index.md index cb1f4984f916..2cfeef9d876a 100644 --- a/translations/ja-JP/content/code-security/dependabot/index.md +++ b/translations/ja-JP/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index 722d2e48bde4..86519f787b49 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ topics: * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md index 21c6e0e3f757..c32115569b8a 100644 --- a/translations/ja-JP/content/code-security/getting-started/github-security-features.md +++ b/translations/ja-JP/content/code-security/getting-started/github-security-features.md @@ -20,7 +20,7 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Available for all repositories {% endif %} ### Security policy @@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Dependency review Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} -{% ifversion ghec or ghes > 3.1 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams {% ifversion ghec %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md index ebb6dbe2c868..dd6785e84cbc 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md @@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. @@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review @@ -138,7 +138,7 @@ You can view and manage alerts from security features to address dependencies an {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md index 6ee9dc430b6f..f89d57da22e5 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing the dependency graph {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %} @@ -79,7 +79,7 @@ For more information, see "[About {% data variables.product.prodname_dependabot_ {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." diff --git a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md index 468aed1cfe46..0a965e2e3e0f 100644 --- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md @@ -1,13 +1,13 @@ --- title: About the security overview intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: About security overview --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ At the organization-level, the security overview displays aggregate and reposito {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### About the enterprise-level security overview -At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts or view all {% data variables.product.prodname_secret_scanning %} alerts from across your enterprise. +At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to. @@ -80,4 +80,4 @@ At the enterprise-level, the security overview displays aggregate and repository ### About the team-level security overview At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 6bf56ee52a6e..7022acece40a 100644 --- a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -1,10 +1,10 @@ --- title: セキュリティの概要でのアラートのフィルタリング intro: 特定カテゴリのアラートを表示させるためのフィルタの利用 -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: アラートのフィルタリング --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/index.md b/translations/ja-JP/content/code-security/security-overview/index.md index 06fbccfd1c07..f6a347730117 100644 --- a/translations/ja-JP/content/code-security/security-overview/index.md +++ b/translations/ja-JP/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 一カ所でOrganization内のセキュリティアラートを表示、 product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: diff --git a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md index 1608092c5d49..6a99b307f8cb 100644 --- a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md @@ -1,7 +1,7 @@ --- title: セキュリティの概要の表示 intro: セキュリティの概要で利用できる様々なビューへのアクセス -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: セキュリティの概要の表示 --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -28,7 +28,8 @@ shortTitle: セキュリティの概要の表示 1. アラートの種類に対する集約された情報を見るには、**Show more（さらに表示）**をクリックしてください。 ![さらに表示ボタン](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} {% if security-overview-views %} -1. あるいは、左のサイドバーを使ってセキュリティ機能ごとに情報をフィルタリングすることもできます。 それぞれのページで、各機能に固有のフィルタを使って検索を微調整できます。 ![Code scanning固有のページのスクリーンショット](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) +{% data reusables.organizations.security-overview-feature-specific-page %} + ![Code scanning固有のページのスクリーンショット](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## Organizationに渡るアラートの表示 @@ -42,6 +43,9 @@ shortTitle: セキュリティの概要の表示 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. ひだりのサイドバーで{% octicon "shield" aria-label="The shield icon" %}**Code Security（コードセキュリティ）**をクリックしてください。 +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## リポジトリのアラートの表示 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/index.md b/translations/ja-JP/content/code-security/supply-chain-security/index.md index 93a4d082a958..817b3f524c91 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 44eb046834e1..95e730d35912 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -6,7 +6,7 @@ shortTitle: 依存関係のレビュー versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 0518b8bf9f81..81bc60f55102 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 409595d281ca..1b04851134b2 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 471d08238414..e9ea74821da1 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -5,7 +5,7 @@ shortTitle: 依存関係レビューの設定 versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index 2b141a43f8d9..6f7f78ff806c 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index bd87958a338f..e5a6efe11992 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 17e72a032a97..0b18f55b8648 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: ソフトウェアサプライチェーンの理解 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index 6de1b7a25da5..0fe9cbaf0e6a 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -59,4 +59,4 @@ Yes, the dependency graph has two categories of limits: - "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} \ No newline at end of file +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index 61015343ad42..b7cdc018d368 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ Issue テンプレートは、コントリビューターが Issue の内容を Issue フォームでは、{% data variables.product.prodname_dotcom %} フォームスキーマを使用して、Web フォームフィールドを持つテンプレートを作成できます。 コントリビューターが Issue フォームを使用して Issue をオープンすると、フォーム入力は標準のマークダウン Issue コメントに変換されます。 さまざまな入力タイプを指定し、必要に応じて入力を設定して、コントリビューターがリポジトリで実行可能な Issue をオープンすることができるようにすることができます。 詳しい情報については、「[リポジトリの Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)」および「[Issue フォームの構文](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)」を参照してください。 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %}詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)」を参照してください。 -{% endif %} Issue テンプレートは、リポジトリのデフォルトブランチ中の隠しディレクトリ `.github/ISSUE_TEMPLATE` に保存されます。 テンプレートを他のブランチで作成した場合、それをコラボレーターが使うことはできません。 Issue テンプレートのファイル名では大文字と小文字は区別されず、*.md* 拡張子が必要です。{% ifversion fpt or ghec %} Issue フォームで作成された Issue テンプレートには、*.yml* 拡張子が必要です。{% endif %} {% data reusables.repositories.valid-community-issues %} diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 7d360b105a6d..14173e6d51f1 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: 設定 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Issue テンプレートを作成する -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. [Features] セクションの [Issues] の下で、[**Set up templates**] をクリックします。 ![[Start template setup] ボタン](/assets/images/help/repository/set-up-templates.png) @@ -62,7 +58,6 @@ Issueフォームのレンダリングバージョンは次のとおりです。 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## テンプレート選択画面を設定する {% data reusables.repositories.issue-template-config %} @@ -99,7 +94,6 @@ contact_links: {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 329289c1f7d3..9916fa1ad50b 100644 --- a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -89,7 +89,7 @@ webhook を保護するためにシークレットが必要なアプリケーシ | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/commits#commit-statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghes or ghae or ghec %} | `vulnerability_alerts` | Grants access to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in a repository. See "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. `none`、`read` のいずれかです。{% endif %} | `Watch` | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。 | diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 0bc31e054b6c..7b20e25cbfc8 100644 --- a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -239,8 +239,8 @@ While most of your API インタラクションのほとんどは、サーバー * [デプロイメントの一覧表示](/rest/reference/deployments#list-deployments) * [デプロイメントの作成](/rest/reference/deployments#create-a-deployment) -* [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [デプロイメントの削除](/rest/reference/deployments#delete-a-deployment){% endif %} +* [Get a deployment](/rest/reference/deployments#get-a-deployment) +* [Delete a deployment](/rest/reference/deployments#delete-a-deployment) #### イベント @@ -422,14 +422,12 @@ While most of your API インタラクションのほとんどは、サーバー * [Organizationのためのpre-receiveフックの強制の削除](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### OrganizationのTeamのプロジェクト * [Teamプロジェクトの一覧表示](/rest/reference/teams#list-team-projects) * [プロジェクトのTeamの権限のチェック](/rest/reference/teams#check-team-permissions-for-a-project) * [Teamのプロジェクト権限の追加あるいは更新](/rest/reference/teams#add-or-update-team-project-permissions) * [Teamからのプロジェクトの削除](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### OrganizationのTeamリポジトリ @@ -575,7 +573,7 @@ While most of your API インタラクションのほとんどは、サーバー #### リアクション -{% ifversion fpt or ghes or ghae or ghec %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Delete a reaction](/rest/reference/reactions) * [コミットコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [コミットコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [Issueへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-an-issue) @@ -587,13 +585,13 @@ While most of your API インタラクションのほとんどは、サーバー * [Teamディスカッションコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Teamディスカッションコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [Teamディスカッションへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Teamディスカッションへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Issueへのリアクションの削除](/rest/reference/reactions#delete-an-issue-reaction) * [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Pull Requestのコメントへのリアクションの削除](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Teamディスカッションへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-reaction) -* [Team ディスカッションのコメントへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### リポジトリ @@ -707,11 +705,9 @@ While most of your API インタラクションのほとんどは、サーバー * [リポジトリのREADMEの取得](/rest/reference/repos#get-a-repository-readme) * [リポジトリのライセンスの取得](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### リポジトリのイベントのディスパッチ * [リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event) -{% endif %} #### リポジトリのフック diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index fc1883a9d7fa..473b1175ead5 100644 --- a/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -338,7 +338,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr * "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## Further reading diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md index eec4a49f78d9..b2ddf4a8d63d 100644 --- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md @@ -84,7 +84,7 @@ Keep these ideas in mind when using personal access tokens: * You can perform one-off cURL requests. * You can run personal scripts. * Don't set up a script for your whole team or company to use. -* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} ## Determining which integration to build diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index f711c1f02bd6..a0fae35e8fcd 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ end * プレーンな `==` 演算子を使用することは**お勧めしません**。 [`secure_compare`][secure_compare] のようなメソッドは、「一定時間」の文字列比較を実行します。これは、通常の等式演算子に対する特定のタイミング攻撃を軽減するのに役立ちます。 -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 070c805e2677..ba0df5ca7cf0 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -353,10 +353,10 @@ webhook イベントは、登録したドメインの特異性に基づいてト ### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------ | ------------------------------------------- | --------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} -| `deployment` | `オブジェクト` | The [deployment](/rest/reference/deployments#list-deployments). | +| キー | 種類 | 説明 | +| ------------ | -------- | -------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `created `になりうる。 | +| `deployment` | `オブジェクト` | [デプロイメント](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -378,14 +378,14 @@ webhook イベントは、登録したドメインの特異性に基づいてト ### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ---------------------------------- | ------------------------------------------- | --------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} -| `deployment_status` | `オブジェクト` | The [deployment status](/rest/reference/deployments#list-deployment-statuses). | -| `deployment_status["state"]` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | -| `deployment_status["target_url"]` | `string` | ステータスに追加されたオプションのリンク。 | -| `deployment_status["description"]` | `string` | オプションの人間可読の説明がステータスに追加。 | -| `deployment` | `オブジェクト` | The [deployment](/rest/reference/deployments#list-deployments) that this status is associated with. | +| キー | 種類 | 説明 | +| ---------------------------------- | -------- | -------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `created `になりうる。 | +| `deployment_status` | `オブジェクト` | [デプロイメントステータス](/rest/reference/deployments#list-deployment-statuses)。 | +| `deployment_status["state"]` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | +| `deployment_status["target_url"]` | `string` | ステータスに追加されたオプションのリンク。 | +| `deployment_status["description"]` | `string` | オプションの人間可読の説明がステータスに追加。 | +| `deployment` | `オブジェクト` | このステータスが関連付けられている [デプロイメント](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1154,7 +1154,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch このイベントは、{% data variables.product.prodname_github_app %} が「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。 @@ -1166,7 +1165,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus ### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} ## リポジトリ @@ -1490,7 +1488,7 @@ The security advisory dataset also powers the GitHub {% data variables.product.p {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md index b6f29e94235d..e7ad7cc18e5a 100644 --- a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -81,14 +81,10 @@ SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git {% endtip %} -{% ifversion fpt or ghes or ghae or ghec %} - ## {% data variables.product.prodname_cli %} を使ってクローンを作成する {% data variables.product.prodname_cli %} をインストールして、ターミナルで {% data variables.product.product_name %} ワークフローを使用することもできます。 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。 -{% endif %} - {% ifversion not ghae %} ## Subversion を使って複製する diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md index 7616cc276e6a..8eaea418ace5 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md @@ -30,7 +30,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} @@ -113,4 +113,4 @@ For more information on starter workflows, see "[Setting up {% data variables.pr - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" {% endif %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md index 73f5cb509ba1..7f7636461aec 100644 --- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md +++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md @@ -117,7 +117,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Scenarios for team discussions - I have a question that's not necessarily related to specific files in the repository. @@ -140,8 +139,6 @@ The `octocat` team member posted a team discussion, informing the team of variou - There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. - Material about the April All Hands is now available for all team members to view. -{% endif %} - ## 次のステップ These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. diff --git a/translations/ja-JP/content/get-started/using-github/github-mobile.md b/translations/ja-JP/content/get-started/using-github/github-mobile.md index e99da062ad19..fe88929e61ca 100644 --- a/translations/ja-JP/content/get-started/using-github/github-mobile.md +++ b/translations/ja-JP/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ With {% data variables.product.prodname_mobile %} you can: - Read, review, and collaborate on issues and pull requests - Search for, browse, and interact with users, repositories, and organizations - Receive a push notification when someone mentions your username -{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication{% endif %} +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Installing {% data variables.product.prodname_mobile %} To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md index 1d7099004372..3c93630690ce 100644 --- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md @@ -28,11 +28,11 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a ## サイト全体のショートカット -| キーボードショートカット | 説明 | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| S または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 | -| G N | 通知に移動します。 詳しい情報については、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 | -| Esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | +| キーボードショートカット | 説明 | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| S または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 | +| G N | 通知に移動します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」を参照してください。 | +| Esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | {% if command-palette %} @@ -106,7 +106,6 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a {% endif %} | R | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | - ## Issue およびプルリクエストのリスト | キーボードショートカット | 説明 | @@ -135,16 +134,15 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a ## プルリクエストの変更 -| キーボードショートカット | 説明 | -| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| C | プルリクエスト内のコミットのリストを開きます | -| T | プルリクエストで変更されたファイルのリストを開きます | -| J | リストで選択を下に移動します | -| K | リストで選択を上に移動します | -| Command+Shift+Enter | プルリクエストの差分にコメントを 1 つ追加します | -| Alt およびクリック | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.|{% ifversion fpt or ghes or ghae or ghec %} -| Click, then Shift and click | Comment on multiple lines of a pull request by clicking a line number, holding Shift, then clicking another line number. 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。 -{% endif %} +| キーボードショートカット | 説明 | +| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | プルリクエスト内のコミットのリストを開きます | +| T | プルリクエストで変更されたファイルのリストを開きます | +| J | リストで選択を下に移動します | +| K | リストで選択を上に移動します | +| Command+Shift+Enter | プルリクエストの差分にコメントを 1 つ追加します | +| Alt およびクリック | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**. | +| Click, then Shift and click | Comment on multiple lines of a pull request by clicking a line number, holding Shift, then clicking another line number. 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。 | ## プロジェクトボード @@ -200,21 +198,14 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a {% endif %} ## 通知 -{% ifversion fpt or ghes or ghae or ghec %} + | キーボードショートカット | 説明 | | ----------------------------- | ------------ | | E | 完了済としてマークします | | Shift+U | 未読としてマークします | -| Shift+I | 既読としてマークします | +| Shift+I | 既読としてマーク | | Shift+M | サブスクライブ解除します | -{% else %} - -| キーボードショートカット | 説明 | -| -------------------------------------------- | ------------ | -| E or I or Y | 既読としてマークします | -| Shift+M | スレッドをミュートします | -{% endif %} ## ネットワークグラフ diff --git a/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 00a5333f72a5..ce5486664ce3 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -60,7 +60,6 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, Follow the steps below to create a gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. @@ -68,7 +67,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. Alternatively, you can drag and drop a text file from your desktop directly into the editor. {% endnote %} -{% endif %} 1. Sign in to {% data variables.product.product_name %}. 2. Navigate to your {% data variables.gists.gist_homepage %}. 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 348416cb7527..47e061b38898 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 @@ -29,7 +29,6 @@ When you use two or more headings, GitHub automatically generates a table of con ![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png) - ## スタイル付きテキスト コメントフィールドと `.md` ファイルでは、太字、斜体、または取り消し線のテキストで強調を示すことができます。 @@ -235,7 +234,7 @@ If a task list item description begins with a parenthesis, you'll need to escape ## 人や Team のメンション -{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、@ に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知の詳細は、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 +{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、@ に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知に関する詳しい情報については「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」を参照してください。 {% note %} @@ -296,7 +295,7 @@ For more information about building a {% data variables.product.prodname_github_ テキスト行の間に空白行を残すことで、新しいパラグラフを作成できます。 -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Footnotes You can add footnotes to your content by using this bracket syntax: diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index 1893824f5816..095ed3c125f1 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## Pull RequestをIssueにリンクする -To link a pull request to an issue to{% ifversion fpt or ghes or ghae or ghec %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. For example, `Closes #10` or `Fixes octo-org/octo-repo#100`. +To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. For example, `Closes #10` or `Fixes octo-org/octo-repo#100`. * close * closes diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 37d11d280637..300f1beadf49 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,8 +30,8 @@ shortTitle: ボード上のカードのフィルタ - `status:pending`、`status:success`、または `status:failure` を使用して、カードをチェックステータスでフィルタリングする - `type:issue`、`type:pr`、または `type:note` を使用して、カードをタイプでフィルタリングする - `is:open`、`is:closed`、または `is:merged`と、`is:issue`、`is:pr`、または `is:note` とを使用して、カードをステータスとタイプでフィルタリングする -- `linked:pr`を使用してクローズしているリファレンスによってプルリクエストにリンクされている Issue でカードをフィルタリングする{% ifversion fpt or ghes or ghae or ghec %} -- `repo:ORGANIZATION/REPOSITORY` を使用して、Organization 全体のプロジェクトボード内のリポジトリでカードをフィルタリングする{% endif %} +- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- `repo:ORGANIZATION/REPOSITORY` を使用して、Organization 全体のプロジェクトボード内のリポジトリでカードをフィルタリングする 1. フィルタリングしたいカードが含まれるプロジェクトボードに移動します。 2. プロジェクトのカード列の上で、[Filter cards] 検索バーをクリックして検索クエリを入力し、カードをフィルタリングします。 ![カードのフィルタリング検索バー](/assets/images/help/projects/filter-card-search-bar.png) diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md index 1bbf0bceba90..3caa42054967 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md @@ -22,7 +22,7 @@ topics: Issueを使って、開発が行われる{% data variables.product.company_short %}上での作業を追跡できます。 他のIssueもしくはPull Request内のIssueにメンションすると、そのIssueのタイムラインにはクロスリファレンスが反映され、関連する作業を追跡できるようになります。 作業が進行中であることを示すために、Pull RequestにIssueをリンクできます。 Pull Requestがマージされると、リンクされたIssueは自動的にクローズされます。 -キーワードに関する詳しい情報については「[Pull RequestのIssueへのリンク](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。 +キーワードに関する詳しい情報については「[Pull RequestのIssueへのリンク](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。 ## 素早いIssueの作成 @@ -36,7 +36,7 @@ Issueは様々な方法で作成できるので、ワークフローで最も便 ## 最新情報の確認 -Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 詳しい情報については{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」{% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications)」{% endif %}及び「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。 +Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." ## コミュニティの管理 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index 692e7bc8f535..bfb120007f8f 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,9 +19,9 @@ shortTitle: Issue及びPRのアサイン ## Issue およびPull Requestをアサインされた人について -You can assign multiple people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 +自身、該当する Issue またはPull Requestにコメントした任意の人、リポジトリへの書き込み権限がある任意の人、およびリポジトリの読み取り権限がある Organization メンバーを含めて、複数人を各 Issue またはPull Requestにアサインできます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 -Issues and pull requests in public repositories, and in private repositories for a paid account, can have up to 10 people assigned. Private repositories on the free plan are limited to one person per issue or pull request. +パブリックリポジトリのIssue及びPull Request、そして有料アカウントのプライベートリポジトリでは、最大10人を割り当てできます。 無料プランのプライベートリポジトリでは、IssueあるいはPull Requestごとに1人に制限されます。 ## 個別の Issue またはPull Requestを割り当てる diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index 1cc1f3df5cfd..d196d100332e 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -173,13 +173,11 @@ Issue およびPull Requestの検索用語により、次のことができま {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} Issueについては、以下も検索に利用できます。 -- クローズしているリファレンス`linked:pr`によってPull RequestにリンクされているIssueのフィルタリング -{% endif %} +- クローズしているリファレンス`linked:pr`によってプルリクエストにリンクされているIssueのフィルタリング -Pull Requestについては、検索を利用して以下の操作もできます。 +プルリクエストについては、検索を利用して以下の操作もできます。 - [ドラフト](/articles/about-pull-requests#draft-pull-requests)Pull Requestのフィルタリング: `is:draft` - まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないPull Requestのフィルタリング: `state:open type:pr review:none` - マージされる前に[レビューを必要とする](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)Pull Requestのフィルタリング: `state:open type:pr review:required` @@ -188,8 +186,8 @@ Pull Requestについては、検索を利用して以下の操作もできま - [レビュー担当者](/articles/about-pull-request-reviews/)によるPull Requestのフィルタリング: `state:open type:pr reviewed-by:octocat` - [レビューを要求された](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)特定のユーザーによるPull Requestのフィルタリング: `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} - 誰かから直接レビューを求められたPull Requestのフィルタリング:`state:open type:pr user-review-requested:@me`{% endif %} -- レビューを要求されたチームによるPull Requestのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- プルリクエストでクローズできるIssueにリンクされているPull Requestのフィルタリング: `linked:issue`{% endif %} +- レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom` +- プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue` ## Issue およびPull Requestをソートする @@ -211,10 +209,9 @@ Pull Requestについては、検索を利用して以下の操作もできま ソートの選択を解除するには、[**Sort**] > [**Newest**] をクリックします。 - ## フィルターを共有する -一定の Issue およびPull Requestをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 +一定の Issue およびプルリクエストをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 Issue が生成した URL は、どのユーザにも送れます。そして、あなたが見ているフィルタビューと同じフィルタで表示できます。 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 983a85c4ee5b..3b37ed1b8208 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -27,7 +27,7 @@ shortTitle: IssueへのPRのリンク ## リンクされたIssueとPull Requestについて -{% ifversion fpt or ghes or ghae or ghec %}手動で、または{% endif %}Pull Requestの説明でサポートされているキーワードを使用して、IssueをPull Requestにリンクすることができます。 +You can link an issue to a pull request manually or using a supported keyword in the pull request description. Pull Requestが対処するIssueにそのPull Requestをリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。 @@ -57,16 +57,15 @@ Pull Requestの説明もしくはコミットメッセージ中でサポート | Issueが別のリポジトリにある | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | 複数の Issue | Issueごとに完全な構文を使用 | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% ifversion fpt or ghes or ghae or ghec %}手動でリンクを解除できるのは、手動でリンクされたPull Requestだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、Pull Requestの説明を編集してそのキーワードを削除する必要があります。{% endif %} +Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むPull Requestは、リンクされたPull Requestとしてリストされません。 -{% ifversion fpt or ghes or ghae or ghec %} ## 手動でPull RequestをIssueにリンクする -リポジトリへの書き込み権限があるユーザなら誰でも、手動でPull RequestをIssueにリンクできます。 +リポジトリへの書き込み権限があるユーザなら誰でも、手動でプルリクエストをIssueにリンクできます。 -手動で1つのPull Requestごとに最大10個のIssueをリンクできます。 IssueとPull Requestは同じリポジトリになければなりません。 +手動で1つのプルリクエストごとに最大10個のIssueをリンクできます。 Issueとプルリクエストは同じリポジトリになければなりません。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} @@ -77,7 +76,6 @@ Pull Requestの説明もしくはコミットメッセージ中でサポート 4. 右のサイドバーで、[**Linked issues**] をクリックします。 ![右サイドバーの [Linked issues]](/assets/images/help/pull_requests/linked-issues.png) {% endif %} 5. Pull RequestにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index 25bc309b45c5..cdb1222e306d 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ Issue およびPull Requestダッシュボードは、すべてのページの ## 参考リンク -- {% ifversion fpt or ghes or ghae or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}「[Watch しているリポジトリのリスト](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}」 +- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index ea8baf685ec4..f330154a85fe 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ shortTitle: Organizationダッシュボード ニュースフィードの [All activity] セクションでは、Organization 内の他の Team やリポジトリからの更新情報を見ることができます。 -[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 詳細は、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}」[リポジトリの Watch と Watch 解除](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}」および「[人をフォローする](/articles/following-people)」を参照してください。 +[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)." たとえば Organization のニュースフィードは Organization 内の誰かが以下のようなことをしたときに 更新情報を知らせます: - 新しいブランチを作成する diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md index 04845b1e7271..aa01ec69dbc3 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ When someone posts or replies to a public discussion on a team's page, members o {% tip %} -**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)." {% endtip %} @@ -40,7 +40,7 @@ By default, if your username is mentioned in a team discussion, you'll receive n To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions. -For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." +For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)." {% ifversion fpt or ghec %} diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 8fd6ad0d7788..31574c549c89 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -162,5 +162,5 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security - "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} 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 40c99cecccee..401665144c8c 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 @@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} @@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### `organization_label` category actions | Action | Description @@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -{% endif %} - ### `oauth_application` category actions | Action | Description @@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator. | `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. | `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 1ca5404bd74e..aeba62732d69 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -158,25 +158,25 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ このセクションでは、{% data variables.product.prodname_advanced_security %}の機能のようなセキュリティ機能に必要なアクセス権を知ることができます。 -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae or ghec %} +| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | -| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} -| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} +| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** {% endif %} -| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | +| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} | -| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} -| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** {% endif %} [1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。 diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 7f2a460d2a09..3332ed60fa47 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -146,7 +146,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ {% endif %} | OrganizationのPull Requestレビューを管理（[OrganizationでのPull Requestのレビューの管理](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)」を参照） | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | Organization のアクション | オーナー | メンバー | セキュリティマネージャー | diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index bfa0005f32dd..0b6c9670e4ba 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ permissions: Organization owners can promote team members to team maintainers. - [Teamディスカッションの削除](/articles/managing-disruptive-comments/#deleting-a-comment) - [OrganizationのメンバーのTeamへの追加](/articles/adding-organization-members-to-a-team) - [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team) -- リポジトリへのTeamのアクセスの削除{% ifversion fpt or ghes or ghae or ghec %} -- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- リポジトリへのTeamのアクセス権の削除 +- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [プルリクエストのスケジュールされたリマインダーの管理](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## Organization メンバーをチームメンテナに昇格させる Organizationメンバーをチームメンテナに昇格するには、そのメンバーはTeamのメンバーになっていなければなりません。 diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md index 44ce4c4065be..64e5295d615a 100644 --- a/translations/ja-JP/content/pages/index.md +++ b/translations/ja-JP/content/pages/index.md @@ -1,7 +1,34 @@ --- title: GitHub Pagesのドキュメンテーション shortTitle: GitHub Pages -intro: '{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上のリポジトリから直接Webサイトを作成できます。' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index 0cf4c53036d3..d18993b04bfb 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: プルリクエストのステージの変更 -intro: 'プルリクエストのドラフトをレビュー準備完了としてマークしたり{% ifversion fpt or ghae or ghes or ghec %}、プルリクエストをドラフトに変換したりすることができます{% endif %}。' +intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -22,20 +22,16 @@ shortTitle: Change the state {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. プルリクエストのリストで、レビューの準備ができたことを示すマークを付けたいプルリクエストクリックします。 3. マージボックスで、[**Ready for review**] をクリックします。 ![[Ready for review] ボタン](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## プルリクエストをドラフトに変換する プルリクエストはいつでもドラフトに変換できます。 たとえば、ドラフトではなくプルリクエストを誤ってオープンした場合、または対処の必要があるプルリクエストについてのフィードバックを受け取った場合、プルリクエストをドラフトに変換して、さらなる変更が必要であることを示すことができます。 プルリクエストをレビューの準備完了として再度マークするまで、プルリクエストをマージすることはできません。 プルリクエストの通知をすでにサブスクライブしているユーザは、プルリクエストをドラフトに変換するときにサブスクライブ解除されません。 @@ -45,8 +41,6 @@ shortTitle: Change the state 3. 右側のサイドバーの [Reviewers] で、[**Convert to draft**] をクリックします。 ![[ドラフトに変換] リンク](/assets/images/help/pull_requests/convert-to-draft-link.png) 4. [**Convert to draft**] をクリックします。 ![ドラフト確認に変換](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## 参考リンク - [プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests) diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index a35b47786628..e34db9436fa5 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ Repositories belong to a personal account (a single individual owner) or an orga To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. -Organization members with write access can also assign a pull request review to any person or team with read access to a repository. リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% ifversion fpt or ghae or ghes or ghec %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 1bd4de46a877..272ea4003252 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -22,7 +22,7 @@ shortTitle: About PR reviews {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[Pull Request レビューをリクエストする](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)」を参照してください。 {% ifversion fpt or ghae or ghes or ghec %}Teamメンバーのサブセットを指定して、Team 全体に代わって自動で割り当てることができます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[Pull Request レビューをリクエストする](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)」を参照してください。 You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." レビューにより、提案された変更についての議論がなされ、その変更がリポジトリのコントリビューションのガイドラインやその他の品質標準を満たすことを保証しやすくなります。 コードの特定の種類や領域に対して、どの個人や Team をオーナーとするかを、CODEOWNERS ファイルで定義できます。 プルリクエストが、定義されたオーナーを持っているコードを変更するものである場合、オーナーである個人あるいはTeam がレビューを担当するよう、自動的にリクエストされます。 詳細は「[コードオーナーについて](/articles/about-code-owners/)」を参照してください。 diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 461a58b8602d..de7328d0d4a5 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index a58f26d3fbd8..e269a9dd163b 100644 --- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -31,9 +31,9 @@ compare の最も一般的な使い方は、新しいプルリクエストを開 ## タグを比較する -リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 {% ifversion fpt or ghae or ghes or ghec %} 詳しい情報については、「[リリースを比較する](/github/administering-a-repository/comparing-releases)」を参照してください。{% endif %} +リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." -{% ifversion fpt or ghae or ghes or ghec %}タグを比較するには、ページ上部の `compare` ドロップダウンメニューからタグ名を選択できます。{% else %}ブランチ名を入力する代わりに、`compare` ドロップダウンメニューにタグの名前を入力します。{% endif %} +To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. 2 つのタグ間を比較する例については、[こちらをクリック](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)してください。 diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index cd840c5c084f..3d66e04fecfe 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -27,8 +27,7 @@ shortTitle: About merge methods {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-linear-history)」を参照してください。{% endif %} +デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-linear-history)」を参照してください。 ## マージコミットのsquash diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index 0210913bcfc2..8b031ae16205 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -37,14 +37,11 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Conflicts between head commit and test merge commit テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、そのテストマージコミットは必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プル](/rest/reference/pulls#get-a-pull-request)」を参照してください。 ![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## Handling skipped but required checks diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index 2627f92c11c4..ed35fc0aa235 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -26,17 +26,15 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} -2. また、既存のリポジトリのディレクトリ構造とファイルを持つリポジトリを作成するには、[**Choose a template**] ドロップダウンでテンプレートリポジトリを選択します。 あなたが所有するテンプレートリポジトリ、あなたがメンバーとして属する Organization が所有するテンプレートリポジトリ、使ったことがあるテンプレートリポジトリが表示されます。 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. 必要に応じて、テンプレートを使用する場合、デフォルトのブランチだけでなく、テンプレートのすべてのブランチからのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +2. また、既存のリポジトリのディレクトリ構造とファイルを持つリポジトリを作成するには、[**Choose a template**] ドロップダウンでテンプレートリポジトリを選択します。 あなたが所有するテンプレートリポジトリ、あなたがメンバーとして属する Organization が所有するテンプレートリポジトリ、使ったことがあるテンプレートリポジトリが表示されます。 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png) +3. 必要に応じて、テンプレートを使用する場合、デフォルトのブランチだけでなく、テンプレートのすべてのブランチからのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) 3. [Owner] ドロップダウンで、リポジトリを作成するアカウントを選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 8fb810fb6d49..0f341a6607e0 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -19,17 +19,13 @@ shortTitle: Create from a template リポジトリに対する読み取り権限があるユーザなら誰でも、テンプレートからリポジトリを作成できます。 詳細は「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照してください。 -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリをテンプレートから作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} テンプレートリポジトリのデフォルトブランチのみからディレクトリ構造とファイルを含めるか、すべてのブランチを含めるかを選択できます。 Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. -{% endif %} テンプレートからリポジトリを作成することは、リポジトリをフォークすることに似ていますが、以下の点で異なります: - 新しいフォークは、親リポジトリのコミット履歴すべてを含んでいますが、テンプレートから作成されたリポジトリには、最初は 1 つのコミットしかありません。 @@ -44,7 +40,7 @@ shortTitle: Create from a template 2. ファイルの一覧の上にある [**Use this template**] をクリックします。 ![[Use this template] ボタン](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} -6. 必要に応じて、デフォルトのブランチだけでなく、テンプレートのすべてのブランチのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +{% data reusables.repositories.choose-repo-visibility %} +6. 必要に応じて、デフォルトのブランチだけでなく、テンプレートのすべてのブランチのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. [**Create repository from template**] をクリックします。 diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index 5628d199e021..98a4fa8d7a0d 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: テンプレートリポジトリを作成する -intro: '既存のリポジトリをテンプレートにして、自分や他の人が同じディレクトリ構造{% ifversion fpt or ghae or ghes or ghec %}、ブランチ、{% endif %}およびファイルで新しいリポジトリを生成できるようにすることができます。' +intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: Create a template repo テンプレートリポジトリを作成するには、リポジトリを作成して、そのリポジトリをテンプレート化する必要があります。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% ifversion fpt or ghae or ghes or ghec %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." +After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 9f73f186dc49..d73455b3d43b 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -119,14 +119,14 @@ By default, when you create a new repository in your personal account, `GITHUB_T {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. [Workflow permissions]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. **Save（保存）**をクリックして、設定を適用してください。 {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### {% data variables.product.prodname_actions %}がPull Requestの作成もしくは承認をできないようにする {% data reusables.actions.workflow-pr-approval-permissions-intro %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 0c0e388b99d0..1075ceca5f94 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -31,7 +31,7 @@ shortTitle: Email notifications for pushes - コミットの一部として変更されたファイル群 - コミットメッセージ -リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳細は、{% ifversion fpt or ghae or ghes or ghec %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」を参照してください。 プッシュのメール通知を無効にすることもできます。 詳しい情報については、「[通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}」を参照してください。 +リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」を参照してください。 ## リポジトリへのプッシュに対するメール通知の有効化 @@ -43,10 +43,5 @@ shortTitle: Email notifications for pushes 7. [**Setup notifications**] をクリックします。 ![設定通知ボタン](/assets/images/help/settings/setup_notifications_settings.png) ## 参考リンク -{% ifversion fpt or ghae or ghes or ghec %} - 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」 -{% else %} -- 「[通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)」 -- [通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) -- 「[メール通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)」 -- 「[Web 通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)」{% endif %} + diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md index 11c9074ced5e..539bf8aefbab 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md @@ -32,7 +32,7 @@ topics: リリースは [Git タグ](https://git-scm.com/book/en/Git-Basics-Tagging)に基づきます。タグは、リポジトリの履歴の特定の地点をマークするものです。 タグの日付は異なる時点で作成できるため、リリースの日付とは異なる場合があります。 既存のタグの表示に関する詳細は「[リポジトリのリリースとタグを表示する](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)」を参照してください。 -リポジトリで新しいリリースが公開されたときに通知を受け取り、リポジトリで他の更新があったときには通知を受け取らないでいることができます。 詳しい情報については、{% ifversion fpt or ghae or ghes or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}「[リポジトリのリリースを Watch および Watch 解除する](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}」を参照してください。 +リポジトリで新しいリリースが公開されたときに通知を受け取り、リポジトリで他の更新があったときには通知を受け取らないでいることができます。 For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." リポジトリへの読み取りアクセス権を持つ人はリリースを表示および比較できますが、リリースの管理はリポジトリへの書き込み権限を持つ人のみができます。 詳細は「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」を参照してください。 diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index ccbef6d1e05d..5dae5b5b8e57 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -17,13 +17,11 @@ topics: shortTitle: View releases & tags --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリリースを表示することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh release view`](https://cli.github.com/manual/gh_release_view)」を参照してください。 {% endtip %} -{% endif %} ## リリースを表示する diff --git a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index e16ade776bac..ba0b521a1122 100644 --- a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -64,7 +64,7 @@ shortTitle: Connections between repositories {% data reusables.repositories.accessing-repository-graphs %} 3. 左サイトバーで [**Forks**] をクリックします。 ![[Forks] タブ](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## リポジトリの依存関係を表示する 依存関係グラフを使用して、リポジトリが依存するコードを調べることができます。 diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md index fd7049fcfa47..2ef42357d4f3 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,10 +41,7 @@ GitHub Appは、単に合格/不合格の二択ではない、情報量の多い ![チェック実行のワークフロー](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} -チェック実行が15日以上にわたり不完全な状態である場合は、チェック実行の`conclusion`が`stale`になり、に状態が -{% data variables.product.prodname_dotcom %}に{% octicon "issue-reopened" aria-label="The issue-reopened icon" %}でstaleと表示されます。 {% data variables.product.prodname_dotcom %}のみが、チェック実行を`stale`としてマークできます。 チェック実行で出る可能性がある結果についての詳細は、 [`conclusion`パラメータ](/rest/reference/checks#create-a-check-run--parameters)を参照してください。 -{% endif %} +チェック実行が15日以上にわたり不完全な状態である場合は、チェック実行の`conclusion`が`stale`になり、{% data variables.product.prodname_dotcom %}に状態が{% octicon "issue-reopened" aria-label="The issue-reopened icon" %}と表示されます。 {% data variables.product.prodname_dotcom %}のみが、チェック実行を`stale`としてマークできます。 チェック実行で出る可能性がある結果についての詳細は、 [`conclusion`パラメータ](/rest/reference/checks#create-a-check-run--parameters)を参照してください。 [`check_suite`](/webhooks/event-payloads/#check_suite) webhookを受け取ったら、チェックが完了していなくてもすぐにチェック実行を作成できます。 チェック実行の`status`は、`queued`、`in_progress`、または`completed`の値で更新でき、より詳細を明らかにして`output`を更新できます。 チェック実行にはタイムスタンプ、詳細情報が記載された外部サイトへのリンク、コードの特定の行に対するアノテーション、および実行した分析についての情報を含めることができます。 diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md index 4791afc21213..726026840e8e 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md @@ -148,7 +148,7 @@ When authenticating, you should see your rate limit bumped to 5,000 requests an You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} To help keep your information secure, we highly recommend setting an expiration for your personal access tokens. @@ -164,7 +164,7 @@ To help keep your information secure, we highly recommend setting an expiration ![Personal Token selection](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date. {% endif %} diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index 81ebce6f9da8..05837720ec1c 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -120,7 +120,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/ {% ifversion fpt or ghec %} -[認証されていないレート制限の詳細](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)をお読みください。 +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index 6d9862e79901..2d136676fbe0 100644 --- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -87,7 +87,6 @@ shortTitle: Understand search syntax スペースなど、いくつかの英数字以外の記号は、引用符で囲ったコード検索クエリから省かれるので、結果が予想外のものになる場合があります。 -{% ifversion fpt or ghes or ghae or ghec %} ## ユーザ名によるクエリ 検索クエリに、`user`、`actor`、`assignee`などユーザ名を必要とする修飾子が含まれる場合は、任意の {% data variables.product.product_name %} ユーザ名を使用して特定の個人を指定するか、`@me`を使用して現在のユーザを指定することができます。 @@ -98,4 +97,3 @@ shortTitle: Understand search syntax | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) は、結果を表示している個人に割り当てられた Issue に一致します。 | `@me` は必ず修飾子とともに使用し、`@me main.workflow` のように検索用語としては使用できません。 -{% endif %} diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index e2948cda1adb..970bb55b17d9 100644 --- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -55,15 +55,12 @@ shortTitle: Search issues & PRs {% data reusables.pull_requests.large-search-workaround %} - | 修飾子 | サンプル | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) は、@defunkt が保有するリポジトリからの「ubuntu」という単語がある Issue にマッチします。 | | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) は、GitHub Organization が保有するリポジトリの Issue にマッチします。 | | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) は、2012 年 3 月より前に作成された @mozilla の shumway プロジェクトからの Issue にマッチします。 | - - ## オープンかクローズかで検索 `state` 修飾子または `is` 修飾子を使って、オープンかクローズかで、Issue およびプルリクエストをフィルタリングできます。 @@ -133,17 +130,15 @@ shortTitle: Search issues & PRs | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** は、@defunkt または @jlord が関与している Issue にマッチします。 | | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues)は、本文に「bootstrap」という単語を含まず、@mdo が関与している Issue にマッチします。 | -{% ifversion fpt or ghes or ghae or ghec %} ## リンクされた Issue とプルリクエストを検索する 結果を絞り込んで、クローズしているリファレンスによってプルリクエストにリンクされている、またはプルリクエストによってクローズされる可能性がある Issue にリンクされている Issue のみを表示することができます。 -| 修飾子 | サンプル | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。 | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。 | -| `-linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。 | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 -{% endif %} +| 修飾子 | サンプル | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。 | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。 | +| `-linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。 | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 | ## ラベルで検索 @@ -212,7 +207,7 @@ shortTitle: Search issues & PRs ## コメントの数で検索 -コメントの数で検索するには、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)とともに `comments` 修飾子を使います。 +You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. | 修飾子 | サンプル | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -221,7 +216,7 @@ shortTitle: Search issues & PRs ## インタラクションの数で検索 -`interactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをインタラクションの数でフィルタリングできます。 インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 +You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 | 修飾子 | サンプル | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | @@ -230,7 +225,7 @@ shortTitle: Search issues & PRs ## リアクションの数で検索 -`reactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをリアクションの数でフィルタリングできます。 +You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). | 修飾子 | サンプル | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | @@ -238,24 +233,27 @@ shortTitle: Search issues & PRs | | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500 から 1,000 までの範囲の Issue にマッチします。 | ## ドラフトプルリクエストを検索 -ドラフトプルリクエストをフィルタリングすることができます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests#draft-pull-requests)を参照してください。 +ドラフトプルリクエストをフィルタリングすることができます。 For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." -| Qualifier | Example | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) はドラフトプルリクエストに一致します。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) は、レビューの準備ができたプルリクエストに一致します。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) はドラフトプルリクエストに一致します。{% endif %} +| 修飾子 | サンプル | +| ------------- | ------------------------------------------------------------------------------------------------------------- | +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. | ## プルリクエストレビューのステータスおよびレビュー担当者で検索 -レビュー担当者およびレビューリクエストを受けた人で、[レビューステータス](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_、_required_、_approved_、または _changes requested_) でプルリクエストをフィルタリングできます。 +You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. -| 修飾子 | サンプル | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) は、レビューされていないプルリクエストにマッチします。 | -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) は、マージ前にレビューが必要なプルリクエストにマッチします。 | -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) は、レビュー担当者が承認したプルリクエストにマッチします。 | -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) は、レビュー担当者が変更を求めたプルリクエストにマッチします。 | -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) は、特定の人がレビューしたプルリクエストにマッチします。 | -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) は、特定の人にレビューがリクエストされているプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} | user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %} -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) は、Team `atom/design`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 | +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 | ## Issue やプルリクエストの作成時期や最終更新時期で検索 diff --git a/translations/ja-JP/data/features/security-managers.yml b/translations/ja-JP/data/features/security-managers.yml index 6e62d12897d1..77f12eb12675 100644 --- a/translations/ja-JP/data/features/security-managers.yml +++ b/translations/ja-JP/data/features/security-managers.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml b/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 000000000000..1aebf50245a1 --- /dev/null +++ b/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,8 @@ +--- +#Reference: #7028. +#Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml index a4369b76c8b4..e0bba6aaf313 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml @@ -15,10 +15,10 @@ sections: - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes. - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - In some cluster topologies, webhook delivery information was not available. - - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled. + - HA設定では、{% data variables.product.prodname_actions %}が以前に有効化されていた場合、レプリカの破棄が失敗します。 - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export. + - '`ghe-migrator`を使う場合、もしくは{% data variables.product.prodname_dotcom_the_website %}からエクスポートする場合、データがエクスポート中に削除されると実行に長時間かかるエクスポートが失敗します。' - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - Links to inaccessible pages were removed. - Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml index 175de423c636..d6625e0168a7 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml @@ -11,7 +11,7 @@ sections: - Creating an impersonation OAuth token using the Enterprise Administration REST API worked incorrectly when an integration matching the OAuth Application ID already existed. changes: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. + - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used. - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml index 647143eb910e..985980238bf1 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml @@ -17,7 +17,7 @@ sections: - Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location. changes: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. + - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. diff --git a/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml index 9205e8151dfa..f1532f3f8cdc 100644 --- a/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -2,7 +2,7 @@ date: '2021-12-06' friendlyDate: 'December 6, 2021' title: 'December 6, 2021' -currentWeek: true +currentWeek: false sections: features: - diff --git a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 000000000000..40645a176d2a --- /dev/null +++ b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,190 @@ +--- +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - + heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + - + heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + - + heading: '依存関係グラフ' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + - + heading: 'Dependabotアラート' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + - + heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + - + heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + - + heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + - + heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + - + heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + - + heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + - + heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + - + heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + - + heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - + heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)." + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any 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](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + changes: + - + heading: 'パフォーマンス' + notes: + - | + Page loads and jobs are now significantly faster for repositories with many Git refs. + - + heading: '管理' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + - + heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + - + heading: 'GitHub Advanced Security' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + - + heading: 'プルリクエスト' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + - | + If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - + heading: 'リポジトリ' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + - + heading: 'リリース' + notes: + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + - + heading: 'Markdown' + notes: + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md b/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md index 5918d645aa2a..efaede7995d3 100644 --- a/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md @@ -4,8 +4,8 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workflows %}, local actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed, and there are additional options for allowing other specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}: -- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae-issue-5094 %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} +- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae or ghec %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} - **Allow specified actions{% if actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% if actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action{% if actions-workflow-policy %} or reusable workflow{% endif %}, use the same syntax used in the workflow to select the action{% if actions-workflow-policy %} or reusable workflow{% endif %}. diff --git a/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md index baf995ad81ca..6b0d0c377c33 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/translations/ja-JP/data/reusables/actions/message-parameters.md b/translations/ja-JP/data/reusables/actions/message-parameters.md index fd9358b1a0cd..8f6097244acf 100644 --- a/translations/ja-JP/data/reusables/actions/message-parameters.md +++ b/translations/ja-JP/data/reusables/actions/message-parameters.md @@ -1 +1 @@ -| Parameter | Value | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | | `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endColumn` | End column number |{% endif %} | `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endLine` | End line number |{% endif %} +| Parameter | Value | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | | `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | End column number |{% endif %} | `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | End line number |{% endif %} diff --git a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md index 94f8884d54c7..46de512b3540 100644 --- a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **非推奨の注意:** {% data variables.product.prodname_dotcom %}は、クエリパラメータを使ったAPIの認証を廃止します。 APIの認証は[HTTPの基本認証](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)で行わなければなりません。{% ifversion fpt or ghec %}APIの認証にクエリパラメータを使用することは、2021年5月5日以降できなくなります。 {% endif %}予定された一時停止を含む詳しい情報については[ブログポスト](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)を参照してください。 @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %}クエリパラメータを使ったAPIの認証は、利用はできるものの、セキュリティ上の懸念からサポートされなくなりました。 その代わりに、インテグレータはアクセストークン、`client_id`もしくは`client_secret`をヘッダに移すことをおすすめします。 {% data variables.product.prodname_dotcom %}は、クエリパラメータによる認証の削除を、事前に通知します。 {% endif %} {% endwarning %} -{% endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md index 5cdc3ccfdb6a..1dfa9be3c4ff 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md @@ -28,13 +28,13 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。 | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} {%- ifversion fpt or ghec %} @@ -116,7 +116,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md index 6956ea62a74c..d862254f027b 100644 --- a/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してIssueやPull Requestをフィルタすることもできます。 詳しい情報については、ドキュメントの「[`gh issue list`](https://cli.github.com/manual/gh_issue_list)」または「[`gh pr list`](https://cli.github.com/manual/gh_pr_list)」{% data variables.product.prodname_cli %} を参照してください。 {% endtip %} -{% endif %} diff --git a/translations/ja-JP/data/reusables/code-scanning/beta.md b/translations/ja-JP/data/reusables/code-scanning/beta.md index bb9cf0d33ce3..0b559e04661b 100644 --- a/translations/ja-JP/data/reusables/code-scanning/beta.md +++ b/translations/ja-JP/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md index 4cfd65386af7..c2bfc45615e0 100644 --- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change. diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index d5ae9b84157e..367cbb25f8e8 100644 --- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} -Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% ifversion ghes or ghae %} +Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/dependency-review.md b/translations/ja-JP/data/reusables/gated-features/dependency-review.md index bd88b5b1824f..779649a9d8c1 100644 --- a/translations/ja-JP/data/reusables/gated-features/dependency-review.md +++ b/translations/ja-JP/data/reusables/gated-features/dependency-review.md @@ -2,12 +2,12 @@ Dependency review is enabled on public repositories. Dependency review is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghec %} -Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for {% data variables.product.prodname_GH_advanced_security %}. +依存関係レビューは、パブリックリポジトリに対して{% data variables.product.product_name %}に含まれています。 To use dependency review in private repositories owned by organizations, you must have a license for {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghes > 3.1 %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release). -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index 3f6d5df5ec8f..5517dbd6ce71 100644 --- a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} Watchしているか、セキュリティアラートをサブスクライブしているリポジトリ上で {% data variables.product.prodname_dependabot_alerts %}に関する通知の配信方法と頻度を選択できます。 {% endif %} diff --git a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md index 78fc92042a7a..999656560ff4 100644 --- a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - メールについては、{% data variables.product.prodname_dependabot %}がリポジトリで有効化された場合、新しいマニフェストファイルがリポジトリにコミットされた場合、重要度が重大もしくは高の新しい脆弱性が見つかった場合に送信されます（**Email each time a vulnerability is found（脆弱性が見つかるたびにメールする）**オプション）。 - ユーザインターフェースについては、脆弱な依存関係があった場合に、リポジトリのファイルとコードビューに警告が表示されます（**UI alerts（UIアラート）**オプション）。 diff --git a/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 000000000000..13f951ee2ffe --- /dev/null +++ b/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +1. あるいは、左のサイドバーを使ってセキュリティ機能ごとに情報をフィルタリングすることもできます。 On each page, you can use filters that are specific to that feature to fine-tune your search. diff --git a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md index ffd13da287fb..19aae1ce72ac 100644 --- a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md +++ b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ - [OrganizationのメンバーのTeamへの追加](/articles/adding-organization-members-to-a-team) - [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team) - [既存のTeamメンバーのチームメンテナへの昇格](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- リポジトリへのTeamのアクセスの削除{% ifversion fpt or ghes or ghae or ghec %} -- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- リポジトリへのTeamのアクセス権の削除 +- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [プルリクエストのスケジュールされたリマインダーの管理](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md index e0870429bb1c..1670aeb05789 100644 --- a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -プルリクエストをIssueにリンクして、{% ifversion fpt or ghes or ghae or ghec %}修復が進んでいることを示すことや、{% endif %}誰かがプルリクエストをマージしたときにIssueを自動的にクローズすることができます。 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 +You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request. 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/default-issue-templates.md b/translations/ja-JP/data/reusables/repositories/default-issue-templates.md index 202722511984..61d5af8ce162 100644 --- a/translations/ja-JP/data/reusables/repositories/default-issue-templates.md +++ b/translations/ja-JP/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -You can create default issue templates{% ifversion fpt or ghes or ghae or ghec %} and a default configuration file for issue templates{% endif %} for your organization{% ifversion fpt or ghes or ghae or ghec %} or personal account{% endif %}. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 - +You can create default issue templates and a default configuration file for issue templates for your organization or personal account. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/dependency-review.md b/translations/ja-JP/data/reusables/repositories/dependency-review.md index 3d3d7623ef76..536aa89b118a 100644 --- a/translations/ja-JP/data/reusables/repositories/dependency-review.md +++ b/translations/ja-JP/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 加えて、 {% data variables.product.prodname_dotcom %}は、リポジトリのデフォルトブランチに対して作成されたPull Request中で追加、更新、削除された依存関係のレビューを行うことができ、プロジェクトに脆弱性をもたらすような変更にフラグを立てることができます。 これによって、脆弱な依存関係がコードベースに達したあとではなく、達する前に特定して対処できるようになります。 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md index ceec95422ed5..93750c547089 100644 --- a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md +++ b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 3a599d66a2b8..e29ea372d6b7 100644 --- a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %}直線状のコミット履歴を必要とする保護されたブランチのルールがリポジトリ中にあるなら、squashマージ、リベースマージ、あるいはその両方を許可しなければなりません。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)」を参照してください。{% endif %} +If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/start-line-comment.md b/translations/ja-JP/data/reusables/repositories/start-line-comment.md index 09b217fd40c6..77114a2099c7 100644 --- a/translations/ja-JP/data/reusables/repositories/start-line-comment.md +++ b/translations/ja-JP/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. コメントを追加したいコードの行の上にカーソルを移動し、青いコメントアイコンをクリックしてください。{% ifversion fpt or ghes or ghae or ghec %}複数行にコメントを追加するには、クリックしてからドラッグで行の範囲を選択し、続いて青いコメントアイコンをクリックしてください。{% endif %} ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif) +1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon. To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon. ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/ja-JP/data/reusables/repositories/suggest-changes.md b/translations/ja-JP/data/reusables/repositories/suggest-changes.md index 22c1a6c0feac..1071b1cd997a 100644 --- a/translations/ja-JP/data/reusables/repositories/suggest-changes.md +++ b/translations/ja-JP/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. あるいは、特定の変更を行{% ifversion fpt or ghes or ghae or ghec %}あるいは複数行{% endif %}に対して示唆するには、{% octicon "diff" aria-label="The diff symbol" %}をクリックし、示唆するブロック内のテキストを編集してください。 ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png) +1. Optionally, to suggest a specific change to the line or lines, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md index 4dd22083b11c..0bc205dfe0b4 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/beta.md +++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md index fe024055e380..8895e000e5b7 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -13,9 +13,9 @@ Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Clou Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt @@ -27,7 +27,7 @@ Azure | Azure Active Directory Application Secret | azure_active_directory_appli Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} @@ -35,7 +35,7 @@ Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_k Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} Clojars | Clojars Deploy Token | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} Databricks | Databricks Access Token | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token{% endif %} Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token @@ -55,7 +55,7 @@ Fastly | Fastly API Token | fastly_api_token{% endif %} Finicity | Finicity App Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} Frame.io | Frame.io JSON Web Token | frameio_jwt Frame.io| Frame.io Developer Token | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub個人アクセストークン | github_personal_access_token{% endif %} @@ -67,13 +67,13 @@ GitHub | GitHubリフレッシュトークン | github_refresh_token{% endif %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Google OAuth Access Token | google_oauth_access_token{% endif %} @@ -93,9 +93,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Linear API Key | linear_api_key{% endif %} @@ -115,13 +115,13 @@ Meta | Facebook Access Token | facebook_access_token{% endif %} Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Notion Integration Token | notion_integration_token{% endif %} @@ -135,15 +135,15 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | OpenAI API Key | openai_api_key{% endif %} Palantir | Palantir JSON Web Token | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} @@ -153,9 +153,9 @@ RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Segment | Segment Public API Token | segment_public_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} diff --git a/translations/ja-JP/data/reusables/security-center/permissions.md b/translations/ja-JP/data/reusables/security-center/permissions.md new file mode 100644 index 000000000000..2a6ce48a2803 --- /dev/null +++ b/translations/ja-JP/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Teamのメンバーは、Teamが管理者権限を持つリポジトリのセキュリティの概要を見ることができます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md index b11c0bbd8bfd..c6184d182d73 100644 --- a/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} +As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md index 72f93c0465a9..1df12c2d8cc0 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md @@ -1,12 +1,12 @@ -| キー | 種類 | 説明 | -| --------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 次のいずれかになります。
  • `created` - 新しいチェックランが作成されました。
  • `completed` - チェックランの`status`は`completed`です。
  • `rerequested` - 誰かがPull RequestのUIからチェックランの再実行をリクエストしています。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。 `rerequested`アクションを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 誰かがチェックの再実行をリクエストした{% data variables.product.prodname_github_app %}だけが`rerequested`ペイロードを受け取ります。
  • `requested_action` - 誰かが、アプリケーションが提供するアクションの実行をリクエストしました。 誰かがアクションの実行をリクエストした{% data variables.product.prodname_github_app %}だけが`requested_action`ペイロードを受け取ります。 チェックランとリクエストされたアクションについて学ぶには、「[チェックランとリクエストされたアクション](/rest/reference/checks#check-runs-and-requested-actions)」を参照してください。
| -| `check_run` | `オブジェクト` | [check_run](/rest/reference/checks#get-a-check-run)。 | -| `check_run[status]` | `string` | チェックランの現在のステータス。 `queued`、`in_progress`、`completed`のいずれか。 | -| `check_run[conclusion]` | `string` | 完了したチェックランの結果。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 | -| `check_run[name]` | `string` | チェックランの名前。 | -| `check_run[check_suite][id]` | `integer` | このチェックランが一部になっているチェックスイートのid。 | -| `check_run[check_suite][pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| -| `check_run[check_suite][deployment]` | `オブジェクト` | リポジトリ環境へのデプロイメント。 これは、チェックランが環境を参照する{% data variables.product.prodname_actions %}ワークフロージョブによって作成された場合にのみ展開される。 | -| `requested_action` | `オブジェクト` | ユーザによってリクエストされたアクション。 | -| `requested_action[identifier]` | `string` | ユーザによってリクエストされたアクションのインテグレーター参照。 | +| キー | 種類 | 説明 | +| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `action` | `string` | 実行されたアクション。 次のいずれかになります。
  • `created` - 新しいチェックランが作成されました。
  • `completed` - チェックランの`status`は`completed`です。
  • `rerequested` - 誰かがPull RequestのUIからチェックランの再実行をリクエストしています。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。 `rerequested`アクションを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 誰かがチェックの再実行をリクエストした{% data variables.product.prodname_github_app %}だけが`rerequested`ペイロードを受け取ります。
  • `requested_action` - 誰かが、アプリケーションが提供するアクションの実行をリクエストしました。 誰かがアクションの実行をリクエストした{% data variables.product.prodname_github_app %}だけが`requested_action`ペイロードを受け取ります。 チェックランとリクエストされたアクションについて学ぶには、「[チェックランとリクエストされたアクション](/rest/reference/checks#check-runs-and-requested-actions)」を参照してください。
| +| `check_run` | `オブジェクト` | [check_run](/rest/reference/checks#get-a-check-run)。 | +| `check_run[status]` | `string` | チェックランの現在のステータス。 `queued`、`in_progress`、`completed`のいずれか。 | +| `check_run[conclusion]` | `string` | 完了したチェックランの結果。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. チェックランが`completed`になるまで、この値は`null`になる。 | +| `check_run[name]` | `string` | チェックランの名前。 | +| `check_run[check_suite][id]` | `integer` | このチェックランが一部になっているチェックスイートのid。 | +| `check_run[check_suite][pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| `check_run[check_suite][deployment]` | `オブジェクト` | リポジトリ環境へのデプロイメント。 これは、チェックランが環境を参照する{% data variables.product.prodname_actions %}ワークフロージョブによって作成された場合にのみ展開される。 | +| `requested_action` | `オブジェクト` | ユーザによってリクエストされたアクション。 | +| `requested_action[identifier]` | `string` | ユーザによってリクエストされたアクションのインテグレーター参照。 | diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md index 217896a2f714..924955220875 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| キー | 種類 | 説明 | -| ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 以下のいずれかになる。
  • `completed` - チェックスイート内のすべてのチェックランが完了しました。
  • `requested` - アプリケーションのリポジトリに新しいコードがプッシュされたときに発生します。 `requested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。
  • `rerequested` - 誰かがチェックスイート全体の再実行をPull Request UIからリクエストしたときに発生します。 `rerequested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。
| -| `check_suite` | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。 | -| `check_suite[head_branch]` | `string` | 変更があるヘッドブランチ名。 | -| `check_suite[head_sha]` | `string` | このチェックスイートに対する最新のコミットのSHA。 | -| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。 | -| `check_suite[conclusion]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 | -| `check_suite[url]` | `string` | チェックスイートAPIのリソースを指すURL。 | -| `check_suite[pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| キー | 種類 | 説明 | +| ---------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 以下のいずれかになる。
  • `completed` - チェックスイート内のすべてのチェックランが完了しました。
  • `requested` - アプリケーションのリポジトリに新しいコードがプッシュされたときに発生します。 `requested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。
  • `rerequested` - 誰かがチェックスイート全体の再実行をPull Request UIからリクエストしたときに発生します。 `rerequested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。
| +| `check_suite` | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。 | +| `check_suite[head_branch]` | `string` | 変更があるヘッドブランチ名。 | +| `check_suite[head_sha]` | `string` | このチェックスイートに対する最新のコミットのSHA。 | +| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。 | +| `check_suite[conclusion]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. チェックランが`completed`になるまで、この値は`null`になる。 | +| `check_suite[url]` | `string` | チェックスイートAPIのリソースを指すURL。 | +| `check_suite[pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| diff --git a/translations/ja-JP/data/reusables/webhooks/installation_properties.md b/translations/ja-JP/data/reusables/webhooks/installation_properties.md index 19c52775c7e0..4dfcea4ed4b6 100644 --- a/translations/ja-JP/data/reusables/webhooks/installation_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | キー | 種類 | 説明 | | -------------- | -------- | ------------------------------------------------- | -| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `created` - 誰かが{% data variables.product.prodname_github_app %}をインストールする。
  • `deleted` - だれかが{% data variables.product.prodname_github_app %}をアンインストールする。
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンドする。
  • `unsuspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンド解除する。
    • {% endif %}
  • `new_permissions_accepted` - 誰かが{% data variables.product.prodname_github_app %}インストールに対する新しい権限を受け入れる。 {% data variables.product.prodname_github_app %}のオーナーが新しい権限をリクエストすると、{% data variables.product.prodname_github_app %}をインストールした人は新しい権限リクエストを受け入れなければならない。
| +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `created` - 誰かが{% data variables.product.prodname_github_app %}をインストールする。
  • `deleted` - だれかが{% data variables.product.prodname_github_app %}をアンインストールする。
  • `suspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンドする。
  • `unsuspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンド解除する。
  • `new_permissions_accepted` - 誰かが{% data variables.product.prodname_github_app %}インストールに対する新しい権限を受け入れる。 {% data variables.product.prodname_github_app %}のオーナーが新しい権限をリクエストすると、{% data variables.product.prodname_github_app %}をインストールした人は新しい権限リクエストを受け入れなければならない。
| | `repositories` | `array` | インストールがアクセスできるリポジトリオブジェクトの配列。 | diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index 71498cda9c6e..0b39777a6743 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -21,6 +21,7 @@ translations/ja-JP/content/actions/using-github-hosted-runners/about-github-host translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,broken liquid tags translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags +translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags