From d41444941f5757145dc6ece9bf3749ca1759dfeb Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Thu, 27 Oct 2022 10:40:43 -0700 Subject: [PATCH] New translation batch for ja (#32131) --- .../managing-notifications-from-your-inbox.md | 4 +- .../about-your-organizations-profile.md | 2 +- .../setting-your-profile-to-private.md | 56 +- ...tributions-not-showing-up-on-my-profile.md | 10 +- .../index.md | 2 +- .../managing-accessibility-settings.md | 2 +- ...ysis-settings-for-your-personal-account.md | 56 +- ...-for-githubs-enterprise-marketing-pages.md | 8 +- .../managing-your-theme-settings.md | 53 +- ...evels-for-a-personal-account-repository.md | 113 +-- .../metadata-syntax-for-github-actions.md | 14 - ...uring-openid-connect-in-hashicorp-vault.md | 102 +- .../using-the-github-cli-on-a-runner.md | 92 +- .../about-self-hosted-runners.md | 4 - .../adding-self-hosted-runners.md | 2 +- .../autoscaling-with-self-hosted-runners.md | 2 +- .../actions/learn-github-actions/contexts.md | 2 +- .../automatic-token-authentication.md | 2 - .../security-guides/encrypted-secrets.md | 2 + .../controlling-access-to-larger-runners.md | 41 +- .../using-larger-runners.md | 4 +- .../workflow-commands-for-github-actions.md | 9 +- .../workflow-syntax-for-github-actions.md | 2 +- ...ng-dependency-review-for-your-appliance.md | 4 +- ...pply-chain-security-for-your-enterprise.md | 2 +- ...he-dependency-graph-for-your-enterprise.md | 2 +- ...enabling-dependabot-for-your-enterprise.md | 8 +- ...configuring-host-keys-for-your-instance.md | 2 +- ...guring-ssh-connections-to-your-instance.md | 2 +- .../about-repository-caching.md | 23 +- .../configuring-a-repository-cache.md | 76 +- .../caching-repositories/index.md | 13 +- .../about-geo-replication.md | 30 +- .../about-high-availability-configuration.md | 12 +- .../creating-a-high-availability-replica.md | 2 +- .../upgrade-requirements.md | 1 - .../upgrading-github-enterprise-server.md | 4 +- ...rise-server-with-github-actions-enabled.md | 2 +- ...ting-github-actions-for-your-enterprise.md | 2 +- .../index.md | 8 +- .../about-github-actions-for-enterprises.md | 8 - ...ub-actions-for-github-enterprise-server.md | 15 +- ...self-hosted-runners-for-your-enterprise.md | 6 - ...ucing-github-actions-to-your-enterprise.md | 4 +- ...-githubcom-actions-using-github-connect.md | 6 +- ...manually-syncing-actions-from-githubcom.md | 2 - ...version-of-the-official-bundled-actions.md | 2 - .../about-enterprise-managed-users.md | 16 +- .../using-ldap.md | 8 +- ...-sign-on-for-your-enterprise-using-okta.md | 8 +- .../troubleshooting-saml-authentication.md | 2 +- translations/ja-JP/content/admin/index.md | 16 +- .../index.md | 9 +- .../setting-up-a-staging-instance.md | 2 +- ...about-the-audit-log-for-your-enterprise.md | 2 - .../audit-log-events-for-your-enterprise.md | 6 +- ...uring-the-audit-log-for-your-enterprise.md | 6 +- ...g-the-audit-log-api-for-your-enterprise.md | 7 +- .../about-upgrades-to-new-releases.md | 10 +- ...ainer-registry-from-the-docker-registry.md | 4 +- ...olicies-for-projects-in-your-enterprise.md | 8 +- .../ja-JP/content/admin/policies/index.md | 8 +- .../index.md | 8 +- .../impersonating-a-user.md | 10 +- .../index.md | 8 +- .../viewing-people-in-your-enterprise.md | 19 +- ...authentication-with-saml-single-sign-on.md | 6 +- .../creating-a-personal-access-token.md | 12 +- .../reviewing-your-security-log.md | 2 +- .../token-expiration-and-revocation.md | 4 +- .../signing-commits.md | 10 +- .../signing-tags.md | 12 +- translations/ja-JP/content/billing/index.md | 8 +- .../index.md | 1 + .../viewing-your-github-codespaces-usage.md | 2 +- .../about-per-user-pricing.md | 5 +- .../index.md | 8 +- ...pting-github-advanced-security-at-scale.md | 8 +- ...lign-on-your-rollout-strategy-and-goals.md | 8 +- .../phase-2-preparing-to-enable-at-scale.md | 8 +- .../phase-3-pilot-programs.md | 8 +- .../phase-4-create-internal-documentation.md | 8 +- ...phase-5-rollout-and-scale-code-scanning.md | 8 +- ...ase-6-rollout-and-scale-secret-scanning.md | 77 +- .../configuring-code-scanning.md | 6 +- ...-codeql-workflow-for-compiled-languages.md | 22 +- ...tting-up-code-scanning-for-a-repository.md | 14 +- ...g-code-scanning-alerts-in-pull-requests.md | 5 +- .../troubleshooting-the-codeql-workflow.md | 43 +- ...-codeql-code-scanning-in-your-ci-system.md | 11 +- ...onfiguring-codeql-cli-in-your-ci-system.md | 4 +- ...iguring-codeql-runner-in-your-ci-system.md | 2 +- .../about-dependabot-alerts.md | 4 +- ...isories-in-the-github-advisory-database.md | 188 ---- ...isories-in-the-github-advisory-database.md | 55 - .../dependabot/dependabot-alerts/index.md | 2 - .../viewing-and-updating-dependabot-alerts.md | 12 +- ...configuring-dependabot-security-updates.md | 2 +- .../dependabot-security-updates/index.md | 10 +- ...ion-options-for-the-dependabot.yml-file.md | 2 +- .../customizing-dependency-updates.md | 72 +- .../dependabot-version-updates/index.md | 10 +- ...ndencies-configured-for-version-updates.md | 41 +- .../content/code-security/dependabot/index.md | 10 +- ...tomating-dependabot-with-github-actions.md | 2 +- .../working-with-dependabot/index.md | 10 +- ...your-actions-up-to-date-with-dependabot.md | 49 +- ...naging-encrypted-secrets-for-dependabot.md | 2 +- .../troubleshooting-dependabot-errors.md | 2 +- ...he-detection-of-vulnerable-dependencies.md | 8 +- ...ng-a-security-policy-to-your-repository.md | 54 +- .../github-security-features.md | 8 +- .../securing-your-organization.md | 6 +- .../securing-your-repository.md | 7 +- .../ja-JP/content/code-security/index.md | 12 +- ...-disclosure-of-security-vulnerabilities.md | 76 -- ...ub-security-advisories-for-repositories.md | 66 -- ...rator-to-a-repository-security-advisory.md | 50 - ...lve-a-repository-security-vulnerability.md | 90 -- ...creating-a-repository-security-advisory.md | 44 - .../editing-a-repository-security-advisory.md | 48 - .../repository-security-advisories/index.md | 36 - ...vels-for-repository-security-advisories.md | 50 - ...blishing-a-repository-security-advisory.md | 101 -- ...tor-from-a-repository-security-advisory.md | 42 - ...hdrawing-a-repository-security-advisory.md | 28 - .../secret-scanning/about-secret-scanning.md | 2 +- ...ing-custom-patterns-for-secret-scanning.md | 36 +- .../protecting-pushes-with-secret-scanning.md | 2 +- .../about-the-security-overview.md | 8 +- .../end-to-end-supply-chain/securing-code.md | 6 +- .../about-dependency-review.md | 2 - .../about-supply-chain-security.md | 16 +- .../about-the-dependency-graph.md | 4 - .../configuring-dependency-review.md | 7 +- .../troubleshooting-the-dependency-graph.md | 59 +- ...pace-to-access-a-private-image-registry.md | 2 +- ...ing-the-machine-type-for-your-codespace.md | 2 +- .../creating-a-codespace.md | 2 +- .../deleting-a-codespace.md | 2 +- .../developing-in-a-codespace.md | 2 +- .../ja-JP/content/codespaces/guides.md | 2 + ...ing-the-codespaces-in-your-organization.md | 4 +- .../ja-JP/content/codespaces/overview.md | 2 +- ...a-prebuild-to-access-other-repositories.md | 2 +- .../adding-a-codespaces-badge.md | 10 +- .../index.md | 1 + ...um-specification-for-codespace-machines.md | 39 +- .../the-githubdev-web-based-editor.md | 2 +- ...troubleshooting-dotfiles-for-codespaces.md | 4 +- ...ng-github-copilot-settings-on-githubcom.md | 8 +- .../authorizing-oauth-apps.md | 4 +- .../getting-started-with-apps/about-apps.md | 4 +- .../ja-JP/content/developers/index.md | 8 +- .../webhooks/webhook-events-and-payloads.md | 4 - ...-started-with-github-community-exchange.md | 8 +- .../index.md | 8 +- ...ubmissions-to-github-community-exchange.md | 8 +- ...repository-to-github-community-exchange.md | 8 +- ...about-github-global-campus-for-students.md | 8 +- ...ly-to-github-global-campus-as-a-student.md | 2 +- .../index.md | 8 +- ...about-github-global-campus-for-teachers.md | 8 +- .../index.md | 8 +- ...-to-global-campus-for-teachers-approved.md | 8 +- .../about-github-advanced-security.md | 2 +- .../quickstart/communicating-on-github.md | 2 +- .../quickstart/contributing-to-projects.md | 3 +- .../get-started/quickstart/fork-a-repo.md | 4 +- .../using-github/keyboard-shortcuts.md | 10 +- .../basic-writing-and-formatting-syntax.md | 6 - .../guides/managing-enterprise-accounts.md | 4 +- .../graphql/overview/breaking-changes.md | 8 +- .../content/graphql/overview/changelog.md | 8 +- .../graphql/overview/schema-previews.md | 8 +- .../ja-JP/content/graphql/reference/enums.md | 8 +- .../graphql/reference/input-objects.md | 8 +- .../content/graphql/reference/interfaces.md | 8 +- .../content/graphql/reference/mutations.md | 8 +- .../content/graphql/reference/objects.md | 8 +- .../content/graphql/reference/queries.md | 8 +- .../content/graphql/reference/scalars.md | 8 +- .../ja-JP/content/graphql/reference/unions.md | 8 +- translations/ja-JP/content/index.md | 8 +- .../index.md | 8 +- .../about-automation-for-project-boards.md | 8 +- .../about-project-boards.md | 4 +- .../changing-project-board-visibility.md | 22 +- .../closing-a-project-board.md | 8 +- ...nfiguring-automation-for-project-boards.md | 8 +- .../copying-a-project-board.md | 45 +- .../creating-a-project-board.md | 95 +- .../deleting-a-project-board.md | 8 +- .../editing-a-project-board.md | 8 +- .../managing-project-boards/index.md | 8 +- ...linking-a-repository-to-a-project-board.md | 8 +- .../reopening-a-closed-project-board.md | 8 +- ...es-and-pull-requests-to-a-project-board.md | 8 +- .../adding-notes-to-a-project-board.md | 8 +- .../archiving-cards-on-a-project-board.md | 8 +- .../filtering-cards-on-a-project-board.md | 8 +- .../index.md | 8 +- ...tracking-progress-on-your-project-board.md | 8 +- .../automating-projects-using-actions.md | 4 +- .../automating-your-project/index.md | 8 +- .../using-the-api-to-manage-projects.md | 8 +- .../using-the-built-in-automations.md | 8 +- .../creating-projects/creating-a-project.md | 8 +- .../creating-projects/index.md | 8 +- .../migrating-from-projects-classic.md | 92 +- .../customizing-a-view.md | 6 +- .../filtering-projects.md | 8 +- .../index.md | 8 +- .../managing-your-views.md | 8 +- .../index.md | 8 +- .../learning-about-projects/about-projects.md | 8 +- .../best-practices-for-projects.md | 4 +- .../learning-about-projects/index.md | 8 +- .../quickstart-for-projects.md | 8 +- .../adding-items-to-your-project.md | 6 +- .../archiving-items-from-your-project.md | 6 +- .../converting-draft-issues-to-issues.md | 8 +- .../managing-items-in-your-project/index.md | 8 +- .../adding-your-project-to-a-repository.md | 8 +- .../closing-and-deleting-your-projects.md | 8 +- .../managing-your-project/index.md | 8 +- .../managing-access-to-your-projects.md | 2 +- .../managing-visibility-of-your-projects.md | 8 +- .../about-date-fields.md | 8 +- .../about-iteration-fields.md | 8 +- .../about-single-select-fields.md | 8 +- .../about-text-and-number-fields.md | 8 +- .../deleting-fields.md | 8 +- .../understanding-field-types/index.md | 8 +- .../renaming-fields.md | 8 +- .../about-insights-for-projects.md | 8 +- .../configuring-charts.md | 8 +- .../creating-charts.md | 8 +- ...-and-searching-issues-and-pull-requests.md | 10 +- .../linking-a-pull-request-to-an-issue.md | 2 +- .../about-organizations.md | 8 +- ...analysis-settings-for-your-organization.md | 14 +- ...ing-the-audit-log-for-your-organization.md | 16 +- ...to-a-project-board-in-your-organization.md | 29 +- .../index.md | 8 +- ...-project-board-for-organization-members.md | 40 +- ...access-to-an-organization-project-board.md | 63 +- ...access-to-an-organization-project-board.md | 4 +- ...ator-from-an-organization-project-board.md | 22 +- ...visibility-changes-in-your-organization.md | 8 +- ...ights-for-projects-in-your-organization.md | 8 +- .../managing-organization-settings/index.md | 8 +- ...it-signoff-policy-for-your-organization.md | 27 +- ...ssions-for-adding-outside-collaborators.md | 35 +- .../roles-in-an-organization.md | 12 +- ...ess-management-with-saml-single-sign-on.md | 4 +- ...access-management-for-your-organization.md | 10 +- ...ging-code-review-settings-for-your-team.md | 2 +- ...ainer-registry-from-the-docker-registry.md | 2 +- .../working-with-the-npm-registry.md | 4 +- .../index.md | 8 +- .../unpublishing-a-github-pages-site.md | 37 +- translations/ja-JP/content/pages/index.md | 1 + ...ng-dependency-changes-in-a-pull-request.md | 2 - ...wing-proposed-changes-in-a-pull-request.md | 2 - .../about-protected-branches.md | 4 +- .../about-repositories.md | 8 + .../transferring-a-repository.md | 6 + .../about-citation-files.md | 10 +- .../about-code-owners.md | 3 - .../about-readmes.md | 4 +- ...classifying-your-repository-with-topics.md | 47 +- ...isabling-project-boards-in-a-repository.md | 8 +- ...d-analysis-settings-for-your-repository.md | 21 +- ...mmit-signoff-policy-for-your-repository.md | 4 +- .../managing-releases-in-a-repository.md | 15 +- .../searching-a-repositorys-releases.md | 10 +- .../working-with-non-code-files.md | 4 - .../rest/deployments/branch-policies.md | 8 +- .../rest/enterprise-admin/audit-log.md | 2 +- .../content/rest/enterprise-admin/scim.md | 2 +- .../content/rest/overview/api-previews.md | 192 +--- .../endpoints-available-for-github-apps.md | 8 +- .../permissions-required-for-github-apps.md | 7 +- .../ja-JP/content/rest/repos/autolinks.md | 10 +- translations/ja-JP/content/rest/repos/lfs.md | 2 +- .../content/rest/users/ssh-signing-keys.md | 8 +- .../searching-issues-and-pull-requests.md | 8 +- translations/ja-JP/content/search/index.md | 8 +- .../index.md | 8 +- .../ja-JP/data/glossaries/external.yml | 936 +++++++++++------- .../ghes-3.2/graphql_previews.enterprise.yml | 117 --- .../data/learning-tracks/code-security.yml | 80 +- .../accounts/create-personal-access-tokens.md | 2 +- .../reusables/actions/about-runner-groups.md | 10 +- .../actions/actions-audit-events-workflow.md | 30 +- .../actions/add-hosted-runner-overview.md | 10 +- .../reusables/actions/add-hosted-runner.md | 26 +- ...utomatically-adding-a-runner-to-a-group.md | 10 +- ...ing-the-access-policy-of-a-runner-group.md | 2 +- .../changing-the-name-of-a-runner-group.md | 2 +- ...ting-a-runner-group-for-an-organization.md | 2 +- .../actions/enterprise-http-proxy.md | 2 +- .../actions/github_sha_description.md | 10 +- .../hosted-runner-security-admonition.md | 10 +- .../reusables/actions/message-parameters.md | 17 +- .../actions/more-resources-for-ghes.md | 17 +- .../actions/moving-a-runner-to-a-group.md | 2 +- .../actions/removing-a-runner-group.md | 10 +- .../runner-group-enterprise-overview.md | 10 +- .../self-hosted-runner-auto-removal.md | 18 +- .../self-hosted-runner-security-admonition.md | 10 +- .../actions/self-hosted-runner-security.md | 10 +- .../data/reusables/actions/sidebar-secret.md | 2 +- .../actions/usage-workflow-run-time.md | 2 +- .../advanced-security/custom-link-beta.md | 10 +- .../secret-scanning-create-custom-pattern.md | 2 +- .../secret-scanning-new-custom-pattern.md | 10 +- .../audit_log/audit-data-retention-tab.md | 10 +- .../audit_log/audit-log-action-categories.md | 5 +- .../audit_log/audit-log-events-workflows.md | 2 - .../git-events-not-in-search-results.md | 10 +- .../audit_log/streaming-check-s3-endpoint.md | 10 +- .../audit_log/streaming-choose-s3.md | 10 +- .../billing/billing-hosted-runners.md | 10 +- .../alerts-found-in-generated-code.md | 12 +- .../reusables/code-scanning/analyze-go.md | 10 +- .../autobuild-compiled-languages.md | 10 +- .../example-configuration-files.md | 10 +- .../code-scanning/non-glibc-linux-support.md | 10 +- .../about-changing-default-editor.md | 9 + .../accessing-prebuild-configuration.md | 10 + .../click-remote-explorer-icon-vscode.md | 10 +- .../codespaces-org-policies-note.md | 2 +- .../codespaces/links-to-get-started.md | 2 +- .../codespaces/max-number-codespaces.md | 10 +- .../prebuilds-permission-authorization.md | 10 +- .../codespaces/stopping-a-codespace.md | 13 + .../codespaces/using-codespaces-in-vscode.md | 9 + .../your-codespaces-procedure-step.md | 2 +- .../data/reusables/copilot/dotcom-settings.md | 10 +- ...security-and-version-updates-onboarding.md | 17 - .../beta-security-and-version-updates.md | 2 +- .../enterprise-enable-dependabot.md | 2 +- .../dependency-review/action-enterprise.md | 10 +- .../data/reusables/dependency-review/beta.md | 15 - .../about-github-community-exchange-intro.md | 10 +- .../reusables/education/submit-application.md | 2 +- .../about-license-sync.md | 10 +- .../about-github-for-enterprises.md | 10 +- .../repository-caching-release-phase.md | 16 +- .../enterprise/upgrade-ghes-for-actions.md | 10 - .../enterprise-backup-utils-directory.md | 10 +- .../enterprise-backup-utils-verify-upgrade.md | 10 +- .../installing-releases.md | 2 +- ...unlocking-management-console-with-shell.md | 9 + .../reusables/gated-features/code-scanning.md | 22 +- .../historical-insights-for-projects.md | 10 +- .../gated-features/hosted-runners.md | 10 +- .../getting-started/bearer-vs-token.md | 10 +- .../getting-started/math-and-diagrams.md | 10 +- .../reusables/git/no-credential-manager.md | 10 +- .../reusables/github-ae/saml-idp-table.md | 12 +- .../reusables/gpg/configure-ssh-signing.md | 10 +- .../about-adding-ip-allow-list-entries.md | 10 +- .../about-checking-ip-address.md | 10 +- .../about-editing-ip-allow-list-entries.md | 10 +- .../about-enabling-allowed-ip-addresses.md | 10 +- .../check-ip-address-step.md | 10 +- .../check-ip-address.md | 10 +- .../ipv6-allow-lists.md | 10 +- .../vigilant-mode-beta-note.md | 2 +- .../custom-notification-types.md | 2 +- .../about-following-organizations.md | 10 +- .../follow-organizations-beta.md | 10 +- .../data/reusables/organizations/new_team.md | 20 +- .../reusables/organizations/org_settings.md | 16 +- .../organization-wide-project.md | 16 +- .../reusables/organizations/owners-team.md | 20 +- .../data/reusables/organizations/people.md | 16 +- .../reusables/organizations/specific_team.md | 20 +- .../data/reusables/organizations/teams.md | 16 +- ...er-registry-ghes-migration-availability.md | 10 +- .../no-graphql-to-delete-packages.md | 10 +- .../package-settings-from-org-level.md | 18 +- .../reusables/pages/check-workflow-run.md | 10 +- .../pages/pages-custom-workflow-beta.md | 10 +- .../profile/navigating-to-profile.md | 9 + .../reusables/projects/access-workflows.md | 13 + .../reusables/projects/add-draft-issue.md | 10 +- .../reusables/projects/add-item-bottom-row.md | 10 +- .../reusables/projects/add-item-via-paste.md | 10 +- .../ja-JP/data/reusables/projects/bulk-add.md | 10 +- .../projects/classic-project-creation.md | 10 +- .../data/reusables/projects/new-field.md | 10 +- .../ja-JP/data/reusables/projects/new-view.md | 10 +- .../data/reusables/projects/open-item-menu.md | 10 +- .../data/reusables/projects/open-view-menu.md | 10 +- ...owners-can-limit-visibility-permissions.md | 10 +- .../data/reusables/projects/save-view.md | 10 +- .../data/reusables/projects/select-an-item.md | 10 +- .../pull_requests/merge-queue-beta.md | 13 +- .../reusables/repositories/commit-signoffs.md | 10 +- .../security-advisories-republishing.md | 10 +- .../data/reusables/saml/ae-uses-saml-sso.md | 10 +- .../reusables/saml/authentication-loop.md | 10 +- ...t-time-earlier-than-notbefore-condition.md | 10 +- .../data/reusables/saml/okta-ae-sso-beta.md | 10 +- .../data/reusables/saml/okta-sign-on-tab.md | 11 +- .../saml/okta-view-setup-instructions.md | 10 +- .../data/reusables/saml/saml-accounts.md | 10 +- .../partner-secret-list-private-repo.md | 59 +- .../push-protection-allow-email.md | 10 +- .../push-protection-remove-secret.md | 10 +- .../push-protection-web-ui-choice.md | 10 +- .../security-advisory-overview.md | 10 +- .../information-varies-GHAS.md | 10 +- .../security-overview/permissions.md | 2 +- .../security/displayed-information.md | 22 +- .../data/reusables/ssh/key-type-support.md | 2 +- .../reusables/support/entitlements-note.md | 10 +- .../support/navigate-to-my-tickets.md | 10 +- .../data/reusables/supported-languages/C.md | 10 +- .../data/reusables/supported-languages/Cpp.md | 10 +- .../data/reusables/supported-languages/Cs.md | 10 +- .../data/reusables/supported-languages/go.md | 10 +- .../reusables/supported-languages/java.md | 10 +- .../supported-languages/javascript.md | 10 +- .../data/reusables/supported-languages/php.md | 10 +- .../products-table-header.md | 13 +- .../reusables/supported-languages/python.md | 10 +- .../reusables/supported-languages/ruby.md | 10 +- .../reusables/supported-languages/scala.md | 10 +- .../supported-languages/typescript.md | 10 +- .../webhooks/webhooks-rest-api-links.md | 16 +- translations/ja-JP/data/variables/product.yml | 2 +- translations/log/msft-ja-resets.csv | 89 +- 437 files changed, 2966 insertions(+), 4083 deletions(-) delete mode 100644 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md delete mode 100644 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/index.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md delete mode 100644 translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml create mode 100644 translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md create mode 100644 translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md create mode 100644 translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md create mode 100644 translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md delete mode 100644 translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md delete mode 100644 translations/ja-JP/data/reusables/dependency-review/beta.md delete mode 100644 translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md create mode 100644 translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md create mode 100644 translations/ja-JP/data/reusables/profile/navigating-to-profile.md create mode 100644 translations/ja-JP/data/reusables/projects/access-workflows.md 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 ba60987068..a006c11816 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 @@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo- ## {% data variables.product.prodname_dependabot %} custom filters -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: - `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. - `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. @@ -170,7 +170,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghae %} If you use {% data variables.product.prodname_dependabot %} to tell you about insecure 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/customizing-your-profile/about-your-organizations-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md index a2124b6092..e90733dfb6 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md @@ -24,7 +24,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec %} +{% ifversion fpt or ghes or ghec %} ![Sample organization profile page](/assets/images/help/organizations/org_profile_with_overview.png) {% else %} ![Sample organization profile page](/assets/images/help/profile/org_profile.png) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md index 9ef85f8450..33de873e4a 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md @@ -1,56 +1,62 @@ --- -title: Setting your profile to private -intro: 'A private profile displays only limited information, and hides some activity.' +title: プロファイルをプライベートに設定する +intro: プライベート プロファイルには限られた情報のみが表示され、一部のアクティビティは表示されません。 versions: fpt: '*' topics: - Profiles shortTitle: Set profile to private +ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148008670' --- -## About private profiles +## プライベート プロファイルについて -To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity. +プロファイル ページの一部を非表示にするには、プロファイルをプライベートにします。 これにより、{% data variables.product.prodname_dotcom_the_website %} のさまざまなソーシャル機能のアクティビティも非表示になります。 プライベート プロファイルでは、すべてのユーザーに対し情報が非表示になります。現在、指定したユーザーにアクティビティを表示するオプションはありません。 -After making your profile private, you can still view all your information when you visit your own profile. +プロファイルをプライベートにした後も、自分のプロファイルにアクセスした場合、すべての情報が表示されます。 -Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private. +プライベート プロファイルでは、[{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) のスポンサーシップを受けることができません。 {% data variables.product.prodname_sponsors %} の対象になるには、プロファイルをプライベートにしないでください。 -## Differences between private and public profiles +## プライベートおよびパブリック プロファイルの違い -When your profile is private, the following content is hidden from your profile page: +プロファイルがプライベートの場合、プロファイル ページで次のコンテンツが非表示になります。 -- Achievements and highlights. -- Activity overview and activity feed. -- Contribution graph. -- Follower and following counts. -- Follow and Sponsor buttons. -- Organization memberships. -- Stars, projects, packages, and sponsoring tabs. +- 実績とハイライト。 +- アクティビティの概要とアクティビティ フィード。 +- コントリビューション グラフ。 +- フォロワーと次の数。 +- フォローとスポンサーのボタン。 +- Organization メンバーシップ。 +- スター、プロジェクト、パッケージ、スポンサー タブ。 {% note %} -**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo. +**注**: プロファイルがプライベートの場合、README、経歴、プロフィール写真などの一部のオプション フィールドは引き続きパブリックに表示されます。 {% endnote %} -## Changes to reporting on your activities +## アクティビティに対する通知の変更 -By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled. +プロフィールをプライベートにしても、過去のアクティビティは削除または非表示になりません。この設定は、プライベート設定が有効になっている間のアクティビティにのみ適用されます。 -When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations: +プロファイルがプライベートの場合、{% data variables.product.prodname_dotcom_the_website %} アクティビティは次の場所に表示されません。 -- Activity feeds for other users. -- Discussions leaderboards. -- The [Trending](https://github.com/trending) page. +- 他のユーザーのアクティビティ フィード。 +- ディスカッション ランキング。 +- [[トレンド]](https://github.com/trending) ページ。 {% note %} -**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API. +**注**: パブリック リポジトリ上のアクティビティは、それらのリポジトリを表示しているユーザーには引き続きパブリックに表示され、一部のアクティビティ データは {% data variables.product.prodname_dotcom %} API を通じて引き続き使用できます。 {% endnote %} -## Changing your profile's privacy settings +## プロファイルのプライバシー設定を変更する {% data reusables.user-settings.access_settings %} -1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**. +1. [コントリビューションとアクティビティ] で、 **[プロファイルを非公開にしてアクティビティを非表示にする]** の横にあるチェックボックスをオンにします。 {% data reusables.user-settings.update-preferences %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 3e24053ec8..fa16c3f01b 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -69,11 +69,15 @@ The email address in the `From:` field is the address that was set in the [local If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %} -{% warning %} +{% ifversion fpt or ghec %} +{% note %} -**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph. +**Note**: If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot add additional email addresses to the account, even if multiple email addresses are registered with your identity provider (IdP). Therefore, only commits that are authored by the primary email address registered with your IdP can be associated with your {% data variables.enterprise.prodname_managed_user %}. -{% endwarning %} +{% endnote %} +{% endif %} + +Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts and linked to commits. If you've authored any commits using a generic email address, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph. ### Commit was not made in the default or `gh-pages` branch diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 63b2860091..d72f863eba 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,6 +1,6 @@ --- title: Setting up and managing your personal account on GitHub -intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself. +intro: 'You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.' shortTitle: Personal accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 20771e8187..68a58042b1 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -1,7 +1,7 @@ --- title: Managing accessibility settings shortTitle: Manage accessibility settings -intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs." +intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.' versions: feature: keyboard-shortcut-accessibility-setting redirect_from: diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index 9362dbfa30..52815b7a7d 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,10 +1,10 @@ --- -title: 個人アカウントのセキュリティと分析設定を管理する -intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。' +title: Managing security and analysis settings for your personal account +intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' topics: - Accounts redirect_from: @@ -12,47 +12,43 @@ redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account shortTitle: Manage security & analysis -ms.openlocfilehash: 61d1944219fd1b75f476c7aef8305018c85735c5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145165351' --- -## セキュリティおよび分析設定の管理について +## About management of security and analysis settings -{% data variables.product.prodname_dotcom %} を使用してリポジトリを保護できます。 このトピックでは、既存または新規のすべてのリポジトリのセキュリティおよび分析機能を管理する方法について説明します。 +{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories. -個々のリポジトリのセキュリティおよび分析機能は引き続き管理できます。 詳細については、「[リポジトリのセキュリティと分析の設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 +You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." -自分の個人アカウントに対するすべてのアクティビティのセキュリティ ログを確認することもできます。 詳細については、「[セキュリティ ログの確認](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)」を参照してください。 +You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)." {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} {% data reusables.security.security-and-analysis-features-enable-read-only %} -リポジトリレベル セキュリティの概要については、「[リポジトリをセキュリティで保護する](/code-security/getting-started/securing-your-repository)」を参照してください。 +For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." -## 既存のリポジトリに対して機能を有効または無効にする +## Enabling or disabling features for existing repositories -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %} -3. [Code security and analysis] の下で機能の右にある **[Disable all]** または **[Enable all]** をクリックします。 - {% ifversion ghes > 3.2 %}!["Configure security and analysis" 機能の "Enable all" または "Disable all" ボタン](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Configure security and analysis" 機能の "Enable all" または "Disable all" ボタン](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %} -6. オプションで、自分が所有する新しいリポジトリに対して機能を既定で有効にできます。 - {% ifversion ghes > 3.2 %}![新しいリポジトリの "Enable by default" オプション](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}![新しいリポジトリの "Enable by default" オプション](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %} -7. **[Disable FEATURE]** または **[Enable FEATURE]** をクリックし、所有するすべてのリポジトリに対してこの機能を無効または有効にします。 - {% ifversion ghes > 3.2 %}![機能を無効または有効にするボタン](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![機能を無効または有効にするボタン](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security-analysis %} +3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. + {% ifversion ghes %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %} +6. Optionally, enable the feature by default for new repositories that you own. + {% ifversion ghes %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %} +7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own. + {% ifversion ghes %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %} {% data reusables.security.displayed-information %} -## 既存のリポジトリに対して機能を有効または無効にする +## Enabling or disabling features for new repositories -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %} -3. 機能の右側にある [Code security and analysis] で、所有する新しいリポジトリに対して既定で機能を有効または無効にします - {% ifversion ghes > 3.2 %}![新しいリポジトリの機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![新しいリポジトリの機能を有効または無効にするチェックボックス](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security-analysis %} +3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own. + {% ifversion ghes %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} -## 参考資料 +## Further reading -- "[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[依存関係を自動的に更新する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)" +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)" diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md index 5a3355a14d..8e891c2997 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md @@ -9,12 +9,12 @@ versions: topics: - Accounts shortTitle: Manage cookie preferences -ms.openlocfilehash: f2fdbcf8bd552902e7db491aa1b3c6622c5673ab -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147760923' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108809' --- ## エンタープライズ マーケティング ページでの Cookie の基本設定について diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md index 80754b00c6..584121c0e5 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -1,6 +1,6 @@ --- -title: テーマ設定を管理する -intro: 'システム設定に従うか、ライトまたはダーク モードを常に使用するようにテーマを設定することで、{% data variables.product.product_name %} の外観を管理できます。' +title: Managing your theme settings +intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' versions: fpt: '*' ghae: '*' @@ -13,52 +13,51 @@ redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings shortTitle: Manage theme settings -ms.openlocfilehash: 6251b265d99271f58a4ad02d2f6cb7fdf722cb6b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580448' --- -{% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 ライトとダークの 2 つのテーマから選択するか、システム設定に従うかを {% data variables.product.product_name %} で設定できます。 -ダーク テーマを使用して、特定のデバイスの電力消費量を削減したり、暗い場所で目の負担を減らしたり、テーマの外観を優先したりすることができます。 +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. -{% ifversion fpt or ghes > 3.2 or ghae or ghec %}弱視の方は、前景と背景の要素のコントラストが強いハイ コントラスト テーマの使用をお勧めします。{% endif %}{% ifversion fpt or ghae or ghec %}色覚障碍がある方には、ライトとダークの色覚障碍向けテーマをお勧めします。 +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. + +If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% endif %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.appearance-settings %} -1. [テーマ モード] で、ドロップダウン メニューを選択し、テーマの設定をクリックします。 +1. Under "Theme mode", select the drop-down menu, then click a theme preference. - ![テーマの設定を選択するための [テーマ モード] のドロップダウン メニュー](/assets/images/help/settings/theme-mode-drop-down-menu.png) -1. 使いたいテーマをクリックしてください。 - - 1 つのテーマを選択する場合は、そのテーマをクリックします。 + ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png) +1. Click the theme you'd like to use. + - If you chose a single theme, click a theme. - {%- ifversion ghes = 3.5 %} {% note %} + {%- ifversion ghes = 3.5 %} + {% note %} - **注**: 明るいハイ コントラスト テーマは、{% data variables.product.product_name %} 3.5.0、3.5.1、3.5.2、および 3.5.3 では使用できませんでした。 このテーマは 3.5.4 以降で使用できます。 アップグレードの詳しい情報については、サイト管理者にお問い合わせください。 + **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator. - 使用する {% data variables.product.product_name %} のバージョンの決定について詳しくは、「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)」を参照してください。 - {% endnote %} {%- endif %} + For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." + {% endnote %} + {%- endif %} - {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![1 つのテーマを選択するためのラジオ ボタン](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![1 つのテーマを選択するためのラジオ ボタン](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - - システム設定に従うことを選択した場合は、昼のテーマと夜のテーマをクリックします。 + ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png) + - If you chose to follow your system settings, click a day theme and a night theme. - {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![システム設定と同期するテーマを選択するためのボタン](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![システム設定と同期するテーマを選択するためのボタン](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - - 現在パブリック ベータ版のテーマを選択する場合は、まず機能プレビューでそれを有効にする必要があります。 詳細については、「[機能プレビューを使用した早期アクセス リリースを探索する](/get-started/using-github/exploring-early-access-releases-with-feature-preview)」を参照してください。{% endif %} + ![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) + {% 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 %} {% ifversion command-palette %} {% note %} -**注:** コマンド パレットを使用してテーマの設定を変更することもできます。 詳細については、「[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)」を参照してください。 +**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)". {% endnote %} {% endif %} -## 参考資料 +## Further reading -- [{% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop) の設定方法 +- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index 44076f88da..e113259b91 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,6 +1,6 @@ --- -title: 個人アカウントのリポジトリの権限レベル -intro: 個人アカウントが所有するリポジトリには、リポジトリ所有者とコラボレーターという 2 つのアクセス許可レベルがあります。 +title: Permission levels for a personal account repository +intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.' redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository @@ -14,84 +14,79 @@ versions: topics: - Accounts shortTitle: Repository permissions -ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066307' --- -## 個人アカウント リポジトリのアクセス許可レベルについて +## About permissions levels for a personal account repository -個人アカウントが所有するリポジトリの所有者は 1 人です。 所有権のアクセス許可を別の個人アカウントと共有することはできません。 +Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account. -{% data variables.product.product_name %} のユーザーをコラボレーターとしてリポジトリに{% ifversion fpt or ghec %}招待{% else %}追加{% endif %}することもできます。 詳細については、「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」を参照してください。 +You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)." {% tip %} -**ヒント:** 個人アカウントが所有しているリポジトリに対して、より詳細なアクセス権が必要な場合には、リポジトリを Organization に移譲することを検討してください。 詳細については、「[リポジトリを移譲する](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)」を参照してください。 +**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)." {% endtip %} -## 個人アカウントが所有しているリポジトリに対する所有者アクセス権 +## Owner access for a repository owned by a personal account -リポジトリオーナーは、リポジトリを完全に制御することができます。 コラボレータが実行できるアクションに加えて、リポジトリオーナーは次のアクションを実行できます。 +The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions. -| アクション | 説明を見る | +| Action | More information | | :- | :- | -| {% ifversion fpt or ghec %}コラボレーターの招待{% else %}コラボレーターの追加{% endif %} | 「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」 | -| リポジトリの表示変更 | 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 |{% ifversion fpt or ghec %} -| リポジトリとのインタラクションの制限 | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %} -| デフォルトブランチを含むブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 | -| 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | 「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」 | -| リポジトリを削除する | 「[リポジトリの削除](/repositories/creating-and-managing-repositories/deleting-a-repository)」 | -| リポジトリのトピックの管理 | 「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」 |{% ifversion fpt or ghec %} -| リポジトリのセキュリティおよび分析設定の管理 | 「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」 |{% endif %}{% ifversion fpt or ghec %} -| プライベートリポジトリの依存関係グラフの有効化 | 「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)」 |{% endif %} -| パッケージの削除および復元 | 「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」 | -| リポジトリのソーシャルメディア向けプレビューのカスタマイズ | 「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)」 | -| リポジトリからのテンプレートの作成 | 「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」 | -| Control access to {% data variables.product.prodname_dependabot_alerts %} へのアクセスを制御する| 「[リポジトリのセキュリティと分析設定を管理する](/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)」 |{% ifversion fpt or ghec %} -| リポジトリで {% data variables.product.prodname_dependabot_alerts %} を閉じる | "[{% data variables.product.prodname_dependabot_alerts %} の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" | -| プライベートリポジトリのデータ利用の管理 | 「[プライベート リポジトリ用のデータ利用設定の管理](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)」|{% endif %} -| リポジトリのコードオーナーを定義する | 「[コード オーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」 | -| リポジトリのアーカイブ | 「[リポジトリのアーカイブ](/repositories/archiving-a-github-repository/archiving-repositories)」 |{% ifversion fpt or ghec %} -| セキュリティアドバイザリの作成 | 「[{% data variables.product.prodname_security_advisories %}について](/github/managing-security-vulnerabilities/about-github-security-advisories)」 | -| スポンサーボタンの表示 | 「[リポジトリにスポンサーボタンを表示する](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)」 |{% endif %} -| プルリクエストの自動マージを許可または禁止 | 「[リポジトリ内のプル リクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」 | +| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | +| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %} +| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" | +| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" | +| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" | +| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %} +| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %} +| 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 %} +| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" | +| 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)" | +| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[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)" |{% ifversion fpt or ghec %} +| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" | +| 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 %} +| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %} +| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %} +| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | +| Manage webhooks and deploy keys | "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" | -## 個人アカウントが所有しているリポジトリに対するコラボレーター アクセス権 +## Collaborator access for a repository owned by a personal account -個人リポジトリのコラボレータは、リポジトリのコンテンツをプル（読み取り）したり、リポジトリに変更をプッシュ（書き込み）したりすることができます。 +Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. {% note %} -**注:** プライベート リポジトリでは、リポジトリ オーナーはコラボレーターに書き込みアクセスしか付与できません。 個人アカウントが所有するリポジトリに対して、コラボレーターが読み取り専用アクセス権を持つことはできません。 +**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account. {% endnote %} -コラボレータは、次のアクションを実行することもできます。 +Collaborators can also perform the following actions. -| アクション | 説明を見る | +| Action | More information | | :- | :- | -| リポジトリのフォーク | 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」 | -| デフォルトブランチ以外のブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 | -| リポジトリ内のコミット、プルリクエスト、Issue に関するコメントの作成、編集、削除 | | -| リポジトリ内の Issue の作成、割り当て、クローズ、再オープン | 「[Issue で作業を管理する](/github/managing-your-work-on-github/managing-your-work-with-issues)」 | -| リポジトリ内の Issue とプルリクエストのラベル管理 | 「[Issue と Pull Request のラベル付け](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)」 | -| リポジトリ内の Issue とプルリクエストのマイルストーン管理 | 「[Issue と Pull Request のマイルストーンの作成と削除](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)」 | -| リポジトリ内の Issue またはプルリクエストを重複としてマーク | 「[Issue と Pull Request の重複について](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)」 | -| リポジトリ内のプルリクエストの作成、マージ、クローズ | 「[プル リクエストで、作業に対する変更を提案する](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)」 | -| プルリクエストの自動マージの有効化または無効化 | 「[プル リクエストを自動的にマージする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)」 -| リポジトリ内のプルリクエストに提案された変更を適用 |「[プル リクエストでのフィードバックを取り込む](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」 | -| リポジトリのフォークからプルリクエストを作成 | 「[フォークからプル リクエストを作成する](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)」 | -| プルリクエストのマージ可能性に影響するプルリクエストについてレビューを送信 | 「[プル リクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」 | -| リポジトリ用のウィキの作成と編集 | 「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」 | -| リポジトリ用のリリースの作成と編集 | 「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」 | -| リポジトリのコードオーナーの定義 | 「[コード オーナーについて](/articles/about-code-owners)」 |{% ifversion fpt or ghae or ghec %} -| パッケージの公開、表示、インストール | 「[パッケージの公開と管理](/github/managing-packages-with-github-packages/publishing-and-managing-packages)」 |{% endif %} -| リポジトリでコラボレーターである自身を削除する | 「[コラボレーターのリポジトリから自分を削除する](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)」 | +| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" | +| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" | +| Create, edit, and delete comments on commits, pull requests, and issues in the repository | | +| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" | +| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" +| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | +| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %} +| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} +| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | -## 参考資料 +## Further reading -- 「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」 +- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" 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 5409856a9d..6fd1dab0b3 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 @@ -231,19 +231,11 @@ For example, this `cleanup.js` will only run on Linux-based runners: ### `runs.steps` -{% 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. -{% endif %} #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The command you want to run. This can be inline or a script in your action repository: -{% else %} -**Required** The command you want to run. This can be inline or a script in your action repository: -{% endif %} {% raw %} ```yaml @@ -269,11 +261,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. -{% else %} -**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. -{% endif %} {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %} #### `runs.steps[*].if` @@ -322,7 +310,6 @@ steps: **Optional** Specifies the working directory where the command is run. -{% 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. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). @@ -371,7 +358,6 @@ runs: middle_name: The last_name: Octocat ``` -{% endif %} {% ifversion ghes > 3.5 or ghae > 3.5 %} diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md index 9d8f3e75a0..d6e76d766c 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md @@ -1,7 +1,7 @@ --- -title: Configuring OpenID Connect in HashiCorp Vault +title: HashiCorp Vault での OpenID Connect の構成 shortTitle: OpenID Connect in HashiCorp Vault -intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault. +intro: ワークフロー内で OpenID Connect を使用して HashiCorp Vault で認証します。 miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -10,31 +10,35 @@ versions: type: tutorial topics: - Security +ms.openlocfilehash: 174243818443709ee6ffe3b22aa668cff254266f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106630' --- +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +## 概要 -## Overview +OpenID Connect (OIDC) を使うと、{% data variables.product.prodname_actions %} ワークフローが HashiCorp Vault で認証し、シークレットを取得できます。 -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to authenticate with a HashiCorp Vault to retrieve secrets. +このガイドでは、HashiCorp Vault が {% data variables.product.prodname_dotcom %} の OIDC をフェデレーション ID として信頼するように構成する方法の概要について説明します。また、この構成を [hashicorp/vault-action](https://github.com/hashicorp/vault-action) アクションで使って HashiCorp Vault からシークレットを取得する方法を示します。 -This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault. - -## Prerequisites +## 前提条件 {% data reusables.actions.oidc-link-to-intro %} {% data reusables.actions.oidc-security-notice %} -## Adding the identity provider to HashiCorp Vault +## HashiCorp Vault への ID プロバイダーの追加 -To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt). +HashiCorp Vault と共に OIDC を使うには、{% data variables.product.prodname_dotcom %} OIDC プロバイダーの信頼構成を追加する必要があります。 詳細については、HashiCorp Vault の[ドキュメント](https://www.vaultproject.io/docs/auth/jwt)を参照してください。 -To configure your Vault server to accept JSON Web Tokens (JWT) for authentication: +認証に JSON Web トークン (JWT) を受け入れるように Vault サーバーを構成します。 -1. Enable the JWT `auth` method, and use `write` to apply the configuration to your Vault. - For `oidc_discovery_url` and `bound_issuer` parameters, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}. These parameters allow the Vault server to verify the received JSON Web Tokens (JWT) during the authentication process. +1. JWT `auth` メソッドを有効にし、`write` を使用して Vault に構成を適用します。 + `oidc_discovery_url` および `bound_issuer` パラメーターの場合は、{% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} を使います。 これらのパラメーターを使用すると、Vault サーバーは認証プロセス中に受信した JSON Web トークン (JWT) を確認できます。 ```sh{:copy} vault auth enable jwt @@ -45,7 +49,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \ oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" ``` -2. Configure a policy that only grants access to the specific paths your workflows will use to retrieve secrets. For more advanced policies, see the HashiCorp Vault [Policies documentation](https://www.vaultproject.io/docs/concepts/policies). +2. ワークフローがシークレットの取得に使用する特定のパスへのアクセスのみを許可するポリシーを構成します。 詳細なポリシーについては、HashiCorp Vault の [「ポリシー」のドキュメント](https://www.vaultproject.io/docs/concepts/policies)を参照してください。 ```sh{:copy} vault policy write myproject-production - <`: Replace this with the URL of your HashiCorp Vault. -- ``: Replace this with the Namespace you've set in HashiCorp Vault. For example: `admin`. -- ``: Replace this with the role you've set in the HashiCorp Vault trust relationship. -- ``: Replace this with the path to the secret you're retrieving from HashiCorp Vault. For example: `secret/data/production/ci npmToken`. +- ``: これを HashiCorp Vault の URL に置き換えます。 +- ``: これを HashiCorp Vault で設定した名前空間に置き換えます。 (例: `admin`)。 +- ``: これを HashiCorp Vault の信頼関係で設定したロールに置き換えます。 +- ``: これを HashiCorp Vault から取得するシークレットのパスに置き換えます。 たとえば、「`secret/data/production/ci npmToken`」のように入力します。 ```yaml{:copy} jobs: @@ -142,19 +146,19 @@ jobs: {% note %} -**Note**: +**注**: -- If your Vault server is not accessible from the public network, consider using a self-hosted runner with other available Vault [auth methods](https://www.vaultproject.io/docs/auth). For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- `` must be set for a Vault Enterprise (including HCP Vault) deployment. For more information, see [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces). +- Vault サーバーにパブリック ネットワークからアクセスできない場合は、他の使用可能な Vault の[認証方法](https://www.vaultproject.io/docs/auth)でセルフホステッド ランナーを使用することを検討してください。 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners)に関する記述をご覧ください。 +- `` は、Vault Enterprise (HCP Vault を含む) デプロイに対して設定する必要があります。 詳しくは、[Vault 名前空間](https://www.vaultproject.io/docs/enterprise/namespaces)に関するページを参照してください。 {% endnote %} -### Revoking the access token +### アクセス トークンの取り消し -By default, the Vault server will automatically revoke access tokens when their TTL is expired, so you don't have to manually revoke the access tokens. However, if you do want to revoke access tokens immediately after your job has completed or failed, you can manually revoke the issued token using the [Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self). +既定で、Vault サーバーでは TTL の有効期限が切れたときにアクセス トークンを自動的に取り消します。そのため、アクセス トークンを手動で取り消す必要はありません。 ただし、ジョブが完了または失敗した直後にアクセス トークンを取り消す場合は、[Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) を使用して発行されたトークンを手動で取り消すことができます。 -1. Set the `exportToken` option to `true` (default: `false`). This exports the issued Vault access token as an environment variable: `VAULT_TOKEN`. -2. Add a step to call the [Revoke a Token (Self)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API to revoke the access token. +1. `exportToken` オプションを `true` (既定値: `false`) に設定します。 これにより、発行された Vault アクセス トークンが環境変数としてエクスポートされます: `VAULT_TOKEN`。 +2. [トークンの取り消し (自己)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API を呼び出してアクセス トークンを取り消すステップを追加します。 ```yaml{:copy} jobs: @@ -183,4 +187,4 @@ jobs: run: | curl -X POST -sv -H "X-Vault-Token: {% raw %}${{ env.VAULT_TOKEN }}{% endraw %}" \ /v1/auth/token/revoke-self -``` \ No newline at end of file +``` diff --git a/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md index 351014a933..e08f35533a 100644 --- a/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md +++ b/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md @@ -1,7 +1,7 @@ --- -title: Using the GitHub CLI on a runner +title: ランナーでの GitHub CLI の使用 shortTitle: Use the GitHub CLI on a runner -intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).' +intro: '継続的インテグレーション (CI) のために高度な {% data variables.product.prodname_actions %} 機能を使用する方法。' versions: fpt: '*' ghes: '> 3.1' @@ -10,40 +10,34 @@ versions: type: how_to topics: - Workflows +ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a +ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148111586' --- - {% data reusables.actions.enterprise-github-hosted-runners %} -## Example overview +## サンプルの概要 -{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details. +{% data reusables.actions.example-workflow-intro-ci %}このワークフローがトリガーされると、{% data variables.product.prodname_dotcom %} Docs サイトに壊れたリンクがあるかどうかを確認するスクリプトが自動的に実行されます。 壊れたリンクが見つかった場合、ワークフローで詳しい情報を含む {% data variables.product.prodname_dotcom %} のイシューが {% data variables.product.prodname_dotcom %} CLI を使用して作成されます。 {% data reusables.actions.example-diagram-intro %} -![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png) +![ワークフローのステップの概要図](/assets/images/help/images/overview-actions-using-cli-ci-example.png) -## Features used in this example +## この例で使用されている機能 {% data reusables.actions.example-table-intro %} -| **Feature** | **Implementation** | +| **機能** | **実装** | | --- | --- | -{% data reusables.actions.cron-table-entry %} -{% data reusables.actions.permissions-table-entry %} -{% data reusables.actions.if-conditions-table-entry %} -{% data reusables.actions.secrets-table-entry %} -{% data reusables.actions.checkout-action-table-entry %} -{% data reusables.actions.setup-node-table-entry %} -| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| -| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | -| Running a script on the runner: | Using `script/check-english-links.js` | -| Generating an output file: | Piping the output using the `>` operator | -| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | -| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | +{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | サード パーティのアクションの使用: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | ランナーでのシェル コマンドの実行: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | ランナーでのスクリプトの実行: | `script/check-english-links.js` の使用 | | 出力ファイルの生成: | `>` 演算子を使用した出力のパイプ処理 | | {% data variables.product.prodname_cli %} を使用した既存のイシューの確認: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | {% data variables.product.prodname_cli %} を使用したイシューへのコメント: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | -## Example workflow +## ワークフローの例 -{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml). +{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml)。 {% data reusables.actions.note-understanding-example %} @@ -178,15 +172,15 @@ jobs: -## Understanding the example +## 例の説明 {% data reusables.actions.example-explanation-table-intro %} - - + + @@ -214,10 +208,10 @@ on: @@ -231,7 +225,7 @@ permissions: @@ -243,7 +237,7 @@ jobs: @@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file. @@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal' @@ -280,7 +274,7 @@ runs-on: ubuntu-latest @@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil @@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` @@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li @@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout` @@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version @@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case @@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script @@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze @@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var @@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th @@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
CodeExplanation"コード"説明
-Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow: +ワークフローのトリガーとして `workflow_dispatch` と `scheduled` を定義します。 -* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch). -* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule). +* `workflow_dispatch` を使用すると、UI からこのワークフローを手動で実行できます。 詳細については、「[`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)」を参照してください。 +* `schedule` イベントにより、`cron` 構文を使用して、ワークフローを自動的にトリガーするための一定の間隔を定義できます。 詳細については、「[`schedule`](/actions/reference/events-that-trigger-workflows#schedule)」を参照してください。
-Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)." +`GITHUB_TOKEN` に付与される既定のアクセス許可を変更します。 これはワークフローのニーズによって異なります。 詳しい情報については、「[ジョブへのアクセス許可の割り当て](/actions/using-jobs/assigning-permissions-to-jobs)」を参照してください。
-Groups together all the jobs that run in the workflow file. +ワークフロー ファイルで実行されるすべてのジョブをグループ化します。
-Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key. +ID `check_all_english_links` と名前 `Check all links` を持つジョブを定義します。これは `jobs` キー内に格納されます。
-Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_. +リポジトリが `docs-internal` という名前で、`github` という Organization 内にある場合のみ、`check_all_english_links` ジョブを実行します。 それ以外の場合、ジョブは _"スキップ済み"_ としてマークされます。
-Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)." +Ubuntu Linux ランナーで実行するようにジョブを設定します。 これは、ジョブが {% data variables.product.prodname_dotcom %} によってホストされている新しい仮想マシンで実行されるということです。 他のランナーを使う構文例については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)」を参照してください。
-Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow. +カスタム環境変数を作成し、組み込み `GITHUB_TOKEN` 変数を再定義してカスタム [シークレット](/actions/security-guides/encrypted-secrets)を使用します。 これらの変数は、ワークフローで後から参照されます。
-Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section. +`check_all_english_links` ジョブの一部として実行されるすべてのステップをグループ化します。 ワークフロー内の各ジョブには、独自の `steps` セクションがあります。
-The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository. +`uses` キーワードは、`actions/checkout` という名前のアクションを取得するようにジョブに指示します。 これは、リポジトリをチェックアウトしてランナーにダウンロードし、コードに対してアクション（テストツールなど）を実行できるようにします。 ワークフローがリポジトリのコードに対して実行されるとき、またはリポジトリで定義されたアクションを使用しているときはいつでも、チェックアウトアクションを使用する必要があります。
-This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command. +このステップでは、`actions/setup-node` アクションを使用して、指定したバージョンの `node` ソフトウェア パッケージをランナーにインストールします。これにより、`npm` コマンドにアクセスできるようになります。
-The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository. +`run` キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、Node.js アプリケーションをリポジトリにインストールしてビルドするための個別のステップとして、`npm ci` コマンドと `npm run build` コマンドが実行されます。
-This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`. +この `run` コマンドは、リポジトリの `script/check-english-links.js` に保存されているスクリプトを実行し、出力を `broken_links.md` というファイルにパイプで渡します。
-If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step). +`check-english-links.js` スクリプトで壊れたリンクが検出され、0 以外 (失敗) の終了状態が返された場合は、[ワークフロー コマンド](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter)を使用して、`broken_links.md` ファイルの先頭行の値を持つ出力を設定します (これは次のステップで使用されます)。
-Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA. +`peter-evans/create-issue-from-file` アクションを使用して、新しい {% data variables.product.prodname_dotcom %} のイシューを作成します。 この例は、`b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA を使用して、特定のバージョンのアクションに合わせて固定されています。
-Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output. +[`gh issue list`](https://cli.github.com/manual/gh_issue_list) を使用して、以前の実行から以前に作成したイシューを見つけます。 これには、後のステップでの処理を簡単にするために、`gh list-reports` という[別名](https://cli.github.com/manual/gh_alias_set)が付けられます。 イシューの URL を取得するために、`jq` 式で結果の JSON 出力を処理します。 -[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one. +次に [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、以前のイシューにリンクするコメントを新しいイシューに追加します。
-If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue. +以前の実行でのイシューが未解決であり誰かに割り当てられている場合は、[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。
-If an issue from a previous run is open and is not assigned to anyone, then: +以前の実行でのイシューが未解決であり誰にも割り当てられない場合は、次のようになります。 -* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue. -* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue. -* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board. +* [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。 +* [`gh issue close`](https://cli.github.com/manual/gh_issue_close) を使用して以前のイシューを閉じます。 +* [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) を使用して以前のイシューを編集し、特定の {% data variables.product.prodname_dotcom %} プロジェクト ボードから削除します。
-## Next steps +## 次の手順 {% data reusables.actions.learning-actions %} 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 f66ea675e4..1f447b00f9 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,13 +69,10 @@ 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 %} ## 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)." -{% endif %} - ## Usage limits There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change. @@ -249,7 +246,6 @@ codeload.github.com {% endnote %} - {% endif %} ## Self-hosted runner security diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 3ccfe230c8..3ea5bd9887 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -32,7 +32,7 @@ For more information, see "[About self-hosted runners](/github/automating-your-w {% endwarning %} {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} You can set up automation to scale the number of self-hosted runners. 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 89ba5d874e..01c8c1cb9f 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 @@ intro: You can automatically scale your self-hosted runners in response to webho versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' ghae: '*' type: overview --- diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md index 2629ad6dba..bdf5bb0bfb 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md +++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md @@ -608,7 +608,7 @@ jobs: ## `secrets` context -The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." +The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." `GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md index a7a52992a7..ba4f2ce5f5 100644 --- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md @@ -87,9 +87,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau | issues | read/write | none | read | | metadata | read | read | read | | packages | read/write | none | read | -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | pages | read/write | none | read | -{%- endif %} | pull-requests | read/write | none | read | | repository-projects | read/write | none | read | | security-events | read/write | none | read | diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md index cd8cf7b99a..693eb7bb34 100644 --- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md @@ -7,6 +7,8 @@ redirect_from: - /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow - /actions/reference/encrypted-secrets + - /actions/managing-workflows/storing-secrets + miniTocMaxHeadingLevel: 3 versions: fpt: '*' diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md index d8fba11f7c..97c4628d94 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md @@ -1,50 +1,49 @@ --- -title: より大きなランナーへのアクセスの制御 -intro: 'Organization または Enterprise に追加された {% data variables.actions.hosted_runner %} へのアクセスを、ポリシーを使って制限できます。' +title: Controlling access to larger runners +shortTitle: 'Control access to {% data variables.actions.hosted_runner %}s' +intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.' product: '{% data reusables.gated-features.hosted-runners %}' versions: feature: actions-hosted-runners type: tutorial -shortTitle: 'Controlling access to {% data variables.actions.hosted_runner %}s' -ms.openlocfilehash: 6761f05ef04d18ebba7b9ef8a2894d7effd2622b -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147764022' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## ランナー グループについて +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}詳しくは、[{% data variables.product.prodname_ghe_cloud %} のドキュメント](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners)をご覧ください。{% endif %} +## About runner groups + +{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %} {% ifversion ghec or ghes or ghae %} -## Organization のランナー グループを作成する +## Creating a runner group for an organization -{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-organization %} +{% data reusables.actions.hosted-runner-security-admonition %} +{% data reusables.actions.creating-a-runner-group-for-an-organization %} -## Enterprise のランナー グループを作成する +## Creating a runner group for an enterprise -{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-enterprise %} +{% data reusables.actions.hosted-runner-security-admonition %} +{% data reusables.actions.creating-a-runner-group-for-an-enterprise %} {% endif %} -## ランナー グループのアクセス ポリシーを変更する +## Changing the access policy of a runner group -{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.changing-the-access-policy-of-a-runner-group %} +{% data reusables.actions.hosted-runner-security-admonition %} +{% data reusables.actions.changing-the-access-policy-of-a-runner-group %} -## ランナー グループの名前を変更する +## Changing the name of a runner group {% data reusables.actions.changing-the-name-of-a-runner-group %} {% ifversion ghec or ghes or ghae %} -## ランナーをグループに移動する +## Moving a runner to a group {% data reusables.actions.moving-a-runner-to-a-group %} -## ランナー グループを削除する +## Removing a runner group {% data reusables.actions.removing-a-runner-group %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md index ed6b379be2..b0f14df4a0 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md @@ -1,11 +1,11 @@ --- title: Using larger runners -shortTitle: 'Larger runners' +shortTitle: Larger runners intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.' miniTocMaxHeadingLevel: 3 product: '{% data reusables.gated-features.hosted-runners %}' versions: - feature: 'actions-hosted-runners' + feature: actions-hosted-runners --- ## Overview of {% data variables.actions.hosted_runner %}s 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 190fb29822..710052edb7 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 @@ -139,8 +139,8 @@ The following table shows which toolkit functions are available within a workflo | Toolkit function | Equivalent workflow command | | ----------------- | ------------- | | `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.debug` | `debug` | +| `core.notice` | `notice` | | `core.error` | `error` | | `core.endGroup` | `endgroup` | | `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | @@ -216,8 +216,6 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} - ## Setting a notice message Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} @@ -245,7 +243,6 @@ Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` {% endpowershell %} -{% endif %} ## Setting a warning message @@ -584,6 +581,8 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines. +Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead. + {% powershell %} {% note %} diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 5c778a85ca..4969f6b53e 100644 --- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -32,7 +32,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays {% ifversion actions-run-name %} ## `run-name` -The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message. +The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message. This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts. diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md index ef0b9fc8fc..192df3affc 100644 --- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md +++ b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md @@ -1,7 +1,7 @@ --- title: Configuring dependency review for your appliance shortTitle: Configuring dependency review -intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.' +intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.' product: '{% data reusables.gated-features.dependency-review %}' miniTocMaxHeadingLevel: 3 versions: @@ -14,8 +14,6 @@ topics: - Security --- -{% data reusables.dependency-review.beta %} - ## About dependency review {% data reusables.dependency-review.feature-overview %} 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 ee72a7d813..d0e0a0fefc 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 @@ -15,6 +15,6 @@ topics: You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. 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){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}." -You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)." diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md index d4d24029d2..eb2b304a79 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -16,7 +16,7 @@ topics: {% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% ifversion ghes %} You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering. 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 8fa01e4e0d..d0b14cf91e 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 @@ -1,6 +1,6 @@ --- title: Enabling Dependabot for your enterprise -intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' +intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Dependabot redirect_from: @@ -26,7 +26,7 @@ topics: ## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %} -{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. +{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. ### About {% data variables.product.prodname_dependabot_alerts %} {% endif %} @@ -51,7 +51,7 @@ When {% data variables.location.product_location %} receives information about a For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." -{% ifversion ghes > 3.2 %} +{% ifversion ghes %} ### About {% data variables.product.prodname_dependabot_updates %} {% data reusables.dependabot.beta-security-and-version-updates %} @@ -124,7 +124,7 @@ After you enable {% data variables.product.prodname_dependabot_alerts %} for you ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) {% endif %} -{% ifversion ghes > 3.2 %} +{% ifversion ghes %} When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md index 0930d0297d..6c4cc51477 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md @@ -2,7 +2,7 @@ title: Configuring host keys for your instance shortTitle: Configure host keys intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.' -permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance." +permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.' versions: ghes: '>= 3.6' type: how_to diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md index c76cd8b27b..3d8a2df2fe 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md @@ -2,7 +2,7 @@ title: Configuring SSH connections to your instance shortTitle: Configure SSH connections intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.' -permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance." +permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.' versions: ghes: '>= 3.6' type: how_to diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md index 31e7fefdbf..814f55de38 100644 --- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md +++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md @@ -1,26 +1,21 @@ --- -title: リポジトリのキャッシュについて -intro: リポジトリのキャッシュを使用して、分散チームと CI ファームでの Git 読み取り操作のパフォーマンスを向上させることができます。 +title: About repository caching +intro: You can increase the performance of Git read operations for distributed teams and CI farms with repository caching. versions: - ghes: '>=3.3' + ghes: '*' type: overview topics: - Enterprise -ms.openlocfilehash: 06a0dd3ba202c73f1ee035d61f7865fadd13b415 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145120645' --- + {% data reusables.enterprise.repository-caching-release-phase %} -世界中にチームと CI ファームがある場合、{% data variables.product.prodname_ghe_server %} のプライマリ インスタンスのパフォーマンスが低下する可能性があります。 アクティブ geo レプリカを使うと読み取り要求のパフォーマンスが向上しますが、書き込みスループットが制限されます。 プライマリ インスタンスの負荷を軽減し、書き込みスループットのパフォーマンスを向上させるには、これらの地理的に分散したクライアントの近くに配置されたリポジトリの非同期読み取り専用ミラーであるリポジトリ キャッシュを構成できます。 +If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients. -リポジトリ キャッシュを使うと、CI ファームや分散チームの近くにリポジトリ データが提供されるため、{% data variables.product.product_name %} は、複数のクライアントにサービスを提供するために、同じ Git データを長距離ネットワーク リンク経由で何回も送信する必要がなくなります。 たとえば、プライマリ インスタンスが北米にあり、アジアの多くの場所でもそれを利用している場合は、アジアの CI ランナーが使用するためのリポジトリ キャッシュをアジアに設けるとメリットがあります。 +A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there. -リポジトリ キャッシュは、プライマリ インスタンス (単一インスタンスでも、geo レプリケートされたインスタンスのセットでも) で、Git データの変更をリッスンします。 CI ファームや他の読み取り負荷の高いコンシューマーは、プライマリ インスタンスの代わりにリポジトリ キャッシュからクローンしてフェッチします。 変更は、クライアントごとに 1 回ではなく、キャッシュ インスタンスごとに 1 回ずつ、定期的にネットワーク全体に反映されます。 通常、Git データは、データがプライマリ インスタンスにプッシュされてから数分以内に、リポジトリ キャッシュで使用できるようになります。 {% ifversion ghes > 3.3 %}CI システムは、[`cache_sync` Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) を使うことで、キャッシュで使用可能になったデータに対応できます。{% endif %} +The repository cache listens to the primary instance, whether that's a single instance or a geo-replicated set of instances, for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the repository cache instead of the primary instance. Changes are propagated across the network, at periodic intervals, once per cache instance rather than once per client. Git data will typically be visible on the repository cache within several minutes after the data is pushed to the primary instance. {% ifversion ghes > 3.3 %}The [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) can be used by CI systems to react to data being available in the cache.{% endif %} -リポジトリ キャッシュと同期できるようにするリポジトリを、きめ細かく制御できます。 Git データは、ユーザーが指定した場所にのみレプリケートされます。 +You have fine-grained control over which repositories are allowed to sync to the repository cache. Git data will only be replicated to the locations you specify. -{% data reusables.enterprise.repository-caching-config-summary %}詳しくは、「[リポジトリ キャッシュを構成する](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)」をご覧ください。 +{% data reusables.enterprise.repository-caching-config-summary %} For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)." diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index 424faf2ecb..26b4536eea 100644 --- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -1,107 +1,105 @@ --- -title: リポジトリ キャッシュの構成 -intro: リポジトリ キャッシュを構成するには、新しいアプライアンスを作成し、リポジトリ キャッシュをプライマリ アプライアンスに接続し、リポジトリ キャッシュに対するリポジトリ ネットワークのレプリケーションを構成します。 +title: Configuring a repository cache +intro: 'You can configure a repository cache by creating a new appliance, connecting the repository cache to your primary appliance, and configuring replication of repository networks to the repository cache.' versions: - ghes: '>=3.3' + ghes: '*' type: how_to topics: - Enterprise -ms.openlocfilehash: dced49e1e6795407e2e41f12275a310c3a98aaf1 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146332011' --- + {% data reusables.enterprise.repository-caching-release-phase %} -## リポジトリ キャッシュの構成について +## About configuration for repository caching -{% data reusables.enterprise.repository-caching-config-summary %}次に、リポジトリ キャッシュにレプリケートされるリポジトリ ネットワークを管理するデータの場所ポリシーを設定できます。 +{% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache. -クラスタリングでは、リポジトリ キャッシュはサポートされていません。 +Repository caching is not supported with clustering. -## リポジトリ キャッシュの DNS +## DNS for repository caches -プライマリ インスタンスとリポジトリ キャッシュの DNS 名は異なっている必要があります。 たとえば、プライマリ インスタンスが `github.example.com` にある場合は、キャッシュ名は `europe-ci.github.example.com` や `github.asia.example.com` に決定できます。 +The primary instance and repository cache should have different DNS names. For example, if your primary instance is at `github.example.com`, you might decide to name a cache `europe-ci.github.example.com` or `github.asia.example.com`. -CI マシンで、プライマリ インスタンスではなくリポジトリ キャッシュからフェッチするには、Git の `url..insteadOf` 構成設定を使用できます。 詳細については、Git ドキュメントにある「[`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf)」を参照してください。 +To have your CI machines fetch from the repository cache instead of the primary instance, you can use Git's `url..insteadOf` configuration setting. For more information, see [`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf) in the Git documentation. -たとえば、CI マシンのグローバル `.gitconfig` には、次の行が含まれます。 +For example, the global `.gitconfig` for the CI machine would include these lines. ``` [url "https://europe-ci.github.example.com/"] - insteadOf = https://github.example.com/ + insteadOf = https://github.example.com/ ``` -次に、`https://github.example.com/myorg/myrepo` をフェッチするように Git に要求すると、代わりに `https://europe-ci.github.example.com/myorg/myrepo` からフェッチされます。 +Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will instead fetch from `https://europe-ci.github.example.com/myorg/myrepo`. -## リポジトリ キャッシュの構成 +## Configuring a repository cache {% ifversion ghes = 3.3 %} -1. プライマリ {% data variables.product.prodname_ghe_server %} アプライアンスで、リポジトリ キャッシュの機能フラグを有効にします。 +1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching. ``` $ ghe-config cluster.cache-enabled true ``` {%- endif %} -1. 新しい {% data variables.product.prodname_ghe_server %} アプライアンスを希望するプラットフォームにセットアップします。 このアプライアンスがリポジトリ キャッシュになります。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。 +1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." {% data reusables.enterprise_installation.replica-steps %} -1. SSH を使用して、リポジトリ キャッシュの IP アドレスに接続します。 +1. Connect to the repository cache's IP address using SSH. ```shell - $ ssh -p 122 admin@REPLICA IP + $ ssh -p 122 admin@REPLICA-IP ``` {%- ifversion ghes = 3.3 %} -1. キャッシュ レプリカで、リポジトリ キャッシュの機能フラグを有効にします。 +1. On your cache replica, enable the feature flag for repository caching. ``` $ ghe-config cluster.cache-enabled true ``` -{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} -1. プライマリへの接続を確認し、リポジトリ キャッシュに対してレプリカ モードを有効にするには、`ghe-repl-setup` をもう一度実行します。 +{%- endif %} +{% data reusables.enterprise_installation.generate-replication-key-pair %} +{% data reusables.enterprise_installation.add-ssh-key-to-primary %} +1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again. ```shell - $ ghe-repl-setup PRIMARY IP + $ ghe-repl-setup PRIMARY-IP ``` -1. *CACHE-LOCATION* を、キャッシュがデプロイされているリージョンなどの英数字識別子に置き換えて、リポジトリ キャッシュに対して `cache_location` を設定します。 また、このキャッシュのデータセンター名も設定します。新しいキャッシュでは、同じデータセンター内の別のキャッシュからシード処理を試みます。 +1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter. ```shell - $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME + $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME ``` -{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %} -1. リポジトリ キャッシュへのリポジトリ ネットワークのレプリケーションを有効にするには、データの場所ポリシーを設定します。 詳細については、「[データの場所ポリシー](#data-location-policies)」を参照してください。 +{% data reusables.enterprise_installation.replication-command %} +{% data reusables.enterprise_installation.verify-replication-channel %} +1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)." -## データの場所ポリシー +## Data location policies -`spokesctl cache-policy` コマンドでリポジトリのデータの場所ポリシーを構成して、データの局所性を制御できます。 データの場所ポリシーによって、どのリポジトリ ネットワークがどのリポジトリ キャッシュにレプリケートされているかが決まります。 既定では、データの場所ポリシーが構成されるまで、どのリポジトリ キャッシュにもリポジトリ ネットワークはレプリケートされません。 +You can control data locality by configuring data location policies for your repositories with the `spokesctl cache-policy` command. Data location policies determine which repository networks are replicated on which repository caches. By default, no repository networks will be replicated on any repository caches until a data location policy is configured. -データの場所ポリシーは、Git コンテンツにのみ影響します。 Issue や pull request コメントなどのデータベース内のコンテンツは、ポリシーに関係なくすべてのノードにレプリケートされます。 +Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy. {% note %} -**注:** データの場所ポリシーは、アクセス制御と同じではありません。 リポジトリにアクセスできるユーザーを制御するには、リポジトリ ロールを使用する必要があります。 リポジトリ ロールの詳細については、「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。 +**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." {% endnote %} -`--default` フラグを使用して、すべてのネットワークをレプリケートするようにポリシーを構成できます。 たとえば、次のコマンドでは、すべてのリポジトリ ネットワークの 1 つのコピーを、`cache_location` が "kansas" であるリポジトリ キャッシュのセットにレプリケートするポリシーが作成されます。 +You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas". ``` $ ghe-spokesctl cache-policy set --default 1 kansas ``` -リポジトリ ネットワークのレプリケーションを構成するには、ネットワークのルートであるリポジトリを指定します。 リポジトリ ネットワークには、リポジトリとリポジトリのすべてのフォークが含まれます。 ネットワーク全体をレプリケートしないと、ネットワークの一部をレプリケートすることはできません。 +To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network. ``` $ ghe-spokesctl cache-policy set 1 kansas ``` -ネットワークのレプリカ数を 0 に指定すると、すべてのネットワークをレプリケートし、特定のネットワークを除外するポリシーをオーバーライドできます。 たとえば、次のコマンドでは、場所 "kansas" 内のリポジトリ キャッシュに、そのネットワークのコピーを含めることができないことが指定されます。 +You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network. ``` $ ghe-spokesctl cache-policy set 0 kansas ``` -特定のキャッシュの場所で、1 より大きいレプリカ数はサポートされていません。 +Replica counts greater than one in a given cache location are not supported. diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md index 62947f4f84..f84a25d1cc 100644 --- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md +++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md @@ -1,18 +1,13 @@ --- -title: リポジトリのキャッシュ -intro: ユーザーと CI クライアントに近い読み取り専用ミラーを提供するリポジトリ キャッシュを使用して、地理的に分散した Team のパフォーマンスを向上させることができます。 +title: Caching repositories +intro: 'You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.' versions: - ghes: '>=3.3' + ghes: '*' topics: - Enterprise children: - /about-repository-caching - /configuring-a-repository-cache -ms.openlocfilehash: 4c019db4ea99bc2383c4496fb9632e8723a7a02b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145112798' --- + {% data reusables.enterprise.repository-caching-release-phase %} diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md index 7eedd8aa5e..99e8a4d951 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md @@ -1,6 +1,6 @@ --- -title: Geo-replicationについて -intro: '{% data variables.product.prodname_ghe_server %} 上の Geo-replication は、地理的に分散したデータセンターからの要求を満たすために、複数のアクティブなレプリカを使用します。' +title: About geo-replication +intro: 'Geo-replication on {% data variables.product.prodname_ghe_server %} uses multiple active replicas to fulfill requests from geographically distributed data centers.' redirect_from: - /enterprise/admin/installation/about-geo-replication - /enterprise/admin/enterprise-management/about-geo-replication @@ -11,32 +11,26 @@ type: overview topics: - Enterprise - High availability -ms.openlocfilehash: 0e4e2feb161dd897172385bf25cf997268527fd3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332809' --- -アクティブなレプリカが複数あれば、最も近いレプリカへの距離を短くできます。 たとえばサンフランシスコ、ニューヨーク、ロンドンにオフィスを持つ組織は、プライマリのアプライアンスをニューヨークの近くのデータセンター内で動作させ、2つのレプリカをサンフランシスコとロンドンの近くのデータセンターで動作させることができます。 地理的な場所を認識するDNSを利用すれば、ユーザーは利用可能な最も近いサーバへ振り分けられ、リポジトリのデータに高速にアクセスできます。 ニューヨークの近くにあるアプライアンスをプライマリにすれば、ロンドンへのレイテンシが大きいサンフランシスコ近くのアプライアンスをプライマリにする場合に比べ、ホスト間のレイテンシの削減に役立ちます。 +Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London. -アクティブなレプリカは、自身では処理できないリクエストをプライマリインスタンスに中継します。 レプリカは、すべてのSSL接続をターミネートする接続点として機能します。 ホスト間のトラフィックは、暗号化されたVPN接続を通じて送信されます。これは、Geo-replicationなしの2ノードのHigh Availability構成に似ています。 +The active replica proxies requests that it can't process itself to the primary instance. The replicas function as a point of presence terminating all SSL connections. Traffic between hosts is sent through an encrypted VPN connection, similar to a two-node high availability configuration without geo-replication. -Git リクエストと、LFS やファイルアップロードなどの特定のファイルサーバーリクエストは、プライマリからデータをロードせずにレプリカから直接処理できます。 Webリクエストは常にプライマリにルーティングされますが、レプリカがユーザに近ければ、近くでSSLのターミネーションが行われることからリクエストは高速に処理されます。 +Git requests and specific file server requests, such as LFS and file uploads, can be served directly from the replica without loading any data from the primary. Web requests are always routed to the primary, but if the replica is closer to the user the requests are faster due to the closer SSL termination. -[Amazon の Route 53 サービス](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)など、Geo DNS は、geo レプリケーションがシームレスに機能するために必要です。 インスタンスのホスト名は、ユーザの場所に最も近いレプリカに解決されるべきです。 +Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), is required for geo-replication to work seamlessly. The hostname for the instance should resolve to the replica that is closest to the user's location. -## 制限事項 +## Limitations -レプリカへの書き込みリクエストには、データをプライマリとすべてのレプリカへ送信することが必要です。 これは、すべての書き込みのパフォーマンスが最も遅いレプリカによって制限されることを意味しますが、新しい Geo-replication レプリカは、プライマリからではなく、既存の同じ場所に配置された Geo-replication レプリカからデータの大部分をシードできます。 {% ifversion ghes > 3.2 %}書き込みスループットに影響を与えず、分散チームと大規模 CI ファームによって引き起こされる待機時間と帯域幅を減らすには、代わりにリポジトリ キャッシュを構成できます。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %} +Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)." -Geo-replication は、{% data variables.product.prodname_ghe_server %} インスタンスに容量を追加したり、不十分な CPU やメモリリソースに関連するパフォーマンスの問題を解決したりしません。 プライマリのアプライアンスがオフラインである場合、アクティブなレプリカはいかなる読み込みや書き込みのリクエストも処理できません。 +Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests. {% data reusables.enterprise_installation.replica-limit %} -## Geo-replication設定のモニタリング +## Monitoring a geo-replication configuration {% data reusables.enterprise_installation.monitoring-replicas %} -## 参考資料 -- 「[geo レプリケーションレプリカの作成](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)」 +## Further reading +- "[Creating geo-replication replicas](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md index b8c4366d1a..2254343985 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md @@ -13,12 +13,12 @@ topics: - High availability - Infrastructure shortTitle: About HA configuration -ms.openlocfilehash: 921a1a935bbfa930c77e2c72d7856f00d54d6016 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b54ca60c6cf1d79b9435ca8deedebec09ed39396 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332746' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109001' --- High Availability設定をする際には、プライマリからレプリカアプライアンスへのすべてのデータストア（Gitリポジトリ、MySQL、Redis、Elasticsearch）の一方方向の非同期レプリケーションが、自動的にセットアップされます。 ほとんどの {% data variables.product.prodname_ghe_server %} 構成設定も、{% data variables.enterprise.management_console %} パスワードを含めてレプリケートされます。 詳細については、「[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)」 (管理コンソールへのアクセス) を参照してください。 @@ -35,8 +35,8 @@ High Availability設定をする際には、プライマリからレプリカア High Availability設定は、以下に対するソリューションとしては適切ではありません。 - - **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。{% ifversion ghes > 3.2 %} - - **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %} + - **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。 + - **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。 - **プライマリ アプライアンスのバックアップ**: High Availabilityレプリカは、システム災害復旧計画のオフサイトバックアップを置き換えるものではありません。 データ破壊や損失の中には、プライマリからレプリカへ即座にレプリケーションされてしまうものもあります。 安定した過去の状態への安全なロールバックを保証するには、履歴スナップショットでの定期的なバックアップを行う必要があります。 - **ダウンタイムなしのアップグレード**: コントロールされた昇格のシナリオにおけるデータ損失やスプリットブレインの状況を避けるには、プライマリアプライアンスをメンテナンスモードにして、すべての書き込みが完了するのを待ってからレプリカを昇格させてください。 diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md index b3f1c3ec05..e70b4f1225 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md @@ -39,7 +39,7 @@ shortTitle: Create HA replica This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)." -{% data reusables.enterprise_clustering.network-latency %}{% ifversion ghes > 3.2 %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."{% endif %} +{% data reusables.enterprise_clustering.network-latency %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)." 1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica. ```shell diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index 24cfb85f46..5b9ed639d1 100644 --- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -17,7 +17,6 @@ topics: {% note %} **Notes:** -{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %} - Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance. - If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. - The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases). diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index c1c8100472..b4203f0a1d 100644 --- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -23,7 +23,6 @@ topics: shortTitle: Upgrading GHES --- -{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %} ## Preparing to upgrade @@ -70,8 +69,7 @@ There are two types of snapshots: | Azure | VM | | Hyper-V | VM | | Google Compute Engine | Disk | -| VMware | VM | {% ifversion ghes < 3.3 %} -| XenServer | VM | {% endif %} +| VMware | VM | ## Upgrading with a hotpatch diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index 986fa1a462..bb63cf03cc 100644 --- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -41,4 +41,4 @@ To restore a backup of {% data variables.location.product_location %} with {% da ``` {% data reusables.actions.apply-configuration-and-enable %} 1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." -1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." \ No newline at end of file +1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index c38c209a49..71088f9285 100644 --- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -156,7 +156,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. 1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows {% data reusables.dependabot.beta-security-and-version-updates %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index e9cbd20df8..3b7a7be889 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -12,11 +12,11 @@ children: - /enabling-github-actions-with-minio-gateway-for-nas-storage - /managing-self-hosted-runners-for-dependabot-updates shortTitle: Enable GitHub Actions -ms.openlocfilehash: 675bbbe0ccbb68d676602b0553c8534f1601bcf6 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 273e03407dd8c3c0a125e2c215a973c88aaf884b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145120446' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109060' --- diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index c8553798a2..921d01760d 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -12,13 +12,6 @@ topics: - Enterprise --- -{% ifversion ghes < 3.3 %} -{% note %} - -**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %} - -{% endnote %} -{% endif %} ## About {% data variables.product.prodname_actions %} for enterprises @@ -56,7 +49,6 @@ You can create your own unique automations, or you can use and adapt workflows f After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %} {% endif %} - ## Further reading - "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %} diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 739cb96d5d..5b79fefc07 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -23,8 +23,6 @@ topics: This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. -{% data reusables.enterprise.upgrade-ghes-for-actions %} - {% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. {% data reusables.actions.introducing-enterprise %} @@ -33,7 +31,6 @@ This article explains how site administrators can configure {% data variables.pr ## Review hardware requirements - {%- ifversion ghes < 3.6 %} The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %} @@ -50,14 +47,6 @@ The peak quantity of connected runners without performance loss depends on such {% endif %} -{%- ifversion ghes = 3.2 %} - -{% data reusables.actions.hardware-requirements-3.2 %} - -Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. - -{%- endif %} - {%- ifversion ghes = 3.3 %} {% data reusables.actions.hardware-requirements-3.3 %} @@ -88,7 +77,6 @@ Maximum concurrency was measured using multiple repositories, job duration of ap {%- endif %} - {%- ifversion ghes = 3.6 %} {% data reusables.actions.hardware-requirements-3.6 %} @@ -114,8 +102,7 @@ For more information about minimum hardware requirements for {% data variables.l - [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations) - [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations) - [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations) -- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %} -- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %} +- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations) {% data reusables.enterprise_installation.about-adjusting-resources %} 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 8fc4c6c049..0c3418282c 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,9 +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 or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners -{% endif %} You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines. @@ -122,14 +120,10 @@ Optionally, organization owners can further restrict the access policy of the ru For more information, see "[Managing access to self-hosted runners using groups](/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 or ghes > 3.2 %} - ## 5. Automatically scale your self-hosted runners Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." -{% endif %} - ## Next steps - You can monitor self-hosted runners and troubleshoot common issues. For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)." diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 8ac0a99e29..625a34aa98 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -18,8 +18,6 @@ topics: ![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png) -{% data reusables.enterprise.upgrade-ghes-for-actions %} - Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs. ## Governance and compliance @@ -102,7 +100,7 @@ You may need to upgrade the CPU and memory resources for {% data variables.locat You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." -{% ifversion ghec or ghes > 3.2 %} +{% ifversion ghec or ghes %} You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." {% endif %} 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 709907e154..79a2892040 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 @@ -31,7 +31,7 @@ Alternatively, if you want stricter control over which actions are allowed in yo {% data reusables.actions.github-connect-resolution %} -If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." +If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow.{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." {% endif %} ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions @@ -46,8 +46,6 @@ 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 %} - ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}. @@ -67,5 +65,3 @@ After using an action from {% data variables.product.prodname_dotcom_the_website **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository. {% endtip %} - -{% endif %} 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 e44a1c5cf1..7e1756c530 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,13 +33,11 @@ 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 %} {% 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.location.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)." {% endnote %} -{% endif %} ## Prerequisites 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 c75e4e6eef..585957f8c6 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,10 +47,8 @@ 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 %} {% 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.location.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)." {% endnote %} - {% endif %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index a448aa318d..2015dcd47d 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -1,5 +1,5 @@ --- -title: About Enterprise Managed Users +title: About {% data variables.product.prodname_emus %} shortTitle: About managed users intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' redirect_from: @@ -16,6 +16,7 @@ topics: - Authentication - Enterprise - SSO +allowTitleToDifferFromFilename: true --- ## About {% data variables.product.prodname_emus %} @@ -24,8 +25,6 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." - {% ifversion oidc-for-emu %} {% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)." @@ -46,6 +45,17 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% endnote %} +## About organization membership management + +Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." + +The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. + +- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. +- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization. + +To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)." + ## Identity provider support {% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods: diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md index 1054fee109..29ea2a82d2 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md @@ -145,7 +145,13 @@ After you enable LDAP sync, a synchronization job will run at the specified time A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group: - If a team's corresponding LDAP group has been removed, remove all members from the team. -- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories. +- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization and is not an owner of the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories. + + {% note %} + + **Note:** LDAP Sync will not remove a user from an organization if the user is an owner of that organization. Another organization owner will need to manually remove the user instead. + + {% endnote %} - If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md index 23d0a0af3e..30d03c2a46 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md @@ -15,12 +15,12 @@ topics: - Enterprise type: how_to shortTitle: Configure SAML SSO with Okta -ms.openlocfilehash: 2772285f266a2593e8fc0900b39602325d30c46d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: e9cbf6e70fb5e07f9cd2c5e27d9b952921e18fdc +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147094807' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109667' --- {% data reusables.enterprise-accounts.emu-saml-note %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md index 3688464fb7..34adc3917c 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md @@ -108,4 +108,4 @@ Ensure that you set the value for `Audience` on your IdP to the `EntityId` for { {% ifversion ghec %} {% data reusables.saml.authentication-loop %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index 7b1bb2788b..f9430e64fa 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -105,14 +105,6 @@ featuredLinks: - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}' - /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise - /admin/enterprise-support/about-github-enterprise-support - videos: - - title: GitHub in the Enterprise – Maya Ross - href: 'https://www.youtube-nocookie.com/embed/1-i39RqaxRs' - - title: What's new for GitHub Enterprise – Jarryd McCree - href: 'https://www.youtube-nocookie.com/embed/ZZviWZgrqhM' - - title: Enforcing information security policy through GitHub Enterprise – Thomas Worley - href: 'https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI' - videosHeading: GitHub Universe 2021 videos layout: product-landing versions: ghec: '*' @@ -133,11 +125,11 @@ children: - /guides - /release-notes - /all-releases -ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb +ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881156' +ms.lasthandoff: 10/26/2022 +ms.locfileid: '148111313' --- diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md index 9a50077926..3136c7cc0d 100644 --- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md +++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md @@ -18,14 +18,13 @@ children: - /installing-github-enterprise-server-on-hyper-v - /installing-github-enterprise-server-on-openstack-kvm - /installing-github-enterprise-server-on-vmware - - /installing-github-enterprise-server-on-xenserver - /setting-up-a-staging-instance shortTitle: Set up an instance -ms.openlocfilehash: 23fe586f2c4baa87a2e2b388685bf8e42d5e10a4 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 7c23ae31e8e976f2acc664f87fbff82ffe025a0e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881462' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109000' --- diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index ecfcde73e0..6ae6322477 100644 --- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/installation/setting-up-a-staging-instance - /admin/installation/setting-up-a-staging-instance versions: - ghes: "*" + ghes: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md index fd9d8dacf6..82146c1824 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md @@ -46,9 +46,7 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you {%- ifversion ghes %} - You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." {%- endif %} -{%- ifversion ghec or ghes > 3.2 or ghae %} - You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)." -{%- endif %} For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." 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 863a314cec..c4610e9a26 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 @@ -265,7 +265,6 @@ Action | Description | `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 %} ## `dependabot_alerts` category actions | Action | Description @@ -285,9 +284,8 @@ Action | Description | Action | Description |--------|------------- | `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated. -{%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 %} +{%- ifversion fpt or ghec or ghes %} ## `dependabot_security_updates` category actions | Action | Description @@ -1341,7 +1339,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi |--------|------------- | `staff.disable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks. | `staff.enable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks. -{%- ifversion ghes > 3.2 or ghae %} +{%- ifversion ghes or ghae %} | `staff.exit_fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}. | `staff.fake_login` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user. {%- endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md index 0bcdaf5744..5c4f84902a 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md @@ -1,8 +1,8 @@ --- title: Configuring the audit log for your enterprise -intro: "You can configure settings for your enterprise's audit log." +intro: You can configure settings for your enterprise's audit log. shortTitle: Configure audit logs -permissions: 'Enterprise owners can configure the audit log.' +permissions: Enterprise owners can configure the audit log. versions: feature: audit-data-retention-tab type: how_to @@ -53,4 +53,4 @@ Before you can enable Git events in the audit log, you must configure a retentio ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png) 1. Click **Save**. -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md index eb7ca4cae4..2d570ef443 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Using the audit log API for your enterprise -intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.' +intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.' shortTitle: Audit log API permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.' miniTocMaxHeadingLevel: 3 @@ -18,7 +18,7 @@ topics: ## Using the audit log API -You can interact with the audit log using the GraphQL API{% ifversion ghec or ghes > 3.2 or ghae %} or the REST API{% endif %}. +You can interact with the audit log using the GraphQL API or the REST API. Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time). @@ -106,7 +106,6 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries). -{% ifversion ghec or ghes > 3.2 or ghae %} ## Querying the audit log REST API To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor: @@ -137,5 +136,3 @@ curl -H "Authorization: Bearer TOKEN" \ --request GET \ "https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat" ``` - -{% endif %} diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md index 46374ba031..94a48882a7 100644 --- a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md @@ -9,15 +9,13 @@ type: overview topics: - Enterprise - Upgrades -ms.openlocfilehash: 196745ee4ededaf78bd5afe876e4afa09141e930 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: b3a2d340ef73ffe92f2117caf38a84e76ba0c8d1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145120205' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108851' --- -{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %} - {% data reusables.enterprise.constantly-improving %}{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %} 通常、機能リリースは四半期ごとに行われ、新機能と機能のアップグレードが含まれます。 {% ifversion ghae %}{% data variables.product.company_short %} は、エンタープライズを最新の機能リリースにアップグレードします。 Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %} diff --git a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md index 9305406cc8..9a64fab4c6 100644 --- a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md +++ b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md @@ -2,9 +2,9 @@ title: Migrating your enterprise to the Container registry from the Docker registry intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.' product: '{% data reusables.gated-features.packages %}' -permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}." +permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.' versions: - feature: 'docker-ghcr-enterprise-migration' + feature: docker-ghcr-enterprise-migration shortTitle: Migrate to Container registry topics: - Containers diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md index c23c175953..6a82551b48 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md @@ -20,12 +20,12 @@ topics: - Policies - Projects shortTitle: Project board policies -ms.openlocfilehash: 2066ab3fd36814150ff79457930d05909027513e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 2bb72b21094fadea8f584eb4749ed0cea69619ee +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147854136' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108797' --- ## エンタープライズ内のプロジェクトのポリシーについて diff --git a/translations/ja-JP/content/admin/policies/index.md b/translations/ja-JP/content/admin/policies/index.md index a9b6fca97b..d18ecee533 100644 --- a/translations/ja-JP/content/admin/policies/index.md +++ b/translations/ja-JP/content/admin/policies/index.md @@ -14,11 +14,11 @@ children: - /enforcing-policies-for-your-enterprise - /enforcing-policy-with-pre-receive-hooks shortTitle: Set policies -ms.openlocfilehash: 075d4f949435539c9c45ae651aedb0878f3317db -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 6fae4d9a9aa9c137be114b51eb90d79eb16d71df +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147400371' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109115' --- diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index b9e44eabf6..f549b95eb5 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -33,11 +33,11 @@ children: - /managing-projects-using-jira - /continuous-integration-using-jenkins shortTitle: Manage organizations -ms.openlocfilehash: 5d1430bc4efff03e6cddfe81f3c018d4f2064155 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 333d9b8d50bcdb86f709a447fee5a4078353dfe2 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884246' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109114' --- diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md index 874c4cddc2..4cb891b65b 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md @@ -3,7 +3,7 @@ title: ユーザーの偽装 intro: トラブルシューティング、ブロック解除、その他の正当な理由のために、ユーザーを偽装し、ユーザーに代わってアクションを実行できます。 permissions: Enterprise owners can impersonate users within their enterprise. versions: - ghes: '>3.2' + ghes: '*' ghae: '*' type: how_to topics: @@ -11,12 +11,12 @@ topics: - Enterprise - User account shortTitle: Impersonate a user -ms.openlocfilehash: 8e237c6ace7e7feb4badefcbd863b0974c983732 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: df0513c3ca2931378e656f228939540dd5ea5816 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145116269' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109291' --- ## ユーザーの偽装について diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md index 7c31b6ef5c..e96df0c9c6 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md @@ -36,11 +36,11 @@ children: - /customizing-user-messages-for-your-enterprise - /rebuilding-contributions-data shortTitle: Manage users -ms.openlocfilehash: 9ec6d7dc6822e71ff72542dd6b67ded031a1c44d -ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4 +ms.openlocfilehash: 763277882c2af96505c2a6d4c236c05475ab9f3f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147878519' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148008663' --- diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 0596124afa..9fed0e1cbb 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -1,7 +1,7 @@ --- title: Viewing people in your enterprise intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.' -permissions: 'Enterprise owners can view the people in an enterprise.' +permissions: Enterprise owners can view the people in an enterprise. redirect_from: - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account - /articles/viewing-people-in-your-enterprise-account @@ -116,7 +116,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in ## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %} -If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." +If your enterprise uses {% data variables.product.prodname_emus %}, you can view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} @@ -129,6 +129,21 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can also You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)." +{% ifversion filter-by-enterprise-member-type %} +## Filtering by member type{% ifversion ghec %} in an {% data variables.enterprise.prodname_emu_enterprise %}{% endif %} + +{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is mananaged in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users#about-organization-membership-management)."{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +1. Under "Organizations," in the search bar, begin typing the organization's name until the organization appears in the search results, then click the name of the organization. + ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png) +1. Under the organization name, click {% octicon "person" aria-label="The Person icon" %} **People**. + ![Screenshot of the People tab](/assets/images/help/enterprises/emu-organization-people-tab.png) +1. Above the list of members, click **Type**, then select the type of members you want to view. + ![Screenshot of the "Type" button](/assets/images/help/enterprises/filter-by-member-type.png) + +{% endif %} + {% ifversion ghec or ghes %} ## Viewing members without an email address from a verified domain diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index c0787f5ae1..b2c8f13f0b 100644 --- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -24,13 +24,15 @@ If you can't access {% data variables.product.product_name %}, contact your loca {% endif %} -{% ifversion fpt or ghec %} +{% ifversion ghec %} {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} -When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. +When you attempt to access most resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. + +{% data reusables.saml.resources-without-sso %} {% data reusables.saml.outside-collaborators-exemption %} 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 88febb34fe..2a8409c383 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 @@ -1,6 +1,6 @@ --- title: Creating a personal access token -intro: You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API. +intro: 'You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.' redirect_from: - /articles/creating-an-oauth-token-for-command-line-use - /articles/creating-an-access-token-for-command-line-use @@ -17,7 +17,7 @@ versions: topics: - Identity - Access management -shortTitle: Create a {% data variables.product.pat_generic %} +shortTitle: 'Create a {% data variables.product.pat_generic %}' --- {% warning %} @@ -112,9 +112,9 @@ If you selected an organization as the resource owner and the organization requi {% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %} {% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %} 5. Give your token a descriptive name. - ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} + ![Token description field](/assets/images/help/settings/token_description.png) 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 %} + ![Token expiration field](/assets/images/help/settings/token_expiration.png) 7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)". {% ifversion fpt or ghes or ghec %} ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif) @@ -143,5 +143,5 @@ Instead of manually entering your {% data variables.product.pat_generic %} for e ## Further reading -- "[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 %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)" +- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)" 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 477a01b0a1..ca865d3bdf 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 @@ -109,7 +109,7 @@ An overview of some of the most common actions that are recorded as events in th | Action | Description |------------------|------------------- | `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 %} +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation). {% 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 877fedd33b..4b4832b39c 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 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 has expired or 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,11 +24,9 @@ This article explains the possible reasons your {% data variables.product.produc {% endnote %} -{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Token revoked after reaching its expiration date When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." -{% endif %} {% ifversion fpt or ghec %} ## Token revoked when pushed to a public repository or public gist diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md index 203deb10cc..b522f9eec2 100644 --- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md +++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md @@ -15,12 +15,12 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: 9b37417ab81bf51e39e41fcbed3a9b64cb4fe7bc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 8550393cc31571756099ac364698434f38b02cfa +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147653227' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106750' --- {% data reusables.gpg.desktop-support-for-commit-signing %} @@ -42,7 +42,7 @@ Git バージョン 2.0.0 以降で、ローカル リポジトリ用に既定 1. ローカルブランチに変更をコミットする場合、 -S フラグをGitコミットコマンドに追加します。 ```shell - $ git commit -S -m "your commit message" + $ git commit -S -m "YOUR_COMMIT_MESSAGE" # Creates a signed commit ``` 2. GPG を使用している場合は、コミットを作成した後、[GPG キーを生成](/articles/generating-a-new-gpg-key)したときに設定したパスフレーズを指定します。 diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md index 5ec53bdfe9..15f50e1148 100644 --- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md +++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md @@ -14,23 +14,23 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: d93cfae4a6e128c2aef79ee1494fb66f30afcf1b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 22bdc1c5095a8fa82d2ac406a19dc633f8f44fc6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147653363' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106678' --- {% data reusables.gpg.desktop-support-for-commit-signing %} 1. タグに署名するには、`git tag` コマンドに `-s` を追加します。 ```shell - $ git tag -s mytag + $ git tag -s MYTAG # Creates a signed tag ``` 2. `git tag -v [tag-name]` を実行して署名されたタグを検証します。 ```shell - $ git tag -v mytag + $ git tag -v MYTAG # Verifies the signed tag ``` diff --git a/translations/ja-JP/content/billing/index.md b/translations/ja-JP/content/billing/index.md index 28a077d3de..eb7972bf01 100644 --- a/translations/ja-JP/content/billing/index.md +++ b/translations/ja-JP/content/billing/index.md @@ -54,11 +54,11 @@ children: - /managing-billing-for-github-marketplace-apps - /managing-billing-for-git-large-file-storage - /setting-up-paid-organizations-for-procurement-companies -ms.openlocfilehash: 816bfb699135974a180ccf350aa04bc36dfbf25a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 977d170024ddec1d49f51723b654ee7171915e94 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147110899' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109292' --- diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md index b565c2a921..839d5dc496 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md @@ -11,3 +11,4 @@ children: - /viewing-your-github-codespaces-usage - /managing-spending-limits-for-github-codespaces --- + diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md index 9652fd43bd..68d34a6ab0 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md @@ -54,4 +54,4 @@ Enterprise owners and billing managers can view {% data variables.product.prodna ## Further reading -- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)" \ No newline at end of file +- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)" diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md index 5f06513eaa..57706ab231 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md @@ -72,9 +72,12 @@ In addition to licensed seats, your bill may include other charges, such as {% d - Enterprise owners who are a member or owner of at least one organization in the enterprise - Organization members, including owners - Outside collaborators on private or internal repositories owned by your organization, excluding forks +- Dormant users + +If your enterprise does not use {% data variables.product.prodname_emus %}, you will also be billed for each of the following accounts: + - Anyone with a pending invitation to become an organization owner or member - Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks -- Dormant users {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md index f099033153..f05b439418 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md @@ -18,11 +18,11 @@ children: - /phase-4-create-internal-documentation - /phase-5-rollout-and-scale-code-scanning - /phase-6-rollout-and-scale-secret-scanning -ms.openlocfilehash: c5624ca33d347e1be1c7bfc9a687f1c06bb828ed -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 5430d24ecf8979f5421c6f3fea9f10ad3f580e4c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147145433' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109721' --- diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md index 5291f45737..ca20e5f4d1 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md @@ -14,12 +14,12 @@ redirect_from: - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise - /admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise miniTocMaxHeadingLevel: 2 -ms.openlocfilehash: 0993205a2f51262c0766062995caa1c2e2714742 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b +ms.openlocfilehash: f42a461b3c53565725d6909680fa8e6a202c0439 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147145426' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109716' --- ## これらの記事について diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md index 1a0a6f1d2b..8d534fbf93 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md @@ -9,12 +9,12 @@ topics: - Advanced Security shortTitle: 1. Align on strategy miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 63154ac960e4b3a9d29f41e72cd925230838069c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b2677cf11c300ad657f9bd6b8862fb1f292c2fb7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147145401' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109709' --- {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md index 4c7306d6c1..ddf5131541 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md @@ -9,12 +9,12 @@ topics: - Advanced Security shortTitle: 2. Preparation miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: a34711765e8beb6d57215c0c8fd16519e975539d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 79368897c125ff23541520a253a34a2aae8c7c27 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147145393' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109715' --- {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md index 90864af28a..c5d40cda24 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md @@ -9,12 +9,12 @@ topics: - Advanced Security shortTitle: 3. Pilot programs miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 3df893158c402b9180260ddd1c82c96f62b84717 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: d56427173580558a192d0709ae700cbd497e2935 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147145394' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109109' --- {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md index 9da136bdc0..5e87bf25c1 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md @@ -9,12 +9,12 @@ topics: - Advanced Security shortTitle: 4. Create internal documentation miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: e9852eacc95b98eca5358aafb9a9b13811888f15 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: caf35f06c3f836ea7532b7c5e9dfb419ba8c325b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147145385' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109108' --- {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md index 72e531fe38..28899aa01f 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md @@ -9,12 +9,12 @@ topics: - Advanced Security shortTitle: 5. Rollout code scanning miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 69c5a4e88c5490cbd7dcddca902426862047dff5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: abbcdf4c1e4a231a568e8d8cd488877ebdf2fd9f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147145386' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109103' --- {% note %} diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md index f764f3fee2..7cf84a8886 100644 --- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md @@ -1,6 +1,6 @@ --- -title: 'フェーズ 6: secret scanning のロールアウトとスケーリング' -intro: 'この最後のフェーズでは、{% data variables.product.prodname_secret_scanning %} のロールアウトについて重点的に取り上げます。 {% data variables.product.prodname_secret_scanning_caps %} は、必要な構成が少ないため、{% data variables.product.prodname_code_scanning %} よりも簡単にロールアウトできるツールですが、新しい結果と古い結果を処理するための戦略を策定することが重要です。' +title: 'Phase 6: Rollout and scale secret scanning' +intro: 'For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it''s critical to have a strategy for handling new and old results.' versions: ghes: '*' ghae: '*' @@ -9,103 +9,98 @@ topics: - Advanced Security shortTitle: 6. Rollout secret scanning miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: f116bd8aad09639fb3c2fad4aa85bfa9a8b3401d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147650390' --- + {% note %} -この記事は、{% data variables.product.prodname_GH_advanced_security %} の大規模な導入に関するシリーズの一部です。 このシリーズの前の記事については、「[フェーズ 5: code scanning のロールアウトとスケーリング](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)」を参照してください。 +This article is part of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)." {% endnote %} -Organization 内の個々のリポジトリまたはすべてのリポジトリに対して secret scanning を有効にすることができます。 詳しい情報については、「[リポジトリのセキュリティと分析設定を管理する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)」または「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 +You can enable secret scanning for individual repositories or for all repositories in an organization. For more information, see "[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)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -この記事では、Organization 内のすべてのリポジトリに対する {% data variables.product.prodname_secret_scanning %} の有効化に重点を置いてプロセスの概要について説明します。 この記事で説明する原則は、時間をずらして、個々のリポジトリに対して {% data variables.product.prodname_secret_scanning %} を有効にする場合でも適用できます。 +This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. -### 1. 新しくコミットされたシークレットに集中する +### 1. Focus on newly committed secrets -{% data variables.product.prodname_secret_scanning %} を有効にする場合、secret scanning によって検出された、新しくコミットされた資格情報の修復に集中する必要があります。 コミットされた資格情報のクリーンアップに集中すると、開発者は誤って新しい視覚情報をプッシュし続ける可能性があります。つまり、シークレットの合計数は、意図したとおりに減少せず、ほぼ同じレベルにとどまります。 現在のシークレットを取り消すことに集中する前に、新しい資格情報が漏洩するのを止めることが不可欠なのは、このためです。 +When you enable {% data variables.product.prodname_secret_scanning %}, you should focus on remediating any newly committed credentials detected by secret scanning. If you focus on cleaning up committed credentials, developers could continue to accidentally push new credentials, which means your total secret count will stay around the same level, not decrease as intended. This is why it is essential to stop new credentials being leaked before focusing on revoking any current secrets. -新しくコミットされた資格情報に取り組むためのアプローチはいくつかありますが、その一例は次のとおりです。 +There are a few approaches for tackling newly committed credentials, but one example approach would be: -1. **通知**: Webhook を使用して、新しいシークレット アラートが、可能な限り迅速に適切なチームに表示されるようにします。 Webhook は、シークレット アラートが作成または解決されるか、もう一度開かれたときに発生します。 その後、Webhook ペイロードを解析し、Slack、Teams、Splunk、メールなど、自分やチームが使用するツールと統合できます。 詳しい情報については、「[Webhook について](/developers/webhooks-and-events/webhooks/about-webhooks)」および「[Webhook イベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)」を参照してください。 -2. **フォローアップ**: すべてのシークレットの種類に対して機能する高度な修復プロセスを作成します。 たとえば、シークレットをコミットした開発者とそのプロジェクトの技術リーダーに連絡し、シークレットを GitHub にコミットする危険性を強調し、検出されたシークレットの取り消しと更新を依頼することができます。 +1. **Notify**: Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)." +2. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to GitHub, and asking the them to revoke, and update the detected secret. {% note %} - **注:** この手順を自動化できます。 数百のリポジトリを持つ大規模な Enterprise および Organization の場合、手動によるフォローアップを持続するのは不可能です。 最初の手順で定義した Webhook プロセスに自動化を取り入れることができます。 Webhook ペイロードには、漏洩したシークレットに関するリポジトリおよび Organization 情報が含まれます。 この情報を使って、リポジトリの現在のメンテナンス担当者に連絡し、責任者宛のメールやメッセージを作成したり、issue を開いたりすることができます。 + **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue. {% endnote %} -3. **教育**: シークレットをコミットした開発者に割り当てる内部トレーニング ドキュメントを作成します。 このトレーニング ドキュメントでは、シークレットをコミットすることによって生じるリスクを説明し、開発中のシークレットの安全な使用についてベスト プラクティス情報を指示します。 開発者が経験から学ばず、シークレットのコミットを続ける場合、エスカレーション プロセスを作成できますが、通常は教育する方が効果的です。 +3. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If the a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well. -漏洩した新しいシークレットについて最後の 2 つの手順を繰り返します。 このプロセスにより、開発者はコードで使用されるシークレットを安全に管理することに対して責任を負うようになり、新しくコミットされたシークレットの削減を測定できます。 +Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets. {% note %} -**注:** より先進的な組織では、特定の種類のシークレットの自動修正を実行することが必要な場合があります。 [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) と呼ばれるオープンソース イニシアチブがあります。これを AWS、Azure、または GCP 環境にデプロイし、最も重要として定義した内容に基づいて特定の種類のシークレットを自動的に取り消すように調整できます。 これは、より自動化されたアプローチでコミットされる新しいシークレットに対応できる優れた方法でもあります。 +**Note:** More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach. {% endnote %} -### 2. 以前にコミットされたシークレットを最も重要なものから順に修復する +### 2. Remediate previously committed secrets, starting with the most critical -新しく公開されたシークレットを監視、通知、修復するプロセスを確立したら、{% data variables.product.prodname_GH_advanced_security %} が導入される前にコミットされたシークレットの作業を開始できます。 +After you have established a process to monitor, notify and remediate newly published secrets, you can start work on secrets committed before {% data variables.product.prodname_GH_advanced_security %} was introduced. -最も重要なシークレットを定義する方法は、Organization のプロセスと統合によって異なります。 たとえば、企業は Slack を使用していない場合、Slack Incoming Webhook のシークレットについて心配しない可能性があります。 Organization にとって最も重要な資格情報の種類の上位 5 つに注目することから始めると便利な場合があります。 +How you define your most critical secrets will depend on your organization's processes and integrations. For example, a company likely isn’t worried about a Slack Incoming Webhook secret if they don’t use Slack. You may find it useful to start by focusing on the top five most critical credential types for your organization. -シークレットの種類を決定したら、次の手順を実行できます。 +Once you have decided on the secret types, you can do the following: -1. 各種類のシークレットを修復するためのプロセスを定義します。 多くの場合、実際の手順は、シークレットの種類によって大きく異なります。 ドキュメントまたは内部のナレッジ ベースに、シークレットの種類ごとのプロセスを書き留めます。 +1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base. {% note %} - **注:** シークレットを取り消すためのプロセスを作成する場合、中央のチームではなく、リポジトリを保守しているチームにシークレットを取り消す責任を与えます。 GHAS の原則の 1 つは、特に、開発者がセキュリティ イシューを作成した場合、開発者がセキュリティの所有権を取得し、セキュリティ イシューを修正する責任を担うことです。 + **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them. {% endnote %} -2. 資格情報を取り消すためにチームが従うプロセスを作成したら、シークレットの種類と、漏洩したシークレットに関連付けられているその他のメタデータに関する情報を照合して、新しいプロセスの伝達先を識別することができます。 +2. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to. {% ifversion not ghae %} - この情報を収集するには、セキュリティの概要を使用できます。 セキュリティの概要の使用に関する詳しい情報については、「[セキュリティの概要でのアラートのフィルタリング](/code-security/security-overview/filtering-alerts-in-the-security-overview)」を参照してください。 + You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)." {% endif %} - 収集する必要がある情報としては、次のものがあります。 + Some information you may want to collect includes: - Organization - - リポジトリ - - シークレットの種類 - - シークレット値 - - 連絡先のリポジトリの保守管理者 + - Repository + - Secret type + - Secret value + - Maintainers on repository to contact {% note %} - **注:** その種類の漏洩したシークレットが少ない場合は、UI を使用します。 数百ものシークレットが漏洩した場合は、API を使用して情報を収集します。 詳しい情報については、「[secret scanning REST API](/rest/reference/secret-scanning)」を参照してください。 + **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[Secret scanning REST API](/rest/reference/secret-scanning)." {% endnote %} -3. 漏洩したシークレットに関する情報を収集したら、シークレットの各種類によって影響を受けるリポジトリを保守しているユーザーを対象とした通信計画を作成します。 電子メールまたはメッセージングを使用でき、影響を受けるリポジトリに GitHub イシューを作成することもできます。 これらのツールによって提供される API を使用して自動的に連絡を送信できる場合、これにより、複数のシークレットの種類にまたがって簡単にスケーリングできます。 +3. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types. -### 3. プログラムを拡張してより多くのシークレットの種類とカスタム パターンを含める +### 3. Expand the program to include more secret types and custom patterns -これで、5 つの最も重要なシークレットの種類を超えて、教育にさらに焦点を当てた、より包括的なリストに拡張できます。 対象としたさまざまなシークレットの種類について前の手順を繰り返し、以前にコミットされたシークレットを修正できます。 +You can now expand beyond the five most critical secret types into a more comprehensive list, with an additional focus on education. You can repeat the previous step, remediating previously committed secrets, for the different secret types you have targeted. -また、初期のフェーズで照合されたより多くのカスタム パターンを含めて、さらに多くのパターンを送信するようにセキュリティ チームや開発者チームに促し、新しいシークレットの種類タイプが作成されたときに新しいパターンを送信するプロセスを確立することもできます。 詳細については、[シークレット スキャンのカスタム パターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)に関する記事を参照してください。 +You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% ifversion secret-scanning-push-protection %} -また、secret scanning を使用してプッシュ保護を有効にすることもできます。 有効にすると、secret scanning により、信頼度の高いシークレットについてプッシュがチェックされ、ブロックされます。 詳細については、「[Protecting pushes with secret scanning (シークレット スキャンによるプッシュの保護)](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)」を参照してください。 +You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)." {% endif %} -他のシークレットの種類の修復プロセスを引き続き構築する際は、組織内の GitHub のすべての開発者と共有できるプロアクティブなトレーニング資料の作成を開始します。 この時点まで、焦点の多くはリアクティブでした。 焦点をプロアクティブに変えて、まず、開発者が GitHub に資格情報をプッシュしないように促すことは、優れたアイデアです。 これは複数の方法で実現できますが、リスクと理由を説明する短いドキュメントを作成することが出発点として適しています。 +As you continue to build your remediation processes for other secret types, start to create proactive training material that can be shared with all developers of GitHub in your organization. Until this point, a lot of the focus has been reactive. It is an excellent idea to shift focus to being proactive and encourage developers not to push credentials to GitHub in the first place. This can be achieved in multiple ways but creating a short document explaining the risks and reasons would be a great place to start. {% note %} -これは、{% data variables.product.prodname_GH_advanced_security %} の大規模な導入に関するシリーズの最後の記事です。 ご質問がある場合、またはサポートが必要な場合は、「[{% data variables.product.prodname_GH_advanced_security %} の大規模な導入の概要](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)」にある {% data variables.contact.github_support %} と {% data variables.product.prodname_professional_services_team %} に関するセクションを参照してください。 +This is the final article of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. If you have questions or need support, see the section on {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} in "[Introduction to adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)." {% endnote %} 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 e7a4e2b032..bfb8740fb1 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,9 +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 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 %} ### Scanning pull requests @@ -85,9 +83,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 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 %} +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)." ### Defining the severities causing pull request check failure diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md index 9135c91197..1220575d5d 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md @@ -41,7 +41,7 @@ For general information about configuring {% data variables.product.prodname_cod ## About autobuild for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository. -For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %} +For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %} {% data reusables.code-scanning.autobuild-compiled-languages %} @@ -90,6 +90,20 @@ The `autobuild` process attempts to autodetect a suitable build method for C# us If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them. 3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows). +### Go + +| Supported system type | System name | +|----|----| +| Operating system | Windows, macOS, and Linux | +| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts | + +The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files: + +1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed. +2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies. +3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes. +4. Extract all Go code in the repository, similar to running `go build ./...`. + ### Java | Supported system type | System name | @@ -107,12 +121,12 @@ The `autobuild` process tries to determine the build system for Java codebases b {% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." -After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. +After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. ``` yaml - run: | - make bootstrap - make release + make bootstrap + make release ``` For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)." 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 56ea5e3cc3..d4e421b540 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 @@ -153,12 +153,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch 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. -{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} - -{% elsif ghes < 3.5 or ghae %} -If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion ghes > 3.2 or ghae %}an "Analysis not found"{% elsif ghes = 3.2 %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +{% ifversion ghes < 3.5 or ghae %} +If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see an "Analysis not found" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion ghes > 3.2 or ghae %} ![Analysis not found for commit message](/assets/images/enterprise/3.4/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 +164,8 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ### Reasons for the "Analysis not found" message -{% elsif ghes = 3.2 %} - ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) -### 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 ghes > 3.2 or ghae %}"Analysis not found"{% elsif ghes = 3.2 %}"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 "Analysis not found" 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 ec6da4e48a..acf7f647a3 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 @@ -35,9 +35,7 @@ In repositories where {% data variables.product.prodname_code_scanning %} is con 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 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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." @@ -49,10 +47,9 @@ 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 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)." +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 %} ### {% data variables.product.prodname_code_scanning_capc %} results check failures diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 658d44b582..11529ccbee 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -49,7 +49,7 @@ To produce more detailed logging output, you can enable step debug logging. For ## Creating {% data variables.product.prodname_codeql %} debugging artifacts You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}. -The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. +The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data. @@ -59,11 +59,10 @@ These artifacts will help you debug problems with {% data variables.product.prod ### Creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs with debug logging enabled -You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." +You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." You need to ensure that you select **Enable debug logging** . This option enables runner diagnostic logging and step debug logging for the run. You'll then be able to download `debug-artifacts` to investigate further. You do not need to modify the workflow file when creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs. - {% endif %} {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} @@ -87,7 +86,7 @@ If an automatic build of code for a compiled language within your project fails, - Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. +- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step: @@ -131,14 +130,15 @@ If your workflow fails with an error `No source code was seen during the build` ``` For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. -1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. -1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are: - * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)." - * Building using a distributed build system external to GitHub Actions, using a daemon process. - * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. +1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. +1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. +1. Your compiled code (in C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are: + + - Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)." + - Building using a distributed build system external to GitHub Actions, using a daemon process. + - {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. @@ -151,9 +151,10 @@ If your workflow fails with an error `No source code was seen during the build` If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}. -For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." {% ifversion fpt or ghes > 3.1 or ghae or ghec %} + ## Lines of code scanned are lower than expected For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons: @@ -163,12 +164,13 @@ For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.p If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled. -### Replace the `autobuild` step +### Replace the `autobuild` step Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan. -For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." +For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database + You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`. ```yaml @@ -188,12 +190,13 @@ The artifact will contain an archived copy of the source files scanned by {% dat ## Extraction errors in the database -The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. +The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis. However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly. {% else %} + ## Portions of my repository were not analyzed using `autobuild` The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." @@ -201,7 +204,7 @@ The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuris ## The build takes too long -If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. +If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. ### Increase the memory or cores @@ -225,7 +228,7 @@ If your analysis is still too slow to be run during `push` or `pull_request` eve ### Check which query suites the workflow runs -By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results. +By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results. You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)." @@ -237,6 +240,7 @@ You may be running extra queries or query suites in addition to the default quer {% endif %} {% ifversion fpt or ghec %} + ## Results differ between analysis platforms If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows. @@ -256,11 +260,13 @@ On very large projects, {% data variables.product.prodname_codeql %} may run out {% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} {% ifversion fpt or ghec %} + ## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %} {% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event. A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches: + ```yaml on: push: @@ -270,7 +276,9 @@ on: branches: - main ``` + An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches: + ```yaml on: push: @@ -282,6 +290,7 @@ on: ### Analysis still failing on the default branch If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check: + - whether {% data variables.product.prodname_dependabot %} authored the commit - whether the pull request that includes the commit has been merged using `@dependabot squash and merge` diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 370ce281d8..6390bcc50e 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -49,21 +49,12 @@ redirect_from: Use the {% data variables.product.prodname_codeql_cli %} to analyze: - Dynamic languages, for example, JavaScript and Python. -- Compiled languages, for example, C/C++, C# and Java. +- Compiled languages, for example, C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java. - Codebases written in a mixture of languages. For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." {% data reusables.code-scanning.licensing-note %} -{% ifversion ghes = 3.2 %} - - -Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has had full feature parity with the {% data variables.product.prodname_codeql_runner %}. - -{% data reusables.code-scanning.deprecation-codeql-runner %} - -{% endif %} - diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 1a0e74ad50..09f10cd3f0 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -78,8 +78,8 @@ You can display the command-line help for any command using the `--help``--command` | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from `--source-root`. Not needed for Python and JavaScript/TypeScript analysis. | | `--db-cluster` | | Optional. Use in multi-language codebases to generate one database for each language specified by `--language`. | `--no-run-unnecessary-builds` | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript). -| `--source-root` | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |{% ifversion fpt or ghec or ghes > 3.2 or ghae %} -| `--codescanning-config` | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |{% endif %} +| `--source-root` | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. | +| `--codescanning-config` | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." | For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index e9d72e176b..c02304f43a 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -115,7 +115,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c ## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages -For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %} +For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %} For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. 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 fa3ad2ded3..7b93d6bb64 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 @@ -76,7 +76,7 @@ For information about access requirements for actions related to {% data variabl When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} @@ -98,7 +98,7 @@ By default, we notify people with admin permissions in the affected repositories You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Further reading - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md deleted file mode 100644 index 663dc63e1b..0000000000 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Browsing security advisories in the GitHub Advisory Database -intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.' -shortTitle: Browse Advisory Database -miniTocMaxHeadingLevel: 3 -redirect_from: - - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database - - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database - - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database - - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -type: how_to -topics: - - Security advisories - - Alerts - - Dependabot - - Vulnerabilities - - CVEs ---- - - -## About the {% data variables.product.prodname_advisory_database %} - -The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories. - -{% data reusables.repositories.tracks-vulnerabilities %} - -## About types of security advisories - -{% data reusables.advisory-database.beta-malware-advisories %} - -Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. - -{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available. - -{% ifversion GH-advisory-db-supports-malware %} - -In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency. - -{% endif %} - -### {% data variables.product.company_short %}-reviewed advisories - -{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information. - -Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry. - -- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %} -- Erlang (registry: https://hex.pm/){% endif %} -- Go (registry: https://pkg.go.dev/) -{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %} -- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %} -- Maven (registry: https://repo.maven.apache.org/maven2) -- npm (registry: https://www.npmjs.com/) -- NuGet (registry: https://www.nuget.org/) -- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %} -- pub (registry: https://pub.dev/packages/registry){% endif %} -- RubyGems (registry: https://rubygems.org/) -- Rust (registry: https://crates.io/) - -If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion. - -If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." - -### Unreviewed advisories - -Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. - -{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion. - -## About information in security advisories - -Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology. - -The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)." -- Low -- Medium/Moderate -- High -- Critical - -The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1. - -{% data reusables.repositories.github-security-lab %} - -## Accessing an advisory in the {% data variables.product.prodname_advisory_database %} - -1. Navigate to https://github.com/advisories. -2. Optionally, to filter the list, use any of the drop-down menus. - ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png) - {% tip %} - - **Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately. - - {% endtip %} -3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %} - - -{% note %} - -The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)." - -{% endnote %} - -## Editing an advisory in the {% data variables.product.prodname_advisory_database %} -You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." - -## Searching the {% data variables.product.prodname_advisory_database %} - -You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. - -{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} - -{% data reusables.search.date_gt_lt %} - -| Qualifier | Example | -| ------------- | ------------- | -| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. | -{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. | -{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. | -| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | -| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | -| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | -| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | -| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | -| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | -| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | -| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | -| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | -| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | -| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | -| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | -| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | -| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | - -## Viewing your vulnerable repositories - -For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." - -1. Navigate to https://github.com/advisories. -2. Click an advisory. -3. At the top of the advisory page, click **Dependabot alerts**. - ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) -4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). - ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) -5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name. - -{% ifversion security-advisories-ghes-ghae %} -## Accessing the local advisory database on {% data variables.location.product_location %} - -If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". - -You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. - -1. Navigate to `https://HOSTNAME/advisories`. -2. Optionally, to filter the list, use any of the drop-down menus. - ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png) - {% note %} - - **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". - - {% endnote %} -3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %} - -You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". - -### Viewing vulnerable repositories for {% data variables.location.product_location %} - -{% data reusables.repositories.enable-security-alerts %} - -In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." - -1. Navigate to `https://HOSTNAME/advisories`. -2. Click an advisory. -3. At the top of the advisory page, click **Dependabot alerts**. - ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) -4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). - ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) -5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name. - -{% endif %} - -## Further reading - -- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability) diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md deleted file mode 100644 index 688f003461..0000000000 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Editing security advisories in the GitHub Advisory Database -intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.' -redirect_from: - - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database - - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database -versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' -type: how_to -topics: - - Security advisories - - Alerts - - Dependabot - - Vulnerabilities - - CVEs -shortTitle: Edit Advisory Database ---- - -## About editing advisories in the {% data variables.product.prodname_advisory_database %} -Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted. -{% ifversion fpt or ghec %} -Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %} - -## Editing advisories in the GitHub Advisory Database - -1. Navigate to https://github.com/advisories. -1. Select the security advisory you would like to contribute to. -1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link. - - ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png) - -1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %} -1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers. - - ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %} - -1. When you finish editing the advisory, click **Submit improvements**. -1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed. - -You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). - -{% ifversion security-advisories-ghes-ghae %} -## Editing advisories from {% data variables.location.product_location %} - -If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. - -1. Navigate to `https://HOSTNAME/advisories`. -2. Select the security advisory you would like to contribute to. -3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. -![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png) -4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above. -{% endif %} 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 8bf3cc268f..4f4b684e45 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 @@ -15,8 +15,6 @@ topics: - Repositories - Dependencies children: - - /browsing-security-advisories-in-the-github-advisory-database - - /editing-security-advisories-in-the-github-advisory-database - /about-dependabot-alerts - /configuring-dependabot-alerts - /viewing-and-updating-dependabot-alerts 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 28df5d5e99..94166566bd 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 @@ -26,13 +26,13 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} 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 %} +{% ifversion fpt or ghec or ghes %} You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## About updates for vulnerable dependencies in your repository {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known security risks. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. @@ -144,16 +144,16 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect ### Fixing vulnerable dependencies 1. View the details for an alert. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](#viewing-dependabot-alerts)" (above). -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} 1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request. ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) 1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version. -{% elsif ghes < 3.3 or ghae %} +{% elsif ghae %} 1. You can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to the manifest or lock file to a secure version. {% endif %} 1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)." {% endif %} diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index 320c6a0c45..0e0910c214 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -13,7 +13,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md index 57a51497e5..126a3bffce 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md @@ -5,7 +5,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' topics: - Repositories - Dependabot @@ -16,11 +16,11 @@ shortTitle: Dependabot security updates children: - /about-dependabot-security-updates - /configuring-dependabot-security-updates -ms.openlocfilehash: 046ef28084ce31c1a4178355f5db6644b5ba0f12 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: e18b6331f762a81b82c759de5fdbc6eeed300308 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145124877' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108899' --- diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index 38b4b62926..eaefe0047a 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -11,7 +11,7 @@ miniTocMaxHeadingLevel: 3 versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: reference topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md index 0b06af8cfa..4ec0f0cac8 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md @@ -1,6 +1,6 @@ --- -title: 依存関係の更新をカスタマイズする -intro: '{% data variables.product.prodname_dependabot %} が依存関係を維持する方法をカスタマイズできます。' +title: Customizing dependency updates +intro: 'You can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.' redirect_from: - /github/administering-a-repository/customizing-dependency-updates @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to topics: - Dependabot @@ -20,40 +20,36 @@ topics: - Pull requests - Vulnerabilities shortTitle: Customize updates -ms.openlocfilehash: 6cb6db974fe880bccc76c89447dc077e0617df9a -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145124842' --- -{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -## 依存関係の更新のカスタマイズについて +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-dependabot %} -バージョン アップデートを有効にすると、*dependabot.yml* ファイルにその他のオプションを追加することで、{% data variables.product.prodname_dependabot %} を使って依存関係を維持する方法をカスタマイズできます。 たとえば、次のことが可能です。 +## About customizing dependency updates -- バージョン アップデートの pull request をオープンする曜日を指定する (`schedule.day`) -- レビュー担当者、担当者、各パッケージ マネージャーのラベルを設定する (`reviewers`、`assignees`、`labels`) -- 各マニフェスト ファイルの変更に対するバージョン管理戦略を定義する (`versioning-strategy`) -- バージョン アップデートの pull requests オープンする回数を、既定の 5 回から最大の回数に変更する (`open-pull-requests-limit`) -- バージョン アップデートの pull request をオープンして、既定のブランチの代わりに特定のブランチをターゲットにする (`target-branch`) +After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could: -構成オプションの詳しい情報については、「[dependabot.yml ファイルの構成オプション](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)」を参照してください。 +- Specify which day of the week to open pull requests for version updates: `schedule.day` +- Set reviewers, assignees, and labels for each package manager: `reviewers`, `assignees`, and `labels` +- Define a versioning strategy for changes to each manifest file: `versioning-strategy` +- Change the maximum number of open pull requests for version updates from the default of 5: `open-pull-requests-limit` +- Open pull requests for version updates to target a specific branch, instead of the default branch: `target-branch` -リポジトリ内の *dependabot.yml* ファイルを更新すると、{% data variables.product.prodname_dependabot %} によって、新しい構成で、すぐにチェックが実行されます。 数分以内に、 **[{% data variables.product.prodname_dependabot %}]** タブに依存関係の更新済みリストが表示されます。リポジトリにある依存関係が多い場合は、時間がかかることがあります。 バージョン更新に関する新しいプルリクエストが表示されることもあります。 詳しい情報については、「[バージョン更新用に設定された依存関係を一覧表示する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)」を参照してください。 +For more information about the configuration options, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." -## 設定変更によるセキュリティアップデートへの影響 +When you update the *dependabot.yml* file in your repository, {% data variables.product.prodname_dependabot %} runs an immediate check with the new configuration. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. You may also see new pull requests for version updates. For more information, see "[Listing dependencies configured for version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)." -*dependabot.yml* ファイルをカスタマイズしていると、セキュリティ アップデートに対して発行された pull request の変更点に気づくかもしれません。 これらのプルリクエストは、{% data variables.product.prodname_dependabot %} スケジュールではなく、常に依存関係のセキュリティアドバイザリによってトリガーされます。 ただし、バージョン アップデートに別のターゲット ブランチを指定していなければ、関連する構成設定は *dependabot.yml* ファイルから継承されます。 +## Impact of configuration changes on security updates -例については、[カスタム ラベルの設定](#setting-custom-labels)に関する以下のセクションを参照してください。 +If you customize the *dependabot.yml* file, you may notice some changes to the pull requests raised for security updates. These pull requests are always triggered by a security advisory for a dependency, rather than by the {% data variables.product.prodname_dependabot %} schedule. However, they inherit relevant configuration settings from the *dependabot.yml* file unless you specify a different target branch for version updates. -## スケジュールを変更する +For an example, see "[Setting custom labels](#setting-custom-labels)" below. -アップデート スケジュールを `daily` に設定すると、既定の 05:00 (UTC) に {% data variables.product.prodname_dependabot %} で新しいバージョンのチェックが行われます。 `schedule.time` を使うと、アップデートのチェックを別の時刻に指定できます (`hh:mm` 形式)。 +## Modifying scheduling -次の *dependabot.yml* ファイルの例では、npm 構成を拡張して、{% data variables.product.prodname_dependabot %} で依存関係のバージョン アップデートをチェックするタイミングを指定します。 +When you set a `daily` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions at 05:00 UTC. You can use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`). + +The example *dependabot.yml* file below expands the npm configuration to specify when {% data variables.product.prodname_dependabot %} should check for version updates to dependencies. ```yaml # dependabot.yml file with @@ -70,13 +66,13 @@ updates: time: "02:00" ``` -## レビュー担当者とアサインされた人を設定する +## Setting reviewers and assignees -デフォルトでは、{% data variables.product.prodname_dependabot %} は、レビュー担当者やアサインされた人なしでプルリクエストを発行します。 +By default, {% data variables.product.prodname_dependabot %} raises pull requests without any reviewers or assignees. -`reviewers` と `assignees` を使うと、パッケージ マネージャーに対して発行されたすべての pull request のレビュー担当者と担当者を指定できます。 Team を指定する場合は、その Team (Organization を含む) を @mentioning していたように、Team のフル ネームを使う必要があります。 +You can use `reviewers` and `assignees` to specify reviewers and assignees for all pull requests raised for a package manager. When you specify a team, you must use the full team name, as if you were @mentioning the team (including the organization). -次の *dependabot.yml* ファイルの例では、npm のバージョン アップデートとセキュリティ アップデートでオープンしたすべての pull request に 2 人のレビュー担当者と 1 人の担当者が存在するように、npm 構成を変更します。 +The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have two reviewers and one assignee. ```yaml # dependabot.yml file with @@ -88,7 +84,7 @@ updates: - package-ecosystem: "npm" directory: "/" schedule: - interval: "daily" + interval: "weekly" # Raise all npm pull requests with reviewers reviewers: - "my-org/team-name" @@ -98,17 +94,17 @@ updates: - "user-name" ``` -## カスタムラベルを設定する +## Setting custom labels {% data reusables.dependabot.default-labels %} -`labels` を使うと、既定のラベルを上書きして、パッケージ マネージャーに対して発行されたすべての pull request に代替ラベルを指定できます。 *dependabot.yml* ファイルでは新しいラベルを作成できないため、リポジトリ内に代替ラベルが既に存在している必要があります。 +You can use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. You can't create new labels in the *dependabot.yml* file, so the alternative labels must already exist in the repository. -次の *dependabot.yml* ファイルの例では、npm のバージョン アップデートとセキュリティ アップデートでオープンしたすべての pull request にカスタム ラベルが存在するように、npm 構成を変更します。 また、Docker 設定を変更して、カスタムブランチに対するバージョン更新を確認し、そのカスタムブランチに対するカスタムラベルを使用してプルリクエストを発行します。 セキュリティアップデートは常にデフォルトのブランチに対して行われるため、Docker への変更はセキュリティアップデートのプルリクエストには影響しません。 +The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch. {% note %} -**注:** 新しい `target-branch` には、更新する Dockerfile が含まれている必要があります。含まれていない場合、この変更を行うと、Docker のバージョン アップデートが無効になります。 +**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker. {% endnote %} @@ -122,7 +118,7 @@ updates: - package-ecosystem: "npm" directory: "/" schedule: - interval: "daily" + interval: "weekly" # Raise all npm pull requests with custom labels labels: - "npm dependencies" @@ -132,7 +128,7 @@ updates: - package-ecosystem: "docker" directory: "/" schedule: - interval: "daily" + interval: "weekly" # Raise pull requests for Docker version updates # against the "develop" branch. The Docker configuration # no longer affects security update pull requests. @@ -143,6 +139,6 @@ updates: - "triage-board" ``` -## その他の例 +## More examples -詳しい情報については、「[dependabot.yml ファイルの設定オプション](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)」を参照してください。 +For more examples, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md index 16fecdf5e9..2f9c0112d5 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' topics: - Repositories - Dependabot @@ -22,11 +22,11 @@ children: - /customizing-dependency-updates - /configuration-options-for-the-dependabot.yml-file shortTitle: Dependabot version updates -ms.openlocfilehash: 7eec75884da9fed388c7f882fe870d993606cb00 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 7d926dd11d8d97511a66109273e30aa018f2707a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145124841' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109805' --- diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md index 4d234695d1..e44e45c3e1 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md @@ -1,6 +1,6 @@ --- -title: バージョン更新用に設定された依存関係を一覧表示する -intro: '{% data variables.product.prodname_dependabot %} が更新を監視している依存関係を表示できます。' +title: Listing dependencies configured for version updates +intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.' redirect_from: - /github/administering-a-repository/listing-dependencies-configured-for-version-updates - /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to topics: - Repositories @@ -16,28 +16,27 @@ topics: - Version updates - Dependencies shortTitle: List configured dependencies -ms.openlocfilehash: 8028c10c39d4b045206954fc38ed805b5432e553 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145124836' --- -{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -## {% data variables.product.prodname_dependabot %} によって監視されている依存関係を表示する +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.enterprise-enable-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)」を参照してください。 +## Viewing dependencies monitored by {% data variables.product.prodname_dependabot %} -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} {% data reusables.dependabot.click-dependabot-tab %} -1. 必要に応じて、パッケージ マネージャーで監視されているファイルを表示するには、関連する {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 - ![監視対象の依存関係ファイル](/assets/images/help/dependabot/monitored-dependency-files.png) +After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." -依存関係が見つからない場合は、ログファイルでエラーを確認します。 パッケージマネージャーが見つからない場合は、設定ファイルを確認してください。 +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.accessing-repository-graphs %} +{% data reusables.repositories.click-dependency-graph %} +{% data reusables.dependabot.click-dependabot-tab %} +1. Optionally, to view the files monitored for a package manager, click the associated {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + ![Monitored dependency files](/assets/images/help/dependabot/monitored-dependency-files.png) -## Viewing {% data variables.product.prodname_dependabot %} のログファイルを表示する +If any dependencies are missing, check the log files for errors. If any package managers are missing, review the configuration file. -1. **[{% data variables.product.prodname_dependabot %}]** タブで、 **[最後のチェックは *時間* 前]** をクリックして、{% data variables.product.prodname_dependabot %} で最後のバージョン更新チェック時に生成されたログファイルを表示します。 - ![[ログ ファイルの表示]](/assets/images/help/dependabot/last-checked-link.png) -2. 必要に応じて、バージョン チェックを再実行するには、 **[更新プログラムをチェックする]** をクリックします。 - ![更新プログラムをチェックする](/assets/images/help/dependabot/check-for-updates.png) +## Viewing {% data variables.product.prodname_dependabot %} log files + +1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. + ![View log file](/assets/images/help/dependabot/last-checked-link.png) +2. Optionally, to rerun the version check, click **Check for updates**. + ![Check for updates](/assets/images/help/dependabot/check-for-updates.png) diff --git a/translations/ja-JP/content/code-security/dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/index.md index c349d32515..757cd057ed 100644 --- a/translations/ja-JP/content/code-security/dependabot/index.md +++ b/translations/ja-JP/content/code-security/dependabot/index.md @@ -1,7 +1,7 @@ --- -title: Dependabot を使用してサプライ チェーンを安全に保つ +title: Keeping your supply chain secure with Dependabot shortTitle: Dependabot -intro: '{% data variables.product.prodname_dependabot %} を使って、プロジェクトで使用される依存関係の脆弱性を監視し{% ifversion fpt or ghec or ghes > 3.2 %}、依存関係を最新の状態に保ちます{% endif %}。' +intro: 'Monitor vulnerabilities in dependencies used in your project{% ifversion fpt or ghec or ghes %} and keep your dependencies up-to-date{% endif %} with {% data variables.product.prodname_dependabot %}.' allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -19,11 +19,5 @@ children: - /dependabot-security-updates - /dependabot-version-updates - /working-with-dependabot -ms.openlocfilehash: 82b385ab7177adfe568344c0dc04357ffafeb0b3 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: '145124835' --- diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md index 4d727384fd..05fcb40b26 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md @@ -6,7 +6,7 @@ miniTocMaxHeadingLevel: 3 versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' ghae: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md index 75d9b73043..8216cae4a2 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md @@ -5,7 +5,7 @@ intro: '{% data variables.product.prodname_dependabot %} で発生した pull re versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' topics: - Repositories - Dependabot @@ -20,11 +20,11 @@ children: - /managing-encrypted-secrets-for-dependabot - /troubleshooting-the-detection-of-vulnerable-dependencies - /troubleshooting-dependabot-errors -ms.openlocfilehash: ae4f4cd7f4f748487420c2804eae67d561455099 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: efab6caf0c9384c9e72cc5ed1fe64bd500cede45 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145125910' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108959' --- diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md index 2185172d64..d6ffb64685 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md @@ -1,6 +1,6 @@ --- -title: Dependabot でアクションを最新に保つ -intro: '{% data variables.product.prodname_dependabot %} を使用して、使用するアクションを最新バージョンに更新しておくことができます。' +title: Keeping your actions up to date with Dependabot +intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the actions you use updated to the latest versions.' redirect_from: - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot - /github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to topics: - Repositories @@ -17,38 +17,33 @@ topics: - Version updates - Actions shortTitle: Auto-update actions -ms.openlocfilehash: b7de2100ad191dbcb66f4853779e5f048ca33a84 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146027964' --- + {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -## {% data variables.product.prodname_dependabot_version_updates %} のアクションについて +## About {% data variables.product.prodname_dependabot_version_updates %} for actions -多くの場合、アクションはバグ修正と新機能で更新され、自動プロセスの信頼性、速度、安全性が向上しています。 {% data variables.product.prodname_actions %} に対して {% data variables.product.prodname_dependabot_version_updates %} を有効にすると、{% data variables.product.prodname_dependabot %} では、リポジトリの *workflow.yml* ファイル内のアクションへのリファレンスが最新の状態に保たれるようにします。 {% data variables.product.prodname_dependabot %} では、ファイル内のアクションごとに、アクションのリファレンス (通常、アクションに関連付けられているバージョン番号またはコミット ID) が最新バージョンと参照されます。 より新しいバージョンのアクションが使用可能な場合、{% data variables.product.prodname_dependabot %} によって、ワークフロー ファイル内のリファレンスを最新バージョンに更新する pull request が送信されます。 {% data variables.product.prodname_dependabot_version_updates %} について詳しくは、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 {% data variables.product.prodname_actions %} のワークフロー構成について詳しくは、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。 +Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." {% data reusables.actions.workflow-runs-dependabot-note %} -## {% data variables.product.prodname_dependabot_version_updates %} のアクションを有効化する +## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions -自分のアクションと、依存するライブラリとパッケージを維持するように {% data variables.product.prodname_dependabot_version_updates %} を構成できます。 +You can configure {% data variables.product.prodname_dependabot_version_updates %} to maintain your actions as well as the libraries and packages you depend on. -1. 他のエコシステムまたはパッケージ マネージャーで既に {% data variables.product.prodname_dependabot_version_updates %} を有効にしている場合は、既存の *dependabot.yml* ファイルを開くだけです。 それ以外の場合、リポジトリの `.github` ディレクトリに *dependabot.yml* 構成ファイルを作成します。 詳しくは、「[Dependabot のバージョン アップデートの設定](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)」をご覧ください。 -1. `"github-actions"` を `package-ecosystem` として指定して監視します。 -1. `directory` を `"/"` に設定して、`.github/workflows` でワークフロー ファイルを確認します。 -1. `schedule.interval` を設定して、新しいバージョンを確認する頻度を指定します。 -{% data reusables.dependabot.check-in-dependabot-yml %} 既存のファイルを編集した場合は、変更を保存します。 +1. If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing *dependabot.yml* file. Otherwise, create a *dependabot.yml* configuration file in the `.github` directory of your repository. For more information, see "[Configuring Dependabot version updates](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)." +1. Specify `"github-actions"` as a `package-ecosystem` to monitor. +1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`. +1. Set a `schedule.interval` to specify how often to check for new versions. +{% data reusables.dependabot.check-in-dependabot-yml %} If you have edited an existing file, save your changes. -フォークで {% data variables.product.prodname_dependabot_version_updates %} を有効化することもできます。 詳細については、「[{% data variables.product.prodname_dependabot %} バージョンの更新の構成](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)」を参照してください。 +You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)." -### {% data variables.product.prodname_actions %} の *dependabot.yml* ファイルの例 +### Example *dependabot.yml* file for {% data variables.product.prodname_actions %} -次の *dependabot.yml* ファイルの例では、{% data variables.product.prodname_actions %} のバージョン更新を設定しています。 `.github/workflows` でワークフロー ファイルを確認するために、`directory` は `"/"` に設定する必要があります。 `schedule.interval` に `"daily"` が設定されています。 このファイルがチェックインまたは更新されると、{% data variables.product.prodname_dependabot %} はアクションの新しいバージョンをチェックします。 {% data variables.product.prodname_dependabot %} では、検出した期限切れのアクションに対してバージョン更新の pull request が生成されます。 初期バージョンの更新後、{% data variables.product.prodname_dependabot %} では 1 日 1 回、期限切れのバージョンのアクションを引き続き確認します。 +The example *dependabot.yml* file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"weekly"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a week. ```yaml # Set update schedule for GitHub Actions @@ -59,14 +54,14 @@ updates: - package-ecosystem: "github-actions" directory: "/" schedule: - # Check for updates to GitHub Actions every weekday - interval: "daily" + # Check for updates to GitHub Actions every week + interval: "weekly" ``` -## {% data variables.product.prodname_dependabot_version_updates %} のアクションを設定する +## Configuring {% data variables.product.prodname_dependabot_version_updates %} for actions -アクションに対して {% data variables.product.prodname_dependabot_version_updates %} を有効にする場合は、`package-ecosystem`、`directory`、`schedule.interval` の値を指定する必要があります。 バージョン更新をさらにカスタマイズするための設定オプションのプロパティは他にもたくさんあります。 詳細については、「[dependabot.yml ファイルの構成オプション](/github/administering-a-repository/configuration-options-for-dependency-updates)」を参照してください。 +When enabling {% data variables.product.prodname_dependabot_version_updates %} for actions, you must specify values for `package-ecosystem`, `directory`, and `schedule.interval`. There are many more optional properties that you can set to further customize your version updates. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)." -## 参考資料 +## Further reading -- 「[GitHub Actions について](/actions/getting-started-with-github-actions/about-github-actions)」 +- "[About GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md index 7b75165e76..d3c87a52e1 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md index 6e58e7a836..2c35207247 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md @@ -11,7 +11,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' type: how_to 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 7974d9e6ee..725554270a 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 @@ -34,13 +34,13 @@ topics: * {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %} * The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)." * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. 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)." +* {% ifversion fpt or ghec or ghes %}{% 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 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 advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.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-insecure-dependencies)." ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles? -{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are: +{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are: * Direct dependencies explicitly declared in a manifest or lockfile * Transitive dependencies declared in a lockfile{% endif %} @@ -84,7 +84,7 @@ The {% data variables.product.prodname_dependabot_alerts %} count in {% data var **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Can Dependabot ignore specific dependencies? You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)." @@ -95,5 +95,5 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" - "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes %} - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md index 0894245232..9c14fe91d4 100644 --- a/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md +++ b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md @@ -1,6 +1,6 @@ --- -title: リポジトリへのセキュリティ ポリシーの追加 -intro: セキュリティポリシーをリポジトリに追加することによって、プロジェクト内のセキュリティ脆弱性を報告する方法の手順を示すことができます。 +title: Adding a security policy to your repository +intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository. redirect_from: - /articles/adding-a-security-policy-to-your-repository - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository @@ -17,47 +17,49 @@ topics: - Repositories - Health shortTitle: Add a security policy -ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145087630' --- -## セキュリティポリシーについて -プロジェクトのセキュリティ脆弱性を報告する手順をユーザーに示すには、{% ifversion fpt or ghes or ghec %} _SECURITY.md_ ファイルを、リポジトリのルート、`docs` フォルダー、または `.github` フォルダーに追加します。{% else %}_SECURITY.md_ ファイルを、リポジトリのルート、または `docs` フォルダーに追加します。{% endif %} だれかがリポジトリに Issue を作成すると、プロジェクトのセキュリティ ポリシーへのリンクが表示されます。 +## About security policies + +To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy. {% ifversion not ghae %} -所属する Organization または個人アカウントにデフォルトのセキュリティ ポリシーを作成できます。 詳細については、「[既定のコミュニティ正常性ファイルの作成](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 +You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} {% tip %} -**ヒント:** セキュリティ ポリシーを検索しやすくするには、README ファイルなど、リポジトリ内の他の場所から _SECURITY.md_ にリンクします。 詳細については、「[README について](/articles/about-readmes)」を参照してください。 +**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)." {% endtip %} -{% ifversion fpt or ghec %} プロジェクトのセキュリティの脆弱性が報告された後は、{% data variables.product.prodname_security_advisories %} を使用して、脆弱性に関する情報を開示、修正、公開できます。 {% data variables.product.prodname_dotcom %} での脆弱性の報告と開示のプロセスに関する詳細については、「[セキュリティ脆弱性の調整された開示について](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)」を参照してください。 {% data variables.product.prodname_security_advisories %} の詳細については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 +{% ifversion fpt or ghec %} +After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %} +{% data reusables.repositories.github-security-lab %} +{% endif %} +{% ifversion ghes or ghae %} -セキュリティの報告の指示を明確に利用できる要することで、ユーザがあなたの好むコミュニケーションチャンネルを使ってリポジトリで見つけたセキュリティ脆弱性を報告することを容易にできます。 +By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel. {% endif %} -## リポジトリへのセキュリティ ポリシーの追加 +## Adding a security policy to your repository -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. 左側のサイドバーで、 **[セキュリティ ポリシー]** をクリックします。 - ![[セキュリティ ポリシー] タブ](/assets/images/help/security/security-policy-tab.png) -4. **[Start setup] (セットアップの開始)** をクリックします。 - ![[セットアップの開始] ボタン](/assets/images/help/security/start-setup-security-policy-button.png) -5. 新しい _SECURITY.md_ ファイルに、サポートされているバージョンのプロジェクトに関する情報と、脆弱性を報告する方法を追加します。 -{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +3. In the left sidebar, click **Security policy**. + ![Security policy tab](/assets/images/help/security/security-policy-tab.png) +4. Click **Start setup**. + ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png) +5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose-commit-email %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} -## 参考資料 +## Further reading -- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not ghae %} -- 「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」{% endif %}{% ifversion fpt or ghec %} +- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %} +- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %} - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %} 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 5e7ed85861..081272149c 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 @@ -28,10 +28,10 @@ Make it easy for your users to confidentially report security vulnerabilities th {% ifversion fpt or ghec %} ### Security advisories -Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." +Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ### {% data variables.product.prodname_dependabot_alerts %} and security updates @@ -39,7 +39,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 %} +{% ifversion ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -47,7 +47,7 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/ View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ### {% data variables.product.prodname_dependabot %} version updates 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)." 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 e00a81e612..63cff8ac9b 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 @@ -56,7 +56,7 @@ Dependency review is an {% data variables.product.prodname_advanced_security %} {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). {% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Managing {% data variables.product.prodname_dependabot_security_updates %} For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization. @@ -123,9 +123,9 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% 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)." +{% 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 repository 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 ghes 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 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 %} 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 919f1b2fdd..3e84f7c163 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 @@ -86,8 +86,7 @@ Dependency review is a {% data variables.product.prodname_GH_advanced_security % {% endif %} - -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Managing {% data variables.product.prodname_dependabot_security_updates %} @@ -132,7 +131,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% 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)." +{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/ja-JP/content/code-security/index.md b/translations/ja-JP/content/code-security/index.md index 7dc0f1030b..e9d02c2953 100644 --- a/translations/ja-JP/content/code-security/index.md +++ b/translations/ja-JP/content/code-security/index.md @@ -1,7 +1,7 @@ --- -title: コードセキュリティ +title: Code security shortTitle: Code security -intro: 'コードベースからシークレットや脆弱性を排除{% ifversion not ghae %}し、ソフトウェアサプライチェーンを管理{% endif %}する機能で、{% data variables.product.prodname_dotcom %}ワークフローにセキュリティを組み込んでください。' +intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.' introLinks: overview: /code-security/getting-started/github-security-features featuredLinks: @@ -53,16 +53,10 @@ children: - /adopting-github-advanced-security-at-scale - /secret-scanning - /code-scanning - - /repository-security-advisories + - /security-advisories - /supply-chain-security - /dependabot - /security-overview - /guides -ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147145240' --- diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md deleted file mode 100644 index 722f0088cd..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: セキュリティ脆弱性の調整された開示について -intro: 脆弱性の開示は、セキュリティの報告者とリポジトリメンテナの調整された取り組みです。 -redirect_from: - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' - ghec: '*' -type: overview -topics: - - Security advisories - - Vulnerabilities -shortTitle: Coordinated disclosure -ms.openlocfilehash: a5d4445525b46536cbfd3301cccb78140589de22 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145087581' ---- -## 業界における脆弱性の開示について - -{% data reusables.security-advisory.disclosing-vulnerabilities %} - -脆弱性の初期の報告は非公開で行われ、完全な詳細はメンテナが問題を認め、理想的には対策もしくはパッチが利用可能になり、場合によってはパッチがインストールできるようさらに時間をおいてから公開されます。 詳細については、OWASP Cheat Sheet Series (OWASP チート シート シリーズ) の Web サイトの [「OWASP Cheat Sheet Series」 (OWASP チート シート シリーズ) の「Vulnerability Disclosure」 (脆弱性の開示) ](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)を参照してください。 - -### 脆弱性報告者のためのベストプラクティス - -脆弱性をメンテナに非公開で報告するのは良いやり方です。 可能なら、脆弱性報告者は以下を避けることをおすすめします。 -- メンテナに対策の機会を与えることなく脆弱性を公開してしまうこと。 -- メンテナをバイパスしてしまうこと。 -- コードの修正バージョンが利用可能になる前に脆弱性を公開してしまうこと。 -- パブリックなバウンティプログラムが存在しない場合に、問題の報告に補償がなされると期待すること。 - -メンテナに連絡を取ろうとしてレスポンスがなかったり、連絡は取れたものの公開をあまりに長く待つよう頼まれたなら、一定期間後に脆弱性報告者が脆弱性を公開することは許容できます。 - -脆弱性の報告者は、報告のプロセスの一部として、開示ポリシーの条件を明確に述べることをおすすめします。 脆弱性報告者が厳密なポリシーに従っていないばあいでも、意図的な脆弱性の開示の時期についてメンテナが明確な期待を持てるようにするのは良い考えです。 開示ポリシーの例については、GitHub Security Lab の Web サイトの「[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)」 (Security Lab の開示ポリシー) を参照してください。 - -### メンテナのためのベストプラクティス - -メンテナは、脆弱性の報告をいつどのように受けたいかを明確に示しておくのが良いでしょう。 この情報が明確に利用できない場合、脆弱性報告者はどのように連絡をすればいいか分からず、gitのコミット履歴から開発者のメールアドレスを取り出して適切なセキュリティに関する連絡先を見つけようとするかもしれません。 これは、不和、報告の喪失、未解決の報告の公開につながるかもしれません。 - -メンテナは、適時に脆弱性を開示すべきです。 リポジトリにセキュリティ脆弱性があるなら、以下のようにすることをおすすめします。 -- 脆弱性は、レスポンスにおいても開示においても単純なバグとしてよりもセキュリティの問題として対処してください。 たとえば、リリースノートではその問題をセキュリティ脆弱性として明示的に言及する必要があります。 -- 脆弱性報告を受け取ったことは、たとえすぐに調査するためのリソースがない場合でも、できるだけ早く認めてください。 これはあなたが迅速に対応して行動するというメッセージを送ることになり、あなたと脆弱性報告者との間のそれ以外のやりとりに肯定的なトーンが設定されます。 -- 報告のインパクトと正確性を検証する際には、脆弱性報告者にも関わってもらってください。 おそらく脆弱性の報告者は、すでにその脆弱性を様々なシナリオの中で考慮するのに時間をかけているでしょう。その中には、あなたが自分では考えていなかったものがあるかもしれません。 -- 脆弱性の報告者が提供してくれた懸念点とアドバイスを慎重に考慮に入れて、適切と思われる方法で問題に対処してください。 脆弱性の報告者は、しばしば特定のコーナーケースや対処のバイパスに関する知識を持っており、それらはセキュリティ研究のバックグラウンドなしでは簡単に見逃してしまうものです。 -- 発見されたことを評価する際には、常に脆弱性の報告者に感謝を示してください。 -- できるかぎり早い修正の公開を目指してください。 -- 脆弱性を開示する際には、広汎なエコシステムがその問題と対策を認識するようにしてください。 認識されたセキュリティの問題がプロジェクトの現在の開発ブランチで修正されながら、そのコミットあるいはそれ以降のリリースがセキュリティ修正あるいはリリースとして明示的に示されていない場合が珍しくありません。 これによって、下流の利用者に問題が生じることがあります。 - -セキュリティ脆弱性の詳細を開会しても、メンテナが悪く見えることはありません。 セキュリティ脆弱性はソフトウェアのあらゆるところに存在し、ユーザはコード中のセキュリティ脆弱性を開示するための明確な確立されたプロセスを持つメンテナを信頼します。 - -## {% data variables.product.prodname_dotcom %}上のプロジェクトの脆弱性の報告と開示について - -{% data variables.product.prodname_dotcom_the_website %}上のプロジェクトの脆弱性の報告と開示のプロセスは以下のようになります。 - - あなたが脆弱性の報告したいと考えている人（たとえばセキュリティ研究者）なら、まず関連するリポジトリにセキュリティポリシーがあるかをチェックしてください。 詳細については、「[セキュリティ ポリシーについて](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)」を参照してください。 セキュリティポリシーがあるなら、そのリポジトリのセキュリティチームに連絡する前に、それに従ってプロセスを理解してください。 - - セキュリティポリシーがないなら、メンテナへの非公開のコミュニケーション方法を確立するための最も効率的な方法は、望ましいセキュリティの連絡先を尋ねるIssueを作成することです。 そのIssueはすぐに公に見ることができるようになるので、そこにはバグに関する情報は含めないようにするべきであることには注意してください。 コミュニケーションが確立できたら、将来的に利用できるよう、セキュリティポリシーを規定してもらうメンテナに提案できます。 - -{% note %} - -**注**: _npm のみ_ - npm パッケージのマルウェアに関する報告を受けた場合は、お客様個人にご連絡させていただきます。 あなたが適時問題に対応しない場合、私たちはその問題を開示します。 詳細については、npm Docs の Web サイトの「[eporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)」 (npm パッケージ内のマルウェアの報告) を参照してください。 - -{% endnote %} - - {% data variables.product.prodname_dotcom_the_website %}でセキュリティ脆弱性を発見したら、私たちの調整された開示プロセスを通じてその脆弱性を報告してください。 詳細については、「[{% data variables.product.prodname_dotcom %} セキュリティ アドバイザリの概要](https://bounty.github.com/)」を参照してください。 - - あなたがメンテナなら、リポジトリのセキュリティポリシーを設定するか、たとえばプロジェクトのREADMEファイルでセキュリティの報告方法を明確にしておくことによって、このパイプラインの開始時点からプロセスの所有権を取ることができます。 セキュリティ ポリシーの追加の詳細については、「[セキュリティ ポリシーについて](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)」を参照してください。 セキュリティポリシーがない場合、セキュリティの報告者はおそらくあなたにメールするか、非公開であなたに連絡しようとするでしょう。 あるいは、誰かがセキュリティの問題の詳細を含む（パブリックな）Issueをオープンするかもしれません。 - - メンテナとしてコード中の脆弱性を開示するために、まずは{% data variables.product.prodname_dotcom %}でパッケージのリポジトリにドラフトのセキュリティアドバイザリを作成します。 {% data reusables.security-advisory.security-advisory-overview %} 詳細については、「[リポジトリの {% data variables.product.prodname_security_advisories %}について](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)」を参照してください。 - - - 開始するには、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md deleted file mode 100644 index 5d7e7d4087..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: リポジトリの GitHub セキュリティ アドバイザリについて -intro: '{% data variables.product.prodname_security_advisories %} を使用して、リポジトリにおけるセキュリティの脆弱性に関する情報を非公開で議論、修正、公開できます。' -redirect_from: - - /articles/about-maintainer-security-advisories - - /github/managing-security-vulnerabilities/about-maintainer-security-advisories - - /github/managing-security-vulnerabilities/about-github-security-advisories - - /code-security/security-advisories/about-github-security-advisories -versions: - fpt: '*' - ghec: '*' -type: overview -topics: - - Security advisories - - Vulnerabilities - - CVEs -shortTitle: Repository security advisories -ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145087576' ---- -{% data reusables.repositories.security-advisory-admin-permissions %} - -{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} - -## {% data variables.product.prodname_security_advisories %} について - -{% data reusables.security-advisory.disclosing-vulnerabilities %} 詳細については、「[セキュリティ脆弱性の調整された開示について](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)」を参照してください。 - -{% data reusables.security-advisory.security-advisory-overview %} - -{% data variables.product.prodname_security_advisories %} では、次のことができます。 - -1. セキュリティアドバイザリのドラフトを作成し、そのドラフトを用いて、プロジェクトに対する脆弱性の影響について非公開で議論します。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。 -2. 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 -3. パッチがリリースされたら、脆弱性のコミュニティに警告するため、セキュリティアドバイザリを公開してください。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。 - -{% data reusables.repositories.security-advisories-republishing %} - -セキュリティアドバイザリに貢献した個人にクレジットを付与することができます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)」を参照してください。 - -{% data reusables.repositories.security-guidelines %} - -セキュリティアドバイザリをリポジトリ中で作成した場合、そのセキュリティアドバイザリはリポジトリに残ります。 依存関係グラフによってサポートされる任意のエコシステムのセキュリティ アドバイザリを、[github.com/advisories](https://github.com/advisories) の {% data variables.product.prodname_advisory_database %} に公開しています。 {% data variables.product.prodname_advisory_database %} に公開されているアドバイザリに、だれでも変更を送信することができます。 詳細については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。 - -特にnpmに対するものであるセキュリティアドバイザリについては、npmセキュリティアドバイザリにも公開します。 詳細については、[npmjs.com/advisories](https://www.npmjs.com/advisories) を確認してください。 - -{% data reusables.repositories.github-security-lab %} - -## CVE 識別番号 - -{% data variables.product.prodname_security_advisories %} は、共通脆弱性識別子(CVE) リストに基づいています。 {% data variables.product.prodname_dotcom %}上のセキュリティアドバイザリフォームは、CVEの記述フォーマットにマッチする標準化されたフォームです。 - -{% data variables.product.prodname_dotcom %} は CVE Numbering Authority (CNA) であり、CVE 識別番号を割り当てる権限があります。 詳細については、CVE の Web サイトで、「[About CVE](https://www.cve.org/About/Overview)」 (CVE の概要)、および「[CVE Numbering Authorities](https://www.cve.org/ProgramOrganization/CNAs)」 (CVE の番号付け機関) を参照してください。 - -{% data variables.product.prodname_dotcom %} でパブリックリポジトリのセキュリティアドバイザリを作成する場合、セキュリティの脆弱性に対する既存の CVE 識別番号を提供するオプションがあります。 {% data reusables.repositories.request-security-advisory-cve-id %} - -セキュリティアドバイザリを公開し、{% data variables.product.prodname_dotcom %} が CVE 識別番号を脆弱性に割り当てたら、{% data variables.product.prodname_dotcom %} は CVE を MITER データベースに公開します。 -詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。 - -## 公開されたセキュリティアドバイザリの {% data variables.product.prodname_dependabot_alerts %} - -{% data reusables.repositories.github-reviews-security-advisories %} diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md deleted file mode 100644 index c0a2741b68..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリへのコラボレータの追加 -intro: あなたと協力するセキュリティアドバイザリとして、ユーザや Team を追加できます。 -redirect_from: - - /articles/adding-a-collaborator-to-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory - - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities - - Collaboration -shortTitle: Add collaborators -ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147879136' ---- -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加できます。 - -{% data reusables.security-advisory.repository-level-advisory-note %} - -## セキュリティアドバイザリにコラボレータを追加する - -コラボレータは、セキュリティアドバイザリへの書き込み権限を持ちます。 詳細については、「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」を参照してください。 - -{% note %} - -{% data reusables.repositories.security-advisory-collaborators-public-repositories %} セキュリティ アドバイザリのコラボレーターの削除に関する詳細については、「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」を参照してください。 - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、コラボレータとして追加するセキュリティアドバイザリをクリックします。 -5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリとして追加するユーザまたは Team の名前を入力します。 - ![ユーザ名または Team 名を入力するフィールド](/assets/images/help/security/add-collaborator-field.png) -6. **[追加]** をクリックします。 - ![[追加] ボタン](/assets/images/help/security/security-advisory-add-collaborator-button.png) - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 -- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」 -- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」。 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md deleted file mode 100644 index 04f3744848..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: 一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする -intro: リポジトリにおけるセキュリティ脆弱性の修正について非公開でコラボレートするため、一時的なプライベートフォークを作成できます。 -redirect_from: - - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities - - Collaboration - - Forks -shortTitle: Temporary private forks -ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d -ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147878543' ---- -{% data reusables.security-advisory.repository-level-advisory-note %} - -## 前提条件 - -一時的なプライベートフォークでコラボレートする前に、ドラフトのセキュリティアドバイザリを作成する必要があります。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。 - -## 一時的なプライベートフォークを作成する - -セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークを作成できます。 - -脆弱性についての情報を保護するため、CI を含むインテグレーションは、一時的なプライベートフォークにアクセスできません。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、一時的なプライベートフォークを作成するセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. **[新しい一時的なプライベートフォーク]** をクリックします。 - ![[新しい一時的なプライベートフォーク] ボタン](/assets/images/help/security/new-temporary-private-fork-button.png) - -## 一時的なプライベートフォークにコラボレータを追加する - -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加でき、セキュリティアドバイザリのコラボレータは一時的なプライベートフォークにアクセスできます。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。 - -## 一時的なプライベートフォークに変更を追加する - -セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークに変更を追加できます。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、変更を追加するセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. {% data variables.product.product_name %} またはローカルに変更を追加します: - - {% data variables.product.product_name %} に変更を追加するには、[このアドバイザリに変更を追加する] で、 **[一時的なプライベート フォーク]** をクリックします。 そして、新しいブランチを作成し、ファイルを編集します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository)」および「[ファイルの編集](/repositories/working-with-files/managing-files/editing-files)」を参照してください。 - - ローカルで変更を追加するには、「クローンを作成して新しいブランチを作成する」および「変更を加えてからプッシュする」の手順に従ってください。 - ![[このアドバイザリに変更を追加する] ボックス](/assets/images/help/security/add-changes-to-this-advisory-box.png) - -## 一時的なプライベートフォークからプルリクエストを作成する - -セキュリティアドバイザリに対する書き込み権限があるユーザなら誰でも、一時的なプライベートフォークからプルリクエストを作成できます。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、セキュリティアドバイザリを作成するプルリクエストをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. ブランチ名の右側にある **[比較と pull request]** をクリックします。 - ![[比較と pull request] ボタン](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %} - -{% data reusables.repositories.merge-all-pulls-together %} 詳細については、「[変更をセキュリティ アドバイザリにマージする](#merging-changes-in-a-security-advisory)」を参照してください。 - -## 変更をセキュリティアドバイザリにマージする - -セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリに変更をマージできます。 - -{% data reusables.repositories.merge-all-pulls-together %} - -セキュリティアドバイザリの変更をマージするには、一時的なプライベートフォークにあるすべてのオープンされたプルリクエストがマージできる必要があります。 マージコンフリクトは許容されません。また、ブランチ保護の要件を満たす必要があります。 脆弱性についての情報を保護するため、一時的なプライベートフォークにあるプルリクエストに対しては、ステータスチェックは実行されません。 詳細については、「[保護されたブランチについて](/articles/about-protected-branches)」を参照してください。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、変更をマージするセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. 一時的なプライベート フォーク内にあるすべてのオープンされた pull request をマージするには、 **[pull requests をマージする]** をクリックします。 - ![[pull request のマージ] ボタン](/assets/images/help/security/merge-pull-requests-button.png) - -セキュリティアドバイザリの変更をマージした後は、プロジェクトの以前のバージョンにある脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。 - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 -- 「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md deleted file mode 100644 index 187072360a..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリの作成 -intro: セキュリティアドバイザリのドラフトを作成して、オープンソースプロジェクトのセキュリティ脆弱性について非公開で議論して修正することができます。 -redirect_from: - - /articles/creating-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/creating-a-security-advisory - - /code-security/security-advisories/creating-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities -shortTitle: Create repository advisories -ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145119397' ---- -リポジトリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリを作成できます。 - -{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} - -## セキュリティ アドバイザリの作成 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. **[セキュリティ アドバイザリの新しいドラフト]** をクリックします。 - ![[アドバイザリのドラフトを開く] ボタン](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png) -5. セキュリティアドバイザリのタイトルを入力します。 -{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %} -11. **[セキュリティ アドバイザリのドラフトの作成]** をクリックします。 - ![[セキュリティ アドバイザリの作成] ボタン](/assets/images/help/security/security-advisory-create-security-advisory-button.png) - -## 次の手順 - -- セキュリティアドバイザリのドラフトにコメントして、チームと脆弱性について話し合います。 -- セキュリティアドバイザリにコラボレータを追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。 -- 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 詳細については、「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください。 -- セキュリティアドバイザリへの貢献に対してクレジットを受け取る必要がある個人を追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)」を参照してください。 -- コミュニティにセキュリティの脆弱性を知らせるため、セキュリティアドバイザリを公開します。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md deleted file mode 100644 index faa02ee4fd..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリの編集 -intro: 詳細を更新したりエラーを修正したりする必要がある場合は、リポジトリ セキュリティ アドバイザリのメタデータと説明を編集できます。 -redirect_from: - - /github/managing-security-vulnerabilities/editing-a-security-advisory - - /code-security/security-advisories/editing-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities -shortTitle: Edit repository advisories -ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145119389' ---- -リポジトリ セキュリティ アドバイザリの管理者権限を持つユーザーは、セキュリティ アドバイザリを編集することができます。 - -{% data reusables.security-advisory.repository-level-advisory-note %} - -## セキュリティアドバイザリのクレジットについて - -セキュリティの脆弱性の発見、報告、修正を支援してくれたユーザにクレジットを付与することができます。 ユーザにクレジットを付与すると、相手はそのクレジットを受け入れるか拒否するかを選択できます。 - -相手がクレジットを受け入れると、そのユーザのユーザ名がセキュリティアドバイザリの [Credits] セクションに表示されます。 リポジトリへの読み取りアクセスを持つユーザは、アドバイザリとそれに対するクレジットを受け入れたユーザを確認することができます。 - -セキュリティアドバイザリに自分がクレジットされるべきだと信じるなら、そのアドバイザリを作成した人物に連絡し、そのアドバイザリを編集してあなたへのクレジットを含めてもらうように頼んでください。 あなたをクレジットできるのはアドバイザリの作者だけなので、セキュリティアドバイザリでのクレジットについてはGitHub Supportに問い合わせないでください。 - -## セキュリティアドバイザリを編集する - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、編集するセキュリティアドバイザリをクリックします。 -5. セキュリティ アドバイザリの詳細の右上隅で、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 - ![セキュリティ アドバイザリの [編集] ボタン](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %} -11. 必要に応じて、セキュリティアドバイザリの [Credits] を編集します。 - ![セキュリティ アドバイザリのクレジット](/assets/images/help/security/security-advisory-credits.png) -12. **[セキュリティ アドバイザリの更新]** をクリックします。 - ![[セキュリティ アドバイザリの更新] ボタン](/assets/images/help/security/update-advisory-button.png) -13. [Credits] セクションに記載されているユーザは、クレジットを受け入れるように勧めるメールまたは Web 通知を受信します。 受け入れた場合、セキュリティアドバイザリが公開されると、そのユーザ名が公開されます。 - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/index.md b/translations/ja-JP/content/code-security/repository-security-advisories/index.md deleted file mode 100644 index 04b515a465..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/index.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: プロジェクトの脆弱性に関するリポジトリ セキュリティ アドバイザリの管理 -shortTitle: Repository security advisories -intro: リポジトリ セキュリティ アドバイザリを利用したリポジトリ内のセキュリティ脆弱性に関する話し合い、修正、開示を行います。 -redirect_from: - - /articles/managing-security-vulnerabilities-in-your-project - - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project - - /code-security/security-advisories -versions: - fpt: '*' - ghec: '*' -topics: - - Security advisories - - Vulnerabilities - - Repositories - - CVEs -children: - - /about-coordinated-disclosure-of-security-vulnerabilities - - /about-github-security-advisories-for-repositories - - /permission-levels-for-repository-security-advisories - - /creating-a-repository-security-advisory - - /adding-a-collaborator-to-a-repository-security-advisory - - /removing-a-collaborator-from-a-repository-security-advisory - - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability - - /publishing-a-repository-security-advisory - - /editing-a-repository-security-advisory - - /withdrawing-a-repository-security-advisory - - /best-practices-for-writing-repository-security-advisories -ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145119382' ---- - diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md deleted file mode 100644 index c2431ee59d..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリの権限レベル -intro: リポジトリ セキュリティ アドバイザリで実行できるアクションは、セキュリティ アドバイザリに対する管理者や書き込みの権限を持っているかどうかによって変わります。 -redirect_from: - - /articles/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories - - /code-security/security-advisories/permission-levels-for-security-advisories -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Security advisories - - Vulnerabilities - - Permissions -shortTitle: Permission levels -ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145119390' ---- -この記事は、リポジトリ レベルのセキュリティ アドバイザリのみを対象としています。 あらゆるユーザーは、[github.com/advisories](https://github.com/advisories) で、{% data variables.product.prodname_advisory_database %} のグローバル セキュリティ アドバイザリに貢献できます。 グローバル アドバイザリを編集しても、リポジトリでのアドバイザリの表示方法が変更されたり、影響を受けたりすることはありません。 詳細については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。 - -## アクセス許可の概要 - -{% data reusables.repositories.security-advisory-admin-permissions %} セキュリティ アドバイザリへのコラボレーターの追加に関する詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。 - -アクション | Write 権限 | 管理者のアクセス許可 | ------- | ----------------- | ----------------- | -セキュリティアドバイザリのドラフトを表示する | X | X | -コラボレーターをセキュリティ アドバイザリに追加する (「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください) | | X | -セキュリティアドバイザリでコメントを編集および削除する | X | X | -セキュリティ アドバイザリに一時的なプライベート フォークを作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X | -セキュリティ アドバイザリの一時的なプライベート フォークに変更を追加する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X | -一時的なプライベート フォークに pull request を作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X | -セキュリティ アドバイザリに変更をマージする (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X | -メタデータをセキュリティ アドバイザリに追加して編集する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | X | X | -セキュリティ アドバイザリのクレジットを追加および削除する (「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください) | X | X | -セキュリティアドバイザリのドラフトをクローズする | | X | -セキュリティ アドバイザリを公開する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | | X | - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」 -- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」 -- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」 -- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md deleted file mode 100644 index 786ddf7660..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリの公開 -intro: プロジェクト内のセキュリティ脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 -redirect_from: - - /articles/publishing-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/publishing-a-security-advisory - - /code-security/security-advisories/publishing-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities - - CVEs - - Repositories -shortTitle: Publish repository advisories -ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145119381' ---- - - -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリを公開できます。 - -{% data reusables.security-advisory.repository-level-advisory-note %} - -## 前提条件 - -セキュリティアドバイザリを公開したり、CVE の ID 番号をリクエストしたりする前に、セキュリティアドバイザリのドラフトを作成し、セキュリティの脆弱性の影響を受けるプロジェクトのバージョンに関する情報を提供する必要があります。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。 - -セキュリティアドバイザリを作成したが、セキュリティの脆弱性が影響を与えるプロジェクトのバージョンに関する詳細をまだ入力していない場合は、セキュリティアドバイザリを編集できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください。 - -## セキュリティアドバイザリの公開について - -セキュリティアドバイザリを公開すると、セキュリティアドバイザリが指定するセキュリティの脆弱性についてコミュニティに通知します。 セキュリティアドバイザリを公開すると、コミュニティがパッケージの依存関係を更新し、セキュリティの脆弱性の影響を調査しやすくなります。 - -{% data reusables.repositories.security-advisories-republishing %} - -セキュリティアドバイザリを公開する前に、一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートできます。 詳細については、「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください。 - -{% warning %} - -**警告**: 可能な限り、アドバイザリを公開する前に、セキュリティ アドバイザリに修正バージョンを追加する必要があります。 そうしない場合、アドバイザリは修正バージョンなしで公開され、{% data variables.product.prodname_dependabot %} は、更新する安全なバージョンを提供することなく、問題についてユーザに警告します。 - -このような状況では、次のステップを行うことをお勧めします。 - -- 修正バージョンが利用可能な場合、可能であれば、修正の準備ができたときに問題を開示するのを待ちます。 -- 修正バージョンが開発中でまだ利用できない場合は、アドバイザリにその旨を記載し、公開後にアドバイザリを編集します。 -- 問題を修正する予定がない場合は、ユーザが修正時期を問い合わせることがないよう、アドバイザリに明示します。 この場合、ユーザが問題を軽減するときに使えるステップを含めると便利です。 - -{% endwarning %} - -パブリックリポジトリからドラフトアドバイザリを公開すると、すべてのユーザが次のことを確認できます。 - -- アドバイザリデータの現在のバージョン。 -- クレジットされたユーザが受け入れたアドバイザリクレジット。 - -{% note %} - -**注**: 一般ユーザーは、アドバイザリの編集履歴にアクセスすることはできず、公開されたバージョンのみを見ることができます。 - -{% endnote %} - -セキュリティアドバイザリの URL は、セキュリティアドバイザリの公開後も公開前と同じままです。 リポジトリへの読み取りアクセス権を持つユーザは、セキュリティアドバイザリを閲覧することができます。 セキュリティアドバイザリのコラボレータは、管理者権限を持つユーザがコラボレータをセキュリティアドバイザリから削除しない限り、セキュリティアドバイザリでコメントストリーム全体を含む過去の会話を引き続き表示できます。 - -公開したセキュリティアドバイザリの情報をアップデートまたは修正する必要がある場合は、セキュリティアドバイザリを編集できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください。 - -## セキュリティアドバイザリを公開する - -セキュリティアドバイザリを公開すると、セキュリティアドバイザリの一時的なプライベートフォークが削除されます。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、公開するセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. ページの下部にある **[アドバイザリの公開]** をクリックします。 - ![[アドバイザリの公開] ボタン](/assets/images/help/security/publish-advisory-button.png) - -## 公開されたセキュリティアドバイザリの {% data variables.product.prodname_dependabot_alerts %} - -{% data reusables.repositories.github-reviews-security-advisories %} - -## CVE 識別番号をリクエストする (省略可能) - -{% data reusables.repositories.request-security-advisory-cve-id %} 詳細については、「[リポジトリの {% data variables.product.prodname_security_advisories %} について](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)」を参照してください。 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、CVE 識別番号をリクエストするセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. **[アドバイザリの公開]** ドロップダウン メニューを使用して、 **[CVE の要求]** をクリックします。 - ![ドロップダウンの [CVE の要求]](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. **[CVE の要求]** をクリックします。 - ![[CVE の要求] ボタン](/assets/images/help/security/security-advisory-request-cve-button.png) - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md deleted file mode 100644 index db0429345e..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリからのコラボレータの削除 -intro: リポジトリ セキュリティ アドバイザリからコラボレーターを削除すると、そのコラボレーターはセキュリティ アドバイザリのディスカッションとメタデータへの読み取りおよび書き込みアクセス権を失います。 -redirect_from: - - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory - - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities - - Collaboration -shortTitle: Remove collaborators -ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145119358' ---- -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリからコラボレータを削除できます。 - -{% data reusables.security-advisory.repository-level-advisory-note %} - -## セキュリティアドバイザリからコラボレータを削除する - -{% data reusables.repositories.security-advisory-collaborators-public-repositories %} - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、コラボレータを削除するセキュリティアドバイザリをクリックします。 - ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリから削除するユーザまたは Team の名前を探します。 - ![セキュリティ アドバイザリのコラボレータ](/assets/images/help/security/security-advisory-collaborator.png) -6. 削除するコラボレーターの横にある **[X]** アイコンをクリックします。 - ![セキュリティ アドバイザリからコラボレータを削除する [X] アイコン](/assets/images/help/security/security-advisory-remove-collaborator-x.png) - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 -- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md deleted file mode 100644 index 2c3377b904..0000000000 --- a/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: リポジトリ セキュリティ アドバイザリの撤回 -intro: 公開したリポジトリ セキュリティ アドバイザリを撤回できます。 -redirect_from: - - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory - - /code-security/security-advisories/withdrawing-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities -shortTitle: Withdraw repository advisories -ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145119326' ---- -{% data reusables.security-advisory.repository-level-advisory-note %} - -誤ってセキュリティアドバイザリを公開した場合は、{% data variables.contact.contact_support %} に連絡するとセキュリティアドバイザリを撤回できます。 - -## 参考資料 - -- 「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md index b9dce9457c..f1c959c882 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md @@ -110,6 +110,6 @@ monitor results from {% data variables.product.prodname_secret_scanning %} acros - "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" {%- ifversion fpt or ghec %} - "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 %} +{%- ifversion fpt or ghec or ghes %} - "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)"{% endif %} - "[Encrypted secrets](/actions/security-guides/encrypted-secrets)" diff --git a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 03bf9dd95a..3b0a2bf172 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -15,35 +15,12 @@ topics: - Secret scanning --- -{% ifversion ghes < 3.3 %} -{% note %} - -**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change. - -{% endnote %} -{% endif %} ## About custom patterns for {% data variables.product.prodname_secret_scanning %} You can define custom patterns to identify secrets that are not detected by the default patterns supported by {% data variables.product.prodname_secret_scanning %}. For example, you might have a secret pattern that is internal to your organization. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." -You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to -{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository. -{%- elsif ghes = 3.2 %} 20 custom patterns for each organization or enterprise account, and per repository. -{%- else %} 100 custom patterns for each organization or enterprise account, and 20 per repository. -{%- endif %} - -{% ifversion ghes < 3.3 %} -{% note %} - -**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}: - -* There is no dry-run functionality. -* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it. -* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning). - -{% endnote %} -{% endif %} +You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository. ## Regular expression syntax for custom patterns @@ -160,7 +137,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin 1. Under "Code security and analysis", click **Security features**.{% else %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %}{% endif %} -1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}. +1. Under "Secret scanning custom patterns", click **New pattern**. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} {%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %} 1. When you're ready to test your new custom pattern, to identify matches in the enterprise without creating alerts, click **Save and dry run**. @@ -172,7 +149,6 @@ Before defining a custom pattern, you must ensure that you enable secret scannin After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Editing a custom pattern When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. @@ -184,7 +160,6 @@ When you save a change to a custom pattern, this closes all the {% data variable 3. When you're ready to test your edited custom pattern, to identify matches without creating alerts, click **Save and dry run**. {%- endif %} 4. When you have reviewed and tested your changes, click **Save changes**. -{% endif %} ## Removing a custom pattern @@ -192,13 +167,8 @@ When you save a change to a custom pattern, this closes all the {% data variable * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above. * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. -{%- ifversion ghec or ghes > 3.2 or ghae %} 1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. 1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. 1. Click **Yes, delete this pattern**. - ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) -{%- elsif ghes = 3.2 %} -1. To the right of the custom pattern you want to remove, click **Remove**. -1. Review the confirmation, and click **Remove custom pattern**. -{%- endif %} + ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) \ No newline at end of file diff --git a/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md index e7ef382b5d..78b23e2fe1 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md @@ -137,4 +137,4 @@ If you confirm a secret is real and that you intend to fix it later, you should 1. Click **Allow secret**. -{% endif %} \ No newline at end of file +{% endif %} 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 69e55a8adc..c763b80753 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 @@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level. +Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} + {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} ### 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, 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. +Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to. + +Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %} {% elsif fpt %} ### About the enterprise-level security overview At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation. {% endif %} +{% ifversion ghes < 3.7 or ghae < 3.7 %} ### 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 %} +{% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md index 882ad462dc..28d368418f 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md @@ -47,7 +47,7 @@ As a first step, you want to make a complete inventory of your dependencies. The ### Automatic detection of vulnerabilities in dependencies -{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes > 3.2 %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes > 3.2 %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}. +{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}. ### Assessment of exposure to risk from a vulnerable dependency @@ -81,15 +81,13 @@ If your organization uses {% data variables.product.prodname_GH_advanced_securit You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### Secure storage of secrets you use in {% data variables.product.product_name %} -{% endif %} {% ifversion fpt or ghec %} Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows, {% data variables.product.prodname_dependabot %}, or your {% data variables.product.prodname_github_codespaces %} development environment to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets)," "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)," and "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)." {% endif %} -{% ifversion ghes > 3.2 or ghae %} +{% ifversion ghes or ghae %} Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows{% ifversion ghes %} or {% data variables.product.prodname_dependabot %}{% endif %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets){% ifversion ghes %}" and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."{% else %}."{% endif %} {% endif %} 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 7a13366bbb..3e83d7902b 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 @@ -19,8 +19,6 @@ redirect_from: - /code-security/supply-chain-security/about-dependency-review --- -{% data reusables.dependency-review.beta %} - ## About dependency review {% data reusables.dependency-review.feature-overview %} 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 33e8c19950..8e83dd646e 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 @@ -1,6 +1,6 @@ --- title: About supply chain security -intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and patching them{% endif %}.' +intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Supply chain security redirect_from: @@ -27,13 +27,13 @@ With the accelerated use of open source, most projects depend on hundreds of ope You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency. -{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghes < 3.3 or ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. +{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. The supply chain features on {% data variables.product.product_name %} are: - **Dependency graph** - **Dependency review** - **{% data variables.product.prodname_dependabot_alerts %} ** -{% ifversion fpt or ghec or ghes > 3.2 %}- **{% data variables.product.prodname_dependabot_updates %}** +{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}** - **{% data variables.product.prodname_dependabot_security_updates %}** - **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %} @@ -43,7 +43,7 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely - Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests. - {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected. -{% ifversion fpt or ghec or ghes > 3.2 %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository. +{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository. {% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities. {% endif %} @@ -79,9 +79,9 @@ For more information about dependency review, see "[About dependency review](/co ### What is Dependabot -{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}. +{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}. -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} The term "{% data variables.product.prodname_dependabot %}" encompasses the following features: - {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version. - {% data variables.product.prodname_dependabot_updates %}: @@ -117,7 +117,7 @@ The term "{% data variables.product.prodname_dependabot %}" encompasses the foll For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} #### What are Dependabot updates There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences. @@ -166,7 +166,7 @@ Any repository type: - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. 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)." - **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} -{% ifversion ghes > 3.2 %} +{% ifversion ghes %} - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." - **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)." {% endif %} 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 15849448f0..42541c3ef9 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 @@ -79,11 +79,7 @@ The recommended formats explicitly define which versions are used for all direct {%- ifversion github-actions-in-dependency-graph %} | {% data variables.product.prodname_actions %} workflows[†] | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` | {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | -{%- elsif ghes = 3.2 %} -| Go modules | Go | `go.mod` | `go.mod` | -{%- endif %} | Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| | pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`[‡] | 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 06bb91f769..460c0bb236 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 @@ -4,7 +4,7 @@ intro: You can use dependency review to catch vulnerabilities before they are ad shortTitle: Configure dependency review versions: fpt: '*' - ghes: '>= 3.2' + ghes: '*' ghae: '*' ghec: '*' type: how_to @@ -16,8 +16,6 @@ topics: - Pull requests --- -{% data reusables.dependency-review.beta %} - ## About dependency review {% data reusables.dependency-review.feature-overview %} @@ -46,8 +44,7 @@ Dependency review is available when dependency graph is enabled for {% data vari {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %} 1. Under "Configure security and analysis features", check if the dependency graph is enabled. -1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes < 3.3 %} - ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %} +1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %} ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %} {% endif %} 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 299550e2af..c1879f3d31 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 @@ -1,6 +1,6 @@ --- -title: 依存関係グラフのトラブルシューティング -intro: 依存関係グラフによって報告された依存関係の情報が期待したものと異なる場合、いくつかの考慮するポイントと、さまざまな確認項目があります。 +title: Troubleshooting the dependency graph +intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.' shortTitle: Troubleshoot dependency graph versions: fpt: '*' @@ -16,56 +16,51 @@ topics: - Dependency graph - CVEs - Repositories -ms.openlocfilehash: 51a1da4eff062263aeca52de02b764385e7e1184 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146458245' --- + {% data reusables.dependabot.result-discrepancy %} -## 依存関係グラフは、マニフェストとロックファイルの依存関係のみを検索しますか？ +## Does the dependency graph only find dependencies in manifests and lockfiles? -依存関係グラフには、環境で明示的に宣言されている依存関係に関する情報が{% ifversion dependency-submission-api %}自動的に{% endif %}含まれます。 つまり、マニフェストまたはロックファイルで指定されている依存関係です。 依存関係グラフには、通常、マニフェストファイル内の依存関係の依存関係を調べることにより、ロックファイルで指定されていない場合でも、推移的な依存関係も含まれます。 +The dependency graph {% ifversion dependency-submission-api %}automatically{% endif %} includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file. -"ゆるい" 依存関係が依存関係グラフに{% ifversion dependency-submission-api %}自動的に{% endif %}含まれることはありません。 「ゆるい」依存関係は、パッケージマネージャーのマニフェストまたはロックファイルで参照されるのではなく、あるソースからコピーされ、リポジトリに直接またはアーカイブ (ZIP ファイルや JAR ファイルなど) に含まれてチェックインされる個々のファイルです。 +The dependency graph doesn't {% ifversion dependency-submission-api %}automatically{% endif %} include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. -{% ifversion dependency-submission-api %}ただし、プロジェクトのビルド時に解決される依存関係など、依存関係がマニフェストまたはロック ファイルで宣言されていない場合でも、Dependency submission API (ベータ) を使用して、依存関係をプロジェクトの依存関係グラフに追加できます。 依存関係グラフには、送信された依存関係がエコシステム別にグループ化されて表示されますが、マニフェストまたはロック ファイルから解析された依存関係とは別になっています。 Dependency submission API について詳しくは、「[Dependency submission API の利用](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)」を参照してください。{% endif %} +{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are not declared in a manifest or lock file, such as dependencies resolved when a project is built. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %} -**チェック**: リポジトリのマニフェストまたはロックファイル内で指定されていない、コンポーネントに対する見落とされている依存関係はありますか? +**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile? -## 依存関係グラフは、変数を使用して指定された依存関係を検出しますか？ +## Does the dependency graph detect dependencies specified using variables? -依存関係グラフは、マニフェストが {% data variables.product.prodname_dotcom %} にプッシュされるときにマニフェストを分析します。 したがって、依存関係グラフはプロジェクトのビルド環境にアクセスできないため、マニフェスト内で使用される変数を解決できません。 マニフェスト内で変数を使用して名前、またはより一般的には依存関係のバージョンを指定する場合、その依存関係は依存関係グラフに{% ifversion dependency-submission-api %}自動的には{% endif %}含まれません。 +The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not {% ifversion dependency-submission-api %}automatically{% endif %} be included in the dependency graph. -{% ifversion dependency-submission-api %}ただし、依存関係がプロジェクトのビルド時にのみ解決される場合でも、Dependency submission API (ベータ) を使用して、依存関係をプロジェクトの依存関係グラフに追加できます。 Dependency submission API について詳しくは、「[Dependency submission API の利用](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)」を参照してください。{% endif %} +{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are only resolved when a project is built. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %} -**チェック**: マニフェストで、名前またはバージョンに変数を使用して、見落とされている依存関係が宣言されていますか? +**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version? -## 依存関係グラフのデータに影響する制限はありますか？ +## Are there limits which affect the dependency graph data? -はい、依存関係グラフの制限には 2 つのカテゴリがあります。 +Yes, the dependency graph has two categories of limits: -1. **処理制限** +1. **Processing limits** - これらは {% data variables.product.prodname_dotcom %} 内に表示される依存関係グラフに影響を与え、{% data variables.product.prodname_dependabot_alerts %} が作成されないようにします。 + These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created. - サイズが 0.5 MB を超えるマニフェストは、Enterprise アカウントに対してのみ処理されます。 他のアカウントの場合、0.5 MB を超えるマニフェストは無視され、{% data variables.product.prodname_dependabot_alerts %} は作成されません。 + Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}. - デフォルト設定では、{% data variables.product.prodname_dotcom %} はリポジトリごとに 20 個を超えるマニフェストを処理しません。 {% data variables.product.prodname_dependabot_alerts %} は、この制限を超えるマニフェストに対しては作成されません。 制限を増やす必要がある場合は、{% data variables.contact.contact_support %} にお問い合わせください。 + By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. -2. **視覚化の制限** +2. **Visualization limits** - これらは、{% data variables.product.prodname_dotcom %} 内の依存関係グラフに表示される内容に影響します。 ただし、作成された {% data variables.product.prodname_dependabot_alerts %} には影響しません。 + These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created. - リポジトリの依存関係グラフの依存関係ビューには、100 個のマニフェストのみが表示されます。 通常、これは上記の処理制限よりも大幅に高いので十分です。 処理制限が100 個を超える状況でも、{% data variables.product.prodname_dotcom %} 内に表示されていないマニフェストに対して {% data variables.product.prodname_dependabot_alerts %} が作成されます。 + The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}. -**チェック**: 0.5 MB を超えるマニフェスト ファイル、または多数のマニフェストがあるリポジトリに見落とされている依存関係はありませんか? +**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests? -## 参考資料 +## Further reading -- "[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)" -- 「[リポジトリのセキュリティと分析設定を管理する](/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 %} -- 「[{% data variables.product.prodname_dependabot %} エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)」{% endif %} +- "[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 %} +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index 40094b5db2..fe7c29fd82 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_ By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository. -This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}. +This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}. If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)." diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md index 5aca361ee0..f985434f1b 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md @@ -105,4 +105,4 @@ You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variable - "[Codespaces machines](/rest/codespaces/machines)" in the REST API documentation - [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) in the {% data variables.product.prodname_cli %} manual -{% endcli %} \ No newline at end of file +{% endcli %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 559ed6dc38..f0e477786b 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -153,4 +153,4 @@ For full details of the options for this command, see [the {% data variables.pro ## Further reading - "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)" -- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" \ No newline at end of file +- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 5a9bb4271a..92bf5d8295 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -124,4 +124,4 @@ You can also use the REST API to delete codespaces for your organization. For mo ## Further reading - "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)" -- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" \ No newline at end of file +- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index 680e4301c4..ed9f3b5c99 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -53,4 +53,4 @@ For more information on using {% data variables.product.prodname_vscode_shortnam ### Using the {% data variables.product.prodname_vscode_command_palette %} -The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." \ No newline at end of file +The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md index 670ce75cde..70587a4b81 100644 --- a/translations/ja-JP/content/codespaces/guides.md +++ b/translations/ja-JP/content/codespaces/guides.md @@ -15,6 +15,8 @@ includeGuides: - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces + - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines + - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md index 68ef8f119d..996b22f228 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md @@ -1,7 +1,7 @@ --- title: Listing the codespaces in your organization shortTitle: List organization codespaces -intro: 'You can list all of the currently active or stopped codespaces for your organization.' +intro: You can list all of the currently active or stopped codespaces for your organization. product: '{% data reusables.gated-features.codespaces %}' permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.' versions: @@ -51,4 +51,4 @@ gh codespace list --org ORGANIZATION --user USER You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details. -For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)." \ No newline at end of file +For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)." diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md index b193cde66d..e0494d19cb 100644 --- a/translations/ja-JP/content/codespaces/overview.md +++ b/translations/ja-JP/content/codespaces/overview.md @@ -44,4 +44,4 @@ For information on pricing, storage, and usage for {% data variables.product.pro {% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)." -You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." \ No newline at end of file +You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md index f9f02988d3..0ef2d0b210 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md @@ -1,7 +1,7 @@ --- title: Allowing a prebuild to access other repositories shortTitle: Allow external repo access -intro: You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully. +intro: 'You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.' versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md index 2f135dcff2..17f055bb42 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md @@ -11,12 +11,12 @@ topics: - Codespaces - Set up product: '{% data reusables.gated-features.codespaces %}' -ms.openlocfilehash: 4a45c11adc5d09888e6bb65b49b9f997f5233fea -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: d2ed02a205a4a8c3e55deb0b52fdc9ffdb855dc4 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147783131' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108947' --- ## 概要 @@ -26,7 +26,7 @@ Markdown ファイルに [{% data variables.product.prodname_github_codespaces % バッジを作成するときに、そのバッジで作成される codespace に対して特定の構成オプションを選ぶことができます。 -ユーザーがバッジをクリックすると、codespace の作成用の [詳細オプション] ページに移動します。選んだオプションは事前に選択されています。 詳細オプション ページについて詳しくは、「[codespace の作成](https://docs-internal-30445-bfc9ce.preview.ghdocs.com/en/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 +ユーザーがバッジをクリックすると、codespace の作成用の [詳細オプション] ページに移動します。選んだオプションは事前に選択されています。 詳細オプション ページについて詳しくは、「[codespace の作成](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 [詳細オプション] ページから、ユーザーは必要に応じて事前に選択された設定を変更し、 **[codespace の作成]** をクリックできます。 diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md index f0ae6ea87c..2219a57e3b 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -17,6 +17,7 @@ children: - /setting-up-your-java-project-for-codespaces - /setting-up-your-python-project-for-codespaces - /setting-a-minimum-specification-for-codespace-machines + - /automatically-opening-files-in-the-codespaces-for-a-repository - /adding-a-codespaces-badge ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md index 9bb7455d6a..9bd36a5a2a 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md @@ -1,7 +1,7 @@ --- -title: codespace コンピューターに対して最小仕様を設定する +title: Setting a minimum specification for codespace machines shortTitle: Set a minimum machine spec -intro: 'リソース不足のコンピューターの種類が、リポジトリの {% data variables.product.prodname_github_codespaces %} に使用されないようにすることができます。' +intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.' permissions: People with write permissions to a repository can create or edit the codespace configuration. versions: fpt: '*' @@ -11,29 +11,24 @@ topics: - Codespaces - Set up product: '{% data reusables.gated-features.codespaces %}' -ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880807' --- -## 概要 -作成する各 codespace は個別の仮想マシンでホストされ、通常はさまざまな種類の仮想マシンから選択できます。 マシンの種類ごとにリソース (CPU、メモリ、ストレージ) が異なり、既定では、リソースが最も少ないコンピューターの種類が使用されます。 詳細については、「[codespace に合わせたコンピューターの種類の変更](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)」を参照してください。 +## Overview -プロジェクトで特定のレベルのコンピューティング能力が必要な場合は、それらの要件を満たすコンピューターの種類のみを、既定で使用、またはユーザーが選択できるように、{% data variables.product.prodname_github_codespaces %} を構成することができます。 `devcontainer.json` ファイル内でこれを構成します。 +Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)." + +If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file. {% note %} -**重要:** 一部のコンピューターの種類へのアクセスは、組織レベルで制限される場合があります。 通常、これは、より高いレートで課金される、よりリソースの多いコンピューターをユーザーが選択することを防ぐために行われます。 リポジトリがコンピューターの種類に関する組織レベルのポリシーの影響を受ける場合は、ユーザーが選択できるコンピューターの種類がなくなるような最小仕様を設定しないようにする必要があります。 詳細については、「[コンピューターの種類へのアクセスの制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」を参照してください。 +**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)." {% endnote %} -## コンピューターの最小仕様の設定 +## Setting a minimum machine specification -1. ご利用のリポジトリの {% data variables.product.prodname_github_codespaces %} は、`devcontainer.json` ファイル内で構成されます。 リポジトリに `devcontainer.json` ファイルがまだ含まれていない場合は、今すぐ追加します。 「[開発コンテナー構成をリポジトリに追加する](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)」を参照してください。 -1. `devcontainer.json` ファイルを編集し、次のような `hostRequirements` プロパティを追加します。 +{% data reusables.codespaces.edit-devcontainer-json %} +1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example: ```json{:copy} "hostRequirements": { @@ -43,16 +38,16 @@ ms.locfileid: '147880807' } ``` - 次のいずれかの、またはすべてのオプションを指定できます: `cpus`、`memory`、`storage`。 + You can specify any or all of the options: `cpus`, `memory`, and `storage`. - リポジトリで現在使用可能な、{% data variables.product.prodname_github_codespaces %} のコンピューターの種類の仕様を確認するには、コンピューターの種類の選択肢が表示されるまで、codespace の作成プロセスをステップ実行します。 詳細については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 + To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." -1. ファイルを保存し、リポジトリの必要なブランチに加えた変更をコミットします。 +1. Save the file and commit your changes to the required branch of the repository. - ここで、リポジトリのそのブランチ用に codespace を作成し、作成設定オプションに進むと、指定したリソースと一致するか、またはそれを超えるコンピューターの種類のみを選択できるようになります。 + Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified. - ![コンピューターの種類の選択が制限されているダイアログ ボックス](/assets/images/help/codespaces/machine-types-limited-choice.png) + ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png) -## 参考資料 +## Further reading -- "[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)" +- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)" diff --git a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md index 3944c4fa55..5b85af4092 100644 --- a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md @@ -2,7 +2,7 @@ title: The github.dev web-based editor intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' versions: - feature: 'githubdev-editor' + feature: githubdev-editor type: how_to miniTocMaxHeadingLevel: 3 topics: diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md index ec51c0bd71..476e7fe0ae 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md @@ -1,5 +1,5 @@ --- -title: Troubleshooting dotfiles for GitHub Codespaces +title: Troubleshooting dotfiles for GitHub Codespaces allowTitleToDifferFromFilename: true intro: Troubleshooting steps for common dotfiles issues. product: '{% data reusables.gated-features.codespaces %}' @@ -23,4 +23,4 @@ If your codespace fails to pick up configuration settings from dotfiles, you sho - If your dotfiles were not cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. 1. Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. For more information, see [Creation logs](/codespaces/troubleshooting/codespaces-logs#creation-logs). -If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings. \ No newline at end of file +If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings. diff --git a/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md b/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md index bf4bfa7870..181734a513 100644 --- a/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md +++ b/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md @@ -11,12 +11,12 @@ redirect_from: - /github/copilot/about-github-copilot-telemetry - /github/copilot/github-copilot-telemetry-terms shortTitle: GitHub.com -ms.openlocfilehash: 139a2c93c76155eff092ca168129f8ef52ce69ae -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: cc87328504e3d9eb5e2bce83d981098b7f989ae0 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147080107' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108838' --- ## {% data variables.product.prodname_dotcom_the_website %} での {% data variables.product.prodname_copilot %} の設定について 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 9ed610b338..557287e15b 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 @@ -341,8 +341,8 @@ 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 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 %} +* "[Device flow errors](#error-codes-for-the-device-flow)" +* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)" ## 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 166ace7868..db0162551d 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,9 +84,9 @@ Keep these ideas in mind when using {% data variables.product.pat_generic %}s: * 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 or ghec %} +* Don't set up a shared personal account to act as a bot user. * Grant your token the minimal privileges it needs. -* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.{% endif %} +* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure. ## Determining which integration to build diff --git a/translations/ja-JP/content/developers/index.md b/translations/ja-JP/content/developers/index.md index 1cbd15dda1..913d3a3de9 100644 --- a/translations/ja-JP/content/developers/index.md +++ b/translations/ja-JP/content/developers/index.md @@ -34,11 +34,11 @@ children: - /webhooks-and-events - /apps - /github-marketplace -ms.openlocfilehash: 00e920befd903527d2928d7ddf6b0b76ab448341 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: dea95cbf3a90b14441c8bd09692c27dd3798d8e5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147643982' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109276' --- 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 0caacccdd8..7f68a7bb88 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 @@ -734,7 +734,6 @@ For a detailed description of this payload and the payload for each type of `act Activity related to merge groups in a merge queue. The type of activity is specified in the action property of the payload object. - ### Availability - Repository webhooks @@ -1621,8 +1620,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae %} - ## workflow_job {% data reusables.webhooks.workflow_job_short_desc %} @@ -1644,7 +1641,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS {{ webhookPayloadsForCurrentVersion.workflow_job }} -{% endif %} {% ifversion fpt or ghes or ghec %} ## workflow_run diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md index 2357d70f1d..96de480aa8 100644 --- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md +++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md @@ -4,12 +4,12 @@ shortTitle: Get started intro: '{% data variables.product.prodname_community_exchange %} にアクセスし、リポジトリを送信する方法について説明します。' versions: fpt: '*' -ms.openlocfilehash: f9280e380b251c52d2b582aadb55eb319d5c342d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b9c866ef33c321b70b87d8bcd3682d0c02737bfe +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574005' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109507' --- ## はじめに diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md index 121b3489d6..23467d9a59 100644 --- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md +++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md @@ -8,11 +8,11 @@ children: - /getting-started-with-github-community-exchange - /submitting-your-repository-to-github-community-exchange - /managing-your-submissions-to-github-community-exchange -ms.openlocfilehash: 420db797ef8e913a597647f2a20fad8cea2c5861 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fe002b4cff8bbecaac9ea4611ff69ab366df240f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409801' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109500' --- diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md index ee911e2c74..a9949ecf65 100644 --- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md +++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md @@ -4,12 +4,12 @@ shortTitle: Manage your submissions intro: '{% data variables.product.prodname_community_exchange %} ギャラリー内の各リポジトリに割り当てられている目的、トピック、オファーを管理したり、リポジトリの送信を削除したりできます。' versions: fpt: '*' -ms.openlocfilehash: 70dc65ccb387817d5b4a78c1fc27085f67dcfc6e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a7da6f3bede47700658fe81a1f0ec3e4e33ef316 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409789' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109476' --- ## 送信について diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md index a0efcd57ad..0cc96fab46 100644 --- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md +++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md @@ -4,12 +4,12 @@ shortTitle: Submit your repository intro: '他のユーザーが閲覧または投稿できるように、リポジトリを {% data variables.product.prodname_community_exchange %} に送信できます。' versions: fpt: '*' -ms.openlocfilehash: d520f303bf368c9230f26580ba2de9bd744b21e7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 07198c74937470a591b30702bd027036d91d3ec7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409783' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109475' --- ## リポジトリの送信について diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md index ea2bbcdb07..872af6c9e9 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md @@ -10,12 +10,12 @@ redirect_from: versions: fpt: '*' shortTitle: For students -ms.openlocfilehash: a34da8bd0f37646bfaad0dbff3b09c6f2df440e4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9012b473399905e60b04a8876a3d4e6afd10a6ba +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574231' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109468' --- 学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md index ecb7b10994..7b76fa9471 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md @@ -1,5 +1,5 @@ --- -title: 'Apply to GitHub Global Campus as a student' +title: Apply to GitHub Global Campus as a student intro: 'As a student, you can apply to join {% data variables.product.prodname_global_campus %} and receive access to the student resources and benefits offered by {% data variables.product.prodname_education %}' redirect_from: - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md index 5f4e6a1daf..068c2e4caa 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md @@ -14,11 +14,11 @@ children: - /why-wasnt-my-application-to-global-campus-for-students-approved - /about-github-community-exchange shortTitle: About Global Campus for students -ms.openlocfilehash: 2ee0b90dc4cc25bbd3ac253e22c516ec3984b94a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 3f61867f7d7365635a8b2d3bd53a19b0180d0604 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574261' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109467' --- diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md index 6d9fb98eb5..6a66913540 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md @@ -10,12 +10,12 @@ redirect_from: versions: fpt: '*' shortTitle: For teachers -ms.openlocfilehash: d4e823cc97b9c75f264b856c39021e30ca0e4fed -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6a0e8b7ba27060b4f48438b515786256d93d6d0c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574219' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108892' --- 認定教育機関の学生または教職員は、{% data variables.product.prodname_education %} 特典とリソースが含まれている {% data variables.product.prodname_global_campus %} を申し込むことができます。 詳しくは、「[教師として {% data variables.product.prodname_global_campus %} に応募する](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)」を参照してください。 diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md index e558dece7e..f3409cc320 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md @@ -13,11 +13,11 @@ children: - /apply-to-github-global-campus-as-a-teacher - why-wasnt-my-application-to-global-campus-for-teachers-approved shortTitle: About Global Campus for teachers -ms.openlocfilehash: f257ff9da81c99c87caf8f864e621cb7e382974d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b29cc4c76f0eb407dafb4080061f7f8a4c9cf62b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574252' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108898' --- diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md index 3ba439a70c..9ab2352573 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md @@ -12,12 +12,12 @@ redirect_from: versions: fpt: '*' shortTitle: Application not approved -ms.openlocfilehash: 86d1f0c3bc1bfe451be611ce47cc3f715fd8ba92 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 68fe0a970c94a73293505849425bc78ec78b265e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147574245' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108893' --- {% tip %} 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 401194125d..7f2ad08c68 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 @@ -51,7 +51,7 @@ For information about {% data variables.product.prodname_advanced_security %} fe {% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features). {% endif %} -{% ifversion ghes > 3.1 or ghec or ghae %} +{% ifversion ghes or ghec or ghae %} ## Deploying GitHub Advanced Security in your enterprise To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)." 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 746d67c59d..4681320f39 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 @@ -151,4 +151,4 @@ For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt o For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." -To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)." \ No newline at end of file +To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)." diff --git a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md index b90de8630e..4bd5001966 100644 --- a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md +++ b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md @@ -26,7 +26,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife. 2. Click **Fork**. - ![Fork button](/assets/images/help/repository/fork_button.png) + ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %} 3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. @@ -43,6 +43,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn **Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)." {% endnote %} +{% endif %} ## Cloning a fork diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md index ad5ed4621b..a8107f1dd2 100644 --- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md @@ -57,7 +57,7 @@ You might fork a project to propose changes to the upstream, or original, reposi 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. 2. In the top-right corner of the page, click **Fork**. - ![Fork button](/assets/images/help/repository/fork_button.png) + ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %} 3. Select an owner for the forked repository. ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. @@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi {% note %} -**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %} +**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %} {% endwebui %} 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 63db7352b5..416cf4f6d1 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 @@ -94,13 +94,13 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Command+K (Mac) or
Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %} |Command+V (Mac) or
Ctrl+V (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %} |Command+Shift+P (Mac) or
Ctrl+Shift+P (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %} -|Command+Shift+V (Mac) or
Ctrl+Shift+V (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -|Command+Shift+Option+V (Mac) or
Ctrl+Shift+Alt+V (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +|Command+Shift+V (Mac) or
Ctrl+Shift+V (Windows/Linux) | Pastes HTML link as plain text{% endif %} +|Command+Shift+Option+V (Mac) or
Ctrl+Shift+Alt+V (Windows/Linux) | Pastes HTML link as plain text |Command+Shift+7 (Mac) or
Ctrl+Shift+7 (Windows/Linux) | Inserts Markdown formatting for an ordered list -|Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %} +|Command+Shift+8 (Mac) or
Ctrl+Shift+8 (Windows/Linux) | Inserts Markdown formatting for an unordered list |Command+Enter (Mac) or
Ctrl+Enter (Windows/Linux) | Submits a comment -|Ctrl+. and then Ctrl+[saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -|Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %} +|Ctrl+. and then Ctrl+[saved reply number] | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)." +|Command+Shift+. (Mac) or
Ctrl+Shift+. (Windows/Linux) | Inserts Markdown formatting for a quote{% ifversion fpt or ghec %} |Command+G (Mac) or
Ctrl+G (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} |R | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | 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 b229b71ca3..5047a0f091 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 @@ -324,7 +324,6 @@ For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet]( You can create a new paragraph by leaving a blank line between lines of text. -{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Footnotes You can add footnotes to your content by using this bracket syntax: @@ -355,7 +354,6 @@ The footnote will render like this: Footnotes are not supported in wikis. {% endtip %} -{% endif %} ## Hiding content with comments @@ -375,14 +373,10 @@ You can tell {% data variables.product.product_name %} to ignore (or escape) Mar For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} - ## Disabling Markdown rendering {% data reusables.repositories.disabling-markdown-rendering %} -{% endif %} - ## Further reading - [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md index 6c5a8fa020..354bd50661 100644 --- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md @@ -60,8 +60,8 @@ For some example queries, see "[An example query using the Enterprise Accounts A - `admin:enterprise` The enterprise account specific scopes are: - - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) - - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae %} + - `admin:enterprise`: Gives full control of enterprises (includes `manage_runners:enterprise`, `manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes or ghae %} - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Read enterprise profile data. diff --git a/translations/ja-JP/content/graphql/overview/breaking-changes.md b/translations/ja-JP/content/graphql/overview/breaking-changes.md index 5bce1f800b..bfa41e837e 100644 --- a/translations/ja-JP/content/graphql/overview/breaking-changes.md +++ b/translations/ja-JP/content/graphql/overview/breaking-changes.md @@ -10,12 +10,12 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: ee38f60dfd12d00688e46c739fc41f328203daf5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c76520b1f9dc806659373771b42501e072319937 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147496653' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109499' --- ## 破壊的変更について diff --git a/translations/ja-JP/content/graphql/overview/changelog.md b/translations/ja-JP/content/graphql/overview/changelog.md index ad79081118..81821a41f8 100644 --- a/translations/ja-JP/content/graphql/overview/changelog.md +++ b/translations/ja-JP/content/graphql/overview/changelog.md @@ -10,11 +10,11 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: e5e1fc0708f46759837f29f0eadcaf8abce15220 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 34f0baed8b75614c939281ed6a2393d7c809c82f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147496549' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109055' --- 破壊的変更には、既存のクエリを損なったり、クライアントの実行時の振る舞いに影響するかもしれない変更が含まれます。 破壊的変更とそれらが行われる時期のリストについては、「[破壊的変更の履歴](/graphql/overview/breaking-changes)」を参照してください。 diff --git a/translations/ja-JP/content/graphql/overview/schema-previews.md b/translations/ja-JP/content/graphql/overview/schema-previews.md index 32d9c085ad..c2e29a1c24 100644 --- a/translations/ja-JP/content/graphql/overview/schema-previews.md +++ b/translations/ja-JP/content/graphql/overview/schema-previews.md @@ -10,12 +10,12 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: a4097cd792931fe33363229b24f0043b9b99a1cd -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 038afd8cbdd60863213eae385ec9a26f707f62d8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147496597' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109054' --- ## スキーマプレビューについて diff --git a/translations/ja-JP/content/graphql/reference/enums.md b/translations/ja-JP/content/graphql/reference/enums.md index ad20e7b08e..5c5a96f34d 100644 --- a/translations/ja-JP/content/graphql/reference/enums.md +++ b/translations/ja-JP/content/graphql/reference/enums.md @@ -4,10 +4,10 @@ redirect_from: - /v4/enum - /v4/reference/enum versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/graphql/reference/input-objects.md b/translations/ja-JP/content/graphql/reference/input-objects.md index 2e2b6f22a9..c2fac85996 100644 --- a/translations/ja-JP/content/graphql/reference/input-objects.md +++ b/translations/ja-JP/content/graphql/reference/input-objects.md @@ -4,10 +4,10 @@ redirect_from: - /v4/input_object - /v4/reference/input_object versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/graphql/reference/interfaces.md b/translations/ja-JP/content/graphql/reference/interfaces.md index 6575e382f5..7834a90307 100644 --- a/translations/ja-JP/content/graphql/reference/interfaces.md +++ b/translations/ja-JP/content/graphql/reference/interfaces.md @@ -4,10 +4,10 @@ redirect_from: - /v4/interface - /v4/reference/interface versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/graphql/reference/mutations.md b/translations/ja-JP/content/graphql/reference/mutations.md index 4fdac19d7f..d92aac569f 100644 --- a/translations/ja-JP/content/graphql/reference/mutations.md +++ b/translations/ja-JP/content/graphql/reference/mutations.md @@ -4,10 +4,10 @@ redirect_from: - /v4/mutation - /v4/reference/mutation versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/graphql/reference/objects.md b/translations/ja-JP/content/graphql/reference/objects.md index 0fd065294c..a843b57912 100644 --- a/translations/ja-JP/content/graphql/reference/objects.md +++ b/translations/ja-JP/content/graphql/reference/objects.md @@ -4,10 +4,10 @@ redirect_from: - /v4/object - /v4/reference/object versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/graphql/reference/queries.md b/translations/ja-JP/content/graphql/reference/queries.md index 971960270b..394cfc85e2 100644 --- a/translations/ja-JP/content/graphql/reference/queries.md +++ b/translations/ja-JP/content/graphql/reference/queries.md @@ -11,12 +11,12 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: 2e4f855c4140193b2d814b937341665e13a535de -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d5c31e8e00788d2e75f27b0bb161249f01fcfb1d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147496525' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109043' --- ## クエリについて diff --git a/translations/ja-JP/content/graphql/reference/scalars.md b/translations/ja-JP/content/graphql/reference/scalars.md index fa1909884b..197191569b 100644 --- a/translations/ja-JP/content/graphql/reference/scalars.md +++ b/translations/ja-JP/content/graphql/reference/scalars.md @@ -10,12 +10,12 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: f52c697c5b9659ff387102756e34cd9a332e882c -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 731b2085e9b207298b39b99b4b37907c517b5814 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147879112' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109704' --- ## スカラについて diff --git a/translations/ja-JP/content/graphql/reference/unions.md b/translations/ja-JP/content/graphql/reference/unions.md index 08cac387e2..f0e4e92119 100644 --- a/translations/ja-JP/content/graphql/reference/unions.md +++ b/translations/ja-JP/content/graphql/reference/unions.md @@ -4,10 +4,10 @@ redirect_from: - /v4/union - /v4/reference/union versions: - fpt: "*" - ghec: "*" - ghes: "*" - ghae: "*" + fpt: '*' + ghec: '*' + ghes: '*' + ghae: '*' topics: - API --- diff --git a/translations/ja-JP/content/index.md b/translations/ja-JP/content/index.md index 91ea171895..967cb422fb 100644 --- a/translations/ja-JP/content/index.md +++ b/translations/ja-JP/content/index.md @@ -128,11 +128,11 @@ externalProducts: name: npm href: 'https://docs.npmjs.com/' external: true -ms.openlocfilehash: dfd88a0c13da67bf929a5f5334e73319c04ad394 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 09ad193360503125adce9c659a465cfae32dd54e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147643846' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148107630' --- diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md index 78808d8231..f269ee99ac 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md @@ -17,11 +17,11 @@ redirect_from: - /tracking-progress-on-your-project-board - /filtering-cards-on-a-project-board - /archiving-cards-on-a-project-board -ms.openlocfilehash: c498a1e93008276aebe022dcc53a66086b86def7 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 5827065f7fe316f4ec8ea41b56be61b1e01943dd +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147422989' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109042' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md index 10255228be..c963d25a3a 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 76cea8f38d7470bd7b6212ae1f93601b5e8c923b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 28c4719cca14dff54d971b9a081837c172f4da76 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423341' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108982' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index aa83f058df..1ef5d0831c 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,5 +1,5 @@ --- -title: About {% data variables.product.prodname_projects_v1 %} +title: 'About {% data variables.product.prodname_projects_v1 %}' intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards @@ -7,7 +7,7 @@ redirect_from: - /articles/about-project-boards - /github/managing-your-work-on-github/about-project-boards versions: - feature: "projects-v1" + feature: projects-v1 topics: - Pull requests allowTitleToDifferFromFilename: true diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md index 6ec3216396..03e1987e4d 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md @@ -1,6 +1,6 @@ --- -title: '{% data variables.product.prodname_project_v1 %}の可視性の変更' -intro: '組織の所有者または{% data variables.projects.projects_v1_board %}管理者は、{% data variables.projects.projects_v1_board %}を{% ifversion ghae %}内部{% else %}パブリック{% endif %}またはプライベートにすることができます。' +title: 'Changing {% data variables.product.prodname_project_v1 %} visibility' +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility - /articles/changing-project-board-visibility @@ -11,12 +11,6 @@ topics: - Pull requests shortTitle: Change visibility allowTitleToDifferFromFilename: true -ms.openlocfilehash: c288e72dccb5c1212e6e01d24197289cc77c18ce -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614480' --- {% data reusables.projects.project_boards_old %} @@ -24,13 +18,15 @@ ms.locfileid: '147614480' {% note %} -**{% ifversion classic-project-visibility-permissions %}注{% else %}注{% endif %}:** {% ifversion classic-project-visibility-permissions %} +**{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %} * {% data reusables.projects.owners-can-limit-visibility-permissions %} -* {% endif %}{% data variables.projects.projects_v1_board %} を{% ifversion ghae %}内部{% else %}パブリック{% endif %}にすると、Organization のメンバーには既定で読み取りアクセス権が付与されます。 特定の Organization メンバーに書き込みまたは管理者権限を付与するには、参加しているチームへのアクセス権限を与えるか、{% data variables.projects.projects_v1_board %}にコラボレーターとして追加します。 詳しくは、「[Organization の{% data variables.product.prodname_project_v1_caps %}のアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。 +* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endnote %} -1. {% ifversion ghae %}インターナル{% else %}パブリック{% endif %}もしくはプライベートにしたいプロジェクトボードにアクセスしてください。 -{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.choose-visibility %} -1. **[保存]** をクリックします。 +1. Navigate to the project board you want to make {% ifversion ghae %}internal{% else %}public{% endif %} or private. +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.choose-visibility %} +1. Click **Save**. diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md index f83625c8c4..7896a33f2d 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md @@ -11,12 +11,12 @@ versions: topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: fb62345b404e94ddd5a6a22995b9481c9855914d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 21dfb0c6837f97d567f19168cd7f343aac06a4c0 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422709' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109703' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md index d306081d2c..8dc6a0a663 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md @@ -15,12 +15,12 @@ topics: shortTitle: Configure automation type: how_to allowTitleToDifferFromFilename: true -ms.openlocfilehash: 67294015021ef97a8210bff8bbe6c95e352dc26e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: faf559c3423178b43f3b524bbf3cdc41acd18a92 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422685' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109698' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md index 2c589a5ac7..2e1aef5aab 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md @@ -1,6 +1,6 @@ --- -title: '{% data variables.product.prodname_project_v1 %}のコピー' -intro: '{% data variables.projects.projects_v1_board %}をコピーして、新しいプロジェクトをすばやく作成できます。 頻繁に使用される、または高度にカスタマイズされた{% data variables.projects.projects_v1_boards %}をコピーすると、ワークフローの標準化に役立ちます。' +title: 'Copying a {% data variables.product.prodname_project_v1 %}' +intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board - /articles/copying-a-project-board @@ -11,34 +11,29 @@ versions: topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: 055e697d2bb5c7aa1ad4667d24bbe919ede87a99 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423605' --- {% data reusables.projects.project_boards_old %} -{% data variables.projects.projects_v1_board %}をコピーすると、{% data variables.projects.projects_v1_board %}のタイトル、説明、および自動化構成を再利用できます。 {% data variables.projects.projects_v1_boards %}をコピーすると、同様のワークフローで新しい{% data variables.projects.projects_v1_boards %}を作成する手動プロセスを排除できます。 +Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows. -{% data variables.projects.projects_v1_board %}を書き込みアクセスがあるリポジトリまたは Organization にコピーするには、読み取りアクセスが必要です。 +You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access. -{% data variables.projects.projects_v1_board %}を Organization にコピーすると、{% data variables.projects.projects_v1_board %}の可視性は既定で非公開になり、可視性を変更するオプションが設定されます。 詳しくは、「[{% data variables.product.prodname_project_v1 %}の可視性の変更](/articles/changing-project-board-visibility/)」を参照してください。 +When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)." -既定では、{% data variables.projects.projects_v1_board %}の自動化も有効になっています。 詳しくは、「[{% data variables.product.prodname_projects_v1 %}の自動化について](/articles/about-automation-for-project-boards/)」を参照してください。 +A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)." -1. コピーする{% data variables.projects.projects_v1_board %}に移動します。 +1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy. {% data reusables.project-management.click-menu %} -3. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、 **[コピー]** をクリックします。 -![プロジェクトボードのサイドバーにある、ドロップダウンメニューの [Copy] オプション](/assets/images/help/projects/project-board-copy-setting.png) -4. [Owner] の下にあるドロップダウンメニューで、プロジェクトボードのコピー先にするリポジトリまたは Organization をクリックします。 -![ドロップダウンメニューから、コピーしたプロジェクトボードのオーナーを選択](/assets/images/help/projects/copied-project-board-owner.png) -5. 必要に応じて、[プロジェクト ボード名] に、コピーした{% data variables.projects.projects_v1_board %}の名前を入力します。 -![コピーされたプロジェクトボードの名前を入力するフィールド](/assets/images/help/projects/copied-project-board-name.png) -6. 必要に応じて、他の人に読んでもらうために、[Description] の下に、コピーしたプロジェクトボードについての説明を入力します。 -![コピーしたプロジェクトボードの説明を入力するフィールド](/assets/images/help/projects/copied-project-board-description.png) -7. 必要に応じて、[Automation settings] の下で、設定済みの自動化されたワークフローをコピーするかどうかを選択します。 既定では、このオプションは有効になっています。 詳しくは、「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards/)」を参照してください。 -![コピーされたプロジェクトボードの自動化設定を選ぶ](/assets/images/help/projects/copied-project-board-automation-settings.png) {% data reusables.project-management.choose-visibility %} -9. **[プロジェクトのコピー]** をクリックします。 -![[コピーを確定する] ボタン](/assets/images/help/projects/confirm-copy-project-board.png) +3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**. +![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png) +4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board. +![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png) +5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}. +![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png) +6. Optionally, under "Description", type a description of the copied project board that other people will see. +![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png) +7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)." +![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png) +{% data reusables.project-management.choose-visibility %} +9. Click **Copy project**. +![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md index d180658a19..8c2e267000 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md @@ -1,6 +1,6 @@ --- -title: '{% data variables.product.prodname_project_v1 %} の作成' -intro: '{% data variables.projects.projects_v1_boards_caps %} は、特定機能の作業の追跡と優先度付け、総合的なロードマップ、さらにはリリース チェックリストなど、ニーズを満たすカスタマイズ ワークフローを作成するために使用できます。' +title: 'Creating a {% data variables.product.prodname_project_v1 %}' +intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board - /articles/creating-a-project @@ -15,12 +15,6 @@ topics: - Project management type: how_to allowTitleToDifferFromFilename: true -ms.openlocfilehash: 9c55be9ea212cf9a09147267fc62da8f6f89fbbc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614256' --- {% data reusables.projects.project_boards_old %} @@ -28,55 +22,94 @@ ms.locfileid: '147614256' {% data reusables.project-management.copy-project-boards %} -{% data reusables.project-management.link-repos-to-project-board %} 詳しい情報については、「[{% data variables.product.prodname_project_v1 %} へのリポジトリのリンク](/articles/linking-a-repository-to-a-project-board)」を参照してください。 +{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %} +](/articles/linking-a-repository-to-a-project-board)." -{% data variables.projects.projects_v1_board %} を作成したら、issue、pull request、ノートを追加できます。 詳しい情報については、「[{% data variables.product.prodname_project_v1 %} への issue と pull request の追加](/articles/adding-issues-and-pull-requests-to-a-project-board)」および「[{% data variables.product.prodname_project_v1 %} へのノートの追加](/articles/adding-notes-to-a-project-board)」を参照してください。 +Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." -{% data variables.projects.projects_v1_board %} を issue や pull request の状態と常に同期させるようにワークフローの自動化を構成することもできます。 詳しい情報については、「[{% data variables.product.prodname_projects_v1 %} の自動化について](/articles/about-automation-for-project-boards)」を参照してください。 +You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." {% data reusables.project-management.project-board-import-with-api %} -## ユーザー所有の {% data variables.projects.projects_v1_board %} の作成 +## Creating a user-owned {% data variables.projects.projects_v1_board %} {% data reusables.projects.classic-project-creation %} {% data reusables.profile.access_profile %} -2. プロファイル ページの上部のメイン ナビゲーションにある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。 -![[プロジェクト] タブ](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %} +2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} +{% data reusables.project-management.linked-repositories %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} {% data reusables.project-management.edit-project-columns %} -## Organization 全体の {% data variables.projects.projects_v1_board %} の作成 +## Creating an organization-wide {% data variables.projects.projects_v1_board %} {% data reusables.projects.classic-project-creation %} -{% ifversion classic-project-visibility-permissions %} {% note %} +{% ifversion classic-project-visibility-permissions %} +{% note %} -**注:** {% data reusables.projects.owners-can-limit-visibility-permissions %} +**Note:** {% data reusables.projects.owners-can-limit-visibility-permissions %} -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.choose-visibility %} +{% data reusables.project-management.linked-repositories %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} {% data reusables.project-management.edit-project-columns %} -## リポジトリの {% data variables.projects.projects_v1_board %} の作成 +## Creating a repository {% data variables.projects.projects_v1_board %} {% data reusables.projects.classic-project-creation %} {% data reusables.repositories.navigate-to-repo %} -2. リポジトリ名の下にある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。 -![[プロジェクト] タブ](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %} +2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.click-new-project %} +{% data reusables.project-management.create-project-name-description %} +{% data reusables.project-management.choose-template %} +{% data reusables.project-management.create-project-button %} +{% data reusables.project-management.add-column-new-project %} +{% data reusables.project-management.name-project-board-column %} +{% data reusables.project-management.select-column-preset %} +{% data reusables.project-management.select-automation-options-new-column %} +{% data reusables.project-management.click-create-column %} +{% data reusables.project-management.add-more-columns %} {% data reusables.project-management.edit-project-columns %} -## 参考資料 +## Further reading -- 「[プロジェクトボードについて](/articles/about-project-boards)」 -- 「[プロジェクトボードの編集](/articles/editing-a-project-board)」{% ifversion fpt or ghec %} -- 「[プロジェクトボードをコピーする](/articles/copying-a-project-board)」{% endif %} -- 「[プロジェクト ボードを閉じる](/articles/closing-a-project-board)」 -- 「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」 +- "[About projects boards](/articles/about-project-boards)" +- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Closing a project board](/articles/closing-a-project-board)" +- "[About automation for project boards](/articles/about-automation-for-project-boards)" diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md index e86b20e254..05eb5e1acd 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md @@ -11,12 +11,12 @@ versions: topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: 13de993715fa8e16f8cbce4555214e7940fb4917 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: fb68b796fa41a565ab2e196f878c17c94ec44a06 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147422973' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108940' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md index fb5cf085e0..61f1a571d6 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md @@ -12,12 +12,12 @@ versions: topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: 23e4958654bd58de323e401ab4b47d1205aaa4ce -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9b3811bcd472d44be809681064476e7e4f5bef08 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422957' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109564' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md index ce33454c75..8f7087dfd5 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md @@ -22,11 +22,11 @@ children: redirect_from: - /github/managing-your-work-on-github/managing-project-boards allowTitleToDifferFromFilename: true -ms.openlocfilehash: a480750b4c44c7934efa6a0a554c1cf7040629de -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b4034bc9c9ffd29709ac491c6729787c958dd50b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422941' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109571' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md index 84e2ed7155..4417ce54eb 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: Link repository to board allowTitleToDifferFromFilename: true -ms.openlocfilehash: 939266bff35928f5b0ae33fe1cce1b380698ee85 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d0893b64551be80577547b9791e7a7ed6a432de0 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423261' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109697' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md index 0b13cd155e..b5fabfbc82 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: d865d4b61000857c943276c45a9ec02163e9f59b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: e0101378c0b7049f7cba5e04dd28231a1237d0c5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882200' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109572' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md index 32b9e379be..45a23052ee 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md @@ -12,12 +12,12 @@ topics: - Pull requests shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 36897518283fa085c37363157fb44cbd8e1a75c6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 3adfb2c337a417b8e4f932ab9ae9860939217c6c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422773' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109692' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md index d7ae97a085..c2a8923ccf 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md @@ -12,12 +12,12 @@ topics: - Pull requests shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 46068bb6de081043b05c78e731a09e7dbaa47c78 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fc9df02b211056a08ed608a6c98b9d2f0b78c5b7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422749' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109788' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md index 1d1148345a..14a1977859 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: de1d0a4981a46c4ceddd73b5d1f49b74f111601f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: bef90f56a55d6d087c21603586def91ec2f1c9ed +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423589' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109691' --- {% data reusables.projects.project_boards_old %} 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 f897fec764..da73054b12 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 @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 337c84415fefad0c542c6b46706de716e71c29b9 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: f203785a6fc18dc5f67b2ae62934aa10c2f6e8b8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882312' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109556' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md index 298e3455f2..be5a9da8aa 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md @@ -16,11 +16,11 @@ children: redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards allowTitleToDifferFromFilename: true -ms.openlocfilehash: ba1428a6423198d972abfb6671165b43c4988f94 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 75699a8c8daa2729de4aaa7389b7e9a0448f09fa +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423621' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109037' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md index f5538eb2e5..c745a9209d 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md @@ -11,12 +11,12 @@ topics: - Pull requests shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 8dae880cb0ef0fbd0a136e16029688c4aaef08ac -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 5104029ad5225c217697ea89a4bca8ff2d3fa4b5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422669' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109036' --- {% data reusables.projects.project_boards_old %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md index 3b0e137b23..87e7359893 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md @@ -1,10 +1,10 @@ --- title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions' -shortTitle: 'Automating with Actions' +shortTitle: Automating with Actions intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.' miniTocMaxHeadingLevel: 3 versions: - feature: "projects-v2" + feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/automating-projects type: tutorial diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md index 2f4dad0c08..93a635bf68 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md @@ -13,11 +13,11 @@ children: - /automating-projects-using-actions - /archiving-items-automatically allowTitleToDifferFromFilename: true -ms.openlocfilehash: 6c9777a65125f574e4a2cd05a7177448606f8348 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9187012a572af445192343af1b1ba121ae442087 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424008' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148107230' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md index afb973e02b..e2b1241fa3 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md @@ -1,10 +1,10 @@ --- title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}' -shortTitle: 'Automating with the API' -intro: 'You can use the GraphQL API to automate your projects.' +shortTitle: Automating with the API +intro: You can use the GraphQL API to automate your projects. miniTocMaxHeadingLevel: 3 versions: - feature: "projects-v2" + feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects type: tutorial @@ -511,7 +511,7 @@ The response will contain the node ID of the newly created draft issue. ```json { "data": { - "addProjectV2ItemById": { + "addProjectV2DraftIssue": { "projectItem": { "id": "PVTI_lADOANN5s84ACbL0zgBbxFc" } diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md index 44e12998e2..ec7814330c 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md @@ -8,12 +8,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 950ad805eaf73361c2c790d9e30c2e1708a871d8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 40f82bbe99ff036a70007f38534d401a972516f7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424878' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109492' --- {% note %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md index 86baf1ff2f..0b5e8191cc 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md @@ -10,12 +10,12 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 0827845ea3dff3a641d99bbac20b8febdfaca885 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6cbe9313866c19e8325bdd34e90c6a39863de515 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424120' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109484' --- {% data variables.product.prodname_projects_v2 %} は、{% data variables.product.company_short %} データを最新の状態に保つアイテムの適応可能なコレクションです。 プロジェクトでは、issue、pull request、メモしたアイデアを追跡できます。 カスタムフィールドを追加して、特定の目的のためのビューを作成できます。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md index cf5fc06b41..5f7d5c1bcf 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md @@ -11,11 +11,11 @@ children: - /creating-a-project - /migrating-from-projects-classic allowTitleToDifferFromFilename: true -ms.openlocfilehash: 3ad98749a0f404446cab9942b8e10883a31bf3ab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 4d982f7f1f5fa66f372bcca74cea084cb2497d9c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424117' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109491' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md index 1cff91eeec..3c10aabb59 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md @@ -1,6 +1,6 @@ --- -title: '{% data variables.product.prodname_projects_v1 %} からの移行' -intro: '{% data variables.projects.projects_v1_board %} を新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行できます。' +title: 'Migrating from {% data variables.product.prodname_projects_v1 %}' +intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,53 +10,57 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: b16235e98306e19a8f08dfc04913c6935772b5cc -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147424116' --- -{% note %} -**注:** - -- 移行するプロジェクトに 1,200 を超える項目が含まれている場合は、未解決の issue が優先され、その後に未解決の pull request、メモが続きます。 残りの領域は、解決された issue、マージされた pull request、および解決された pull request に使用されます。 この制限により移行できない項目は、アーカイブに移動されます。 アーカイブの上限である 10,000 項目に達した場合、追加の項目は移行されません。 -- ノート カードは下書きの issue に変換され、内容は下書きの issue の本文に保存されます。 情報が見つからないように見える場合は、非表示フィールドを表示します。 詳しくは、「[フィールドの表示と非表示](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)」を参照してください。 -- 自動化は移行されません。 -- トリアージ、アーカイブ、アクティビティは移行されません。 -- 移行後、新しく移行されたプロジェクトと古いプロジェクトは同期されません。 - -{% endnote %} - -## プロジェクトの移行について - -プロジェクト ボードを新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行し、テーブル、複数のビュー、新しい自動化オプション、強力なフィールドの種類を試すことができます。 詳しくは、「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。 - -## 組織のプロジェクト ボードの移行 - -{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %} -1. 左側の **[プロジェクト (クラシック)]** をクリックします。 - ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %} - -## ユーザー プロジェクト ボードの移行 - -{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %} -1. プロファイル ページの上部のメイン ナビゲーションにある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。 -![[プロジェクト] タブ](/assets/images/help/projects/user-projects-tab.png) -1. プロジェクトの一覧の上にある **[プロジェクト (クラシック)]** をクリックします。 - ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-user.png) {% data reusables.projects.migrate-project-steps %} - -## リポジトリのプロジェクトボードの移行 {% note %} -**注:** {% data variables.projects.projects_v2_caps %} では、リポジトリ レベルのプロジェクトはサポートされていません。 リポジトリ プロジェクト ボードを移行すると、リポジトリ プロジェクトを所有する組織または個人アカウントに移行され、移行されたプロジェクトは元のリポジトリにピン留めされます。 +**Notes:** + +- If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated. +- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)." +- Automation will not be migrated. +- Triage, archive, and activity will not be migrated. +- After migration, the new migrated project and old project will not be kept in sync. {% endnote %} -{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %} -1. リポジトリ名の下にある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。 -![[プロジェクト] タブ](/assets/images/help/projects/repo-tabs-projects.png) -1. **[プロジェクト (クラシック)]** をクリックします。 - ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %} +## About project migration + +You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." + +## Migrating an organization project board + +{% data reusables.projects.enable-migration %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %} +1. On the left, click **Projects (classic)**. + ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png) +{% data reusables.projects.migrate-project-steps %} + +## Migrating a user project board + +{% data reusables.projects.enable-migration %} +{% data reusables.profile.access_profile %} +1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/user-projects-tab.png) +1. Above the list of projects, click **Projects (classic)**. + ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-user.png) +{% data reusables.projects.migrate-project-steps %} + +## Migrating a repository project board + +{% note %} + +**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository. + +{% endnote %} + +{% data reusables.projects.enable-migration %} +{% data reusables.repositories.navigate-to-repo %} +1. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/repo-tabs-projects.png) +1. Click **Projects (classic)**. + ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png) +{% data reusables.projects.migrate-project-steps %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md index 1929b511b2..960ace9738 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md @@ -1,9 +1,9 @@ --- -title: 'Customizing a view' +title: Customizing a view intro: 'Display the information you need by changing the layout, grouping, sorting in your project.' miniTocMaxHeadingLevel: 3 versions: - feature: "projects-v2" + feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/customizing-your-project-views type: tutorial @@ -147,4 +147,4 @@ In the board layout, you can can choose which columns to display. The available ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md index dd1f43e5b5..171c7b065d 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md @@ -10,12 +10,12 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 820a9b22deab6ecaf7fa06129e2205267b22812c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b1c04738a3c03d892b360c3b23def694d202ee0c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424183' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109025' --- Issueにアサインされた人やラベルといったアイテムのメタデータやプロジェクトのフィールドに対するフィルタを使って、ビューをカスタマイズできます。 フィルタを組み合わせて、ビューとして保存できます。 詳しくは、「[プロジェクトのビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」をご覧ください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md index da6bf82a9b..4930d06904 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md @@ -12,11 +12,11 @@ children: - /filtering-projects - /managing-your-views allowTitleToDifferFromFilename: true -ms.openlocfilehash: c5a7f7f8aff5ab61a4711f6fbb30f64cf9fea002 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 10c4aaf54f90773acb1d7a9ed2a8dc186278010e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424177' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109030' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md index 1d088d8a7a..4989b89d22 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md @@ -7,12 +7,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: d434b4b086c1ec8526c3214161ac00d58dced4fd -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9b3d7f4b12210841a0c55f3b0b7356da9b225416 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424162' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109563' --- ## プロジェクトビューの作成 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md index bf31061a3e..27c380429f 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md @@ -19,11 +19,11 @@ children: allowTitleToDifferFromFilename: true redirect_from: - /issues/trying-out-the-new-projects-experience -ms.openlocfilehash: de9bdc87563e88ac945783bc8e98fd520dfb36ef -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 80a894cdca5dda3afff3476a8209cb54589c89b5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147425249' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109555' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md index 61e008d2ad..d189455973 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md @@ -10,12 +10,12 @@ redirect_from: type: overview topics: - Projects -ms.openlocfilehash: f50d54b95862102eafe97dcf1dfcec4daa1d7995 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 4de4e96b6e445a29377c63188f6529c5b2023a5e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424156' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109031' --- ## {% data variables.product.prodname_projects_v2 %} について diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index d427bed2f3..bc5b255031 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,10 +1,10 @@ --- title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' -intro: 'Learn tips for managing your projects.' +intro: Learn tips for managing your projects. allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: - feature: "projects-v2" + feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects type: overview diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md index 32a5d28e69..ad03814aee 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md @@ -11,11 +11,11 @@ children: - /quickstart-for-projects - /best-practices-for-projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 3bd91ba9dda01dd1dc567cde62336a86b3968260 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 3629a25866eb08c704ee857ef78140e356202337 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424153' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109024' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md index 19ea9a2d17..d61e693b56 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md @@ -10,12 +10,12 @@ redirect_from: type: quick_start topics: - Projects -ms.openlocfilehash: 165f12f1f76bcc571a7f7c47c33106bad2d6ff42 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 39798565419acaa831a996a0c86cc62f367f4bb7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424053' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109685' --- ## はじめに diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md index 7fc55bb88e..25daa92188 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -1,10 +1,10 @@ --- title: 'Adding items to your {% data variables.projects.project_v2 %}' -shortTitle: 'Adding items' +shortTitle: Adding items intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' miniTocMaxHeadingLevel: 4 versions: - feature: "projects-v2" + feature: projects-v2 type: tutorial topics: - Projects @@ -83,4 +83,4 @@ Draft issues can have a title, text body, assignees, and any custom fields from **Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue. -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md index d49c64ef7c..05edecb409 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -1,10 +1,10 @@ --- title: 'Archiving items from your {% data variables.projects.project_v2 %}' -shortTitle: 'Archiving items' +shortTitle: Archiving items intro: 'You can archive items, keeping them available to restore, or permanently delete them.' miniTocMaxHeadingLevel: 2 versions: - feature: "projects-v2" + feature: projects-v2 type: tutorial topics: - Projects @@ -45,4 +45,4 @@ You can delete an item to remove it from the project entirely. 1. Click **Delete from project**. ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) 1. When prompted, confirm your choice by clicking **Delete**. - ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) \ No newline at end of file + ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md index 11f90b26a3..fb8c138578 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md @@ -8,12 +8,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 22d80acf06957a3ab617e51d0051c75cf42db988 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6c956f5453941bdd6b9fbe89191737b1b7f59cec +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424029' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109019' --- ## テーブル レイアウトでのドラフト issue の変換 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md index 872628e18e..09e065fe6e 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md @@ -12,11 +12,11 @@ children: - /converting-draft-issues-to-issues - /archiving-items-from-your-project allowTitleToDifferFromFilename: true -ms.openlocfilehash: 76a77b3ba3cf61b37aaf2b23ae1117951d5b3105 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 99f64d6e5f4d9cb39771f1ef9f0fae42c36a8cb7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424020' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109680' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md index 07f84290c9..97a7a6a54a 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md @@ -9,12 +9,12 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 58739f4e548985729d01a962e67a12ea0c0b38e9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 30486f727a04ccea3b5bfd374a4da3c6367d1cb6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424152' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109679' --- リポジトリ中で、関連するプロジェクトをリストできます。 リストできるのは、リポジトリを所有している同じユーザもしくはOrganizationが所有しているプロジェクトだけです。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md index d190afd92d..066978afba 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md @@ -11,12 +11,12 @@ type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: a37980d4d19ca0392fab51dc7e99987e469d2c9a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: cfd4db85e8bd046e667b108c5c8d8c23102e0d29 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424071' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109674' --- ## プロジェクトの削除 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md index 0aa855634d..151af578fd 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md @@ -13,11 +13,11 @@ children: - /adding-your-project-to-a-repository - /adding-your-project-to-a-team allowTitleToDifferFromFilename: true -ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c7dd1657bae11e0f43895e946b5e20a209666363 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424047' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109018' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md index e5f823f24e..bda406771e 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md @@ -4,7 +4,7 @@ shortTitle: 'Managing {% data variables.projects.project_v2 %} access' intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.' miniTocMaxHeadingLevel: 3 versions: - feature: "projects-v2" + feature: projects-v2 redirect_from: - /issues/trying-out-the-new-projects-experience/managing-access-to-projects type: tutorial diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md index bd0a4b01d0..9ae363ad33 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md @@ -12,12 +12,12 @@ topics: - Projects allowTitleToDifferFromFilename: true permissions: Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions. -ms.openlocfilehash: 0fcd51dc996f28103179835f05fc74941eb1daee -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: fbe4f0943010129b14ace21f6071b99e1160053b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147854061' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109787' --- ## プロジェクトの可視性について diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md index ad7b151fba..ebc5e9fcd2 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md @@ -8,12 +8,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: e5cdcbdfbc2e51949c22c27fb1071b6e931ee59a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 7c3bc45c036e209e0be682c3b13b9dafcba17885 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424101' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109668' --- `YYYY-MM-DD` 形式 (`date:2022-07-01` など) を使用して、日付値をフィルター処理できます。 `>`、`>=`、`<`、`<=`、`..` などの演算子を使用することもできます。 たとえば、`date:>2022-07-01` や `date:2022-07-01..2022-07-31`す。 `@today` を指定して、フィルターで現在の日付を表すこともできます。 詳細については、[プロジェクトのフィルター処理](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)に関するページを参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md index 1c2290e33a..b13876acda 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md @@ -10,12 +10,12 @@ redirect_from: type: tutorial topics: - Projects -ms.openlocfilehash: fe0b02e356023880b03302de93a44273efd135a5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 93039327ab7075e0f79c9d5ae5d6652aa635a500 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424017' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109781' --- 繰り返しフィールドを作成して、アイテムを特定の繰り返し時間ブロックに関連づけることができます。 繰り返しは任意の長さに設定でき、休憩を含められ、名前と日付の範囲を変更するために個別に編集できます。 プロジェクトでは、繰り返しでグループ化を行い、今後の作業のバランスを視覚化し、フィルタを使って繰り返しの1つに焦点を当て、繰り返しで並べ替えできます。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md index 3bfb878685..ab50d84b6c 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md @@ -8,12 +8,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: 50251608201f6a5e199c235cb0c715449bc99882 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 1dfb11e43de04bd55f544a9fb97a0a9346a22d96 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424113' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109252' --- オプション (`fieldname:option` など) を指定して、単一選択フィールドでフィルター処理することができます。 オプションのコンマ区切りリスト (`fieldname:option,option` など) を指定して、複数の値をフィルター処理できます。 詳細については、[プロジェクトのフィルター処理](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)に関するページを参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md index 4ae2735fa7..f82adba43e 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md @@ -8,12 +8,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: d6ab274812f4f35ff4f6afa9e1e2139abf86dd54 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 2ef01bbd4ec13e37fdcd95e2a536e73c6da2304d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424145' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109267' --- テキスト フィールドを使用して、プロジェクトに注釈やその他のフリーフォーム テキストを含めることができます。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md index b7001731b6..ced1d25304 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md @@ -7,12 +7,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: c0e250a584d596377c5efaa15d06dacf943827a7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 2998d4d39a3ec5f59a649fe62fd15c974e1e7ff7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424132' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109259' --- {% data reusables.projects.project-settings %} 1. 削除するフィールドの名前をクリックします。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md index d22b655c23..9a340fb59d 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md @@ -15,11 +15,11 @@ children: - /renaming-fields - /deleting-fields allowTitleToDifferFromFilename: true -ms.openlocfilehash: 8b4f48ba1d55d81c571256f48334c54ce3a7e71d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: eaa9fe7d4dbd6b2c43d0ab2ad12faf173d6f571a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423999' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109013' --- diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md index 5b8c0001d7..e0d66c9b5b 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md @@ -7,12 +7,12 @@ versions: type: tutorial topics: - Projects -ms.openlocfilehash: ab1373e5bea18c01ba97f37a7e77441d0bb70422 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: a8e43cc14edf9dd0c6838d8f75839a2c0624a7a5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717550' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109097' --- {% data reusables.projects.project-settings %} 1. 名前を変更するフィールドの名前をクリックします。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md index 6f7fc9f4ac..96a1e4cb41 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md @@ -11,12 +11,12 @@ product: '{% data reusables.gated-features.historical-insights-for-projects %}' topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: a90ec5dfb6aa983b8ffe26c84c4ec6ad01b0471d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 89f93ace53547fccd69ffb7e6d7b666a6cb48991 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424014' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109096' --- {% ifversion fpt %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md index ca173e7237..6b25e43565 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md @@ -8,12 +8,12 @@ type: tutorial product: '{% data reusables.gated-features.historical-insights-for-projects %}' topics: - Projects -ms.openlocfilehash: 4fffa6ebd196419dc08de7abaf5d85349bd38737 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: dd8f97ac69beb90a511c36ddd0a51f0e16b2d4b3 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424144' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109091' --- {% ifversion fpt %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md index 7bcabb1d1a..277d446928 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md @@ -8,12 +8,12 @@ type: tutorial product: '{% data reusables.gated-features.historical-insights-for-projects %}' topics: - Projects -ms.openlocfilehash: 1f6a072676480b02bcfbd589f5d4e9011e8e8052 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c708476decfb76086f32d96d8fc1e085030ae37e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423996' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108977' --- {% data reusables.projects.access-insights %} 3. 左側のメニューで **[新しいグラフ]** をクリックします。 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 adbebde7ee..93e9451968 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 @@ -107,8 +107,8 @@ You can filter a repository's list of pull requests to find: - Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged - Pull requests that a reviewer has approved - Pull requests in which a reviewer has asked for changes -- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- Pull requests that someone has asked you directly to review{% endif %} +- Pull requests that you have reviewed +- Pull requests that someone has asked you directly to review - Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -168,7 +168,6 @@ With issue and pull request search terms, you can: - Filter issues and pull requests by label: `state:open type:issue label:"bug"` - Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} {% tip %} **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. @@ -176,7 +175,6 @@ With issue and pull request search terms, you can: - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`. {% endtip %} -{% endif %} For issues, you can also use search to: @@ -190,8 +188,8 @@ For pull requests, you can also use search to: - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` - Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` -- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} +- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me` - Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/docs` - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue` 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 5802070b3c..10b193cadf 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 @@ -1,6 +1,6 @@ --- title: Linking a pull request to an issue -intro: You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged. +intro: 'You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue - /articles/closing-issues-via-commit-message diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index bbb80dd102..b886081748 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -12,12 +12,12 @@ versions: topics: - Organizations - Teams -ms.openlocfilehash: 3780e309aa149de90a6871fbe236aac752c67d0b -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 +ms.openlocfilehash: 7412c38e647ddec33543bd04d38d813bf6a93c88 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147878795' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108976' --- ## Organizationについて 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 58f47d8e9d..bb75ec8494 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 @@ -70,12 +70,10 @@ You can enable or disable features for all repositories. {% ifversion ghec %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png) {% endif %} - {% ifversion ghes > 3.2 %} + {% ifversion ghes %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png) {% endif %} - {% ifversion ghes = 3.2 %} - !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png) - {% endif %} + {% ifversion ghae %} !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) @@ -108,17 +106,15 @@ You can enable or disable features for all repositories. {% ifversion fpt or ghec %} ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} - {% ifversion ghes > 3.2 %} + {% ifversion ghes %} ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} - {% ifversion ghes = 3.2 %} - ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) - {% endif %} + {% ifversion ghae %} ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png) {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies 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 8ab11cb17b..704456d6fe 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 @@ -42,16 +42,16 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% endif %}{% ifversion fpt or ghec %} | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.{% endif %}{% ifversion fpt or ghec %} | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |{% endif %}{% ifversion fpt or ghec %} -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %} | [`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_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.{% ifversion fpt or ghec or ghes %} | [`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)." | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | 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 %} | [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} | [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. | [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %} -| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %} +| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %} | [`hook`](#hook-category-actions) | Contains all activities related to webhooks. | [`integration_installation`](#integration_installation-category-actions) | Contains activities related to integrations installed in an account. | | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %} @@ -77,8 +77,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %} | [`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 %}{% ifversion 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 %}{% ifversion 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 %} +| [`repository_secret_scanning_custom_pattern`](#repository_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 %}{% ifversion secret-scanning-audit-log-custom-patterns %} +| [`repository_secret_scanning_push_protection`](#repository_secret_scanning_push_protection-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).{% 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 %}{% ifversion 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 %} @@ -253,7 +253,6 @@ 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 %} ### `dependabot_alerts` category actions | Action | Description @@ -267,9 +266,8 @@ An overview of some of the most common actions that are recorded as events in th |------------------|------------------- | `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." | `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. -{% endif %} -{% ifversion fpt or ghec or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes %} ### `dependabot_security_updates` category actions | Action | Description @@ -867,4 +865,4 @@ For more information, see "[Managing the publication of {% data variables.produc - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} {%- ifversion fpt or ghec %} - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} -{%- endif %} \ No newline at end of file +{%- endif %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md index afd77dd2cc..228294ab4c 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: 'Organization の {% data variables.product.prodname_project_v1 %} に外部コラボレーターを追加する' -intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、{% data variables.projects.projects_v1_board %} に外部コラボレーターを追加し、そのアクセス許可をカスタマイズできます。' +title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization' +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.' redirect_from: - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization @@ -14,18 +14,21 @@ topics: - Teams shortTitle: Add a collaborator allowTitleToDifferFromFilename: true -ms.openlocfilehash: 04a8728c1dc38937a00277316e162ead9acb0fef -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422949' --- + {% data reusables.projects.project_boards_old %} -外部コラボレーターは、Organization の明示的なメンバーではありませんが、Organization 内の {% data variables.projects.projects_v1_board %} に対するアクセス許可を持つユーザーです。 +An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization. -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} -9. [Search by username, full name or email address] (ユーザ名、フルネーム、メールアドレスでの検索) の下で、外部のコラボレータの名前、ユーザ名、{% data variables.product.prodname_dotcom %}メールを入力してください。 - ![Octocat のユーザー名が検索フィールドに入力されている [コラボレーター] セクション](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. + ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md index 149b54fe0a..1054ec6f24 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -22,11 +22,11 @@ children: - /removing-an-outside-collaborator-from-an-organization-project-board shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access' allowTitleToDifferFromFilename: true -ms.openlocfilehash: bde0cbf48426b968aae6326e3db7a66fe47fda16 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: ec3c6cdaffc23dcb4df631879d17ec1ca6c1d61b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422933' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108833' --- diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md index cdd3771833..c17aea1352 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -1,6 +1,6 @@ --- -title: 'Organization メンバーの {% data variables.product.prodname_project_v1 %} へのアクセスを管理する' -intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、すべての Organization メンバーの {% data variables.projects.projects_v1_board %} に対する既定のアクセス許可レベルを設定できます。' +title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members' +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.' redirect_from: - /articles/managing-access-to-a-project-board-for-organization-members - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members @@ -14,33 +14,33 @@ topics: - Teams shortTitle: Manage access for members allowTitleToDifferFromFilename: true -ms.openlocfilehash: fe9d8ebee09d4eb6278545b5561b9691a0468bf5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880783' --- + {% data reusables.projects.project_boards_old %} -既定では、Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者が特定の {% data variables.projects.projects_v1_boards %} に対して別のアクセス許可を設定しない限り、Organization メンバーは、その Organization の {% data variables.projects.projects_v1_boards %} に対する書き込みアクセス権が付与されます。 +By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}. -## Organization のすべてのメンバーに対して標準の権限レベルを設定する +## Setting a baseline permission level for all organization members {% tip %} -**ヒント:** Organization メンバーに、{% data variables.projects.projects_v1_board %} に対するより高いアクセス許可を付与できます。 詳細については、「[Organization のプロジェクト ボード権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endtip %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} -8. [Organization メンバーのアクセス許可] で、すべての Organization メンバーの基準の権限レベル (**読み取り**、**書き込み**、**管理者**、**なし** のいずれか) を選択します。 -![Organization のすべてのメンバーのプロジェクト ボードに対する基準の権限オプション](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) -9. **[保存]** をクリックします。 +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +8. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**. +![Baseline project board permission options for all organization members](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) +9. Click **Save**. -## 参考資料 +## Further reading -- 「[Organization の {% data variables.product.prodname_project_v1 %} への個人のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-project-board)」 -- 「[Organization の {% data variables.product.prodname_project_v1 %} への Team のアクセスを管理する](/articles/managing-team-access-to-an-organization-project-board)」 -- 「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」 +- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)" +- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md index ca6d14b31b..adaec974e3 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Organization の {% data variables.product.prodname_project_v1 %} への個人のアクセスを管理する' -intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、Organization が所有する {% data variables.projects.projects_v1_board %} への個々のメンバーのアクセス権を管理できます。' +title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}' +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.' redirect_from: - /articles/managing-an-individual-s-access-to-an-organization-project-board - /articles/managing-an-individuals-access-to-an-organization-project-board @@ -15,40 +15,57 @@ topics: - Teams shortTitle: Manage individual access allowTitleToDifferFromFilename: true -ms.openlocfilehash: 3fd77225e83df2124e8e026453b539f6961ff473 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422893' --- + {% data reusables.projects.project_boards_old %} {% note %} -**注:** {% data reusables.project-management.cascading-permissions %} 詳しい情報については、「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。 +**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." {% endnote %} -## {% data variables.projects.projects_v1_board %} へのアクセス権を Organization メンバーに付与する +## Giving an organization member access to a {% data variables.projects.projects_v1_board %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} -9. [Search by username, full name or email address] で、コラボレーターの名前、ユーザ名、または {% data variables.product.prodname_dotcom %} メールを入力します。 - ![Octocat のユーザー名が検索フィールドに入力されている [コラボレーター] セクション](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +9. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email. + ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png) +{% data reusables.project-management.add-collaborator %} +{% data reusables.project-management.collaborator-permissions %} -## {% data variables.projects.projects_v1_board %} への Organization メンバーのアクセス権を変更する +## Changing an organization member's access to a {% data variables.projects.projects_v1_board %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.collaborator-permissions %} -## {% data variables.projects.projects_v1_board %} への Organization メンバーのアクセス権を削除する +## Removing an organization member's access to a {% data variables.projects.projects_v1_board %} -コラボレーターを {% data variables.projects.projects_v1_board %} から削除しても、コラボレーターは引き続き他のロールに対するアクセス許可に基づいてボードにアクセスできる場合があります。 {% data variables.projects.projects_v1_board %} へのアクセス権を完全に削除するには、そのユーザーが持つ各ロールのアクセス権を削除する必要があります。 たとえば、ユーザーは、Organization メンバーまたは Team メンバーとして {% data variables.projects.projects_v1_board %} にアクセスできます。 詳しい情報については、「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。 +When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.remove-collaborator %} -## 参考資料 +## Further reading -- 「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」 +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index 522bc91b7a..30b1dbf759 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -1,5 +1,5 @@ --- -title: Managing team access to an organization {% data variables.product.prodname_project_v1 %} +title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}' intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.' redirect_from: - /articles/managing-team-access-to-an-organization-project-board @@ -68,4 +68,4 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher - [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md index 09991aca0d..fb33b5a98b 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Organization の {% data variables.product.prodname_project_v1 %} から外部コラボレーターを削除する' -intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、{% data variables.projects.projects_v1_board %} への外部コラボレーターのアクセス権を削除できます。' +title: 'Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}' +intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.' redirect_from: - /articles/removing-an-outside-collaborator-from-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board @@ -14,14 +14,16 @@ topics: - Teams shortTitle: Remove outside collaborator allowTitleToDifferFromFilename: true -ms.openlocfilehash: 2dfcc372565366328820e968d6c6384f97b0e2c1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884198' --- + {% data reusables.projects.project_boards_old %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} -1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %} +1. Click **Projects (classic)**{% endif %} +{% data reusables.project-management.select-project %} +{% data reusables.project-management.click-menu %} +{% data reusables.project-management.access-collaboration-settings %} +{% data reusables.project-management.collaborator-option %} +{% data reusables.project-management.remove-collaborator %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md index 1054ccf40e..5e485b33cf 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md @@ -9,12 +9,12 @@ topics: shortTitle: Project visibility permissions allowTitleToDifferFromFilename: true permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.' -ms.openlocfilehash: 784b0f35ff86a1a2620a0c96d4e951a8ca28e136 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 5f8963e8c03e2c0a62586964b6331ec7b3d945b5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147854085' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109539' --- ## プロジェクトの可視性の変更について diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md index e0536d2906..60d34b7621 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md @@ -8,12 +8,12 @@ topics: - Projects shortTitle: 'Disable {% data variables.product.prodname_projects_v2 %} insights' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 06ab0f550603e3810bf860f01efe9113766c0fb3 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 80a35ea28d90b89c39fb7f9207b2ea950a98a8b6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147424083' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108832' --- Organization 内のプロジェクトの分析情報を無効にした後、Organization が所有するプロジェクトの分析情報にアクセスできなくなります。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md index c3e16e92ab..8996d8f20e 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/index.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md @@ -45,11 +45,11 @@ children: - /disabling-insights-for-projects-in-your-organization - /allowing-project-visibility-changes-in-your-organization shortTitle: Manage organization settings -ms.openlocfilehash: 5e89284314ef4f1125ff4ca0843031326e378b0b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d19c515ac3d908df15afd8c5741553f7526a6f99 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424745' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148008712' --- {% ifversion fpt or ghec %} {% endif %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md index 3e9cacd22c..25ed41ec30 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md @@ -1,29 +1,26 @@ --- -title: Organization のコミット サインオフ ポリシーの管理 -intro: 'Organization が所有するリポジトリへの {% data variables.product.product_name %} の Web インターフェイスでユーザーが行ったすべてのコミットを、自動的にサインオフするように要求できます。' +title: Managing the commit signoff policy for your organization +intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.' versions: feature: commit-signoffs permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author. topics: - Organizations shortTitle: Manage the commit signoff policy -ms.openlocfilehash: 0d4f2a0fae7db59a7a1f5d8646263e965e9be9ef -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409825' --- -## コミットのサインオフについて -コミットがリポジトリを管理するルールとライセンスに準拠していることを確認するために、多くの Organization では、開発者がすべてのコミットをサインオフする必要があります。 Organization でコミットのサインオフが必要な場合は、{% data variables.product.product_name %} の Web インターフェイスを介してコミットするユーザーに対して強制コミット サインオフを有効にすることで、コミット プロセスのシームレスな部分をサインオフできます。 Organization の強制コミット サインオフを有効にした後、{% data variables.product.product_name %} の Web インターフェイスを介してその Organization 内のリポジトリに対して行われたすべてのコミットは、コミット作成者によって自動的にサインオフされます。 +## About commit signoffs -リポジトリへの管理者アクセス権を持つユーザーは、リポジトリ レベルで強制コミット サインオフを有効にすることもできます。 詳しくは、「[リポジトリのコミット サインオフ ポリシーの管理](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)」を参照してください。 +To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author. + +People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." {% data reusables.repositories.commit-signoffs %} -## Organization の強制コミット サインオフの管理 +## Managing compulsory commit signoffs for your organization -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %} -1. **[共同作成者に Web ベースのコミットのサインオフを要求する]** を選択または選択解除します。 - ![[共同作成者に Web ベースのコミットのサインオフを要求する] のスクリーンショット](/assets/images/help/organizations/require-signoffs.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.repository-defaults %} +1. Select or deselect **Require contributors to sign off on web-based commits**. + ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png) diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md index ed25ce1f3e..43c2116721 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -1,6 +1,6 @@ --- -title: 外部のコラボレーターを追加するための権限を設定する -intro: Organization のデータを保護し、Organization 内で使用されている有料ライセンスの数が無駄遣いされないようにするために、外部コラボレーターを Organization のリポジトリに追加できる人を構成できます。 +title: Setting permissions for adding outside collaborators +intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can configure who can add outside collaborators to organization repositories.' redirect_from: - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories - /articles/setting-permissions-for-adding-outside-collaborators @@ -13,28 +13,25 @@ topics: - Organizations - Teams shortTitle: Set collaborator policy -ms.openlocfilehash: eadf4f805775a99f763ec4df211fe6ea9735dabc -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145119245' --- -デフォルトでは、リポジトリへの管理アクセスを持つ人は、そのリポジトリで作業してもらうために外部のコラボレータを招待できます。 外部のコラボレータを追加する機能は、Organizationのオーナーのみに制限することもできます。 -{% ifversion ghec %} {% note %} +By default, anyone with admin access to a repository can invite outside collaborators to work on the repository. You can choose to restrict the ability to add outside collaborators to organization owners only. -**注:** {% data variables.product.prodname_ghe_cloud %} を使う Organization だけが、外部のコラボレータを招待する機能を Organization のオーナーに制限できます。 {% data reusables.enterprise.link-to-ghec-trial %} +{% ifversion ghec %} +{% note %} -{% endnote %} {% endif %} +**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite outside collaborators to organization owners. {% data reusables.enterprise.link-to-ghec-trial %} -{% ifversion ghec %}Organization がエンタープライズアカウントによって所有されているとき、{% else %}{% endif %}エンタープライズ所有者がエンタープライズレベルでポリシーを設定している場合、Organization にこの設定を構成できないことがあります。 詳しくは、「Enterprise でリポジトリ管理ポリシーを適用する{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}」を参照してください。 +{% endnote %} +{% endif %} + +{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}." {% data reusables.organizations.outside-collaborators-use-seats %} -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %}{% ifversion ghes < 3.3 %} -5. [リポジトリ招待] の下で、 **[この Organization のリポジトリに外部コラボレータを招待することをメンバーに許可する]** を選択します。 - ![外部コラボレータを Organization リポジトリに招待することをメンバーに許可するためのチェックボックス](/assets/images/help/organizations/repo-invitations-checkbox-old.png){% else %} -5. [リポジトリの外部コラボレータ] で **[この Organization のリポジトリに外部コラボレータを招待することをリポジトリ管理者に許可する]** の選択を解除します。 - ![外部コラボレータを Organization リポジトリに招待することをリポジトリ管理者に許可するためのチェックボックス](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% endif %} -6. **[保存]** をクリックします。 +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository outside collaborators", deselect **Allow repository administrators to invite outside collaborators to repositories for this organization**. + ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png) +6. Click **Save**. 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 52f83adc9b..6e30cf02ec 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 @@ -15,12 +15,12 @@ topics: - Organizations - Teams shortTitle: Roles in an organization -ms.openlocfilehash: d8d07ff40026de0d12fce2e11479c424b781680a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 960f6f701ad524220e9e79ada04fa9e4d30b8e9f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061739' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108803' --- ## ロールについて {% data reusables.organizations.about-roles %} @@ -142,7 +142,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ | Team 同期を有効にする (「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照) | **X** | | | | |{% 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 %} +{% elsif ghes or ghae %} | Organization のアクション | 所有者 | メンバー | セキュリティマネージャー | @@ -167,7 +167,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ | "*チーム メンテナ*" に指定できる | **X** | **X** | **X** | | リポジトリを移譲する | **X** | | | | セキュリティと分析の設定を管理する (「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | **X** |{% ifversion ghes %} -| Organization のセキュリティの概要を表示する (「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %} +| Organization のセキュリティの概要を表示する (「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照) | **X** | | **X** |{% endif %}{% ifversion ghes %} | {% data variables.product.prodname_dependabot_security_updates %} を管理する (「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照) | **X** | | **X** |{% endif %} | Organization の SSH 認証局を管理する (「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** | | | | プロジェクト ボードを作成する (「[Organization のプロジェクト ボード権限](/articles/project-board-permissions-for-an-organization)」を参照) | **X** | **X** | **X** | diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index a6056acced..b0a8576c06 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -20,10 +20,12 @@ shortTitle: IAM with SAML SSO {% data reusables.saml.saml-accounts %} -Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." +{% data reusables.saml.resources-without-sso %} {% data reusables.saml.outside-collaborators-exemption %} +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." + Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md index c38eff7ab0..1a08195f35 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md @@ -9,12 +9,12 @@ topics: shortTitle: Troubleshooting access redirect_from: - /organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management -ms.openlocfilehash: 41a629c9cff075e06e31d186a4a4edf7eebd96d2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d3110d61fb511f55aa840d0911c036dd342fa833 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147093201' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148106974' --- {% data reusables.saml.current-time-earlier-than-notbefore-condition %} @@ -84,7 +84,7 @@ SCIM REST APIは、外部アイデンティティの下でSCIMメタデータが ``` ```shell -curl -X POST -H "Authorization: Bearer " -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username} user { login } } } } } } }" }' https://api.github.com/graphql +curl -X POST -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username} user { login } } } } } } }" }' https://api.github.com/graphql ``` GraphQL APIの利用に関する詳しい情報については、以下を参照してください。 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md index afbb13b86e..a577717cf0 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md @@ -86,7 +86,7 @@ Any team members that have set their status to "Busy" will not be selected for r {% ifversion ghes < 3.4 %} 1. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** {%- endif %} -{% ifversion fpt or ghec or ghae > 3.3 or ghes > 3.2 %} +{% ifversion fpt or ghec or ghes or ghae > 3.3 %} 1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. 1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. 1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**. diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md index 400f954e6d..0fe78be916 100644 --- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md +++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghec: '*' - feature: 'docker-ghcr-enterprise-migration' + feature: docker-ghcr-enterprise-migration shortTitle: Migration to Container registry topics: - Containers diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index f17d1a1b94..e687fd7b2b 100644 --- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re {% endif %} ```shell "publishConfig": { - "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" }, ``` {% ifversion ghes %} If your instance has subdomain isolation disabled: ```shell "publishConfig": { - "registry":"https://HOSTNAME/_registry/npm/" + "registry": "https://HOSTNAME/_registry/npm/" }, ``` {% endif %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md index b1e2bcecad..907b514a06 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md @@ -24,11 +24,11 @@ children: - /using-submodules-with-github-pages - /unpublishing-a-github-pages-site shortTitle: Get started -ms.openlocfilehash: 7e9d3b9bb171a596b84b814eac52d4c5d22134de -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 4945585f635543fefe2f60de2f82b49bf4d10e84 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147643878' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109268' --- diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md index b0e56e98b1..bdaf20e577 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,6 +1,6 @@ --- -title: GitHub Pages サイトを取り下げる -intro: '{% data variables.product.prodname_pages %} サイトを取り下げて、サイトを利用不可にすることができます。' +title: Unpublishing a GitHub Pages site +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - /articles/how-do-i-unpublish-a-project-page - /articles/unpublishing-a-project-page @@ -18,38 +18,35 @@ versions: topics: - Pages shortTitle: Unpublish Pages site -ms.openlocfilehash: fbfec49ec44c250e5f6cb2da85fda59261c1d0d9 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147428349' --- + {% ifversion pages-custom-workflow %} -自分のサイトを非公開にすると、そのサイトは利用不可になります。 既存のリポジトリ設定またはコンテンツが、影響を受けることはありません。 +When you unpublish your site, the site will no longer be available. Any existing repository settings or content will not be affected. {% data reusables.repositories.navigate-to-repo %} -1. **{% data variables.product.prodname_pages %}** の下で、**サイトがライブになっている場所** に関するメッセージの横にある、[{% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}] をクリックします。 -1. 表示されるメニューで、 **[サイトを取り下げる]** を選びます。 +1. Under **{% data variables.product.prodname_pages %}**, next to the **Your site is live at** message, click {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}. +1. In the menu that appears, select **Unpublish site**. - ![サイトを取り下げるためのドロップ ダウン メニュー](/assets/images/help/pages/unpublish-site.png) + ![Drop down menu to unpublish site](/assets/images/help/pages/unpublish-site.png) {% else %} -## プロジェクトサイトを取り下げる +## Unpublishing a project site {% data reusables.repositories.navigate-to-repo %} -2. リポジトリに `gh-pages` ブランチが存在する場合は、`gh-pages` ブランチを削除します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」を参照してください。 -3. `gh-pages` ブランチが公開ソースの場合、{% ifversion fpt or ghec %}手順 6 に進みます{% else %}サイトは公開されていません。残りの手順はスキップできます{% endif %}。 -{% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -5. "{% data variables.product.prodname_pages %}" で、 **[Source]\(ソース\)** ドロップダウン メニューを使用し、 **[None]\(なし\)** を選択します。 - ![公開ソースを選択するためのドロップダウン メニュー](/assets/images/help/pages/publishing-source-drop-down.png) {% data reusables.pages.update_your_dns_settings %} +2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)." +3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.** + ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +{% data reusables.pages.update_your_dns_settings %} -## ユーザまたは Organization サイトを取り下げる +## Unpublishing a user or organization site {% data reusables.repositories.navigate-to-repo %} -2. 公開元として使用しているブランチを削除するか、リポジトリ全体を削除します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」と「[リポジトリを削除する](/articles/deleting-a-repository)」を参照してください。 +2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)." {% data reusables.pages.update_your_dns_settings %} {% endif %} diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md index 5c8d0c692f..19adbee123 100644 --- a/translations/ja-JP/content/pages/index.md +++ b/translations/ja-JP/content/pages/index.md @@ -50,3 +50,4 @@ children: - /setting-up-a-github-pages-site-with-jekyll - /configuring-a-custom-domain-for-your-github-pages-site --- + 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 5ecd5f08d3..141f27d805 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 @@ -22,8 +22,6 @@ shortTitle: Review dependency changes --- -{% data reusables.dependency-review.beta %} - ## About dependency review {% data reusables.dependency-review.feature-overview %} diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 922f9dbb84..32a3feaa26 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -65,8 +65,6 @@ For more information on reviewing pull requests in {% data variables.product.pro {% ifversion fpt or ghes or ghec %} ## Reviewing dependency changes -{% data reusables.dependency-review.beta %} - If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." {% data reusables.repositories.changed-files %} diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index ae7c873c86..a2808b957d 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -95,7 +95,7 @@ Optionally, you can require approvals from someone other than the last person to Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)." -Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/commits#commit-statuses)" in the REST documentation. +Before you can enable required status checks, you must configure the repository to use the commit status API. For more information, see "[Commit statuses](/rest/commits/statuses)" in the REST API documentation. After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch. @@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`. {% endif %} -You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch or create a matching branch. +You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}. ### Allow force pushes diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md index 014c709c08..04007167b4 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -78,6 +78,14 @@ People with admin permissions for a repository can change an existing repository {% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +{% ifversion ghec %} +{% note %} + +**Note:** You can only create internal repositories if you use {% data variables.product.prodname_ghe_cloud %} with an enterprise account. An enterprise account is a separate type of account that allows a central point of management for multiple organizations. For more information, see "[Types of {% data variables.product.prodname_dotcom %} account](/get-started/learning-about-github/types-of-github-accounts)." + +{% endnote %} +{% endif %} + All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." {% ifversion ghes %} diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index dff4c98d4d..ca7dd28f84 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc $ git remote set-url origin NEW_URL ``` + {% warning %} + + **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work. + + {% endwarning %} + - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %} - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index b3a5dbf23b..77460dc0f2 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -5,17 +5,17 @@ redirect_from: - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files versions: fpt: '*' - ghes: '>=3.3' + ghes: '*' ghae: '*' ghec: '*' topics: - Repositories -ms.openlocfilehash: 2f7869e9218679c3c18c3182b15835bcd24e134d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 96e5e7308ba5d1877f231dcb454d7b797a63f221 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145193803' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108971' --- ## CITATION ファイルについて diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 343a994c1e..d3212418a8 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -37,13 +37,11 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. -{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ## CODEOWNERS file size CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. -{% endif %} ## CODEOWNERS syntax @@ -129,7 +127,6 @@ apps/ @octocat ## CODEOWNERS and branch protection Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." - ## Further reading - "[Creating new files](/articles/creating-new-files)" diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index 03bfb1040b..7de402dfc0 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -17,7 +17,7 @@ topics: --- ## About READMEs -You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. +You can add a README file to a repository to communicate important information about your project. A README, along with a repository license, citation file{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." @@ -66,4 +66,4 @@ A README should contain only the necessary information for developers to get sta - 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" {%- ifversion fpt or ghec %} - "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)" -{%- endif %} \ No newline at end of file +{%- endif %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index c939fb420e..0227ac595d 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -1,6 +1,6 @@ --- -title: トピックでリポジトリを分類する -intro: あなたのプロジェクトを他の人が見つけて貢献しやすくするために、プロジェクトの目的、分野、主催グループなどの、リポジトリに関するトピックを追加できます。 +title: Classifying your repository with topics +intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.' redirect_from: - /articles/about-topics - /articles/classifying-your-repository-with-topics @@ -14,35 +14,36 @@ versions: topics: - Repositories shortTitle: Classify with topics -ms.openlocfilehash: 68bd754ac6c50968961c61e533cb6b9de26e4cc4 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: '145132235' --- -## Topics について -Topics を利用すれば、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを見つけたり、特定の問題に対する新たなソリューションを見つけ出すことができます。 Topics は、リポジトリのメインページに表示されます。 トピック名をクリックして、{% ifversion fpt or ghec %}関連するトピックや、そのトピックに分類される他のリポジトリのリストを見たりすることができます。{% else %}そのトピックの他のリポジトリを検索することができます。{% endif %} +## About topics -![Topics を表示しているテストリポジトリのメインページ](/assets/images/help/repository/os-repo-with-topics.png) +With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}. -最も使われているトピックを参照するには、 https://github.com/topics/ にアクセスします。 +![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png) -{% ifversion fpt or ghec %}[github/explore](https://github.com/github/explore) リポジトリにある {% data variables.product.product_name %} の注目のトピックのセットにコントリビュートできます。 {% endif %} +To browse the most used topics, go to https://github.com/topics/. -リポジトリの管理者は、リポジトリに好きなトピックを追加できます。 リポジトリを分類するのに役立つトピックには、そのリポジトリの意図する目的、主題の領域、コミュニティ、言語などがあります。{% ifversion fpt or ghec %}加えて、{% data variables.product.product_name %} はパブリックなリポジトリの内容を分析し、推奨されるトピックを生成します。リポジトリの管理者は、これを受諾することも拒否することもできます。 プライベートリポジトリの内容は分析されず、Topics が推奨されることはありません。{% endif %} +{% ifversion fpt or ghec %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %} -{% ifversion fpt %}パブリックとプライベート{% elsif ghec or ghes %}パブリック、プライベート、内部{% elsif ghae %}プライベートと内部{% endif %}のリポジトリにはトピックを含めることができますが、トピック検索結果にはアクセスできるプライベート リポジトリのみが表示されます。 +Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %} -特定のトピックに関連付けられているリポジトリを検索できます。 詳細については、「[リポジトリを検索する](/search-github/searching-on-github/searching-for-repositories#search-by-topic)」を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳しくは、「[トピックを検索する](/search-github/searching-on-github/searching-topics)」をご覧ください。 +{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results. -## Topics をリポジトリに追加する +You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)." + +## Adding topics to your repository + +{% note %} + +**Note:** Topic names are always public, even if you create the topic from within a private repository. + +{% endnote %} {% data reusables.repositories.navigate-to-repo %} -2. [バージョン情報] の右側にある {% octicon "gear" aria-label="The Gear icon" %} をクリックします。 - ![リポジトリのメイン ページにある歯車アイコン](/assets/images/help/repository/edit-repository-details-gear.png) -3. [Topics] で、リポジトリに追加するトピックを入力してから、スペースを入力します。 - ![トピックの入力フォーム](/assets/images/help/repository/add-topic-form.png) -4. トピックの追加が終わったら、 **[変更の保存]** をクリックします。 - ![[リポジトリの詳細の編集] の [変更の保存] ボタン](/assets/images/help/repository/edit-repository-details-save-changes-button.png) +2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}. + ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png) +3. Under "Topics", type the topic you want to add to your repository, then type a space. + ![Form to enter topics](/assets/images/help/repository/add-topic-form.png) +4. After you've finished adding topics, click **Save changes**. + !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png) diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md index 1d38c1ac93..0b6d9e77db 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md @@ -15,12 +15,12 @@ topics: - Pull requests shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}' allowTitleToDifferFromFilename: true -ms.openlocfilehash: 0407d6df39ae664474aa3fb5c99dc7998df1b951 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 8c550cd9ebc767327298e39dc0b3a6a11368dc3f +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147422661' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109524' --- {% data variables.projects.projects_v1_boards %} を無効にすると、タイムラインや[監査ログ](/articles/reviewing-your-security-log/)に {% data variables.projects.projects_v1_board %} の情報が表示されなくなります。 diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md index 3bc55f4486..1cbb6dffab 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md @@ -50,8 +50,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g {% ifversion fpt or ghes or ghec %} 4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% endif %}{% ifversion fpt %} ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %} - ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.6 or ghae > 3.6 %}{% elsif ghes = 3.2 %} - ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/repository/security-and-analysis-disable-or-enable-ghes.png){% else %} + ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.6 or ghae > 3.6 %} ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} {% ifversion not fpt %} @@ -81,23 +80,19 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %} 4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. - {% ifversion fpt or ghec or ghes > 3.2 %} + {% ifversion fpt or ghec or ghes %} ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) {% endif %} - {% ifversion ghes < 3.3 %} - ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png) - {% endif %} + {% ifversion ghae %} ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png) {% endif %} 5. Click **Save changes**. - {% ifversion fpt or ghes > 3.2 or ghec %} + {% ifversion fpt or ghes or ghec %} !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) {% endif %} - {% ifversion ghes < 3.3 %} - !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png) - {% endif %} + {% ifversion ghae %} !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png) {% endif %} @@ -108,12 +103,10 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %} 4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. - {% ifversion fpt or ghec or ghes > 3.2 %} + {% ifversion fpt or ghec or ghes %} !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) {% endif %} - {% ifversion ghes < 3.3 %} - !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png) - {% endif %} + {% ifversion ghae %} !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png) {% endif %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md index 188b4b10dc..941d10d1b0 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md @@ -1,6 +1,6 @@ --- title: Managing the commit signoff policy for your repository -intro: You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}'s web interface. +intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.' versions: feature: commit-signoffs permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author. @@ -22,4 +22,4 @@ Organization owners can also enable compulsory commit signoffs at the organizati {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 1. Select **Require contributors to sign off on web-based commits**. - ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png) \ No newline at end of file + ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png) diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index d01f6e8e7a..832a7ae04f 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -39,22 +39,19 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da 1. Click **Draft a new release**. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %} -1. {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae %}, and press **Enter**{% endif %}. Alternatively, select an existing tag. +1. Click **Choose a tag**, type a version number for your release, and press **Enter**. Alternatively, select an existing tag. - {% ifversion fpt or ghec or ghes > 3.2 or ghae %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png) + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) 1. If you are creating a new tag, click **Create new tag**. ![Screenshot of confirming you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) - {% else %} - ![Screenshot of the Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) -{% endif %} + 1. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. - {% ifversion fpt or ghec or ghes > 3.2 or ghae %} + ![Screenshot of dropdown to choose a branch](/assets/images/help/releases/releases-choose-branch.png) - {% else %} - ![Screenshot of the Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %} + {%- data reusables.releases.previous-release-tag %} 1. Type a title and description for your release. @@ -90,7 +87,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da 1. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) - {%- ifversion fpt or ghec or ghes > 3.2 or ghae > 3.3 %} + {%- ifversion fpt or ghec or ghae > 3.3 %} You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Screenshot of your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)." {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %} diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index 7fd76aff9f..b910f68b66 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -6,16 +6,16 @@ shortTitle: Searching releases versions: fpt: '*' ghec: '*' - ghes: '>3.2' + ghes: '*' ghae: '>= 3.4' topics: - Repositories -ms.openlocfilehash: 193363cc5762db6cb030906a64dacb7bab6f5b7a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a61e49521452befdcddf2724cad837062c7d54a1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066187' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109652' --- ## リポジトリ内のリリースの検索 diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 5dd1df54fe..d8ad87c848 100644 --- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -199,14 +199,10 @@ You can click {% octicon "file" aria-label="The paper icon" %} to see the change ![Rendered Prose changes](/assets/images/help/repository/rendered_prose_changes.png) -{% ifversion fpt or ghes > 3.2 or ghae or ghec %} - ### Disabling Markdown rendering {% data reusables.repositories.disabling-markdown-rendering %} -{% endif %} - ### Visualizing attribute changes We provide a tooltip diff --git a/translations/ja-JP/content/rest/deployments/branch-policies.md b/translations/ja-JP/content/rest/deployments/branch-policies.md index 77b8636e5d..07177ff285 100644 --- a/translations/ja-JP/content/rest/deployments/branch-policies.md +++ b/translations/ja-JP/content/rest/deployments/branch-policies.md @@ -11,12 +11,12 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 70f5d05f0a28e9fa21bf7bc99abbac6bd4a6509a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 109bf81019d62e4c654ba6da4fa71f8fd359ceb4 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147549127' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109595' --- ## デプロイ ブランチ ポリシー API について diff --git a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md index 33ca7acbfc..f5f5ec12fb 100644 --- a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md +++ b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md @@ -2,7 +2,7 @@ title: Audit log intro: '' versions: - ghes: '>=3.3' + ghes: '*' ghec: '*' ghae: '*' topics: diff --git a/translations/ja-JP/content/rest/enterprise-admin/scim.md b/translations/ja-JP/content/rest/enterprise-admin/scim.md index 05b64bf796..5f0be8c0ba 100644 --- a/translations/ja-JP/content/rest/enterprise-admin/scim.md +++ b/translations/ja-JP/content/rest/enterprise-admin/scim.md @@ -1,6 +1,6 @@ --- title: SCIM -intro: 'You can automate user creation and team memberships using the SCIM API.' +intro: You can automate user creation and team memberships using the SCIM API. versions: ghes: '>=3.6' topics: diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md index 6fa7bcc827..9ec7f2ffc9 100644 --- a/translations/ja-JP/content/rest/overview/api-previews.md +++ b/translations/ja-JP/content/rest/overview/api-previews.md @@ -1,203 +1,29 @@ --- -title: API プレビュー -intro: API プレビューを使用して新機能を試し、これらの機能が正式なものになる前にフィードバックを提供できます。 +title: API previews +intro: You can use API previews to try out new features and provide feedback before these features become official. redirect_from: - /v3/previews versions: ghes: <3.4 topics: - API -ms.openlocfilehash: fe00e2ab78881edab8d0f7704f80f2f20163fdeb -ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147878439' --- -API プレビューを使用すると、正式に GitHub API の一部になる前に、新しい API や既存の API メソッドへの変更を試すことができます。 -プレビュー期間中は、開発者からのフィードバックに基づいて機能を変更することがあります。 変更を行う際には、事前の通知なく[開発者ブログ](https://developer.github.com/changes/)で発表します。 -API プレビューにアクセスするには、自分の要求の `Accept` ヘッダーにカスタムの[メディアの種類](/rest/overview/media-types)を指定する必要があります。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 +API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API. -{% ifversion ghes < 3.3 %} +During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice. -## 強化されたデプロイメント - -より多くの情報と細かい粒度で[デプロイ](/rest/reference/repos#deployments)をより細かく制御します。 - -**カスタムのメディアの種類:** `ant-man-preview` -**発表日:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## リアクション - -コミット、問題、コメントの[リアクション](/rest/reference/reactions)を管理します。 - -**カスタムのメディアの種類:** `squirrel-girl-preview` -**発表:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) -**更新:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## タイムライン - -問題または pull request の[イベントの一覧](/rest/reference/issues#timeline)を取得します。 - -**カスタムのメディアの種類:** `mockingbird-preview` -**発表日:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) - -{% endif %} - -{% ifversion ghes < 3.3 %} -## プロジェクト - -[プロジェクト](/rest/reference/projects)を管理します。 - -**カスタムのメディアの種類:** `inertia-preview` -**発表:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) -**更新:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) {% endif %} {% ifversion ghes < 3.3 %} - -## コミット検索 - -[コミットを検索します](/rest/reference/search)。 - -**カスタムのメディアの種類:** `cloak-preview` -**発表:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% endif %} {% ifversion ghes < 3.3 %} - -## リポジトリトピック - -リポジトリの結果を返す[呼び出し](/articles/about-topics/)で[リポジトリ トピック](/rest/reference/repos)の一覧を表示します。 - -**カスタムのメディアの種類:** `mercy-preview` -**発表:** [2017-01-31](https://github.com/blog/2309-introducing-topics) {% endif %} {% ifversion ghes < 3.3 %} - -## 行動規範 - -すべての[行動規範](/rest/reference/codes-of-conduct)を表示するか、リポジトリに現在含まれる行動規範を取得します。 - -**カスタムのメディアの種類:** `scarlet-witch-preview` - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## グローバル webhook - -[組織](/webhooks/event-payloads/#organization)と[ユーザー](/webhooks/event-payloads/#user)のイベントの種類に対して[グローバル Webhook](/rest/reference/enterprise-admin#global-webhooks/) を有効にします。 この API プレビューは {% data variables.product.prodname_ghe_server %} でのみ使用できます。 - -**カスタムのメディアの種類:** `superpro-preview` -**発表日:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## 署名済みコミットの必須化 - -これで、API を使用して、[保護されたブランチで署名済みコミットを必須にする](/rest/reference/repos#branches)ための設定を管理できるようになりました。 - -**カスタムのメディアの種類:** `zzzax-preview` -**発表:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) {% endif %} {% ifversion ghes < 3.3 %} - -## 複数の承認レビューの必須化 - -API を使用することで、pull request に対して[複数の承認レビューを要求](/rest/reference/repos#branches)できるようになりました。 - -**カスタムのメディアの種類:** `luke-cage-preview` -**発表日:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## プロジェクトカードの詳細 - -[issue イベント](/rest/reference/issues#events)と [issue タイムライン イベント](/rest/reference/issues#timeline) の REST API 応答から、プロジェクト関連のイベントの `project_card` フィールドが返されるようになりました。 - -**カスタムのメディアの種類:** `starfox-preview` -**発表日:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## デプロイメントステータス - -これで、[デプロイ状態](/rest/reference/deployments#create-a-deployment-status)の `environment` を更新し、`in_progress` と `queued` の状態を使用できるようになりました。 デプロイの状態を作成する際に、`auto_inactive` パラメーターを使用して古い `production` デプロイを `inactive` として使用できるようになりました。 - -**カスタムのメディアの種類:** `flash-preview` -**発表日:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## リポジトリの作成権限 - -Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、[組織の更新](/rest/reference/orgs#update-an-organization)に関するページを参照してください。 - -**カスタムのメディアの種類:** `surtur-preview` -**発表:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) - -{% endif %} +To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. {% ifversion ghes < 3.4 %} -## コンテンツの添付 +## Content attachments -{% data variables.product.prodname_unfurls %} API を使用して、登録されたドメインにリンクする URL の詳細情報を GitHub で提供できるようになりました。 詳細については、「[添付コンテンツを使用する](/apps/using-content-attachments/)」を参照してください。 +You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details. -**カスタムのメディアの種類:** `corsair-preview` -**発表:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) - -{% endif %} {% ifversion ghes < 3.3 %} - -## Pages の有効化と無効化 - -[Pages API](/rest/reference/repos#pages) の新しいエンドポイントを使用して、Pages を有効または無効にすることができます。 Pages の詳細については、[GitHub Pages の基本](/categories/github-pages-basics)に関するページを参照してください。 - -**カスタムのメディアの種類:** `switcheroo-preview` -**発表:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +**Custom media types:** `corsair-preview` +**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) {% endif %} -{% ifversion ghes < 3.3 %} -## コミットのブランチまたはプルリクエストの一覧表示 - -[Commits API](/rest/reference/repos#commits) で 2 つの新しいエンドポイントを使用して、コミットのブランチまたは pull requests を一覧表示できます。 - -**カスタムのメディアの種類:** `groot-preview` -**発表:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) - -{% endif %} - -{% ifversion ghes < 3.3 %} - -## プルリクエストブランチの更新 - -新しいエンドポイントを使用することで、アップストリーム ブランチの HEAD からの変更で [pull request ブランチを更新](/rest/reference/pulls#update-a-pull-request-branch)することができます。 - -**カスタムのメディアの種類:** `lydian-preview` -**発表:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) - -{% endif %} {% ifversion ghes < 3.3 %} - -## リポジトリテンプレートの作成および使用 - -新しいエンドポイントを使用すると、[テンプレートを使用してリポジトリを作成](/rest/reference/repos#create-a-repository-using-a-template)したり、`is_template` パラメーターを `true` に設定して[認証済みユーザー用のリポジトリを作成](/rest/reference/repos#create-a-repository-for-the-authenticated-user)したりできます。 [リポジトリを取得](/rest/reference/repos#get-a-repository)することで、`is_template` キーを使用してそれがテンプレート リポジトリとして設定されているかどうかを確認できます。 - -**カスタムのメディアの種類:** `baptiste-preview` -**発表:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% endif %} {% ifversion ghes < 3.3 %} - -## Repositories API の新しい可視性パラメータ - -[Repositories API](/rest/reference/repos) でリポジトリの可視性を設定および取得できます。 - -**カスタムのメディアの種類:** `nebula-preview` -**発表:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md b/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md index f3fbea2471..73eb4745e2 100644 --- a/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md +++ b/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md @@ -13,11 +13,11 @@ versions: topics: - API shortTitle: GitHub App-enabled endpoints -ms.openlocfilehash: ab79abe1df9a14f7fdcc73f863e7bce5aa4abd4c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d8bb53e1844b8171a1ce742fc38e4c4bb29013e7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410364' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109523' --- diff --git a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md index 67ed185aab..3d7ecba758 100644 --- a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md +++ b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md @@ -140,6 +140,7 @@ If you set the metadata permission to **No access** and select a permission that - [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (read) - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (read) - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (read) +- [`POST /repos/:owner/:repo/actions/workflows/:workflow_id/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) (write) {% endif %} ## Administration @@ -284,20 +285,14 @@ If you set the metadata permission to **No access** and select a permission that - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (read) - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (read) - [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#update-a-code-scanning-alert) (write) -{% ifversion fpt or ghec or ghes or ghae -%} - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (read) -{% endif -%} - [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (read) -{% ifversion fpt or ghec or ghes or ghae -%} - [`GET /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (read) -{% endif -%} {% ifversion fpt or ghec or ghes -%} - [`DELETE /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (write) {% endif -%} - [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) (write) -{% ifversion fpt or ghec or ghes or ghae -%} - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (read) -{% endif -%} {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%} - [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (read) {% endif -%} diff --git a/translations/ja-JP/content/rest/repos/autolinks.md b/translations/ja-JP/content/rest/repos/autolinks.md index ea8442f75c..ad8ae892e4 100644 --- a/translations/ja-JP/content/rest/repos/autolinks.md +++ b/translations/ja-JP/content/rest/repos/autolinks.md @@ -5,18 +5,18 @@ shortTitle: Autolinks intro: ご利用のワークフローをスムーズにするには、API を使って、JIRA の Issue や Zendesk のチケットなど外部リソースへの自動リンクを追加します。 versions: fpt: '*' - ghes: '>=3.3' + ghes: '*' ghae: '*' ghec: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 1a0900a0665675526381987836631c7ff3496a81 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c35d9232ec43cf9dc19c9559de0e8411fa85e242 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066555' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148109007' --- ## リポジトリ自動リンク API について diff --git a/translations/ja-JP/content/rest/repos/lfs.md b/translations/ja-JP/content/rest/repos/lfs.md index a258ba1f75..a402c744c9 100644 --- a/translations/ja-JP/content/rest/repos/lfs.md +++ b/translations/ja-JP/content/rest/repos/lfs.md @@ -3,7 +3,7 @@ title: Git LFS intro: 'You can enable or disable {% data variables.large_files.product_name_long %} (LFS) for a repository.' versions: fpt: '*' - ghes: '>=3.3' + ghes: '*' ghae: '*' ghec: '*' topics: diff --git a/translations/ja-JP/content/rest/users/ssh-signing-keys.md b/translations/ja-JP/content/rest/users/ssh-signing-keys.md index df9418c21a..678c0a704c 100644 --- a/translations/ja-JP/content/rest/users/ssh-signing-keys.md +++ b/translations/ja-JP/content/rest/users/ssh-signing-keys.md @@ -9,12 +9,12 @@ topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 758f7897f965323e3675bf6b0ac1d295a3338f05 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: c8b9b71cf14efdd119f759fa36f5baae8e7a9301 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147773905' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108935' --- ## ユーザーの SSH 署名キー API について 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 0054f0a88c..71105cabcd 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 @@ -163,8 +163,8 @@ You can narrow your results by labels, using the `label` qualifier. Since issues | ------------- | ------------- | label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." -| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %} -| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved." +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved." ## Search by milestone @@ -266,8 +266,8 @@ You can filter pull requests based on their [review status](/pull-requests/colla | `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. Requested reviewers are no longer listed in the search results after they review a pull request. 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 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 %} +| 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. Requested reviewers are no longer listed in the search results after they review a pull request. 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. +| 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. | team-review-requested:TEAMNAME | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request. ## Search by when an issue or pull request was created or last updated diff --git a/translations/ja-JP/content/search/index.md b/translations/ja-JP/content/search/index.md index 1d56a86dc2..6d79ce0407 100644 --- a/translations/ja-JP/content/search/index.md +++ b/translations/ja-JP/content/search/index.md @@ -6,11 +6,11 @@ versions: ghec: '*' ghes: '*' ghae: '*' -ms.openlocfilehash: d7e276ed5305ffc8fd9732f6895fdf3b7461fb4c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 1a780ae1a9481af58598ac2a37eec1553b08f627 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147648290' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108826' --- diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index 56cb561fd3..734faced51 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -23,11 +23,11 @@ children: - /tax-information-for-github-sponsors - /disabling-your-github-sponsors-account - /unpublishing-your-github-sponsors-profile -ms.openlocfilehash: 7f7a6e7a1f46dadaac3cf75b8387bf18dd22e0d0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d7d3b8f98e7acf74ee24e7cf705f0ddb3c5d4b26 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145149677' +ms.lasthandoff: 10/25/2022 +ms.locfileid: '148108821' --- diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index ff91db0de1..2fd18cd191 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -1,564 +1,788 @@ -- term: '@メンション' +- term: '@mention' description: - "GitHub のユーザーに通知するには、ユーザー名の前に \"@\" を付けます。GitHub の Organization のユーザーも、メンションされるチームの一員にすることができます。" -- term: アクセス トークン + To notify a person on GitHub by using `@` before their username. Users in an organization on GitHub can also be a part of a team that can be + mentioned. +- term: access token description: >- - コマンド ラインと API のどちらで Git を使っても、HTTPS 経由で Git 操作を実行するときにパスワードの代わりに使用されるトークン。個人用アクセス トークンとも呼ばれます。 -- term: API プレビュー + A token that is used in place of a password when performing Git operations + over HTTPS with Git on the command line or the API. Also called a personal + access token. +- term: API preview description: >- - 新しい API や、既存の API メソッドに対する変更を、公式 GitHub API の一部となる前に試す方法。 -- term: アプライアンス + A way to try out new APIs and changes to existing API methods before they + become part of the official GitHub API. +- term: appliance description: >- - Just Enough Operating System (JeOS) と結合して、業界標準ハードウェア (通常はサーバー) または仮想マシンで最適に動作するソフトウェア アプリケーション。 + A software application combined with just enough operating system (JeOS) to + run optimally on industry-standard hardware (typically a server) or in a + virtual machine. - term: assignee - description: issue に割り当てられたユーザー。 -- term: 認証コード + description: The user that is assigned to an issue. +- term: authentication code description: >- - ブラウザーから 2FA でサインインするときに、GitHub パスワードの他に入力するコード。このコードは、アプリケーションによって生成されるか、お使いのスマートフォンにテキスト メッセージで送信されます。"2FA 認証コード" とも呼ばれます。 -- term: ベース ブランチ + A code you'll supply, in addition to your GitHub password, when signing in + with 2FA via the browser. This code is either generated by an application or delivered to + your phone via text message. Also called a "2FA authentication code." +- term: base branch description: - pull request をマージするときに変更の組み込み先となるブランチ。必要な場合は、pull request を作成するときに、ベース ブランチをリポジトリの既定のブランチから別のブランチに変更できます。 -- term: Basic 認証 + The branch into which changes are combined when you merge a pull request. + When you create a pull request, you can change the base branch from the repository's default branch to another branch if required. +- term: basic authentication description: >- - 資格情報が暗号化されていないテキストとして送信される場合の認証の方法。 -- term: 略歴 + A method of authentication where the credentials are sent as + unencrypted text. +- term: bio description: >- - プロフィールに記載されている、ユーザーが作成した説明 ([プロフィールに略歴を追加する](/articles/adding-a-bio-to-your-profile)) -- term: 支払いサイクル - description: 特定の支払いプランの時間間隔。 -- term: 支払い請求先メール アドレス + The user-generated description found on a profile: + [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile) +- term: billing cycle + description: The interval of time for your specific billing plan. +- term: billing email description: >- - 領収書や、クレジットカードまたは PayPal の支払いなど、GitHub からの支払い関連の連絡の送信先となる Organization のメール アドレス。 -- term: 支払いマネージャー - description: Organization の支払い設定を管理する Organization メンバー。 -- term: お支払いプラン + The organization email address where GitHub sends receipts, credit card or + PayPal charges, and other billing-related communication. +- term: billing manager + description: The organization member that manages billing settings for an organization. +- term: billing plan description: >- - ユーザーと Organization 向けのお支払いプラン。プランの各タイプのセット機能が含まれています。 + Payment plans for users and organizations that include set features for each + type of plan. - term: blame description: >- - Git の "blame" 機能は、ファイルの各行に対して最後に行われた変更を説明するものであり、通常は、リビジョン、作成者、時刻が表示されます。これは、機能が追加された日時や、特定のバグを引き起こしたコミットを追跡する場合などに役立ちます。 + The "blame" feature in Git describes the last modification to each line of a + file, which generally displays the revision, author and time. This is + helpful, for example, in tracking down when a feature was added, or which + commit led to a particular bug. - term: block description: >- - ユーザーが Organization のリポジトリでコラボレーションできないようにすること。 -- term: 分岐 + To remove a user's ability to collaborate on an organization's repositories. +- term: branch description: >- - ブランチとは、リポジトリのパラレル バージョンです。これは、リポジトリに含まれていますが、プライマリ ブランチや main ブランチに影響を与えることはなく、"ライブ" バージョンに混乱をもたらさずに自由に作業できるものです。必要な変更を行ったら、ブランチを main ブランチにマージし直して、変更を公開できます。 -- term: ブランチ制限 + A branch is a parallel version of a repository. It is contained within the + repository, but does not affect the primary or main branch allowing you to + work freely without disrupting the "live" version. When you've made the + changes you want to make, you can merge your branch back into the main + branch to publish your changes. +- term: branch restriction description: >- - 特定のユーザーまたはチームのみが、プッシュしたり、ブランチに対して変更を行ったりすることができるように、リポジトリ管理者が有効化できる制限。 -- term: Business プラン + A restriction that repository admins can enable so that only certain users + or teams can push or make certain changes to the branch. +- term: Business plan description: >- - Organization の支払いプラン。無制限のパブリック リポジトリやプライベート リポジトリでコラボレーションしたり、SAML SSO を使った GitHub に対する認証を Organization メンバーに許可または要求したり、SAML または SCIM を使ってアクセスをプロビジョニングまたはプロビジョニング解除したりすることができます。 -- term: CA 証明書 + An organization billing plan where you can collaborate on unlimited public + and private repositories, allow or require organization members to + authenticate to GitHub using SAML SSO, and provision and deprovision access + with SAML or SCIM. +- term: CA certificate description: >- - 証明機関 (CA) から発行されるデジタル証明書。これによって、2 つのマシン (ユーザーのコンピューターと GitHub.com など) の間で有効な接続が確保され、サイトの所有権が検証されます。 -- term: カード - description: Issue または pull request に関連付けられたプロジェクト ボード内にある移動可能な正方形。 -- term: チェック + A digital certificate issued by Certificate Authority (CA) that ensures there are valid connections between two machines, such as a user's computer and GitHub.com and verifies the ownership of a site. +- term: card + description: A movable square within a project board associated with an issue or pull request. +- term: check description: >- - チェックは、{% data variables.product.product_name %} でのステータス チェックのタイプの 1 つです。「[ステータス チェック](#status-checks)」を参照してください。 -- term: チェックアウト + A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)." +- term: checkout description: >- - "git checkout" は、コマンド ラインで使うと、新しいブランチを作成できます。また、"git checkout" によって、作業中のブランチを、別のブランチに変更するだけではなく、"git checkout [branchname] [path to file]" を指定した別のブランチの別のバージョンのファイルに切り替えることもできます。"checkout" アクションを使うと、オブジェクト データベースのツリー オブジェクトや BLOB でワーキング ツリー全体または一部を更新できます。また、ワーキングツリー全体が新しいブランチをポイントしている場合は、インデックスと HEAD を更新できます。 -- term: チェリーピック + You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or + blob from the object database, and updates the index and HEAD if the whole + working tree is pointing to a new branch. +- term: cherry-picking description: >- - 変更のサブセットを一連の変更 (通常はコミット) から選び、新しい一連の変更を別の codebase 上に記録すること。Git では、別のブランチの既存のコミットによって導入された変更を抽出したり、それを現在のブランチのヒントに基づいて新しいコミットとして記録したりするために、"git cherry-pick" コマンドを使ってこれを実行します。詳しくは、Git ドキュメントで [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) に関するページを参照してください。 -- term: 子チーム + To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation. +- term: child team description: >- - 入れ子チーム内で、親チームのアクセス権限と @メンションを継承するサブチーム。 -- term: クリーン + Within nested teams, the subteam that inherits the parent team's access + permissions and @mentions. +- term: clean description: >- - ワーキング ツリーが現在の HEAD によって参照されているリビジョンに対応している場合、そのワーキング ツリーはクリーンです。「ダーティ」も参照してください。 -- term: 複製 + A working tree is clean if it corresponds to the revision referenced by the + current HEAD. Also see "dirty". +- term: clone description: >- - クローンとは、Web サイトのサーバー上ではなく、ユーザーのコンピューターに存在するリポジトリのコピーのことです。または、そのコピーを作成する操作を指します。クローンを作成すると、好きなエディターでファイルを編集したり、オンラインでなくても、Git を使って変更を記録したりすることができます。クローンしたリポジトリは、リモート バージョンには接続されたままなので、オンラインになったときに、ローカルで行った変更をリモート バージョンにプッシュすれば同期させることができます。 -- term: クラスターリング + A clone is a copy of a repository that lives on your computer instead of on + a website's server somewhere, or the act of making that copy. When you make a + clone, you can edit the files in your preferred editor and use Git to keep + track of your changes without having to be online. The repository you cloned + is still connected to the remote version so that you can push your local + changes to the remote to keep them synced when you're online. +- term: clustering description: >- - 複数のノードにわたって、またこれらのノード間の負荷分散リクエストにわたって、GitHub Enterprise サービスを実行する機能。 -- term: コードの更新頻度のグラフ + The ability to run GitHub Enterprise services across multiple nodes and load + balance requests between them. +- term: code frequency graph description: >- - 各週のコンテンツの追加と削除の回数をリポジトリの履歴に示すリポジトリ グラフ。 -- term: 行動規範 - description: コミュニティへの参加方法の基準を定義したドキュメント。 -- term: コード オーナー + A repository graph that shows the content additions and deletions for each + week in a repository's history. +- term: code of conduct + description: A document that defines standards for how to engage in a community. +- term: code owner description: >- - リポジトリのコードがある部分のオーナーに指名されたユーザー。コード オーナーが所有するコードを変更する pull request を他のユーザーが開くと、コード オーナーに対してレビューが自動的にリクエストされます。 -- term: コラボレーター + A person who is designated as an owner of a portion of a repository's code. The code owner is automatically requested for review when someone opens a pull request (not in draft mode) that makes changes to code the code owner owns. +- term: collaborator description: >- - コラボレーターとは、リポジトリへの読み取りアクセスと書き込みアクセスを持ち、コントリビューションするようにリポジトリ オーナーが招待したユーザーのことです。 -- term: コミット (commit) + A collaborator is a person with read and write access to a repository who + has been invited to contribute by the repository owner. +- term: commit description: >- - コミットは、ファイル (またはファイルのセット) に対する個別の変更のことであり、"リビジョン" とも呼ばれます。コミットして作業内容を保存すると、Git によって一意の ID ("SHA" や "ハッシュ" とも呼ばれます) が作成されます。この ID で、コミットした特定の変更や、作成したユーザーや日時の記録を保持することができます。通常、コミットには、変更の内容について簡潔に記述されたコミット メッセージが含まれています。 -- term: コミット作者 - description: コミットを行うユーザー。 -- term: コミット グラフ + A commit, or "revision", is an individual change to a file (or set of + files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a + commit message which is a brief description of what changes were made. +- term: commit author + description: The user who makes the commit. +- term: Commit graph description: >- - 1 つのリポジトリに対して過去 1 年間で行われたすべてのコミットを示すリポジトリ グラフ。 -- term: コミット ID - description: SHA とも呼ばれます。コミットを識別する 40 文字のチェックサム ハッシュ。 -- term: コミット メッセージ + A repository graph that shows all the commits made to a repository in the + past year. +- term: commit ID + description: Also known as SHA. A 40-character checksum hash that identifies the commit. +- term: commit message description: >- - コミットに付ける短い説明テキスト。コミットによって行われる変更について伝えます。 -- term: 比較ブランチ + Short, descriptive text that accompanies a commit and communicates the change + the commit is introducing. +- term: compare branch description: >- - pull request の作成に使うブランチ。このブランチは、pull request で選んだベース ブランチと比較されて、変更内容が特定されます。pull request がマージされると、このベース ブランチは、比較ブランチからの変更を使って更新されます。pull request の "ヘッド ブランチ" とも呼ばれます。 -- term: 継続的インテグレーション + The branch you use to create a pull request. + This branch is compared to the base branch you choose for the pull request, and the changes are identified. + When the pull request is merged, the base branch is updated with the changes from the compare branch. + Also known as the "head branch" of the pull request. +- term: continuous integration description: >- - CI とも呼ばれます。GitHub 上に構成されたリポジトリに対してユーザーが変更をコミットすると、自動化されたビルドとテストを実行するプロセス。CI は、ソフトウェア開発の一般的なベスト プラクティスであり、エラーの検出に役立ちます。 -- term: コントリビューション グラフ + Also known as CI. A process that runs automated builds and tests once a person commits a change to a configured repository on GitHub. CI is a common best practice in software development that helps detect errors. +- term: contribution graph description: >- - ユーザーのプロファイルの一部であり、過去最大 1 年間の 1 日ごとのコントリビューションを示します。 -- term: コントリビューション ガイドライン - description: ユーザーがプロジェクトにコントリビューションする方法を説明したドキュメント。 -- term: コントリビューション + The part of a user's profile that shows their contributions over a period of + up to one year, day by day. +- term: contribution guidelines + description: A document explaining how people should contribute to your project. +- term: contributions description: >- - ユーザーのコントリビューション グラフに正方形を追加 (「[コントリビューションとして何がカウントされるか](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)」) したり、ユーザーのプロファイルでユーザーのタイムラインにアクティビティを追加 (「[コントリビューション アクティビティ](/articles/viewing-contributions-on-your-profile/#contribution-activity)」) したりする、GitHub での特定のアクティビティ。 -- term: 共同作成者 + Specific activities on GitHub that will: + - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" + - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)" +- term: contributor description: >- - 共同作成者とは、リポジトリへのコラボレーター アクセスはないものの、プロジェクトに対してコントリビューションを行い、オープンした pull request をリポジトリにマージさせたユーザーのことです。 -- term: 共同作成者グラフ - description: リポジトリの共同作成者上位 100 人を表示するリポジトリ グラフ。 -- term: クーポン + A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository. +- term: contributors graph + description: A repository graph that displays the top 100 contributors to a repository. +- term: coupon description: >- - ユーザーや Organization がサブスクリプション全体または一部の支払いに使うことができる、GitHub が指定したコード。 + A GitHub-provided code that users or organizations can use to pay for all or + part of their subscription. - term: cron - description: Unix のようなコンピューター オペレーティング システムでの、時間ベースのジョブ スケジューラ。 + description: A time-based job scheduler in Unix-like computer operating systems. - term: cURL - description: データを転送するためにコマンド ラインまたはスクリプトで使用されます。 + description: Used in command lines or scripts to transfer data. - term: dashboard description: >- - パーソナル ダッシュボードは、GitHub でのアクティビティのメイン ハブです。パーソナル ダッシュボードでは、フォロー中または作業中の issue や pull request を記録したり、トップ リポジトリやチームのページにアクセスしたり、watch 中または参加中のリポジトリの最近のアクティビティについて把握したりすることができます。また、フォロー中のユーザーや、Star を付けたリポジトリに基づいた、お勧めの新しいリポジトリを見つけることもできます。特定の Organization でのアクティビティのみを表示するには、Organization のダッシュボードにアクセスしてください。詳しくは、「[パーソナル ダッシュボードについて](/articles/about-your-personal-dashboard)」または「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard)」を参照してください。 -- term: 既定のブランチ + Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)" or "[About your organization dashboard](/articles/about-your-organization-dashboard)." +- term: default branch description: >- - リポジトリ内の新しい pull request とコードのコミットのためのベース ブランチです。それぞれのリポジトリには、ブランチが 1 つ以上ありますが、これは、リポジトリを初期化すると Git によって作成されるものです。通常、最初のブランチは {% ifversion ghes < 3.2 %}"master"{% else %}"main"{% endif %} という名前のものですが、たいていは既定のブランチです。 -- term: 依存グラフ + The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch. +- term: dependents graph description: >- - パブリック リポジトリに依存するパッケージ、プロジェクト、リポジトリを示すリポジトリ グラフ。 -- term: 依存関係グラフ + A repository graph that shows the packages, projects, and repositories that depend on a + public repository. +- term: dependency graph description: >- - リポジトリが依存するパッケージとプロジェクトを示すリポジトリ グラフ。 -- term: デプロイ キー + A repository graph that shows the packages and projects that the repository depends on. +- term: deploy key description: >- - デプロイ キーは、サーバー上に格納されている SSH キーのことで、単一の GitHub リポジトリへのアクセス権の付与に使います。このキーは、個人用ユーザー アカウントにアタッチされるのではなく、リポジトリに直接アタッチされます。 -- term: デタッチされた HEAD + A deploy key is an SSH key that is stored on your server and grants access + to a single GitHub repository. This key is attached directly to the + repository instead of to a personal user account. +- term: detached HEAD description: >- - Git では、デタッチされた HEAD で作業しようとすると、Git によってブランチがポイントされていないという警告や、ユーザーが行ったコミットがコミット履歴に表示されないという警告が表示されます。 たとえば、チェックアウトした任意のコミットが、特定のブランチの最新のコミットではない場合、"デタッチされた HEAD" で作業をしていることになります。 -- term: 診断 - description: GitHub Enterprise インスタンスの設定と環境の概要。 + Git will warn you if you're working on a detached HEAD, which means that Git + is not pointing to a branch and that any commits you make will not appear in + commit history. For example, when you check out an arbitrary commit that + is not the latest commit of any particular branch, you're working on a + "detached HEAD." +- term: diagnostics + description: An overview of a GitHub Enterprise instance's settings and environment. - term: diff description: >- - diff とは、2 つのコミットまたは保存された変更間の差異のことです。diff では、最後のコミット以降にファイルに追加されたかファイルから削除されたものを視覚的に説明します。 + A diff is the difference in changes between two commits, or saved changes. + The diff will visually describe what was added or removed from a file since + its last commit. - term: directory description: >- - 1 つ以上のファイルまたはフォルダーを含むフォルダー。ディレクトリを作成すると、リポジトリの内容を整理できます。 -- term: ダーティ + A folder containing one or more files or folders. You can create directories to organize the contents of a repository. +- term: dirty description: >- - ワーキング ツリーは、現在のブランチにコミットされていない修正が含まれている場合は、"ダーティ" と見なされます。 -- term: 電子メール通知 - description: ユーザーのメール アドレスに送信される通知。 -- term: Enterprise アカウント - description: "Enterprise アカウントでは、複数の Organization のポリシーと支払いを一元管理できます。{% data reusables.gated-features.enterprise-accounts %}" -- term: エクスプローラー + A working tree is considered "dirty" if it contains modifications that have + not been committed to the current branch. +- term: email notifications + description: Notifications sent to a user's email address. +- term: enterprise account + description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %} +- term: Explorer description: >- - GraphiQL のインスタンスであり、"グラフィカルな対話型ブラウザー内 GraphQL IDE" です。 + An instance of GraphiQL, which is a "graphical interactive in-browser GraphQL + IDE." - term: fast-forward description: >- - fast-forward とは、リビジョンがあり、かつ別のブランチでの変更を "マージしている" が、その変更が偶然にもそのリビジョンの子孫である場合の、特別なタイプのマージのことです。そのような場合は、新しいマージ コミットを行いませんが、代わりに、このリビジョンに対して更新を行います。これは、リモート リポジトリのリモート追跡ブランチで頻繁に起こります。 -- term: 機能ブランチ + A fast-forward is a special type of merge where you have a revision and you + are "merging" another branch's changes that happen to be a descendant of + what you have. In such a case, you do not make a new merge commit but + instead just update to this revision. This will happen frequently on a + remote-tracking branch of a remote repository. +- term: feature branch description: >- - 新しい機能の実験や、本番には存在しない issue の修正に使うブランチ。トピック ブランチとも呼ばれます。 -- term: フェンスされたコード ブロック - description: "コード ブロックの前後に 3 つのバックティック (\\ \\ \\) を使って、GitHub Flavored Markdown で作成できるコードのインデント付きブロック。こちらの[例](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)を参照してください。" + A branch used to experiment with a new feature or fix an issue that is not in production. Also called a topic branch. +- term: fenced code block + description: An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks). - term: fetch description: >- - "git fetch" は、変更をコミットせずに、リモート リポジトリからローカルで作業中のブランチに追加する場合に使います。"git pull" とは異なり、変更を、ローカル ブランチにコミットする前にレビューできます。 -- term: フォロー (ユーザー) - description: 別のユーザーのコントリビューションとアクティビティについて通知を受けること。 -- term: フォース プッシュ + When you use `git fetch`, you're adding changes from the remote repository to + your local working branch without committing them. Unlike `git pull`, fetching + allows you to review changes before committing them to your local branch. +- term: following (users) + description: To get notifications about another user's contributions and activity. +- term: force push description: >- - 競合を考慮することなく、リモート リポジトリをローカルな変更で上書きする Git プッシュ。 -- term: フォーク + A Git push that overwrites the remote repository with local changes without + regard for conflicts. +- term: fork description: >- - フォークとは、自分のアカウントに存在する別のユーザーのリポジトリの個人用のコピーのことです。フォークすると、元の上流リポジトリに影響を与えることなく、プロジェクトに対して自由に変更を加えることができます。また、上流リポジトリで pull request を開いたり、両方のリポジトリが接続されたままなので、自分が行ったフォークを最新の変更に同期させ続けたりすることもできます。 -- term: Free プラン + A fork is a personal copy of another user's repository that lives on your + account. Forks allow you to freely make changes to a project without + affecting the original upstream repository. You can also open a pull request in + the upstream repository and keep your fork synced with the latest changes since + both repositories are still connected. +- term: Free plan description: >- - 無料のユーザー アカウントお支払いプラン。ユーザーは、無制限のパブリック リポジトリで、無制限のコラボレーターと共同作業できます。 + A user account billing plan that is free. Users can collaborate on unlimited + public repositories with unlimited collaborators. - term: gist description: >- - gist とは、共有可能なファイルであり、GitHub 上で編集、クローン、フォークできます。gist を、{% ifversion ghae %}内部{% else %}パブリック{% endif %}またはシークレットの gist にすることができますが、シークレット gist は、URL を持つ{% ifversion ghae %}すべての Enterprise メンバー {% else %}すべてのユーザー{% endif %}が使用できます。 + A gist is a shareable file that you can edit, clone, and fork on GitHub. + You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be + available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL. - term: Git description: >- - Git は、テキスト ファイルの変更を追跡するためのオープン ソース プログラムです。Linux オペレーティング システムの作成者によって記述されたもので、ソーシャルなユーザー インターフェイスである GitHub は、その最上位に構築された中核となるテクノロジです。 + Git is an open source program for tracking changes in text files. It was + written by the author of the Linux operating system, and is the core + technology that GitHub, the social and user interface, is built on top of. - term: GitHub App description: >- - GitHub App は、Organization 全体に対してサービスを提供します。また、機能の実行には、独自の ID が使用されます。Organization やユーザー アカウントに直接インストールすることができ、特定のリポジトリへのアクセス権も付与されます。細かな権限が付与されており、Webhook が組み込まれています。 + GitHub Apps provide a service to an entire organization and use their own + identity when performing their function. They can be installed directly on + organizations and user accounts and granted access to specific repositories. + They come with granular permissions and built-in webhooks. - term: GitHub Flavored Markdown - description: "GitHub 全体で文章やコードを書式設定するために使用される、GitHub 固有の Markdown。「[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)」または「[GitHub での記述と書式設定の開始](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。" + description: GitHub-specific Markdown used to format prose and code across GitHub. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github). - term: GitHub Importer description: >- - コミットやリビジョン履歴などのソース コード リポジトリを、ユーザーに代わってすばやく GitHub にインポートするツール。 + A tool that quickly imports source code repositories, including commits and + revision history, to GitHub for users. - term: GitHub Jobs description: >- - GitHub ユーザーが関心を持ちそうな仕事について雇用主が投稿できる GitHub サイト。 + A GitHub site where employers can post jobs that GitHub users may be + interested in. - term: GitHub Marketplace description: >- - GitHub ユーザーや Organization 向けの、ワークフローを拡張して補完するアプリケーションを購入してインストールするためのサブサイト。 -- term: GitHub ページ + A subsite for GitHub users and organizations to purchase and install + applications that extend and complement their workflow. +- term: GitHub Pages description: >- - Pages とも呼ばれます。個人、Organization、またはプロジェクトのページを GitHub リポジトリから直接ホストするように設計された、静的サイト ホスティング サービス。 + Also referred to as Pages. A static site hosting service designed to host + your personal, organization, or project pages directly from a GitHub + repository. - term: GitHub Wiki - description: wiki スタイルのドキュメントを GitHub リポジトリ上でホストするためのセクション。 + description: A section for hosting wiki style documentation on a GitHub repository. - term: gitfile description: >- - プレーンな ".git" ファイル。常に、ワーキング ツリーのルートに存在し、Git リポジトリ全体とそのメタ データが含まれる Git ディレクトリをポイントしています。このファイルは、リポジトリが実際のリポジトリであれば、コマンド ラインに "git rev-parse --git-dir" が含まれます。 + A plain `.git` file, which is always at the root of a working tree and points to the Git directory, which has the entire Git repository and its meta data. You can view this file for your repository on the command line with `git rev-parse --git-dir`. + that is the real repository. - term: GraphQL description: >- - API のクエリ言語であり、既存のデータを使ってクエリを実行するためのランタイムです。 + A query language for APIs and a runtime for fulfilling those queries with + your existing data. - term: HEAD - description: ブランチの定義済みコミット。通常は、ブランチの先頭にある最新のコミットです。 -- term: head ブランチ - description: "pull request をマージすると、このブランチの変更がベース ブランチに組み込まれます。\"比較ブランチ\" とも呼ばれます。" + description: A defined commit of a branch, usually the most recent commit at the tip of the branch. +- term: head branch + description: The branch whose changes are combined into the base branch + when you merge a pull request. + Also known as the "compare branch." - term: 'Hello, World' description: >- - "Hello, World!" プログラムは、"Hello, World!" をユーザーに対して出力または表示するコンピューター プログラムです。このプログラムは通常、非常に単純なので、プログラミング言語の基本的な構文の例として使用されることが多く、一般的に、新しいプログラミング言語を学習するための最初の演習として使用されます。 + A "Hello, World!" program is a computer program that outputs or displays + "Hello, World!" to a user. Since this program is usually very simple, it is + often used as an example of a programming language's basic syntax and + serves as a common first exercise for learning a new programming language. - term: high-availability description: >- - 長時間継続して稼働させるのが望ましいシステムまたはコンポーネント。 -- term: フック + A system or component that is continuously operational for a desirably long + length of time. +- term: hook description: >- - いくつかの GitHub コマンドでは、コマンドの正常な実行中に、オプションのスクリプトに対してコールアウトが行われるので、開発者は機能やチェックを追加することができます。一般的には、フックすると、コマンドが事前に検証されて終了してしまったり、操作の完了後に事後通知が表示されたりする可能性があります。 + During the normal execution of several Git commands, call-outs are made to + optional scripts that allow a developer to add functionality or checking. + Typically, the hooks allow for a command to be pre-verified and potentially + aborted, and allow for a post-notification after the operation is done. - term: hostname description: >- - ネットワークに接続されているデバイスのアドレスに対応する、人間が判読可能なニックネーム。 -- term: アイデンティコン + Human-readable nicknames that correspond to the address of a device + connected to a network. +- term: identicon description: >- - ユーザーが GitHub にサインアップするときに既定のプロフィール写真として使用される、自動生成された画像。ユーザーは、アイデンティコンを自分のプロフィール写真に置き換えることができます。 -- term: ID プロバイダー + An auto-generated image used as a default profile photo when users sign up for + GitHub. Users can replace their identicon with their own profile photo. +- term: identity provider description: >- - IdP とも呼ばれます。他の Web サイトへのアクセスに SAML シングル サインオン (SSO) を使うことができる、信頼できるプロバイダー。 + Also known as an IdP. A trusted provider that lets you use SAML single + sign-on (SSO) to access other websites. - term: instance description: >- - Organization の GitHub のプライベートコピー。Organization によって構成され、制御されている仮想マシン内に含まれています。 -- term: 統合 + An organization's private copy of GitHub contained within a virtual machine + that they configure and control. +- term: integration description: >- - GitHub と統合されるサードパーティ アプリケーション。これは、GitHub Apps、OAuth Apps、または Webhook である場合があります。 -- term: イシュー + A third-party application that integrates with GitHub. These can be GitHub + Apps, OAuth Apps, or webhooks. +- term: issue description: >- - issue とは、リポジトリに関する改善の提案、タスク、または質問のことです。issue は、あらゆるユーザーが作成することができ (パブリック リポジトリの場合)、リポジトリのコラボレーターによってモデレートされます。各 issue には、独自のディスカッション スレッドが含まれています。また、ラベルを付けて分類したり、他のユーザーに割り当てたりすることもできます。 + Issues are suggested improvements, tasks or questions related to the + repository. Issues can be created by anyone (for public repositories), and + are moderated by repository collaborators. Each issue contains its own discussion thread. You can also categorize an issue with labels and assign it to someone. - term: Jekyll - description: 個人、プロジェクト、または Organization のサイト用の静的サイトジェネレータ。 -- term: Jekyll テーマ選択画面 + description: A static site generator for personal, project, or organization sites. +- term: Jekyll Theme Chooser description: >- - Jekyll サイトで、CSS ファイルを編集したりコピーしたりせずに、ビジュアル テーマを選ぶ自動化された方法。 -- term: キー フィンガープリント - description: 長い公開キーを識別するのに使用される、短いバイトのシーケンス。 -- term: キーチェーン - description: macOS のパスワード管理システム。 -- term: キーワード (keyword) - description: pull request 内で使用される場合、issue をクローズする特定の単語。 + An automated way to select a visual theme for your Jekyll site without editing or + copying CSS files. +- term: key fingerprint + description: A short sequence of bytes used to identify a longer public key. +- term: keychain + description: A password management system in macOS. +- term: keyword + description: A specific word that closes an issue when used within a pull request. - term: label description: >- - issue または pull request に付けるタグ。リポジトリには、既定のラベルがいくつかありますが、ユーザーはカスタム ラベルを作成することができます。 + A tag on an issue or pull request. Repositories come with a handful of + default labels, but users can create custom labels. - term: LFS description: >- - Git Large File Storage。大きいファイルをバージョン管理するためのオープンソース Git 拡張機能。 + Git Large File Storage. An open source Git extension for versioning large + files. - term: license description: >- - ソース コードを使ってできることとできないことをユーザーに知らせるためにプロジェクトに含めることができるドキュメント。 + A document that you can include with your project to let people know what + they can and can't do with your source code. - term: Linguist description: >- - GitHub で使用されるライブラリ。BLOB 言語を検出し、バイナリ ファイルやベンダーされたファイルを無視し、diff で生成されたファイルを非表示にし、言語別グラフを生成します。 -- term: 行コメント - description: 特定のコード行についての、pull request 内にあるコメント。 -- term: 行終端 + A library used on GitHub to detect blob languages, ignore binary or vendored + files, suppress generated files in diffs, and generate language breakdown + graphs. +- term: line comment + description: A comment within a pull request on a specific line of code. +- term: line ending description: >- - テキスト ファイルの行末をシンボル化する、1 つ以上の非表示の文字。 -- term: ロックされた個人用アカウント + An invisible character or characters that symbolize the end of a line in a + text file. +- term: locked personal account description: >- - ユーザーがアクセスできない個人用アカウント。ユーザーが有料アカウントから無料アカウントに変更したり、有料プランの支払い期限を過ぎたりすると、アカウントはロックされます。 -- term: 管理コンソール + A personal account that cannot be accessed by the user. Accounts are locked + when users downgrade their paid account to a free one, or if their paid plan + is past due. +- term: management console description: >- - GitHub Enterprise インターフェイス内にある、管理機能を含むセクション。 + A section within the GitHub Enterprise interface that contains + administrative features. - term: Markdown description: >- - Markdown は、非常に簡潔なセマンティック ファイル形式で、.doc、.rtf、.txt にやや近いものです。Markdown は、文章 (リンク、一覧、箇条書きなどを含む) を書いて Web サイトのように表示させるというような Web 発行の経験がないユーザーにとっても取り扱いやすいものです。GitHub では、Markdown をサポートするとともに、GitHub Flavored Markdown という名前の特別な形式の Markdown を使っています。「[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)」または「[GitHub での記述と書式設定の開始](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。 -- term: マークアップ - description: ドキュメントの注釈と書式設定を行うためのシステム。 -- term: メイン + Markdown is an incredibly simple semantic file format, not too dissimilar + from .doc, .rtf and .txt. Markdown makes it easy for even those without a + web-publishing background to write prose (including with links, lists, + bullets, etc.) and have it displayed like a website. GitHub supports + Markdown and uses a particular form of Markdown called GitHub Flavored Markdown. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github). +- term: markup + description: A system for annotating and formatting a document. +- term: main description: >- - {% ifversion fpt or ghes > 3.1 or ghae %} 既定の開発ブランチ。Git リポジトリを作成するたびに、"main" という名前のブランチが作成され、アクティブなブランチになります。ほとんどの場合、これにはローカル開発が含まれますが、あくまでも規則によるものであり、必須ではありません。{% else %}リポジトリの既定のブランチには、"master" という名前が代わりに選択されることもよくあります。{% endif %} + The default development branch. Whenever you create a Git repository, + a branch named `main` is created, and becomes the active branch. + In most cases, this contains the local development, though that is purely by + convention and is not required. - term: master description: >- - 多くの Git リポジトリの既定のブランチ。既定では、コマンド ラインで新しい Git リポジトリを作成すると、"master" という名前のブランチが作成されます。多くのツールでは、既定のブランチに別の名前を使うようになってきています。{% ifversion fpt or ghes > 3.1 or ghae %} たとえば、GitHub で新しいリポジトリを作成する場合、既定のブランチは "main" という名前です。{% endif %} -- term: メンバー グラフ - description: リポジトリのすべてのフォークを示すリポジトリ グラフ。 -- term: メンション + The default branch in many Git repositories. By default, when you create + a new Git repository on the command line, a branch called `master` is created. + Many tools now use an alternative name for the default branch. For example, + when you create a new repository on GitHub, the default branch is called `main`. +- term: members graph + description: A repository graph that shows all the forks of a repository. +- term: mention description: >- - ユーザー名の前に @ 記号を付けることで、そのユーザーに送信される通知。GitHub の Organization のユーザーも、メンションされるチームの一員にすることができます。 + A notification sent to a user by prefacing their username with the @ symbol. + Users in an organization on GitHub can also be a part of a team that can be + mentioned. - term: merge description: >- - マージとは、1 つのブランチから (同じリポジトリ内で、またはフォークから) 変更を取得し、その変更を別のブランチに適用することです。これは、多くの場合、"pull request" (マージのリクエストと考えてもよいでしょう) として、またはコマンド ライン経由で行われます。マージは、競合する変更がない場合や、常にコマンド ライン経由で行われる場合は、GitHub.com Web インターフェイス経由で pull request を介して行われます。 -- term: マージの競合 + Merging takes the changes from one branch (in the same repository or from a + fork), and applies them into another. This often happens as a "pull request" + (which can be thought of as a request to merge), or via the command line. A + merge can be done through a pull request via the GitHub.com web + interface if there are no conflicting changes, or can always be done via the + command line. +- term: merge conflict description: >- - マージされたブランチ間で発生する差異。マージの競合は、複数のユーザーが同じファイルの同じ行に異なる変更を加えた場合や、1 人のユーザーがファイルを編集し、別のユーザーがその同じファイルを削除した場合に発生します。ブランチをマージするには、マージの競合を解決しておく必要があります。 -- term: マイルストーン + A difference that occurs between merged branches. Merge conflicts happen + when people make different changes to the same line of the same file, or + when one person edits a file and another person deletes the same file. The + merge conflict must be resolved before you can merge the branches. +- term: milestone description: >- - リポジトリ内にある issue や pull request のグループの進行状況を追跡する方法。 -- term: ミラー - description: リポジトリの新しいコピー。 -- term: 入れ子チーム + A way to track the progress on groups of issues or pull requests in a + repository. +- term: mirror + description: A new copy of a repository. +- term: nested team description: >- - 親チームの子チーム。ユーザーは、複数の子チーム (または入れ子チーム) を持つことができます。 -- term: ネットワーク グラフ + A child team of a parent team. You can have multiple children (or nested) + teams. +- term: network graph description: >- - ルート リポジトリのブランチや、ネットワーク固有のコミットを含むフォークのブランチなど、リポジトリ ネットワーク全体のブランチ履歴を示すリポジトリグラフ。 -- term: ニュース フィード + A repository graph that shows the branch history of the entire repository + network, including branches of the root repository and branches of forks + that contain commits unique to the network. +- term: news feed description: >- - Watch しているリポジトリまたはユーザーのアクティビティ ビュー。Organization のニュース フィードには、Organization が所有するリポジトリでのアクティビティが表示されます。 + An activity view of repositories or people you watch. An organization's News + Feed shows activity on repositories owned by the organization. - term: non-fast-forward description: >- - リポジトリのローカル コピーが上流リポジトリと同期されておらず、ローカルの変更をプッシュするには、上流の変更をフェッチする必要がある場合。 -- term: 通知 (notification) + When your local copy of a repository is out-of-sync with the upstream + repository and you need to fetch the upstream changes before you push your + local changes. +- term: notification description: >- - 関心のあるアクティビティについての情報を提供するアップデート。設定に応じて、Web またはメールで届きます。 + Updates, delivered by either the web or email depending on your settings, + that give you information about the activities you're interested in. - term: OAuth App description: >- - ユーザーに関する情報にアクセスするために、パスワードではなくアクセス トークンが使用されるサードパーティ アプリケーション。 -- term: OAuth トークン - description: ユーザーに関する情報にアクセスするために OAuth Apps で使用されるアクセス トークン。 -- term: 外部コラボレーター + A third-party application that uses access tokens rather than passwords to + access information for users. +- term: OAuth token + description: The access token used in OAuth Apps to access information for users. +- term: outside collaborator description: >- - Organization の 1 つ以上のリポジトリへのアクセス権が付与されているが、その Organization への他のアクセス権は付与されておらず、その Organization のメンバーではないユーザー。 -- term: オープン ソース + A user who has been given access to one or more of an organization’s + repositories, but has no other access to the organization and is not a + member of the organization. +- term: open source description: >- - オープン ソース ソフトウェアとは、あらゆるユーザーが自由に使い、変更し、共有できるソフトウェアのことです (形式の変更の有無は問いません)。今日の "オープン ソース" の概念は、ソフトウェアの枠を超えて語られることが多く、あらゆるユーザーがオンラインで素材をフォーク、変更、ディスカッション、コントリビューションを行うことができるという意味でのコラボレーションという考え方を表しています。 + Open source software is software that can be freely used, modified, and + shared (in both modified and unmodified form) by anyone. Today the concept + of "open source" is often extended beyond software, to represent a + philosophy of collaboration in which working materials are made available + online for anyone to fork, modify, discuss, and contribute to. - term: organization description: >- - Organization とは、通常、実際の組織を反映する、2 人以上のユーザーのグループのことです。Organization の管理はユーザーが行い、リポジトリとチームの両方を含めることができます。 -- term: Organization オーナー - description: 所有する Organization の管理機能へのフル アクセスを持つユーザー。 + Organizations are a group of two or more users that typically mirror + real-world organizations. They are administered by users and can contain + both repositories and teams. +- term: organization owner + description: Users who have full administrative access to the organization they own. - term: origin description: >- - 既定の上流リポジトリ。ほとんどのプロジェクトには、追跡対象となっている 1 つ以上の上流プロジェクトがあります。既定では、origin がその目的で使用されます。 + The default upstream repository. Most projects have at least one upstream + project that they track. By default, origin is used for that purpose. - term: owner description: >- - Organization のすべての管理機能へのアクセスを持つ Organization メンバー。 -- term: 親チーム + Organization members that have complete administrative access to the + organization. +- term: parent team description: >- - 入れ子チーム内で、子チームによるアクセス権限と @メンションの継承元となっているメイン チーム。 -- term: 参加通知 + Within nested teams, the main team from which child teams inherit access + permissions and @mentions. +- term: participating notifications description: >- - 自分のユーザー名またはチームがメンションされていた、または以前コメント内で返信していた issue や pull request 内の会話のアップデートについての通知。 -- term: パーマリンク - description: 特定の Web ページへの永続的な静的ハイパーリンク。 -- term: 個人用アカウント + A notification about an update in a conversation in an issue or pull request + where your username or team was mentioned or where you have previously replied + in a comment. +- term: permalink + description: A permanent static hyperlink to a particular web page. +- term: personal account description: >- - 個々のユーザーに属している GitHub アカウント。 -- term: プライマリ メール アドレス + A GitHub account that belongs to an individual user. +- term: primary email address description: >- - 領収書や、クレジットカードまたは PayPal の支払いなど、GitHub からの支払い関連の連絡の送信先となる主要なメール アドレス。 -- term: 固定リポジトリ + The main email address where GitHub sends receipts, credit card or PayPal + charges, and other billing-related communication. +- term: pinned repository description: >- - ユーザーがアピールのために自分のプロフィールに表示することにしたリポジトリ。 -- term: pre-receive フック + A repository that a user has decided to display prominently on their + profile. +- term: pre-receive hooks description: >- - GitHub Enterprise サーバー上で実行されるスクリプトで、品質チェックの実装に使うことができます。 -- term: プライベート コントリビューション - description: プライベート リポジトリ (パブリック リポジトリではなく) に対して行われるコントリビューション。 -- term: プライベートリポジトリ + Scripts that run on the GitHub Enterprise server that you can use to + implement quality checks. +- term: private contributions + description: Contributions made to a private (vs. public) repository. +- term: private repository description: >- - プライベート リポジトリは、オーナーが指定したリポジトリ オーナーとコラボレーターにのみ表示されます。 -- term: 本番ブランチ + Private repositories are only visible to the repository owner and + collaborators that the owner specified. +- term: production branch description: >- - すぐに使用できる状態になっており、アプリケーションやサイトへのデプロイの準備が完了している、最終変更を含むブランチ。 + A branch with final changes that are ready to be used or deployed to an application or site. - term: profile - description: GitHub 上でのユーザーのアクティビティに関する情報を示すページ。 -- term: プロフィール写真 + description: The page that shows information about a user's activity on GitHub. +- term: profile photo description: >- - ユーザーが、自分のアクティビティを特定できるように GitHub にアップロードするカスタム画像。通常は、ユーザー名も記載されます。これは、アバターとも呼ばれます。 -- term: プロジェクト ボード + A custom image users upload to GitHub to identify their activity, usually + along with their username. This is also referred to as an avatar. +- term: project board description: >- - issue、pull request、メモから成る GitHub 内のボード。列内では、カードとして分類されます。 -- term: 保護されたブランチ + Boards within GitHub that are made up of issues, pull requests, and notes + that are categorized as cards in columns. +- term: protected branch description: >- - 保護されたブランチを使うと、リポジトリ管理者が保護対象として選んだブランチ上で、Git のいくつかの機能がブロックされます。このブランチに対して強制プッシュや削除はできません。また、必要なチェックに合格していない状態や必要なレビューが承認されていない状態で変更をマージしたり、GitHub Web インターフェイスからファイルをアップロードしたりすることはできません。保護されたブランチは通常、既定のブランチです。 -- term: パブリック コントリビューション - description: パブリック リポジトリ (プライベート リポジトリではなく) に対して行われるコントリビューション。 -- term: パブリック リポジトリ + Protected branches block several features of Git on a branch that a + repository administrator chooses to protect. They can't be force pushed, + deleted, have changes merged without required checks passing or required + reviews approved, or have files uploaded to it from the GitHub web + interface. A protected branch is usually the default branch. +- term: public contributions + description: Contributions made to a public (vs. private) repository. +- term: public repository description: >- - パブリック リポジトリは、GitHub ユーザーではないユーザーも含め、すべてのユーザーが見ることができます。 -- term: プル (pull) + A public repository can be viewed by anyone, including people who aren't + GitHub users. +- term: pull description: >- - プルとは、変更をフェッチしてマージすることを指します。たとえば、自分が作業しているファイルを他のユーザーが編集した場合に、その変更を自分のローカル コピーにプルして、最新の状態になるようにすることです。「フェッチ」も参照してください。 -- term: プル アクセス - description: 読み取りアクセスの同義語。 + Pull refers to when you are fetching in changes and merging them. For + instance, if someone has edited the remote file you're both working on, + you'll want to pull in those changes to your local copy so that it's up to + date. See also fetch. +- term: pull access + description: A synonym for read access. - term: pull request description: >- - pull request とは、リポジトリに対して提案された変更のことです。ユーザーがこれを送信すると、リポジトリのコラボレーターはこれを受け入れるか拒否します。issue と同様に、pull request にはそれぞれ独自のディスカッション フォーラムがあります。 -- term: pull request レビュー + Pull requests are proposed changes to a repository submitted by a user and + accepted or rejected by a repository's collaborators. Like issues, pull + requests each have their own discussion forum. +- term: pull request review description: >- - コラボレーターからの pull request についてのコメント。pull request がマージされる前に、変更を承認したり、その他の変更を要求したりします。 -- term: パルス グラフ - description: リポジトリのアクティビティの概要を示すリポジトリ グラフ。 -- term: パンチ グラフ + Comments from collaborators on a pull request that approve the changes or + request further changes before the pull request is merged. +- term: pulse graph + description: A repository graph that gives you an overview of a repository's activity. +- term: punch graph description: >- - リポジトリのアップデートの頻度を、曜日ごと、または時刻ごとに示すリポジトリ グラフ + A repository graph that shows the frequency of updates to a repository based + on the day of week and time of day - term: push description: >- - プッシュとは、コミットした変更を GitHub.com 上のリモート リポジトリに送信するという意味です。たとえば、ローカルで何かを変更した場合、その変更をプッシュすると、他のユーザーがアクセスできるようになります。 -- term: ブランチをプッシュする + To push means to send your committed changes to a remote repository on + GitHub.com. For instance, if you change something locally, you can push those changes so that others may access them. +- term: push a branch description: >- - リモート リポジトリへのブランチのプッシュが成功したら、ローカル ブランチからの変更でリモート ブランチを更新します。"ブランチをプッシュする" と、Git では、リモート リポジトリ内にあるブランチの HEAD ref の検索と、それがブランチのローカル HEAD ref の直接の先祖であることの検証が行われます。検証されると、Git によって、すべてのオブジェクト (ローカル HEAD ref から到達可能で、リモート リポジトリにはないもの) がリモート オブジェクト データベースにプルされて、リモート HEAD ref が更新されます。リモート HEAD がローカル HEAD の先祖ではない場合、プッシュは失敗です。 -- term: プッシュ アクセス - description: 書き込みアクセスの同義語。 -- term: 読み取りアクセス + When you successfully push a branch to a remote repository, you update the remote branch with changes from your local branch. When you "push a branch", Git will search for the branch's HEAD ref in the remote repository and verify that it is a direct ancestor to the branch's local HEAD ref. Once verified, Git pulls all objects (reachable from the local HEAD ref and missing from the remote repository) into the remote object database and then updates the remote HEAD ref. If the remote HEAD is not an ancestor to the local HEAD, the push fails. +- term: push access + description: A synonym for write access. +- term: read access description: >- - リポジトリでの権限レベル。これにより、ユーザーは、リポジトリからの情報のプルや読み取りが許可されます。読み取りアクセスは、すべてのパブリック リポジトリによって、すべての GitHub ユーザーに付与されます。プル アクセスの同義語。 + A permission level on a repository that allows the user to pull, or read, + information from the repository. All public repositories give read access to + all GitHub users. A synonym for pull access. - term: README - description: リポジトリ内のファイルに関する情報を含むテキスト ファイル。通常、リポジトリの訪問者に表示される最初のファイルです。README ファイルは、リポジトリ ライセンス、投稿ガイドライン、行動規範とともに、期待値の共有や、プロジェクトへのコントリビューションの管理に役立ちます。 -- term: リベース + description: A text file containing information about the files in a repository that is typically the first file a visitor to your repository will see. A README file, along with a repository license, contribution guidelines, and a code of conduct, helps you share expectations and manage contributions to your project. +- term: rebase description: >- - ブランチからの複数の変更を別のベースに再適用して、そのブランチの HEAD を結果にリセットすること。 -- term: リカバリー コード - description: GitHub アカウントへのアクセスを再取得できるようにするコード。 + To reapply a series of changes from a branch to a different base, and reset + the HEAD of that branch to the result. +- term: recovery code + description: A code that helps you regain access to your GitHub account. - term: release - description: ソフトウェアをパッケージ化してユーザーに提供する、GitHub での方法。 -- term: リモート + description: GitHub's way of packaging and providing software to your users. +- term: remote description: >- - これは、サーバー上 (ほとんどの場合 GitHub.com) でホストされるリポジトリまたはブランチのバージョンのことです。リモート バージョンは、ローカルのクローンに接続できるので、変更を同期させることができます。 -- term: リモート リポジトリ + This is the version of a repository or branch that is hosted on a server, most likely + GitHub.com. Remote versions can be connected to local clones so that changes can be + synced. +- term: remote repository description: >- - 同じプロジェクトの追跡に使用されるが、別の場所にあるリポジトリ。 -- term: リモート URL + A repository that is used to track the same project but resides somewhere + else. +- term: remote URL description: >- - コードが格納されている場所。GitHub 上のリポジトリや別のユーザーのフォークという場合もあれば、別のサーバーという場合もあります。 -- term: レプリカ (replica) + The place where your code is stored: a repository on GitHub, another user's + fork, or even a different server. +- term: replica description: >- - GitHub Enterprise のプライマリ インスタンスに対して冗長性を与える GitHub Enterprise インスタンス。 + A GitHub Enterprise instance that provides redundancy for the primary GitHub + Enterprise instance. - term: repository description: >- - リポジトリは、GitHub の最も基本的な要素です。プロジェクトのフォルダーと考えるのが最もわかりやすいでしょう。1 つのリポジトリには、すべてのプロジェクト ファイル (ドキュメントを含みます) が含まれ、各ファイルのリビジョン履歴が格納されます。リポジトリは、複数のコラボレーターが参加することができ、パブリックとプライベートのどちらにもすることができます。 -- term: リポジトリのキャッシュ + A repository is the most basic element of GitHub. They're easiest to imagine + as a project's folder. A repository contains all of the project files + (including documentation), and stores each file's revision history. + Repositories can have multiple collaborators and can be either public or + private. +- term: repository cache description: >- - 分散チームと CI クライアントの近くに配置される、GitHub Enterprise サーバー インスタンスのリポジトリの読み取り専用ミラー。 -- term: リポジトリ グラフ - description: リポジトリのデータの視覚的表現。 -- term: リポジトリ メンテナ + A read-only mirror of repositories for your GitHub Enterprise server instance, located near + distributed teams and CI clients. +- term: repository graph + description: A visual representation of your repository's data. +- term: repository maintainer description: >- - リポジトリを管理するユーザー。このユーザーは、リポジトリの作業を管理するために、issue のトリアージや、ラベルなどの機能の使用の支援を行うことができます。また、このユーザーには、README の維持管理や、ファイルを最新の状態に保つ責任もあります。 -- term: pull request レビュー必須 + Someone who manages a repository. This person may help triage issues and use labels and other features to manage the work of the repository. This person may also be responsible for keeping the README and contributing files updated. +- term: required pull request review description: >- - 必須レビューを行うと、コラボレーターが保護されたブランチに対して変更を加える前に、pull request 内のレビューが少なくとも 1 つは確実に承認済みになります。 -- term: ステータス チェック必須 + Required reviews ensure that pull requests have at least one approved review + before collaborators can make changes to a protected branch. +- term: required status check description: >- - pull request に対するチェック。これを行うと、コラボレーターが保護されたブランチに対して変更を加える前に、すべての必須 CI テストに確実に合格します。 + Checks on pull requests that ensure all required CI tests are passing before + collaborators can make changes to a protected branch. - term: resolve - description: 失敗した自動マージで実行されなかったものを手動で修正するアクション。 -- term: 打ち消し + description: The action of fixing up manually what a failed automatic merge left behind. +- term: revert description: >- - GitHub 上で pull request を打ち消すと、新しい pull request が自動的に開きます。これには、マージされた元の pull request からのマージ コミットを打ち消すコミットが 1 つ含まれます。Git では、コミットを打ち消すには "git revert" を使います。 -- term: レビュー + When you revert a pull request on GitHub, a new pull request is automatically opened, which has one commit that reverts the merge commit + from the original merged pull request. In Git, you can revert commits with `git revert`. +- term: review description: >- - レビューでは、リポジトリへのアクセスを持つ他のユーザーが、pull request 内で提案されている変更についてコメントしたり、変更を承認したり、その pull request がマージされる前にさらに変更をリクエストしたりすることができます。 -- term: ルート ディレクトリ - description: 階層内の最初のディレクトリ。 -- term: ルート ファイルシステム - description: 基本オペレーティング システムと GitHub Enterprise アプリケーション環境。 -- term: 返信テンプレート + Reviews allow others with access to your repository to comment on the changes proposed in pull + requests, approve the changes, or request further changes before the pull + request is merged. +- term: root directory + description: The first directory in a hierarchy. +- term: root filesystem + description: The base operating system and the GitHub Enterprise application environment. +- term: saved reply description: >- - 自分の GitHub ユーザー アカウントに保存したり追加したりすることで、GitHub のあらゆる場所で、issue や pull request に使うことができるコメント。 + A comment you can save and add to your GitHub user account so that you can + use it across GitHub in issues and pull requests. - term: scope description: >- - OAuth App からリクエストできる、パブリック データと非パブリック データの両方へのアクセスの権限を、グループとして名前を付けたもの。 -- term: シート + Named groups of permissions that an OAuth App can request to access both + public and non-public data. +- term: seat description: >- - GitHub Enterprise の Organization 内のユーザー。これは、"シート数" と呼ばれることがあります。 -- term: シークレット チーム + A user within a GitHub Enterprise organization. This may be referred to as + "seat count." +- term: secret team description: >- - チームの他のユーザーと、オーナー権限を持つユーザーにのみ表示されるチーム。 -- term: セキュリティ ログ + A team that is only visible to the other people on the team and people with owner + permissions. +- term: security log description: >- - 最新の 50 個のアクションまたは過去 90 日間に実行されたアクションを一覧表示するログ。 -- term: server-to-server リクエスト + A log that lists the last 50 actions or those performed within the last 90 + days. +- term: server-to-server request description: >- - 特定のユーザーとは無関係に、ボットとして機能するアプリケーションで使用される API 要求。たとえば、スケジュールどおりに実行され、長時間アクティビティがないと issue をクローズするアプリケーションなどがあります。このタイプの認証を使うアプリケーションでは、ライセンスされた GitHub アカウントを使わないため、特定の数のライセンスの使用が許可されているお支払いプランの Enterprise では、server-to-server ボットに GitHub ライセンスを 1 つも使いません。server-to-server リクエストに使うトークンは、[GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app) 経由でプログラムによって取得します。「[user-to-server リクエスト](#user-to-server-request)」も参照してください。 -- term: サービス フック + An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via [the GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app). See also, "[user-to-server request](#user-to-server-request)." +- term: service hook description: >- - "Webhook" とも呼ばれます。 Webhook を使うと、特定のアクションがリポジトリまたは Organization で発生した場合に、外部の Web サーバーへ通知を送信できます。 -- term: シングル サインオン + Also called "webhook." Webhooks provide a way for notifications to be + delivered to an external web server whenever certain actions occur on a + repository or organization. +- term: single sign-on description: >- - SSO とも呼ばれます。1 つの場所 (ID プロバイダー (IdP)) へのサインインをユーザーに許可してから、そのユーザーに他のサービス プロバイダーへのアクセス権を付与します。 -- term: スナップショット - description: ある時点での仮想マシンのチェックポイント。 + Also called SSO. Allows users to sign in to a single location - an identity + provider (IdP) - that then gives the user access to other service providers. +- term: snapshot + description: A checkpoint of a virtual machine at a point in time. - term: squash - description: 複数のコミットを結合して 1 つのコミットにすること。Git コマンドとしても使います。 -- term: SSH キー + description: To combine multiple commits into a single commit. Also a Git command. +- term: SSH key description: >- - SSH キーは、暗号化したメッセージを使って、オンライン サーバーに対して自分自身を識別する方法です。自分のコンピューターに別のサービス用の独自の一意のパスワードが設定されているかのように見えます。{% data variables.product.product_name %} では、SSH キーを使って、コンピューターへの情報の転送が安全に行われます。 -- term: ステージング インスタンス + SSH keys are a way to identify yourself to an online server, using an encrypted message. It's as if your computer has its own unique password to another service. {% data variables.product.product_name %} uses SSH keys to securely transfer information to your computer. +- term: staging instance description: >- - 変更を実際の GitHub Enterprise インスタンスに適用する前にテストする方法。 + A way to test modifications before they are applied to your actual GitHub + Enterprise instance. - term: status description: >- - コミットがコントリビューション先のリポジトリに設定されている条件を満たしていることの、pull request 内での視覚的な表現。 -- term: ステータス チェック + A visual representation within a pull request that your commits meet the + conditions set for the repository you're contributing to. +- term: status checks description: >- - ステータス チェックとは、リポジトリにコミットするたびに実行される継続的インテグレーションのビルドのような、外部のプロセスです。詳しくは、「[ステータス チェックについて](/articles/about-status-checks)」を参照してください。 -- term: 星 + Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[About status checks](/articles/about-status-checks)." +- term: star description: >- - リポジトリのブックマークまたは感謝の表現。星は、プロジェクトの人気をランク付けするための手動の方法です。 + A bookmark or display of appreciation for a repository. Stars are a manual + way to rank the popularity of projects. - term: subscription - description: ユーザーまたは Organization の GitHub プラン。 -- term: チーム + description: A user or organization's GitHub plan. +- term: team description: >- - Organization メンバーのグループ。アクセス権限とメンションのカスケードを使って、会社やグループの構造を反映します。 -- term: チーム メンテナ + A group of organization members that reflect your company or group's + structure with cascading access permissions and mentions. +- term: team maintainer description: >- - チームを管理するために Organization オーナーが行使できる権限のサブセットが付与された Organization メンバー。 -- term: Team プラン + Organization members that have a subset of permissions available to + organization owners to manage teams. +- term: Team plan description: >- - パブリック リポジトリとプライベート リポジトリを無制限に利用できる Organization のお支払いプラン。 -- term: タイムライン - description: pull request 内またはユーザー プロファイル上の一連のイベント。 -- term: トピック ブランチ + An organization billing plan that gives you unlimited public and private + repositories. +- term: timeline + description: A series of events in a pull request or on a user profile. +- term: topic branch description: >- - 開発の分野を概念的に分類したものを識別するために開発者が使う、通常の Git ブランチ。ブランチは非常に簡単で低コストなので、小さなブランチを複数用意して、それぞれのブランチに、明確に定義した概念、小さな増分、関連する変更を含めるのがよいでしょう。機能ブランチとも呼ばれます。 + A regular Git branch that is used by a developer to identify a conceptual + line of development. Since branches are very easy and inexpensive, it is + often desirable to have several small branches that each contain very well + defined concepts or small incremental yet related changes. Can also be called a feature branch. - term: topics description: >- - Git Hub で、特定の対象分野のリポジトリを探索したり、コントリビューション先となるプロジェクトを見つけたり、特定の問題への新しい解決方法を発見したりするための方法。 -- term: トラフィック グラフ + A way to explore repositories in a particular subject area, find projects to + contribute to, and discover new solutions to a specific problem on GitHub. +- term: traffic graph description: >- - フル クローン (フェッチではなく)、過去 14 日間の訪問者数、参照サイト数、人気のコンテンツなど、リポジトリのトラフィックを示すリポジトリ グラフ。 -- term: 転送 + A repository graph that shows a repository's traffic, including full clones + (not fetches), visitors from the past 14 days, referring sites, and popular + content. +- term: transfer description: >- - リポジトリの転送には、リポジトリのオーナーの変更という意味があります。新しいオーナーは、リポジトリのコンテンツ、issue、pull request、リリース、設定の管理をすぐに行うことができるようになります。 -- term: 上流 + To transfer a repository means to change the owner of a repository. The new owner will be able to + immediately administer the repository's contents, issues, pull requests, + releases, and settings. +- term: upstream description: >- - ブランチまたはフォークについて説明する場合、元のリポジトリにあるプライマリ ブランチは、他の変更の主な発生源となるため、"上流" と呼ばれることがよくあります。そのため、ユーザーが作業するブランチやフォークは、"下流" と呼ばれます。origin とも呼ばれます。 -- term: 上流ブランチ + When talking about a branch or a fork, the primary branch on the original + repository is often referred to as the "upstream", since that is the main + place that other changes will come in from. The branch/fork you are working + on is then called the "downstream". Also called origin. +- term: upstream branch description: >- - あるブランチにマージされる既定のブランチ (または、そのブランチのリベース先のブランチ)。"branch..remote" と "branch..merge" を使って構成されます。A の上流ブランチが origin/B だとすると、"A は origin/B を追跡している" という言い方をすることがあります。 + The default branch that is merged into the branch in question (or the branch + in question is rebased onto). It is configured via `branch..remote` and + `branch..merge`. If the upstream branch of A is origin/B sometimes we + say "A is tracking origin/B". - term: user description: >- - ユーザーとは、個人用 GitHub アカウントを持つユーザーのことです。ユーザーはそれぞれ、個人用プロフィールを持っており、リポジトリ (パブリックとプライベートのどちらでも) を複数所有できます。Organization を作成したり、Organization に招待されて参加したり、別のユーザーのリポジトリでコラボレーションしたりすることもできます。 + Users are people with personal GitHub accounts. Each user has a personal profile, and + can own multiple repositories, public or private. They can create or be + invited to join organizations or collaborate on another user's repository. - term: username - description: GitHub 上でのユーザーのハンドル。 -- term: user-to-server リクエスト + description: A user's handle on GitHub. +- term: user-to-server request description: >- - 特定のユーザーの代わりにタスクを実行するアプリケーションで使用される API 要求。user-to-server 認証でタスクが実行された場合、GitHub には、ユーザーによってアプリケーション経由で実行済みとして表示されます。たとえば、サードパーティ アプリケーションから issue を作成すると、GitHub 上では、ユーザーの代わりにそのアプリケーションが issue を作成したことになります。user-to-server リクエストを使った、アプリケーションによる実行が可能なタスクは、アプリとユーザーの両方の権限とアクセスによって範囲が制限されます。user-to-server リクエストで使用されるトークンは、OAuth を介して取得します。詳しくは、「[GitHub アプリのユーザーを特定および認可する](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)」を参照してください。 「[server-to-server リクエスト](#server-to-server-request)」も参照してください。 -- term: 参照可能なチーム - description: どの Organization メンバーにも表示され、@メンションできるチーム。 + An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." See also, "[server-to-server request](#server-to-server-request)." +- term: visible team + description: A team that can be viewed and @mentioned by every organization member. - term: watch description: >- - リポジトリや issue を watch すると、issue や pull request が更新されるたびに通知を受け取ることができます。 -- term: watch 対象の通知 - description: ユーザーがサブスクライブしているリポジトリでのアクティビティについての通知。 -- term: Web 通知 + You can watch a repository or issue to receive notifications when updates are made to an issue or pull request. +- term: watching notifications + description: A notification about activity in a repository a user has subscribed to. +- term: web notifications description: >- - GitHub の Web インターフェイス (https://github.com/notifications) に表示される通知 + Notifications displayed in the web interface on GitHub: + https://github.com/notifications - term: webhooks description: >- - Webhook を使うと、GitHub.com の特定のイベントをサブスクライブする GitHub Apps をビルドまたはセットアップできます。Webhook を使うと、特定のアクションがリポジトリまたは Organization で発生した場合に、外部の Web サーバーへ通知を送信できます。サービス フックとも呼ばれます。 -- term: 書き込みアクセス + Webhooks allow you to build or set up GitHub Apps which subscribe to certain + events on GitHub.com. Webhooks provide a way for notifications to be + delivered to an external web server whenever certain actions occur on a + repository or organization. Also called a service hook. +- term: write access description: >- - リポジトリへの変更のプッシュ、書き込み、変更をユーザーに許可する、リポジトリでの権限レベル。 + A permission level on a repository that allows the user to push, or write, + changes to the repository. diff --git a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml deleted file mode 100644 index 8820c19067..0000000000 --- a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml +++ /dev/null @@ -1,117 +0,0 @@ -- title: パッケージのバージョン削除へのアクセス - description: このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。 - toggled_by: ':package-deletes-preview' - announcement: null - updates: null - toggled_on: - - Mutation.deletePackageVersion - owning_teams: - - '@github/pe-package-registry' -- title: デプロイメント - description: このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。 - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/c2c-actions-service' -- title: MergeInfoPreview - プルリクエストのマージ状態に関する詳細な情報。 - description: このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。 - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。 - description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。 - toggled_by: ':update-refs-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateRefs - - GitRefname - - RefUpdate - - UpdateRefsInput - - UpdateRefsPayload - owning_teams: - - '@github/reponauts' -- title: プロジェクトイベントの詳細 - description: このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。 - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- title: コンテンツ添付ファイルの作成 - description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。 - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/feature-lifecycle' -- title: ラベルのプレビュー - description: このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。 - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- title: プロジェクトのインポート - description: このプレビューは、プロジェクトのインポートのサポートを追加します。 - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- title: Teamレビューの割り当てプレビュー - description: このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します - toggled_by: ':stone-crop-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateTeamReviewAssignment - - UpdateTeamReviewAssignmentInput - - TeamReviewAssignmentAlgorithm - - Team.reviewRequestDelegationEnabled - - Team.reviewRequestDelegationAlgorithm - - Team.reviewRequestDelegationMemberCount - - Team.reviewRequestDelegationNotifyTeam - owning_teams: - - '@github/pe-pull-requests' \ No newline at end of file diff --git a/translations/ja-JP/data/learning-tracks/code-security.yml b/translations/ja-JP/data/learning-tracks/code-security.yml index e08d0012c2..3b35eb0a73 100644 --- a/translations/ja-JP/data/learning-tracks/code-security.yml +++ b/translations/ja-JP/data/learning-tracks/code-security.yml @@ -1,25 +1,29 @@ # Feature available only on dotcom security_advisories: - title: 'セキュリティ脆弱性の修正と開示' - description: 'リポジトリ セキュリティ アドバイザリを使用して、報告された脆弱性を非公開で修正し、CVE を取得します。' + title: 'Fix and disclose a security vulnerability' + description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}' guides: - - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - - /code-security/repository-security-advisories/creating-a-repository-security-advisory - - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory - - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability - - /code-security/repository-security-advisories/publishing-a-repository-security-advisory - - /code-security/repository-security-advisories/editing-a-repository-security-advisory - - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory - - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database + - /code-security/security-advisories/global-security-advisories/about-global-security-advisories + - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories + - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory + - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory + - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track dependabot_alerts: - title: 'セキュリティで保護されていない依存関係の通知を受け取る' - description: '依存関係に新しい脆弱性{% ifversion GH-advisory-db-supports-malware %}またはマルウェア{% endif %}が見つかった場合に警告するように Dependabot を設定します。' + title: 'Get notifications for insecure dependencies' + description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.' guides: - /code-security/dependabot/dependabot-alerts/about-dependabot-alerts - - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}' + - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}' - /code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts - /code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates @@ -28,20 +32,20 @@ dependabot_alerts: # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track dependabot_security_updates: - title: '脆弱な依存関係を更新するために pull request を取得する' - description: '新しい脆弱性が報告されたときに pull request を作成する Dependabot を設定する' + title: 'Get pull requests to update your vulnerable dependencies' + description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.' guides: - /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates - /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates - - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}' - - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}' + - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}' + - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}' - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates - - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}' + - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}' # Feature available only on dotcom and GHES 3.3+ dependency_version_updates: - title: '依存関係を最新に保つ' - description: 'Dependabot を使って新しいリリースを確認し、依存関係を更新します。' + title: 'Keep your dependencies up-to-date' + description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.' guides: - /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates - /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates @@ -56,8 +60,8 @@ dependency_version_updates: # Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there. secret_scanning: - title: 'シークレットのスキャン' - description: 'トークン、パスワード、その他のシークレットを誤ってリポジトリにチェックインしないように Secret Scanning を設定します。' + title: 'Scan for secrets' + description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.' guides: - '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}' - '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}' @@ -69,20 +73,20 @@ secret_scanning: # Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions security_alerts: - title: 'セキュリティ アラートの調査と管理' - description: 'セキュリティ アラートの場所と解決方法について説明します。' + title: 'Explore and manage security alerts' + description: 'Learn where to find and resolve security alerts.' guides: - - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/about-the-security-overview {% endif %}' - - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/viewing-the-security-overview {% endif %}' - - '{% ifversion ghec or ghes > 3.1 %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}' - - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}' - - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}' - - '{% ifversion ghec or ghes > 3.1 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}' + - '{% ifversion ghec or ghes %}/code-security/security-overview/about-the-security-overview {% endif %}' + - '{% ifversion ghec or ghes %}/code-security/security-overview/viewing-the-security-overview {% endif %}' + - '{% ifversion ghec or ghes %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}' + - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}' + - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}' + - '{% ifversion ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}' # Feature available in all versions from GHES 2.22 up code_security_actions: - title: 'GitHub Actions で Code Scanning を実行する' - description: '既定のブランチとすべての pull request を確認して、リポジトリに脆弱性とエラーがないようにします。' + title: 'Run code scanning with GitHub Actions' + description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.' featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}' guides: - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning @@ -94,8 +98,8 @@ code_security_actions: # Feature available in all versions from GHES 2.22 up code_security_integration: - title: 'Code Scanning と統合する' - description: 'SARIF を使ってサードパーティ システムから GitHub にコード分析結果をアップロードします。' + title: 'Integrate with code scanning' + description: 'Upload code analysis results from third-party systems to GitHub using SARIF.' guides: - /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning - /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github @@ -104,8 +108,8 @@ code_security_integration: # Feature available in all versions from GHES 2.22 up code_security_ci: - title: 'CI で CodeQL Code Scanning を実行する' - description: '既存の CI 内で CodeQL を設定し、結果を GitHub Code Scanning にアップロードします。' + title: 'Run CodeQL code scanning in your CI' + description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.' guides: - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system @@ -115,8 +119,8 @@ code_security_ci: # Feature available in all versions end_to_end_supply_chain: - title: 'エンド ツー エンドのサプライ チェーン' - description: 'ユーザー アカウント、コード、ビルド プロセスのセキュリティ保護に関する考え方。' + title: 'End-to-end supply chain' + description: 'How to think about securing your user accounts, your code, and your build process.' guides: - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview - /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts diff --git a/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md b/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md index f68aaad4ba..38f1bde189 100644 --- a/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md +++ b/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md @@ -1 +1 @@ -1. For each of your accounts, create a dedicated {% data variables.product.pat_v1 %} with `repo` scope. {% ifversion pat-v2 %}Or, for each of your accounts and for each organization that you are a member of, create a {% data variables.product.pat_v2 %} that can access the desired repositories and that has read and write permissions on repository contents.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." \ No newline at end of file +1. For each of your accounts, create a dedicated {% data variables.product.pat_v1 %} with `repo` scope. {% ifversion pat-v2 %}Or, for each of your accounts and for each organization that you are a member of, create a {% data variables.product.pat_v2 %} that can access the desired repositories and that has read and write permissions on repository contents.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." diff --git a/translations/ja-JP/data/reusables/actions/about-runner-groups.md b/translations/ja-JP/data/reusables/actions/about-runner-groups.md index f3b4dbd192..3df3ae937c 100644 --- a/translations/ja-JP/data/reusables/actions/about-runner-groups.md +++ b/translations/ja-JP/data/reusables/actions/about-runner-groups.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 98ccaf5f02919ebeb19485e3b2237f7c96ebfc3e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 8492ebc0962837c6f748fe30dbca08f529c353fc +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764012" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109090" --- {% ifversion fpt %} {% note %} @@ -20,4 +20,4 @@ ms.locfileid: "147764012" 新しいランナーが作成されると、それらは自動的にデフォルトグループに割り当てられます。 ランナーは一度に1つのグループにのみ参加できます。 ランナーはデフォルトグループから別のグループに移動できます。 詳しくは、「[ランナーをグループに移動する](#moving-a-runner-to-a-group)」をご覧ください。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md index 7f82e808ab..4ebc8f8a39 100644 --- a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md @@ -1,12 +1,20 @@ -| Action | Description +--- +ms.openlocfilehash: 1162ab428d4c20f7f0ca4af8c1ec743b30e42852 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109085" +--- +| アクション | 説明 |------------------|------------------- -| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %} -| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} -| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %} -| `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)." -| `disable_workflow` | Triggered when a workflow is disabled. -| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`. -| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %} -| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %} -| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." -| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." +| `cancel_workflow_run` | ワークフローの実行がキャンセルされたときにトリガーされます。 詳細については、「[ワークフローの取り消し](/actions/managing-workflow-runs/canceling-a-workflow)」を参照してください。 +| `completed_workflow_run` | ワークフローの状態が `completed` に変わったときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳細については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +| `created_workflow_run` | ワークフローの実行が作成されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳細については、「[ワークフローの例を作成する](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。 +| `delete_workflow_run` | ワークフローの実行が削除されたときにトリガーされます。 詳細については、「[ワークフロー実行の削除](/actions/managing-workflow-runs/deleting-a-workflow-run)」を参照してください。 +| `disable_workflow` | ワークフローが無効化されたときにトリガーされます。 +| `enable_workflow` | 以前に `disable_workflow` によって無効にされたワークフローが有効にされたときにトリガーされます。 +| `rerun_workflow_run` | ワークフローの実行が再実行されたときにトリガーされます。 詳細については、[ワークフローの再実行](/actions/managing-workflow-runs/re-running-a-workflow)に関するページを参照してください。 +| `prepared_workflow_job` | ワークフロージョブが開始されたときにトリガーされます。 ジョブに渡されたシークレットのリストを含みます。 REST API を使ってのみ表示できます。 これは、{% data variables.product.prodname_dotcom %} Web インターフェイスでは表示されず、JSON/CSV エクスポートにも含まれません。 詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 +| `approve_workflow_job` | ワークフロー ジョブが承認されたときにトリガーされます。 詳細については、「[デプロイの確認](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。 +| `reject_workflow_job` | ワークフロー ジョブが拒否されたときにトリガーされます。 詳細については、「[デプロイの確認](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md b/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md index 94bc82faad..61fdac58ca 100644 --- a/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md +++ b/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 7020f9ed86843200a1b56c9b9142ed238aaf0dd5 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 955bbcc4f03b8a3a810f282c74230f220908f6b8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764016" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109084" --- 使用可能なオプションのリストから、オペレーティング システムとハードウェア構成を選ぶことができます。 このランナーの新しいインスタンスが自動スケーリングによってデプロイされると、ここで定義したオペレーティング システムとハードウェア構成が使用されます。 -また、ランナーを識別するラベルを定義することもできます。これは、処理のためにワークフローを使ってランナーにジョブを送信する方法です (`runs-on` を使います)。 新しいランナーが既定のグループに自動的に割り当てられるか、ランナー作成プロセス中にランナーを結合する必要があるグループを選ぶことができます。 また、ランナーを登録した後で、ランナーのグループ メンバーシップを変更できます。 詳しくは、「[{% data variables.actions.hosted_runner %}へのアクセスの制御](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)」を参照してください。 \ No newline at end of file +また、ランナーを識別するラベルを定義することもできます。これは、処理のためにワークフローを使ってランナーにジョブを送信する方法です (`runs-on` を使います)。 新しいランナーが既定のグループに自動的に割り当てられるか、ランナー作成プロセス中にランナーを結合する必要があるグループを選ぶことができます。 また、ランナーを登録した後で、ランナーのグループ メンバーシップを変更できます。 詳しくは、「[{% data variables.actions.hosted_runner %}へのアクセスの制御](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/add-hosted-runner.md b/translations/ja-JP/data/reusables/actions/add-hosted-runner.md index e3d2580d6b..809ed2ad54 100644 --- a/translations/ja-JP/data/reusables/actions/add-hosted-runner.md +++ b/translations/ja-JP/data/reusables/actions/add-hosted-runner.md @@ -1,19 +1,11 @@ ---- -ms.openlocfilehash: 216386e3e7dc31df99a383af6a335681c72911c2 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764046" ---- -1. **[新しいランナー]** をクリックしたら、 **[{% octicon "mark-github" aria-label="New hosted runner" %} 新しい Github ホステッド ランナー]** をクリックします。 -1. 必要な詳細を入力して、新しいランナーを構成します。 +1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**. +1. Complete the required details to configure your new runner: - - **名前**: 新しいランナーの名前を入力します。 識別しやすくするには、ハードウェアとオペレーティング システム (`ubuntu-20.04-16core` など) を示しておくのがよいでしょう。 - - **ランナー イメージ**: 使用可能なオプションからオペレーティング システムを選びます。 オペレーティング システムを選ぶと、特定のバージョンを選ぶことができるようになります。 - - **ランナーのサイズ**: 使用可能なオプションのドロップダウン リストからハードウェア構成を選びます。 - - **自動スケーリング**: いつでもアクティブにすることができるランナーの最大数を選びます。 - - **ランナー グループ**: ランナーがメンバーとなるグループを選びます。 需要に合わせてスケールアップまたはスケールダウンしながら、このグループによって、ランナーのインスタンスが複数ホストされます。 - - **ネットワーク**: {% data variables.product.prodname_ghe_cloud %} の場合のみ、静的 IP アドレス範囲を {% data variables.actions.hosted_runner %} のインスタンスに割り当てるかどうかを選びます。 合計で最大 10 個の静的 IP アドレスを使うことができます。 + - **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`. + - **Runner image**: Choose an operating system from the available options. Once you've selected an operating system, you will be able to choose a specific version. + - **Runner size**: Choose a hardware configuration from the drop-down list of available options. + - **Auto-scaling**: Choose the maximum number of runners that can be active at any time. + - **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand. + - **Networking**: Only for {% data variables.product.prodname_ghe_cloud %}: Choose whether a static IP address range will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 static IP addresses in total. -1. **[ランナーの作成]** をクリックします。 \ No newline at end of file +1. Click **Create runner**. diff --git a/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md b/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md index 8a442f263c..79fdada0e7 100644 --- a/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md +++ b/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 39b0767cfd400a12b2fb2d6709e2588dce9be503 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 4e8c79051e378c800568f0fcf36c783a1bdd8811 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147763997" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109078" --- 構成スクリプトを使うと、新しいランナーをグループに自動的に追加できます。 たとえば、このコマンドを実行すると、新しいランナーが登録されて、`--runnergroup` パラメーターを使って `rg-runnergroup` という名前のグループに追加されます。 @@ -16,4 +16,4 @@ ms.locfileid: "147763997" ``` Could not find any self-hosted runner group named "rg-runnergroup". -``` \ No newline at end of file +``` diff --git a/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md b/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md index cd60712e46..6fe8813540 100644 --- a/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md +++ b/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md @@ -35,4 +35,4 @@ You can configure a runner group to run either selected workflows or all workflo 1. Click **Save**. -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md b/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md index 7bf82cfc33..3a5df8fce0 100644 --- a/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md +++ b/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md @@ -6,4 +6,4 @@ {% elsif ghae < 3.4 or ghes < 3.4 %} {% data reusables.actions.configure-runner-group %} 1. Change the runner group name. -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md b/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md index bb19db9e3b..afe2577607 100644 --- a/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md +++ b/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md @@ -35,4 +35,4 @@ When creating a group, you must choose a policy that defines which repositories{ ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png) 1. Click **Save group** to create the group and apply the policy. -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md index 6b17543e34..1c7693f8ea 100644 --- a/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md +++ b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md @@ -3,4 +3,4 @@ If you have an **HTTP Proxy Server** configured on {% data variables.location.pr - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. - If your external storage location is not routable, then you must also add your external storage URL to the exclusion list. - For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." \ No newline at end of file + For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." diff --git a/translations/ja-JP/data/reusables/actions/github_sha_description.md b/translations/ja-JP/data/reusables/actions/github_sha_description.md index c06ad90ef7..bd4d1f95a3 100644 --- a/translations/ja-JP/data/reusables/actions/github_sha_description.md +++ b/translations/ja-JP/data/reusables/actions/github_sha_description.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 6d59b7ddcb233704ff06531143d1f2d7126f874b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b362ff01387cbd9a70aeeceb51bff2b48f776bb9 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147614570" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109763" --- -ワークフローをトリガーしたコミット SHA。 このコミット SHA の値は、ワークフローをトリガーしたイベントによって異なります。 詳細については、「[ワークフローをトリガーするイベント](/actions/using-workflows/events-that-trigger-workflows)」を参照してください。 たとえば、「 `ffac537e6cbbf934b08745a378932722df287a53` 」のように入力します。 \ No newline at end of file +ワークフローをトリガーしたコミット SHA。 このコミット SHA の値は、ワークフローをトリガーしたイベントによって異なります。 詳細については、「[ワークフローをトリガーするイベント](/actions/using-workflows/events-that-trigger-workflows)」を参照してください。 たとえば、「 `ffac537e6cbbf934b08745a378932722df287a53` 」のように入力します。 diff --git a/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md b/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md index 7c628b0e8d..e664e58554 100644 --- a/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md +++ b/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 7da9bbc78d15f92478a3d67e7bfd195a5635d500 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 2ce890fe0439b1030ce00041ff72cd98aeca73db +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147763988" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109764" --- {% warning %} **警告**: {% data reusables.actions.hosted-runner-security %} -{% endwarning %} \ No newline at end of file +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/actions/message-parameters.md b/translations/ja-JP/data/reusables/actions/message-parameters.md index 3306182ff0..2d37cc50dd 100644 --- a/translations/ja-JP/data/reusables/actions/message-parameters.md +++ b/translations/ja-JP/data/reusables/actions/message-parameters.md @@ -1,9 +1,8 @@ ---- -ms.openlocfilehash: bbc3a414d8a29780d8df51bd14b9f8a5843a6c4b -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147885509" ---- -| パラメーター | 値 | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | カスタム タイトル |{% endif %} | `file` | ファイル名 | | `col` | 1 から始まる列番号 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | 終了列番号 |{% endif %} | `line` | 1 から始まる行番号 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | 終了行番号 |{% endif %} +| Parameter | Value | +| :- | :- | +| `title` | Custom title | +| `file` | Filename | +| `col` | Column number, starting at 1 | +| `endColumn` | End column number | +| `line` | Line number, starting at 1 | +| `endLine` | End line number | diff --git a/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md b/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md index ec13c86d5d..f3b008579a 100644 --- a/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md +++ b/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md @@ -1,18 +1,5 @@ ---- -ms.openlocfilehash: 0a3393009a2dcd812f5b20e3cdd1b160aee69d5e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147168309" ---- -インスタンスのユーザーに対して {% data variables.product.prodname_actions %} を有効にする予定の場合は、さらに多くのリソースが必要です。 +If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required. -{%- ifversion ghes = 3.2 %} - -{% data reusables.actions.hardware-requirements-3.2 %} - -{%- endif %} {%- ifversion ghes = 3.3 %} @@ -32,4 +19,4 @@ ms.locfileid: "147168309" {%- endif %} -これらの要件の詳細については、「[{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} の概要](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)」を参照してください。 +For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." diff --git a/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md b/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md index 61a617e79c..f0d634cbeb 100644 --- a/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md +++ b/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md @@ -12,4 +12,4 @@ If you don't specify a runner group during the registration process, your new ru ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) 3. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md b/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md index 2f057111e0..2a33557252 100644 --- a/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md +++ b/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 62e8c6a4133d8402083e84402453b5fb6820bac3 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: d3eda8a12037f1da8ec915c4652fa658f34fcc6b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764049" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109751" --- ランナーは、そのグループが削除されると自動的に既定のグループに戻ります。 @@ -13,4 +13,4 @@ ms.locfileid: "147764049" 2. グループを削除するには、 **[グループの削除]** をクリックします。 3. 確認プロンプトを確認し、 **[Remove this runner group]\(このランナー グループの削除\)** をクリックします。 このグループのすべてのランナーは、既定のグループに自動的に移動します。ここでは、このグループに割り当てられたアクセス許可を継承します。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md b/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md index 425c274aac..9c38d882bf 100644 --- a/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md +++ b/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 3e11d726bb45f2a291ea7fbae4d10770cd505eaf -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 761cee3710852bda8e1f36d47da475e2c6d6b130 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147763976" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109746" --- ランナー グループは、Organization レベルと Enterprise レベルのランナーへのアクセスを制御するために使用されます。 Enterprise の所有者はアクセス ポリシーを設定して、Enterprise 内のどの Organization {% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}がランナー グループにアクセスできるかを制御できます。 Organization の所有者はアクセス ポリシーを設定して、Organization 内のどのリポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}がランナー グループにアクセスできるかを制御できます。 -Enterprise の所有者がランナー グループにアクセス権を付与する場合、Organization の所有者には、Organization のランナー設定に一覧表示されているランナー グループが表示されます。 その後、Organization の所有者は、リポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}の詳細な追加アクセス ポリシーを、Enterprise ランナー グループに割り当てることができます。 \ No newline at end of file +Enterprise の所有者がランナー グループにアクセス権を付与する場合、Organization の所有者には、Organization のランナー設定に一覧表示されているランナー グループが表示されます。 その後、Organization の所有者は、リポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}の詳細な追加アクセス ポリシーを、Enterprise ランナー グループに割り当てることができます。 diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md index 4800d4e61d..f6fa64f23f 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md @@ -1,12 +1,6 @@ ---- -ms.openlocfilehash: 80d40b1947f72a35fad5cf4cfb69f7ce68d28eab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147558376" ---- -{%- ifversion fpt or ghec or ghes > 3.6 %} セルフホストランナーは、{% data variables.product.prodname_actions %} に 14 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。 -エフェメラル セルフホストランナーは、{% data variables.product.prodname_actions %} に 1 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。 -{%- elsif ghae or ghes < 3.7 %} セルフホストランナーは、{% data variables.product.prodname_actions %} に 30 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。 -{%- endif %} \ No newline at end of file +{%- ifversion fpt or ghec or ghes > 3.6 %} +A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days. +An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day. +{%- elsif ghae or ghes < 3.7 %} +A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days. +{%- endif %} diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md index ed65924082..dfc9f74cbb 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: bf779905fbb6aa54c5719b4e1046e6e24fc8ad85 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 8c2084dcfcee3042fd067f1e82138875724c59ac +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147764240" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109740" --- {% warning %} @@ -12,4 +12,4 @@ ms.locfileid: "147764240" 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)に関する記述をご覧ください。 -{% endwarning %} \ No newline at end of file +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md index b2cc85cb56..4a290bd07a 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 61eed0176c65b4e7b691b69b68e32032ea3ee3eb -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 518c31dffd71180ff4733f98ba7df3d5fe6028d9 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147763797" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109739" --- -セルフホストランナーは、プライベートリポジトリでのみ利用することをおすすめします。 これは、ワークフロー内でコードを実行する pull request を作成することで、パブリック リポジトリのフォークによって、セルフホステッド ランナー マシン上で危険なコードが実行される可能性があるからです。 \ No newline at end of file +セルフホストランナーは、プライベートリポジトリでのみ利用することをおすすめします。 これは、ワークフロー内でコードを実行する pull request を作成することで、パブリック リポジトリのフォークによって、セルフホステッド ランナー マシン上で危険なコードが実行される可能性があるからです。 diff --git a/translations/ja-JP/data/reusables/actions/sidebar-secret.md b/translations/ja-JP/data/reusables/actions/sidebar-secret.md index 5fa0f6887b..91d60259f5 100644 --- a/translations/ja-JP/data/reusables/actions/sidebar-secret.md +++ b/translations/ja-JP/data/reusables/actions/sidebar-secret.md @@ -2,4 +2,4 @@ 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **Actions**. {%- else %} 1. In the left sidebar, click **Secrets**. -{%- endif %} \ No newline at end of file +{%- endif %} diff --git a/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md b/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md index e368272fe8..9d41c4d993 100644 --- a/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md +++ b/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md @@ -1 +1 @@ -- **Workflow run time** - {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval.{% else %}Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.{% endif %} +- **Workflow run time** - Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval. diff --git a/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md b/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md index f4a769e189..71eec7290b 100644 --- a/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md +++ b/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: eca31e7c0c729309568cbf6359a27437ce35fbd2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f9f5661230c99fb281c3625972b7e5d0fce98963 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147683812" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108815" --- {% note %} **メモ:** 現在、ブロックされた push メッセージにリソース リンクを追加する機能はパブリック ベータ版であり、変更される可能性があります。 -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md index 8b6afe3169..f4fc70a9c2 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md @@ -1 +1 @@ -1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. +1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**.{% endif %} diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md index 8aaee97b01..0f675c8f77 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: fffcf27ed7d0b6a175d218436989af63172b5d2b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145113990" ---- -1. [{% data variables.product.prodname_secret_scanning_caps %}] の [カスタム パターン] で、{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **[新しいパターン]** {% elsif ghes = 3.2 %} **[新しいカスタム パターン]** をクリックします{% endif %}。 +1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click **New pattern**. diff --git a/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md b/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md index 38de8f9835..5128ffbc03 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 7b51303370d46101100bc953a25193ea3d14d032 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 +ms.openlocfilehash: ce590bb087145ff4abfb195d7257c614464c2b19 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884422" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109727" --- 1. [監査ログ] で、 **[データ保持の監査]** をクリックします。 - ![[データ保持の監査] タブのスクリーンショット](/assets/images/help/enterprises/audit-data-retention-tab.png) \ No newline at end of file + ![[データ保持の監査] タブのスクリーンショット](/assets/images/help/enterprises/audit-data-retention-tab.png) 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 a135b85355..f6f3bf77d0 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 @@ -33,12 +33,11 @@ {%- 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 %} | +| | `dependabot_alerts` | 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 %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." | `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 %} +{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | 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)." | `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 %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md index a41b568841..a5b8769233 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md @@ -7,8 +7,6 @@ | `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`. | `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | `workflows.rerun_workflow_run` | A workflow run was re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)." -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `workflows.completed_workflow_run` | A workflow status changed to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history). | `workflows.created_workflow_run` | A workflow run was created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)." | `workflows.prepared_workflow_job` | A workflow job was started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." -{%- endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md b/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md index a3709f54be..11a875bdb9 100644 --- a/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md +++ b/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: a17c50cfb04b759fe451f686129f86bb4b22fcff -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6b7d1cd8cae2ecd6688a1a5d41d7bda03d8e8d97 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424871" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109651" --- {% ifversion git-events-audit-log %} {% note %} **注:** Git イベントは検索結果に含まれません。 -{% endnote %} {% endif %} \ No newline at end of file +{% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md b/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md index 78b626948e..976ff3a514 100644 --- a/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md +++ b/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: e52e6f55f04b57e1b1f8a8d044b4651b69e2caf5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6e4387a1736c320dbef802ea07c22dfc1fa091a6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147080077" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109275" --- 1. {% data variables.product.prodname_dotcom %} で Amazon S3 エンドポイントに接続して書き込めることを確認するには、 **[Check endpoint]\(エンドポイントのチェック\)** をクリックします。 - ![エンドポイントをチェックする](/assets/images/help/enterprises/audit-stream-check.png) \ No newline at end of file + ![エンドポイントをチェックする](/assets/images/help/enterprises/audit-stream-check.png) diff --git a/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md b/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md index 9de52f7e09..45e69049f0 100644 --- a/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md +++ b/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 67009b930a04da090718919ea104317809515027 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c8ea836ffb23f1d69d2a42c5204143442480eafa +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147080074" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109244" --- 1. **[Configure stream]\(ストリームの構成\)** ドロップダウンを選び、 **[Amazon S3]** をクリックします。 - ![ドロップダウン メニューから [Amazon S3] を選択する](/assets/images/help/enterprises/audit-stream-choice-s3.png) \ No newline at end of file + ![ドロップダウン メニューから [Amazon S3] を選択する](/assets/images/help/enterprises/audit-stream-choice-s3.png) diff --git a/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md b/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md index 3dc6aa2725..295a63f256 100644 --- a/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md +++ b/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 430ca2e9df62f3bfc869356e5ff58c6170119d77 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 44593ccc9877d4cb1a224122f7c1dd9695db27f6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147763996" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109243" --- -| Linux | 4 | $0.016 | | Linux | 8 | $0.032 | | Linux | 16 | $0.064 | | Linux | 32 | $0.128 | | Linux | 64 | $0.256 | | Windows | 8 | $0.064 | | Windows | 16 | $0.128 | | Windows | 32 | $0.256 | | Windows | 64 | $0.512 | \ No newline at end of file +| Linux | 4 | $0.016 | | Linux | 8 | $0.032 | | Linux | 16 | $0.064 | | Linux | 32 | $0.128 | | Linux | 64 | $0.256 | | Windows | 8 | $0.064 | | Windows | 16 | $0.128 | | Windows | 32 | $0.256 | | Windows | 64 | $0.512 | diff --git a/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md b/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md index 242d8e3c1e..7f8f459e7c 100644 --- a/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md +++ b/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: 599e48d3a38c855896fac842f5c8b4833488aeae -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147063737" ---- -Java、C、C++、C# などのコンパイルされた言語の場合、{% data variables.product.prodname_codeql %} はワークフローの実行中に作成されたすべてのコードを分析します。 分析するコードの量を制限するには、`run` ブロックで独自のビルド ステップを指定して、分析するコードのみをビルドします。 独自のビルド ステップの指定と、`pull_request` イベントや `push` イベントでの `paths` フィルターまたは `paths-ignore` フィルターの使用を組み合わせることで、特定のコードが変更されたときにのみワークフローが実行されるようにすることができます。 詳細については、[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)に関するページを参照してください。 +For compiled languages like Java,{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build ony the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)." -ソース コードをコンパイルせずに {% data variables.product.prodname_codeql %} で分析される Go、JavaScript、Python、TypeScript などの言語の場合、追加の設定オプションを指定して分析するコードの量を制限できます。 詳細については、「[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)」(スキャンするディレクトリの指定) を参照してください。 +For languages like{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/analyze-go.md b/translations/ja-JP/data/reusables/code-scanning/analyze-go.md index 432d0add0d..cd600af953 100644 --- a/translations/ja-JP/data/reusables/code-scanning/analyze-go.md +++ b/translations/ja-JP/data/reusables/code-scanning/analyze-go.md @@ -1 +1,9 @@ -For these three languages, {% data variables.product.prodname_codeql %} analyzes the source files in your repository that are built. {% data variables.product.prodname_codeql %} also runs a build for Go projects to set up the project, but then analyzes _all_ Go files in the repository, not just the files that are built. For any of these languages, including Go, you can disable `autobuild` and instead use custom build commands in order to analyze only the files that are built by these custom commands. \ No newline at end of file +--- +ms.openlocfilehash: e9f2162fa5c65d4a59b2bd350aea2b131205f9a6 +ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 09/05/2022 +ms.locfileid: "145113374" +--- +{% data variables.product.prodname_codeql %}は、プロジェクトをセットアップするためにGoのプロジェクトのビルドも実行します。 ただし、他のコンパイル済み言語と対照的に、ビルドされたものだけでなく、リポジトリ内のすべての Go ファイルが抽出されます。 カスタム ビルド コマンドを使用すると、ビルドによって使用されない Go ファイルの抽出をスキップできます。 diff --git a/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md index 60801fcd73..58d3db79d2 100644 --- a/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md +++ b/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d772b6eae7cf42f2635bb427605b6d0626bdad05 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145113358" ---- -サポートされているコンパイル言語の場合、{% data variables.product.prodname_codeql_workflow %} の `autobuild` アクションを使用してコードをビルドできます。 これにより、C/C++、C#、Java についての明示的なビルド コマンドを指定する必要がなくなります。 +For the supported compiled languages, you can use the `autobuild` action in the {% data variables.product.prodname_codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md index 51e34a25ac..c5179a14d9 100644 --- a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md +++ b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 94e76ae2e8580c87d4493d454e4921f777da810c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 77c9b4b73d2d839bc9c0bdaa73ffc148f0eda6ca +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147717782" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109228" --- この構成ファイルは、コードのスキャン時に {% data variables.product.prodname_codeql %} によって実行されるクエリのリストに `security-and-quality` クエリ スイートを追加します。 使用できるクエリ スイートの詳細については、「[追加のクエリを実行する](#running-additional-queries)」を参照してください。 @@ -56,4 +56,4 @@ query-filters: - recommendation ``` -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md b/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md index 3857ddb2d4..e595949d71 100644 --- a/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md +++ b/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: c33cc3f12d4b55379e23107890edc72673d4552d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 2c492c061232518888ac11c439ee5917fe032eeb +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682688" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109227" --- -{% data variables.product.prodname_codeql_cli %} は現在、glibc 以外の Linux ディストリビューション ((musl ベースの) Alpine Linux など) との互換性がありません。 \ No newline at end of file +{% data variables.product.prodname_codeql_cli %} は現在、glibc 以外の Linux ディストリビューション ((musl ベースの) Alpine Linux など) との互換性がありません。 diff --git a/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md b/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md new file mode 100644 index 0000000000..fcf94fe475 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: ba91a4555a2ae0e8ec359aee8c466e201525647c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109220" +--- +個人用設定ページで、{% data variables.product.prodname_codespaces %} の既定のエディターを設定できます。 diff --git a/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md b/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md new file mode 100644 index 0000000000..423b9fd764 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md @@ -0,0 +1,10 @@ +--- +ms.openlocfilehash: e18c37f7f93e2125d7280bd5b24a6eebea77d935 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106942" +--- +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} +1. サイドバーの [コードとオートメーション] セクションで、 **[{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}]** をクリックします。 diff --git a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index 9b1dde968f..c64ee3c814 100644 --- a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 008615ba94fed6838f09aa137e6da23e89168573 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a0a609a6e7a1cab14059012a15b6a08be53d8cbd +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682488" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109211" --- 1. {% data variables.product.prodname_vscode_shortname %} の左サイドバーで、[リモート エクスプローラー] のアイコンをクリックします。 ![{% data variables.product.prodname_vscode %} のリモート エクスプローラー アイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) -{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %} \ No newline at end of file +{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %} diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md index 8ca2465442..4bbbeeb02f 100644 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md @@ -2,4 +2,4 @@ **Note**: Codespace policies only apply to codespaces for which your organization will be billed. If an individual user creates a codespace for a repository in your organization, and the organization is not billed, then the codespace will not be bound by these policies. For information on how to choose who can create codespaces that are billed to your organization, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md index 37b7fa79a8..b27dca483d 100644 --- a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md +++ b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md @@ -1 +1 @@ -To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)." \ No newline at end of file +To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)." diff --git a/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md b/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md index b84d9dedb5..808e7692ad 100644 --- a/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md +++ b/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: f2d4527cb962dc9dc65d1aa1cc150f048814a917 -ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e +ms.openlocfilehash: 5a221eb6ab8719ebea834e50059bbc6aead1fa79 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147878647" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109203" --- -作成できる codespace の数と、同時に実行できる codespace の数には制限があります。 これらの制限は、いくつかの要因によって異なります。 codespace の最大数に達してからさらに作成しようとすると、新しい codespace を作成する前に既存のものを削除する必要があることを示すメッセージが表示されます。 \ No newline at end of file +作成できる codespace の数と、同時に実行できる codespace の数には制限があります。 これらの制限は、いくつかの要因によって異なります。 codespace の最大数に達してからさらに作成しようとすると、新しい codespace を作成する前に既存のものを削除する必要があることを示すメッセージが表示されます。 diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md index 4b49500f87..a21b08a741 100644 --- a/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md +++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 21a587f89a71ccd8e9f1a69aa5423a840f26b9a6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: c32a9f6f6a799c3653cb17fe89721090fc01d155 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147431627" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109195" --- リポジトリの開発コンテナー構成で他のリポジトリにアクセスするためのアクセス許可が指定されている場合は、認可ページが表示されます。 `devcontainer.json` ファイルでこれを指定する方法について詳しくは、「[codespace 内の他のリポジトリへのアクセスを管理する](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)」を参照してください。 @@ -18,4 +18,4 @@ ms.locfileid: "147431627" **注**: このプレビルドを使って codespace を作るユーザーも、これらのアクセス許可を付与するように求められます。 - {% endnote %} \ No newline at end of file + {% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md new file mode 100644 index 0000000000..e41bb8fbb8 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 5431cd0a877d3a87e4dd22fc3503bb9f67058b76 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109188" +--- +codespace はいつでも停止できます。 codespace を停止すると、実行中のすべてのプロセスが停止され、ターミナルの履歴が消去されます。 次に codespace を起動するときに、codespace に保存した変更は引き続き使用できます。 codespace を明示的に停止しない場合、非アクティブからタイムアウトするまで実行され続けます。 詳細については、「[Codespace のタイムアウト](/codespaces/developing-in-codespaces/codespaces-lifecycle#codespaces-timeouts)」を参照してください。 + +実行中の codespace にのみ CPU 料金が発生します。停止した codespace では、ストレージ コストのみが発生します。 + +codespace を停止し、再起動したときに、変更を適用したいと思うかもしれません。 たとえば、codespace に使用するマシンの種類を変更した場合、変更を有効にするには、その codespace を停止して再起動する必要があります。 また、エラーや予期しない問題が発生した場合に、codespace を停止し、再起動または削除することもできます。 diff --git a/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md new file mode 100644 index 0000000000..df3eb5c14a --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 93ed5f6170cc81999a5389dbc94453ac93023db1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109187" +--- +{% data variables.product.prodname_vscode_shortname %} で {% data variables.product.prodname_github_codespaces %} を使用するには、{% data variables.product.prodname_codespaces %} 拡張機能をインストールする必要があります。 diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md index 7ff974f84e..ff9f666cb8 100644 --- a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md +++ b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md @@ -1 +1 @@ -1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). \ No newline at end of file +1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md index 2207d65d03..8ad69b4238 100644 --- a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md +++ b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: e1df21c0657c55fb934b9c1d837a0ee19df7e37b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 224ce401421d3af0e9afa5976695c95ed219a7b5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147419746" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109179" --- ## {% data variables.product.prodname_copilot %} の設定を {% data variables.product.prodname_dotcom_the_website %} で構成する @@ -28,4 +28,4 @@ ms.locfileid: "147419746" ## 参考資料 -- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq) \ No newline at end of file +- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq) diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md deleted file mode 100644 index 752b254147..0000000000 --- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -ms.openlocfilehash: 22d4fde4f9dd7adbb4c9620e9d72e6dc52a716d4 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145138876" ---- -{% ifversion ghes > 3.2 %} - -{% note %} - -**注意:** Dependabot のセキュリティ アップデートとバージョン アップデートは現在、{% data variables.product.prodname_ghe_cloud %}、および {% data variables.product.prodname_ghe_server %} 3.3 のベータ版で利用できます。 Dependabot アップデートを有効にする手順については、[アカウント管理チームにお問い合せください](https://enterprise.github.com/contact)。 - -{% endnote %} - -{% endif %} diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md index d1a685249b..a6d2d6cd01 100644 --- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md +++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md @@ -1,4 +1,4 @@ -{% ifversion ghes > 3.2 and ghes < 3.5 %} +{% ifversion ghes < 3.5 %} {% note %} {% ifversion ghes = 3.4 %} diff --git a/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md index 844b35d9ea..86180c6b2a 100644 --- a/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -1,4 +1,4 @@ -{% ifversion ghes > 3.2 %} +{% ifversion ghes %} {% note %} diff --git a/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md b/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md index 9427c650a2..605e2fc50a 100644 --- a/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md +++ b/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 5a31b3124d838bfaad532763c644a8b446dcd0aa -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: ff7a0c836b3df74110b4613fa032541e0f27d347 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147887834" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109163" --- {% ifversion ghes or ghae %} エンタープライズ所有者とリポジトリへの管理アクセス権を持つユーザーは、{% data variables.product.prodname_dependency_review_action %}をそれぞれエンタープライズとリポジトリに追加できます。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/dependency-review/beta.md b/translations/ja-JP/data/reusables/dependency-review/beta.md deleted file mode 100644 index c009e2fc88..0000000000 --- a/translations/ja-JP/data/reusables/dependency-review/beta.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -ms.openlocfilehash: b55c1d61ba8da90884c50184240d2aea8e8b0ee9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145138699" ---- -{% ifversion ghes = 3.2 %} {% note %} - -**注:** 依存関係のレビューは現在ベータ版であり、変更される可能性があります。 - -{% endnote %} - -{% endif %} diff --git a/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md b/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md index 1612ffd207..88af5246dd 100644 --- a/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md +++ b/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 3419a29bb8fad04801ff8e2846c11da684f61910 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 82c3a5fa91313a6f2e27e58b62c706ea5b0ef4d9 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147410789" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109644" --- -{% data variables.product.prodname_community_exchange %} は、{% data variables.product.prodname_global_campus %} ポータル内の学生コミュニティです。 そこでは、学生は、自分のプロジェクトを公開し、コラボレーターやメンテナンス担当者を必要とする他の学生リポジトリを見つけることができます。 \ No newline at end of file +{% data variables.product.prodname_community_exchange %} は、{% data variables.product.prodname_global_campus %} ポータル内の学生コミュニティです。 そこでは、学生は、自分のプロジェクトを公開し、コラボレーターやメンテナンス担当者を必要とする他の学生リポジトリを見つけることができます。 diff --git a/translations/ja-JP/data/reusables/education/submit-application.md b/translations/ja-JP/data/reusables/education/submit-application.md index d881e524c5..5014f7638f 100644 --- a/translations/ja-JP/data/reusables/education/submit-application.md +++ b/translations/ja-JP/data/reusables/education/submit-application.md @@ -7,4 +7,4 @@ {% endnote %} - If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester. \ No newline at end of file + If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester. diff --git a/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md b/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md index 82b710c595..5111e2627b 100644 --- a/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md +++ b/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 12b28d4c3665573a1cfc0d56e2a61b616ee0a9ec -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fbb3311774be7ef276adaba8461a100f73c1c6bb +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147572673" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109643" --- -複数の {% data variables.product.prodname_enterprise %} 環境を使用しているユーザーが 1 つのライセンスのみを使用するためには、環境間でライセンス利用状況を同期する必要があります。 その後、ユーザー アカウントに関連付けられているメール アドレスに基づいて、{% data variables.product.company_short %} によりユーザーの重複が除去されます。 詳しくは、[{% data variables.product.prodname_enterprise %} のライセンス利用状況のトラブルシューティング](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)に関するページを参照してください。 \ No newline at end of file +複数の {% data variables.product.prodname_enterprise %} 環境を使用しているユーザーが 1 つのライセンスのみを使用するためには、環境間でライセンス利用状況を同期する必要があります。 その後、ユーザー アカウントに関連付けられているメール アドレスに基づいて、{% data variables.product.company_short %} によりユーザーの重複が除去されます。 詳しくは、[{% data variables.product.prodname_enterprise %} のライセンス利用状況のトラブルシューティング](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)に関するページを参照してください。 diff --git a/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md b/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md index 37112ad7ad..6bf5f25473 100644 --- a/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md +++ b/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: de369a16e292dac48d6e6aee2907e28ae1f46af3 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: a708ef37153f09729c17dd9a06f258cb64579e6b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147390433" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109635" --- -企業が {% data variables.product.company_short %} の製品を使ってソフトウェア開発ライフサイクルをサポートする方法について、詳しくは、「[エンタープライズ向け {% data variables.product.prodname_dotcom %}](/admin/overview/about-github-for-enterprises) について」を参照してください。 \ No newline at end of file +企業が {% data variables.product.company_short %} の製品を使ってソフトウェア開発ライフサイクルをサポートする方法について、詳しくは、「[エンタープライズ向け {% data variables.product.prodname_dotcom %}](/admin/overview/about-github-for-enterprises) について」を参照してください。 diff --git a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md index 6dd6f32b4f..31a2b15709 100644 --- a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md +++ b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: 4d2db8622a5ddf12d83595e903e3b2ba1774727b -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147878943" ---- -{% ifversion ghes < 3.6 %} {% note %} +{% ifversion ghes < 3.6 %} +{% note %} -**注:** リポジトリ キャッシュは現在ベータ版であり、変更される可能性があります。 +**Note:** Repository caching is currently in beta and subject to change. -{% endnote %} {% endif %} \ No newline at end of file +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md b/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md deleted file mode 100644 index 73e58ca754..0000000000 --- a/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -ms.openlocfilehash: ce032c1829e6b93f7adcd62e1b731953669ffb91 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145111893" ---- -{% ifversion ghes < 3.3 %} {% data variables.product.prodname_actions %} は、{% data variables.product.prodname_ghe_server %} 3.0 以降で使用できます。 以前のバージョンの {% data variables.product.prodname_ghe_server %} を使用している場合は、{% data variables.product.prodname_actions %} を使用するようにアップグレードする必要があります。 {% data variables.product.prodname_ghe_server %} インスタンスのアップグレードの詳細については、「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」を参照してください。 -{% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md index 630dfc76aa..afa6a21c84 100644 --- a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md +++ b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 5c1cf00625a805fc4054a78bc4ac675a161a1c1b -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 5302e6f9d952c4a8881d1f28fe7ea847a70d0efe +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147861699" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109628" --- -1. バックアップ ホストで、{% data variables.product.prodname_enterprise_backup_utilities %} ディレクトリ (通常は `backup-utils`) に移動します。 \ No newline at end of file +1. バックアップ ホストで、{% data variables.product.prodname_enterprise_backup_utilities %} ディレクトリ (通常は `backup-utils`) に移動します。 diff --git a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md index cae65131ea..484c57ea24 100644 --- a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md +++ b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 8289b9aadf88b85cf8d4dc71d2fc74db42c01289 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 76be6868da14b227e1b0fbc16b8c9f913b4f04e0 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147861688" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109627" --- 1. 正常にアップグレードされたことを確認するには、次のコマンドを実行します。 ```shell @@ -15,4 +15,4 @@ ms.locfileid: "147861688" ```shell ./bin/ghe-host-check ``` - \ No newline at end of file + diff --git a/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md index 444818f8fe..f9044ae820 100644 --- a/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md +++ b/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md @@ -4,4 +4,4 @@ To ensure that {% data variables.location.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}. -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md b/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md new file mode 100644 index 0000000000..95b7ba2b5a --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 88d76852d3e379e556b364b31199800e73ecd0c7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109363" +--- +{% data variables.enterprise.management_console %} をただちにロック解除するには、管理シェルから `ghe-reactivate-admin-login` コマンドを使用します。 詳細については、「[コマンド ライン ユーティリティ](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)」と「[管理シェルへのアクセス (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gated-features/code-scanning.md b/translations/ja-JP/data/reusables/gated-features/code-scanning.md index 87bb7275dd..3512f732b5 100644 --- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md @@ -1,13 +1,17 @@ -{%- ifversion fpt %} -{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_code_scanning_capc %} is also available for 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 %}. +--- +ms.openlocfilehash: 0ea67362c541ed183fec256765d5bb9d1fd18e3c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109355" +--- +{%- ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリに使用できます。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_ghe_cloud %} を使用していて {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Organization によって所有されるリポジトリで使用できます。 -{%- elsif ghec %} -{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_code_scanning %} in a private repository owned by an organization, you must have a license for {% data variables.product.prodname_GH_advanced_security %}. +{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリに使用できます。 Organization によって所有されるプライベート リポジトリで {% data variables.product.prodname_code_scanning %} を使うには、{% data variables.product.prodname_GH_advanced_security %} のライセンスが必要です。 -{%- elsif ghes %} -{% data variables.product.prodname_code_scanning_capc %} 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 ghes %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.product_name %} の Organization 所有のリポジトリで利用できます。 この機能には、{% data variables.product.prodname_GH_advanced_security %} のライセンスが必要です。 -{%- elsif ghae %} -{% data variables.product.prodname_code_scanning_capc %} 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). +{%- elsif ghae %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.product_name %} の Organization 所有のリポジトリで利用できます。 これは {% data variables.product.prodname_GH_advanced_security %} の機能です (ベータ リリース中は無料)。 -{%- 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/gated-features/historical-insights-for-projects.md b/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md index 41cd73318a..73b73c4c8c 100644 --- a/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md +++ b/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: fd865e1bcf0fb2af69739d4d81fa27796e2e0b33 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f28c558acbb1dacd503964146c0522145d44948b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424210" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109347" --- -履歴グラフは、Organization 向けの {% data variables.product.prodname_team %} と {% data variables.product.prodname_ghe_cloud %} で利用できます。 Organization 向けの {% data variables.product.prodname_team %} および {% data variables.product.prodname_ghe_cloud %} と、ユーザー向けの {% data variables.product.prodname_pro %} で、プライベート プロジェクトに無制限のグラフを保存できます。 パブリック プロジェクトを使用しているユーザーと Organization も、無制限のグラフを保存できます。 {% data variables.product.prodname_free_team %} またはレガシ プランを使用しているユーザーと Organization は、プライベート プロジェクトに 2 つのグラフを保存できます。 {% data reusables.gated-features.more-info %} \ No newline at end of file +履歴グラフは、Organization 向けの {% data variables.product.prodname_team %} と {% data variables.product.prodname_ghe_cloud %} で利用できます。 Organization 向けの {% data variables.product.prodname_team %} および {% data variables.product.prodname_ghe_cloud %} と、ユーザー向けの {% data variables.product.prodname_pro %} で、プライベート プロジェクトに無制限のグラフを保存できます。 パブリック プロジェクトを使用しているユーザーと Organization も、無制限のグラフを保存できます。 {% data variables.product.prodname_free_team %} またはレガシ プランを使用しているユーザーと Organization は、プライベート プロジェクトに 2 つのグラフを保存できます。 {% data reusables.gated-features.more-info %} diff --git a/translations/ja-JP/data/reusables/gated-features/hosted-runners.md b/translations/ja-JP/data/reusables/gated-features/hosted-runners.md index d983a32737..669390e197 100644 --- a/translations/ja-JP/data/reusables/gated-features/hosted-runners.md +++ b/translations/ja-JP/data/reusables/gated-features/hosted-runners.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 2d2d2bc1f01e722c0f30cf11b642033a762c429c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 54a0c4cae87acc79c4d4763521f11da1a37cd2d6 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147853683" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109340" --- -{% data variables.actions.hosted_runner %} 機能は、{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} プランを使用している Organization やエンタープライズでは現在ベータ版で、これは今後変わる可能性があります。 ベータ版の使用を求める場合には、[サインアップ ページ](https://github.com/features/github-hosted-runners/signup)にアクセスします。 \ No newline at end of file +{% data variables.actions.hosted_runner %} 機能は、{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} プランを使用している Organization やエンタープライズでは現在ベータ版で、これは今後変わる可能性があります。 ベータ版の使用を求める場合には、[サインアップ ページ](https://github.com/features/github-hosted-runners/signup)にアクセスします。 diff --git a/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md b/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md index 6daf30d07d..741ec870b5 100644 --- a/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md +++ b/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: a6189685e97d4aeabb737421203acb96ccd0f61c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 43a23bdc9abc48a087e62f93a6d01a1aaabe0eb0 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147718224" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109339" --- -ほとんどの場合は、`Authorization: Bearer` または `Authorization: token` を使用してトークンを渡すことができます。 ただし、JSON Web トークン (JWT) を渡す場合は、`Authorization: Bearer` を使用する必要があります。 \ No newline at end of file +ほとんどの場合は、`Authorization: Bearer` または `Authorization: token` を使用してトークンを渡すことができます。 ただし、JSON Web トークン (JWT) を渡す場合は、`Authorization: Bearer` を使用する必要があります。 diff --git a/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md b/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md index 8c6f60a5eb..59cadf5151 100644 --- a/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md +++ b/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: d68b3fb76a086f8ba99cd3c968b547f9d94eb8c9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: ff4fa65700cd685f99a3e94541df48a2f5e77985 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147529763" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109332" --- -{% ifversion mermaid %}Markdown を使用して、レンダリングされた数式、ダイアグラム、マップ、3D モデルを Wiki に追加できます。 レンダリングされた数式の作成の詳細については、「[数式の記述](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)」を参照してください。 ダイアグラム、マップ、3D モデルの作成の詳細については、「[ダイアグラムの作成](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)」を参照してください。{% endif %} \ No newline at end of file +{% ifversion mermaid %}Markdown を使用して、レンダリングされた数式、ダイアグラム、マップ、3D モデルを Wiki に追加できます。 レンダリングされた数式の作成の詳細については、「[数式の記述](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)」を参照してください。 ダイアグラム、マップ、3D モデルの作成の詳細については、「[ダイアグラムの作成](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)」を参照してください。{% endif %} diff --git a/translations/ja-JP/data/reusables/git/no-credential-manager.md b/translations/ja-JP/data/reusables/git/no-credential-manager.md index ab4384f3b5..45bee44340 100644 --- a/translations/ja-JP/data/reusables/git/no-credential-manager.md +++ b/translations/ja-JP/data/reusables/git/no-credential-manager.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: c1773da7070760a6a40d198a66f7646536d7a236 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: af8f3c7c0c5378080257097644571e8a0d04a840 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147687147" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109331" --- -- 出力に資格情報マネージャーの名前が含まれていない場合は、資格情報マネージャーが構成されていないため、次の手順に進むことができます。 \ No newline at end of file +- 出力に資格情報マネージャーの名前が含まれていない場合は、資格情報マネージャーが構成されていないため、次の手順に進むことができます。 diff --git a/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md b/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md index c2ef59482a..dfa948ec5f 100644 --- a/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md +++ b/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md @@ -1,8 +1,16 @@ +--- +ms.openlocfilehash: 8afd93954b55495a93b01ca1ed2c0a58946ffbd5 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109324" +--- {% ifversion ghae %} -IdP | SAML | User provisioning | Team mapping| +IdP | SAML | ユーザー プロビジョニング | Team マッピング| --- | --- | ---------------- | --------- | [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}| {% octicon "check-circle-fill" aria-label="The check icon" %} | -[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[Beta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) | +[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[ベータ版](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[ベータ版](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[ベータ版](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) | {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md b/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md index 137509f34f..a16d5d5b94 100644 --- a/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md +++ b/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: fb14a6e9eb1b7ac1846b7b7e39fa1d6b7f000840 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 0a0e572422bee311ca8adb2b40c81a00907c0dfb +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147653405" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109620" --- 1. コミットやタグの署名に SSH を使うよう Git を構成します。 ```bash $ git config --global gpg.format ssh - ``` \ No newline at end of file + ``` diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md index e2943e5a06..3c08dedb53 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 6775f1ca71684e74de0fedce4cb7e6c6b15c2820 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: db4c80c49c4e3effe99073f29010147f3a1efc08 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682895" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108934" --- それぞれに IP アドレスまたはアドレス範囲を含むエントリを追加することで、IP 許可リストを作成できます。{% ifversion ip-allow-list-address-check %} エントリの追加が完了したら、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。{% endif %} -Enterprise 内の Organization が所有する {% ifversion ghae %}Enterprise{% else %} プライベート アセット{% endif %}へのアクセスがリストによって制限される前に、許可 IP アドレスも有効にする必要があります。 \ No newline at end of file +Enterprise 内の Organization が所有する {% ifversion ghae %}Enterprise{% else %} プライベート アセット{% endif %}へのアクセスがリストによって制限される前に、許可 IP アドレスも有効にする必要があります。 diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md index 7f5fed6b12..4d37fc5e1d 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: ad162035ba2dcbb3c38f368dc7376b8fd5dd0b0c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d7e7459f3ed9898a892c8b3504a32c1106e69442 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682908" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108929" --- -許可リストが現時点で有効になっていなくても、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 \ No newline at end of file +許可リストが現時点で有効になっていなくても、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md index d4e1a2e007..f8ace38686 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 0f621e8e83d20f58e208fd9285082441fe29aa74 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 8f78a77c83ea498d8d41a0deff20903062542479 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682894" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108928" --- IP 許可リストのエントリを編集できます。 有効なエントリを編集すると、変更がすぐに適用されます。 {% ifversion ip-allow-list-address-check %}エントリの編集が完了したら、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md index d8eb3f5cf3..16814a5064 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 4a8eaf38855e436884a6abdfc8d0b21473e71904 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 095556009ed66ca0b687734f62f21c70fd87699a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682905" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108923" --- IP 許可リストを作成すると、許可 IP アドレスを有効にすることができます。 許可 IP アドレスを有効にすると、IP 許可リスト内のいずれかの有効なエントリが、{% data variables.product.company_short %} によってすぐに適用されます。 {% ifversion ip-allow-list-address-check %} 許可 IP アドレスを有効にする前に、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 詳しくは、「[IP アドレスが許可されているかどうかを確認する](#checking-if-an-ip-address-is-permitted)」を参照してください。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md index 1f41542e94..eb6f69a26c 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 767afd2426bcfba04a2eb3c845b1041e65d006f9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 5eaf0aa831a27f61216ae9574df61fe7445f2f94 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682888" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109619" --- 1. [IP アドレスの確認] で、IP アドレスを入力します。 - ![[IP アドレスの確認] テキスト フィールドのスクリーンショット](/assets/images/help/security/check-ip-address.png) \ No newline at end of file + ![[IP アドレスの確認] テキスト フィールドのスクリーンショット](/assets/images/help/security/check-ip-address.png) diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md index 0dc3ab1849..21bc6ff94a 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: bc619567dc896525b2c11f30ef4b721e17279618 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 7b848e4c3bb4a9a4578e3f1ff92f6249dd20c699 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147682902" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109612" --- {%- ifversion ip-allow-list-address-check %} 1. 必要に応じて、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 詳しくは、「[IP アドレスが許可されているかどうかを確認する](#checking-if-an-ip-address-is-permitted)」を参照してください。 -{%- endif %} \ No newline at end of file +{%- endif %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md b/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md index 0746e33cba..c7680a186a 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: fdfc231ccda60a08923fd8cd91160fea9389e9b0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 1df7a9480c4cfd3a5edfc1ee16cd2a3259921e6b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147707311" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109531" --- {% ifversion fpt or ghec %} {% note %} **注:** {% data variables.product.company_short %} では、IPv6 のサポートを段階的にロールアウトしています。 {% data variables.product.prodname_dotcom %} サービスには引き続き IPv6 のサポートが追加されるため、{% data variables.product.prodname_dotcom %} ユーザーの IPv6 アドレスの認識を開始できます。 アクセスの中断の可能性を防ぐには、必要な IPv6 アドレスが自分の IP 許可リストに確実に追加されている状態にしてください。 -{% endnote %} {% endif %} \ No newline at end of file +{% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md index 1913d6e459..8c5bcb44ec 100644 --- a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md +++ b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md @@ -4,4 +4,4 @@ **Note:** Vigilant mode is currently in beta and subject to change. {% endnote %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md index cd318e85fc..b6445e487a 100644 --- a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md @@ -1 +1 @@ -issues, pull requests, releases, security alerts, or discussions \ No newline at end of file +issues, pull requests, releases, security alerts, or discussions diff --git a/translations/ja-JP/data/reusables/organizations/about-following-organizations.md b/translations/ja-JP/data/reusables/organizations/about-following-organizations.md index 91b83567e4..d42b31bf6a 100644 --- a/translations/ja-JP/data/reusables/organizations/about-following-organizations.md +++ b/translations/ja-JP/data/reusables/organizations/about-following-organizations.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 9d70c0e47d7aed9253d990146233d8fac92d339c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f9490c302fe4534be6937805e0eec85fe9c5db1a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147692147" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109587" --- -{% data variables.product.product_name %} で組織をフォローすると、個人用ダッシュボードに{% ifversion fpt or ghec %}パブリック{% endif %} アクティビティが表示されます。 このアクティビティには、新しいディスカッション、スポンサーシップ、リポジトリが含まれます。 \ No newline at end of file +{% data variables.product.product_name %} で組織をフォローすると、個人用ダッシュボードに{% ifversion fpt or ghec %}パブリック{% endif %} アクティビティが表示されます。 このアクティビティには、新しいディスカッション、スポンサーシップ、リポジトリが含まれます。 diff --git a/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md b/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md index e358486dbf..09183b3034 100644 --- a/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md +++ b/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: f64274ea187e812242eb07e1dd9a7204b6522e50 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 4e2e744a966a1e1b8111f6f5194542f7512670fc +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147692140" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109611" --- {% note %} **注:** 組織をフォローする機能は現在パブリック ベータ段階であり、変更される可能性があります。 -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/ja-JP/data/reusables/organizations/new_team.md b/translations/ja-JP/data/reusables/organizations/new_team.md index 2e3249f2f5..ad329ffe34 100644 --- a/translations/ja-JP/data/reusables/organizations/new_team.md +++ b/translations/ja-JP/data/reusables/organizations/new_team.md @@ -1,12 +1,8 @@ ---- -ms.openlocfilehash: 383ba2a3fe279dfa18f20c931a58a5b4785e8727 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883757" ---- -1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %} -1. [Team] タブの右側にある **[新しい Team]** をクリックします。 - ![[新しい Team] ボタン](/assets/images/help/teams/new-team-button.png) +1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**. + {% ifversion fpt or ghes or ghec %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png) + {% else %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png) + {% endif %} +1. On the right side of the Teams tab, click **New team**. + ![New team button](/assets/images/help/teams/new-team-button.png) diff --git a/translations/ja-JP/data/reusables/organizations/org_settings.md b/translations/ja-JP/data/reusables/organizations/org_settings.md index b72f78972a..4e84c3e807 100644 --- a/translations/ja-JP/data/reusables/organizations/org_settings.md +++ b/translations/ja-JP/data/reusables/organizations/org_settings.md @@ -1,10 +1,6 @@ ---- -ms.openlocfilehash: 86e15f92ffd6a5a5b90d7a70a666447a6a51a62a -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145122542" ---- -1. Organization 名の下で、{% octicon "gear" aria-label="The Settings gear" %} **[設定]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization の設定ボタン](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) {% else %} ![Organization の設定ボタン](/assets/images/help/organizations/organization-settings-tab.png) {% endif %} +1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. + {% ifversion fpt or ghes or ghec %} + ![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) + {% else %} + ![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png) + {% endif %} diff --git a/translations/ja-JP/data/reusables/organizations/organization-wide-project.md b/translations/ja-JP/data/reusables/organizations/organization-wide-project.md index 5c7821b50e..052670fdf5 100644 --- a/translations/ja-JP/data/reusables/organizations/organization-wide-project.md +++ b/translations/ja-JP/data/reusables/organizations/organization-wide-project.md @@ -1,10 +1,6 @@ ---- -ms.openlocfilehash: cba236cbf17553914d18f006b2a17a77a4892658 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145122494" ---- -1. Organization 名の下の {% octicon "project" aria-label="The Projects icon" %} **[プロジェクト]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization の [プロジェクト] タブ](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png) {% else %} ![Organization の [プロジェクト] タブ](/assets/images/help/organizations/organization-projects-tab.png) {% endif %} +1. Under your organization name, click {% octicon "project" aria-label="The Projects icon" %} **Projects**. + {% ifversion fpt or ghes or ghec %} + ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png) + {% else %} + ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab.png) + {% endif %} diff --git a/translations/ja-JP/data/reusables/organizations/owners-team.md b/translations/ja-JP/data/reusables/organizations/owners-team.md index 9b6c7848c6..b66f0838ca 100644 --- a/translations/ja-JP/data/reusables/organizations/owners-team.md +++ b/translations/ja-JP/data/reusables/organizations/owners-team.md @@ -1,12 +1,8 @@ ---- -ms.openlocfilehash: 953f11ac28cbb526cd4e93bc316cf81b12241f08 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145122469" ---- -1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %} -1. [Team] タブで、 **[オーナー]** をクリックします。 - ![オーナーの Team が選択されている](/assets/images/help/teams/owners-team.png) +1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**. + {% ifversion fpt or ghes or ghec %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png) + {% else %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png) + {% endif %} +1. On the Teams tab, click **Owners**. + ![Owners team selected](/assets/images/help/teams/owners-team.png) diff --git a/translations/ja-JP/data/reusables/organizations/people.md b/translations/ja-JP/data/reusables/organizations/people.md index 451f2a1223..d69d13281b 100644 --- a/translations/ja-JP/data/reusables/organizations/people.md +++ b/translations/ja-JP/data/reusables/organizations/people.md @@ -1,10 +1,6 @@ ---- -ms.openlocfilehash: 3a40932cc10fd659071bbc951940a79a1c0498bf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145122461" ---- -1. Organization 名の下で、{% octicon "person" aria-label="The Person icon" %} **[People]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![[People] タブ](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png) {% else %} ![[People] タブ](/assets/images/help/organizations/organization-people-tab.png) {% endif %} +1. Under your organization name, click {% octicon "person" aria-label="The Person icon" %} **People**. + {% ifversion fpt or ghes or ghec %} + ![The People tab](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png) + {% else %} + ![The People tab](/assets/images/help/organizations/organization-people-tab.png) + {% endif %} diff --git a/translations/ja-JP/data/reusables/organizations/specific_team.md b/translations/ja-JP/data/reusables/organizations/specific_team.md index 96b974a0f4..655628972a 100644 --- a/translations/ja-JP/data/reusables/organizations/specific_team.md +++ b/translations/ja-JP/data/reusables/organizations/specific_team.md @@ -1,12 +1,8 @@ ---- -ms.openlocfilehash: e073e782e9271d660c789014a93a5b0f7d703de9 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145122286" ---- -1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %} -1. Teamsタブで、Teamの名前をクリックしてください。 - ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png) +1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**. + {% ifversion fpt or ghes or ghec %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png) + {% else %} + ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png) + {% endif %} +1. On the Teams tab, click the name of the team. + ![List of the organization's teams](/assets/images/help/teams/click-team-name.png) diff --git a/translations/ja-JP/data/reusables/organizations/teams.md b/translations/ja-JP/data/reusables/organizations/teams.md index 533593ff2f..55600311cf 100644 --- a/translations/ja-JP/data/reusables/organizations/teams.md +++ b/translations/ja-JP/data/reusables/organizations/teams.md @@ -1,10 +1,6 @@ ---- -ms.openlocfilehash: ddf350dbd9a76a2d7168e67fe690662ac2e63c35 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147878735" ---- -1. 組織名の下で、{% octicon "people" aria-label="The people icon" %} **[Teams]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![組織ページの [Teams] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![組織ページの [Teams] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %} +1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**. + {% ifversion fpt or ghes or ghec %} + ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab-with-overview.png) + {% else %} + ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab.png) + {% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md index 63d4118408..751ada92e8 100644 --- a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 86b8c01b5dc27c55e316ba0d81176fd693f85e45 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 4a39732206e0ad91422acfb3977ba7bea7d0b283 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147410747" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109516" --- -{% data variables.product.product_name %} 3.6 では、Organization に格納されている Docker イメージの移行がサポートされています。 今後のリリースでは、ユーザー所有のイメージの移行がサポートされます。 \ No newline at end of file +{% data variables.product.product_name %} 3.6 では、Organization に格納されている Docker イメージの移行がサポートされています。 今後のリリースでは、ユーザー所有のイメージの移行がサポートされます。 diff --git a/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md b/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md index fde6a42efb..18c9c747d4 100644 --- a/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md +++ b/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: deca3a28d17f3716b20a84281ad843c47bdbbee2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 5f35d3186458109231db91e80343bcb64a2193c1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147705078" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108917" --- -{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API では、パッケージ名前空間 `https://ghcr.io/OWNER/PACKAGE-NAME` を使用するコンテナーまたは Docker イメージ、またはパッケージ名前空間 `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` を使用する npm イメージはサポートされていません。{% endif %} \ No newline at end of file +{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API では、パッケージ名前空間 `https://ghcr.io/OWNER/PACKAGE-NAME` を使用するコンテナーまたは Docker イメージ、またはパッケージ名前空間 `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` を使用する npm イメージはサポートされていません。{% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md b/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md index 2818915f3a..d46f87514d 100644 --- a/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md +++ b/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md @@ -1,11 +1,7 @@ ---- -ms.openlocfilehash: f0e8ddbcd9cbfd2166663191a293876d6e2f8a2e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145121910" ---- -1. {% data variables.product.prodname_dotcom %}で、Organizationのメインページにアクセスしてください。 -2. Organization 名の下で、 **[パッケージ]** をクリックします。 - {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization ランディングページの [パッケージ] タブ](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png) {% else %} ![Organization ランディングページの [パッケージ] タブ](/assets/images/help/package-registry/org-tab-for-packages.png) {% endif %} +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization. +2. Under your organization name, click **Packages**. + {% ifversion fpt or ghes or ghec %} + ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png) + {% else %} + ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages.png) + {% endif %} diff --git a/translations/ja-JP/data/reusables/pages/check-workflow-run.md b/translations/ja-JP/data/reusables/pages/check-workflow-run.md index d6c582a973..c17f524db6 100644 --- a/translations/ja-JP/data/reusables/pages/check-workflow-run.md +++ b/translations/ja-JP/data/reusables/pages/check-workflow-run.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: d2f50ce890ed4d9a90015498ecdf9909348155fb -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 +ms.openlocfilehash: 258f73f928cd99de64f45fda0e6cec8e08ff335c +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147879208" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108922" --- {% ifversion build-pages-with-actions %} 1. {% data variables.product.prodname_pages %} サイトは、{% data variables.product.prodname_actions %} ワークフローでビルドされ、デプロイされます。 詳細については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。 @@ -15,4 +15,4 @@ ms.locfileid: "147879208" {% endnote %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md b/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md index 3bad436703..75d24f06fa 100644 --- a/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md +++ b/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 653ecfef09a75144cb39fc0d3bf47ba7394a1ce8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a231b3c0bf02051ba3593f5dd04ac7fdf5506ea7 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147428443" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109428" --- {% ifversion pages-custom-workflow %} @@ -14,4 +14,4 @@ ms.locfileid: "147428443" {% endnote %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/profile/navigating-to-profile.md b/translations/ja-JP/data/reusables/profile/navigating-to-profile.md new file mode 100644 index 0000000000..1fba1ca676 --- /dev/null +++ b/translations/ja-JP/data/reusables/profile/navigating-to-profile.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 32a0fded4915b0b23b3db1110d556bd14e0830a8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106646" +--- +1. 任意の {% data variables.product.product_name %} ページ上の右上隅にある自分のプロフィール写真をクリックしてから、 **[自分のプロフィール]** をクリックします。 diff --git a/translations/ja-JP/data/reusables/projects/access-workflows.md b/translations/ja-JP/data/reusables/projects/access-workflows.md new file mode 100644 index 0000000000..f4a8917a8d --- /dev/null +++ b/translations/ja-JP/data/reusables/projects/access-workflows.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: 2637ffcb5913f0c84f3ae092653c410ad0a5fdad +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148106591" +--- +1. プロジェクトにアクセスします。 +1. 右上の {% octicon "kebab-horizontal" aria-label="The menu icon" %} をクリックして、メニューを開きます。 + ![メニュー アイコンを示すスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで {% octicon "workflow" aria-label="The workflow icon" %} **[ワークフロー]** をクリックします。 + ![[ワークフロー] メニュー項目を示すスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png) diff --git a/translations/ja-JP/data/reusables/projects/add-draft-issue.md b/translations/ja-JP/data/reusables/projects/add-draft-issue.md index 4ba1f0bf1b..6f2d3a516d 100644 --- a/translations/ja-JP/data/reusables/projects/add-draft-issue.md +++ b/translations/ja-JP/data/reusables/projects/add-draft-issue.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 8dd7d544c14de78ff9150bebb1192bbd4a6007f0 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 303fc7fa60ba2ccc37689055f6056a59655a6eae +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880205" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109144" --- {% data reusables.projects.add-item-bottom-row %} 1. アイデアを入力し、**Enter** キーを押します。 ![issue URL を貼り付けてプロジェクトに追加することを示すスクリーンショット](/assets/images/help/projects-v2/add-draft-issue.png) -1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるマークダウンの入力ボックスに、ドラフト Issue の本文のテキストを入力し、 **[保存]** をクリックします。 \ No newline at end of file +1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるマークダウンの入力ボックスに、ドラフト Issue の本文のテキストを入力し、 **[保存]** をクリックします。 diff --git a/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md b/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md index 089f82501c..bd5387bb90 100644 --- a/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md +++ b/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 62086a2f270c2d05a7e3774431e23e6ed089e1cb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 8af3f341f8b2a91038d1e489a1d2ed59d8743234 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424231" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109126" --- 1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。 - ![項目を追加する一番下の行を示すスクリーンショット](/assets/images/help/projects-v2/add-item.png) \ No newline at end of file + ![項目を追加する一番下の行を示すスクリーンショット](/assets/images/help/projects-v2/add-item.png) diff --git a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md index cf56424bcb..8381e50ea8 100644 --- a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md +++ b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 0191556eb977c4b657f1fd78330f6f691f34f039 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 477122edeb960deca31d1ad0b97b7ad30681f23b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147424059" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109427" --- {% data reusables.projects.add-item-bottom-row %} 1. IssueあるいはPull RequestのURLを貼り付けてください。 ![issue URL を貼り付けてプロジェクトに追加することを示すスクリーンショット](/assets/images/help/projects-v2/paste-url-to-add.png) -3. issue または pull request を追加するには、Return キーを押します。 \ No newline at end of file +3. issue または pull request を追加するには、Return キーを押します。 diff --git a/translations/ja-JP/data/reusables/projects/bulk-add.md b/translations/ja-JP/data/reusables/projects/bulk-add.md index d57acfc471..ee959241a6 100644 --- a/translations/ja-JP/data/reusables/projects/bulk-add.md +++ b/translations/ja-JP/data/reusables/projects/bulk-add.md @@ -1,14 +1,14 @@ --- -ms.openlocfilehash: b8288219bd82b857d0bbeeefef3b27a3c8f0d3de -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 +ms.openlocfilehash: d0d7eb973a255091345f61ff69f8f20f6361d0d9 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884713" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109156" --- 1. 必要に応じて、リポジトリを変更するには、ドロップダウンをクリックしてリポジトリを選びます。 特定の issue や pull request を検索することもできます。 ![[リポジトリ] ドロップダウン示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-select-repo.png) 1. 追加する issue と pull request を選びます。 ![追加する issue と pull request が選ばれているところを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-select-issues.png) 1. **[選択した項目の追加]** をクリックします。 - ![[選択した項目の追加] ボタンを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-save.png) \ No newline at end of file + ![[選択した項目の追加] ボタンを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-save.png) diff --git a/translations/ja-JP/data/reusables/projects/classic-project-creation.md b/translations/ja-JP/data/reusables/projects/classic-project-creation.md index b555c661b1..3ae073c69c 100644 --- a/translations/ja-JP/data/reusables/projects/classic-project-creation.md +++ b/translations/ja-JP/data/reusables/projects/classic-project-creation.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: cd5e613522bc536aa433d900e193ef2276df6410 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 682ba253ea2660d8608033598343393372ae3cbf +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147375724" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109419" --- {% ifversion fpt or ghec %} @@ -14,4 +14,4 @@ ms.locfileid: "147375724" {% endnote %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/projects/new-field.md b/translations/ja-JP/data/reusables/projects/new-field.md index 29c4e66c17..58541ba367 100644 --- a/translations/ja-JP/data/reusables/projects/new-field.md +++ b/translations/ja-JP/data/reusables/projects/new-field.md @@ -1,14 +1,14 @@ --- -ms.openlocfilehash: daf5b47c71e8cbde44c6dab38eabf7c6d922be9a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 3acee6d785e2b633f979e7edb8f80544dfa09ced +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882876" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109412" --- 1. テーブル ビューで、右端のフィールド ヘッダーの [{% octicon "plus" aria-label="the plus icon" %}] をクリックします。 ![新しいフィールドのボタンを示すスクリーンショット](/assets/images/help/projects-v2/new-field-button.png) 1. **[新しいフィールド]** をクリックします。 ![新しいフィールドのメニュー項目を示すスクリーンショット](/assets/images/help/projects-v2/new-field-menu-item.png) 1. 新しいフィールドの名前を入力します。 - ![フィールド名を示すスクリーンショット](/assets/images/help/projects-v2/new-field-name.png) \ No newline at end of file + ![フィールド名を示すスクリーンショット](/assets/images/help/projects-v2/new-field-name.png) diff --git a/translations/ja-JP/data/reusables/projects/new-view.md b/translations/ja-JP/data/reusables/projects/new-view.md index b515b2e349..6e4c439e9f 100644 --- a/translations/ja-JP/data/reusables/projects/new-view.md +++ b/translations/ja-JP/data/reusables/projects/new-view.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 831716db8a52f44aee809924a38f8288952d23df -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9bac51e4098b1da121c0763f8581716a547353af +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424136" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108869" --- 1. 既存のビューの右側にある **[新しいビュー]** をクリックします - ![列フィールド メニューを示すスクリーンショット](/assets/images/help/projects-v2/new-view.png) \ No newline at end of file + ![列フィールド メニューを示すスクリーンショット](/assets/images/help/projects-v2/new-view.png) diff --git a/translations/ja-JP/data/reusables/projects/open-item-menu.md b/translations/ja-JP/data/reusables/projects/open-item-menu.md index 66f48a0dca..5e48e08c83 100644 --- a/translations/ja-JP/data/reusables/projects/open-item-menu.md +++ b/translations/ja-JP/data/reusables/projects/open-item-menu.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 15b1ba8ed434c9c9c6bb81c0ca0376c2e42fca48 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 10c8c2b298fd4eaec742bf9efbc686d6f2bb3c0b +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147878632" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109411" --- -1. {% octicon "triangle-down" aria-label="the item menu" %} (テーブル レイアウトの場合) または {% octicon "kebab-horizontal" aria-label="the item menu" %} (ボード レイアウトの場合) を選びます。 \ No newline at end of file +1. {% octicon "triangle-down" aria-label="the item menu" %} (テーブル レイアウトの場合) または {% octicon "kebab-horizontal" aria-label="the item menu" %} (ボード レイアウトの場合) を選びます。 diff --git a/translations/ja-JP/data/reusables/projects/open-view-menu.md b/translations/ja-JP/data/reusables/projects/open-view-menu.md index cb88dd3387..31956ba97f 100644 --- a/translations/ja-JP/data/reusables/projects/open-view-menu.md +++ b/translations/ja-JP/data/reusables/projects/open-view-menu.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 0873b7b527997d2472413b016a12f2f413f06e86 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 167d4ab0b57e2af8ee07f720db569725829adf69 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880141" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109403" --- 1. 現在開いているビューの名前の横にある {% octicon "triangle-down" aria-label="the drop-down icon" %} をクリックします。 - ![ビュー メニュー アイコン示すスクリーンショット](/assets/images/help/projects-v2/view-menu-icon.png) \ No newline at end of file + ![ビュー メニュー アイコン示すスクリーンショット](/assets/images/help/projects-v2/view-menu-icon.png) diff --git a/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md b/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md index 66cb527f58..c13be1a16f 100644 --- a/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md +++ b/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: e9790db64c727836fb25001ef5160b0030a12da4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a811a75bedf573e347f2346a8872dd533b3a4466 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147614562" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108916" --- -Organization の所有者は、パブリック {% data variables.projects.projects_v2_and_v1 %} を作成したり、既存の {% data variables.projects.projects_v2_and_v1 %} の可視性をパブリックに変更したりする Organization のメンバーの機能を制御できます。 詳しくは、「[Organization のプロジェクトの可視性の変更を許可する](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)」をご覧ください。 \ No newline at end of file +Organization の所有者は、パブリック {% data variables.projects.projects_v2_and_v1 %} を作成したり、既存の {% data variables.projects.projects_v2_and_v1 %} の可視性をパブリックに変更したりする Organization のメンバーの機能を制御できます。 詳しくは、「[Organization のプロジェクトの可視性の変更を許可する](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)」をご覧ください。 diff --git a/translations/ja-JP/data/reusables/projects/save-view.md b/translations/ja-JP/data/reusables/projects/save-view.md index 3cf08b91e2..c6ba1ada3f 100644 --- a/translations/ja-JP/data/reusables/projects/save-view.md +++ b/translations/ja-JP/data/reusables/projects/save-view.md @@ -1,11 +1,11 @@ --- -ms.openlocfilehash: 9103637cf5f41c5c40b4328f050edf1c5ca8eabc -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b +ms.openlocfilehash: 2a7a472bbfeed56c58e483b61c2a140aa52e63e8 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147424222" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108875" --- {% data reusables.projects.open-view-menu %} 1. **[変更を保存]** をクリックします。 - ![保存メニュー項目が表示されたスクリーンショット](/assets/images/help/projects-v2/save-view.png) \ No newline at end of file + ![保存メニュー項目が表示されたスクリーンショット](/assets/images/help/projects-v2/save-view.png) diff --git a/translations/ja-JP/data/reusables/projects/select-an-item.md b/translations/ja-JP/data/reusables/projects/select-an-item.md index 363d00954b..57cdff7de9 100644 --- a/translations/ja-JP/data/reusables/projects/select-an-item.md +++ b/translations/ja-JP/data/reusables/projects/select-an-item.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: a78a08bd4cdf72ca732b4c2a664164d0f69f1815 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 8fef95ca781a57606206a89a8408bcd4774402e2 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424219" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109508" --- 1. 項目を選びます。 複数のアイテムを選択するには、以下のいずれかのようにしてください。 - command (Mac) または Ctrl (Windows または Linux) キーを押しながら各項目をクリックします。 - 1 つの項目を選んでから Shift+↑ または Shift+↓ キーを押して、選んだ項目の上または下にある追加項目を選びます。 - 1 つの項目を選んでから Shift キーを押し、もう 1 つの項目をクリックして、2 つの項目の間にあるすべての項目を選びます。 - - 1 つの行または項目を既に選んだ状態で、command+A (Mac) または Ctrl+A (Windows または Linux) を押して、列またはボード レイアウトのすべての項目、あるいはテーブル レイアウトのすべての項目を選びます。 \ No newline at end of file + - 1 つの行または項目を既に選んだ状態で、command+A (Mac) または Ctrl+A (Windows または Linux) を押して、列またはボード レイアウトのすべての項目、あるいはテーブル レイアウトのすべての項目を選びます。 diff --git a/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md b/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md index fe55c68405..c0b4d6f240 100644 --- a/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md +++ b/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md @@ -1,7 +1,14 @@ -{% ifversion fpt or ghec %} -{% note %} +--- +ms.openlocfilehash: 85db1024fd3a47bebaf0a6fef56843c8be2509a9 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148008724" +--- +{% ifversion fpt or ghec %} {% note %} -**Note:** The pull request merge queue feature is currently in limited public beta and subject to change. +**注:** pull request のマージ キュー機能は現在、限定的なパブリック ベータ版であり、変更される可能性があります。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md index 488608a956..37aeb9275e 100644 --- a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md +++ b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 50db50aff42d977575a89a2e22287b1672081ee4 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 1b3e7f64c7507fde4a126cddaca3c4a97247d967 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147881390" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109483" --- 強制コミットのサインオフは、Web インターフェイスを介して行われたコミットにのみ適用されます。 Git コマンド ライン インターフェイスを使用して行われたコミットは、コミット作成者が `--signoff` オプションを使用してコミットにサインオフする必要があります。 詳しくは、[Git ドキュメント](https://git-scm.com/docs/git-commit)を参照してください。 @@ -15,4 +15,4 @@ ms.locfileid: "147881390" コミットでサインオフする前に、コミット先のリポジトリを管理する規則とライセンスに準拠していることを確認する必要があります。 リポジトリでは、Linux Foundation の Developer Certificate of Origin などのサインオフ契約を使用できます。 詳しくは「[Developer Certificate of Origin](https://developercertificate.org/)」をご覧ください。 -コミットへの署名は、コミットのサインオフとは異なります。 詳しくは、「[コミットの署名の検証について](/authentication/managing-commit-signature-verification/about-commit-signature-verification)」をご覧ください。 \ No newline at end of file +コミットへの署名は、コミットのサインオフとは異なります。 詳しくは、「[コミットの署名の検証について](/authentication/managing-commit-signature-verification/about-commit-signature-verification)」をご覧ください。 diff --git a/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md b/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md index 105a68b9f5..c2f7cd1471 100644 --- a/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md +++ b/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145090538" ---- -{% data variables.product.prodname_security_advisories %}を使い、すでに別の場所で公開したセキュリティ脆弱性の詳細をコピーして新しいセキュリティアドバイザリに貼り付けることにより、その詳細を再度公開できます。 +You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory. diff --git a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md index d515bef08a..24ad8ee1f2 100644 --- a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md +++ b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 3657d22416c277ff6af595279480f31134d7b6d8 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: 8396c212c048ddf20c4b00d4891a21052555325e +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145117750" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109127" --- -{% data variables.product.product_name %}は、ユーザ認証にSAML SSOを使用します。 {% data variables.product.prodname_ghe_managed %}へのアクセスは、SAML 2.0標準をサポートするIdPから集中管理できます。 +{% data variables.product.product_name %}は、ユーザ認証にSAML SSOを使用します。 {% data variables.product.prodname_ghe_managed %}へのアクセスは、SAML 2.0標準をサポートするIdPから集中管理できます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/saml/authentication-loop.md b/translations/ja-JP/data/reusables/saml/authentication-loop.md index af2e5e526e..982fde3f9c 100644 --- a/translations/ja-JP/data/reusables/saml/authentication-loop.md +++ b/translations/ja-JP/data/reusables/saml/authentication-loop.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: e7dd0182fdc70186e5b3d137ac99cebd2ff562ea -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 7e0f711826a1f1ea1bee8cec18bf5b4614815174 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147093192" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109132" --- ## ユーザーが繰り返し認証するようにリダイレクトされる @@ -12,4 +12,4 @@ ms.locfileid: "147093192" SAML 応答で送信される `SessionNotOnOrAfter` 値によって、ユーザーが認証のために IdP にリダイレクトされるタイミングが決まります。 SAML セッション期間を 2 時間以下に構成した場合、期限切れの 5 分前に SAML セッションは {% data variables.product.prodname_dotcom_the_website %} によって更新されます。 セッション期間を 5 分以下に構成した場合、ユーザーは SAML 認証ループから抜け出せなくなる可能性があります。 -この問題を解決するには、最短 SAML セッション期間を 4 時間に構成することをお勧めします。 詳細については、「[SAML 構成リファレンス](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)」をご覧ください。 \ No newline at end of file +この問題を解決するには、最短 SAML セッション期間を 4 時間に構成することをお勧めします。 詳細については、「[SAML 構成リファレンス](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)」をご覧ください。 diff --git a/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md b/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md index 8208b7fd3f..f4a0bd2bb1 100644 --- a/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md +++ b/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: b0db396765557122de192fe6dde98aeeb0057ec2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: a9ba68f182b48a4186a4ae63909ef4e146d7c392 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147093208" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109133" --- ## エラー: "Current time is earlier than NotBefore condition" (現在の時刻は NotBefore 条件より前です) @@ -12,4 +12,4 @@ ms.locfileid: "147093208" {% ifversion ghes %}この問題を防ぐには、可能であれば、IdP と同じネットワーク タイム プロトコル (NTP) ソースを指すようにアプライアンスを設定することをお勧めします。 {% endif %}このエラーが発生した場合は、{% ifversion ghes %}アプライアンス{% else %}IdP {% endif %}の時刻が NTP サーバーと適切に同期していることを確認します。 -IdP の立場で ADFS を使っている場合は、{% data variables.product.prodname_dotcom %} のために ADFS の `NotBeforeSkew` も 1 分に設定します。 `NotBeforeSkew` を 0 に設定すると、ミリ秒などの非常に短い時間差でも認証の問題が発生する可能性があります。 \ No newline at end of file +IdP の立場で ADFS を使っている場合は、{% data variables.product.prodname_dotcom %} のために ADFS の `NotBeforeSkew` も 1 分に設定します。 `NotBeforeSkew` を 0 に設定すると、ミリ秒などの非常に短い時間差でも認証の問題が発生する可能性があります。 diff --git a/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md b/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md index 1fc5466e5c..e9b9febc25 100644 --- a/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md +++ b/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md @@ -1,8 +1,16 @@ +--- +ms.openlocfilehash: eef3fbd7285fbea49bf20ed9359b2a7c6c49fff1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109067" +--- {% ifversion ghae %} {% note %} -**Note:** {% data variables.product.prodname_ghe_managed %} single sign-on (SSO) support for Okta is currently in beta. +**注:** Okta に対する {% data variables.product.prodname_ghe_managed %} シングル サインオン (SSO) のサポートは、現在ベータ版です。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md index 02c945e55a..bd640b9263 100644 --- a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md +++ b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md @@ -1,10 +1,11 @@ --- -ms.openlocfilehash: 0626c11052a92500820ca0a3ac24f0cad784ebd6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: c1c07418ac678e38f387f9be4ebc00153558ae22 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145130456" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109308" --- 1. アプリケーションの名前の下にある **[サインオン]** をクリックします。 - ![Okta アプリケーションの [サインオン] タブのスクリーンショット](/assets/images/help/saml/okta-sign-on-tab.png) + + ![[サインオン] タブ](/assets/images/help/saml/okta-ae-sign-on-tab.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md b/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md index febffcf723..7e7d37cb1a 100644 --- a/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md +++ b/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md @@ -1,9 +1,11 @@ --- -ms.openlocfilehash: 0c41ccbde38c607916822e265d7fb749318db717 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: fef8d78e7518ea1b11d657f0ed82929847cd5575 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145130452" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108796" --- 1. [サインオン方法] で **[セットアップ手順の表示]** をクリックします。 + + ![[サインオン] タブ](/assets/images/help/saml/okta-ae-view-setup-instructions.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/saml/saml-accounts.md b/translations/ja-JP/data/reusables/saml/saml-accounts.md index a7b72ffe55..366783c3a0 100644 --- a/translations/ja-JP/data/reusables/saml/saml-accounts.md +++ b/translations/ja-JP/data/reusables/saml/saml-accounts.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 41c1afacc9dbebc6722e5b60cbd5a52b5786df5d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b5ea320db35c6a770853644bcdb50117d3da578d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147526821" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108790" --- SAML SSO を構成する場合、組織のメンバーは引き続き {% data variables.product.prodname_dotcom_the_website %} で個人アカウントにサインインします。 組織内の非パブリックのリソースにメンバーがアクセスすると、{% data variables.product.prodname_dotcom %} により、認証のためにメンバーが IdP にリダイレクトされます。 認証に成功すると、IdP はメンバーを {% data variables.product.prodname_dotcom %} にリダイレクトして戻します。 詳細については、「[SAML のシングル サインオンでの認証について](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)」を参照してください。 @@ -12,4 +12,4 @@ SAML SSO を構成する場合、組織のメンバーは引き続き {% data va **注:** SAML SSO は、{% data variables.product.prodname_dotcom %} の通常のサインイン プロセスに代わるものではありません。 {% data variables.product.prodname_emus %} を使用する場合を除き、メンバーは {% data variables.product.prodname_dotcom_the_website %} で引き続き個人アカウントにサインインし、各個人アカウントは IdP で外部 ID にリンクされます。 -{% endnote %} \ No newline at end of file +{% endnote %} 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 af2f8af01c..3d68fc424b 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 @@ -9,8 +9,7 @@ Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id
amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id
aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} -Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key{% endif %} +Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token
aws_temporary_access_key_id
aws_secret_access_key Asana | Asana {% data variables.product.pat_generic %} | asana_personal_access_token Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt @@ -31,14 +30,12 @@ Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae < 3.4 %} 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 %} -Beamer | Beamer API Key | beamer_api_key{% endif %} +Beamer | Beamer API Key | beamer_api_key Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} -Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token{% endif %} +Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token Databricks | Databricks Access Token | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} DevCycle | DevCycle Client API Key | devcycle_client_api_key @@ -69,8 +66,7 @@ Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key 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 %} -FullStory | FullStory API Key | fullstory_api_key{% endif %} +FullStory | FullStory API Key | fullstory_api_key GitHub | GitHub {% data variables.product.pat_generic %} | github_personal_access_token GitHub | GitHub OAuth Access Token | github_oauth_access_token GitHub | GitHub Refresh Token | github_refresh_token @@ -80,14 +76,11 @@ GitHub | GitHub SSH Private Key | github_ssh_private_key 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 %} -Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} +Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} -Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} -Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret{% endif %} +Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id
google_cloud_storage_access_key_secret +Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Google | Google OAuth Access Token | google_oauth_access_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} @@ -97,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %} Grafana | Grafana API Key | grafana_api_key HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %} HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token @@ -104,10 +99,8 @@ Ionic | Ionic {% data variables.product.pat_generic %} | ionic_personal_access_t Ionic | Ionic Refresh Token | ionic_refresh_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %} -{%- 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 %} -JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} +JFrog | JFrog Platform Access Token | jfrog_platform_access_token +JFrog | JFrog Platform API Key | jfrog_platform_api_key Linear | Linear API Key | linear_api_key Linear | Linear OAuth Access Token | linear_oauth_access_token Lob | Lob Live API Key | lob_live_api_key @@ -125,14 +118,10 @@ Meta | Facebook Access Token | facebook_access_token Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %} -{%- 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 %} -New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- 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 %} -New Relic | New Relic License Key | new_relic_license_key{% endif %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key +New Relic | New Relic REST API Key | new_relic_rest_api_key +New Relic | New Relic Insights Query Key | new_relic_insights_query_key +New Relic | New Relic License Key | new_relic_license_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Notion | Notion Integration Token | notion_integration_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} @@ -145,14 +134,10 @@ Onfido | Onfido Live API Token | onfido_live_api_token Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token OpenAI | OpenAI API Key | openai_api_key Palantir | Palantir JSON Web Token | palantir_jwt -{%- 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 %} -PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- 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 %} -Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id
plivo_auth_token{% endif %} +PlanetScale | PlanetScale Database Password | planetscale_database_password +PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token +PlanetScale | PlanetScale Service Token | planetscale_service_token +Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id
plivo_auth_token Postman | Postman API Key | postman_api_key {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %} Prefect | Prefect Server API Key | prefect_server_api_key @@ -173,10 +158,8 @@ Samsara | Samsara OAuth Access Token | samsara_oauth_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} Segment | Segment Public API Token | segment_public_api_token{% endif %} SendGrid | SendGrid API Key | sendgrid_api_key -{%- 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 %} -Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} +Sendinblue | Sendinblue API Key | sendinblue_api_key +Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key Shippo | Shippo Live API Token | shippo_live_api_token Shippo | Shippo Test API Token | shippo_test_api_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md index bf25ea801c..879300206c 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md +++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: ba22b3461f3e8bf93257698d2c6f4eb4bc863949 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 +ms.openlocfilehash: 46850cadc908d94d514fde76ee0fecbddce0affe +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147409831" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109061" --- {% ifversion secret-scanning-push-protection-email %}共同作成者がシークレットのプッシュ保護ブロックをバイパスすると、{% data variables.product.prodname_dotcom %} により、電子メール通知をオプトインした Organization の所有者、セキュリティ マネージャー、リポジトリ管理者にも電子メール アラートが送信されます。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md index df11ed08b7..58efbca68b 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md +++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: d22214ea8eb5bc89912bed3c43a678fba80f014b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 3d0f861b8ee9ff6b4e948dee7dfb67a648021404 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147578734" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109388" --- -シークレットが本物であることを確認したら、再度プッシュする前に、ブランチから ("それが表示されるすべてのコミットから") シークレットを削除する必要があります。 \ No newline at end of file +シークレットが本物であることを確認したら、再度プッシュする前に、ブランチから ("それが表示されるすべてのコミットから") シークレットを削除する必要があります。 diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md index 32360458e8..eacc4cb86f 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md +++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: 7ebce174e896689b1976b9d43f1f0884ce065229 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 7bb1603715c255f08ac0bfbe7ff2cdbfe99a3134 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147683800" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109121" --- Web UI を使用して、プッシュ保護が有効になっているシークレット スキャンを使用して、サポートされているシークレットをリポジトリまたは organization にコミットすると、{% data variables.product.prodname_dotcom %} によってプッシュがブロックされます。 @@ -18,4 +18,4 @@ Web UI を使用して、プッシュ保護が有効になっているシーク ![シークレット スキャンのプッシュ保護のためにブロックされた Web UI でのコミットを示すスクリーンショット](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md index bc7964470e..3c4c6a964f 100644 --- a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md +++ b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145137531" ---- -{% data variables.product.prodname_security_advisories %} を使用すると、リポジトリメンテナがプロジェクトのセキュリティの脆弱性について非公開で議論し、修正できます。 共同で修正を行った後、リポジトリ保守担当者はセキュリティ アドバイザリを公開して、セキュリティの脆弱性をプロジェクトのコミュニティに開示することができます。 セキュリティ アドバイザリを公開することにより、リポジトリ保守担当者は、コミュニティがいっそう簡単にパッケージの依存関係を更新したり、セキュリティの脆弱性の影響を調べたりできるようにします。 +Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities. diff --git a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md index 807851a0fe..99c5c8d771 100644 --- a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md +++ b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md @@ -1,10 +1,10 @@ --- -ms.openlocfilehash: f6fdffa80f99a405c65fc6f536b8a821cc1c334d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 55863906d744c997149aa2fffd6541f32e42c0d1 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147525741" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108905" --- {% ifversion security-overview-displayed-alerts %} セキュリティの概要に示される情報は、リポジトリへのアクセス権や、{% data variables.product.prodname_GH_advanced_security %} がこれらのリポジトリによって使用されているかどうかに応じて異なります。 -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/security-overview/permissions.md b/translations/ja-JP/data/reusables/security-overview/permissions.md index 2cf85d19c5..43dd55172d 100644 --- a/translations/ja-JP/data/reusables/security-overview/permissions.md +++ b/translations/ja-JP/data/reusables/security-overview/permissions.md @@ -1 +1 @@ -Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} 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 %}. Members of a team can see the security overview for repositories that the team has admin privileges for. +{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %} diff --git a/translations/ja-JP/data/reusables/security/displayed-information.md b/translations/ja-JP/data/reusables/security/displayed-information.md index 91f9a8a279..fa5451eb0e 100644 --- a/translations/ja-JP/data/reusables/security/displayed-information.md +++ b/translations/ja-JP/data/reusables/security/displayed-information.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: c9e2c1bf2b01805ed973effedd219c3552ac2bf4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "146455670" ---- -既存のリポジトリで1つ以上のセキュリティ及び分析機能を有効化すると、数分のうちに{% data variables.product.prodname_dotcom %}上に結果が表示されます。 +When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes: -- 既存のすべてのリポジトリは、選択された設定を持ちます。 -- 新しいリポジトリに対するチェックボックスを有効化していれば、新しいリポジトリは選択された設定に従います。{% ifversion fpt or ghec %} -- 関連するサービスに適用するマニフェストファイルをスキャンするために権限を使用します。 -- 有効化すると、依存関係グラフに依存関係情報が表示されます。 -- 有効化すると、{% data variables.product.prodname_dotcom %} により、脆弱な依存関係またはマルウェアに対して {% data variables.product.prodname_dependabot_alerts %}が生成されます。{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} -- 有効化すると、{% data variables.product.prodname_dependabot %} セキュリティ更新プログラムは、{% data variables.product.prodname_dependabot_alerts %} がトリガーされたときに、脆弱な依存関係をアップグレードするための pull request を作成します。{% endif %} +- All the existing repositories will have the selected configuration. +- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% ifversion fpt or ghec %} +- We use the permissions to scan for manifest files to apply the relevant services. +- If enabled, you'll see dependency information in the dependency graph. +- If enabled, {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies or malware.{% endif %}{% ifversion fpt or ghec or ghes %} +- If enabled, {% data variables.product.prodname_dependabot %} security updates will create pull requests to upgrade vulnerable dependencies when {% data variables.product.prodname_dependabot_alerts %} are triggered.{% endif %} diff --git a/translations/ja-JP/data/reusables/ssh/key-type-support.md b/translations/ja-JP/data/reusables/ssh/key-type-support.md index 324873282a..2c2295e0ba 100644 --- a/translations/ja-JP/data/reusables/ssh/key-type-support.md +++ b/translations/ja-JP/data/reusables/ssh/key-type-support.md @@ -25,4 +25,4 @@ Your site administrator can adjust the cutoff date for connections using RSA-SHA {% endnote %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/support/entitlements-note.md b/translations/ja-JP/data/reusables/support/entitlements-note.md index 426b28570e..79040074fe 100644 --- a/translations/ja-JP/data/reusables/support/entitlements-note.md +++ b/translations/ja-JP/data/reusables/support/entitlements-note.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 52b42a427d098d34e26dc12b20fce44ef15e7458 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 35ed9fffb50a66b6867f71bf0e7e579284b9ee5d +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147080101" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109387" --- {% note %} **注:** Organization または Enterprise アカウントに関連付けられたチケットを表示するには、Enterprise サポート エンタイトルメントが必要です。 詳細については、「[Managing support entitlements for your enterprise (エンタープライズのサポート エンタイトルメントの管理)](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。 -{% endnote %} \ No newline at end of file +{% endnote %} diff --git a/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md b/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md index 4a4f38ec09..8a7b4dccd2 100644 --- a/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md +++ b/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 88b8399eab75b7ac5a3c2f0e12eec2fc0000df2d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fb2826ec7adf7edcff710866d08654c7f94ab484 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147080095" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108868" --- 1. [GitHub サポート ポータル](https://support.github.com/)に移動します。 1. ヘッダーで **[マイ チケット]** をクリックします。 - ![GitHub サポート ポータルのヘッダーに [マイ チケット] リンクが示されたスクリーンショット。](/assets/images/help/support/my-tickets-header.png) \ No newline at end of file + ![GitHub サポート ポータルのヘッダーに [マイ チケット] リンクが示されたスクリーンショット。](/assets/images/help/support/my-tickets-header.png) diff --git a/translations/ja-JP/data/reusables/supported-languages/C.md b/translations/ja-JP/data/reusables/supported-languages/C.md index 0c5b57472a..77a301dce0 100644 --- a/translations/ja-JP/data/reusables/supported-languages/C.md +++ b/translations/ja-JP/data/reusables/supported-languages/C.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 586b13b105c32f8b67218cc277af8916dc2c8783 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052201" ---- -| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/Cpp.md b/translations/ja-JP/data/reusables/supported-languages/Cpp.md index dae804a16a..5a255a3ae3 100644 --- a/translations/ja-JP/data/reusables/supported-languages/Cpp.md +++ b/translations/ja-JP/data/reusables/supported-languages/Cpp.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 801a3486a32e80dbb0a85cef76c2c6887babd258 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147052033" ---- -| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/Cs.md b/translations/ja-JP/data/reusables/supported-languages/Cs.md index f0d4efd984..dc5fa3e1e8 100644 --- a/translations/ja-JP/data/reusables/supported-languages/Cs.md +++ b/translations/ja-JP/data/reusables/supported-languages/Cs.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 5e148185ae940f67f4137f209ce451f74faa1a7e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052361" ---- -| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% endif %} +| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
`dotnet` CLI |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/go.md b/translations/ja-JP/data/reusables/supported-languages/go.md index fa73b331e6..2670d677ba 100644 --- a/translations/ja-JP/data/reusables/supported-languages/go.md +++ b/translations/ja-JP/data/reusables/supported-languages/go.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d811deaf63f404f0ded3952a4411fc519d29547a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147066979" ---- -| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Go モジュール | {% octicon "check" aria-label="The check icon" %}
Go モジュール | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Go モジュール {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
Go モジュール {% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Go modules | {% octicon "check" aria-label="The check icon" %}
Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Go modules | {% octicon "check" aria-label="The check icon" %}
Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/java.md b/translations/ja-JP/data/reusables/supported-languages/java.md index 0e516886f1..9572164283 100644 --- a/translations/ja-JP/data/reusables/supported-languages/java.md +++ b/translations/ja-JP/data/reusables/supported-languages/java.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 7429b486c393de2a4c5184914b3528d1f189c2a5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 2e8ea634a95d2bca03b70aef430be7e638272605 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052025" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109452" --- -| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven {% ifversion ghes > 3.2 %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% endif %} +| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/javascript.md b/translations/ja-JP/data/reusables/supported-languages/javascript.md index 3e347bf24f..d11df349ce 100644 --- a/translations/ja-JP/data/reusables/supported-languages/javascript.md +++ b/translations/ja-JP/data/reusables/supported-languages/javascript.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: dbf7349c32cb38d666f89d149831f5254e2afee2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 9d072e402eca457ea6ebc803c1c56461d909e11a +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052161" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148108874" --- -| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% endif %} +| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/php.md b/translations/ja-JP/data/reusables/supported-languages/php.md index 47f8aeca50..a6cde8219a 100644 --- a/translations/ja-JP/data/reusables/supported-languages/php.md +++ b/translations/ja-JP/data/reusables/supported-languages/php.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: eb8ee6547c65b4cea6e6528d2f96132f1936e0d6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052242" ---- -| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Composer {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
Composer{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %}
Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/products-table-header.md b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md index 23d8e71ca4..6147ff8b8b 100644 --- a/translations/ja-JP/data/reusables/supported-languages/products-table-header.md +++ b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md @@ -1,9 +1,4 @@ ---- -ms.openlocfilehash: 2bbdb89e1c3f02014566e38f43cd482cc54af641 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052234" ---- -{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [コード ナビゲーション](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ、{% data variables.product.prodname_dependabot_alerts %}、{% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ、{% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %}、{% data variables.product.prodname_dependabot_security_updates %}{% endif %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes > 3.2 %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: {% ifversion ghes > 3.2 %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %} +{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | +| :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | +| :-- | :-: | :-: {% ifversion ghes %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | +| :-- | :-: | :-: | :-: |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/python.md b/translations/ja-JP/data/reusables/supported-languages/python.md index b5d9773952..d8df9a72ba 100644 --- a/translations/ja-JP/data/reusables/supported-languages/python.md +++ b/translations/ja-JP/data/reusables/supported-languages/python.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0e9bc62ae013232cf0a15ebb3dfd1948b672480e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052337" ---- -| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
precise | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %}
pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/ruby.md b/translations/ja-JP/data/reusables/supported-languages/ruby.md index a0be42ff11..69eaaa15cd 100644 --- a/translations/ja-JP/data/reusables/supported-languages/ruby.md +++ b/translations/ja-JP/data/reusables/supported-languages/ruby.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: a740daee0bb180392f099956cf9dc26b6b8c83ed -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 +ms.openlocfilehash: 7609bd15d8e77a5da778cfb3a4acd21ea7884e46 +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147885045" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109372" --- -| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
RubyGems {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
RubyGems{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% endif %} +| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %}
RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
RubyGems |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/scala.md b/translations/ja-JP/data/reusables/supported-languages/scala.md index 01b9533ffc..4da351ea79 100644 --- a/translations/ja-JP/data/reusables/supported-languages/scala.md +++ b/translations/ja-JP/data/reusables/supported-languages/scala.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3e5390b74f8d438fc7f83cd2f9e1e6917d4282f3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052329" ---- -| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Maven | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Maven、Gradle {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} +| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Maven | {% octicon "check" aria-label="The check icon" %}
Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %}
Maven, Gradle | {% octicon "check" aria-label="The check icon" %}
Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}1 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %} diff --git a/translations/ja-JP/data/reusables/supported-languages/typescript.md b/translations/ja-JP/data/reusables/supported-languages/typescript.md index 8500ddfb00..168d8b203e 100644 --- a/translations/ja-JP/data/reusables/supported-languages/typescript.md +++ b/translations/ja-JP/data/reusables/supported-languages/typescript.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 728285dc8fbdfcfa3e6a2f047383bcdc7875b8ff -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 6128eeee4e46b139b78ce717ed3723ba0dbba3ba +ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147052097" +ms.lasthandoff: 10/25/2022 +ms.locfileid: "148109251" --- -| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}
npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% endif %} +| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm、Yarn | {% octicon "check" aria-label="The check icon" %}
npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}
npm |{% endif %} diff --git a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md index a6d3d93624..51191b7a9e 100644 --- a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md +++ b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 3e175aefd9a243a098b5c35ca6d4068a651d2f61 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147878487" ---- -Webhook REST API を使用すれば、リポジトリ、組織、アプリ Webhook の管理ができます。{% ifversion fpt or ghes > 3.2 or ghae or ghec %}この API を使って Webhook の配信を一覧表示したり、Webhook の個々の配信を取得して再配信したりできます。これは、外部のアプリまたはサービスに統合できます。{% endif %}REST API を使用して、Webhook の構成を変更することもできます。 たとえば、ペイロードURL、コンテントタイプ、SSLの検証、シークレットを変更できます。 詳細については、次を参照してください。 +The webhook REST APIs enable you to manage repository, organization, and app webhooks. You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service. You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret. For more information, see: -- [リポジトリ Webhook REST API](/rest/reference/webhooks#repository-webhooks) -- [組織の Webhook REST API](/rest/reference/orgs#webhooks) -- [{% data variables.product.prodname_github_app %} Webhook REST API](/rest/reference/apps#webhooks) +- [Repository Webhooks REST API](/rest/reference/webhooks#repository-webhooks) +- [Organization Webhooks REST API](/rest/reference/orgs#webhooks) +- [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks) diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 16646ba56b..09ba187929 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -72,7 +72,7 @@ prodname_codeql_cli: 'CodeQL CLI' # CodeQL usually bumps its minor version for each minor version of GHES. # Update this whenever a new enterprise version of CodeQL is being prepared. codeql_cli_ghes_recommended_version: >- - {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %} + {% ifversion ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %} # Projects v2 prodname_projects_v2: 'Projects' diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv index 352c55ef51..0c39b2403a 100644 --- a/translations/log/msft-ja-resets.csv +++ b/translations/log/msft-ja-resets.csv @@ -72,6 +72,7 @@ translations/ja-JP/content/admin/identity-and-access-management/using-enterprise translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/index.md,file deleted because it no longer exists in main translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups.md,file deleted because it no longer exists in main translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,file deleted because it no longer exists in main +translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,file deleted because it no longer exists in main translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,file deleted because it no longer exists in main translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md,file deleted because it no longer exists in main @@ -80,7 +81,20 @@ translations/ja-JP/content/authentication/troubleshooting-commit-signature-verif translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main +translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main @@ -212,6 +226,7 @@ translations/ja-JP/content/site-policy/privacy-policies/github-data-protection-a translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main translations/ja-JP/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main +translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main @@ -229,7 +244,9 @@ translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md,file translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main +translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main +translations/ja-JP/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main @@ -237,6 +254,7 @@ translations/ja-JP/data/reusables/education/upgrade-organization.md,file deleted translations/ja-JP/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main +translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise_management_console/username_normalization.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main @@ -288,7 +306,6 @@ translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifi translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags @@ -302,7 +319,10 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error @@ -328,9 +348,7 @@ translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/d translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags -translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md,broken liquid tags translations/ja-JP/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags -translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error @@ -354,6 +372,7 @@ translations/ja-JP/content/actions/quickstart.md,broken liquid tags translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,rendering error translations/ja-JP/content/actions/security-guides/encrypted-secrets.md,rendering error translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error +translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md,rendering error translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md,rendering error translations/ja-JP/content/actions/using-workflows/about-workflows.md,rendering error translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md,broken liquid tags @@ -407,8 +426,12 @@ translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initi translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags +translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error +translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error +translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md,rendering error translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags +translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags @@ -571,6 +594,7 @@ translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/a translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags +translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error @@ -589,22 +613,26 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error -translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error -translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error +translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error +translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error +translations/ja-JP/content/code-security/dependabot/index.md,broken liquid tags translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error +translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error +translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags translations/ja-JP/content/code-security/getting-started/github-security-features.md,rendering error translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,rendering error translations/ja-JP/content/code-security/getting-started/securing-your-repository.md,rendering error +translations/ja-JP/content/code-security/index.md,rendering error translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md,rendering error translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error @@ -621,6 +649,7 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags +translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags @@ -659,6 +688,7 @@ translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-pre translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags +translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags @@ -766,8 +796,12 @@ translations/ja-JP/content/graphql/reference/mutations.md,broken liquid tags translations/ja-JP/content/graphql/reference/objects.md,broken liquid tags translations/ja-JP/content/graphql/reference/unions.md,broken liquid tags translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags +translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error +translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error +translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags +translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,broken liquid tags @@ -780,15 +814,21 @@ translations/ja-JP/content/organizations/granting-access-to-your-organization-wi translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error +translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md,rendering error +translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md,rendering error +translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md,rendering error translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error +translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md,rendering error translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error +translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags +translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags @@ -816,6 +856,7 @@ translations/ja-JP/content/packages/working-with-a-github-packages-registry/work translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags +translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error translations/ja-JP/content/pages/index.md,broken liquid tags translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags @@ -859,6 +900,7 @@ translations/ja-JP/content/repositories/creating-and-managing-repositories/trans translations/ja-JP/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error +translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,broken liquid tags translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error @@ -900,6 +942,7 @@ translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md,brok translations/ja-JP/content/rest/guides/traversing-with-pagination.md,rendering error translations/ja-JP/content/rest/guides/working-with-comments.md,broken liquid tags translations/ja-JP/content/rest/migrations/source-imports.md,broken liquid tags +translations/ja-JP/content/rest/overview/api-previews.md,rendering error translations/ja-JP/content/rest/overview/other-authentication-methods.md,broken liquid tags translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md,rendering error translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags @@ -920,8 +963,10 @@ translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponso translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md,rendering error translations/ja-JP/content/support/learning-about-github-support/about-github-support.md,rendering error +translations/ja-JP/data/glossaries/external.yml,broken liquid tags translations/ja-JP/data/learning-tracks/actions.yml,broken liquid tags translations/ja-JP/data/learning-tracks/admin.yml,broken liquid tags +translations/ja-JP/data/learning-tracks/code-security.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml,rendering error translations/ja-JP/data/release-notes/enterprise-server/2-21/17.yml,rendering error translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml,rendering error @@ -962,7 +1007,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml,rendering erro translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md,broken liquid tags translations/ja-JP/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags -translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md,rendering error +translations/ja-JP/data/reusables/actions/add-hosted-runner.md,broken liquid tags translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md,broken liquid tags translations/ja-JP/data/reusables/actions/cache-default-size.md,broken liquid tags translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error @@ -979,6 +1024,8 @@ translations/ja-JP/data/reusables/actions/github-connect-resolution.md,broken li translations/ja-JP/data/reusables/actions/hosted-runner-security.md,broken liquid tags translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags +translations/ja-JP/data/reusables/actions/message-parameters.md,broken liquid tags +translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md,rendering error translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error translations/ja-JP/data/reusables/actions/ref_name-description.md,broken liquid tags translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md,rendering error @@ -986,6 +1033,7 @@ translations/ja-JP/data/reusables/actions/reusable-workflow-calling-syntax.md,re translations/ja-JP/data/reusables/actions/reusable-workflows.md,rendering error translations/ja-JP/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error translations/ja-JP/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error +translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md,rendering error translations/ja-JP/data/reusables/actions/self-hosted-runner-check-installation-success.md,broken liquid tags translations/ja-JP/data/reusables/actions/self-hosted-runner-management-permissions-required.md,rendering error translations/ja-JP/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags @@ -1003,6 +1051,7 @@ translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error +translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md,rendering error @@ -1011,8 +1060,9 @@ translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md, translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error translations/ja-JP/data/reusables/branches/new-repo-default-branch.md,broken liquid tags translations/ja-JP/data/reusables/classroom/about-autograding.md,broken liquid tags -translations/ja-JP/data/reusables/code-scanning/analyze-go.md,broken liquid tags +translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md,broken liquid tags translations/ja-JP/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags +translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags translations/ja-JP/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error @@ -1063,6 +1113,7 @@ translations/ja-JP/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken translations/ja-JP/data/reusables/enterprise-accounts/security-tab.md,rendering error translations/ja-JP/data/reusables/enterprise/apply-configuration.md,broken liquid tags translations/ja-JP/data/reusables/enterprise/rate_limit.md,broken liquid tags +translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md,rendering error translations/ja-JP/data/reusables/enterprise/test-in-staging.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_installation/download-package.md,broken liquid tags @@ -1079,7 +1130,6 @@ translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentica translations/ja-JP/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags translations/ja-JP/data/reusables/files/choose-commit-email.md,broken liquid tags -translations/ja-JP/data/reusables/gated-features/code-scanning.md,broken liquid tags translations/ja-JP/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags translations/ja-JP/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error translations/ja-JP/data/reusables/gated-features/secret-scanning-partner.md,rendering error @@ -1093,7 +1143,6 @@ translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.m translations/ja-JP/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags translations/ja-JP/data/reusables/git/git-push.md,broken liquid tags translations/ja-JP/data/reusables/git/provide-credentials.md,broken liquid tags -translations/ja-JP/data/reusables/github-ae/saml-idp-table.md,broken liquid tags translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,broken liquid tags translations/ja-JP/data/reusables/large_files/storage_assets_location.md,broken liquid tags translations/ja-JP/data/reusables/large_files/use_lfs_tip.md,broken liquid tags @@ -1105,9 +1154,16 @@ translations/ja-JP/data/reusables/organizations/billing_plans.md,rendering error translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error translations/ja-JP/data/reusables/organizations/member-privileges.md,rendering error translations/ja-JP/data/reusables/organizations/navigate-to-org.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/new_team.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/org_settings.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/organization-wide-project.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/owners-team.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/people.md,broken liquid tags translations/ja-JP/data/reusables/organizations/repository-defaults.md,rendering error translations/ja-JP/data/reusables/organizations/security-and-analysis.md,rendering error translations/ja-JP/data/reusables/organizations/security.md,rendering error +translations/ja-JP/data/reusables/organizations/specific_team.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/teams.md,broken liquid tags translations/ja-JP/data/reusables/organizations/teams_sidebar.md,rendering error translations/ja-JP/data/reusables/organizations/verified-domains.md,rendering error translations/ja-JP/data/reusables/package_registry/authenticate-packages.md,broken liquid tags @@ -1115,6 +1171,7 @@ translations/ja-JP/data/reusables/package_registry/authenticate-to-container-reg translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags +translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/packages-billing.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/required-scopes.md,broken liquid tags translations/ja-JP/data/reusables/pages/build-failure-email-server.md,broken liquid tags @@ -1125,7 +1182,6 @@ translations/ja-JP/data/reusables/pages/sidebar-pages.md,rendering error translations/ja-JP/data/reusables/projects/enable-basic-workflow.md,broken liquid tags translations/ja-JP/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags translations/ja-JP/data/reusables/pull_requests/default_merge_option.md,broken liquid tags -translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags translations/ja-JP/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags @@ -1139,6 +1195,7 @@ translations/ja-JP/data/reusables/repositories/navigate-to-code-security-and-ana translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags translations/ja-JP/data/reusables/repositories/navigate-to-repo.md,broken liquid tags translations/ja-JP/data/reusables/repositories/repository-branches.md,rendering error +translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md,broken liquid tags translations/ja-JP/data/reusables/repositories/sidebar-notifications.md,rendering error translations/ja-JP/data/reusables/repositories/suggest-changes.md,broken liquid tags translations/ja-JP/data/reusables/repositories/you-can-fork.md,broken liquid tags @@ -1150,7 +1207,6 @@ translations/ja-JP/data/reusables/saml/authorized-creds-info.md,broken liquid ta translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md,broken liquid tags translations/ja-JP/data/reusables/saml/create-a-machine-user.md,broken liquid tags translations/ja-JP/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags -translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md,broken liquid tags translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags translations/ja-JP/data/reusables/scim/after-you-configure-saml.md,rendering error translations/ja-JP/data/reusables/scim/enterprise-account-scim.md,broken liquid tags @@ -1160,7 +1216,9 @@ translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scann translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md,broken liquid tags translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error +translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags translations/ja-JP/data/reusables/security-overview/permissions.md,rendering error +translations/ja-JP/data/reusables/security/displayed-information.md,broken liquid tags translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags translations/ja-JP/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags translations/ja-JP/data/reusables/ssh/about-ssh.md,broken liquid tags @@ -1168,6 +1226,14 @@ translations/ja-JP/data/reusables/ssh/key-type-support.md,rendering error translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags translations/ja-JP/data/reusables/support/help_resources.md,rendering error translations/ja-JP/data/reusables/support/submit-a-ticket.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/C.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/Cpp.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/Cs.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/go.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/php.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/products-table-header.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/python.md,broken liquid tags +translations/ja-JP/data/reusables/supported-languages/scala.md,broken liquid tags translations/ja-JP/data/reusables/user-settings/access_applications.md,rendering error translations/ja-JP/data/reusables/user-settings/account_settings.md,rendering error translations/ja-JP/data/reusables/user-settings/appearance-settings.md,rendering error @@ -1185,6 +1251,7 @@ translations/ja-JP/data/reusables/user-settings/ssh.md,rendering error translations/ja-JP/data/reusables/webhooks/pull_request_properties.md,broken liquid tags translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags +translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags translations/ja-JP/data/variables/product.yml,broken liquid tags translations/ja-JP/data/variables/projects.yml,broken liquid tags