diff --git a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md index 6a7c5dec5e..3c274fc8e7 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md @@ -88,7 +88,7 @@ This section explains how you can use release management to distribute updates t ### Good practices for release management -If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's major version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility. +If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's patch version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility. Under this release management approach, users should not be referencing an action's default branch, as it's likely to contain the latest code and consequently might be unstable. Instead, you can recommend that your users specify a major version when using your action, and only direct them to a more specific version if they encounter issues. 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 2aca610995..c77d2b5156 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 @@ -53,8 +53,8 @@ name: Create issue on commit on: [ push ] jobs: - create_commit: - runs-on: ubuntu-latest + create_issue: + runs-on: ubuntu-latest permissions: issues: write steps: diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index 0542427cee..e336ae0ea7 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -149,7 +149,7 @@ With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{ ### Using starter workflows for code scanning {% data reusables.advanced-security.starter-workflows-beta %} -{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available. +{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. ゼロから始めるのではなく、提案されるこれらのワークフローを使って、独自の{% data variables.product.prodname_code_scanning %}ワークフローを構築できます。 {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)." diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 8bbfa3afa8..bbdcf5a7d3 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -109,6 +109,7 @@ macOS 仮想マシンのハードウェア仕様: For the overall list of included tools for each runner operating system, see the links below: +* [Ubuntu 22.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) * [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md) * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) diff --git a/translations/ja-JP/content/admin/code-security/index.md b/translations/ja-JP/content/admin/code-security/index.md index 970c4013fb..bcd53ce82c 100644 --- a/translations/ja-JP/content/admin/code-security/index.md +++ b/translations/ja-JP/content/admin/code-security/index.md @@ -4,7 +4,6 @@ shortTitle: Manage code security intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.' versions: ghes: '*' - ghec: '*' ghae: '*' topics: - Enterprise diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md deleted file mode 100644 index 443ca3a510..0000000000 --- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md +++ /dev/null @@ -1,403 +0,0 @@ ---- -title: Deploying GitHub Advanced Security in your enterprise -intro: 'Learn how to plan, prepare, and implement a phased approach for rolling out {% data variables.product.prodname_GH_advanced_security %} (GHAS) in your enterprise.' -product: '{% data reusables.gated-features.advanced-security %}' -redirect_from: - - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise -miniTocMaxHeadingLevel: 3 -versions: - ghes: '*' - ghec: '*' -type: how_to -topics: - - Advanced Security - - Code scanning - - Enterprise - - Security ---- - -## Overview of the deployment process - -{% data reusables.security.overview-of-phased-approach-for-ghas-rollout %} - -For a high-level summary of these different phases, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)." - -Before starting your deployment, we recommend you review the prerequisites for installing GHAS and best practices for GHAS deployment in "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)." - -## {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff - -{% note %} - -{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 0 may last roughly between 1-4 weeks. This range can vary depending on your release needs and any necessary approvals your company may need on the deployment plan. - -{% endnote %} - -The goal of the planning and kickoff phase is to ensure that you have all of your people, processes, and technologies set up and ready for implementing GHAS. - -To help you reach buy-in from the executive sponsor, we recommend preparing and aligning on a rollout plan and goals before releasing GHAS in your enterprise. - -As a part of a phased rollout strategy, we recommend that you identify high-impact and critical teams or applications that should be targeted to join GHAS before the rest of your enterprise. - -If a phased rollout doesn't work for your enterprise, you can skip to the [pilot project phase](#--phase-1-pilot-projects). - -If you’re working with {% data variables.product.prodname_professional_services %}, during this phase you will also establish a plan for how your teams will work together throughout the rollout and implementation process. The {% data variables.product.prodname_professional_services_team %} team can support you with the creation of the phased rollout plan and goals as needed. - -### Step 1: Kickoff meeting with {% data variables.product.prodname_professional_services %} (optional) - -If you signed up for {% data variables.product.prodname_professional_services %}, you’ll begin the rollout and implementation process by meeting with your Services representative. - -If you haven't signed up for {% data variables.product.prodname_professional_services %}, you can skip to the next step. - -The goal of this meeting is to align the two teams on the necessary information to begin crafting a rollout and implementation plan that will work best for your company. In preparation for this meeting, we have created a survey that will help us better prepare for the discussion. Your Services representative will send you this survey. - -To help you prepare for this initial meeting, review these topics. - -- Aligning on how your company and {% data variables.product.prodname_professional_services %} will work best together - - Setting expectations on how to best utilize service hours/days purchased - - Communications plans/frequency of meetings - - Roles and responsibilities -- Review of how GHAS works within the Software Development Life cycle (SDLC). Your {% data variables.product.prodname_professional_services %} representative will explain how GHAS works. -- Review of best practices for deploying GHAS. This is offered as a refresher if your team finds it valuable or if your enterprise did not participate in the Proof of Concept (POC) exercise. This review includes a discussion of your existing Application Security program and its level of maturity, against something like the DevSecOps maturity model. -- Alignment on next steps for your GHAS deployment. Your {% data variables.product.prodname_professional_services %} representative will outline your next steps and the support you can expect from your partnership. - -To help you plan your rollout strategy, you can also expect to discuss these questions: - - How many teams will be enabled? - - What is the anatomy of the teams’ repositories? (Tech stack, current tooling, etc.) - - Some of this might have already been covered during the Proof of Concept exercise if your company participated. If not, this is a crucial time to discuss this. - - What level of adoption do we expect to be organic, assisted, or inorganic? - - What does assisted adoption look like from a resourcing and documentation perspective? - - How will you manage inorganic adoption down the line? (For example, using policy enforcement or centrally managed workflows.) - -### Step 2: Internal kickoff at your company - -Whether or not your company chooses to work with {% data variables.product.prodname_professional_services %}, we always recommend you hold your own kickoff meeting to align your own team(s). - -During this kickoff meeting, it's important to ensure there is a clear understanding of goals, expectations, and that a plan is in place for how to move forward with your rollout and implementation. - -In addition, this is a good time to begin thinking about training and preparations for your team to ensure they have the right tools and expertise to support the rollout and implementation of GHAS. - -#### Topics for your internal kickoff meeting - -We recommend you cover these topics in your internal kickoff meeting at your company if you haven't already covered these with the same group in your kickoff meeting with {% data variables.product.prodname_professional_services %}. - -- What are your business success metrics, how do you plan to measure and report on those measures? - - If these have not been defined, please define them. If they have been defined, communicate them and talk about how you plan to provide data-driven progress updates. -- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is expected to work for your company. -- Review of best practices if your company did not participate in the Proof of Concept exercise (or a refresher if your team finds value in this review) - - How does this compare/contrast with your existing Application Security Program? -- Discuss and agree how your internal team will work best together throughout rollout and implementation. - - Align on your communications plans and frequency of meetings for your internal team - - Review tasks for rollout and implementation completion, defining roles and responsibilities. We have outlined the majority of the tasks in this article, but there may be additional tasks your company requires we have not included. - - Consider establishing a “Champions Program” for scaled enablement - - Begin discussing timing for the completion of tasks -- Begin working on ideal rollout approaches that will work best for your company. This will include understanding a few important items: - - How many teams will be enabled? Some of this might have already been covered during the POC (Proof of Concept) exercise if your company participated. If not, this is a crucial time to discuss this. - - Of the critical applications identified for the initial rollout, how many are built on a technology supported by GHAS? - - How much organizational preparation is needed? To learn more, see "[Phase 2](#--phase-2-organizational-buy-in--rollout-preparation)." - -### Step 3: Prepare your rollout & implementation plan and goals - -Before you can move forward with pilot project(s) for the first phase of the rollout, it’s crucial to ensure a rollout plan and business goals have been established for how your company plans to proceed. - -If you’re working with {% data variables.product.prodname_professional_services %}, they can play a significant role in the creation of this plan. - -If you’re working independently, this section outlines some things to ensure are included in your plan as you prepare to move forward. - -Plans for process changes (if needed) and training for team members as needed: - - Documented team assignments for roles and responsibilities. For more information on the permissions required for each feature, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." - - Documented plan of tasks and timelines/timeframes where possible. This should include infrastructure changes, process changes/training, and all subsequent phases of enablement of GHAS, allowing for timeframes for remediations and configuration adjustments as needed. For more information, see "[Phase 1: Pilot projects(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" below. - - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent plans for which projects/teams will come in following phases - - Success metrics based on business goals. This will be a crucial reference point following the Pilot Project(s) to gain buy-in for the full rollout. - -{% note %} - -**Note:** To ensure awareness, buy-in, and adoption comes from all groups in your company, it's important to set realistic expectations around the rollout timing and impact on your company's infrastructure, processes, and general day-to-day development workflows. For a smoother and more successful rollout, ensure your security and development teams understand the impact of GHAS. - -{% endnote %} - -{% ifversion ghes %} - -For {% data variables.product.prodname_ghe_server %} customers, to help ensure your instance can support the rollout and implementation of GHAS, review the following: - -- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)」を参照してください。 - -- High Availability 設定では、完全に冗長なセカンダリの {% data variables.product.prodname_ghe_server %} アプライアンスは、すべての主要なデータストアのレプリケーションによってプライマリアプライアンスとの同期を保ちます。 For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)." - -- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. 詳しい情報については「[システムの概要](/admin/overview/system-overview)」を参照してください。 - -{% endif %} - -### Step 4: Establish a baseline of organizational insights - -As your company prepares to begin your pilot project(s), it’s crucial to ensure that you have set a baseline for where your enterprise is today and have defined clear success metrics to measure your pilot project(s) progress against. - -There are likely key business goals your company has that will need to be measured against, but there are other metrics we can identify to help gauge your pilot’s success. - -As a starting point, some of these metrics might include: - - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and practices the pilot project(s) / team(s) utilized. - - The code scanning integration's findings for the top X most critical applications. - - The number of applications that have SAST (Static application security testing) integrated versus before the engagement. - -If you participated in the POC exercise prior to purchasing GHAS, these objectives might look familiar. This success criteria includes several objectives for the following high-level roles: - - Implementation & Administration teams - - Security / CISO (Chief Information Security Officer) - - Application Development Teams - -If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main evaluation criteria in DSOMM: - -- **Static depth:** How comprehensive is the static code scan that you’re performing within the AppSec CI pipeline -- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the AppSec CI pipeline -- **Intensity:** Your schedule frequency for the security scans running in AppSec CI pipeline -- **Consolidation:** Your remediation workflow for handling findings and process completeness - -To learn more about this approach and how to implement it in GHAS, you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)." - -Based on your wider company’s goals and current levels of DevSecOps maturity, we can help you determine how to best measure your pilot’s progress and success. - -## {% octicon "milestone" aria-label="The milestone icon" %} Phase 1: Pilot project(s) - -{% note %} - -{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 1 may last roughly between 2 weeks to 3+ months. This range can vary largely depending on your company’s infrastructure or systems complexity, internal processes to manage/approve these changes, as well as if larger organizational process changes are needed to move forward with GHAS. - -{% endnote %} - -To begin enabling GHAS across your company, we recommend beginning with a few high-impact projects or teams to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company. - -Before you start your pilot project(s), we recommend that you schedule some checkpoint meetings for your team(s), such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These checkpoint meetings will help you all make adjustments as needed and ensure your team(s) are prepared and supported to complete the pilot successfully. - -These steps will help you enable GHAS on your enterprise, begin using its features, and review your results. - -If you’re working with {% data variables.product.prodname_professional_services %}, they can provide additional assistance through this process through onboarding sessions, GHAS workshops, and troubleshooting as needed. - -### Step 1: GHAS set-up & installation - -{% ifversion ghes %} - -If you haven't already enabled GHAS for your {% data variables.product.prodname_ghe_server %} instance, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." - -{% endif %} - -You need to enable GHAS for each pilot project, either by enabling the GHAS feature for each repository or for all repositories in any organizations taking part in the project. 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)" - -The vast majority of GHAS set-up and installation is centered around enabling and configuring code scanning on your enterprise and in your repositories. - -Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. 詳しい情報については、「[コードスキャニングについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)」を参照してください。 - -### Step 2: Set up {% data variables.product.prodname_code_scanning_capc %} - -{% ifversion ghes %} - -To enable {% data variables.product.prodname_code_scanning %} on your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." - -{% endif %} - -To set up code scanning, you must decide whether you'll run code scanning with [{% data variables.product.prodname_actions %}](#using-github-actions-for-code-scanning) or your own [third-party CI system](#using-a-third-party-ci-system-with-the-codeql-cli-for-code-scanning). - -#### Using {% data variables.product.prodname_actions %} for {% data variables.product.prodname_code_scanning %} - -{% ifversion ghes %} - -To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)." - -{% endif %} - -For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners)」を参照してください。 - -For more information about {% data variables.product.prodname_actions %}, see: - - "[Learn GitHub Actions](/actions/learn-github-actions)" - - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)" - - [ワークフローをトリガーするイベント](/actions/learn-github-actions/events-that-trigger-workflows) - - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)" - -#### Using a third-party CI system with the CodeQL CLI for {% data variables.product.prodname_code_scanning %} - -If you’re not using {% data variables.product.prodname_actions %} and have your own continuous integration system, you can use the CodeQL CLI to perform CodeQL code scanning in a third-party CI system. - -詳しい情報については、以下を参照してください。 - - "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)" - -### Step 3: Enable {% data variables.product.prodname_code_scanning_capc %} in repositories - -If you’re using a phased approach to roll out GHAS, we recommend enabling {% data variables.product.prodname_code_scanning %} on a repository-by-repository basis as part of your rollout plan. For more information, see "[Setting up code scanning for a repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)." - -If you’re not planning on a phased rollout approach and want to enable code scanning for many repositories, you may want to script the process. - -For an example of a script that opens pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. - -### Step 4: Run code scans and review your results - -With code scanning enabled in the necessary repositories, you're ready to help your development team(s) understand how to run code scans and reports, view reports, and process results. - -#### {% data variables.product.prodname_code_scanning_capc %} - -With code scanning, you can find vulnerabilities and errors in your project's code on GitHub, as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts. - -When code scanning identifies a problem in a pull request, you can review the highlighted code and resolve the alert. 詳しい情報については、「[プルリクエストで {% data variables.product.prodname_code_scanning %} アラートをトリガーする](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。 - -If you have write permission to a repository you can manage code scanning alerts for that repository. With write permission to a repository, {% ifversion delete-code-scanning-alerts %}you can view, fix, dismiss, or delete alerts {% else %}you can view, fix, or dismiss alerts{% endif %} for potential vulnerabilities or errors in your repository's code. 詳しい情報については、「[リポジトリの Code scanningアラートを管理する](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)」を参照してください。 - -#### Generate reports of {% data variables.product.prodname_code_scanning %} alerts - -If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. 詳しい情報については、「[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)」を参照してください。 - -For an example of how to use the {% data variables.product.prodname_code_scanning_capc %} API, see the [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample) repository. - -### Step 5: Configure {% data variables.product.prodname_code_scanning_capc %} to fine tune your results - -When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans. - -詳しい情報については、「[コードスキャンを設定する](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)」を参照してください。 - -If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)." - -### Step 6: Set up secret scanning - -GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally. - -{% ifversion ghes %} - -To enable secret scanning for your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring secret scanning for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance)." - -{% endif %} - -You need to enable secret scanning for each pilot project, either by enabling the feature for each repository or for all repositories in any organizations taking part in the project. 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)" - -To learn how to view and close alerts for secrets checked into your repository, see "[Managing alerts from secret scanning](/code-security/secret-scanning/managing-alerts-from-secret-scanning)." - -### Step 7: Set up dependency management - -GitHub helps you avoid using third-party software that contains known vulnerabilities. We provide the following tools for updating vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and removing malware{% endif %}. - -| Dependency Management Tool | 説明 | -| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects insecure dependencies. 詳しい情報については、「[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)」を参照してください。 | -| 依存関係グラフ | 依存関係グラフは、リポジトリに保存されているマニフェストファイルおよびロックファイルのサマリーです。 コードベースが依存するエコシステムとパッケージ（依存関係）、およびプロジェクトに依存するリポジトリとパッケージ（依存関係）が表示されます。 詳しい情報については、「[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)」を参照してください。 |{% ifversion ghes or ghec %} -| 依存関係のレビュー | プルリクエストに依存関係への変更が含まれている場合は、変更内容の概要と、依存関係に既知の脆弱性があるかどうかを確認できます。 For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." |{% endif %} {% ifversion ghec or ghes > 3.2 %} -| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." | -| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. 詳しい情報については、「[ Dependabot のバージョン更新について](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)」を参照してください。 | {% endif %} - -{% data reusables.dependabot.beta-security-and-version-updates-onboarding %} - -### Step 8: Establish a remediation process - -Once your team(s) have been able to run scans, identify vulnerabilities and dependencies, and can consume the results of each security feature, the next step is to ensure that they can remediate the vulnerabilities identified within their normal development processes without involving your security team. - -This means that the development teams understand how to utilize the GHAS features throughout the development process, can run scans, read reports, consume the results, and remediate vulnerabilities within their normal development workflows, without having to have a separate security phase at the end of development, or have a need to involve your security team to understand reports/results. - -### Step 9: Set up custom analysis if needed - -Custom analysis is an optional deeper use of code scanning when custom CodeQL queries are needed beyond the available default (and community) set of queries. The need for custom queries is rare. - -Custom queries are used to identify custom security alerts or help developers follow coding standards by detecting certain code patterns. - -If your company is interested in writing custom CodeQL queries, there are certain requirements your company should meet. - -If your team can provide some examples of existing vulnerabilities you'd like to find via CodeQL, please let the GitHub team know and we can schedule an introductory session to review the basics of the language and discuss how to tackle one of your problems. If you want to cover CodeQL in more depth, then we offer additional engagement options to cover more topics to enable your team to build their own queries. - -You can learn more about [CodeQL queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in our [CodeQL documentation](https://codeql.github.com/docs/codeql-overview/), or reach out to your {% data variables.product.prodname_professional_services %} team or sales representative. - -### Step 10: Create & maintain documentation - -All throughout the pilot phase, it’s essential to create and maintain high-quality internal documentation of the infrastructure and process changes made within your company, as well as learnings from the pilot process and configuration changes made as your team(s) progress throughout the rollout and implementation process. - -Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process. Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s). - -Good documentation doesn’t end when rollout and implementation are complete. The most helpful documentation is actively updated and evolves as your teams expand their experience using GHAS and as their needs grow. - -In addition to your documentation, we recommend your company provides clear channels to your team(s) for support and guidance all throughout rollout, implementation, and beyond. Depending on the level of change your company needs to take on in order to support the rollout and implementation of GHAS, having well-supported teams will help ensure a successful adoption into your development teams’ daily workflow. - -## {% octicon "milestone" aria-label="The milestone icon" %} Phase 2: Organizational buy-in & rollout preparation - -{% note %} - -{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 2 may last roughly between 1 week to over a month. This range can vary largely depending on your company’s internal approval processes. - -{% endnote %} - -One of the main goals of this phase is to ensure you have the organizational buy-in to make the full deployment of GHAS successful. - -During this phase, your company reviews the results of the pilot project(s) to determine if the pilot was successful, what adjustments may need to be made, and if the company is ready to continue forward with the rollout. - -Depending on your company’s approval process, organizational buy-in from your executive sponsor may be necessary to continue forward. In most cases, organizational buy-in from your team(s) is necessary to begin utilizing the value of GHAS for your company. - -Before moving forward to the next phase of rolling out GHAS more widely across your company, modifications are often made to the original rollout plan based on learnings from the pilot. - -Any changes that may impact the documentation should also be made to ensure it is current for continued rollout. - -We also recommend that you consider your plan to train any teams or team members that will be introduced to GHAS in the next phases of your rollout if you haven't already. - -### Step 1: Organize results - -At the completion of Phase 1, your team(s) should have {% ifversion ghes %} GHAS enabled on your {% data variables.product.prodname_ghe_server %} instance and have{% endif %} been able to utilize all of the key features of GHAS successfully, potentially with some configuration changes to optimize results. If your company clearly defined success metrics in Phase 0, you should be able to measure against these metrics to determine the success of your pilot. - -It’s important to revisit your baseline metrics when preparing your results to ensure that incremental progress can be demonstrated based on metrics collected from the pilot against your original business goals. If you need assistance with this information, GitHub can help by ensuring that your company has the right metrics to measure your progress against. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." - -### Step 2: Secure organizational buy-in - -Organizational buy-in will vary depending on a variety of factors, including your company’s size, approval process, or even the level of change required to rollout GHAS to name a few. - -For some companies, securing buy-in is a one-time meeting, but for others, this process can take quite some time (potentially weeks or months). Buy-in may require approval from your executive sponsor or may require the adoption of GHAS into your teams’ daily workflows. - -This duration of this stage is entirely up to your company and how quickly you would like to proceed. We recommend seeking support or services from GitHub where possible to help answer questions and provide any recommendations that may be needed to help support this process. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." - -### Step 3: Revise and update documentation - -Review the results and findings from your pilot project(s) and the needs of the remaining teams at your company. Based on your findings and needs analysis, update/revise your documentation. - -We've found that it’s essential to ensure that your documentation is up-to-date before continuing with the rollout to the remainder of your company's enterprise. - -### Step 4: Prepare a full rollout plan for your company - -Based on what you learned from your pilot project(s), update the rollout plan you designed in stage 0. To prepare for rolling out to your company, consider any training your teams will need, such as training on using GHAS, process changes, or migration training if your enterprise is migrating to GitHub. - -## {% octicon "milestone" aria-label="The milestone icon" %} Phase 3: Full organizational rollout & change management - -{% note %} - -{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 3 may -last anywhere from 2 weeks to multiple months. This range can vary largely depending on your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc. - -{% endnote %} - -Once your company has aligned on the results and findings from your pilot project(s) and all rollout preparation steps have been completed from Phase 2, you can move forward with the full rollout to your company based on your plan. - -### Step 1: Evaluate your rollout as you go - -If you're using a phased approach to rolling out GHAS, we recommend taking a brief pause and completing a short evaluation after rolling out GHAS to a different segment of your company to ensure the rollout is moving forward smoothly. Your evaluation can ensure that teams are enabled and trained properly, that any unique GHAS configuration needs are met, and that plans and documentation can be adjusted as needed. - -### Step 2: Set up any needed training - -When rolling GHAS out to any teams beyond your pilot project team(s), it’s important to ensure teams are either trained or there are training resources available to provide additional support where needed. - -These are the main areas where we see companies needing further support: - - training on GHAS - - training for customers new to GitHub - - training on how to migrate to GitHub - -Our {% data variables.product.prodname_professional_services_team %} team provides a variety of training services, bootcamps, and just general advice to help support your team(s) throughout the rollout and implementation process. For more information, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)." - -To help support your teams, here's a recap of relevant GitHub documentation. - -For documentation on how to enable GHAS, see: - - "[Enabling Advanced Security features](/get-started/learning-about-github/about-github-advanced-security)" - - 「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」 - - 「[リポジトリのセキュリティおよび分析設定を管理する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)」 - -For documentation on how to migrate to GitHub, see: - - 「[GitHub にソースコードをインポートする](/github/importing-your-projects-to-github/importing-source-code-to-github)」 - -For documentation on getting started with GitHub, see: - - "[Get started](/get-started)" - -### Step 3: Help your company manage change - -In step 4 of phase 2, we recommended that you update the initial rollout plan based on your learnings from the pilot project(s). Ensure that you continue to update your plan as you implement any necessary organizational changes to successfully roll out GHAS to your company. - -Successful GHAS rollouts and the adoption of best practices into daily workflows depend on ensuring that your teams understand why it’s necessary to include security in their work. - -### Step 4: Continued customization - -Configuration and customization of GHAS are not complete once it’s rolled out across your company's enterprise. Further custom configuration changes should continue to be made over time to ensure GHAS continues to support your company's changing needs. - -As your team becomes more experienced and skilled with GHAS over time, this will create additional opportunities for further customization. diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md index 3d31ba6e8b..da4e62035c 100644 --- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md @@ -27,7 +27,7 @@ When you enable {% data variables.product.prodname_GH_advanced_security %} for y {% endif %} {% ifversion ghes %} -For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying GitHub Advanced Security in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." +For guidance on a phased deployment of GitHub Advanced Security, see "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)." {% endif %} ## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md index a504b86b4f..f3ee256100 100644 --- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md @@ -9,14 +9,11 @@ redirect_from: - /admin/advanced-security versions: ghes: '*' - ghec: '*' topics: - Enterprise children: - /enabling-github-advanced-security-for-your-enterprise - /configuring-code-scanning-for-your-appliance - /configuring-secret-scanning-for-your-appliance - - /overview-of-github-advanced-security-deployment - - /deploying-github-advanced-security-in-your-enterprise --- diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md deleted file mode 100644 index 5adfe6c124..0000000000 --- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md +++ /dev/null @@ -1,267 +0,0 @@ ---- -title: Overview of GitHub Advanced Security deployment -intro: 'Help your company successfully prepare to adopt {% data variables.product.prodname_GH_advanced_security %} (GHAS) by reviewing and understanding these best practices, rollout examples, and our enterprise-tested phased approach.' -product: '{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features, included in {% data variables.product.prodname_GH_advanced_security %}, see "[About GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."' -redirect_from: - - /admin/advanced-security/overview-of-github-advanced-security-deployment -miniTocMaxHeadingLevel: 3 -versions: - ghes: '*' - ghec: '*' -type: how_to -topics: - - Advanced Security - - Code scanning - - Enterprise - - Security ---- - -{% data variables.product.prodname_GH_advanced_security %} (GHAS) helps teams build more secure code faster using integrated tooling such as CodeQL, the world’s most advanced semantic code analysis engine. GHAS is a suite of tools that requires active participation from developers across your enterprise. To realize the best return on your investment, you must learn how to use, apply, and maintain GHAS to truly protect your code. - -One of the biggest challenges in tackling new software for an company can be the rollout and implementation process, as well as bringing about the cultural change to drive the organizational buy-in needed to make the rollout successful. - -To help your company better understand and prepare for this process with GHAS, this overview is aimed at: - - Giving you an overview of what a GHAS rollout might look like for your company. - - Helping you prepare your company for a rollout. - - Sharing key best practices to help increase your company’s rollout success. - -To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." - -## Recommended phased approach for GHAS rollouts - -We’ve created a phased approach to GHAS rollouts developed from industry and GitHub best practices. You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently. - -While the phased approach is recommended, adjustments can be made based on the needs of your company. We also suggest creating and adhering to a timeline for your rollout and implementation. As you begin your planning, we can work together to identify the ideal approach and timeline that works best for your company. - -![Diagram showing the three phases of GitHub Advanced Security rollout and deployment, including Phase 0: Planning & Kickoff, Phase 1: Pilot projects, Phase 2: Org Buy-in and Rollout for early adopters, and Phase 3: Full org rollout & change management](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png) - - -Based on our experience helping customers with a successful deployment of {% data variables.product.prodname_GH_advanced_security %}, we expect most customers will want to follow these phases. Depending on the needs of your company, you may need to modify this approach and alter or remove some phases or steps. - -For a detailed guide on implementing each of these phases, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." The next section gives you a high-level summary of each of these phases. - -### {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff - -During this phase, the overall goal is to plan and prepare for your rollout, ensuring that you have your people, processes, and technologies in place and ready for your rollout. You should also consider what success criteria will be used to measure GHAS adoption and usage across your teams. - -### {% octicon "milestone" aria-label="The milestone icon" %} Phase 1: Pilot project(s) - -To begin implementing GHAS, we recommend beginning with a few high-impact projects/teams with which to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS, learn how to enable and configure GHAS, and build a solid foundation on GHAS before rolling out to the remainder of your company. - -### {% octicon "milestone" aria-label="The milestone icon" %} Phase 2: Organizational buy-in & rollout preparation - -Phase 2 is a recap of previous phases and preparing for a larger rollout across the remainder of the company. In this phase, organizational buy-in can refer to your company’s decision to move forward after the pilot project(s) or the company’s use and adoption of GHAS over time (this is most common). If your company decides to adopt GHAS over time, then phase 2 can continue into phase 3 and beyond. - -### {% octicon "milestone" aria-label="The milestone icon" %} Phase 3: Full organizational rollout & change management - -Once your company is in alignment, you can begin rolling GHAS out to the remainder of the company based on your rollout plan. During this phase, it’s crucial to ensure that a plan has been made for any organizational changes that may need to be made during your rollout of GHAS and ensuring teams understand the need, value, and impact of the change on current workflows. - -## Best practices for a successful GHAS rollout - -We’ve found that companies that have completed successful GHAS rollouts have several similar characteristics that help drive their success. To help your company increase the success of your GHAS rollout, review these best practices. - -### {% octicon "checklist" aria-label="The checklist icon" %} Set clear goals for your company’s rollout - -Setting goals may seem obvious, but we do see some companies that begin GHAS rollouts with no clear goals in mind. It’s more difficult for these companies to gain the true organizational buy-in that’s needed to complete the rollout process and realize the value of GHAS within their company. - -As you begin planning for your rollout and implementation, begin outlining goals for GHAS within your company and ensure these are communicated to your team. Your goals can be highly detailed or something simple, as long as there is a starting point and alignment. This will help build a foundation for the direction of your company’s rollout and can help you build a plan to get there. If you need assistance with your goals, {% data variables.product.prodname_professional_services %} can help with recommendations based on our experience with your company and prior engagements with other customers. - -Here are some high-level examples of what your goals for rolling out GHAS might look like: - - **Reducing the number of vulnerabilities:** This may be in general, or because your company was recently impacted by a significant vulnerability that you believe could have been prevented by a tool like GHAS. - - **Identifying high-risk repositories:** Some companies may simply want to target repositories that contain the most risk, ready to begin remediating vulnerabilities and reducing risk. - - **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing the accumulation of security debt. - - **Meeting compliance requirements:** This can be as simple as creating new compliance requirements or something more specific. We find many healthcare companies use GHAS to prevent the exposure of PHI (Personal Health Information). - - **Preventing secrets leakage:** This is often a goal of companies that have had (or want to prevent) critical information leaked such as software keys, customer or financial data, etc. - - **Dependency management:** This is often a goal for companies that may have fallen victim due to hacks from unpatched dependencies, or those seeking to prevent these types of attacks by updating vulnerable dependencies. - -### {% octicon "checklist" aria-label="The checklist icon" %} Establish clear communication and alignment between your teams - -Clear communication and alignment are critical to the success of any project, and the rollout of GHAS is no different. We’ve found that companies that have clear communication and alignment between their security and development groups, as well as their executive sponsor (either CISO or VP) from the purchase of GHAS through rollout, often have more success with their rollouts. - -In addition to ensuring these groups are aligned throughout your GHAS rollout, there are a few specific areas we recommend focusing on. - -#### Rollout planning - -How will you roll out GHAS to your company? There will likely be many ideas and opinions. Here are some questions you should consider answering and aligning on before moving forward: - - What teams will be included in the pilot? - - What projects are focused on in the pilot? - - How should projects be prioritized for rollout? - - How do you plan to measure success in the pilot and beyond? - - What is the level of daily change your teams will be taking on? How will that be communicated? - - How will your rollout plans be communicated across the company? - - How do you plan to train your teams? - - How do you plan to manage scan results initially? (For more information, see the next section on "Processing results") - -#### Processing results - -Before GHAS is rolled out to your teams, there should be clear alignment on how results should be managed over time. We recommend initially looking at results as more informative and non-blocking. It’s likely your company has a full CI/CD pipeline, so we recommend this approach to avoid blocking your company’s process. As you get used to processing these results, then you can incrementally increase the level of restriction to a point that feels more accurate for your company. - -### {% octicon "checklist" aria-label="The checklist icon" %} Lead your rollout with both your security and development groups - -Many companies lead their GHAS rollout efforts with their security group. Often, development teams aren’t included in the rollout process until the pilot has concluded. However, we’ve found that companies that lead their rollouts with both their security and development teams tend to have more success with their GHAS rollout. - -なぜ？ GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in. - -When development groups are involved earlier (ideally from purchase), security and development groups can achieve alignment early in the process. This helps to remove silos between the two groups, builds and strengthens their working relationships, and helps shift the groups away from a common mentality of “throwing things over the wall.” All of these things help support the overall goal to help companies shift and begin utilizing GHAS to address security concerns earlier in the development process. - -#### {% octicon "people" aria-label="The people icon" %} Recommended key roles for your rollout team - -We recommend a few key roles to have on your team to ensure that your groups are well represented throughout the planning and execution of your rollout and implementation. - -We highly recommend your rollout team include these roles: -- **Executive Sponsor:** This is often the CISO, CIO, VP of Security, or VP of Engineering. -- **Technical Security Lead:** The technical security lead provides technical support on behalf of the security team throughout the implementation process. -- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team. - -We also recommend your rollout team include these roles: -- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success. -- **Quality Assurance Engineer:** Including a member of your company’s Quality Assurance team helps ensure process changes are taken into account for the QA team. - -### {% octicon "checklist" aria-label="The checklist icon" %} Understand key GHAS facts to prevent common misconceptions - -Going into a GHAS implementation, it’s important to understand some key basic facts about what GHAS is and can do, to prevent many common misconceptions companies have going into their GHAS rollouts. - -{% note %} - -**Note:** If you’re interested in furthering your GHAS education, {% data variables.product.prodname_professional_services %} provides a variety of options for additional education and training, including topics that your company needs to prepare for GHAS. These offerings may take the form of workshops, demonstrations, and bootcamps. Topics can range from deploying GHAS and basic usage of GHAS to more advanced topics to continue to build your team’s skills. For more information on working with the {% data variables.product.prodname_professional_services_team %} team, see "[{% data variables.product.prodname_professional_services %}](#github-professional-services)." - -{% endnote %} - - -#### Fact 1: GHAS is a suite of security tools that require action to protect your code. - -It’s not security software that is installed and forgotten—just having GHAS on its own does not protect your code. GHAS is a suite of tools that increases with value when configured, maintained, used in daily workflows, and in combination with other tools. - -#### Fact 2: GHAS will require adjustment out of the box. - -Once GHAS is set up on your repositories, there are additional steps that need to be taken to ensure it works for your company’s needs. Code scanning in particular requires further configuration to fine-tune your results, for example, customizing what is flagged by the scans to adjust what is picked up in future scans. Many customers find that initial scans either pick up no results or results that are not relevant based on the application's threat model and need to be adjusted to their company’s needs. - -#### Fact 3: GHAS tools are most effective when used together, but the most effective AppSec programs involve the use of additional tools/activities. - -GHAS is most effective when all of the tools are used together. When companies integrate GHAS with other tools and activities, such as penetration testing and dynamic scans, it further improves the effectiveness of the AppSec program. We recommend always utilizing multiple layers of protection. - -#### Fact 4: Not all companies will use/need custom {% data variables.product.prodname_codeql %} queries, but they can help you customize/target scan results. - -Code scanning is powered by {% data variables.product.prodname_codeql %}—the world’s most powerful code analysis engine. While many companies are excited at the prospect of being able to write custom queries, for a large portion of our customers the base query set and additional queries available in the community are typically more than sufficient. However, many companies may find the need for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new queries to target results your company may need. - -However, if your company is interested in writing custom {% data variables.product.prodname_codeql %} queries, we recommend you complete your rollout and implementation of GHAS before exploring custom queries. - -{% note %} - -**Note:** It’s crucial for your company to have a solid foundation on GHAS before diving deeper into deeper security practices. - -{% endnote %} - -When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use cases for custom queries. - -#### Fact 5: {% data variables.product.prodname_codeql %} scans the whole code base, not just the changes made in a pull request. - -When code scanning is run from a pull request, the scan will include the full codebase and not just the changes made in the pull request. While this may seem unnecessary at times, this is an important step to ensure the change has been reviewed all against all interactions in the codebase. - -## Examples of successful {% data variables.product.prodname_GH_advanced_security %} rollouts - -Now that you have a better understanding of some of the keys to a successful GHAS rollout and implementation, here are some examples of how our customers made their rollouts successful. Even if your company is in a different place, {% data variables.product.prodname_dotcom %} can help you with building a customized path that suits the needs of your rollout. - -### Example rollout for a mid-sized healthcare technology company - -A mid-sized healthcare technology company based out of San Francisco completed a successful GHAS rollout process. While they may not have had a large number of repositories that needed to be enabled, this company’s keys to success included having a well-organized and aligned team for the rollout, with a clearly established key contact to work with {% data variables.product.prodname_dotcom %} to troubleshoot any issues during the process. This allowed them to complete their rollout within two months. - -In addition, having an engaged development team allowed the company to have teams using code scanning at the pull request level following the completion of their rollout. - -### Example rollout for a mid-sized data platform company - -A global data platform company has had great success with GHAS to date. They’ve completed their initial implementation and are currently progressing through the rollout process. This company is mature in their security posture and tooling, and are well-aligned as an company. This allows them to operate very self-sufficiently and has enabled them to move quickly and smoothly through their rollout. - -This company's strong alignment, efficient operations, and security tooling maturity allowed them to implement GHAS quickly and build a good foundation for {% data variables.product.prodname_codeql %}. Since their implementation, they can now automatically enable {% data variables.product.prodname_codeql %} across different repositories. - -In addition to their security and technical maturity, another critical key to this company’s success is having a project owner and single point of contact from their team to drive the project forward. Not only is having this key contact crucial, but they are incredibly resourceful and skilled, and directly contribute to the success of the rollout. - -## Prerequisites for your company before rolling out GHAS - -{% data variables.product.prodname_professional_services %} can help to provide additional support to help your company break down and understand these prerequisites and help you get prepared for the GHAS implementation process. - - ### CI/CD systems and process - -If your company has not yet invested in or implemented continuous integration or continuous delivery (CI/CD) systems and processes, we recommend taking this step in conjunction with moving forward with GHAS. This may be a significant shift for your company—we can work with you to provide recommendations and guidance for implementing a CI/CD system, as well as supporting any training that might be needed. - -### Requirements to install {% data variables.product.prodname_GH_advanced_security %} - -There are a few different paths that can be taken for your GHAS installation based on what combinations of technologies your company uses. This section outlines a quick breakdown of the different paths your company may need to take. - -{% ifversion ghes %} - -#### {% data variables.product.prodname_ghe_server %} - -It’s important that you’re utilizing a version of {% data variables.product.prodname_ghe_server %} (GHES) that will support your company’s needs. - -If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. 詳しい情報については、以下を参照してください。 - - "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)" - - "[Upgrade requirements](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)" - -If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." - -If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting. - -{% endif %} - -{% ifversion ghec %} - -#### {% data variables.product.prodname_ghe_cloud %} - -If you’re a {% data variables.product.prodname_ghe_cloud %} (GHEC) customer there are prerequisites that you’ll need to meet depending on what CI/CD you plan to utilize. - -Using {% data variables.product.prodname_actions %} for your CI/CD: -- To ensure {% data variables.product.prodname_code_scanning %} can be integrated and utilized properly, you should have a basic understanding of {% data variables.product.prodname_actions %} before proceeding with your installation. - -Using a third-party tool for CI/CD: -- To integrate the {% data variables.product.prodname_codeql_cli %}, you should have a basic understanding of the CI/CD system, as well as *nix and Windows—in particular how commands are executed and how success/failure is signaled. For more information about how to integrate a third-party tool, see "[Using CodeQL code scanning with your existing CI system ](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)." - -{% endif %} - -## Partnering with GitHub for your rollout - -As you prepare for your GHAS implementation, it’s important to consider what will be required from your company to make this project successful. Our most successful implementations of GHAS rely on shared responsibilities between both GitHub and our customers throughout the process with a clearly identified stakeholder from the customer owning the project. - -#### Success model for customer and GitHub responsibilities - -**Customer responsibilities** -- Completing infrastructure and process prerequisites -- Managing rollout and implementation, including planning and execution -- Internal training -- (Optional) Contributing {% data variables.product.prodname_codeql %} queries to the GitHub Community - -**GitHub responsibilities** - -- Maintenance and enhancements for features, such as {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %} -- Providing, maintaining, and delivering the following services: {% data variables.product.prodname_dotcom %} Docs, {% data variables.product.prodname_dotcom %} Community, {% data variables.product.prodname_dotcom %} Support - -{% note %} - -**Note:** {% data variables.product.prodname_professional_services %} can help support many of the customer responsibilities. To learn more, see "[GitHub services and support](#github-services-and-support)." - -{% endnote %} - -## {% data variables.product.prodname_dotcom %} services and support - -### {% data variables.product.prodname_dotcom %} Support - -If you run into any issues during your implementation, you can search our deep documentation for solutions or engage with {% data variables.product.prodname_dotcom %} Support, a team of highly technical engineers that can support you as issues arise. For more information, see "[GitHub Enterprise Support](https://enterprise.github.com/support). - -In addition, you can also try our [ {% data variables.product.prodname_gcf %}](https://github.community/). - -If you purchased a Premium Support plan, you can submit your ticket in the [Premium Support Portal](https://enterprise.github.com/support). If you’re unsure of which Support plan you purchased, you can reach out to your sales representative or review the plan options. - -For more information the Premium support plan options, see: - - "[Premium Support](https://github.com/premium-support)" {% ifversion ghec %} - - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %} - - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %} - -### {% data variables.product.prodname_professional_services %} - -Our {% data variables.product.prodname_professional_services_team %} team can partner with you for a successful rollout and implementation of {% data variables.product.prodname_GH_advanced_security %}. We offer a variety of options for the type of guidance and support you expect to need for your implementation. We also have training and bootcamps available to help your company to optimize the value of GHAS. - -If you’d like to work with our {% data variables.product.prodname_professional_services_team %} team for your implementation, we recommend you begin thinking about your system design and infrastructure, as well as the number of repositories that you want to set up with GHAS, to begin these conversations. In addition, begin thinking about goals for what you would like to achieve with this rollout. - -Implementation is just one step in a successful security-driven journey where you’ll learn how to use GHAS. Once you’ve completed your implementation, there will be more to learn with the rollout throughout your infrastructure and codebases. Speak with your sales representative for more information about all the {% data variables.product.prodname_professional_services_team %} options available. - -If you initially opted out of additional services, but find that additional support is needed as you begin your implementation, please reach out to your sales representative to discuss what services options may be needed to support your implementation. diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index 6c9b078f10..17e6e46471 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -92,3 +92,9 @@ If {% data variables.product.product_location %} indicates that your session has - Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.product.product_location %} ](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)." For more information, refer to the documentation for your load balancer. + +### Live updates to issues and check runs not working + +When {% data variables.product.product_location %} is accessed via a load balancer or reverse proxy, expected live updates, such as new comments on issues and changes in notification badges or check run output, may not display until the page is refreshed. This is most common when the reverse proxy or load balancer is running in a layer 7 mode or does not support the required [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) protocol. + +To enable live updates, you may need to reconfigure the load balancer or proxy. For more information, refer to the documentation for your load balancer. 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 fae514bdff..69bbbb2d6d 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 @@ -165,17 +165,17 @@ The scope of the events that appear in your enterprise's audit log depend on whe {%- ifversion fpt or ghec %} ## `codespaces` カテゴリアクション -| アクション | 説明 | -| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `codespaces.connect` | A codespace was started. | -| `codespaces.create` | A user [created a codespace](/github/developing-online-with-codespaces/creating-a-codespace). | -| `codespaces.destroy` | A user [deleted a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). | -| `codespaces.allow_permissions` | A codespace using custom permissions from its `devcontainer.json` file was launched. | -| `codespaces.attempted_to_create_from_prebuild` | An attempt to create a codespace from a prebuild was made. | -| `codespaces.create_an_org_secret` | A user created an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) | -| `codespaces.update_an_org_secret` | A user updated an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | -| `codespaces.remove_an_org_secret` | A user removed an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | -| `codespaces.manage_access_and_security` | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | +| アクション | 説明 | +| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `codespaces.connect` | A codespace was started. | +| `codespaces.create` | A user [created a codespace](/github/developing-online-with-codespaces/creating-a-codespace). | +| `codespaces.destroy` | A user [deleted a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). | +| `codespaces.allow_permissions` | A codespace using custom permissions from its `devcontainer.json` file was launched. | +| `codespaces.attempted_to_create_from_prebuild` | An attempt to create a codespace from a prebuild was made. | +| `codespaces.create_an_org_secret` | A user created an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) | +| `codespaces.update_an_org_secret` | A user updated an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | +| `codespaces.remove_an_org_secret` | A user removed an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). | +| `codespaces.manage_access_and_security` | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | {%- endif %} {%- ifversion fpt or ghec %} @@ -601,7 +601,7 @@ The scope of the events that appear in your enterprise's audit log depend on whe {%- endif %} | `org.block_user` | An organization owner blocked a user from accessing the organization's repositories. |{% ifversion fpt or ghec %}For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | An invitation for an organization to join an enterprise was revoked. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | An invitation sent to a user to join an organization was revoked. | `org.clear_actions_settings` | An organization owner cleared {% data variables.product.prodname_actions %} policy settings for an organization. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)." | `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." | `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. 詳細は「[Organization のチーム作成権限を設定する](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)」を参照してください。 | `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. |{% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos` | An organization owner cleared a restriction on repository creation in an organization. 詳しい情報については「[Organization でのリポジトリ作成の制限](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)」を参照してください。 | `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. 詳しい情報については「[外部のコラボレータを追加する権限の設定](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)」を参照してください。 | `org.clear_new_repository_default_branch_setting` | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)." {%- ifversion fpt or ghec %} -| `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_codespaces %} was granted trusted repository access to all other repositories in an organization. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_codespaces %} trusted repository access to all other repositories in an organization was revoked. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." +| `org.codespaces_trusted_repo_access_granted` | {% data variables.product.prodname_github_codespaces %} was granted trusted repository access to all other repositories in an organization. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." | `org.codespaces_trusted_repo_access_revoked` | {% data variables.product.prodname_github_codespaces %} trusted repository access to all other repositories in an organization was revoked. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." {%- endif %} | `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | The interaction limit for prior contributors only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | The interaction limit for collaborators only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | The interaction limit for prior contributors only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | An invitation for an organization to join an enterprise was confirmed. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | An organization was created. 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 {%- ifversion fpt or ghec or ghes %} @@ -756,12 +756,12 @@ The scope of the events that appear in your enterprise's audit log depend on whe ## `prebuild_configuration` category actions -| アクション | 説明 | -| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | -| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | -| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | -| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." | +| アクション | 説明 | +| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | +| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | +| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | +| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." | {%- endif %} {%- ifversion ghes %} 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 a620b80ed4..4076923bba 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 @@ -39,7 +39,7 @@ The security log lists all actions performed within the last 90 days. | カテゴリ名 | 説明 | | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} | [`支払い`](#billing-category-actions) | 自分の支払い情報に関連するすべての活動が対象です。 | -| [`codespaces`](#codespaces-category-actions) | {% data variables.product.prodname_codespaces %} に関連するすべての活動が対象です。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。 | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_github_codespaces %}. 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。 | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 | | [`marketplace_listing`](#marketplace_listing-category-actions) | {% data variables.product.prodname_marketplace %} に一覧表示しているアプリに関連するすべての活動が対象です。{% endif %} | [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %} diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index a4abbe3e2b..d3d7ca971f 100644 --- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -57,7 +57,7 @@ Repository administrators can enforce required commit signing on a branch to blo {% ifversion ghes %}If a site administrator has enabled web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.product_name %} will have a verified status. You can verify the signature locally using the public key available at `https://HOSTNAME/web-flow.gpg`. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." {% else %}{% data variables.product.prodname_dotcom %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.prodname_dotcom %} will have a verified status. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. -You can optionally choose to have {% data variables.product.prodname_dotcom %} sign commits you make in {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."{% endif %} +You can optionally choose to have {% data variables.product.prodname_dotcom %} sign commits you make in {% data variables.product.prodname_github_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)."{% endif %} {% endif %} ## GPG commit signature verification diff --git a/translations/ja-JP/content/billing/index.md b/translations/ja-JP/content/billing/index.md index d0a7248b80..655a763943 100644 --- a/translations/ja-JP/content/billing/index.md +++ b/translations/ja-JP/content/billing/index.md @@ -1,7 +1,7 @@ --- title: Billing and payments on GitHub shortTitle: Billing and payments -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}' +intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md similarity index 79% rename from translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md rename to translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md index 681a686e29..c81bc018f2 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md @@ -1,8 +1,8 @@ --- -title: Codespaces の支払いについて +title: GitHub Codespaces の支払いについて shortTitle: 支払いについて -intro: '価格を見て、Organizationでの{% data variables.product.prodname_codespaces %}の支払いの管理方法を確認してください。' -permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' +intro: '価格を見て、Organizationでの{% data variables.product.prodname_github_codespaces %}の支払いの管理方法を確認してください。' +permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.' versions: fpt: '*' ghec: '*' @@ -11,11 +11,13 @@ product: '{% data reusables.gated-features.codespaces %}' topics: - Codespaces - Billing +redirect_from: + - /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces --- -## {% data variables.product.prodname_codespaces %}の価格 +## {% data variables.product.prodname_github_codespaces %}の価格 -{% data variables.product.prodname_codespaces %}の利用状況に対しては、{% data variables.product.prodname_team %}及び{% data variables.product.prodname_enterprise %}上のすべてのOrganization及びEnterpriseアカウントについて課金され、これには無料の分あるいはストレージは含まれません。 現在のところ、個人のアカウントは{% data variables.product.prodname_codespaces %}の利用に対して課金されません。 +{% data variables.product.prodname_github_codespaces %}の利用状況に対しては、{% data variables.product.prodname_team %}及び{% data variables.product.prodname_enterprise %}上のすべてのOrganization及びEnterpriseアカウントについて課金され、これには無料の分あるいはストレージは含まれません。 現在のところ、個人のアカウントは{% data variables.product.prodname_codespaces %}の利用に対して課金されません。 {% data variables.product.prodname_codespaces %}の利用については、以下の表に示す計測単位に従って課金されます。 @@ -32,7 +34,7 @@ topics: {% data reusables.codespaces.codespaces-billing %} -{% data variables.product.prodname_codespaces %} の利用については、アカウントの既存の請求日、支払い方法、領収書が共有されます。 {% data reusables.dotcom_billing.view-all-subscriptions %} +{% data variables.product.prodname_github_codespaces %} の利用については、アカウントの既存の請求日、支払い方法、領収書が共有されます。 {% data reusables.dotcom_billing.view-all-subscriptions %} {% ifversion ghec %} Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_enterprise %} を購入した場合、Azure サブスクリプションID をEnterpriseアカウントに接続して、 {% data variables.product.prodname_codespaces %} の使用を有効にして支払うことができます。 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 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 8fcb5b0d2c..13f8389c0c 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 @@ -7,8 +7,8 @@ versions: ghec: '*' product: '{% data reusables.gated-features.codespaces %}' children: - - /about-billing-for-codespaces - - /viewing-your-codespaces-usage - - /managing-spending-limits-for-codespaces + - /about-billing-for-github-codespaces + - /viewing-your-github-codespaces-usage + - /managing-spending-limits-for-github-codespaces --- diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md similarity index 79% rename from translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md rename to translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md index d69045841c..6eac7dd958 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md @@ -1,6 +1,6 @@ --- -title: Codespacesの利用制限の管理 -intro: '{% data variables.product.prodname_codespaces %} の使用に対して利用上限を設定できます。' +title: GitHub Codespacesの利用制限の管理 +intro: '{% data variables.product.prodname_github_codespaces %} の使用に対して利用上限を設定できます。' versions: fpt: '*' ghec: '*' @@ -14,15 +14,17 @@ topics: - User account - Billing shortTitle: 利用上限 +redirect_from: + - /billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces --- -## {% data variables.product.prodname_codespaces %} の利用上限について +## {% data variables.product.prodname_github_codespaces %} の利用上限について {% data reusables.codespaces.codespaces-spending-limit-requirement %} 使用上限に達すると、Organizationあるいはリポジトリではそれ以上新しいcodespaceを作成できなくなり、既存のcodespaceも起動できなくなります。 まだ実行中の既存のcodespaceはシャットダウンされません。使用上限を変更しなければ、上限を超えた分に対する支払いは生じません。 -{% data variables.product.prodname_codespaces %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)」を参照してください。 +{% data variables.product.prodname_codespaces %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_github_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)」を参照してください。 {% ifversion ghec %} ## Azureサブスクリプションの利用 @@ -58,11 +60,11 @@ Enterprise アカウントの {% data variables.product.prodname_codespaces %} メール通知は、利用量がアカウントの利用上限の50%、75%、90%、100%に達したときに、アカウントのオーナーと支払いマネージャーに送信されます。 -You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. +これらの通知は、**Spending Limit（利用上限）** ページの下部にアクセスしていつでも無効化できます。 ![支払いのメール通知設定のスクリーンショット](/assets/images/help/billing/codespaces-spending-limit-notifications.png) ## 参考リンク - 「[マシンタイプへのアクセスの制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」 -- 「[Organization内のCodespacesの支払いの管理](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)」 +- 「[Organization の {% data variables.product.prodname_github_codespaces %} の支払い管理](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)」 diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md similarity index 57% rename from translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md rename to translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md index 49a5e2fbf2..0546b3ee88 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md @@ -1,8 +1,8 @@ --- -title: Codespacesの使用状況の表示 +title: GitHub Codespacesの使用状況の表示 shortTitle: 使用状況の表示 -intro: '{% data variables.product.prodname_codespaces %}によるコンピュートの分とストレージを見ることができます。' -permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' +intro: '{% data variables.product.prodname_github_codespaces %}によるコンピュートの分とストレージを見ることができます。' +permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -11,11 +11,13 @@ type: overview topics: - Codespaces - Billing +redirect_from: + - /billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage --- -## Organizationの {% data variables.product.prodname_codespaces %} の使用状況を表示する +## Organizationの {% data variables.product.prodname_github_codespaces %} の使用状況を表示する -Organization については、Organization のオーナーと支払いマネージャーが {% data variables.product.prodname_codespaces %} の使用状況を管理できます。 Enterpriseアカウントが管理しているOrganizationでは、OrganizationのオーナーはOrganizationの支払いページで{% data variables.product.prodname_codespaces %}の使用状況を見ることができ、Enterpriseの管理者はEnterprise全体の使用状況を見ることができます。 +Organization については、Organization のオーナーと支払いマネージャーが {% data variables.product.prodname_github_codespaces %} の使用状況を管理できます。 Enterpriseアカウントが管理しているOrganizationでは、OrganizationのオーナーはOrganizationの支払いページで{% data variables.product.prodname_codespaces %}の使用状況を見ることができ、Enterpriseの管理者はEnterprise全体の使用状況を見ることができます。 {% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.codespaces-minutes %} diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md index b64681778f..4507a70f77 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Azure サブスクリプションを Enterprise に接続する -intro: 'Microsoft Enterprise Agreement を使用して、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_codespaces %}の使用を有効化して支払うことができます。' +intro: 'Microsoft Enterprise Agreement を使用して、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_github_codespaces %}の使用を有効化して支払うことができます。' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise @@ -24,7 +24,7 @@ Azure サブスクリプションに接続した後、利用上限を管理す - 「[{% data variables.product.prodname_registry %}の利用上限の管理](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)」 - 「[{% data variables.product.prodname_actions %}の利用上限の管理](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)」 -- 「[{% data variables.product.prodname_codespaces %}の利用上限の管理](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)」 +- 「[{% data variables.product.prodname_github_codespaces %}の利用上限の管理](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)」 ## Azure サブスクリプションを Enterprise アカウントに接続する diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md index 6cf58b740e..3eb2425d3d 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md @@ -23,7 +23,7 @@ shortTitle: インドの1回払い - {% data variables.product.prodname_marketplace %}の購入 - {% data variables.product.prodname_sponsors %}の取引 - Git Large File Storageの購入 -- {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_codespaces %}の消費 +- {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_github_codespaces %}の消費 混乱を最小限に抑えるため、影響を受けたお客様の定期的な取引は、2021 年10月29日に一時停止されました。 RBIの規制によって影響を受けたお客様については、有料の機能やサービスは引き続きご利用いただけます。 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 new file mode 100644 index 0000000000..214b45ace3 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md @@ -0,0 +1,22 @@ +--- +title: GitHub Advanced Securityの大規模な採用 +shortTitle: GHASの大規模な採用 +intro: GitHub Advanced Securityを企業において業界とGitHubのベストプラクティスを利用してロールアウトする、段階的なアプローチ。 +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Secret scanning + - Advanced Security + - Repositories +children: + - /introduction-to-adopting-github-advanced-security-at-scale + - /phase-1-align-on-your-rollout-strategy-and-goals + - /phase-2-preparing-to-enable-at-scale + - /phase-3-pilot-programs + - /phase-4-create-internal-documentation + - /phase-5-rollout-and-scale-code-scanning + - /phase-6-rollout-and-scale-secret-scanning +--- + 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 new file mode 100644 index 0000000000..36ea731188 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md @@ -0,0 +1,54 @@ +--- +title: Introduction to adopting GitHub Advanced Security at scale +intro: 'You can adopt {% data variables.product.prodname_GH_advanced_security %} at scale in your company following industry and GitHub best practices.' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: Introduction +redirect_from: + - /admin/advanced-security/overview-of-github-advanced-security-deployment + - /admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment + - /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 +--- + +## About these articles + +{% data variables.product.prodname_GH_advanced_security %} (GHAS) helps teams build more secure code faster using integrated tooling such as secret scanning and code scanning using CodeQL. To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[About GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)." + +GHAS is a suite of tools that requires active participation from developers across your enterprise. To realize the best return on your investment, you must learn how to use, apply, and maintain GHAS. + + +We’ve created a phased approach to GHAS rollouts developed from industry and GitHub best practices. We expect most customers will want to follow these phases, based on our experience helping customers with a successful deployment of {% data variables.product.prodname_GH_advanced_security %}, but you may need to modify this approach to meet the needs of your company. + +Enabling GHAS across a large organization can be broken down into six core phases. + +1. [**Align on your rollout strategy and goals**](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals): Think about what success will look like, and align on how GHAS will be implemented in your company. This phase may only take a few days or a week, but it lays a solid foundation for the rest of the rollout. + +2. [**Preparing to enable at scale**](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale): Prepare developers, collect data about your repositories, and ensure you're ready for the next phase. + +3. [**Pilot programs**](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs): Optionally, pilot an initial rollout to a few high-impact projects and teams. This will allow an initial group within your company to get familiar with GHAS before you roll out to the remainder of your company. + +4. [**Create internal documentation**](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation): Create and communicate internal documentation for the consumers of GHAS. Without proper documentation provided to developers, security engineers, and others who will be using GHAS, the value will get lost in the rollout. + +5. [**Rollout and scale {% data variables.product.prodname_code_scanning %}**](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning): Leveraging the available APIs, automatically rollout {% data variables.product.prodname_code_scanning %} by team and by language across your enterprise, using the repository data you collected earlier. + +6. [**Rollout and scale {% data variables.product.prodname_secret_scanning %}**](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning): Roll out {% data variables.product.prodname_secret_scanning %}, which involves less configuration and is therefore simpler to adopt than {% data variables.product.prodname_code_scanning %}. Still, it's critical to have a strategy for handling new and old results. + +## {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} + +If you encounter any issues or have any questions during your implementation, you can search our documentation for solutions or engage with {% data variables.contact.github_support %}. For more information, see "[About GitHub Support](/support/learning-about-github-support/about-github-support)." + +If you prefer to have guidance throughout the rollout process, {% data variables.product.prodname_professional_services %} can partner with you for a successful rollout and implementation of {% data variables.product.prodname_GH_advanced_security %}. We offer a variety of options for guidance and support. We also have training and bootcamps available to help your company to optimize the value of {% data variables.product.prodname_GH_advanced_security %}. + +Speak with your sales representative for more information about all the Professional Services options available. For more information, contact {% data variables.contact.contact_enterprise_sales %}. + +{% note %} + +For the first article in this series, see "[Phase 1: Align on your rollout strategy and goals](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals)." + +{% endnote %} \ No newline at end of file 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 new file mode 100644 index 0000000000..78173a007c --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md @@ -0,0 +1,71 @@ +--- +title: 'フェーズ1: ロールアウトの戦略とゴールの調整' +intro: '{% data variables.product.prodname_code_scanning %}と{% data variables.product.prodname_secret_scanning %}を有効化する前に、GHASを企業でどのようにロールアウトするかを計画しましょう。' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 1. 戦略の調整 +miniTocMaxHeadingLevel: 3 +--- + +{% 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)」を参照してください。 + +{% endnote %} + +### 企業におけるロールアウトの明確なゴールの設定 + +企業のロールアウトの方向性の基盤を構築するために、企業内でのGHASのゴールの概要を描き、それらのゴールをチームに伝えてください。 チームと調整できているかぎり、ゴールはシンプルなものでも複雑なものでもかまいません。 ゴールに関して支援が必要な場合には、{% data variables.product.prodname_professional_services %}はあなたやその他の企業との私たちの経験に基づき、推奨事項を提供できます。 + +以下は、GHASのロールアウトのゴールの高レベルの例です。 + + - **脆弱性の数を減らす**: これは一般的なものかもしれません。あるいはあなたの企業が最近大きな脆弱性の影響をうけており、それがGHASのようなツールで回避できたと信じていることによるかもしれません。 + - **高リスクなリポジトリの特定**: 一部の企業は、単純にほとんどのリスクを含むリポジトリをターゲットとして、脆弱性を修復することによってリスクを低減できるようにしたいと考えています。 + - **修復率の向上**: セキュリティの負債が積み重ならないようにするために、開発者による調査結果の採用を促進し、それらの脆弱性が適時に修復されるようにしたいことでしょう。 + - **コンプライアンス要件を満たす**: たとえば、多くのヘルスケア企業はGHASを使ってPHI（Personal Health Information = 個人健康情報）の露出を防いでいます。 + - **シークレットの漏洩の防止**: 多くの企業は、ソフトウェアキーや財務データなどの重要な情報の漏洩を防止したいと考えています。 + +### セキュリティ及び開発グループでロールアウトをリード + +セキュリティ及び開発チームをともにGHASのロールアウトに参加させる企業は、セキュリティグループだけを参加させ、パイロットが終わった時点で開発チームを含めようと待っている企業に比べて、成功する傾向があります。 + +GHASは、開発者のワークフローのシームレスに統合することによって、ソフトウェアセキュリティに開発者中心のアプローチを取ります。 開発グループから早期に主要な代表者をプロセスに参加させることで、ロールアウトのリスクを引き下げ、組織的な賛同が促進されます。 + +開発グループを早期に、理想的には購入の時点から参加させることで、開発プロセスの早期からセキュリティ上の懸念に対応するために企業がGHASを活用しやすくなります。 両方のグループが協力することで、プロセスの早い段階で調整を行い、サイロを取り除き、協力関係を構築して強化し、ロールアウトの責任をさらに引き受けられるようになります。 + + +### GHASについて学ぶ + +ロールアウトへの現実的な期待を設定するには、すべてのステークホルダーがGHASの働き方に関する以下の重要な事項を理解しておくようにしてください。 + +#### 1. GHASは、コードを保護するためのアクションを必要とするセキュリティツール群です。 + +GHASは、設定され、メンテナンスされ、日々のワークフローで使われ、他のツールと組み合わせられることによって価値が高まるツール群です。 + +#### 2. GHASには最初の時点から調整が必要です。 + +GHASをリポジトリでセットアップした後には、企業の要求に合わせてGHASを設定する必要があります。 特にCode scanningには、初期の結果の評価と将来のスキャンの調整など、さらなるカスタマイズが必要です。 多くのお客様は、アプリケーションの脅威モデルに基づいてCode scanningを調整するまで、初期のスキャンは限定的あるいは無関係な結果を返すことに気づいています。 + +#### 3. GHASのツール群は、合わせて使われ、アプリケーションセキュリティプログラムに統合されたときに最も効果的になります。 + +GHASは、そのツールのすべてが合わせて使われたときに最も効果的になります。 アプリケーションセキュリティプログラムの効果は、GHASをペネトレーションテストや動的スキャンといった他のツールやアクティビティと統合した時にさらに改善されます。 常に複数の保護層を利用することをおすすめします。 + +#### 4. 一部の企業では、スキャンの結果をカスタマイズしてターゲットを絞るためにカスタムの{% data variables.product.prodname_codeql %}クエリが使われています + +Code scanningは、世界で最も強力なコード解析エンジンである{% data variables.product.prodname_codeql %}によって駆動されています。 多くのお客様にとって、基本のクエリセットとコミュニティで利用できる追加のクエリは、十分以上のものです。 しかし、企業によっては異なる結果をターゲットとしたり、誤検知を減らすためにカスタムの{% data variables.product.prodname_codeql %}クエリが必要になることがあります。 + +カスタムの{% data variables.product.prodname_codeql %}クエリに関心がある企業でも、まずGHASのロールアウトと実装を完了させることをおすすめします。 続いて、企業の準備が整ったなら、{% data variables.product.prodname_professional_services %}は要求を見ていき、企業がカスタムクエリを必要としていることを確認する手助けができます。 + +#### 5. {% data variables.product.prodname_codeql %}は、Pull Requestで行われた変更だけではなく、コードベース全体をスキャンします + +Codd scanningがPull Requestから実行された場合、そのスキャンにはPull Requestで行われた変更だけではなく、コードベース全体が含まれます。 コードベース全体がスキャンされることは、コードベース内のすべての関係に対して変更が完全にレビューされることを保証するための重要なステップです。 + +{% note %} + +このシリーズの次の記事として、「[フェーズ2: 大規模な有効化の準備](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale)」を参照してください。 + +{% endnote %} 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 new file mode 100644 index 0000000000..35b7d781dc --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md @@ -0,0 +1,153 @@ +--- +title: 'フェーズ2: 大規模な有効化の準備' +intro: 'このフェーズでは、開発者を準備し、リポジトリに関するデータを収集して、チームの準備が整い、パイロットプログラムと{% data variables.product.prodname_code_scanning %}及び{% data variables.product.prodname_secret_scanning %}のロールアウトに必要なものがすべて揃っていることを確認します。' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 2. 準備 +miniTocMaxHeadingLevel: 3 +--- + +{% note %} + +この記事は、{% data variables.product.prodname_GH_advanced_security %}の大規模な採用に関するシリーズの一部です。 このシリーズの以前の記事としては「[フェーズ1: ロールアウトの戦略とゴールの調整](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals)」を参照してください。 + +{% endnote %} + +## {% data variables.product.prodname_code_scanning %}の有効化の準備 + +{% data reusables.code-scanning.about-code-scanning %} 詳しい情報については「[Code scanningについて](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)」を参照してください。 + +数百のリポジトリに対する{% data variables.product.prodname_code_scanning %}のロールアウトは、特に非効率的に行われた場合、難しくなることがあります。 以下のステップに従えば、確実にロールアウトは効率的に成功できます。 準備の一部として、チームと協力し、リポジトリに関するデータの収集を自動化し、{% data variables.product.prodname_code_scanning %}を有効化します。 + +### {% data variables.product.prodname_code_scanning %}に対するチームの準備 + +最初に、{% data variables.product.prodname_code_scanning %}を使う準備をチームに行ってください。 {% data variables.product.prodname_code_scanning %}を使うチームが多ければ多いほど、修復プランを推進し、ロールアウトの進捗をモニターするためのデータが得られることになります。 このフェーズの間は、APIの活用と内部的な有効化のイベントに集中してください。 + +中核的な焦点は、できるかぎり多くのチームが{% data variables.product.prodname_code_scanning %}を使うよう準備することにすべきです。 修復を適切に行うこともチームに推奨すべきですが、このフェーズでは問題の修復よりも{% data variables.product.prodname_code_scanning %}の有効化と利用を優先することをおすすめします。 + +### リポジトリに関する情報の収集 + +You can programmatically gather information about the different programming languages used in your repositories and use that data to enable {% data variables.product.prodname_code_scanning %} on all repositories that use the same language, using {% data variables.product.product_name %}'s GraphQL API. + +{% note %} + +**Note:** To gather this data without manually running the GraphQL queries described in this article, you can use our publicly available tool. For more information, see the "[ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement)" repository. + +{% endnote %} + +If you want to gather information from repositories belonging to multiple organizations in your enterprise, you can use the query below to obtain the names of your organizations and then feed those into repository query. Replace OCTO-ENTERPRISE with your enterprise name. + +```graphql +query { + enterprise(slug: "OCTO-ENTERPRISE") { + organizations(first: 100) { + totalCount + nodes { + name + } + pageInfo { + endCursor + hasNextPage + } + } + } +} +``` + +You can identify which repositories use which languages by collating repositories by language at the organization level. You can modify the sample GraphQL query below, replacing OCTO-ORG with the organization name. + +```graphql +query { + organization(login: "OCTO-ORG") { + repositories(first: 100) { + totalCount + nodes { + nameWithOwner + languages(first: 100) { + totalCount + nodes { + name + } + } + } + pageInfo { + endCursor + hasNextPage + } + } + } +} +``` + +For more information about running GraphQL queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." + +Then, convert the data from the GraphQL query into a readable format, such as a table. + +| 言語 | Number of Repos | Name of Repos | +| ----------------------- | --------------- | ----------------------------- | +| JavaScript (TypeScript) | 4212 | org/repo
org/repo | +| Python | 2012 | org/repo
org/repo | +| Go | 983 | org/repo
org/repo | +| Java | 412 | org/repo
org/repo | +| Swift | 111 | org/repo
org/repo | +| Kotlin | 82 | org/repo
org/repo | +| C | 12 | org/repo
org/repo | + +You can filter out the languages that are currently not supported by {% data variables.product.prodname_GH_advanced_security %} from this table. + +If you have repositories with multiple languages, you can format the GraphQL results as shown in the table below. Filter out languages that are not supported, but retain all repositories with at least one supported language. You can enable {% data variables.product.prodname_code_scanning %} on these repositories, and all supported languages will be scanned. + +| Language(s) | Number of Repos | Name of Repos | +| ---------------------- | --------------- | ------------------------------ | +| JavaScript/Python/Go | 16 | org/repo
org/repo | +| Rust/TypeScript/Python | 12 | org/repo
org/repo | + +An understanding of which repositories are using which languages will help you identify candidate repositories for pilot programs in phase 3, and prepares you to enable {% data variables.product.prodname_code_scanning %} across all repositories, one language at a time, in phase 5. + +{% ifversion ghes %} + +### Enabling {% data variables.product.prodname_code_scanning %} for your appliance + +Before you can proceed with pilot programs and rolling out {% data variables.product.prodname_code_scanning %} across your enterprise, you must first enable {% data variables.product.prodname_code_scanning %} for your appliance. For more information, see "[Configuring code scanning for your appliance](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance)." + +{% endif %} + +## Preparing to enable {% data variables.product.prodname_secret_scanning %} + +If a project communicates with an external service, it might use a token or private key for authentication. リポジトリにシークレットをチェックインする場合、リポジトリへの読み取りアクセスを持つすべてのユーザがシークレットを使用して、自分の権限で外部サービスにアクセスできます。 {% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repositories for secrets and alert you{% ifversion secret-scanning-push-protection %} or block the push containing the secret{% endif %}. 詳しい情報については、「[シークレットスキャニングについて](/code-security/secret-scanning/about-secret-scanning)」を参照してください。 + +### Considerations when enabling {% data variables.product.prodname_secret_scanning %} + +{% data variables.product.product_name %}’s {% data variables.product.prodname_secret_scanning %} capability is slightly different from {% data variables.product.prodname_code_scanning %} since it requires no specific configuration per programming language or per repository and less configuration overall to get started. This means enabling {% data variables.product.prodname_secret_scanning %} at the organizational level can be easy but clicking **Enable All** at the organization level and ticking the option **Automatically enable {% data variables.product.prodname_secret_scanning %} for every new repository** has some downstream effects that you should be aware of: + +- **License consumption** + Enabling {% data variables.product.prodname_secret_scanning %} for all repositories will consume all your licenses, even if no one is using code scanning. This is fine unless you plan to increase the number of active developers in your organization. If the number of active developers is likely to increase in the coming months, you may exceed your license limit and then be unable to use {% data variables.product.prodname_GH_advanced_security %} on newly created repositories. +- **Initial high volume of detected secrets** + If you are enabling {% data variables.product.prodname_secret_scanning %} on a large organization, be prepared to see a high number of secrets found. Sometimes this comes as a shock to organizations and the alarm is raised. If you would like to turn on {% data variables.product.prodname_secret_scanning %} across all repositories at once, plan for how you will respond to multiple alerts across the organization. + +{% data variables.product.prodname_secret_scanning_caps %} can be enabled for individual repositories. 詳しい情報については「[リポジトリでの{% data variables.product.prodname_secret_scanning %}の設定](/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories)」を参照してください。 {% data variables.product.prodname_secret_scanning_caps %} can also be enabled for all repositories in your organization, as described above. For more information on enabling for all repositories, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + +### Custom patterns for {% data variables.product.prodname_secret_scanning %} + +{% ifversion ghae %} +{% note %} + +**ノート:** {% data variables.product.prodname_secret_scanning %}のカスタムパターンは現在ベータであり、変更されることがあります。 + +{% endnote %} +{% endif %} + +{% data variables.product.prodname_secret_scanning_caps %} detects a large number of default patterns but can also be configured to detect custom patterns, such as secret formats unique to your infrastructure or used by integrators that {% data variables.product.product_name %}'s {% data variables.product.prodname_secret_scanning %} does not currently detect. For more information about supported secrets for partner patterns, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)." + +As you audit your repositories and speak to security and developer teams, build a list of the secret types that you will later use to configure custom patterns for {% data variables.product.prodname_secret_scanning %}. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 + + +{% note %} + +For the next article in this series, see "[Phase 3: Pilot programs](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs)." + +{% endnote %} 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 new file mode 100644 index 0000000000..3c48c7d8a8 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md @@ -0,0 +1,86 @@ +--- +title: 'Phase 3: Pilot programs' +intro: 'You may benefit from beginning with a few high-impact projects and teams with which to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS, learn how to enable and configure GHAS, and build a solid foundation on GHAS before rolling out to the remainder of your company.' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 3. Pilot programs +miniTocMaxHeadingLevel: 3 +--- + +{% note %} + +この記事は、{% data variables.product.prodname_GH_advanced_security %}の大規模な採用に関するシリーズの一部です。 For the previous article in this series, see "[Phase 2: Preparing to enable at scale](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale)." + +{% endnote %} + +## About pilot programs + +We recommend you identify a few high-impact projects or teams to use in a pilot rollout of GHAS. This allows an initial group within your company to get familiar with GHAS and builds a solid foundation for GHAS before you roll it out to the remainder of your company. + +The steps in this phase will help you enable GHAS on your enterprise, begin using its features, and review your results. If you’re working with {% data variables.product.prodname_professional_services %}, they can provide additional assistance through this process through onboarding sessions, GHAS workshops, and troubleshooting as needed. + +Before you start your pilot projects, we recommend that you schedule some meetings for your teams, such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These meetings will help you all make adjustments as needed and ensure your teams are prepared and supported to complete the pilot successfully. + +{% ifversion ghes %} + +If you haven't already enabled GHAS for your {% data variables.product.prodname_ghe_server %} instance, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." + +{% endif %} + +You need to enable GHAS for each pilot project, either by enabling the GHAS features for each repository or for all repositories in any organizations taking part in the pilot. 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)" + +## Piloting {% data variables.product.prodname_code_scanning %} + +{% ifversion ghes %} + +To enable {% data variables.product.prodname_code_scanning %} on your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." + +{% elsif ghae %} + +To enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %} you must make runners available to run workflows in {% data variables.product.prodname_ghe_managed %}, see "[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 %} + +You can run code scanning on a repository by creating a {% data variables.product.prodname_actions %} workflow to run the [CodeQL action](https://github.com/github/codeql-action/). {% ifversion ghec %}{% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners)」を参照してください。{% endif %} + +For more information about {% data variables.product.prodname_actions %}, see: + - "[Learn GitHub Actions](/actions/learn-github-actions)" + - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)" + - [ワークフローをトリガーするイベント](/actions/learn-github-actions/events-that-trigger-workflows) + - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)" + +We recommend enabling {% data variables.product.prodname_code_scanning %} on a repository-by-repository basis as part of your pilot program. For more information, see "[Setting up code scanning for a repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)." + +If you want to enable code scanning for many repositories, you may want to script the process. + +For an example of a script that opens pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. + +When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans. 詳しい情報については、「[Code scanningを設定する](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)」を参照してください。 + +If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, which are generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)." + +## Piloting {% data variables.product.prodname_secret_scanning %} + +GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally. + +{% ifversion ghes %} + +To enable secret scanning for your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring secret scanning for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance)." + +{% endif %} + +You need to enable secret scanning for each pilot project, either by enabling the feature for each repository or for all repositories in any organizations taking part in the project. 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)." + +If you have collated any custom patterns specific to your enterprise, especially any related to the projects piloting {% data variables.product.prodname_secret_scanning %}, you can configure those. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 + +To learn how to view and close alerts for secrets checked into your repository, see "[Managing alerts from secret scanning](/code-security/secret-scanning/managing-alerts-from-secret-scanning)." + +{% note %} + +For the next article in this series, see "[Phase 4: Create internal documentation](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation)." + +{% endnote %} 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 new file mode 100644 index 0000000000..4c466cd226 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md @@ -0,0 +1,32 @@ +--- +title: 'Phase 4: Create internal documentation' +intro: 'You will create internal documentation and then communicate this to the consumers of {% data variables.product.prodname_GH_advanced_security %}.' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 4. Create internal documentation +miniTocMaxHeadingLevel: 3 +--- + +{% note %} + +この記事は、{% data variables.product.prodname_GH_advanced_security %}の大規模な採用に関するシリーズの一部です。 For the previous article in this series, see "[Phase 3: Pilot programs](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs)." + +{% endnote %} + +Before enabling {% data variables.product.prodname_GH_advanced_security %}, you should create internal documentation that defines processes for teams to follow. Everyone needs to know what to do when they receive a security alert, even if the process simply asks the team to apply their best judgment. Documentation will also prevent developers from getting blocked when they have questions. You should put the documentation about GHAS with existing developer-focused documentation, such as your developer portal or custom knowledge base. + +If you ran pilot programs, use the experiences and feedback from the teams involved in those pilots to influence your documentation. This is especially useful if you encountered issues that are specific to your company, that other teams will also likely encounter. + +If you skip creating internal documentation, your rollout won’t go at your intended pace. Creating internal documentation may slow the initial rollout by a week or two, but that time will be made up when developers can answer their own questions instead of coming to your team. + +Education is probably the most crucial part of the rollout as it teaches developers what to do in different situations. You should ensure developers are empowered to maintain the security of their repository and that the security team are authorized to verify both what developers are doing and that it's in the best interest of security. In additional to internal documentation, education can take the form of online sessions, Q&As, etc. + +{% note %} + +For the next 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 %} 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 new file mode 100644 index 0000000000..63820eeb14 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md @@ -0,0 +1,56 @@ +--- +title: 'Phase 5: Rollout and scale code scanning' +intro: 'You can leverage the available APIs to rollout {% data variables.product.prodname_code_scanning %} programmatically by team and by language across your enterprise using the repository data you collected earlier.' +versions: + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 5. Rollout code scanning +miniTocMaxHeadingLevel: 3 +--- + +{% note %} + +この記事は、{% data variables.product.prodname_GH_advanced_security %}の大規模な採用に関するシリーズの一部です。 For the previous article in this series, see "[Phase 4: Create internal documentation](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation)." + +{% endnote %} + +### コードスキャンを有効化する + +Using the data you collated in [Phase 2](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale), you can begin to enable GHAS and then {% data variables.product.prodname_code_scanning %} on your repositories, one language at a time. The step-by-step process for enabling GHAS should look like this: + +1. Enable GHAS on the repository. 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 +1. Create a pull request against the repository's default branch with a `codeql-analysis.yml` file containing an example of how to run CodeQL for that language. 詳しい情報については[プルリクエストの作成](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)を参照してください。 +1. Create an issue in the repository to explain why a pull request has been raised. The issue you create can contain a link to the previous communication sent to all users, but can also explain what changes the pull request introduces, what next steps the team have to take, what the team's responsibilities are, and how the team should be using {% data variables.product.prodname_code_scanning %}. 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-an-issue)」を参照してください。 + +There is a publicly available tool that completes the first two steps called the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement). You can re-run the ghas-enablement tool in batches of languages where it makes sense. For example, JavaScript, TypeScript, Python, and Go likely have a similar build process and could therefore use a similar CodeQL analysis file. The ghas-enablement tool can also be used for languages such as Java, C, and C++, but due to the varied nature of how these languages build and compile you may need to create more targeted CodeQL analysis files. + +{% note %} + +**Note:** If you are intending to use {% data variables.product.prodname_actions %} to control {% data variables.product.prodname_code_scanning %} and you do not use the [ghas-enablement tool](https://github.com/NickLiffen/ghas-enablement), keep in mind that there is no API access to the `.github/workflow` directory. This means that you cannot create a script without a git client underlying the automation. The workaround is to leverage bash scripting on a machine or container which has a git client. The git client can push and pull files into the `.github/workflows` directory where the `codeql-analysis.yml` file is located. + +{% endnote %} + +It is important to not just push the `codeql-analysis.yml` file the repository's default branch. Using a pull request puts ownership on the development team to review and merge, allowing the development team to learn about {% data variables.product.prodname_code_scanning %} and involving the team in the process. + +You should capture the pull request URLs created by automation, and check each week for any activity and see which ones are closed. After a few weeks, it may be worth creating another issue or sending internal emails if the pull request remains unmerged. + +### Creating subject matter experts + +You can then proceed to the next stage of enablement, which is creating internal subject matter experts (or SMEs) and arranging company meetings. Opening pull requests and issues in repositories will likely tackle a large percentage of your adoption, but this doesn’t tackle one-off use cases where a specific build process, framework, or library needs specific feature flags to be enabled. A more personalized and hands-on approach is required to push high adoption, especially for Java, C, and C++. + +It’s a good idea to run regular company meetings on specific topics to educate and discuss the rollout with a larger group. This is much more time-efficient for an enterprise with thousands of repositories compared to working with one team at a time. Teams can come to sessions that are relevant to them. Some example sessions that have been run before include: + +- コンテナで {% data variables.product.prodname_code_scanning_capc %} +- {% data variables.product.prodname_code_scanning_capc %} & Java Struts +- {% data variables.product.prodname_code_scanning_capc %} & JSP + +You can use the data you have collected about the distribution of different languages among repositories to create targeted meetings. + +{% note %} + +For the next article in this series, see "[Phase 6: Rollout and scale secret scanning](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning)." + +{% endnote %} 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 new file mode 100644 index 0000000000..327d99fe10 --- /dev/null +++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md @@ -0,0 +1,106 @@ +--- +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: '*' + ghec: '*' +topics: + - Advanced Security +shortTitle: 6. Rollout secret scanning +miniTocMaxHeadingLevel: 3 +--- + +{% note %} + +この記事は、{% data variables.product.prodname_GH_advanced_security %}の大規模な採用に関するシリーズの一部です。 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 %} + +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)." + +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. Focus on newly committed secrets + +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. **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 %} + + **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 a email/message to the responsible people or open an issue. + + {% endnote %} +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. + +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 %} + +**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. Remediate previously committed secrets, starting with the most critical + +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. + +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. 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 %} + + **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. 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 %} + + 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 + - リポジトリ + - Secret type + - Secret value + - Maintainers on repository to contact + + {% note %} + + **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. 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. Expand the program to include more secret types and custom patterns + +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. + +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. 詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 + +{% ifversion secret-scanning-push-protection %} + +You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. 詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)」を参照してください。 + +{% endif %} + +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 %} + +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/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 767d9dedac..8cdc0a86f8 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 @@ -37,7 +37,7 @@ topics: コードベースが既知のセキュリティリスクのある依存関係を使用していることを検出すると、{% data variables.product.product_name %} は {% data variables.product.prodname_dependabot_alerts %} を生成します。 {% data variables.product.prodname_dependabot_security_updates %} が有効になっているリポジトリの場合、{% data variables.product.product_name %} がデフォルトのブランチで脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} はそれを修正するためのプルリクエストを作成します。 プルリクエストは、脆弱性を回避するために必要最低限の安全なバージョンに依存関係をアップグレードします。 -{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}{% data variables.product.prodname_dependabot_alerts %}は、{% data variables.product.prodname_dependabot_alerts %}タブ内のドロップダウンメニューで、あるいは検索バーで`key:value`ペアとしてフィルタを入力することで、ソートとフィルタリングできます。 利用可能なフィルタは、リポジトリ（たとえば`repo:my-repository`）、パッケージ（たとえば`package:django`）、エコシステム（たとえば`ecosystem:npm`）、マニフェスト（たとえば`manifest:webwolf/pom.xml`）、状態（たとえば`is:open`）、アドバイザリがパッチを持っているか（たとえば`has: patch`）です。{% ifversion dependabot-alerts-development-label %}たとえば`scope:development`あるいは`scope:runtime`というように、`scope`を使って依存関係のスコープデータでアラートをフィルタすることもできます。 `scope:development`を指定すると、アラートのリストは実働ではなく開発の間に使われた依存関係だけを表示します。{% endif %} +{% ifversion dependabot-most-important-sort-option %} By default, {% data variables.product.prodname_dependabot_alerts %} are displayed in the {% data variables.product.prodname_dependabot_alerts %} tab in order of importance, but you can sort alerts by other criteria. {% endif %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %}You can sort and filter {% data variables.product.prodname_dependabot_alerts %} with the dropdown menus in the {% data variables.product.prodname_dependabot_alerts %} tab or by typing filters as `key:value` pairs into the search bar. 利用可能なフィルタは、リポジトリ（たとえば`repo:my-repository`）、パッケージ（たとえば`package:django`）、エコシステム（たとえば`ecosystem:npm`）、マニフェスト（たとえば`manifest:webwolf/pom.xml`）、状態（たとえば`is:open`）、アドバイザリがパッチを持っているか（たとえば`has: patch`）です。{% ifversion dependabot-alerts-development-label %}たとえば`scope:development`あるいは`scope:runtime`というように、`scope`を使って依存関係のスコープデータでアラートをフィルタすることもできます。 `scope:development`を指定すると、アラートのリストは実働ではなく開発の間に使われた依存関係だけを表示します。{% endif %} それぞれの{% data variables.product.prodname_dependabot %}アラートは一意の数値識別子を持っており、{% data variables.product.prodname_dependabot_alerts %}タブにはすべての検出された脆弱性に対するアラートがリストされます。 旧来の{% data variables.product.prodname_dependabot_alerts %}は依存関係で脆弱性をグループ化し、依存関係ごとに1つのアラートを生成しました。 旧来の{% data variables.product.prodname_dependabot %}アラートにアクセスすると、そのパッケージでフィルタされた{% data variables.product.prodname_dependabot_alerts %}タブにリダイレクトされます。 {% endif %} {% endif %} @@ -90,7 +90,16 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} -1. あるいは、アラートをフィルタリングするには、**Repository（リポジトリ）**、**Package（パッケージ）**、**Ecosystem（エコシステム）**、**Manifest（マニフェスト）**ドロップダウンメニューを選択し、続いて適用したいフィルタをクリックしてください。 検索バーにフィルタを入力することもできます。 たとえば`ecosystem:npm`{% ifversion ghes < 3.7 or ghae-issue-5638 %}もしくは`has:patch`{% endif %}{% ifversion dependabot-alerts-development-label %}、`has:patch`、`scope:development`{% endif %}。 アラートをソートするには**Sort（ソート）**ドロップダウンメニューを選択し、ソートに使いたい選択肢をクリックしてください。 +1. あるいは、アラートをフィルタリングするには、**Repository（リポジトリ）**、**Package（パッケージ）**、**Ecosystem（エコシステム）**、**Manifest（マニフェスト）**ドロップダウンメニューを選択し、続いて適用したいフィルタをクリックしてください。 検索バーにフィルタを入力することもできます。 たとえば`ecosystem:npm`{% ifversion ghes < 3.7 or ghae-issue-5638 %}もしくは`has:patch`{% endif %}{% ifversion dependabot-alerts-development-label %}、`has:patch`、`scope:development`{% endif %}。 To sort alerts, select the **Sort** dropdown menu then click the option that you would like to sort by, or type `sort:` into the search bar and choose an option from the suggestions (for example, `sort:newest`). + + {% ifversion dependabot-most-important-sort-option %} + {% note %} + + **Note:** By default, {% data variables.product.prodname_dependabot_alerts %} are sorted by importance. The "Most important" sort helps you prioritize which {% data variables.product.prodname_dependabot_alerts %} to focus on first. Alerts are ranked based on their potential impact, actionability, and relevance. Our prioritization calculation is constantly being improved and includes factors like CVSS score, dependency scope, and whether vulnerable function calls are found for the alert. + {% endnote %} + + ![Screenshot of Sort dropdown with "Most important" sort](/assets/images/help/dependabot/dependabot-alerts-sort-dropdown.png) + {% endif %} アラートのラベルをクリックして、その種類のアラートだけを表示させることもできます。{% ifversion dependabot-alerts-development-label %}たとえば、アラートのリスト内の`Development`ラベルをクリックすれば、実働ではなく開発で使われている依存関係に関係するアラートだけが表示されます。 サポートされているエコシステムのリストに関する情報については「[依存関係スコープでサポートされているエコシステムとマニフェスト](#supported-ecosystems-and-manifests-for-dependency-scope)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md index 1f07031b8a..0d98a178bb 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md @@ -44,9 +44,13 @@ shortTitle: Dependabot PRの管理 デフォルトでは、{% data variables.product.prodname_dependabot %} は自動的にプルリクエストをリベースして競合を解決します。 マージの競合を手動で処理する場合は、`rebase-strategy` オプションを使用してこれを無効にできます。 詳細については「[dependabot.ymlファイルの設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)」を参照してください。 +## {% data variables.product.prodname_dependabot %}に対する追加のコミットへのリベースとフォースプッシュの許可 + +デフォルトでは、{% data variables.product.prodname_dependabot %}はPull Requestに対して追加のコミットが行われると、そのPull Requestのリベースを止めます。 ブランチに追加されたコミットに対するフォースプッシュを{% data variables.product.prodname_dependabot %}に許可するには、`[dependabot skip]`、`[skip dependabot]`、`[dependabot-skip]`、`[skip-dependabot]`のいずれかの文字列をコミットメッセージに含めてください。大文字でも小文字でもかまいません。 + ## {% data variables.product.prodname_dependabot %} Pull Requestをコメントコマンドで管理する -{% data variables.product.prodname_dependabot %} はコメント内の単純なコマンドに応答します。 それぞれのPull Requestには、"{% data variables.product.prodname_dependabot %} commands and options"セクションの下に、そのPull Requestを処理するのに使えるコマンド（たとえばPull Requestのマージ、squash、再オープン、クローズ、リベース）の詳細があります。 これらの自動生成されたプルリクエストをできるだけ簡単にトリアージできるようにすることが目的です。 +{% data variables.product.prodname_dependabot %} はコメント内の単純なコマンドに応答します。 それぞれのPull Requestには、"{% data variables.product.prodname_dependabot %} commands and options"セクションの下に、そのPull Requestを処理するのに使えるコマンド（たとえばPull Requestのマージ、squash、再オープン、クローズ、リベース）の詳細があります。 これらの自動生成されたPull Requestをできるだけ簡単にトリアージできるようにすることが目的です。 {% data variables.product.prodname_dependabot %} Pull Requestでは、以下のいずれのコマンドを使うこともできます。 diff --git a/translations/ja-JP/content/code-security/index.md b/translations/ja-JP/content/code-security/index.md index e7248afec2..14748f9224 100644 --- a/translations/ja-JP/content/code-security/index.md +++ b/translations/ja-JP/content/code-security/index.md @@ -50,6 +50,7 @@ topics: - Vulnerabilities children: - /getting-started + - /adopting-github-advanced-security-at-scale - /secret-scanning - /code-scanning - /repository-security-advisories diff --git a/translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md index b9db1d2e86..d81285627b 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md +++ b/translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md @@ -71,4 +71,4 @@ shortTitle: シークレットスキャンの設定 ## 参考リンク - 「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」 -- "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)" +- 「[{% data variables.product.prodname_secret_scanning %}のカスタムパターンの定義](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)」 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 6889d3b34d..2e04c3175f 100644 --- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md @@ -1,6 +1,6 @@ --- -title: セキュリティの概要について -intro: OrganizationもしくはTeamが所有するリポジトリに関するセキュリティアラートを、セキュリティの概要ページという一カ所で表示、フィルタリング、ソートできます。 +title: About the security overview +intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: @@ -19,65 +19,65 @@ topics: - Dependencies - Organizations - Teams -shortTitle: セキュリティの概要について +shortTitle: About security overview --- {% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} -## セキュリティの概要について +## About the security overview -{% ifversion ghes or ghec or ghae %}{% elsif fpt %}{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationにおいて、{% endif %}セキュリティの概要は{% ifversion ghes or ghec or ghae %}自分の{% elsif fpt %}{% endif %}Organizationのセキュリティの状況の高レベルの表示に、あるいは介入が必要な問題のあるリポジトリを特定するために利用できます。 {% ifversion ghes or ghec or ghae %}{% elsif fpt %}それらのOrganizationの{% endif %}セキュリティの概要では、集約されたセキュリティ情報あるいはリポジトリ固有のセキュリティ情報を表示できます。 {% ifversion ghes or ghec or ghae %}{% elsif fpt %}{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationでは、{% endif %}セキュリティの概要を使って{% ifversion ghes or ghec or ghae %}自分の{% elsif fpt %}Organizationの{% endif %}リポジトリでどのセキュリティ機能が有効化されているかを見ることも、現在使われていない利用可能なセキュリティ機能を設定することもできます。 {% ifversion fpt %}詳しい情報については[{% data variables.product.prodname_ghe_cloud %}ドキュメンテーション](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)を参照してください。{% endif %} +{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can use the security overview for a high-level view of the security status of {% ifversion ghes or ghec or ghae %}your {% elsif fpt %}their{% endif %} organization or to identify problematic repositories that require intervention. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %}These organizations{% endif %} can view aggregate or repository-specific security information in the security overview. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can also use the security overview to see which security features are enabled for {% ifversion ghes or ghec or ghae %}your {% elsif fpt %}their {% endif %} repositories and to configure any available security features that are not currently in use. {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %} {% ifversion ghec or ghes or ghae %} The security overview indicates whether {% ifversion fpt or ghes or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} -リポジトリ及びOrganizationレベルでのコードの保護に関する詳しい情報については「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」及び「[Organizationの保護](/code-security/getting-started/securing-your-organization)」を参照してください。 +For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)." -あなたの会社のアプリケーションセキュリティチームは、Organizationのセキュリティの状況の幅広い分析と特定の分析の両方にセキュリティの概要を利用できます。 たとえば、Enterpriseに{% data variables.product.prodname_GH_advanced_security %}をロールアウトするのにしたがって、Organizationや特定のTeamによる機能の採用をモニタリングしたり、Organization内のすべてのリポジトリに渡って特定のタイプと重要度のアラートをすべてレビューしたりするのに概要ページを利用できます。 +The application security team at your company can use the security overview for both broad and specific analyses of your organization's security status. For example, they can use the overview page to monitor adoption of features by your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %} to your enterprise, or to review all alerts of a specific type and severity level across all repositories in your organization. -### アラートのフィルタリングとソートについて +### About filtering and sorting alerts -セキュリティの概要では、Organizationや特定のリポジトリ内のセキュリティリスクを理解するために、アラートを表示、ソート、フィルタリングできます。 セキュリティのサマリは高度に対話型であり、アラートのリスクレベル、アラートのタイプ、機能の有効化といった修飾子に基づいて特定のカテゴリの情報を調査できます。 関心の領域をより狭めて集中するために、複数のフィルタを適用することもできます。 たとえば、多数の{% data variables.product.prodname_dependabot_alerts %}が生じているプライベートリポジトリや、{% data variables.product.prodname_code_scanning %}アラートのないリポジトリを識別できます。 詳しい情報については「[セキュリティの概要におけるアラートのフィルタリング](/code-security/security-overview/filtering-alerts-in-the-security-overview)」を参照してください。 +In the security overview, you can view, sort, and filter alerts to understand the security risks in your organization and in specific repositories. The security summary is highly interactive, allowing you to investigate specific categories of information, based on qualifiers like alert risk level, alert type, and feature enablement. You can also apply multiple filters to focus on narrower areas of interest. For example, you can identify private repositories that have a high number of {% data variables.product.prodname_dependabot_alerts %} or repositories that have no {% data variables.product.prodname_code_scanning %} alerts. For more information, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)." {% ifversion security-overview-views %} -セキュリティの概要では、Organizationとリポジトリの双方のレベルにおいて、Secret scanningアラートやCode scanningアラートといったとくていのセキュリティ機能のための専用のビューがあります。 これらのビューを使って、分析をアラートの特定セットに制限し、さらにそれぞれのビューに固有のフィルタ群で結果をさらに絞り込むことができます。 たとえば、Secret scanningアラートビューでは、`Secret type`フィルタを使ってGitHubの個人アクセストークンのような特定のシークレットだけのSecret scanningアラートを表示させることができます。 リポジトリレベルでは、セキュリティの概要を使って特定のリポジトリの現在のセキュリティの状況を評価し、そのリポジトリでまだ使われていない追加のセキュリティ機能を設定できます。 +In the security overview, at both the organization and repository level, there are dedicated views for specific security features, such as secret scanning alerts and code scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. {% endif %} -![Organizationのセキュリティの概要](/assets/images/help/organizations/security-overview.png) +![The security overview for an organization](/assets/images/help/organizations/security-overview.png) -セキュリティの概要中の各リポジトリで、セキュリティ機能のそれぞれの種類のアイコンと、それぞれの種類についていくつのアラートがあるかが表示されます。 リポジトリでセキュリティの機能が有効化されていないなら、その機能のアイコンはグレー表示されます。 加えて、各リポジトリについてCode scanning、Dependabot、Secret scanningアラートに基づいてリスクスコアが計算されます。 このスコアはベータであり、注意して使用してください。 このアルゴリズムとアプローチは変更されることがあります。 +For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its code scanning, Dependabot and secret scanning alerts. This score is in beta and should be used with caution. Its algorithm and approach is subject to change. -![セキュリティの概要中のアイコン](/assets/images/help/organizations/security-overview-icons.png) +![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png) -| アイコン | 意味 | -| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} アラート. 詳しい情報については「[{% data variables.product.prodname_code_scanning %}について](/code-security/secure-coding/about-code-scanning)」を参照してください。 | -| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} アラート. 詳しい情報については「[{% data variables.product.prodname_secret_scanning %}について](/code-security/secret-security/about-secret-scanning)」を参照してください。 | -| {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}について受ける方法は、カスタマイズできます。 詳しい情報については「[{% data variables.product.prodname_dependabot_alerts %}について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 | -| {% octicon "check" aria-label="Check" %} | セキュリティ機能は有効化されていますが、このリポジトリではアラートを発していません。 | -| {% octicon "x" aria-label="x" %} | このリポジトリでは、このセキュリティ機能はサポートされていません。 | +| Icon | Meaning | +| -------- | -------- | +| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." | +| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." | +| {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." | +| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. | +| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. | -セキュリティの概要は、セキュリティ機能が発したアクティブなアラートを表示します。 リポジトリに対してセキュリティの概要でアラートがない場合でも、検出されていないセキュリティ脆弱性やコードのエラーは存在するかもしれません。 +The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist. -### Organizationレベルのセキュリティの概要について +### About the organization-level security overview -Organizationのレベルでは、セキュリティの概要はOrganizationが所有するリポジトリに関する集約されたリポジトリ固有のセキュリティ情報を表示します。 Organizationレベルでセキュリティ機能によって情報をフィルタリングできます。 +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. {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} -### Enterpriseレベルのセキュリティの概要について -Enterpriseのレベルでは、セキュリティの概要はEnterpriseにおける集約されたセキュリティ情報と、リポジトリ固有のセキュリティ情報を表示します。 Enterpriseが所有しており、セキュリティアラートがあるリポジトリを見ることも、Enterpirse全体にわたってすべてのセキュリティアラートあるいはセキュリティ機能固有のアラートを見ることもできます。 +### 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. -Enterprise内のOrganizationのオーナー及びOrganizationのセキュリティ管理者も、Enterpriseレベルのセキュリティ概要への限定されたアクセスを持ちます。 それらの人々は、完全なアクセスを持っているOrganizationのリポジトリとアラートだけを見ることができます。 +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. {% elsif fpt %} -### Enterpriseレベルのセキュリティの概要について -Enterpriseのレベルでは、セキュリティの概要はEnterpriseにおける集約された情報と、リポジトリ固有の情報を表示します。 詳しい情報については{% data variables.product.prodname_ghe_cloud %}、ドキュメンテーションの、「[Enterpriseレベルのセキュリティの概要について](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)を参照してください。 +### 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 %} -### Teamレベルのセキュリティの概要について -Teamレベルでは、セキュリティの概要はTeamが管理権限を持つリポジトリの固有のセキュリティ情報を表示します。 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)」を参照してください。 +### About the team-level security overview +At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." {% endif %} 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 5b3bb39b73..7f94a835ea 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 @@ -1,6 +1,6 @@ --- title: codespace がプライベートイメージレジストリにアクセスできるようにする -intro: 'シークレットを使用して、{% data variables.product.prodname_codespaces %} がプライベートイメージレジストリにアクセスできるようにすることができます' +intro: 'シークレットを使用して、{% data variables.product.prodname_github_codespaces %} がプライベートイメージレジストリにアクセスできるようにすることができます' versions: fpt: '*' ghec: '*' @@ -10,15 +10,15 @@ product: '{% data reusables.gated-features.codespaces %}' shortTitle: プライベートイメージレジストリ --- -## About private image registries and {% data variables.product.prodname_codespaces %} +## About private image registries and {% data variables.product.prodname_github_codespaces %} A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more images. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub. -{% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry. +{% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_github_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry. ## Accessing images stored in {% data variables.product.prodname_dotcom %} Container Registry -{% data variables.product.prodname_dotcom %} Container Registry is the easiest way for {% data variables.product.prodname_github_codespaces %} to consume devcontainer container images. +{% data variables.product.prodname_dotcom %} Container Registry is the easiest way for {% data variables.product.prodname_codespaces %} to consume devcontainer container images. For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)". @@ -52,13 +52,13 @@ We recommend publishing images via {% data variables.product.prodname_actions %} ## Accessing images stored in other container registries -If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. これらのシークレットが見つかった場合、{% data variables.product.prodname_codespaces %} はレジストリを codespace 内で使用できるようにします。 +If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. これらのシークレットが見つかった場合、{% data variables.product.prodname_github_codespaces %} はレジストリを codespace 内で使用できるようにします。 - `<*>_CONTAINER_REGISTRY_SERVER` - `<*>_CONTAINER_REGISTRY_USER` - `<*>_CONTAINER_REGISTRY_PASSWORD` -シークレットは、ユーザ、リポジトリ、または Organization レベルで保存できるため、異なる Codespaces 間で安全に共有できます。 When you create a set of secrets for a private image registry, you need to replace the "<*>" in the name with a consistent identifier. 詳しい情報については、「[Codespaces の暗号化されたシークレットを管理する](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」および「[Codespaces のリポジトリと Organization の暗号化されたシークレットを管理する](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)」を参照してください。 +シークレットは、ユーザ、リポジトリ、または Organization レベルで保存できるため、異なる Codespaces 間で安全に共有できます。 When you create a set of secrets for a private image registry, you need to replace the "<*>" in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)." If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list. diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md similarity index 82% rename from translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md rename to translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md index ba8c543f31..4fa92e8d97 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Codespaces のシステム災害復旧 +title: Disaster recovery for GitHub Codespaces intro: この記事では、大規模な自然災害や広範囲にわたるサービスの中断により、地域全体で障害が発生した場合のシステム災害復旧シナリオのガイダンスについて説明します。 versions: fpt: '*' @@ -8,9 +8,11 @@ product: '{% data reusables.gated-features.codespaces %}' topics: - Codespaces shortTitle: Disaster recovery +redirect_from: + - /codespaces/codespaces-reference/disaster-recovery-for-codespaces --- -当社は、ユーザが {% data variables.product.prodname_codespaces %} をいつでも確実にご利用いただけるよう努力しています。 しかし、当社の管理できる範囲を超えてサービスに影響を及ぼし、計画外のサービスの中断を引き起こす不可抗力が発生する可能性があります。 +当社は、ユーザが {% data variables.product.prodname_github_codespaces %} をいつでも確実にご利用いただけるよう努力しています。 しかし、当社の管理できる範囲を超えてサービスに影響を及ぼし、計画外のサービスの中断を引き起こす不可抗力が発生する可能性があります。 システム災害復旧シナリオはまれにしか発生しませんが、リージョン全体にわたる停止が発生する可能性に備えておくことをお勧めします。 リージョン全体でサービスが中断した場合、ローカルで冗長化されたデータのコピーは一時的に利用できなくなります。 @@ -24,7 +26,7 @@ shortTitle: Disaster recovery ## Option 1: Create a new codespace in another region -In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. この新しい codespace には、{% data variables.product.prodname_dotcom %} への最後のプッシュ時点までのすべての変更が含まれます。 For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." +In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. この新しい codespace には、{% data variables.product.prodname_dotcom %} への最後のプッシュ時点までのすべての変更が含まれます。 For information on manually setting another region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)." You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." @@ -36,7 +38,7 @@ You can check the current service status on the [Status Dashboard](https://www.g ## オプション 3: リポジトリをローカルでクローンする、またはブラウザで編集する -{% data variables.product.prodname_codespaces %} では事前構成された開発者環境を利用できるメリットがありますが、ソースコードは常に {% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリからアクセス可能である必要があります。 {% data variables.product.prodname_codespaces %} が停止した場合でも、リポジトリをローカルでクローンしたり、{% data variables.product.company_short %} ブラウザエディタでファイルを編集したりすることができます。 For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." +{% data variables.product.prodname_codespaces %} では事前構成された開発者環境を利用できるメリットがありますが、ソースコードは常に {% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリからアクセス可能である必要があります。 {% data variables.product.prodname_codespaces %} が停止した場合でも、リポジトリをローカルでクローンしたり、{% data variables.product.company_short %} ブラウザエディタでファイルを編集したりすることができます。 詳しい情報については「[ファイルの編集](/repositories/working-with-files/managing-files/editing-files)」を参照してください。 このオプションでは開発環境を設定しませんが、サービスの中断が解決するのを待つ間、必要に応じてソースコードを変更できます。 diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/index.md b/translations/ja-JP/content/codespaces/codespaces-reference/index.md index 8c93bae032..9a21153932 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/index.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/index.md @@ -1,16 +1,16 @@ --- title: リファレンス -intro: 'このセクションには、{% data variables.product.prodname_codespaces %} を正しく使用するためのリファレンスが含まれています' +intro: 'このセクションには、{% data variables.product.prodname_github_codespaces %} を正しく使用するためのリファレンスが含まれています' versions: fpt: '*' ghec: '*' product: '{% data reusables.gated-features.codespaces %}' children: - - /understanding-billing-for-codespaces + - /understanding-billing-for-github-codespaces - /allowing-your-codespace-to-access-a-private-image-registry - - /using-github-copilot-in-codespaces + - /using-github-copilot-in-github-codespaces - /using-the-vs-code-command-palette-in-codespaces - - /security-in-codespaces - - /disaster-recovery-for-codespaces + - /security-in-github-codespaces + - /disaster-recovery-for-github-codespaces --- diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md similarity index 88% rename from translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md rename to translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md index 8523e1bb86..29dd25e8ae 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md @@ -1,6 +1,6 @@ --- -title: Security in Codespaces -intro: 'Overview of the {% data variables.product.prodname_codespaces %} security architecture, with guidelines to help you maintain security and minimize the risk of attack.' +title: Security in GitHub Codespaces +intro: 'Overview of the {% data variables.product.prodname_github_codespaces %} security architecture, with guidelines to help you maintain security and minimize the risk of attack.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -10,17 +10,19 @@ topics: - Security type: reference shortTitle: Security in Codespaces +redirect_from: + - /codespaces/codespaces-reference/security-in-codespaces --- ## Overview of codespace security -{% data variables.product.prodname_codespaces %} is designed to be security hardened by default. Consequently, you will need to ensure that your software development practices do not risk reducing the security posture of your codespace. +{% data variables.product.prodname_github_codespaces %} is designed to be security hardened by default. Consequently, you will need to ensure that your software development practices do not risk reducing the security posture of your codespace. This guide describes the way Codespaces keeps your development environment secure and provides some of the good practices that will help maintain your security as you work. As with any development tool, remember that you should only open and work within repositories you know and trust. ### Environment isolation -{% data variables.product.prodname_codespaces %} is designed to keep your codespaces separate from each other, with each using its own virtual machine and network. +{% data variables.product.prodname_github_codespaces %} is designed to keep your codespaces separate from each other, with each using its own virtual machine and network. #### Isolated virtual machines @@ -48,7 +50,7 @@ An organization's administrators specify which repositories should be considered ### Codespace connections -You can connect to your codespace using the TLS encrypted tunnel provided by the {% data variables.product.prodname_codespaces %} service. Only the creator of a codespace can connect to a codespace. Connections are authenticated with {% data variables.product.product_name %}. +You can connect to your codespace using the TLS encrypted tunnel provided by the {% data variables.product.prodname_github_codespaces %} service. Only the creator of a codespace can connect to a codespace. Connections are authenticated with {% data variables.product.product_name %}. If you need to allow external access to services running on a codespace, you can enable port forwarding for private or public access. @@ -87,7 +89,7 @@ Secrets are not copied into the environment if you don't have write access to th For more information on secrets, see: - 「[codespacesのための暗号化されたシークレットの管理](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」 -- "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)" ### Working with other people's contributions and repositories diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md similarity index 56% rename from translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md rename to translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md index a7d9621acb..116f80f6de 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md @@ -1,6 +1,6 @@ --- -title: Understanding billing for Codespaces -intro: 'Learn how your {% data variables.product.prodname_codespaces %} usage is billed.' +title: Understanding billing for GitHub Codespaces +intro: 'Learn how your {% data variables.product.prodname_github_codespaces %} usage is billed.' versions: fpt: '*' ghec: '*' @@ -8,6 +8,7 @@ redirect_from: - /github/developing-online-with-codespaces/about-billing-for-codespaces - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces - /codespaces/codespaces-reference/about-billing-for-codespaces + - /codespaces/codespaces-reference/understanding-billing-for-codespaces type: reference topics: - Codespaces @@ -18,9 +19,9 @@ shortTitle: Understanding billing This article explains how billing works for your codespaces, and explains how your organization's billing manager can help. -## Getting access to {% data variables.product.prodname_codespaces %} +## Getting access to {% data variables.product.prodname_github_codespaces %} -Your organization's administrator might limit {% data variables.product.prodname_codespaces %} usage to only specific personal accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access and security for your codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)." +Your organization's administrator might limit {% data variables.product.prodname_github_codespaces %} usage to only specific personal accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access and security for your codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)." ## How much it costs to use {% data variables.product.prodname_codespaces %} @@ -30,24 +31,24 @@ To see the pricing for {% data variables.product.prodname_codespaces %} usage, s Your codespace is billed for its compute minutes and for the amount of storage it uses on disk. -If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." +If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." ### Understanding what compute minutes are Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again. ### Understanding how codespace storage is billed -For {% data variables.product.prodname_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces. +For {% data variables.product.prodname_github_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces. ## How spending limits work -Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)." ## 利用上限に達した際の変更のエクスポート {% data reusables.codespaces.exporting-changes %} ## Checking your current usage and limits -If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your Codespaces usage](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +If you need to check your current usage or spending limit, contact your organization's billing manager. 詳しい情報については「[{% data variables.product.prodname_github_codespaces %}の利用状況の表示](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)」を参照してください。 ## Codespaces can be automatically deleted @@ -59,4 +60,4 @@ You can manually delete your codespaces in https://github.com/codespaces and fro ## 参考リンク -- 「[Organization内のCodespacesの支払いの管理](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)」 +- 「[Organization の {% data variables.product.prodname_github_codespaces %} の支払い管理](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)」 diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md deleted file mode 100644 index 25bcca0b2b..0000000000 --- a/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Using GitHub Copilot in Codespaces -intro: You can use Copilot in Codespaces by adding the extension. -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Codespaces - - Copilot - - Visual Studio Code -product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Copilot in Codespaces -redirect_from: - - /codespaces/codespaces-reference/using-copilot-in-codespaces ---- - -## {% data variables.product.prodname_copilot %}を使用する - -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). - -To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)」を参照してください。 Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." - diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md new file mode 100644 index 0000000000..73f9b81acd --- /dev/null +++ b/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md @@ -0,0 +1,24 @@ +--- +title: Using GitHub Copilot in GitHub Codespaces +intro: 'You can use Copilot in {% data variables.product.prodname_github_codespaces %} by adding the extension.' +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Codespaces + - Copilot + - Visual Studio Code +product: '{% data reusables.gated-features.codespaces %}' +shortTitle: Copilot in Codespaces +redirect_from: + - /codespaces/codespaces-reference/using-copilot-in-codespaces + - /codespaces/codespaces-reference/using-github-copilot-in-codespaces +--- + +## {% data variables.product.prodname_copilot %}を使用する + +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_github_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). + +To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." + diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index 297bcfdf10..fe5c5af7c4 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -1,6 +1,6 @@ --- -title: Using the Visual Studio Code Command Palette in Codespaces -intro: '{% data variables.product.prodname_vscode %} のコマンドパレット機能を使用して、Codespaces 内の多くのコマンドにアクセスできます。' +title: Using the Visual Studio Code Command Palette in GitHub Codespaces +intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in {% data variables.product.prodname_github_codespaces %}.' versions: fpt: '*' ghec: '*' @@ -17,7 +17,7 @@ redirect_from: ## {% data variables.product.prodname_vscode_command_palette %} について -コマンドパレットは、Codespaces で使用できる {% data variables.product.prodname_vscode %} の中心的な機能の1つです。 The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +The Command Palette is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in {% data variables.product.prodname_github_codespaces %}. The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %} @@ -31,9 +31,9 @@ You can access the {% data variables.product.prodname_vscode_command_palette_sho ![アプリケーションメニュー](/assets/images/help/codespaces/codespaces-view-menu.png) -## {% data variables.product.prodname_github_codespaces %} のコマンド +## {% data variables.product.prodname_codespaces %} のコマンド -To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces". +To see all commands related to {% data variables.product.prodname_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces". ![Codespaces に関連するすべてのコマンドのリスト](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -63,6 +63,6 @@ To rebuild your container, [access the {% data variables.product.prodname_vscode You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs. -To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". [**Codespaces: Export Logs**] を選択して Codespaces に関連するすべてのログをエクスポートするか、[**Codespaces: View Creation Logs**] を選択して設定に関連するログを表示します。 +To retrieve the logs for {% data variables.product.prodname_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup. ![ログにアクセスするコマンド](/assets/images/help/codespaces/codespaces-logs.png) 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 b4929a3fc4..1a52335ed8 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 @@ -17,7 +17,7 @@ type: how_to {% note %} -**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_codespaces %} and are creating a codespace on a repository owned by that organization. +**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_github_codespaces %} and are creating a codespace on a repository owned by that organization. {% endnote %} diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md index e79a0ab94d..5d5c045665 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md @@ -13,7 +13,7 @@ type: how_to By default, {% data variables.product.prodname_codespaces %} are automatically deleted after they have been stopped and have remained inactive for 30 days. -However, because {% data variables.product.prodname_codespaces %} incur storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +However, because {% data variables.product.prodname_codespaces %} incur storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." {% note %} @@ -50,7 +50,7 @@ Each codespace has its own retention period. You may, therefore, have codespaces {% warning %} - **Warning**: Setting the period to `0` will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." + **Warning**: Setting the period to `0` will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." {% endwarning %} diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md index 150f5293ca..449eca6d71 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md @@ -1,6 +1,6 @@ --- title: Customizing your codespace -intro: '{% data variables.product.prodname_codespaces %} は自分専用の環境に整えることができます。 You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.' +intro: '{% data variables.product.prodname_github_codespaces %} は自分専用の環境に整えることができます。 You can configure your repositories with a dev container to define their default {% data variables.product.prodname_github_codespaces %} environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,11 +10,11 @@ redirect_from: topics: - Codespaces children: - - /personalizing-codespaces-for-your-account + - /personalizing-github-codespaces-for-your-account - /changing-the-machine-type-for-your-codespace - - /setting-your-default-editor-for-codespaces - - /setting-your-default-region-for-codespaces - - /setting-your-timeout-period-for-codespaces + - /setting-your-default-editor-for-github-codespaces + - /setting-your-default-region-for-github-codespaces + - /setting-your-timeout-period-for-github-codespaces - /configuring-automatic-deletion-of-your-codespaces --- diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md similarity index 85% rename from translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md rename to translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md index e8f16c2e6e..77bd7be249 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md @@ -1,11 +1,12 @@ --- -title: Personalizing Codespaces for your account +title: Personalizing GitHub Codespaces for your account shortTitle: Personalize your codespaces -intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' +intro: 'You can personalize {% data variables.product.prodname_github_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' redirect_from: - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account + - /codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account versions: fpt: '*' ghec: '*' @@ -93,11 +94,11 @@ If your codespace fails to pick up configuration settings from dotfiles, see "[T You can also personalize {% data variables.product.prodname_codespaces %} using additional [{% data variables.product.prodname_codespaces %} settings](https://github.com/settings/codespaces): -- To set your default region, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." -- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)." -- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." -- To allow your codespaces to access other repositories, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." +- To set your default region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)." +- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." +- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)." +- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)." +- To allow your codespaces to access other repositories, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)." ## Further reading diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md similarity index 93% rename from translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md rename to translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md index 1b923f6296..04d2d4b449 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Setting your default editor for Codespaces +title: Setting your default editor for GitHub Codespaces shortTitle: Set the default editor intro: 'You can set your default editor for {% data variables.product.prodname_codespaces %} in your personal settings page.' product: '{% data reusables.gated-features.codespaces %}' @@ -8,6 +8,7 @@ versions: ghec: '*' redirect_from: - /codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces + - /codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces topics: - Codespaces type: how_to diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md similarity index 87% rename from translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md rename to translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md index 276fd62b72..1e19cfab8b 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Setting your default region for Codespaces +title: Setting your default region for GitHub Codespaces shortTitle: Set the default region intro: 'You can set your default region in the {% data variables.product.prodname_github_codespaces %} profile settings page to personalize where your data is held.' product: '{% data reusables.gated-features.codespaces %}' @@ -8,6 +8,7 @@ versions: ghec: '*' redirect_from: - /codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces + - /codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces topics: - Codespaces type: how_to diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md similarity index 86% rename from translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md rename to translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md index fe74848057..6def40c9fe 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Setting your timeout period for Codespaces +title: Setting your timeout period for GitHub Codespaces shortTitle: Set the timeout intro: 'You can set your default timeout for {% data variables.product.prodname_codespaces %} in your personal settings page.' product: '{% data reusables.gated-features.codespaces %}' @@ -9,6 +9,8 @@ versions: topics: - Codespaces type: how_to +redirect_from: + - /codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces --- A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace. @@ -17,7 +19,7 @@ Some organizations may have a maximum idle timeout policy. If an organization po {% warning %} -**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. 詳しい情報については、「[{% data variables.product.prodname_github_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)」を参照してください。 {% endwarning %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md index 4e93dbceb1..73fc5e0630 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md @@ -35,7 +35,7 @@ If you have unsaved changes, your editor will prompt you to save them before exi ## Codespaces timeouts -If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)." +If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)." When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)." diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md index 8c37404960..cb14f04c2e 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md @@ -1,6 +1,6 @@ --- title: Connecting to a private network -intro: 'You can connect {% data variables.product.prodname_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.' +intro: 'You can connect {% data variables.product.prodname_github_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -42,4 +42,4 @@ For more information about the Meta API, see "[Meta](/rest/reference/meta)." At present, there is no way to restrict codespaces from accessing the public internet, or to restrict appropriately authenticated users from accessing a forwarded port. -For more information on how to secure your codespaces, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces)." +For more information on how to secure your codespaces, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces)." 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 cddb002a8b..fd11485d2a 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 @@ -43,11 +43,11 @@ If you want to use Git hooks for your codespace, then you should set up hooks us {% data reusables.codespaces.prebuilds-crossreference %} -## Access to {% data variables.product.prodname_codespaces %} +## Access to {% data variables.product.prodname_github_codespaces %} {% data reusables.codespaces.availability %} -When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository. +When you have access to {% data variables.product.prodname_github_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository. You'll have access to codespaces under the following conditions: @@ -65,7 +65,7 @@ Organization owners can allow all members of the organization to create codespac Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)." -If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. +If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_github_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. ## codespace を作成する 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 2f68961c34..0dbfcc71be 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 @@ -19,9 +19,9 @@ shortTitle: Develop in a codespace -## About development with {% data variables.product.prodname_codespaces %} +## About development with {% data variables.product.prodname_github_codespaces %} -{% data variables.product.prodname_codespaces %} は、{% data variables.product.prodname_vscode %} の完全な開発体験を提供します。 {% data reusables.codespaces.use-visual-studio-features %} +{% data variables.product.prodname_github_codespaces %} は、{% data variables.product.prodname_vscode %} の完全な開発体験を提供します。 {% data reusables.codespaces.use-visual-studio-features %} {% data reusables.codespaces.links-to-get-started %} @@ -41,7 +41,7 @@ shortTitle: Develop in a codespace ### Codespace をパーソナライズする -{% data reusables.codespaces.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)」を参照してください。 +{% data reusables.codespaces.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_github_codespaces %} をパーソナライズする](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)」を参照してください。 {% data reusables.codespaces.apply-devcontainer-changes %}詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)」を参照してください。 diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 7315eca255..848f80f6b1 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: ポートの転送 ポート転送を使用すると、Codespaces 内で実行されている TCP ポートにアクセスできます。 For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging. -When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_codespaces %} in the browser or in {% data variables.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP. +When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_github_codespaces %} in the browser or in {% data variables.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP. ![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) @@ -150,7 +150,7 @@ You can label a port to make the port more easily identifiable in a list. ## Adding a port to the codespace configuration -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-configuration-changes-to-a-codespace)」を参照してください。 +You can add a forwarded port to the {% data variables.product.prodname_github_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-configuration-changes-to-a-codespace)」を参照してください。 `forwardPorts` プロパティで `.devcontainer.json` ファイルで転送ポートを手動で設定するか、codespace の [Ports] パネルを使用できます。 diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md index 1754cc0c90..2d822f6961 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md @@ -12,12 +12,12 @@ children: - /creating-a-codespace - /developing-in-a-codespace - /using-source-control-in-your-codespace - - /using-codespaces-for-pull-requests + - /using-github-codespaces-for-pull-requests - /deleting-a-codespace - /forwarding-ports-in-your-codespace - /default-environment-variables-for-your-codespace - /connecting-to-a-private-network - - /using-codespaces-in-visual-studio-code - - /using-codespaces-with-github-cli + - /using-github-codespaces-in-visual-studio-code + - /using-github-codespaces-with-github-cli --- diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md similarity index 81% rename from translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md rename to translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md index 3649aca318..9b94956da9 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md @@ -1,7 +1,7 @@ --- -title: Using Codespaces for pull requests +title: Using GitHub Codespaces for pull requests shortTitle: プルリクエスト -intro: 'You can use {% data variables.product.prodname_codespaces %} in your development workflow to create pull requests, review pull requests, and address review comments.' +intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your development workflow to create pull requests, review pull requests, and address review comments.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -11,11 +11,13 @@ topics: - Codespaces - Visual Studio Code - Developer +redirect_from: + - /codespaces/developing-in-codespaces/using-codespaces-for-pull-requests --- -## {% data variables.product.prodname_codespaces %} のプルリクエストについて +## {% data variables.product.prodname_github_codespaces %} のプルリクエストについて -{% data variables.product.prodname_codespaces %} provides you with many of the capabilities you might need to work with pull requests: +{% data variables.product.prodname_github_codespaces %} provides you with many of the capabilities you might need to work with pull requests: - [Create a pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Using either the Terminal and Git commands or the Source Control view, you can create pull requests just as you would on {% data variables.product.prodname_dotcom_the_website %}. If the repository uses a pull request template, you'll be able to use this within the Source Control view. - [Open a pull request](#opening-a-pull-request-in-codespaces) – You can open an existing pull request in a codespace, provided you have codespace access to the branch that is being merged in. diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md similarity index 81% rename from translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md rename to translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md index 3b81563de2..ede81ee663 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md @@ -1,11 +1,12 @@ --- -title: Using Codespaces in Visual Studio Code +title: Using GitHub Codespaces in Visual Studio Code intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio + - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code versions: fpt: '*' ghec: '*' @@ -18,19 +19,19 @@ shortTitle: Visual Studio Code --- -## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} +## About {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %} -You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." -By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." -If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync)." ## Prerequisites -To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. +To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. -Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% mac %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md similarity index 86% rename from translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md rename to translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md index af6afb971b..350d80c98d 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md @@ -1,5 +1,5 @@ --- -title: Using Codespaces with GitHub CLI +title: Using GitHub Codespaces with GitHub CLI shortTitle: GitHub CLI intro: 'You can work with {% data variables.product.prodname_github_codespaces %} directly from your command line by using `gh`, the {% data variables.product.product_name %} command line interface.' product: '{% data reusables.gated-features.codespaces %}' @@ -11,6 +11,8 @@ topics: - Codespaces - CLI - Developer +redirect_from: + - /codespaces/developing-in-codespaces/using-codespaces-with-github-cli --- ## {% data variables.product.prodname_cli %} について @@ -18,16 +20,16 @@ topics: {% data reusables.cli.about-cli %} 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。 You can work with {% data variables.product.prodname_codespaces %} in the {% data variables.product.prodname_cli %} to: -- [List your codespaces](#list-all-of-your-codespaces) -- [Create a codespace](#create-a-new-codespace) -- [Stop a codespace](#stop-a-codespace) -- [Delete a codespace](#delete-a-codespace) -- [SSH into a codespace](#ssh-into-a-codespace) -- [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) -- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) -- [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace) -- [Modify ports in a codespace](#modify-ports-in-a-codespace) -- [Access codespace logs](#access-codespace-logs) + - [List all of your codespaces](#list-all-of-your-codespaces) + - [Create a new codespace](#create-a-new-codespace) + - [Stop a codespace](#stop-a-codespace) + - [Delete a codespace](#delete-a-codespace) + - [SSH into a codespace](#ssh-into-a-codespace) + - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in--data-variablesproductprodname_vscode-) + - [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) + - [Copy a file to/from a codespace](#copy-a-file-tofrom-a-codespace) + - [Modify ports in a codespace](#modify-ports-in-a-codespace) + - [Access codespace logs](#access-codespace-logs) ## {% data variables.product.prodname_cli %}のインストール @@ -80,7 +82,7 @@ gh codespace create -r owner/repository [-b branch] gh codespace stop -c codespace-name ``` -For more information, see "[Deep dive into Codespaces](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)." +For more information, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)." ### Delete a codespace @@ -190,4 +192,4 @@ You can see the creation log for a codespace. After entering this command you wi gh codespace logs -c codespace-name ``` -For more information about the creation log, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs#creation-logs)." +For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)." diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 161e505d05..6abaafe4d8 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -15,7 +15,7 @@ shortTitle: ソースコントロール -## {% data variables.product.prodname_codespaces %} のソースコントロールについて +## {% data variables.product.prodname_github_codespaces %} のソースコントロールについて 必要なすべての Git アクションを codespace 内で直接実行できます。 たとえば、リモートリポジトリから変更をフェッチしたり、ブランチを切り替えたり、新しいブランチを作成したり、変更をコミットしてプッシュしたり、プルリクエストを作成したりすることができます。 Codespace 内の統合ターミナルを使用して Git コマンドを入力するか、アイコンとメニューオプションをクリックして最も一般的な Git タスクをすべて完了することができます。 このガイドでは、ソースコントロールにグラフィカルユーザインターフェースを使用する方法について説明します。 diff --git a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md index 875c41abac..f1696544d8 100644 --- a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md +++ b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md @@ -1,6 +1,7 @@ --- -title: Deep dive into Codespaces -intro: '{% data variables.product.prodname_codespaces %} のしくみを知る.' +title: 'Deep dive into {% data variables.product.prodname_github_codespaces %}' +shortTitle: 'Deep dive into {% data variables.product.prodname_codespaces %}' +intro: '{% data variables.product.prodname_github_codespaces %} のしくみを知る.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -11,7 +12,7 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. +{% data variables.product.prodname_github_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. ## codespace を作成する @@ -54,7 +55,7 @@ Once you are connected to your codespace, your automated setup may continue to b If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. -If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)」を参照してください。 +If you have a public dotfiles repository for {% data variables.product.prodname_github_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. 詳しい情報については、「[アカウントの {% data variables.product.prodname_github_codespaces %} をパーソナライズする](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles)」を参照してください。 Finally, the entire history of the repository is copied down with a full clone. @@ -97,7 +98,7 @@ Git is available by default in your codespace and so you can rely on your existi ![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) -You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. リポジトリごと、さらにはブランチごとに1つ以上のcodespaceを作成できます。 However, each personal account has a limit of 10 codespaces. この制限に達した場合に新しいcodespaceを作成したいなら、まずcodespaceを削除しなければなりません。 +You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_github_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. リポジトリごと、さらにはブランチごとに1つ以上のcodespaceを作成できます。 However, each personal account has a limit of 10 codespaces. この制限に達した場合に新しいcodespaceを作成したいなら、まずcodespaceを削除しなければなりません。 {% note %} diff --git a/translations/ja-JP/content/codespaces/getting-started/index.md b/translations/ja-JP/content/codespaces/getting-started/index.md index bca01bcd3c..6ea0df0a1b 100644 --- a/translations/ja-JP/content/codespaces/getting-started/index.md +++ b/translations/ja-JP/content/codespaces/getting-started/index.md @@ -1,6 +1,7 @@ --- -title: '{% data variables.product.prodname_codespaces %} を使ってみる' -intro: '特定の言語のセットアップや構成など、{% data variables.product.prodname_codespaces %} の使用方法を学びます。' +title: '{% data variables.product.prodname_github_codespaces %}を使い始める' +shortTitle: はじめましょう +intro: '特定の言語のセットアップや構成など、{% data variables.product.prodname_github_codespaces %} の使用方法を学びます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' diff --git a/translations/ja-JP/content/codespaces/getting-started/quickstart.md b/translations/ja-JP/content/codespaces/getting-started/quickstart.md index 05fd14d9ef..1a22692624 100644 --- a/translations/ja-JP/content/codespaces/getting-started/quickstart.md +++ b/translations/ja-JP/content/codespaces/getting-started/quickstart.md @@ -1,6 +1,7 @@ --- -title: Quickstart for Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes.' +title: 'Quickstart for {% data variables.product.prodname_github_codespaces %}' +shortTitle: 'Quickstart for {% data variables.product.prodname_codespaces %}' +intro: 'Try out {% data variables.product.prodname_github_codespaces %} in 5 minutes.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -19,7 +20,7 @@ In this guide, you'll create a codespace from a [template repository](https://gi From this quickstart, you will learn how to create a codespace, connect to a forwarded port to view your running application, use version control in a codespace, and personalize your setup with extensions. -For more information on exactly how {% data variables.product.prodname_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/deep-dive)." +For more information on exactly how {% data variables.product.prodname_github_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)." ## codespace を作成する diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md similarity index 87% rename from translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md rename to translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md index 642bbe5d0c..db2f279779 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md @@ -1,11 +1,12 @@ --- -title: Organization の Codespaces を有効にする +title: Enabling GitHub Codespaces for your organization shortTitle: Enable Codespaces -intro: 'Organization 内のどのユーザが {% data variables.product.prodname_codespaces %} を使用できるかを制御できます。' +intro: 'Organization 内のどのユーザが {% data variables.product.prodname_github_codespaces %} を使用できるかを制御できます。' product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' +permissions: 'To manage user permissions for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.' redirect_from: - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization + - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization versions: fpt: '*' ghec: '*' @@ -17,14 +18,14 @@ topics: --- -## About enabling {% data variables.product.prodname_codespaces %} for your organization +## About enabling {% data variables.product.prodname_github_codespaces %} for your organization Organization のオーナーは、Organization 内のどのユーザが Codespaces を作成および使用できるかを制御できます。 To use codespaces in your organization, you must do the following: - Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. -- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#enable-codespaces-for-users-in-your-organization). You can choose to allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users. +- [Enable {% data variables.product.prodname_github_codespaces %} for users in your organization](#enable-codespaces-for-users-in-your-organization). You can choose to allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users. - [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) - Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md index 85424ae66f..9686141edc 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -1,5 +1,6 @@ --- title: Organization の Codespaces を管理する +shortTitle: Managing your organization intro: 'Organization 内のユーザの {% data variables.product.prodname_github_codespaces %} の使用方法について管理および確認できます。' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -8,15 +9,14 @@ versions: topics: - Codespaces children: - - /enabling-codespaces-for-your-organization - - /managing-billing-for-codespaces-in-your-organization - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces + - /enabling-github-codespaces-for-your-organization + - /managing-billing-for-github-codespaces-in-your-organization + - /managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces - /managing-repository-access-for-your-organizations-codespaces - - /reviewing-your-organizations-audit-logs-for-codespaces + - /reviewing-your-organizations-audit-logs-for-github-codespaces - /restricting-access-to-machine-types - /restricting-the-visibility-of-forwarded-ports - /restricting-the-idle-timeout-period - /restricting-the-retention-period-for-codespaces -shortTitle: Managing your organization --- diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md similarity index 74% rename from translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md rename to translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md index f9cd3847c3..ca50b3f071 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md @@ -1,9 +1,9 @@ --- -title: Managing billing for Codespaces in your organization +title: Managing billing for GitHub Codespaces in your organization shortTitle: Manage billing -intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.' +intro: 'You can check your {% data variables.product.prodname_github_codespaces %} usage and set usage limits.' product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' +permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.' versions: fpt: '*' ghec: '*' @@ -11,11 +11,13 @@ type: reference topics: - Codespaces - Billing +redirect_from: + - /codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization --- ## 概要 -To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +To learn about pricing for {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." {% data reusables.codespaces.codespaces-billing %} @@ -25,11 +27,11 @@ To learn about pricing for {% data variables.product.prodname_codespaces %}, see ## 使用制限 -You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}: +You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_github_codespaces %}: -- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)." -- **Storage usage:** For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +- **Storage usage:** For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage"](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)." ## Disabling or limiting {% data variables.product.prodname_codespaces %} diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md similarity index 86% rename from translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md rename to translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md index 5b46656b64..ef9ad3f847 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md @@ -1,9 +1,9 @@ --- -title: リポジトリの暗号化されたシークレットと Codespaces の Organization を管理する +title: Managing encrypted secrets for your repository and organization for GitHub Codespaces shortTitle: 暗号化されたシークレット -intro: '暗号化されたシークレットを使用すると、機密情報を Organization、リポジトリ、または {% data variables.product.prodname_codespaces %} に保存できます。' +intro: '暗号化されたシークレットを使用すると、機密情報を Organization、リポジトリ、または {% data variables.product.prodname_github_codespaces %} に保存できます。' product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' +permissions: 'To manage secrets for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.' versions: fpt: '*' ghec: '*' @@ -11,13 +11,15 @@ topics: - Codespaces - Secret store - Security +redirect_from: + - /codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces --- ## シークレットについて -シークレットは、Organization またはリポジトリで作成する暗号化された環境変数です。 作成したシークレットは、{% data variables.product.prodname_codespaces %} で使用できます。 GitHub は [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用して、シークレットが GitHub に到達する前に暗号化し、codespace で使用する場合にのみ復号化します。 +シークレットは、Organization またはリポジトリで作成する暗号化された環境変数です。 作成したシークレットは、{% data variables.product.prodname_github_codespaces %} で使用できます。 GitHub は [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用して、シークレットが GitHub に到達する前に暗号化し、codespace で使用する場合にのみ復号化します。 Organization レベルのシークレットを使用すると、複数のリポジトリ間でシークレットを共有できるため、重複するシークレットを作成する必要が軽減されます。 アクセスポリシーを使用して、Organization のシークレットを使用できるリポジトリを制御できます。 diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index a3693b0f7a..eb3b108b14 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -1,9 +1,9 @@ --- title: Managing repository access for your organization's codespaces shortTitle: Repository access -intro: '{% data variables.product.prodname_codespaces %} がアクセスできる Organization 内のリポジトリを管理できます。' +intro: '{% data variables.product.prodname_github_codespaces %} がアクセスできる Organization 内のリポジトリを管理できます。' product: '{% data reusables.gated-features.codespaces %}' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' +permissions: 'To manage access and security for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.' versions: fpt: '*' ghec: '*' @@ -26,7 +26,7 @@ redirect_from: デフォルト設定では、Codespace は作成されたリポジトリにのみアクセスできます。 When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. 信頼するリポジトリに対してのみ、アクセスとセキュリティを有効にしてください。 -Organization 内のどのユーザが {% data variables.product.prodname_codespaces %} を使用できるかを管理するには、「[Organization のユーザ権限を管理する](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)」を参照してください。 +Organization 内のどのユーザが {% data variables.product.prodname_github_codespaces %} を使用できるかを管理するには、「[Organization のユーザ権限を管理する](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)」を参照してください。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md index 061242b1d6..415f43e055 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md @@ -14,7 +14,7 @@ topics: ## 概要 -Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." +Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization. @@ -76,4 +76,4 @@ You can edit an existing policy. For example, you may want to add or remove cons ## 参考リンク -- "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)" +- "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md index 90e86b0df5..fc28f2cf6e 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -16,7 +16,7 @@ topics: By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. -The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." +The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces created for repositories owned by your organization. This can help you to limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for the codespaces for all repositories owned by your organization, or for the codespaces of specific repositories. @@ -26,7 +26,7 @@ As an organization owner, you may want to configure constraints on the maximum i {% endnote %} -For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." ### Behavior when you set a maximum idle timeout constraint diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md index d3fdd471c6..06d0b8f5e8 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md @@ -18,7 +18,7 @@ topics: Everyone who has access to {% data variables.product.prodname_github_codespaces %} can configure a retention period for the codespaces they create. The initial setting for this default retention period is 30 days. Individual users can set this period within the range 0-30 days. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)." -As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." You can set a maximum retention period for all, or for specific, repositories owned by your organization. +As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." You can set a maximum retention period for all, or for specific, repositories owned by your organization. ### Setting organization-wide and repository-specific policies diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md similarity index 54% rename from translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md rename to translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md index c5c50811b3..055b356f42 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md @@ -1,7 +1,7 @@ --- -title: Organization の Codespaces の Audit log を確認する +title: Reviewing your organization's audit logs for GitHub Codespaces shortTitle: 監査ログ -intro: 'Audit log を使用して、{% data variables.product.prodname_codespaces %} に関連するすべてのアクションを確認できます。' +intro: 'Audit log を使用して、{% data variables.product.prodname_github_codespaces %} に関連するすべてのアクションを確認できます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -11,11 +11,13 @@ topics: - Codespaces - Security - Administrator +redirect_from: + - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces --- -Organization のメンバーが {% data variables.product.prodname_codespaces %} に関連するアクションを実行すると、Audit log でアクションを確認できます。 ログへのアクセスについては、「[Audit log を確認する](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)」を参照してください。 +Organization のメンバーが {% data variables.product.prodname_github_codespaces %} に関連するアクションを実行すると、Audit log でアクションを確認できます。 ログへのアクセスについては、「[Audit log を確認する](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)」を参照してください。 ![Codespaces 情報を含む Audit log](/assets/images/help/settings/codespaces-audit-log-org.png) @@ -23,4 +25,4 @@ The audit log includes details such as who performed the action, what the action ## 参考リンク -- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" +- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md index f29c8486a7..d4ee059039 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md @@ -12,7 +12,7 @@ redirect_from: children: - /managing-encrypted-secrets-for-your-codespaces - /managing-repository-access-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces + - /reviewing-your-security-logs-for-github-codespaces + - /managing-gpg-verification-for-github-codespaces --- diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 73424ab112..d38b858d2c 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -20,7 +20,7 @@ shortTitle: 暗号化されたシークレット -## {% data variables.product.prodname_codespaces %} の暗号化されたシークレットについて +## About encrypted secrets for {% data variables.product.prodname_github_codespaces %} You can add encrypted secrets to your personal account that you want to use in your codespaces. たとえば、次のような機密情報を暗号化されたシークレットとして保存しアクセスするとよいでしょう。 @@ -41,7 +41,7 @@ You can add encrypted secrets to your personal account that you want to use in y ### シークレットの制限 -{% data variables.product.prodname_codespaces %} には最大 100 個のシークレットを保存できます。 +You can store up to 100 secrets for {% data variables.product.prodname_github_codespaces %}. シークレットの容量は最大64 KBです。 @@ -77,4 +77,4 @@ You can add encrypted secrets to your personal account that you want to use in y ## 参考リンク -- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md similarity index 65% rename from translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md rename to translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md index 2af48e96ad..992180c629 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Codespaces の GPG 検証を管理する +title: Managing GPG verification for GitHub Codespaces intro: '変更が信頼できるソースからのものであることを他の人々が確信できるよう、コードスペースで作成したコミットに GPG を自動的に使用して署名するよう {% data variables.product.company_short %} に許可できます。' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -13,12 +13,13 @@ topics: redirect_from: - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces + - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces shortTitle: GPG 検証 --- -GPG 検証を有効にすると、{% data variables.product.company_short %} は {% data variables.product.prodname_codespaces %} であなたが作成したコミットに自動的に署名し、そのコミットは {% data variables.product.product_name %} で検証済みのステータスとなります。 デフォルトでは、GPG 検証は作成されたコードスペースに対して無効になっています。 GPG 検証を、すべてのリポジトリに対して許可するか特定のリポジトリに対して許可するか選択できます。 GPG 検証は、信頼するリポジトリに対してのみ有効にしてください。 {% data variables.product.product_name %} が署名したコミットに関する詳しい情報については、「[コミット署名の検証について](/github/authenticating-to-github/about-commit-signature-verification)」を参照してください。 +GPG 検証を有効にすると、{% data variables.product.company_short %} は {% data variables.product.prodname_github_codespaces %} であなたが作成したコミットに自動的に署名し、そのコミットは {% data variables.product.product_name %} で検証済みのステータスとなります。 デフォルトでは、GPG 検証は作成されたコードスペースに対して無効になっています。 GPG 検証を、すべてのリポジトリに対して許可するか特定のリポジトリに対して許可するか選択できます。 GPG 検証は、信頼するリポジトリに対してのみ有効にしてください。 {% data variables.product.product_name %} が署名したコミットに関する詳しい情報については、「[コミット署名の検証について](/github/authenticating-to-github/about-commit-signature-verification)」を参照してください。 Once you enable GPG verification, it will immediately take effect for all your codespaces. diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index 3366306e7e..98255366e3 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -2,7 +2,7 @@ title: Managing access to other repositories within your codespace allowTitleToDifferFromFilename: true shortTitle: Repository access -intro: '{% data variables.product.prodname_codespaces %} がアクセスできるリポジトリを管理できます。' +intro: '{% data variables.product.prodname_github_codespaces %} がアクセスできるリポジトリを管理できます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -16,7 +16,7 @@ redirect_from: ## 概要 -By default, your codespace is assigned a token scoped to the repository from which it was created. For more information, see "[Security in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/security-in-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions. +By default, your codespace is assigned a token scoped to the repository from which it was created. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions. When permissions are listed in the `devcontainer.json` file, you will be prompted to review and authorize the additional permissions as part of codespace creation for that repository. Once you've authorized the listed permissions, {% data variables.product.prodname_github_codespaces %} will remember your choice and will not prompt you for authorization unless the permissions in the `devcontainer.json` file change. @@ -29,7 +29,7 @@ To create codespaces with custom permissions defined, you must use one of the fo ## Setting additional repository permissions -1. You configure repository permissions for {% data variables.product.prodname_github_codespaces %} in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. For more information, "[Add a dev container to your project](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." +1. You configure repository permissions for {% data variables.product.prodname_codespaces %} in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. For more information, "[Add a dev container to your project](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." 1. Edit the `devcontainer.json` file, adding the repository name and permissions needed to the `repositories` object: @@ -105,7 +105,7 @@ To create codespaces with custom permissions defined, you must use one of the fo ## Authorizing requested permissions -If additional repository permissions are defined in the `devcontainer.json` file, you will be prompted to review and optionally authorize the permissions when you create a codespace for this repository. When you authorize permissions for a repository, {% data variables.product.prodname_github_codespaces %} will not re-prompt you unless the set of requested permissions has changed for the repository. +If additional repository permissions are defined in the `devcontainer.json` file, you will be prompted to review and optionally authorize the permissions when you create a codespace for this repository. When you authorize permissions for a repository, {% data variables.product.prodname_codespaces %} will not re-prompt you unless the set of requested permissions has changed for the repository. ![The requested permissions page](/assets/images/help/codespaces/codespaces-accept-permissions.png) diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md similarity index 51% rename from translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md rename to translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md index f634dc36cd..c501c48163 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md @@ -1,7 +1,7 @@ --- -title: Codespaces のセキュリティログをレビューする +title: Reviewing your security logs for GitHub Codespaces shortTitle: Security logs -intro: 'セキュリティログを使用して、{% data variables.product.prodname_codespaces %} に関連するすべてのアクションをレビューできます。' +intro: 'セキュリティログを使用して、{% data variables.product.prodname_github_codespaces %} に関連するすべてのアクションをレビューできます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,13 +10,15 @@ topics: - Codespaces - Developer - Security +redirect_from: + - /codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces --- -## {% data variables.product.prodname_codespaces %} のセキュリティログについて +## {% data variables.product.prodname_github_codespaces %} のセキュリティログについて -When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your personal account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)." +When you perform an action related to {% data variables.product.prodname_github_codespaces %} in repositories owned by your personal account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)." ![Codespaces 情報を含むセキュリティログ](/assets/images/help/settings/codespaces-audit-log.png) @@ -24,4 +26,4 @@ When you perform an action related to {% data variables.product.prodname_codespa ## 参考リンク -- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)" diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md index a9057f7df9..7fcc96490b 100644 --- a/translations/ja-JP/content/codespaces/overview.md +++ b/translations/ja-JP/content/codespaces/overview.md @@ -2,7 +2,7 @@ title: GitHub Codespaces overview shortTitle: 概要 product: '{% data reusables.gated-features.codespaces %}' -intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.' +intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.' allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/about-codespaces @@ -20,19 +20,19 @@ topics: ## What is a codespace? -A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. +A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. -{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. ![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) -## Using Codespaces +## {% data variables.product.prodname_github_codespaces %}を使用する You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. {% data reusables.codespaces.links-to-get-started %} To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository. -If you don't add a dev container configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +If you don't add a dev container configuration, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md similarity index 91% rename from translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md rename to translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md index 30b9256840..22c8890df5 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md @@ -1,5 +1,5 @@ --- -title: About Codespaces prebuilds +title: About GitHub Codespaces prebuilds shortTitle: About prebuilds intro: Codespaces prebuilds help to speed up the creation of new codespaces for large or complex repositories. versions: @@ -8,13 +8,15 @@ versions: topics: - Codespaces product: '{% data reusables.gated-features.codespaces %}' +redirect_from: + - /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds --- ## 概要 Prebuilding your codespaces allows you to be more productive and access your codespace faster, particularly if your repository is large or complex and new codespaces currently take more than 2 minutes to start. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace. -By default, whenever you push changes to your repository, {% data variables.product.prodname_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. +By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. When prebuilds are available for a particular branch of a repository, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 @@ -28,7 +30,7 @@ When prebuilds are available for a particular branch of a repository, and for yo ## About billing for {% data variables.product.prodname_codespaces %} prebuilds -{% data reusables.codespaces.billing-for-prebuilds %} For details of {% data variables.product.prodname_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." +{% data reusables.codespaces.billing-for-prebuilds %} For details of {% data variables.product.prodname_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." Use of codespaces created using prebuilds is charged at the same rate as regular codespaces. diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index 1afb583732..f234e94605 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -17,14 +17,14 @@ You can set up a prebuild configuration for a specific branch of your repository Any branch created from a prebuild-enabled base branch will typically also get assigned a prebuild during codespace creation. This is true if the dev container on the branch is the same as on the base branch. This is because the majority of the prebuild configuration for branches with the same dev container configuration are identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." -Typically, when you configure prebuilds for a branch, prebuilds will be available for {% data variables.product.prodname_codespaces %} machine types for that branch. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. +Typically, when you configure prebuilds for a branch, prebuilds will be available for {% data variables.product.prodname_github_codespaces %} machine types for that branch. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. {% data reusables.codespaces.prebuilds-not-available %} ## Prerequisites Before you can configure prebuilds for your project the following must be true: -* {% data variables.product.prodname_github_codespaces %} must be enabled for your organization. For more information, see "[Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +* {% data variables.product.prodname_github_codespaces %} must be enabled for your organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." * {% data variables.product.prodname_actions %} must be enabled for your repository. Each prebuild configuration needs to be able to trigger an associated Actions workflow. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)." ## Configuring a prebuild @@ -61,14 +61,14 @@ Before you can configure prebuilds for your project the following must be true: {% note %} **Notes**: - * The prebuild template for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." - * Developers can set their default region for {% data variables.product.prodname_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces)." + * The prebuild template for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-github-codespaces-prebuilds)." + * Developers can set their default region for {% data variables.product.prodname_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)." {% endnote %} 1. Set the number of prebuild template versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest template version and the previous version are saved. - Depending on your prebuild trigger settings, your prebuild template could change with each push or on each dev container configuration change. Retaining older versions of prebuild templates enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild template. Since there is a storage cost associated with retaining prebuild template versions, you can choose the number of versions to be retained based on the needs of your team. For more information on billing, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." + Depending on your prebuild trigger settings, your prebuild template could change with each push or on each dev container configuration change. Retaining older versions of prebuild templates enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild template. Since there is a storage cost associated with retaining prebuild template versions, you can choose the number of versions to be retained based on the needs of your team. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." If you set the number of prebuild template versions to save to 1, {% data variables.product.prodname_codespaces %} will only save the latest version of the prebuild template and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration. diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md index d924342f20..b9f835e8b0 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md @@ -10,7 +10,7 @@ topics: redirect_from: - /codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project children: - - /about-codespaces-prebuilds + - /about-github-codespaces-prebuilds - /configuring-prebuilds - /managing-prebuilds - /testing-dev-container-changes diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index 2f6ee3da34..59e3ac8d04 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -14,7 +14,7 @@ miniTocMaxHeadingLevel: 3 ## Checking, changing, and deleting your prebuild configurations -The prebuilds that you configure for a repository are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_codespaces %} service. +The prebuilds that you configure for a repository are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_github_codespaces %} service. Depending on the settings in a prebuild configuration, the workflow to update the prebuild template may be triggered by these events: @@ -115,7 +115,7 @@ By default, the {% data variables.product.prodname_actions %} workflow for a pre {% endif %} 1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. 1. Sign back into the account that has admin access to the repository. -1. In the repository for which you want to create {% data variables.product.prodname_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)." +1. In the repository for which you want to create {% data variables.product.prodname_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)." The PAT will be used for all subsequent prebuild templates created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. 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 5b6dc3a370..f651e80d5e 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 @@ -1,7 +1,8 @@ --- -title: 'Setting up your repository for {% data variables.product.prodname_codespaces %}' +title: 'Setting up your repository for {% data variables.product.prodname_github_codespaces %}' +shortTitle: Setting up your repository allowTitleToDifferFromFilename: true -intro: '特定の言語のセットアップや構成など、{% data variables.product.prodname_codespaces %} の使用方法を学びます。' +intro: '特定の言語のセットアップや構成など、{% data variables.product.prodname_github_codespaces %} の使用方法を学びます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index 6a7e630c94..0ce9332868 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -53,7 +53,7 @@ For information about how to choose your preferred dev container configuration w It's useful to think of the `devcontainer.json` file as providing "customization" rather than "personalization." You should only include things that everyone working on your codebase needs as standard elements of the development environment, not things that are personal preferences. Things like linters are good to standardize on, and to require everyone to have installed, so they're good to include in your `devcontainer.json` file. Things like user interface decorators or themes are personal choices that should not be put in the `devcontainer.json` file. -You can personalize your codespaces by using dotfiles and Settings Sync. For more information, see "[Personalizing Codespaces for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account)." +You can personalize your codespaces by using dotfiles and Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)." ### Dockerfile 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 a35dc96b2f..da1c63a35d 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: Setting a minimum specification for codespace machines shortTitle: Set a minimum machine spec -intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.' +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: '*' @@ -15,7 +15,7 @@ product: '{% data reusables.gated-features.codespaces %}' ## 概要 -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 (CPUs, 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)." +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 (CPUs, memory, storage) and, by default, the machine type with the least resources is used. 詳しい情報については「[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. @@ -27,7 +27,7 @@ If your project needs a certain level of compute power, you can configure {% dat ## Setting a minimum machine specification -1. {% data variables.product.prodname_codespaces %} for your repository are configured in a `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container configuration to your repository](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." +1. {% data variables.product.prodname_github_codespaces %} for your repository are configured in a `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container configuration to your repository](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." 1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this: ```json{:copy} @@ -40,7 +40,7 @@ If your project needs a certain level of compute power, you can configure {% dat You can specify any or all of the options: `cpus`, `memory`, and `storage`. - To check the specifications of the {% data variables.product.prodname_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. 詳しい情報については、「[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. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 1. Save the file and commit your changes to the required branch of the repository. 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 7ec50726d1..f4e8cb4723 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 @@ -45,7 +45,7 @@ You can open any {% data variables.product.prodname_dotcom %} repository in the ## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} -Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_github_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. | | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/ja-JP/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/ja-JP/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index 5eb72a809c..b089fe2037 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -13,7 +13,7 @@ shortTitle: Exporting changes ## Exporting changes to a branch -While using {% data variables.product.prodname_codespaces %}, you may want to export your changes to a branch without launching your codespace. +While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. diff --git a/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md b/translations/ja-JP/content/codespaces/troubleshooting/github-codespaces-logs.md similarity index 95% rename from translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md rename to translations/ja-JP/content/codespaces/troubleshooting/github-codespaces-logs.md index cafbb21f10..90a6b34faf 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/github-codespaces-logs.md @@ -1,6 +1,6 @@ --- -title: Codespace のログ -intro: 'Overview of the logging locations used by {% data variables.product.prodname_codespaces %}.' +title: GitHub Codespaces logs +intro: 'Overview of the logging locations used by {% data variables.product.prodname_github_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,10 +10,12 @@ topics: - Codespaces - Logging shortTitle: Codespace のログ +redirect_from: + - /codespaces/troubleshooting/codespaces-logs --- -Information on {% data variables.product.prodname_codespaces %} is output to three different logs: +Information on {% data variables.product.prodname_github_codespaces %} is output to three different logs: - Codespace logs - Creation logs diff --git a/translations/ja-JP/content/codespaces/troubleshooting/index.md b/translations/ja-JP/content/codespaces/troubleshooting/index.md index 988b43f7bd..e744b4fda2 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/index.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/index.md @@ -2,7 +2,7 @@ title: Troubleshooting Codespaces shortTitle: トラブルシューティング product: '{% data reusables.gated-features.codespaces %}' -intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_codespaces %}' +intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_github_codespaces %}' versions: fpt: '*' ghec: '*' @@ -12,14 +12,14 @@ redirect_from: - /github/developing-online-with-codespaces/troubleshooting-your-codespace - /codespaces/working-with-your-codespace/troubleshooting-your-codespace children: - - /codespaces-logs + - /github-codespaces-logs - /exporting-changes-to-a-branch - /troubleshooting-creation-and-deletion-of-codespaces - - /troubleshooting-your-connection-to-codespaces + - /troubleshooting-your-connection-to-github-codespaces - /troubleshooting-prebuilds - /troubleshooting-dotfiles-for-codespaces - - /troubleshooting-port-forwarding-for-codespaces + - /troubleshooting-port-forwarding-for-github-codespaces - /troubleshooting-codespaces-clients - - /working-with-support-for-codespaces + - /working-with-support-for-github-codespaces --- diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index c1dbad82e7..4afe402686 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -14,7 +14,7 @@ shortTitle: Creation and deletion ## Creating codespaces ### No access to create a codespace -{% data variables.product.prodname_codespaces %} are not available for all repositories. If the "Open with Codespaces" button is missing, {% data variables.product.prodname_codespaces %} may not be available for that repository. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)」を参照してください。 +{% data variables.product.prodname_codespaces %} are not available for all repositories. If the "Open with Codespaces" button is missing, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)」を参照してください。 If you believe your organization has [enabled {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), make sure that an organization owner or billing manager has set the spending limit for {% data variables.product.prodname_codespaces %}. 詳しい情報については「[{% data variables.product.prodname_codespaces %}の利用上限の管理](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)」を参照してください。 @@ -23,7 +23,7 @@ If you believe your organization has [enabled {% data variables.product.prodname If you create a codespace and it does not open: 1. Try reloading the page in case there was a caching or reporting problem. -2. Go to your {% data variables.product.prodname_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page. +2. Go to your {% data variables.product.prodname_github_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page. 3. Retry creating the codespace for the repository to rule out a transient communication failure. If you still cannot create a codespace for a repository where {% data variables.product.prodname_codespaces %} are available, {% data reusables.codespaces.contact-support %} diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md similarity index 78% rename from translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md rename to translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md index d1c7b3610b..5b79fb4b53 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md @@ -1,5 +1,5 @@ --- -title: Troubleshooting port forwarding for Codespaces +title: Troubleshooting port forwarding for GitHub Codespaces intro: Troubleshooting steps for common port forwarding issues. product: '{% data reusables.gated-features.codespaces %}' versions: @@ -9,9 +9,11 @@ type: reference topics: - Codespaces shortTitle: Port forwarding +redirect_from: + - /codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces --- -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)." diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index c99a8face2..d798eabd12 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -24,7 +24,7 @@ If you have your {% data variables.product.prodname_codespaces %} editor prefere ![The 'prebuilt codespace found' message](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)." After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md similarity index 87% rename from translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md rename to translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md index 1452ca84b6..b1b17e697b 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting your connection to Codespaces -intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_codespaces %}.' +title: Troubleshooting your connection to GitHub Codespaces +intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_github_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -9,6 +9,8 @@ type: reference topics: - Codespaces shortTitle: コネクション +redirect_from: + - /codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces --- ## 503 codespace service unavailable @@ -35,7 +37,7 @@ If you cannot connect to a codespace from {% data variables.product.prodname_vsc 1. Check that you have the latest version of the {% data variables.product.prodname_github_codespaces %} extension installed. The extension is a preview release and frequent updates are released. 1. In {% data variables.product.prodname_vscode %}, display the "Extensions" tab. - 2. Select the {% data variables.product.prodname_github_codespaces %} extension to display the extension's overview page. + 2. Select the {% data variables.product.prodname_codespaces %} extension to display the extension's overview page. 3. If an update is available, a button is shown, click **Update to X.X.X** to upgrade to the latest version. 2. Check whether you are using the stable build of {% data variables.product.prodname_vscode %} or the [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) release (nightly updates). If you are using the insiders release, try installing the [stable build](https://code.visualstudio.com/). 3. Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device. @@ -44,4 +46,4 @@ If you still cannot connect, {% data reusables.codespaces.contact-support %} ### The codespace has latency issues -If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can [manually set your {% data variables.product.prodname_github_codespaces %} region](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). +If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can [manually set your {% data variables.product.prodname_codespaces %} region](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). diff --git a/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md similarity index 83% rename from translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md rename to translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md index 31b86e449d..5094075f8b 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md @@ -1,6 +1,6 @@ --- -title: Working with support for Codespaces -intro: 'Tips on getting the best help from support for {% data variables.product.prodname_codespaces %}.' +title: Working with support for GitHub Codespaces +intro: 'Tips on getting the best help from support for {% data variables.product.prodname_github_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -9,9 +9,11 @@ type: reference topics: - Codespaces shortTitle: Working with support +redirect_from: + - /codespaces/troubleshooting/working-with-support-for-codespaces --- -Before support can help you with problems with codespaces, you need to know the name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." +Before support can help you with problems with codespaces, you need to know the name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." ### Codespace names @@ -22,7 +24,7 @@ To find the name of a codespace: - Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-myrepo-gmc7.github.dev` is the URL for the `octocat-myrepo-gmc7` codespace. - If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces. ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) -The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)." +The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)." ### Codespaces IDs diff --git a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md index f2396974ba..6e1840d06d 100644 --- a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md +++ b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md @@ -23,8 +23,9 @@ If you use a JetBrains IDE, you can view and incorporate suggestions from {% dat To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ. -1. In your JetBrains IDE, under the **File** menu, click **Settings**. -1. At the top of the "Settings" dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}** and click **Install**. ![Screenshot of Marketplace search](/assets/images/help/copilot/jetbrains-marketplace.png) +1. In your JetBrains IDE, under the **File** menu for Windows or under the name of your IDE for Mac (for example, **PyCharm** or **IntelliJ**), click **Settings** for Windows or **Preferences** for Mac. +2. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**. +3. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**. ![Screenshot of Marketplace search](/assets/images/help/copilot/jetbrains-marketplace.png) 1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**. 1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**. ![Screenshot of JetBrains tools menu](/assets/images/help/copilot/jetbrains-tools-menu.png) 1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**. ![Screenshot of device code copy and open](/assets/images/help/copilot/device-code-copy-and-open.png) diff --git a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md index aa94ff185a..280b0d7999 100644 --- a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md +++ b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md @@ -45,9 +45,9 @@ To use {% data variables.product.prodname_copilot %}, you must first install the {% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly. {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function header. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary. +1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary. ```csharp{:copy} - function calculateDaysBetweenDates(begin, end) { + int CalculateDaysBetweenDates( ``` ![Screenshot of a first suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) {% data reusables.copilot.accept-suggestion %} @@ -55,10 +55,10 @@ To use {% data variables.product.prodname_copilot %}, you must first install the ## Seeing alternative suggestions {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion. ```csharp{:copy} - function calculateDaysBetweenDates(begin, end) { + int CalculateDaysBetweenDates( ``` 1. If alternative suggestions are available, you can see these alternatives by pressing Alt+] (or Alt+[). 1. Optionally, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions. diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 89205fdf14..e5f5e65e8f 100644 --- a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -76,7 +76,7 @@ X-Accepted-OAuth-Scopes: user | **`admin:gpg_key`** | GPGキーを完全に管理できます。 | |  `write:gpg_key` | GPGキーの作成、リスト、詳細の表示ができます。 | |  `read:gpg_key` | GPGキーのリストと詳細を表示できます。{% ifversion fpt or ghec %} -| **`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."{% endif %} +| **`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)."{% endif %} | **`ワークフロー`** | {% data variables.product.prodname_actions %}のワークフローファイルの追加と更新機能を許可します。 同じリポジトリ内の他のブランチに同じファイル（パスと内容が同じ）が存在する場合、ワークフローファイルはこのスコープがなくてもコミットできます。 ワークフローファイルは、異なるスコープのセットを持ちうる`GITHUB_TOKEN`を公開できます。 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。 | {% note %} diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index 0e61e57eb7..849ffcbecb 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -36,9 +36,9 @@ You can choose the IDE you'd like to use for an assignment when you create an as The first time you configure an assignment using a different IDE, you must ensure that it is set up correctly. -Unless you use {% data variables.product.prodname_github_codespaces %}, you must authorize the OAuth app for the IDE for your organization. For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." +Unless you use {% data variables.product.prodname_codespaces %}, you must authorize the OAuth app for the IDE for your organization. For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." -{% data variables.product.prodname_github_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_github_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_codespaces %}. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)." +{% data variables.product.prodname_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_codespaces %}. For more information, see "[Using {% data variables.product.prodname_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)." ## Further reading diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 8d5e8d50ff..e9fa3339a9 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -8,7 +8,7 @@ versions: permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}' --- -## {% data variables.product.prodname_codespaces %}について +## {% data variables.product.prodname_github_codespaces %}について {% data variables.product.prodname_github_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment that is the same for all users of your project. For more information, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." @@ -36,7 +36,7 @@ After you have confirmation that you are a verified teacher, visit [{% data vari If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_codespaces %} usage. However, you can change or remove these policies in your organization settings. 詳しい情報については「[マシンタイプへのアクセス制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」を参照してください。 -When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_codespaces %} usage, your organization will be billed for additional usage. 詳しい情報については、「[{% data variables.product.prodname_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#about-billing-for-codespaces)」を参照してください。 +When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_codespaces %} usage, your organization will be billed for additional usage. 詳しい情報については、「[{% data variables.product.prodname_github_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#about-billing-for-codespaces)」を参照してください。 ## Enabling {% data variables.product.prodname_codespaces %} for your organization 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 691bf03588..ec6b3b6496 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 @@ -63,12 +63,11 @@ 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 %}{% ifversion ghec %}, except for the security overview{% endif %}. 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. They also have access to an organization-level security overview. {% 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 %} {% endif %} -{% ifversion ghes or ghec %} +{% ifversion ghes > 3.1 or ghec %} ## 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, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)." +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)." -To review the rollout phases we recommended in more detail, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." {% endif %} {% ifversion not fpt %} diff --git a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md index 71bd17d37a..24fab8d859 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md +++ b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md @@ -84,7 +84,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - リポジトリインサイトグラフ: パルス、コントリビューター、トラフィック、コミット、コード頻度、ネットワーク、およびフォーク {%- ifversion fpt or ghec %} - The option to enable {% data variables.product.prodname_github_codespaces %} - - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." + - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." {%- endif %} {% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %} diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md index 33b1b17fa6..b861ebd607 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -18,7 +18,7 @@ topics: {% warning %} -**Warning:** If you add an image or video to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you attach a file to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -35,7 +35,7 @@ Issue やプルリクエストの会話にファイルを添付するには、 The maximum file size is: - 10MB for images and gifs{% ifversion fpt or ghec %} - 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan -- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif ghes or ghae %} +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif ghes or ghae-issue-7575 %} - 100MB for videos{% endif %} - 25MB for all other files @@ -51,13 +51,13 @@ The maximum file size is: * Microsoft Word (*.docx*)、Powerpoint (*.pptx*)、および Excel (*.xlsx*) 文書 * テキストファイル (*.txt*) * PDF (*.pdf*) -* ZIP (*.zip*, *.gz*) -* ビデオ(*.mp4*, *.mov*) +* ZIP (*.zip*, *.gz*){% ifversion fpt or ghec or ghes or ghae-issue-7575 %} +* ビデオ(*.mp4*, *.mov*){% endif %} -{% note %} +{% ifversion fpt or ghec or ghes or ghae-issue-7575 %}{% note %} **Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility. -{% endnote %} +{% endnote %}{% endif %} ![添付アニメーション GIF](/assets/images/help/pull_requests/dragging_images.gif) diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md index c574b7e549..3b5693c44b 100644 --- a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md @@ -33,13 +33,14 @@ GraphQLサーバーと通信するには、適切なスコープを持つOAuth ``` repo -repo:status -repo_deployment{% ifversion not ghae %} -public_repo{% endif %} +repo_deployment +read:packages read:org read:public_key read:repo_hook user +read:discussion +read:enterprise read:gpg_key ``` diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md index 38d941592d..987aa998fa 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md @@ -594,7 +594,7 @@ gh api graphql -f query=' {% note %} -**ノート:** ` updateProjectV2ItemFieldValue `を使って`Assignees`、`Labels`、`Milestone`、`Repository`を変更することはできません。これは、これらのフィールドがプロジェクトのアイテムのプロパティではなく、Pull RequestやIssueのプロパティだからです。 Instead, you may use the following mutations: +**ノート:** ` updateProjectV2ItemFieldValue `を使って`Assignees`、`Labels`、`Milestone`、`Repository`を変更することはできません。これは、これらのフィールドがプロジェクトのアイテムのプロパティではなく、Pull RequestやIssueのプロパティだからです。 その代わりに、以下のミューテーションを利用できます。 - [addAssigneesToAssignable](/graphql/reference/mutations#addassigneestoassignable) - [removeAssigneesFromAssignable](/graphql/reference/mutations#removeassigneesfromassignable) diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index ac74f8d83e..c149cf49fa 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -74,7 +74,7 @@ OktaでのTeam同期のエラーの可能性を回避するために、{% data v OrganizationのメンバーがリンクされたSCIMアイデンティティを持たない場合、Teamの同期は期待された動作をせず、そのユーザはTeamに追加も削除もされないかもしれません。 もしもユーザの中にSCIMのリンクされたアイデンティティを持たない者がいた場合、それらのユーザはプロビジョニングし直さなければなりません。 -For help on provisioning users that have missing a missing SCIM linked identity, see "[Troubleshooting identity and access management for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization)." +SCIMのリンクされたアイデンティティを欠いているユーザのプロビジョニングに関するヘルプについては「[Organizationのアイデンティティ及びアクセス管理のトラブルシューティング](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization)」を参照してください。 {% data reusables.identity-and-permissions.team-sync-okta-requirements %} 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 373c5e7f5b..56fdbc73ce 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 @@ -1,5 +1,5 @@ --- -title: Troubleshooting identity and access management for your organization +title: Organizationのアイデンティティ及びアクセス管理のトラブルシューティング intro: OrganizationのSAML SSO、Team同期、アイデンティティプロバイダ（IdP）との接続に関するエラーに対する一般的なトラブルシューティングをレビューして解決してください。 versions: ghec: '*' @@ -96,4 +96,4 @@ IdPを介して、ユーザのSCIMを手動で再プロビジョニングでき ## 参考リンク -- "[Troubleshooting identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise)" +- 「[Enterpriseのアイデンティティ及びアクセス管理のトラブルシューティング](/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise)」 diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 956a23d1c3..b13ec3933b 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -1,6 +1,8 @@ --- title: Team をアイデンティティプロバイダグループと同期する -intro: 'You can synchronize a {% data variables.product.product_name %} team with a supported identity provider (IdP) group to automatically add and remove team members.' +intro: |- + {% data variables.product.product_name %}のTeamをサポートされているアイデンティティプロバイダ（IdP) + グループと同期して、自動的にTeamメンバーの追加や削除を行えます。 redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' diff --git a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index 3ce25b899a..2290c045b1 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -102,7 +102,7 @@ curl -X POST \ HOSTNAME/graphql ``` -{% data variables.product.prodname_registry %}に公開したすべてのプライベートパッケージをバージョンIDと合わせて見つけるには、`repository`オブジェクトを通じて`packages`コネクションを使うことができます。 `read:packages`及び`repo`のスコープを持つトークンが必要です。 For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. +{% data variables.product.prodname_registry %}に公開したすべてのプライベートパッケージをバージョンIDと合わせて見つけるには、`repository`オブジェクトを通じて`packages`コネクションを使うことができます。 `read:packages`及び`repo`のスコープを持つトークンが必要です。 詳しい情報については[`packages`](/graphql/reference/objects#repository)コネクションあるいは[`PackageOwner`](/graphql/reference/interfaces#packageowner)インターフェースを参照してください。 `deletePackageVersion`ミューテーションの詳しい情報については、「[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)」を参照してください。 diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md index 6e19d81e19..839256b3ce 100644 --- a/translations/ja-JP/content/packages/quickstart.md +++ b/translations/ja-JP/content/packages/quickstart.md @@ -27,7 +27,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor 3. Create an `index.js` file and add a basic alert to say "Hello world!" {% raw %} ```javascript{:copy} - alert("Hello, World!"); + console.log("Hello, World!"); ``` {% endraw %} 4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package. diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index a40f8da73b..1e06b7fb90 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -26,7 +26,7 @@ topics: {% endnote %} -You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI. +You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_github_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI. プルリクエストを初期化すると、あなたのブランチ（比較ブランチ）とリポジトリのベースブランチとの差異の高レベルの概要を示すレビューページが表示されます。 提案した変更の概要を追加したり、コミットによる変更をレビューしたり、ラベルやマイルストーン、アサインされた人を追加したり、個人のコントリビューターやTeamに@メンションできます。 詳しい情報については[プルリクエストの作成](/articles/creating-a-pull-request)を参照してください。 diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index 886696d05c..6653e82565 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -154,7 +154,7 @@ gh pr create --web 1. マージ元のローカルブランチとリポジトリ、およびマージ先のリモートブランチとリポジトリが正しいことを確認します。 そして、プルリクエストにタイトルと説明を付けます。 ![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png) 1. ** Create（作成）**をクリックしてください。 -For more information on creating pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +For more information on creating pull requests in {% data variables.product.prodname_github_codespaces %}, see "[Using {% data variables.product.prodname_github_codespaces %} for pull requests](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)." {% endcodespaces %} 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 23cef7d07a..b123499917 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 @@ -54,11 +54,11 @@ shortTitle: Review proposed changes {% codespaces %} -You can use [{% data variables.product.prodname_codespaces %}](/codespaces/overview) to test, run, and review pull requests. +You can use [{% data variables.product.prodname_github_codespaces %}](/codespaces/overview) to test, run, and review pull requests. {% data reusables.codespaces.review-pr %} -For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using {% data variables.product.prodname_github_codespaces %} for pull requests](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)." {% endcodespaces %} {% endif %} diff --git a/translations/ja-JP/content/rest/codespaces/codespaces.md b/translations/ja-JP/content/rest/codespaces/codespaces.md index 78ee261b0e..8e4b885f52 100644 --- a/translations/ja-JP/content/rest/codespaces/codespaces.md +++ b/translations/ja-JP/content/rest/codespaces/codespaces.md @@ -11,4 +11,4 @@ miniTocMaxHeadingLevel: 3 ## Codespaces APIについて -{% data variables.product.prodname_codespaces %} API では、REST API を使用して {% data variables.product.prodname_codespaces %} を管理できます。 このAPIは認証を受けたユーザとOAuth Appが利用できますが、GitHub Appは利用できません。 詳細は「[{% data variables.product.prodname_codespaces %}](/codespaces)」を参照してください。 +{% data variables.product.prodname_github_codespaces %} API では、REST API を使用して {% data variables.product.prodname_codespaces %} を管理できます。 このAPIは認証を受けたユーザとOAuth Appが利用できますが、GitHub Appは利用できません。 詳細は「[{% data variables.product.prodname_codespaces %}](/codespaces)」を参照してください。 diff --git a/translations/ja-JP/content/rest/codespaces/index.md b/translations/ja-JP/content/rest/codespaces/index.md index 62c00e7b16..1956630bd6 100644 --- a/translations/ja-JP/content/rest/codespaces/index.md +++ b/translations/ja-JP/content/rest/codespaces/index.md @@ -1,6 +1,6 @@ --- title: Codespaces -intro: '{% data variables.product.prodname_codespaces %} APIを使うと、REST APIを利用してCodespacesを管理できます。' +intro: '{% data variables.product.prodname_github_codespaces %} APIを使うと、REST APIを利用してCodespacesを管理できます。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index cf97970894..5f05d74dbb 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -165,7 +165,7 @@ $ curl {% ifversion fpt or ghae or ghec %} ## GraphQL グローバルノード ID -See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. +REST API を介して `node_id` を検索し、それらを GraphQL 操作で使用する方法について詳しくは、「[グローバルノード ID を使用する](/graphql/guides/using-global-node-ids)」のガイドを参照してください。 ## クライアントエラー diff --git a/translations/ja-JP/content/rest/search.md b/translations/ja-JP/content/rest/search.md index 3693a79e39..62a94321be 100644 --- a/translations/ja-JP/content/rest/search.md +++ b/translations/ja-JP/content/rest/search.md @@ -107,7 +107,8 @@ cURL と、上記の [Issue 検索例](#search-issues-and-pull-requests) を使 ``` shell curl -H 'Accept: application/vnd.github.text-match+json' \ -'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc' +'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug \ ++language:python+state:open&sort=created&order=asc' ``` レスポンスには、検索結果ごとに `text_matches` 配列が含まれます。 以下の JSON では、`text_matches` 配列に 2 つのオブジェクトがあります。 @@ -123,7 +124,9 @@ curl -H 'Accept: application/vnd.github.text-match+json' \ "object_url": "https://api.github.com/repositories/215335/issues/132", "object_type": "Issue", "property": "body", - "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n", + "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly + distributed windows font that supports them then no problem (we can use html + font tags) but otherwise the '(21)' style is probably better.\n", "matches": [ { "text": "windows", @@ -145,7 +148,9 @@ curl -H 'Accept: application/vnd.github.text-match+json' \ "object_url": "https://api.github.com/repositories/215335/issues/comments/25688", "object_type": "IssueComment", "property": "body", - "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n", + "fragment": " right after that are a bit broken IMHO :). I suppose we could + have some hack that maxes out at whatever the font does...\n\nI'll check + what the state of play is on Windows.\n", "matches": [ { "text": "Windows", diff --git a/translations/ja-JP/content/rest/webhooks/index.md b/translations/ja-JP/content/rest/webhooks/index.md index c51d41d6a0..0def1ab4f6 100644 --- a/translations/ja-JP/content/rest/webhooks/index.md +++ b/translations/ja-JP/content/rest/webhooks/index.md @@ -70,9 +70,9 @@ PubSubHubbub リクエストは複数回送信できます。 フックがすで #### パラメータ -| 名前 | 種類 | 説明 | -| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hub.mode` | `string` | **必須**。 `subscribe` または `unsubscribe`。 | -| `hub.topic` | `string` | **必須**。 GitHub リポジトリがサブスクライブする URI。 パスのフォーマットは `/{owner}/{repo}/events/{event}` としてください。 | -| `hub.callback` | `string` | トピックの更新を受信する URI。 | -| `hub.secret` | `string` | 送信する本文コンテンツの ハッシュ署名を生成する共有秘密鍵。 You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. 詳細は、 [PubSubHubbub のドキュメント](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)を参照してください。 | +| 名前 | 種類 | 説明 | +| -------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `hub.mode` | `string` | **必須**。 `subscribe` または `unsubscribe`。 | +| `hub.topic` | `string` | **必須**。 GitHub リポジトリがサブスクライブする URI。 パスのフォーマットは `/{owner}/{repo}/events/{event}` としてください。 | +| `hub.callback` | `string` | トピックの更新を受信する URI。 | +| `hub.secret` | `string` | 送信する本文コンテンツの ハッシュ署名を生成する共有秘密鍵。 GitHubからきたプッシュを、そのリクエストのボディを{% ifversion fpt or ghes or ghec %}`X-Hub-Signature`もしくは`X-Hub-Signature-256`ヘッダ{% elsif ghae %}`X-Hub-Signature-256`ヘッダ{% endif %}と比較して、検証できます。 詳細は、 [PubSubHubbub のドキュメント](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)を参照してください。 | diff --git a/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md index 82aac069b7..b56d01407e 100644 --- a/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md @@ -34,13 +34,13 @@ To see our Privacy Notice to residents of California, please go to [GitHub's Not | セクション | 各セクションの内容 | | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your Personal Data in connection with the Website or Service. | -| [GitHubが収集する情報](#what-information-github-collects) | GitHubは、お客様の登録内容や支払い、取引、ユーザプロフィールから直接情報を収集します。 当社は、また、お客様の同意が必要な場合は同意を得て、自動的に利用情報、クッキー、およびデバイス情報から収集します。 GitHub may also collect Personal Data from third parties. We only collect the minimum amount of Personal Data necessary from you, unless you choose to provide more. | +| [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your personal data in connection with the Website or Service. | +| [GitHubが収集する情報](#what-information-github-collects) | GitHubは、お客様の登録内容や支払い、取引、ユーザプロフィールから直接情報を収集します。 当社は、また、お客様の同意が必要な場合は同意を得て、自動的に利用情報、クッキー、およびデバイス情報から収集します。 GitHub may also collect personal data from third parties. We only collect the minimum amount of personal data necessary from you, unless you choose to provide more. | | [当社のお客様情報の利用方法](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Website or Service or develop new features and functionality of our Website or Service. 法令が要求している場合、さらに、お客様の情報を処理する法的な根拠を記載します。 | | [当社が収集したお客様の情報の共有方法](#how-we-share-the-information-we-collect) | 次のいずれかの場合において、当社はお客様の情報を第三者と共有することがあります。 ・お客様の同意がある場合 ・当社のサービスプロバイダ間と共有する場合 ・セキュリティを目的とする場合 ・当社の法的義務を遵守する必要がある場合 ・事業法人または事業部門について支配者の変更または売却が行われた場合 当社が個人情報を販売することはありません。GitHubでは広告を掲載することもありません。 | | [Your choices regarding our processing of your personal data](#your-choices-regarding-our-processing-of-your-personal-data) | 当社は、お客様に対して、お客様の個人情報にアクセス、変更または削除する方法を提供します。 | | [クッキー](#cookies) | We only use strictly necessary cookies to provide, secure, and improve our Website or Service or develop new features and functionality of our Website or Service. 当社は、このクッキーとトラッキングについて透明性の高いページを提供します。 We do not send any information to third-party analytics services. | -| [お客様情報についての当社の保護方法](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your Personal Data on GitHub and to protect the resilience of our servers. | +| [お客様情報についての当社の保護方法](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your personal data on GitHub and to protect the resilience of our servers. | | [Communication preferences](#communication-preferences) | 当社は、お客様にemailでご連絡します。 アカウント設定または当社にご連絡いただければ、当社からお客様への方法を管理できます。 | | [苦情の解決](#resolving-complaints) | 万が一、当社がプライバシーに関する懸念を迅速かつ十分に解決できない場合、当社は紛争解決の方法を提案します。 | | [プライバシーステートメントの変更](#changes-to-our-privacy-statement) | 当社は、本プライバシーステートメントの重大な変更について当該変更が有効となる30日前に、お客様に通知します。 お客様は、変更を当社のサイトポリシーリポジトリにおいて確認することもできます。 | @@ -57,7 +57,7 @@ This privacy statement does not apply to personal data we process as a service p ## GitHub acting on your behalf -In some cases, GitHub is acting only on your behalf for the personal data we collect and process in connection with our Service (for example, for the Personal Data added to a repository by the contributors to such repository). In such cases, GitHub will only process the data in order to provide the Service requested by you. Please note that subject to our [Private Information Removal Policy](/site-policy/content-removal-policies/github-private-information-removal-policy) contributors’ requests to remove Personal Data generally require notice to and action from the repository owner. +In some cases, GitHub is acting only on your behalf for the personal data we collect and process in connection with our Service (for example, for the personal data added to a repository by the contributors to such repository). In such cases, GitHub will only process the data in order to provide the Service requested by you. Please note that subject to our [Private Information Removal Policy](/site-policy/content-removal-policies/github-private-information-removal-policy) contributors’ requests to remove personal data generally require notice to and action from the repository owner. ## GitHubが収集する情報 @@ -102,7 +102,7 @@ We infer new information from other data we collect, including using automated m ### 当社から第三者から収集する情報 -Other companies with whom you choose to engage. GitHub may collect Personal Data about you from third parties. たとえば、お客様が、トレーニングにサインアップしたり、当社のベンダー、パートナーや関連会社からGitHubについての情報を受け取る場合に、行われる可能性があります。 GitHub does not purchase Personal Data from third-party data brokers. +Other companies with whom you choose to engage. GitHub may collect personal data about you from third parties. たとえば、お客様が、トレーニングにサインアップしたり、当社のベンダー、パートナーや関連会社からGitHubについての情報を受け取る場合に、行われる可能性があります。 GitHub does not purchase personal data from third-party data brokers. Service Providers. We may also receive information from processors or service providers who process the data on our behalf, such as our payment processor who process payment and billing information in connection with our Service. @@ -112,7 +112,7 @@ Co-branding/marketing partners. We may receive information from partners with wh Publicly available sources. We may also obtain information from publicly available sources as GitHub repositories. -When you are asked to provide Personal Data, you may decline. And you may use web browser or operating system controls to prevent certain types of automatic data collection. But if you choose not to provide or allow information that is necessary for certain services or features, those services or features may not be available or fully functional. +When you are asked to provide personal data, you may decline. And you may use web browser or operating system controls to prevent certain types of automatic data collection. But if you choose not to provide or allow information that is necessary for certain services or features, those services or features may not be available or fully functional. ## 当社のお客様情報の利用方法 We may use your information to provide, administer, analyze, manage, and operate our Service. For example, we use your information for the following purposes: @@ -128,7 +128,7 @@ We combine data we collect from different sources for these purposes and to give ## 当社が収集したお客様の情報の共有方法 -We share Personal Data with your consent or as necessary to complete your transactions or provide the services you have requested or authorized. In addition, we may share each of the categories of your Personal Data described above with the types of third parties described below for the following business purposes: +We share personal data with your consent or as necessary to complete your transactions or provide the services you have requested or authorized. In addition, we may share each of the categories of your personal data described above with the types of third parties described below for the following business purposes: ### Public information You may select options available through our Service to publicly display and share your name and/or username and certain other information, such as your profile, demographic data, content and files, or geolocation data. For example, if you would like your email address to remain private, even when you’re commenting on public repositories, [you can adjust your setting for your email address to be private in your user profile](https://github.com/settings/emails). You can also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). コミットメッセージ内のメールアドレスに関する詳細については、[こちら](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)を参照してください。 @@ -136,50 +136,50 @@ You may select options available through our Service to publicly display and sha Please note that if you would like to compile GitHub data, you must comply with our [Terms of Service](/site-policy/github-terms/github-terms-of-service) regarding information usage and privacy, and you may only use any public-facing information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. ### Third-party applications -We share your Personal Data with third parties when you tell us to do so. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your Personal Data. たとえば、お客様がOrganizationに参加する場合、OrganizationのオーナーにOrganizationのアクセスログを使ってお客様のアクティビティを表示する権限を付与したい旨を指示できます。 +We share your personal data with third parties when you tell us to do so. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your personal data. たとえば、お客様がOrganizationに参加する場合、OrganizationのオーナーにOrganizationのアクセスログを使ってお客様のアクティビティを表示する権限を付与したい旨を指示できます。 -You can enable or add third-party applications, known as "Developer Products" to your Account. このDeveloper Productsは、お客様がGitHubを利用するにあたって、必ずしも必要なものではありません。 We will share your Personal Data with such third-party applications when you ask us to; however, you are responsible for your use of the third-party Developer Product and for the amount of Personal Data you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. +You can enable or add third-party applications, known as "Developer Products" to your Account. このDeveloper Productsは、お客様がGitHubを利用するにあたって、必ずしも必要なものではありません。 We will share your personal data with such third-party applications when you ask us to; however, you are responsible for your use of the third-party Developer Product and for the amount of personal data you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. ### Organizations with which you engage -You may indicate, through your actions on GitHub, that you are willing to share your Personal Data. If you collaborate on or become a member of an organization, then its Account owners may receive your Personal Data. When you accept an invitation to an organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Please contact the Account owners for more information about how they might process your Personal Data in their Organization and the ways for you to access, update, alter, or delete your Personal Data stored in the Account. +You may indicate, through your actions on GitHub, that you are willing to share your personal data. If you collaborate on or become a member of an organization, then its Account owners may receive your personal data. When you accept an invitation to an organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Please contact the Account owners for more information about how they might process your personal data in their Organization and the ways for you to access, update, alter, or delete your personal data stored in the Account. ### サービスプロバイダ -We share your Personal Data with service providers who process the information on our behalf to provide or improve our Service. For example, our service providers may perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all Personal Data in the United States, our service providers may process data outside of the United States or the European Union. Such processing by service providers will be in compliance with applicable law including any relevant transfer mechanism. +We share your personal data with service providers who process the information on our behalf to provide or improve our Service. For example, our service providers may perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all personal data in the United States, our service providers may process data outside of the United States or the European Union. Such processing by service providers will be in compliance with applicable law including any relevant transfer mechanism. - ### Affiliates We enable access to Personal Data across our subsidiaries, affiliates, and related companies, for example, where we share common data systems or where access is needed to operate and provide the Service. + ### Affiliates We enable access to personal data across our subsidiaries, affiliates, and related companies, for example, where we share common data systems or where access is needed to operate and provide the Service. ### セキュリティを目的とする場合 -We will disclose Personal Data if we believe it is necessary to: +We will disclose personal data if we believe it is necessary to: - protect our customers and others, for example to prevent spam or attempts to commit fraud, or to help prevent the loss of life or serious injury of anyone; - operate and maintain the security of the Service, including to prevent or stop an attack on our systems or networks; or - protect the rights or property or ourselves or others, including enforcing our agreements, terms, and policies. ### 法令にもとづく開示を求められた場合 -GitHub may disclose Personal Data or other information we collect about you to law enforcement or other governmental agencies if required in response to a valid legal process. For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data). +GitHub may disclose personal data or other information we collect about you to law enforcement or other governmental agencies if required in response to a valid legal process. For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data). ### 管理者の変更または売却があった場合 -We may share your Personal Data if we are involved in a merger, sale, or acquisition of corporate entities or business units as described in this Privacy Statement. +We may share your personal data if we are involved in a merger, sale, or acquisition of corporate entities or business units as described in this Privacy Statement. -Please note that some of the features on our Service include integrations, references, or links to services provided by third parties whose privacy practices differ from ours. If you provide Personal Data to any of those third parties, or allow us to share Personal Data with them, that data is governed by their privacy statements. +Please note that some of the features on our Service include integrations, references, or links to services provided by third parties whose privacy practices differ from ours. If you provide personal data to any of those third parties, or allow us to share personal data with them, that data is governed by their privacy statements. Finally, we may share de-identified information in accordance with applicable law. -### No Selling of Personal Data -We *do not* sell your Personal Data for monetary or other consideration as defined under California and Nevada state laws. You can learn more about the CCPA and how we comply with it [here](#githubs-notice-to-california-residents). +### No selling of personal data +We *do not* sell your personal data for monetary or other consideration as defined under California and Nevada state laws. You can learn more about the CCPA and how we comply with it [here](#githubs-notice-to-california-residents). ## Your choices regarding our processing of your personal data -We provide choices about the Personal Data we collect about you. The choices you make will not apply to any Personal Data associated with an Organization under your Account. +We provide choices about the personal data we collect about you. The choices you make will not apply to any personal data associated with an Organization under your Account. Access, correction, and deletion. If you're a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). 当社がお客様について収集する情報は、プロフィールに掲載する情報を限定する、お客様の情報を最新に保つ、または[GitHub Support](https://support.github.com/contact)もしくは[GitHubPremium Support](https://enterprise.githubsupport.com/hc/en-us)に連絡することにより管理できます。 -We retain and use your information as described in this Privacy Statement, but barring legal requirements, we will delete your full profile within 90 days of your request. アカウントが削除された後でも、他のユーザのリポジトリへのコントリビューションおよび他のIssueのコメントなどの一定のデータは残存します。 However, we will delete or de-identify your Personal Data, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a ghost user. That said, the email address you have provided via your Git commit settings will always be associated with your commits in the Git system. メールアドレスを非公開にする場合、Gitコミット設定もアップデートする必要があります。 当社は、Gitコミット履歴のデータを変更または削除することはできません。Gitソフトウェアは記録を保持する設計になっています。ただし、当社は、お客様がその記録に入力する情報を管理できるようにします。 +We retain and use your information as described in this Privacy Statement, but barring legal requirements, we will delete your full profile within 90 days of your request. アカウントが削除された後でも、他のユーザのリポジトリへのコントリビューションおよび他のIssueのコメントなどの一定のデータは残存します。 However, we will delete or de-identify your personal data, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a ghost user. That said, the email address you have provided via your Git commit settings will always be associated with your commits in the Git system. メールアドレスを非公開にする場合、Gitコミット設定もアップデートする必要があります。 当社は、Gitコミット履歴のデータを変更または削除することはできません。Gitソフトウェアは記録を保持する設計になっています。ただし、当社は、お客様がその記録に入力する情報を管理できるようにします。 -If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). +If GitHub processes personal data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your personal data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). -You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). +You can adjust the settings on your Account regarding the display of your personal data in private or public repositories or personal data processed in connection with Community Features (such as GitHub Feed, GitHub Sponsors, and GitHub Explore) through [profile settings](https://github.com/settings/profile). -Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. +Additionally, if you are unable to access certain personal data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. ### データポータビリティ @@ -196,13 +196,13 @@ Depending on your [email settings](https://github.com/settings/emails), GitHub m ### European Data Protection Rights -If the processing of Personal Data about you is subject to European Union data protection law, you have certain rights with respect to that data: +If the processing of personal data about you is subject to European Union data protection law, you have certain rights with respect to that data: -You can request access to, and rectification or erasure of, Personal Data; If any automated processing of Personal Data is based on your consent or a contract with you, you have a right to transfer or receive a copy of the Personal Data in a usable and portable format; If the processing of Personal Data is based on your consent, you can withdraw consent at any time for future processing; You can to object to, or obtain a restriction of, the processing of Personal Data under certain circumstances; and For residents of France, you can send us specific instructions regarding the use of your data after your death. +You can request access to, and rectification or erasure of, personal data; If any automated processing of personal data is based on your consent or a contract with you, you have a right to transfer or receive a copy of the personal data in a usable and portable format; If the processing of personal data is based on your consent, you can withdraw consent at any time for future processing; You can to object to, or obtain a restriction of, the processing of personal data under certain circumstances; and For residents of France, you can send us specific instructions regarding the use of your data after your death. To make such requests, please use the contact information at the bottom of this statement. When we are processing data on behalf of another party (i.e., where GitHub is acting as a data processor) you should direct your request to that party. You also have the right to lodge a complaint with a supervisory authority, but we encourage you to first contact us with any questions or concerns. -We rely on different lawful bases for collecting and processing Personal Data about you, for example, with your consent and/or as necessary to provide the services you use, operate our business, meet our contractual and legal obligations, protect the security of our systems and our customers, or fulfill other legitimate interests. +We rely on different lawful bases for collecting and processing personal data about you, for example, with your consent and/or as necessary to provide the services you use, operate our business, meet our contractual and legal obligations, protect the security of our systems and our customers, or fulfill other legitimate interests. ## Our use of cookies and tracking technologies @@ -216,11 +216,11 @@ Our emails to users may contain a pixel tag, which is a small, clear image that 「[Do Not Track](https://www.eff.org/issues/do-not-track)」(DNT) とは、オンラインサービスに対して、第三者のトラッキングサービスからお客様のオンライン活動についての特定の種類の情報を収集して共有することを望まない場合に、ブラウザで設定できるプライバシー設定です。 GitHubは、ブラウザのDNTシグナルに応答し、[DNTシグナルへの応答についてのW3C基準](https://www.w3.org/TR/tracking-dnt/)に従います。 トラッキングを望まないことを通知するようブラウザに対して設定したい場合、この通知を有効化する方法について、ブラウザのドキュメントをご確認ください。 [Privacy Badger](https://privacybadger.org/)など、トラッキングをブロックする良いアプリケーションもあります。 -## Retention of Personal Data -We retain Personal Data for as long as necessary to provide the services and fulfill the transactions you have requested, comply with our legal obligations, resolve disputes, enforce our agreements, and other legitimate and lawful business purposes. Because these needs can vary for different data types in the context of different services, actual retention periods can vary significantly based on criteria such as user expectations or consent, the sensitivity of the data, the availability of automated controls that enable users to delete data, and our legal or contractual obligations. For example, we may retain your Personal Data for longer periods, where necessary, subject to applicable law, for security purposes. +## Retention of personal data +We retain personal data for as long as necessary to provide the services and fulfill the transactions you have requested, comply with our legal obligations, resolve disputes, enforce our agreements, and other legitimate and lawful business purposes. Because these needs can vary for different data types in the context of different services, actual retention periods can vary significantly based on criteria such as user expectations or consent, the sensitivity of the data, the availability of automated controls that enable users to delete data, and our legal or contractual obligations. For example, we may retain your personal data for longer periods, where necessary, subject to applicable law, for security purposes. ## お客様情報についての当社の保護方法 -GitHub takes reasonable measures necessary to protect your Personal Data from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of your Personal Data. To help us protect personal data, we request that you use a strong password and never share your password with anyone or use the same password with other sites or accounts. +GitHub takes reasonable measures necessary to protect your personal data from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of your personal data. To help us protect personal data, we request that you use a strong password and never share your password with anyone or use the same password with other sites or accounts. In addition, if your account has private repositories, you control the access to that Content. GitHub personnel does not access private repository content except for - security purposes, @@ -233,10 +233,10 @@ In addition, if your account has private repositories, you control the access to Github will provide notice regarding private repository access where not prohibited by law or if in response to a security threat or other risk to security. ### クロスボーダーデータトランスファー -GitHub processes Personal Data both inside and outside of the United States and relies on legal mechanisms such as Standard Contractual Clauses to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. You may request a copy of the Standard Contractual Clauses using the contact details provided in the section entitled “Contacting GitHub” below. +GitHub processes personal data both inside and outside of the United States and relies on legal mechanisms such as Standard Contractual Clauses to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. You may request a copy of the Standard Contractual Clauses using the contact details provided in the section entitled “Contacting GitHub” below. ### 苦情の解決 -If you have concerns about the way GitHub is handling your Personal Data, please let us know immediately. 当社はお客様を手助けしたいと考えています。 お客様は、[プライバシー連絡フォーム](https://support.github.com/contact/privacy)に記入することで、当社に連絡できます。 You may also email us directly at **(privacy [at] github [dot] com)** with the subject line "Privacy Concerns." 当社は、遅くとも45日以内に速やかに返信します。 +If you have concerns about the way GitHub is handling your personal data, please let us know immediately. 当社はお客様を手助けしたいと考えています。 お客様は、[プライバシー連絡フォーム](https://support.github.com/contact/privacy)に記入することで、当社に連絡できます。 You may also email us directly at **(privacy [at] github [dot] com)** with the subject line "Privacy Concerns." 当社は、遅くとも45日以内に速やかに返信します。 お客様は、当社のデータ保護責任者に直接連絡することもできます。 diff --git a/translations/ja-JP/data/features/dependabot-most-important-sort-option.yml b/translations/ja-JP/data/features/dependabot-most-important-sort-option.yml new file mode 100644 index 0000000000..429c3e6be0 --- /dev/null +++ b/translations/ja-JP/data/features/dependabot-most-important-sort-option.yml @@ -0,0 +1,6 @@ +#Reference: Issue #7510 - Dependabot alerts: "Most important" sort (prioritization score) - [GA] +versions: + fpt: '*' + ghec: '*' + ghes: '>3.6' + ghae: 'issue-7510' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml index 02f53cd76a..a2df564967 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -37,7 +37,7 @@ sections: heading: Depandabotアップデートの一般提供 notes: - | - Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin. For more information, see "[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + Dependabotバージョン及びセキュリティアップデートは、GitHub Enterprise Server 3.5で一般提供になりました。GitHub.comリポジトリで動作する一般的なすべてのエコシステムと機能は、GitHub Enterprise Serverインスタンスでセットアップできます。GitHub Enterprise Server上のDependabotにはGitHub ActionsとセルフホストのDependabotランナーのプール、GitHub Connectの有効化、管理者によるDependabotの有効化が必要です。詳しい情報については「[Dependabotアップデートのセットアップ](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)」を参照してください。 - heading: Server Statisticsのパブリックベータ notes: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml index 3b3f1499d0..ec83bb9f7f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml @@ -30,7 +30,7 @@ sections: heading: Depandabotアップデートの一般提供 notes: - | - Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin. For more information, see "[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + Dependabotバージョン及びセキュリティアップデートは、GitHub Enterprise Server 3.5で一般提供になりました。GitHub.comリポジトリで動作する一般的なすべてのエコシステムと機能は、GitHub Enterprise Serverインスタンスでセットアップできます。GitHub Enterprise Server上のDependabotにはGitHub ActionsとセルフホストのDependabotランナーのプール、GitHub Connectの有効化、管理者によるDependabotの有効化が必要です。詳しい情報については「[Dependabotアップデートのセットアップ](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)」を参照してください。 - heading: Server Statisticsのパブリックベータ notes: diff --git a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml index f4716c8c6a..730b68e9e3 100644 --- a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml +++ b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -114,9 +114,6 @@ sections: - | You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. - - - | - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." - | GitHub AE now automatically generates a table of contents for Wikis, based on headings. diff --git a/translations/ja-JP/data/reusables/actions/about-secrets.md b/translations/ja-JP/data/reusables/actions/about-secrets.md index 7e67aff95e..4853f0aa0b 100644 --- a/translations/ja-JP/data/reusables/actions/about-secrets.md +++ b/translations/ja-JP/data/reusables/actions/about-secrets.md @@ -1 +1 @@ -Encrypted secrets allow you to store sensitive information, such as access tokens, in your repository, repository environments, or organization. +暗号化されたシークレットを使えば、アクセストークンのようなセンシティブな情報をリポジトリやリポジトリ環境、Organizationに保存できます。 diff --git a/translations/ja-JP/data/reusables/actions/github-token-permissions.md b/translations/ja-JP/data/reusables/actions/github-token-permissions.md index c884110135..c43bd01912 100644 --- a/translations/ja-JP/data/reusables/actions/github-token-permissions.md +++ b/translations/ja-JP/data/reusables/actions/github-token-permissions.md @@ -1 +1 @@ -ワークフロー内のジョブが開始されるたびに、`GITHUB_TOKEN`はそのリポジトリのアクセストークンに設定されます。 You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。 +ワークフロー内のジョブが開始されるたびに、`GITHUB_TOKEN`はそのリポジトリのアクセストークンに設定されます。 `contents`スコープに対する読み取りアクセス権と、`packages`スコープに対する書き込み権を付与するために、ワークフローファイル中でこのアクセストークンに権限を設定しなければなりません。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md b/translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md index 0ca428ef32..a96b040ce2 100644 --- a/translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md +++ b/translations/ja-JP/data/reusables/actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %}に公開するために`mvn --batch-mode deploy`コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 The `permissions` key specifies the access granted to the `GITHUB_TOKEN`. +{% data variables.product.prodname_registry %}に公開するために`mvn --batch-mode deploy`コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 `permissions`キーは、`GITHUB_TOKEN`に付与されたアクセスを指定します。 diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md index ef5632f174..c1237b71f6 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md @@ -1 +1 @@ -1. In the "Runners" section of the settings page, next to the runner group you'd like to configure, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit name and [organization|repository] access**. ![リポジトリの権限の管理](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. 設定ページの"Runners（ランナー）"のセクションで、設定したいランナーグループの隣の{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて**Edit name and [organization|repository] access（名前と[Organization|リポジトリ]アクセスの編集）**をクリックしてください。 ![リポジトリの権限の管理](/assets/images/help/settings/actions-runner-manage-permissions.png) diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md index 6e53ef0e5b..5b49e7dbe6 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-list.md @@ -1 +1 @@ -1. Locate the list of runners under "Runners". +1. "Runners（ランナー）"の下で、ランナーのリストを見つけてください。 diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md index 9b4573b00e..74569a97aa 100644 --- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md +++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Under "Runners", locate the runner in the list. ランナーがグループ内にあるなら、{% octicon "chevron-down" aria-label="The downwards chevron" %}をクリックしてリストを展開してください。 +1. "Runners（ランナー）"の下で、ランナーのリストを見つけてください。 ランナーがグループ内にあるなら、{% octicon "chevron-down" aria-label="The downwards chevron" %}をクリックしてリストを展開してください。 1. 削除したいランナーの隣の{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて** Remove（削除）**をクリックしてください。 ![セルフホストランナーの設定の削除](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/ja-JP/data/reusables/advanced-security/check-for-ghas-license.md b/translations/ja-JP/data/reusables/advanced-security/check-for-ghas-license.md index 9fcc39ac76..e20d2e39f9 100644 --- a/translations/ja-JP/data/reusables/advanced-security/check-for-ghas-license.md +++ b/translations/ja-JP/data/reusables/advanced-security/check-for-ghas-license.md @@ -1 +1 @@ -You can identify if your enterprise has a {% data variables.product.prodname_GH_advanced_security %} license by reviewing your enterprise settings. For more information, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise#checking-whether-your-license-includes-github-advanced-security)." +Enterpriseの設定を確認すれば、Enterpriseが{% data variables.product.prodname_GH_advanced_security %}ライセンスを持っているかを確認できます。 詳しい情報については「[EnterpriseでのGitHub Advanced Securityの有効化](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise#checking-whether-your-license-includes-github-advanced-security)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md index 0825738dc0..7453688fc4 100644 --- a/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md +++ b/translations/ja-JP/data/reusables/advanced-security/getting-the-most-from-your-license.md @@ -1,6 +1,6 @@ -{% data variables.product.prodname_GH_advanced_security %} の優先順位を付けるリポジトリと Organization を決定するときは、それらを確認して次のことを特定する必要があります。 +{% data variables.product.prodname_GH_advanced_security %} の優先順位を高めるリポジトリと Organization を決定するには、それらを確認して次のことを特定する必要があります。 -- 会社の成功にとって最も重要なコードベース。 These are the projects for which the introduction of vulnerable code, hard-coded secrets, or insecure dependencies would have the greatest impact on your company. +- 会社の成功にとって最も重要なコードベース。 これらは、脆弱なコード、ハードコードされたシークレット、または安全ではない依存関係の導入が会社に最大の影響を与えるプロジェクトです。 - コミット頻度が最も高いコードベース。 これらは最も積極的に開発されたプロジェクトであるため、セキュリティの問題が発生するリスクが高くなります。 -When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, assess which other codebases you could add without incurring billing for unique committers. Finally, review the remaining important and busy codebases. {% ifversion fpt or ghes or ghec %}If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} +これらのOrganizationやリポジトリで{% data variables.product.prodname_GH_advanced_security %}を有効化したら、個々のコミッタが支払いをすることなく追加できる他のコードベースを評価してください。 最後に、残りの重要で忙しいコードベースをレビューしてください。 {% ifversion fpt or ghes or ghec %}ライセンス中のシート数を増やしたい場合には、{% data variables.contact.contact_enterprise_sales %}にお問い合わせください。{% endif %} diff --git a/translations/ja-JP/data/reusables/advanced-security/license-overview.md b/translations/ja-JP/data/reusables/advanced-security/license-overview.md index 7ec44bfb3e..59cabc8bac 100644 --- a/translations/ja-JP/data/reusables/advanced-security/license-overview.md +++ b/translations/ja-JP/data/reusables/advanced-security/license-overview.md @@ -1,4 +1,4 @@ -{% data variables.product.prodname_GH_advanced_security %}の各ライセンスは、それらの機能を使用できるアカウントもしくはシートの最大数を指定します。 少なくとも1つのリポジトリでこの機能が有効化されているそれぞれのアクティブなコミッターは、1つのシートを使用します。 A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored. +Each license for {% data variables.product.prodname_GH_advanced_security %} specifies a maximum number of accounts, or seats, that can use these features. Each active committer to at least one repository with the feature enabled uses one seat. A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored. {% note %} diff --git a/translations/ja-JP/data/reusables/advanced-security/more-information-about-enforcement-policy.md b/translations/ja-JP/data/reusables/advanced-security/more-information-about-enforcement-policy.md index d830fa0205..14f5efb7fe 100644 --- a/translations/ja-JP/data/reusables/advanced-security/more-information-about-enforcement-policy.md +++ b/translations/ja-JP/data/reusables/advanced-security/more-information-about-enforcement-policy.md @@ -1 +1 @@ -For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)." +詳しい情報については「[Enterpriseでの{% data variables.product.prodname_advanced_security %}のポリシーの施行]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md index d41b8b1f06..285c975f3b 100644 --- a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -2,6 +2,6 @@ {% note %} **ノート:** -{% data variables.product.prodname_GH_advanced_security %}を有効化した場合、それらのリポジトリのコミッターは{% data variables.product.prodname_GH_advanced_security %}ライセンス上でシートを利用することになります。 このオプションは、ライセンスの容量を超えた場合には無効化されます。 {% ifversion fpt or ghec %}For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +{% data variables.product.prodname_GH_advanced_security %}を有効化した場合、それらのリポジトリのコミッターは{% data variables.product.prodname_GH_advanced_security %}ライセンス上でシートを利用することになります。 このオプションは、ライセンスの容量を超えた場合には無効化されます。 {% ifversion fpt or ghec %}詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}の支払いについて](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)」を参照してください。{% endif %} {% endnote %} {% endif %} diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index e5946561cb..5871419f49 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -1,7 +1,7 @@ 1. 新しいカスタムパターンの詳細を入力します。 1. 少なくともパターンの名前と、シークレットパターンのフォーマットとして正規表現を提供しなければなりません。 1. [**More options {% octicon "chevron-down" aria-label="down" %}** ]をクリックして、シークレットのフォーマットのその他の周辺コンテンツあるいは追加のマッチ要件を提供できます。 - 1. Provide a sample test string to make sure your configuration is matching the patterns you expect. + 1. サンプルのテスト文字列を指定し、設定内容が期待するパターンにマッチすることを確認してください。 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %} ![カスタムの{% data variables.product.prodname_secret_scanning %}パターン形式の作成](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) {% else %} 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 8f4453f9fc..a0723f7e50 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-issue-5499 %}**Publish pattern**{% elsif ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. +1. 新しいカスタムパターンに満足したら、{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}**Publish pattern（パターンの公開）**{% elsif ghes > 3.2 or ghae %}**Create pattern（パターンの作成）**{% elsif ghes = 3.2 %}**Create custom pattern（カスタムパターンの作成）**{% endif %}をクリックしてください。 diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-results.md index e1fa2f748a..968ca87639 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-results.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-results.md @@ -1,3 +1,3 @@ -1. When the dry run finishes, you'll see a sample of results (up to 1000). Review the results and identify any false positive results. ![Screenshot showing results from dry run](/assets/images/help/repository/secret-scanning-publish-pattern.png) -1. Edit the new custom pattern to fix any problems with the results, then, to test your changes, click **Save and dry run**. +1. dry runが終了すると、結果のサンプル（最大1000）が表示されます。 結果をレビューし、誤検知の結果を確認してください。 ![dry runの結果を表示しているスクリーンショット](/assets/images/help/repository/secret-scanning-publish-pattern.png) +1. 結果に問題があれば修正するために新しいカスタムパターンを編集し、その変更をテストするために**Save and dry run（保存してdry run）**をクリックしてください。 {% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %} diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md index 5526314385..d70e6538d2 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md @@ -1,2 +1,2 @@ -1. Search for and select up to 10 repositories where you want to perform the dry run. ![dry runのために選択したリポジトリを表示しているスクリーンショット](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png) +1. dry runを実行したいリポジトリを最大10個まで検索して選択してください。 ![dry runのために選択したリポジトリを表示しているスクリーンショット](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png) 1. カスタムパターンをテストする準備ができたら、**Dry run**をクリックしてください。 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 f4253a5e11..2d7bf56f22 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 +1 @@ -1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}. +1. "{% data variables.product.prodname_secret_scanning_caps %}"の下の"Custom patterns（カスタムパターン）"の下で、 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}**New pattern（新規パターン）**{% elsif ghes = 3.2 %}**New custom pattern（新規カスタムパターン）**{% endif %}をクリックしてください。 diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md index c39f2b505d..03b7a69cb8 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md @@ -1,2 +1,2 @@ -1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**. ![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for an organization](/assets/images/help/organizations/secret-scanning-enable-push-protection.png) -1. Optionally, click "Automatically enable for private repositories added to {% data variables.product.prodname_secret_scanning %}." +1. "{% data variables.product.prodname_secret_scanning_caps %}"の下の"Push protection（プッシュ保護）"の下で、**Enable all（すべて有効化）**をクリックしてください。 ![任意のOrganizationで{% data variables.product.prodname_secret_scanning %}のプッシュ保護を有効化する方法を示しているスクリーンショット](/assets/images/help/organizations/secret-scanning-enable-push-protection.png) +1. あるいは、"Automatically enable for private repositories added to {% data variables.product.prodname_secret_scanning %}"をクリックしてください。 diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-repo.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-repo.md index 4cc816ff8f..5465c590d7 100644 --- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-repo.md +++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-repo.md @@ -1 +1 @@ -1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable**. ![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for a repository](/assets/images/help/repository/secret-scanning-enable-push-protection.png) +1. "{% data variables.product.prodname_secret_scanning_caps %}"の下の"Push protection（プッシュ保護）"の下で、**Enable（有効化）**をクリックしてください。 ![リポジトリで{% data variables.product.prodname_secret_scanning %}のプッシュ保護を有効化する方法を示しているスクリーンショット](/assets/images/help/repository/secret-scanning-enable-push-protection.png) diff --git a/translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md b/translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md index ef965ceae3..d3aba07b48 100644 --- a/translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md +++ b/translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md @@ -1 +1 @@ -Some features are available for {% ifversion ghes or ghae %}all repositories{% elsif fpt or ghec %}repositories on all plans{% endif %}. Additional features are available to enterprises that use {% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt or ghec %}{% data variables.product.prodname_GH_advanced_security %} features are also enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %} +一部の機能は{% ifversion ghes or ghae %}すべてのリポジトリで{% elsif fpt or ghec %}すべてのプランのリポジトリで{% endif %}利用できます。 追加の機能は、{% data variables.product.prodname_GH_advanced_security %}を使用するEnerpriseで利用できます。 {% ifversion fpt or ghec %}{% data variables.product.prodname_GH_advanced_security %}の機能は、{% data variables.product.prodname_dotcom_the_website %}上のすべてのパブリックリポジトリでも有効化されています。{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md b/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md index f5f341401c..4ab916b584 100644 --- a/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md +++ b/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md @@ -1 +1 @@ -{% data variables.product.product_name %} provides starter workflows for security features such as {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. +{% data variables.product.product_name %}は、{% data variables.product.prodname_code_scanning %}などのセキュリティ機能に対するスターターワークフローを提供しています。 ゼロから始めるのではなく、提案されるこれらのワークフローを使って、独自の{% data variables.product.prodname_code_scanning %}ワークフローを構築できます。 diff --git a/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md b/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md index 7cce688d11..9a3a2cb30f 100644 --- a/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md +++ b/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Starter workflows for {% data variables.product.prodname_advanced_security %} have been consolidated in a "Security" category in the **Actions** tab of a repository. This new configuration is currently in beta and subject to change. +**ノート:** {% data variables.product.prodname_advanced_security %}のスターターワークフローは、リポジトリの**Actions**タブの"Security（セキュリティ）"カテゴリに統合されました。 この新しい設定は現在ベータであり、変更されることがあります。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md index 94fc49a4c6..37446f2df5 100644 --- a/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md +++ b/translations/ja-JP/data/reusables/advisory-database/beta-malware-advisories.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Advisories for malware are currently in beta and subject to change. +**ノート:** マルウェアのアドバイザリは現在ベータであり、変更されることがあります。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md b/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md index b76fef614b..167b6cecee 100644 --- a/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md +++ b/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md @@ -1 +1 @@ -You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: +`Accept`ヘッダでフォーマットを指定すれば、様々なフォーマットでレスポンスを受け取ることもできます。 たとえば`Accept: application/json`あるいは`Accept: application/xml`: diff --git a/translations/ja-JP/data/reusables/apps/oauth-token-limit.md b/translations/ja-JP/data/reusables/apps/oauth-token-limit.md index 38f4ef11fb..40688d6aeb 100644 --- a/translations/ja-JP/data/reusables/apps/oauth-token-limit.md +++ b/translations/ja-JP/data/reusables/apps/oauth-token-limit.md @@ -1 +1 @@ -ユーザ／アプリケーション／スコープの組み合わせごとに、発行できるトークン数には10という上限があります。 If an application creates more than 10 tokens for the same user and the same scopes, the oldest tokens with the same user/application/scope combination will be revoked. +ユーザ／アプリケーション／スコープの組み合わせごとに、発行できるトークン数には10という上限があります。 アプリケーションが同じユーザと同じスコープに対して10個以上のトークンを作成すると、同じユーザ/アプリケーション/スコープの組み合わせに対する最も古いトークンが取り消されます。 diff --git a/translations/ja-JP/data/reusables/apps/optional_feature_activation.md b/translations/ja-JP/data/reusables/apps/optional_feature_activation.md index 9bfbd4fefe..ab8c479883 100644 --- a/translations/ja-JP/data/reusables/apps/optional_feature_activation.md +++ b/translations/ja-JP/data/reusables/apps/optional_feature_activation.md @@ -1,2 +1,2 @@ -4. In the left sidebar, click **Optional Features**. ![Optional features tab](/assets/images/github-apps/optional-features-option.png) -5. Next to the optional feature you want to enable for your app, click **Opt-in**. ![オプション機能を有効にするオプトインボタン](/assets/images/github-apps/enable-optional-features.png) +4. 左のサイドバーで、**Optional Features（オプション機能）**をクリックしてください。 ![オプション機能のタブ](/assets/images/github-apps/optional-features-option.png) +5. アプリケーションで有効化したいオプション機能の隣の**Opt-in（オプトイン）**をクリックしてください。 ![オプション機能を有効にするオプトインボタン](/assets/images/github-apps/enable-optional-features.png) diff --git a/translations/ja-JP/data/reusables/apps/settings-step.md b/translations/ja-JP/data/reusables/apps/settings-step.md index 043bd9f058..74c0d0fb8f 100644 --- a/translations/ja-JP/data/reusables/apps/settings-step.md +++ b/translations/ja-JP/data/reusables/apps/settings-step.md @@ -1,3 +1,3 @@ 1. アカウント設定にアクセスしてください。 - - For a {% data variables.product.prodname_github_app %} owned by a personal account, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![ユーザバーの [Settings（設定）] アイコン](/assets/images/settings/userbar-account-settings_post2dot12.png) + - 個人アカウントが所有する{% data variables.product.prodname_github_app %}の場合、任意のページの右上でプロフィール写真をクリックしてから、**Settings（設定）**をクリックしてください。 ![ユーザバーの [Settings（設定）] アイコン](/assets/images/settings/userbar-account-settings_post2dot12.png) - Organizationが所有する{% data variables.product.prodname_github_app %}の場合、任意のページの右上でプロフィール写真をクリックしてから、**Your organizations（自分のOrganization）**をクリックしてください。 そして、Organizationの右の**Settings（設定）**をクリックしてください。 ![プロフィールメニューのあなたのOrganization](/assets/images/help/profile/your-organizations.png) ![設定ボタン](/assets/images/help/organizations/settings-button.png) diff --git a/translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md b/translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md index 60ba02467d..f6f89ef1ec 100644 --- a/translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md +++ b/translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md @@ -1 +1 @@ -{% ifversion ghes %}By default, user-to-server{% else %}User-to-server{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from OAuth applications authorized by a user or a personal access token owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user. +{% ifversion ghes %}デフォルトでは、user-to-server{% else %}user-to-server{% endif %}リクエストは、認証を受けたユーザの1時間ごとに{% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %}リクエストに制限されます。 ユーザもしくはユーザが所有する個人アクセストークンによって認可されたOAuthアプリケーションからのすべてのリクエスト、及びユーザのいずれかの認証情報によって認証されたリクエストは、そのユーザの1時間あたり{% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %}リクエストという同じクオータを共有します。 diff --git a/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md index 7c4e394de9..29835aa93d 100644 --- a/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md +++ b/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md @@ -1 +1 @@ -リポジトリのための{% data variables.product.prodname_codespaces %}の設定が変更された後、codespaceのコンテナをリビルドしてその変更を既存のcodespaceに適用できます。 +リポジトリのための{% data variables.product.prodname_github_codespaces %}の設定が変更された後、codespaceのコンテナをリビルドしてその変更を既存のcodespaceに適用できます。 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md index 394f39607f..0be4a46707 100644 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-billing.md @@ -1,9 +1,9 @@ {% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage. ### Calculating compute usage -Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly. +Compute usage is defined as the total number of uptime minutes for which a {% data variables.product.prodname_github_codespaces %} instance is active. Compute usage is calculated by summing the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly. Uptime is controlled by stopping your codespace, which can be done manually or automatically after a developer specified period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)". ### Calculating storage usage -For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 +For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md index 12c91c9bdc..53aecddf17 100644 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md @@ -1,3 +1,3 @@ -Typically, you can run your codespace on a choice of remote machine, from 2 cores to 32 cores. これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 For information, see "[About billing for Codespaces](/github/developing-online-with-codespaces/about-billing-for-codespaces)." +Typically, you can run your codespace on a choice of remote machine, from 2 cores to 32 cores. これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。 For information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)." By default the machine type with the lowest valid resources is used when you create a codespace. diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md index 370656971e..61e7031435 100644 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md +++ b/translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md @@ -4,6 +4,6 @@ {% endnote %} -By default, your organization or enterprise will have a {% data variables.product.prodname_codespaces %} spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0. +By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0. {% data reusables.billing.overages-billed-monthly %} 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 5448b6204f..d4e5abc125 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_codespaces %}, see "[Quickstart for {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_codespaces %} works, see "[Deep dive into Codespaces](/codespaces/getting-started/deep-dive)." +To get started with {% data variables.product.prodname_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_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/prebuilds-crossreference.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md index a6d82dba27..68d9b051fd 100644 --- a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md +++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md @@ -1 +1 @@ -To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." +To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)." diff --git a/translations/ja-JP/data/reusables/gated-features/codespaces.md b/translations/ja-JP/data/reusables/gated-features/codespaces.md index 4b85591f8f..572854b8ff 100644 --- a/translations/ja-JP/data/reusables/gated-features/codespaces.md +++ b/translations/ja-JP/data/reusables/gated-features/codespaces.md @@ -1 +1 @@ -Codespaces is available for organizations using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} +{% data variables.product.prodname_github_codespaces %} is available for organizations using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ja-JP/data/reusables/repositories/reaction_list.md b/translations/ja-JP/data/reusables/repositories/reaction_list.md index 6ad9436a84..25dff0fcff 100644 --- a/translations/ja-JP/data/reusables/repositories/reaction_list.md +++ b/translations/ja-JP/data/reusables/repositories/reaction_list.md @@ -1,10 +1,42 @@ -| 内容 | 絵文字 | -| ------- | ---------- | -| `+1` | :+1: | -| `-1` | :-1: | -| `笑い` | :smile: | -| `混乱` | :confused: | -| `heart` | :heart: | -| `万歳` | :tada: | -| `ロケット` | :rocket: | -| `目` | :eyes: | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
内容絵文字
+1👍
-1👎
笑い😄
混乱😕
heart❤️
万歳🎉
ロケット🚀
目👀
diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md index 9249552208..941cbc1c78 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md @@ -4,7 +4,7 @@ | `check_suite` | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。 | | `check_suite[head_branch]` | `string` | 変更があるヘッドブランチ名。 | | `check_suite[head_sha]` | `string` | このチェックスイートに対する最新のコミットのSHA。 | -| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。 | +| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 Can be `queued`, `requested`, `in_progress`, or `completed`. | | `check_suite[conclusion]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. チェックランが`completed`になるまで、この値は`null`になる。 | | `check_suite[url]` | `string` | チェックスイートAPIのリソースを指すURL。 | | `check_suite[pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:** | diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index 121a2f5d8a..da7d7fe9f9 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -86,6 +86,7 @@ translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/s translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-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/introduction-to-adopting-github-advanced-security-at-scale.md,broken liquid tags translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md,broken liquid tags @@ -122,13 +123,14 @@ translations/ja-JP/content/code-security/index.md,broken liquid tags translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md,broken liquid tags translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,broken liquid tags translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md,broken liquid tags +translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md,broken liquid tags translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md,broken liquid tags translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,broken liquid tags translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,broken liquid tags translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489 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/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags -translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags +translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md,broken liquid tags +translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md,broken liquid tags translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,broken liquid tags @@ -270,6 +272,8 @@ translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md,bro translations/ja-JP/data/reusables/actions/self-hosted-runner-reusing.md,broken liquid tags translations/ja-JP/data/reusables/actions/self-hosted-runners-prerequisites.md,broken liquid tags translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags +translations/ja-JP/data/reusables/advanced-security/license-overview.md,broken liquid tags +translations/ja-JP/data/reusables/apps/user-to-server-rate-limits-ghec.md,broken liquid tags translations/ja-JP/data/reusables/classroom/classroom-codespaces-link.md,broken liquid tags translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags