From 2179db781a48e2e596650636aebf1dde34649627 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Fri, 2 Dec 2022 08:51:34 -0800 Subject: [PATCH 1/3] New translation batch for ja (#33182) --- .../adding-labels-to-issues.md | 52 ++--- .../about-server-statistics.md | 151 +++++++------- ...github-packages-with-azure-blob-storage.md | 3 + .../githubs-ssh-key-fingerprints.md | 23 ++- .../using-ssh-over-the-https-port.md | 8 +- .../secret-scanning-patterns.md | 70 ++++--- .../deleting-a-codespace.md | 10 +- .../developing-in-codespaces/index.md | 8 +- .../opening-an-existing-codespace.md | 10 +- .../stopping-and-starting-a-codespace.md | 51 ++--- .../codespaces/getting-started/deep-dive.md | 10 +- .../codespaces/getting-started/index.md | 8 +- .../the-codespace-lifecycle.md | 73 +++++++ .../ja-JP/content/codespaces/index.md | 8 +- .../introduction-to-dev-containers.md | 193 +++++++++--------- ...ll-request-template-for-your-repository.md | 61 +++--- ...-with-github-copilot-in-a-jetbrains-ide.md | 126 ++++++------ ...g-started-with-github-copilot-in-neovim.md | 35 ++-- ...th-github-copilot-in-visual-studio-code.md | 84 ++++---- ...ed-with-github-copilot-in-visual-studio.md | 84 ++++---- ...rl-for-a-repository-from-github-desktop.md | 33 +++ .../index.md | 8 +- ...github-codespaces-with-github-classroom.md | 10 +- .../using-the-graphql-api-for-discussions.md | 10 +- ...figuring-a-remote-repository-for-a-fork.md | 43 ++++ .../working-with-forks/index.md | 8 +- .../working-with-forks/syncing-a-fork.md | 62 +++--- .../content/rest/overview/api-versions.md | 54 +++++ .../content/rest/overview/breaking-changes.md | 30 +++ .../overview/resources-in-the-rest-api.md | 12 +- .../codespaces/stopping-a-codespace.md | 10 +- .../reusables/copilot/copilot-cta-button.md | 9 + .../discussions/repository-category-limit.md | 10 +- .../reusables/rest-api/about-api-versions.md | 32 +++ .../data/reusables/rest-api/version-header.md | 9 + translations/log/msft-ja-resets.csv | 12 +- 36 files changed, 871 insertions(+), 549 deletions(-) create mode 100644 translations/ja-JP/content/codespaces/getting-started/the-codespace-lifecycle.md create mode 100644 translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md create mode 100644 translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md create mode 100644 translations/ja-JP/content/rest/overview/api-versions.md create mode 100644 translations/ja-JP/content/rest/overview/breaking-changes.md create mode 100644 translations/ja-JP/data/reusables/copilot/copilot-cta-button.md create mode 100644 translations/ja-JP/data/reusables/rest-api/about-api-versions.md create mode 100644 translations/ja-JP/data/reusables/rest-api/version-header.md diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 213c2d5c9c6a..dfec386110bb 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -1,7 +1,7 @@ --- -title: Adding labels to issues +title: Issue にラベルを追加する shortTitle: Add labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: '{% data variables.product.prodname_actions %} を使用して、Issue に自動的にラベルを付けることができます。' redirect_from: - /actions/guides/adding-labels-to-issues versions: @@ -13,24 +13,28 @@ type: tutorial topics: - Workflows - Project management +ms.openlocfilehash: a3523069b9422ecd8107007ca5e00fb0071dd738 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185562' --- +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +## はじめに -## Introduction +このチュートリアルでは、ワークフローで [`actions/github-script` アクション](https://github.com/marketplace/actions/github-script)を使用して、新しくオープンまたは再オープンした Issue にラベルを付ける方法を示します。 たとえば、Issue をオープンまたは再オープンするたびに `triage` ラベルを追加できます。 次に、`triage` ラベルで Issue をフィルター処理して、トリアージする必要のあるすべての Issue を確認できます。 -This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label. +`actions/github-script` アクションを使うと、ワークフローで {% data variables.product.prodname_dotcom %} API を簡単に使用できます。 -The `actions/github-script` action allows you to easily use the {% data variables.product.prodname_dotcom %} API in a workflow. +チュートリアルでは、[`actions/github-script` アクション](https://github.com/marketplace/actions/github-script)を使用するワークフロー ファイルをまず作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。 -In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs. - -## Creating the workflow +## ワークフローの作成 1. {% data reusables.actions.choose-repo %} 2. {% data reusables.actions.make-workflow-file %} -3. Copy the following YAML contents into your workflow file. +3. 次の YAML コンテンツをワークフローファイルにコピーします。 ```yaml{:copy} name: Label issues @@ -56,23 +60,23 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git }) ``` -4. Customize the `script` parameter in your workflow file: - - The `issue_number`, `owner`, and `repo` values are automatically set using the `context` object. You do not need to change these. - - Change the value for `labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `["help wanted", "good first issue"]`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)." +4. ワークフロー ファイルの `script` パラメーターをカスタマイズします。 + - `issue_number`、`owner`、`repo` の値は、`context` オブジェクトを使って自動的に設定されます。 これらを変更する必要はありません。 + - `labels` の値を、Issue に追加するラベルのリストに変更します。 複数のラベルはコンマで区切ります。 たとえば、「 `["help wanted", "good first issue"]` 」のように入力します。 ラベルの詳細については、「[ラベルを管理する](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)」を参照してください。 5. {% data reusables.actions.commit-workflow %} -## Testing the workflow +## ワークフローのテスト -Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue. +リポジトリ内の Issue をオープンするか再オープンするたびに、このワークフローは指定したラベルを Issue に追加します。 -Test out your workflow by creating an issue in your repository. +リポジトリに Issue を作成して、ワークフローをテストします。 -1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." -2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -3. When the workflow completes, the issue that you created should have the specified labels added. +1. リポジトリで Issue を作成します。 詳細については、「[Issue の作成](/github/managing-your-work-on-github/creating-an-issue)」を参照してください。 +2. Issue の作成によってトリガーされたワークフローの実行を確認するには、ワークフローの実行履歴を表示します。 詳細については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +3. ワークフローが完了すると、作成した Issue に指定されたラベルが追加されます。 -## Next steps +## 次の手順 -- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script). -- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." -- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action. +- `actions/github-script` アクションで実行できる追加の機能について詳しくは、[`actions/github-script` アクションのドキュメント](https://github.com/marketplace/actions/github-script)にアクセスしてください。 +- ワークフローをトリガーできるさまざまなイベントの詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#issues)」を参照してください。 +- このアクションを使用するワークフローの例については [GitHub を検索](https://github.com/search?q=%22uses:+actions/github-script%22&type=code)してください。 diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index a3cb3c1f5bcd..d2a8a37bad01 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: About Server Statistics -intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' +title: Server Statistics について +intro: '{% data variables.product.prodname_server_statistics %} を使って、{% data variables.product.prodname_ghe_server %} からの独自の集計データを分析し、{% data variables.product.company_short %} 製品の改善に役立てることができます。' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -8,97 +8,102 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics topics: - Enterprise +ms.openlocfilehash: 3d17df54cd5dcf9ad102ab5079794a9bcb3e664b +ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185186' --- +## {% data variables.product.prodname_server_statistics %} の利点について -## About the benefits of {% data variables.product.prodname_server_statistics %} +{% data variables.product.prodname_server_statistics %} は、Organization のニーズを予測し、チームの活動状況を把握し、{% data variables.product.prodname_ghe_server %} から得られた価値を確認するのに役立ちます。 -{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +{% data variables.product.prodname_server_statistics %} を有効にすると、特定の機能のインスタンスでの使用量に関する集計データが経時的に収集されます。 最終日のデータのみを返す他の [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) エンドポイントとは異なり、{% data variables.product.prodname_server_statistics %} では、機能を有効にした日から収集されたすべての {% data variables.product.prodname_server_statistics %} メトリックの履歴データが提供されます。 詳しくは、「[Enterprise で {% data variables.product.prodname_server_statistics %} を有効にする](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」をご覧ください。 -Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +{% data variables.product.prodname_server_statistics %} を有効にすると、より優れた {% data variables.product.prodname_dotcom %} を構築できます。 提供される集計データにより、お客様に対する {% data variables.product.prodname_dotcom %} の価値についての分析情報が得られます。 この情報を利用することで、{% data variables.product.company_short %} は製品に関していっそう適切な決定を情報に基づいて行うことができ、最終的にはお客様のメリットになります。 -When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. +## データのセキュリティについて -## About data security +GitHub はお客様のデータを尊重します。 前もってお客様から許可をいただかない限り、{% data variables.location.product_location %} からデータを送信することはありません。 -We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so. +GitHub は個人データを収集しません。 また、コード、issue、コメント、pull request の内容など、{% data variables.product.company_short %} のいかなるコンテンツも収集しません。 -We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. +データにアクセスできるのは、{% data variables.product.prodname_ghe_cloud %} 上の接続された Enterprise アカウントまたは Organization の所有者だけです。 -Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. +リポジトリ、issue、pull request、その他の機能については、特定の集計メトリックのみが収集されます。 収集される集計メトリックの一覧については、「[{% data variables.product.prodname_server_statistics %} で収集されるデータ](#server-statistics-data-collected)」をご覧ください。 -Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." +収集されるメトリックは、{% data variables.product.prodname_ghe_server %} の今後の機能リリースで更新され、それについては [{% data variables.product.prodname_ghe_server %} のリリース ノート](/admin/release-notes)で説明されます。 さらに、この記事もすべてのメトリックの更新に関して更新されます。 -Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. +{% data variables.product.prodname_server_statistics %} のデータの格納およびセキュリティ保護の方法について詳しくは、「[GitHub のセキュリティ](https://github.com/security)」をご覧ください。 -For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." +### データの保持と削除について -### About data retention and deletion +{% data variables.product.company_short %} は、お客様の {% data variables.product.prodname_ghe_server %} ライセンスがアクティブで、{% data variables.product.prodname_server_statistics %} 機能が有効になっている場合にのみ、{% data variables.product.prodname_server_statistics %} のデータを収集します。 -{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. +お客様がデータの削除を望まれる場合は、GitHub サポート、お客様の {% data variables.product.prodname_dotcom %} アカウント担当者、または担当のカスタマー サクセス マネージャーにご連絡ください。 一般に、データの削除は、プライバシーに関する声明で指定されている期間に行われます。 詳しくは、{% data variables.product.prodname_dotcom_the_website %} のドキュメントの「[{% data variables.product.company_short %} のプライバシーについての声明](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data)」をご覧ください。 -If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. +### データの移植性について -### About data portability +{% data variables.product.prodname_ghe_cloud %} の Organization 所有者または Enterprise 所有者は、CSV または JSON ファイルにデータをエクスポートすることで、または {% data variables.product.prodname_server_statistics %} REST API を使って、{% data variables.product.prodname_server_statistics %} のデータにアクセスできます。 詳しくは、「[REST API を使用して {% data variables.product.prodname_server_statistics %} を要求する](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)」または「[{% data variables.product.prodname_server_statistics %} をエクスポートする](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)」をご覧ください。 -As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." +## データ収集の無効化について -## About disabling data collection +{% data variables.product.prodname_server_statistics %} の機能はいつでも無効にできます。 詳しくは、「[Enterprise で {% data variables.product.prodname_server_statistics %} を有効にする](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」をご覧ください。 -You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +## {% data variables.product.prodname_server_statistics %} で収集されるデータ -## {% data variables.product.prodname_server_statistics %} data collected +{% data variables.product.prodname_server_statistics %} を有効にすると、{% data variables.location.product_location %} で実行される日次ジョブを通じてメトリックが収集されます。 集計メトリックは、{% data variables.product.prodname_ghe_cloud %} の組織またはエンタープライズ アカウントに格納され、{% data variables.location.product_location %} には格納されません。 -After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}. +次の集計メトリックは、毎日収集および送信され、その日の合計カウントを表します。 -The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day. - -CSV column | Name | Description | +CSV 列 | Name | 説明 | ---------- | ---- | ----------- | -A | `github_connect.features_enabled` | Array of {% data variables.product.prodname_github_connect %} features that are enabled for your instance (see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)" ) | -B | `host_name` | The hostname for your instance | -C | `dormant_users.dormancy_threshold` | The length of time a user must be inactive to be considered dormant | -D | `dormant_users.total_dormant_users` | Number of dormant user accounts | -E | `ghes_version` | The version of {% data variables.product.product_name %} that your instance is running | -F | `server_id` | The UUID generated for your instance -G | `collection_date` | The date the metrics were collected | -H | `schema_version` | The version of the database schema used to store this data | -I | `ghe_stats.comments.total_commit_comments` | Number of comments on commits | -J | `ghe_stats.comments.total_gist_comments` | Number of comments on gists | -K | `ghe_stats.comments.total_issue_comments` | Number of comments on issues | -L | `ghe_stats.comments.total_pull_request_comments` | Number of comments on pull requests | -M | `ghe_stats.gists.total_gists` | Number of gists (both secret and public) | -N | `ghe_stats.gists.private_gists` | Number of secret gists | -O | `ghe_stats.gists.public_gists` | Number of public gists | -P | `ghe_stats.hooks.total_hooks` | Number of pre-receive hooks (both active and inactive) | -Q | `ghe_stats.hooks.active_hooks` | Number of active pre-receive hooks | -R | `ghe_stats.hooks.inactive_hooks` | Number of inactive pre-receive hooks | -S | `ghe_stats.issues.total_issues` | Number of issues (both open and closed) | -T | `ghe_stats.issues.open_issues` | Number of open issues | -U | `ghe_stats.issues.closed_issues` | Number of closed issues | -V | `ghe_stats.milestones.total_milestones` | Number of milestones (both open and closed) | -W | `ghe_stats.milestones.open_milestones` | Number of open milestones | -X | `ghe_stats.milestones.closed_milestones` | Number of closed milestones | -Y | `ghe_stats.orgs.total_orgs` | Number of organizations (both enabled and disabled) | -Z | `ghe_stats.orgs.disabled_orgs` | Number of disabled organizations | -AA | `ghe_stats.orgs.total_teams` | Number of teams | -AB | `ghe_stats.orgs.total_team_members` | Number of team members | -AC | `ghe_stats.pages.total_pages` | Number of {% data variables.product.prodname_pages %} sites | -AD | `ghe_stats.pulls.total_pulls` | Number of pull requests | -AE | `ghe_stats.pulls.merged_pulls` | Number of merged pull requests | -AF | `ghe_stats.pulls.mergeable_pulls` | Number of pull requests that are currently mergeable | -AG | `ghe_stats.pulls.unmergeable_pulls` | Number of pull requests that are currently unmergeable | -AH | `ghe_stats.repos.total_repos` | Number of repositories (both upstream repositories and forks) | -AI | `ghe_stats.repos.root_repos` | Number of upstream repositories | -AJ | `ghe_stats.repos.fork_repos` | Number of forks | -AK | `ghe_stats.repos.org_repos` | Number of repositories owned by organizations | -AL | `ghe_stats.repos.total_pushes` | Number of pushes to repositories | -AM | `ghe_stats.repos.total_wikis` | Number of wikis | -AN | `ghe_stats.users.total_users` | Number of user accounts | -AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators | -AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended | - -## {% data variables.product.prodname_server_statistics %} data examples - -To see an example of the headings included in the CSV export for {% data variables.product.prodname_server_statistics %}, download the [{% data variables.product.prodname_server_statistics %} CSV example](/assets/server-statistics-csv-example.csv). - -To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." \ No newline at end of file +A | `github_connect.features_enabled` | インスタンスに対して有効になっている {% data variables.product.prodname_github_connect %} 機能の配列 (「[{% data variables.product.prodname_github_connect %} について](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)」を参照) | +B | `host_name` | インスタンスのホスト名 | +C | `dormant_users.dormancy_threshold` | ユーザーが休眠と見なされるまでに非アクティブである必要がある時間の長さ | +D | `dormant_users.total_dormant_users` | 休眠ユーザー アカウントの数 | +E | `ghes_version` | インスタンスが実行されている {% data variables.product.product_name %} のバージョン | +F | `server_id` | インスタンスに対して生成された UUID +G | `collection_date` | メトリックが収集された日付 | +H | `schema_version` | このデータの格納に使用されるデータベース スキーマのバージョン | +I | `ghe_stats.comments.total_commit_comments` | コミットに対するコメントの数 | +J | `ghe_stats.comments.total_gist_comments` | gist に対するコメントの数 | +K | `ghe_stats.comments.total_issue_comments` | イシューに対するコメントの数 | +L | `ghe_stats.comments.total_pull_request_comments` | pull request に対するコメントの数 | +M | `ghe_stats.gists.total_gists` | gists の数 (シークレットとパブリックの両方) | +N | `ghe_stats.gists.private_gists` | シークレット gist の数 | +O | `ghe_stats.gists.public_gists` | パブリック gist の数 | +P | `ghe_stats.hooks.total_hooks` | pre-receive フックの数 (アクティブと非アクティブの両方) | +Q | `ghe_stats.hooks.active_hooks` | アクティブな pre-receive フックの数 | +R | `ghe_stats.hooks.inactive_hooks` | 非アクティブな pre-receive フックの数 | +S | `ghe_stats.issues.total_issues` | イシューの数 (オープンとクローズの両方) | +T | `ghe_stats.issues.open_issues` | オープンのイシューの数 | +U | `ghe_stats.issues.closed_issues` | クローズされたイシューの数 | +V | `ghe_stats.milestones.total_milestones` | マイルストーンの数 (オープンとクローズの両方) | +W | `ghe_stats.milestones.open_milestones` | オープンのマイルストーンの数 | +X | `ghe_stats.milestones.closed_milestones` | クローズされたマイルストーンの数 | +Y | `ghe_stats.orgs.total_orgs` | 組織の数 (有効と無効の両方) | +Z | `ghe_stats.orgs.disabled_orgs` | 無効な組織の数 | +AA | `ghe_stats.orgs.total_teams` | チームの数 | +AB | `ghe_stats.orgs.total_team_members` | チーム メンバーの数 | +AC | `ghe_stats.pages.total_pages` | {% data variables.product.prodname_pages %} サイトの数 | +AD | `ghe_stats.pulls.total_pulls` | pull request の数 | +AE | `ghe_stats.pulls.merged_pulls` | マージされた pull request の数 | +AF | `ghe_stats.pulls.mergeable_pulls` | 現在マージ可能な pull request の数 | +AG | `ghe_stats.pulls.unmergeable_pulls` | 現在マージ不可能な pull request の数 | +AH | `ghe_stats.repos.total_repos` | リポジトリの数 (アップストリーム リポジトリとフォークの両方) | +AI | `ghe_stats.repos.root_repos` | アップストリーム リポジトリの数 | +AJ | `ghe_stats.repos.fork_repos` | フォークの数 | +AK | `ghe_stats.repos.org_repos` | 組織が所有しているリポジトリの数 | +AL | `ghe_stats.repos.total_pushes` | リポジトリへのプッシュの数 | +AM | `ghe_stats.repos.total_wikis` | wiki の数 | +AN | `ghe_stats.users.total_users` | ユーザー アカウントの数 | +AO | `ghe_stats.users.admin_users` | サイト管理者であるユーザー アカウントの数 | +AP | `ghe_stats.users.suspended_users` | 一時停止されているユーザー アカウントの数 | + +## {% data variables.product.prodname_server_statistics %} データの例 + +{% data variables.product.prodname_server_statistics %} の CSV エクスポートに含まれる見出しの例を確認するには、[{% data variables.product.prodname_server_statistics %} CSV の例](/assets/server-statistics-csv-example.csv)をダウンロードしてください。 + +{% data variables.product.prodname_server_statistics %} API の応答ペイロードの例については、「[REST API を使用して {% data variables.product.prodname_server_statistics %} を要求する](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)」をご覧ください。 diff --git a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index ad147336e7cb..1286785f705f 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -1,6 +1,6 @@ --- -title: GitHub の SSH キーフィンガープリント -intro: パブリックキーフィンガープリントを使用して、リモートサーバへの接続を有効にすることができます。 +title: GitHub's SSH key fingerprints +intro: Public key fingerprints can be used to validate a connection to a remote server. redirect_from: - /articles/what-are-github-s-ssh-key-fingerprints - /articles/github-s-ssh-key-fingerprints @@ -14,15 +14,20 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: 29f61df463d014e6a72ad7dd21049a2b338b893e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145088446' --- -{% data variables.product.prodname_dotcom %} の公開鍵のフィンガープリントは次のとおりです。 +These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated) - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) + +You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts: + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== +``` + +For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)." diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 92f37fba9d43..7815859b8efc 100644 --- a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -30,7 +30,7 @@ $ ssh -T -p 443 git@ssh.github.com **Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). @@ -71,8 +71,8 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> Are you sure you want to continue connecting (yes/no/[fingerprint])? ``` -It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches -one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches +one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." diff --git a/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md index 91f0779732b8..a43693a91c80 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md +++ b/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md @@ -1,6 +1,6 @@ --- -title: secret scanning パターン -intro: 'サポートされているシークレットと、誤ってコミットされたシークレットの不正使用を防ぐために {% data variables.product.company_short %} が連携するパートナーの一覧。' +title: Secret scanning patterns +intro: 'Lists of supported secrets and the partners that {% data variables.product.company_short %} works with to prevent fraudulent use of secrets that were committed accidentally.' product: '{% data reusables.gated-features.secret-scanning-partner %}' versions: fpt: '*' @@ -13,65 +13,69 @@ topics: - Advanced Security redirect_from: - /code-security/secret-scanning/secret-scanning-partners -ms.openlocfilehash: 68dd1338fc1812cd2fc40ba38949434a04986f86 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578643' --- -{% data reusables.secret-scanning.beta %} {% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} {% ifversion fpt or ghec %} -## {% data variables.product.prodname_secret_scanning %} パターンについて +## About {% data variables.product.prodname_secret_scanning %} patterns -{% data variables.product.product_name %} では、{% data variables.product.prodname_secret_scanning %} パターンの次のさまざまなセットが保持されています。 +{% data variables.product.product_name %} maintains these different sets of {% data variables.product.prodname_secret_scanning %} patterns: -1. **パートナー パターン。** すべてのパブリック リポジトリで潜在的なシークレットを検出するために使われます。 詳しくは、「[パートナー パターンでサポートされるシークレット](#supported-secrets-for-partner-patterns)」をご覧ください。 -2. **高度なセキュリティ パターン。** {% data variables.product.prodname_secret_scanning %} が有効になっているリポジトリで潜在的なシークレットを検出するために使われます。 {% ifversion ghec %}詳しくは、「[高度なセキュリティでサポートされるシークレット](#supported-secrets-for-advanced-security)」をご覧ください。{% endif %}{% ifversion secret-scanning-push-protection %} -3. **プッシュ保護パターン。** プッシュ保護として {% data variables.product.prodname_secret_scanning %} が有効になっているリポジトリで潜在的なシークレットを検出するために使われます。 詳しくは、「[プッシュ保護でサポートされるシークレット](#supported-secrets-for-push-protection)」をご覧ください。{% endif %} +1. **Partner patterns.** Used to detect potential secrets in all public repositories. For details, see "[Supported secrets for partner patterns](#supported-secrets-for-partner-patterns)." +2. **Advanced security patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} enabled. {% ifversion ghec %} For details, see "[Supported secrets for advanced security](#supported-secrets-for-advanced-security)."{% endif %}{% ifversion secret-scanning-push-protection %} +3. **Push protection patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} as a push protection enabled. For details, see "[Supported secrets for push protection](#supported-secrets-for-push-protection)."{% endif %} -{% ifversion fpt %} {% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_GH_advanced_security %} を使っている Organization は、リポジトリで {% data variables.product.prodname_secret_scanning_GHAS %} を有効にすることができます。 これらのパターンについて詳しくは、 [{% data variables.product.prodname_ghe_cloud %} のドキュメント](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)をご覧ください。 +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %} can enable {% data variables.product.prodname_secret_scanning_GHAS %} on their repositories. For details of these patterns, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security). {% endif %} -## パートナー パターンでサポートされるシークレット +## Supported secrets for partner patterns -現在 {% data variables.product.product_name %} は、パブリックリポジトリをスキャンして、次のサービスプロバイダが発行したシークレットを探します。 {% data variables.product.prodname_secret_scanning_partner %} について詳しくは、「[{% data variables.product.prodname_secret_scanning_partner %} について](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)」をご覧ください。 +{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers and alerts the relevant service provider whenever a secret is detected in a commit. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)." {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} -{% data reusables.secret-scanning.partner-secret-list-public-repo %} {% endif %} +{% data reusables.secret-scanning.partner-secret-list-public-repo %} +{% endif %} {% ifversion ghec or ghae or ghes %} -## {% ifversion ghec %}高度なセキュリティ{% endif %}でサポートされるシークレット +## Supported secrets{% ifversion ghec %} for advanced security{% endif %} -{% data variables.product.prodname_secret_scanning_GHAS %} が有効になっていると、{% data variables.product.prodname_dotcom %} は、次のサービス プロバイダーによって発行されたシークレットをスキャンします。 {% ifversion ghec %}{% data variables.product.prodname_secret_scanning_GHAS %} について詳しくは、「[{% data variables.product.prodname_secret_scanning_GHAS %} について](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)」をご覧ください。{% endif %} +When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %} {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} -secret scanning に REST API を使う場合は、`Secret type` を使って特定の発行者からのシークレットについて報告できます。 詳しくは、「[secret scanning](/enterprise-cloud@latest/rest/secret-scanning)」をご覧ください。 +If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)." -{% ifversion ghes or ghae or ghec %} {% note %} +{% ifversion ghes or ghae or ghec %} +{% note %} -**注:** リポジトリ、Organization、または Enterprise 用のカスタム {% data variables.product.prodname_secret_scanning %} パターンを定義することもできます。 詳細については、「[{% data variables.product.prodname_secret_scanning %}のカスタム パターンの定義](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)」を参照してください。 +**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for your repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% endif %} +{% data reusables.secret-scanning.partner-secret-list-private-repo %} +{% endif %} {% ifversion secret-scanning-push-protection %} -## プッシュ保護でサポートされるシークレット +## Supported secrets for push protection -プッシュ保護として {% data variables.product.prodname_secret_scanning_caps %} は、現在、次のサービス プロバイダーによって発行されたシークレットのリポジトリをスキャンします。 +{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers. {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} {% data reusables.secret-scanning.secret-list-private-push-protection %} {% endif %} -## 参考資料 - -- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」 -- 「[アカウントとデータを安全に保つ](/github/authenticating-to-github/keeping-your-account-and-data-secure)」{%- ifversion fpt or ghec %} -- [{% data variables.product.prodname_secret_scanning_caps %} パートナー プログラム](/developers/overview/secret-scanning-partner-program){%- else %} -- [{% data variables.product.prodname_secret_scanning_caps %} パートナー プログラム](/free-pro-team@latest/developers/overview/secret-scanning-partner-program) ({% data variables.product.prodname_ghe_cloud %} ドキュメント){% endif %} +## Further reading + +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" +{%- ifversion fpt or ghec %} +- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)" +{%- else %} +- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/free-pro-team@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation +{% endif %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 1df68e4964e0..17a06095ae44 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,12 +13,12 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace -ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158662' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188257' --- codespace はさまざまな方法で削除できます。たとえば、ターミナルで {% data variables.product.prodname_cli %} を使用して、{% data variables.product.prodname_vscode %} で、または、お使いの Web ブラウザーで削除できます。 この記事のタブを使用し、codespace を削除する各種方法の手順を表示してください。 @@ -135,5 +135,5 @@ gh codespace delete --repo octo-org/octo-repo --days 7 REST API を使用して組織の codespace を削除することもできます。 詳細については、[codespace 組織](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)に関する記事を参照してください。 ## 参考資料 -- 「[codespace のライフサイクル](/codespaces/developing-in-codespaces/the-codespace-lifecycle)」 +- 「[codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」 - [codespace の自動削除の構成](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) 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 a4f795849996..0063e633a4b0 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159014' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188289' --- diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index 225c8b3fab8c..692aa05569b6 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -10,12 +10,12 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace -ms.openlocfilehash: e7a35c1a7b3a251094bf69fcd401291b69d03eae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159006' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188297' --- {% jetbrains %} @@ -23,7 +23,7 @@ ms.locfileid: '148159006' {% endjetbrains %} -{% data variables.product.prodname_dotcom_the_website %} 上、JetBrains IDE 内、{% data variables.product.prodname_vscode %} 内、または {% data variables.product.prodname_cli %} を使って、アクティブなまたは停止している codespace をもう一度開くことができます。 削除された codespace を開き直すことはできません。 詳しくは、「[codespace のライフサイクル](/codespaces/developing-in-codespaces/the-codespace-lifecycle)」を参照してください。 +{% data variables.product.prodname_dotcom_the_website %} 上、JetBrains IDE 内、{% data variables.product.prodname_vscode %} 内、または {% data variables.product.prodname_cli %} を使って、アクティブなまたは停止している codespace をもう一度開くことができます。 削除された codespace を開き直すことはできません。 詳しくは、「[codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」を参照してください。 自分のすべての codespace は、[github.com/codespaces](https://github.com/codespaces) の [あなたの codespace] ページで確認できます。 このページからは、次のことを行うことができます。 diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index 6602cce6b44f..b0eed3503415 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Stopping and starting a codespace -intro: 'You can stop and start your codespace to save resources and to pause work.' +title: codespace の停止と開始 +intro: codespace を停止して開始すると、リソースを保存し、作業を一時停止することができます。 versions: fpt: '*' ghec: '*' @@ -10,28 +10,33 @@ topics: - Fundamentals - Developer shortTitle: Stop a codespace +ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188249' --- - {% jetbrains %} {% data reusables.codespaces.codespaces-jetbrains-beta-note %} {% endjetbrains %} -## About stopping and starting a codespace +## codespace の停止と開始について {% data reusables.codespaces.stopping-a-codespace %} -Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces. +codespaces は、作成またはアクセスした場所に関係なく、 https://github.com/codespaces で表示および管理できます。 -## Stopping a codespace +## codespace を停止する {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} - 1. To the right of the codespace you want to stop, click the elipsis (**...**). - 1. Click **Stop codespace**. - ![Screenshot of option to stop a codespace](/assets/images/help/codespaces/stop-codespace-webui.png) + 1. 停止する codespace の右側にある省略記号 ( **...** ) をクリックします。 + 1. **[codespace の停止]** をクリックします。 + ![codespace を停止するオプションのスクリーンショット](/assets/images/help/codespaces/stop-codespace-webui.png) {% endwebui %} @@ -39,7 +44,7 @@ Regardless of where you created or access your codespaces, you can view and mana {% data reusables.cli.cli-learn-more %} - To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed. + codespace を停止するには、`gh codespace stop` サブコマンドを使用し、表示される一覧から停止する codespace を選びます。 ```shell{:copy} gh codespace stop @@ -50,38 +55,38 @@ Regardless of where you created or access your codespaces, you can view and mana {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to stop. +1. 「`stop`」と入力し、オプションの一覧から **[codespace: codespace の停止]** を選びます。 +1. codespace の一覧で、停止する codespace を選びます。 {% endvscode %} {% jetbrains %} -You can stop a codespace from the "Your codespaces" page (see [the web browser instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) or by using {% data variables.product.prodname_cli %} (see [the CLI instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)). +codespace は、[Your codespaces] ページから ([Web ブラウザーの手順](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)を参照)、または {% data variables.product.prodname_cli %} を使って ([CLI の手順](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)を参照) 停止できます。 {% endjetbrains %} -## Restarting a codespace +## codespace の再起動 {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} -1. Click the name of the codespace you want to restart. -![Screenshot of stopped codespaces](/assets/images/help/codespaces/restart-codespace-webui.png) +1. 再起動する codespace の名前をクリックします。 +![停止した codespace のスクリーンショット](/assets/images/help/codespaces/restart-codespace-webui.png) {% endwebui %} {% cli %} -When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser. +codespace を再起動するとき、{% data variables.product.prodname_vscode %} で開くか、ブラウザーで開くかを選ぶことができます。 - - To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed. + - codespace を再起動し、{% data variables.product.prodname_vscode %} で開くには、`gh codespace code` サブコマンドを使用し、表示される一覧から再起動する codespace を選びます。 ```shell{:copy} gh codespace code ``` - - To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed. + - codespace を再起動してブラウザーで開くには、`gh codespace open --web` サブコマンドを使用し、表示される一覧から再起動する codespace を選びます。 ```shell{:copy} gh codespace open --web @@ -92,8 +97,8 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to restart. +1. 「`connect`」と入力し、オプションの一覧から **[codespaces: codespace に接続]** を選びます。 +1. codespace の一覧で、再起動する codespace を選びます。 {% endvscode %} @@ -103,6 +108,6 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% endjetbrains %} -## Further reading +## 参考資料 -- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" +- 「[codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」 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 ab69b69208d1..de492b4128cc 100644 --- a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md +++ b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md @@ -9,12 +9,12 @@ versions: type: quick_start topics: - Codespaces -ms.openlocfilehash: 5f97a137ec09191d5cbaa9c10aa280e10f11bbc0 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 01e4f3990cc47f61678811f7c4a77b86626fd8a5 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158646' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188265' --- {% data variables.product.prodname_github_codespaces %} は、クラウドベースのインスタント開発環境であり、コンテナーを使用して開発用の共通言語、ツール、ユーティリティを提供します。 また、{% data variables.product.prodname_github_codespaces %} は構成可能で、プロジェクトに合わせてカスタマイズされた開発環境を作成できます。 プロジェクト用のカスタム開発環境を構成することにより、プロジェクトのすべてのユーザーに対して繰り返し可能な codespace 構成を作成できます。 @@ -161,4 +161,4 @@ JetBrains IDE で codespace を操作する場合は、JetBrains Marketplace か - 「[Organization での {% data variables.product.prodname_github_codespaces %} の有効化について](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)」 - 「[Organization で {% data variables.product.prodname_github_codespaces %} のコストを管理する](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)」 - 「[開発コンテナー構成をリポジトリに追加する](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)」 -- 「[codespace のライフサイクル](/codespaces/developing-in-codespaces/the-codespace-lifecycle)」 +- 「[codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」 diff --git a/translations/ja-JP/content/codespaces/getting-started/index.md b/translations/ja-JP/content/codespaces/getting-started/index.md index 67468619ec98..3f491a9faa8f 100644 --- a/translations/ja-JP/content/codespaces/getting-started/index.md +++ b/translations/ja-JP/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160252' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188273' --- diff --git a/translations/ja-JP/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/ja-JP/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..2d55de178e9d --- /dev/null +++ b/translations/ja-JP/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: codespace のライフサイクル +intro: '{% data variables.product.prodname_github_codespaces %} 環境で開発し、codespace のライフサイクル全体にわたってデータを維持できます。' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188370' +--- +## codespace のライフサイクルについて + +codespace のライフサイクルは、codespace を作成するときに開始され、削除すると終了します。 実行中のプロセスに影響を与えることなく、アクティブな codespace を切断して再接続できます。 プロジェクトに加えた変更を失うことなく、codespace を停止して再起動できます。 + +## codespace を作成する + +プロジェクトで作業する場合は、新しい codespace を作成するか、既存の codespace を開くかを選択できます。 {% data variables.product.prodname_github_codespaces %} で開発するたびに、リポジトリのブランチから新しい codespace を作成することも、機能の実行時間の長い codespace を保持することもできます。 {% data reusables.codespaces.starting-new-project-template %} 詳細については、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)」と「[テンプレートから codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)」を参照してください。 + +{% data reusables.codespaces.max-number-codespaces %} 同様に、アクティブな codespace の最大数に達してからさらに起動しようとすると、アクティブな codespace のいずれかを停止するように求められます。 + +プロジェクトで作業するたびに新しい codespace を作成する場合は、新しいコミットがすべて {% data variables.product.prodname_dotcom %} で行われるように、変更を定期的にプッシュする必要があります。 プロジェクトで実行時間の長い codespace を使用する場合は、環境で一番新しいコミットが行われるように、codespace で作業を開始するたびにリポジトリの既定のブランチからプルする必要があります。 このワークフローは、ローカル コンピューターでプロジェクトを操作していた場合とよく似ています。 + +{% data reusables.codespaces.prebuilds-crossreference %} + +## codespace で変更を保存する + +Web 経由で codespace に接続すると、Web エディターに対して自動保存が自動的に有効になり、遅延後に変更を保存するように構成されます。 デスクトップで実行されている {% data variables.product.prodname_vscode %} を介して codespace に接続する場合は、自動保存を有効にする必要があります。 詳細については、{% data variables.product.prodname_vscode %} のドキュメントの「[保存/自動保存](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)」を参照してください。 + +作業はクラウド内の仮想マシンに保存されます。 codespace を閉じて停止し、後で保存した作業に戻ることができます。 保存されていない変更がある場合、エディターは終了する前に保存するように求められます。 ただし、codespace が削除されると、作業も削除されます。 作業を永続化するには、変更をコミットしてリモート リポジトリにプッシュするか、テンプレートから codespace を作成した場合は、新しいリモート リポジトリに作業を発行する必要があります。 詳細については、「[Codespace でソース コントロールを使用する](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)」を参照してください + +## {% data variables.product.prodname_github_codespaces %} のタイムアウト + +対話なしで codespace を実行したままにした場合、または明示的に停止せずに codespace を終了した場合、codespace は一定期間非アクティブになった後にタイムアウトし、実行を停止します。 既定では、非アクティブ状態になって 30 分が経過した後に、codespace がタイムアウトしますが、作成する新しい codespace のタイムアウト期間をカスタマイズできます。 codespace の既定のタイムアウト期間の設定について詳しくは、「[{% data variables.product.prodname_github_codespaces %} のタイムアウト期間を設定する](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)」をご覧ください。 codespace の停止の詳細については、「[codespace を停止する](#stopping-a-codespace)」参照してください。 + +codespace がタイムアウトすると、変更が最後に保存された時点からデータが保持されます。 詳細については、「[codespace の変更を保存する](#saving-changes-in-a-codespace)」を参照してください。 + +## Codespace を再構築する + +codespace をリビルドして、開発コンテナーの構成に変更を実装できます。 ほとんどの場合、codespace を再構築する代わりに、新しい codespace を作成できます。 既定では、codespace をリビルドすると、{% data variables.product.prodname_github_codespaces %} によりキャッシュからイメージが再利用され、再構築プロセスが高速化されます。 または、完全なリビルドを実行できます。これにより、キャッシュがクリアされ、新しいイメージを使用してコンテナーが再構築されます。 + +詳細については、「[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)」および「[コンテナーの完全なリビルドの実行](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)」を参照してください。 + +## codespace を停止する + +{% data reusables.codespaces.stopping-a-codespace %} 詳細については、「[codespace の停止と開始](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)」を参照してください。 + +## codespace を削除する + +特定のタスクの codespace を作成し、変更をリモート ブランチにプッシュした後で、その codespace を安全に削除できます。 + +プッシュしていない Git コミットと一緒に codespace を削除しようとすると、リモート ブランチにプッシュされていない変更があることがエディターから通知されます。 必要な変更をプッシュしてから codespace を削除することも、codespace とコミットしていない変更をそのまま削除することもできます。 新しい codespace を作成せずに、コードを新しいブランチにエクスポートすることもできます。 詳細については、「[ブランチへの変更のエクスポート](/codespaces/troubleshooting/exporting-changes-to-a-branch)」を参照してください。 + +指定した期間停止され、非アクティブなままになっている Codespace は自動的に削除されます。 既定では、非アクティブな codespace は 30 日後に削除されますが、codespace の保持期間はカスタマイズできます。 詳しい情報については、「[codespace の自動削除を構成する](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)」をご覧ください。 + +codespace を作成すると、アクティブか停止かに関係なく、削除されるまでストレージ料金が発生し続けます。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)」をご覧ください。 codespace を削除しても、{% data variables.product.prodname_github_codespaces %} の現在の課金対象金額は減少しません。これは、毎月の請求期間の間に累積されます。 詳細については、「[{% data variables.product.prodname_github_codespaces %} の使用状況を表示する](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)」を参照してください。 + +codespace の削除について詳しくは、「[codespace を削除する](/codespaces/developing-in-codespaces/deleting-a-codespace)」を参照してください。 + +## {% data variables.product.prodname_github_codespaces %} の使用中に接続が失われる + +{% data variables.product.prodname_github_codespaces %} はクラウドベースの開発環境であり、インターネット接続が必要です。 codespace で作業しているときにインターネットへの接続が失われると、その codespace にアクセスできなくなります。 ただし、コミットされていない変更はすべて保存されます。 インターネット接続に再度アクセスできるようになると、切断されたときとまったく同じ状態で codespace に接続できます。 インターネット接続が不安定な場合は、頻繁に変更をコミットしてプッシュする必要があります。 + +オフラインで作業することが多いことがわかっている場合は、{% data variables.product.prodname_vscode_shortname %} の ["Dev Containers" 拡張機能](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)で `devcontainer.json` ファイルを使用して、リポジトリのローカル開発コンテナーをビルドしてアタッチできます。 詳細については、{% data variables.product.prodname_vscode %} ドキュメントの「[コンテナー内で開発する](https://code.visualstudio.com/docs/remote/containers)」を参照してください。 diff --git a/translations/ja-JP/content/codespaces/index.md b/translations/ja-JP/content/codespaces/index.md index 0b922a1d4ae6..1c8d5ad5d2e6 100644 --- a/translations/ja-JP/content/codespaces/index.md +++ b/translations/ja-JP/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160435' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188305' --- 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 d755ec57f7ab..046229da0c1b 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 @@ -1,6 +1,6 @@ --- -title: Introduction to dev containers -intro: 'When you work in a codespace, the environment you are working in is created using a development container, or dev container, hosted on a virtual machine.' +title: 開発コンテナーの概要 +intro: codespace で作業する場合、作業している環境は、仮想マシンでホストされている開発コンテナーを使用して作成されます。 permissions: People with write permissions to a repository can create or edit the codespace configuration. redirect_from: - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project @@ -16,71 +16,76 @@ topics: - Codespaces - Set up - Fundamentals +ms.openlocfilehash: 646f8068e68040f1d12f8155c3ba9e2bdb84c2ca +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185092' --- +## 開発コンテナについて -## About dev containers +開発コンテナーは、完全な機能を備えた開発環境を提供するように特別に構成された Docker コンテナーです。 codespace で作業を行うときは常に、仮想マシンで開発コンテナーを使用します。 -Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine. +リポジトリの開発コンテナーを構成できるので、そのリポジトリ用に作成された codespace によって、特定のプロジェクトの作業を行うために必要なすべてのツールとランタイムを備えた、カスタマイズされた開発環境が提供されます。 リポジトリで構成を定義しない場合、{% data variables.product.prodname_github_codespaces %} で既定の構成が使用されます。この構成には、チームがプロジェクトで開発を行うために必要な可能性がある一般的なツールの多くが含まれています。 詳しくは、「[既定の開発コンテナー構成の使用](#using-the-default-dev-container-configuration)」をご覧ください。 -You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +開発コンテナーの構成ファイルは、リポジトリの `.devcontainer` ディレクトリに含まれています。 {% data variables.product.prodname_vscode %} を使用して、構成ファイルを追加できます。 さまざまなプロジェクト タイプ向けにあらかじめ定義されている構成の中から選択できます。 これらを追加の構成なしで使うこともできますし、構成を編集して生成される開発環境を改善することもできます。 詳しくは、「[事前定義済みの開発コンテナー構成の使用](#using-a-predefined-dev-container-configuration)」をご覧ください。 -The configuration files for a dev container are contained in a `.devcontainer` directory in your repository. You can use {% data variables.product.prodname_vscode %} to add configuration files for you. You can choose from a selection of predefined configurations for various project types. You can use these without further configuration, or you can edit the configurations to refine the development environment they produce. For more information, see "[Using a predefined dev container configuration](#using-a-predefined-dev-container-configuration)." +または、独自のカスタム構成ファイルを追加することもできます。 詳しくは、「[カスタム開発コンテナー構成の作成](#creating-a-custom-dev-container-configuration)」をご覧ください。 -Alternatively, you can add your own custom configuration files. For more information, see "[Creating a custom dev container configuration](#creating-a-custom-dev-container-configuration)." +リポジトリ用に単一の開発コンテナー構成を定義したり、異なるブランチ用に異なる構成を定義したり、複数の構成を定義したりできます。 複数の構成を利用できる場合、ユーザーは codespace を作成するときに好みの構成を選択できます。 これは、異なるプログラミング言語のソース コードを含む大規模なリポジトリの場合や、さまざまなプロジェクトがある場合に特に役立ちます。 構成の選択肢を作成することで、異なるチームが、実行する作業用に適切に設定された codespace で作業できるようになります。 -You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing. - -When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)." +テンプレートから codespace を作成する場合は、ワークスペース内の 1 つ以上の開発コンテナー構成ファイルを使用して開始できます。 環境をさらに構成するには、これらのファイルの設定を追加または削除し、コンテナーをリビルドして、作業中の codespace に変更を適用します。 {% data variables.product.product_name %} 上のリポジトリに codespace を発行すると、そのリポジトリから作成されたすべての codespace で、定義した構成が共有されます。 詳しい情報については、「[codespace に構成変更を適用する](#applying-configuration-changes-to-a-codespace)」と「[テンプレートから codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)」をご覧ください。 ### devcontainer.json -The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file. +開発コンテナー構成のプライマリ ファイルは `devcontainer.json` ファイルです。 このファイルを使用して、リポジトリ用に作成される codespace の環境を決定できます。 このファイルの内容によって、フレームワーク、ツール、拡張機能、ポート フォワーディングを含めることができる開発コンテナーが定義されます。 通常、`devcontainer.json` ファイルには Dockerfile (通常は `devcontainer.json` ファイルと一緒に配置します) への参照が含まれています。 -If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +`devcontainer.json` ファイルを含まないリポジトリから codespace を作成する場合、または {% data variables.product.company_short %} の空のテンプレートから開始する場合は、既定の開発コンテナー構成が使用されます。 詳しくは、「[既定の開発コンテナー構成の使用](#using-the-default-dev-container-configuration)」をご覧ください。 -The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`. +通常、`devcontainer.json` ファイルはリポジトリの `.devcontainer` ディレクトリに配置します。 または、リポジトリのルートに直接配置することもできます。その場合は、ファイル名の先頭をピリオドにする必要があります (`.devcontainer.json`)。 -If you want to have a choice of dev container configurations in your repository, any alternatives to the `.devcontainer/devcontainer.json` (or `.devcontainer.json`) file must be located in their own subdirectory at the path `.devcontainer/SUBDIRECTORY/devcontainer.json`. For example, you could have a choice of two configurations: +リポジトリで開発コンテナー構成を選択できるようにする場合は、`.devcontainer/devcontainer.json` (または `.devcontainer.json`) ファイルに代わるファイルを `.devcontainer/SUBDIRECTORY/devcontainer.json` というパスの独自のサブディレクトリに配置する必要があります。 たとえば、次の 2 つの構成から選ぶようにすることができます。 * `.devcontainer/database-dev/devcontainer.json` * `.devcontainer/gui-dev/devcontainer.json` -When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory. +リポジトリに複数の `devcontainer.json` ファイルがある場合、各 codespace はいずれかの構成のみから作成されます。 `devcontainer.json` ファイル間で設定をインポートまたは継承することはできません。 カスタム サブディレクトリの `devcontainer.json` ファイルに依存ファイル (Dockerfile など) や `devcontainer.json` ファイル内のコマンドによって実行されるスクリプトがある場合は、これらのファイルを同じサブディレクトリに一緒に配置することをお勧めします。 -For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." +codespace の作成時にお好みの開発コンテナー構成を選ぶ方法については、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)」をご覧ください。 {% data reusables.codespaces.more-info-devcontainer %} -#### How to use the devcontainer.json +#### devcontainer.json の使用方法 -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. +`devcontainer.json` ファイルは、"パーソナル化" ではなく "カスタマイズ" を提供するものだと考えると有益です。 コードベースで作業するすべてのユーザーが必要とするもののみを開発環境の標準要素として含め、個人の好みのものは含めないようにする必要があります。 リンターのようなものは標準化して、すべてのユーザーにインストールするよう求めることが適切なので、`devcontainer.json` ファイルに含めることができます。 ユーザー インターフェイスのデコレーターやテーマなどは、`devcontainer.json` ファイルに含めるべきでない個人的な選択肢です。 -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)." +ドットファイルと Settings Sync を使用すると、codespace をパーソナル化できます。詳しくは、「[アカウントの {% data variables.product.prodname_github_codespaces %} をパーソナライズする](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)」をご覧ください。 ### Dockerfile -You can add a Dockerfile as part of your dev container configuration. +開発コンテナー構成の一部として Dockerfile を追加できます。 -The Dockerfile is a text file that contains the instructions needed to create a Docker container image. This image is used to generate a development container each time someone creates a codespace using the `devcontainer.json` file that references this Dockerfile. The instructions in the Dockerfile typically begin by referencing a parent image on which the new image that will be created is based. This is followed by commands that are run during the image creation process, for example to install software packages. +Dockerfile は Docker コンテナー イメージを作成するために必要な命令が含まれているテキスト ファイルです。 このイメージは、この Dockerfile を参照する `devcontainer.json` ファイルを使用して codespace を作成するたびに、開発コンテナーの生成に使用されます。 Dockerfile 内の命令は通常、作成される新しいイメージの基になる親イメージを参照することから始まります。 その後に、ソフトウェア パッケージのインストールなど、イメージの作成プロセス中に実行されるコマンドが続きます。 -The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced. +開発コンテナーの Dockerfile は通常、参照元の `devcontainer.json` と共に `.devcontainer` フォルダーに配置します。 {% note %} -**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. For more information, see "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +**注**: Dockerfile を使用する代わりに、`image` プロパティを `devcontainer.json` ファイルで使用して、使用する既存のイメージを直接参照できます。 ここで指定するイメージは、設定されている Organization のイメージ ポリシーで許可されている必要があります。 詳しい情報については、「[codespace の基本イメージを制限する](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)」をご覧ください。 Dockerfile もイメージも見つからない場合は、既定のコンテナー イメージが使用されます。 詳しくは、「[既定の開発コンテナー構成の使用](#using-the-default-dev-container-configuration)」をご覧ください。 {% endnote %} -#### Simple Dockerfile example +#### シンプルな Dockerfile の例 -The following example uses four instructions: +次の例では、4 つの命令を使用します。 -`ARG` defines a build-time variable. +`ARG` は、ビルド時の変数を定義します。 -`FROM` specifies the parent image on which the generated Docker image will be based. +`FROM` は、生成される Docker イメージの基になる親イメージを指定します。 -`COPY` copies a file and adds it to the filesystem. +`COPY` は、ファイルをコピーしてファイルシステムに追加します。 -`RUN` updates package lists and runs a script. You can also use a `RUN` instruction to install software, as shown by the commented out instructions. To run multiple commands, use `&&` to combine the commands into a single `RUN` statement. +`RUN` は、パッケージの一覧を更新して、スクリプトを実行します。 コメント アウトされた命令で示されているように、`RUN` 命令を使用してソフトウェアをインストールすることもできます。 複数のコマンドを実行するには、`&&` を使用して、コマンドを 1 つの `RUN` ステートメントに結合します。 ```Dockerfile{:copy} ARG VARIANT="16-buster" @@ -97,11 +102,11 @@ COPY library-scripts/github-debian.sh /tmp/library-scripts/ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh ``` -For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation. +Dockerfile の命令について詳しくは、Docker のドキュメントの「[Dockerfile リファレンス](https://docs.docker.com/engine/reference/builder)」をご覧ください。 -#### Using a Dockerfile +#### Dockerfile の使用 -To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property. +開発コンテナー構成の一部として Dockerfile を使用するには、`devcontainer.json` ファイル内で `dockerfile` プロパティを使用して参照します。 ```json{:copy} { @@ -111,134 +116,134 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo } ``` -Various options are available to you if you want to use existing container orchestration in your dev container. For more information, see the "Orchestration options" section of the [Specification](https://containers.dev/implementors/spec/#orchestration-options) on the Development Containers website. +開発コンテナー内で既存のコンテナー オーケストレーションを使用する場合は、さまざまなオプションを使用できます。 詳しい情報については、開発コンテナーの Web サイトで[仕様](https://containers.dev/implementors/spec/#orchestration-options)の「オーケストレーション オプション」セクションをご覧ください。 -## Using the default dev container configuration +## 既定の開発コンテナー構成の使用 -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace using a default Linux image. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs. +リポジトリで構成を定義しない場合は、{% data variables.product.prodname_dotcom %} が既定の Linux イメージを使用して codespace を作成します。 この Linux イメージには、Python、Node、PHP、Java、Go、C++、Ruby、.NET Core/C# などの一般的な言語のランタイム バージョンが多数含まれています。 これらの言語の最新または LTS リリースが使用されます。 JupyterLab や Conda など、データ サイエンスと機械学習をサポートするツールもあります。 イメージには、Git、GitHub CLI、yarn、openssh、vim などの他の開発者ツールやユーティリティも含まれています。 含まれているすべての言語、ランタイム、ツールを確認するには、codespace ターミナル内で `devcontainer-info content-url` コマンドを使用し、コマンドで出力された URL にアクセスしてください。 -For information about what's included in the default Linux image, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository. +既定の Linux イメージに何が含まれているかについては、[`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) リポジトリをご覧ください。 -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides. +{% data variables.product.prodname_github_codespaces %} が提供する言語とツールを使用する小さなプロジェクトで作業している場合は、既定の構成が適しています。 -## Using a predefined dev container configuration +## 事前定義済みの開発コンテナー構成の使用 -If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. +{% data variables.product.prodname_vscode %} または Web ブラウザーで {% data variables.product.prodname_codespaces %} を使用する場合は、定義済みの構成の一覧から選ぶことで、リポジトリの開発コンテナー構成を作成できます。 これらの構成は、特定のプロジェクト タイプの共通セットアップを提供するものです。また、適切なコンテナー オプション、{% data variables.product.prodname_vscode %} 設定、インストールする必要がある {% data variables.product.prodname_vscode %} 拡張機能が構成で既に用意されているので、短時間で使い始めることができます。 -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository. +追加の拡張性が必要な場合は、事前定義済みの設定を使用することをお勧めします。 事前定義済みの構成から始めて、プロジェクトに合わせて修正することもできます。 定義済みの開発コンテナーの定義について詳しくは、[`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) リポジトリをご覧ください。 -You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar. +事前定義済みの開発コンテナー構成は、codespace での作業中、またはローカルでのリポジトリの作業中に追加できます。 ローカルで作業していて、codespace に接続されていないときに {% data variables.product.prodname_vscode_shortname %} でこれを行うには、"Dev Containers" 拡張機能がインストールされ、有効になっている必要があります。 この拡張機能について詳しくは、「[{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)」をご覧ください。 次の手順では、codespace を使用している場合のプロセスについて説明します。 codespace に接続していない場合の {% data variables.product.prodname_vscode_shortname %} の手順は非常によく似ています。 {% data reusables.codespaces.command-palette-container %} -1. Click the definition you want to use. +1. 使用する定義をクリックします。 - ![Screenshot of a list of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) + ![定義済みのコンテナー定義の一覧のスクリーンショット](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)." -1. Click **OK**. +1. プロンプトに従って定義をカスタマイズします。 定義をカスタマイズするためのオプションの詳細については、「[`devcontainer.json` ファイルへの追加機能の追加](#adding-additional-features-to-your-devcontainerjson-file)」を参照してください。 +1. **[OK]** をクリックします。 - ![Screenshot of the OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) + ![[OK] ボタンのスクリーンショット](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." +1. codespace で作業している場合は、ウィンドウの右下にあるメッセージで **[今すぐリビルド]** をクリックして変更を適用します。 コンテナーのリビルドの詳細については、「[構成への変更の適用](#applying-configuration-changes-to-a-codespace)」を参照してください。 - ![Screenshot of a prompt to 'Rebuild now'](/assets/images/help/codespaces/rebuild-prompt.png) + ![[今すぐリビルド] を確認するスクリーンショット](/assets/images/help/codespaces/rebuild-prompt.png) -### Adding additional features to your `devcontainer.json` file +### `devcontainer.json` ファイルへの追加機能の追加 -{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)." +{% data reusables.codespaces.about-features %}詳しい情報については、「[`devcontainer.json` ファイルへの機能の追加](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)」をご覧ください。 -## Creating a custom dev container configuration +## カスタム開発コンテナー構成の作成 -If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file. +事前定義済みの構成がどれもニーズを満たさない場合は、独自の `devcontainer.json` ファイルを記述してカスタム構成を作成できます。 -* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository. -* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory. +* リポジトリから codespace を作成するすべてのユーザーが使用する単一の `devcontainer.json` ファイルを追加する場合は、リポジトリのルートにある `.devcontainer` ディレクトリ内にファイルを作成します。 +* ユーザーが構成を選択できるようにする場合は、複数のカスタム `devcontainer.json` ファイルを作成して、それぞれを `.devcontainer` ディレクトリの個別のサブディレクトリ内に配置できます。 {% note %} - **Notes**: - - You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. - - {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." + **注**: + - `devcontainer.json` ファイルは、`.devcontainer` より 2 レベル以上下位のディレクトリに配置することはできません。 たとえば、`.devcontainer/teamA/devcontainer.json` にあるファイルは機能しますが、`.devcontainer/teamA/testing/devcontainer.json` の場合は機能しません。 + - {% data reusables.codespaces.configuration-choice-templates %}詳しい情報については、「[{% data variables.product.prodname_github_codespaces %} のテンプレート リポジトリを設定する](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)」をご覧ください。 {% endnote %} - If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." + リポジトリで複数の `devcontainer.json` ファイルが見つかった場合は、それらが codespace の作成オプション ページに一覧表示されます。 詳しくは、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)」を参照してください。 - ![Screenshot of a choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + ![構成ファイルの選択肢のスクリーンショット](/assets/images/help/codespaces/configuration-file-choice.png) -### Adding a `devcontainer.json` file +### `devcontainer.json` ファイルの追加 -If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}. -1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. -1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**. +リポジトリにまだ `devcontainer.json` ファイルがない場合は、{% data variables.product.prodname_dotcom_the_website %} からそれをすばやく追加できます。 +1. 自分のリポジトリに移動し、 **[{% octicon "code" aria-label="The code icon" %} コード]** ドロップダウンをクリックします。 +1. **[Codespaces]** タブで省略記号 ( **...** ) をクリックし、次に **[開発コンテナーの構成]** を選択します。 - ![Screenshot of the Code dropdown, with "Configure dev container" highlighted](/assets/images/help/codespaces/configure-dev-container.png) + ![[コード] ドロップダウンのスクリーンショット。[開発コンテナーの構成] が強調表示されています](/assets/images/help/codespaces/configure-dev-container.png) -A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)." +新しい `.devcontainer/devcontainer.json` ファイルがエディターで開きます。 ファイルには、新しいツール、ライブラリ、またはランタイムを追加できる `features` オブジェクトなど、いくつかの初期プロパティが含まれます。 詳しい情報については、「[ファイルへの `devcontainer.json` 機能の追加](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)」をご覧ください。 -If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev. +リポジトリに既に 1 つ以上の `devcontainer.json` ファイルが含まれている場合は、 **[開発コンテナーの構成]** をクリックすると、containers.dev の`devcontainer.json`仕様 [に従って、優先順位が最も高い既存の](https://containers.dev/implementors/spec/#devcontainerjson) ファイルが開きます。 -### Default configuration selection during codespace creation +### codespace の作成時における既定の構成の選択 -If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default. +`.devcontainer/devcontainer.json` または `.devcontainer.json` が存在する場合は、codespace を作成するときに使用可能な構成ファイルの一覧でそれが既定の選択になります。 どちらのファイルも存在しない場合は、既定の開発コンテナー構成が既定で選択されます。 -![Screenshot of the default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png) +![既定の構成の選択肢が選択されたスクリーンショット](/assets/images/help/codespaces/configuration-file-choice-default.png) -### Editing the devcontainer.json file +### devcontainer.json ファイルの編集 -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +`devcontainer.json` ファイルでサポートされている構成キーを追加および編集して、codespace の環境の要素を指定できます (たとえば、どの {% data variables.product.prodname_vscode_shortname %} 拡張機能をインストールするか)。 {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +`devcontainer.json` ファイルは JSONC (コメント付きの JSON) 形式を使用して記述されます。 これにより、構成ファイル内にコメントを含めることができます。 詳しくは、{% data variables.product.prodname_vscode_shortname %} のドキュメントの「[{% data variables.product.prodname_vscode_shortname %} での JSON の編集](https://code.visualstudio.com/docs/languages/json#_json-with-comments)」をご覧ください。 {% note %} -**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors. +**注**: リンターを使用して `devcontainer.json` ファイルを検証する場合は、JSON ではなく JSONC に設定されていることを確認してください。正しく設定されていないと、コメントがエラーとして報告されます。 {% endnote %} -### Interface settings for {% data variables.product.prodname_vscode_shortname %} +### {% data variables.product.prodname_vscode_shortname %} のインターフェイス設定 -You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor. +{% data variables.product.prodname_vscode_shortname %} のインターフェイス設定は、ワークスペース、リモート [Codespaces]、ユーザーの 3 つのスコープで構成できます。 これらのスコープは、{% data variables.product.prodname_vscode_shortname %} 設定エディターで表示できます。 -![Screenshot showing the choice of scopes in the Settings editor](/assets/images/help/codespaces/scopes-for-vscode.png) +![設定エディターでのスコープの選択を示すスクリーンショット](/assets/images/help/codespaces/scopes-for-vscode.png) -If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User. +設定が複数のスコープで定義されている場合は、ワークスペース 設定が優先され、次にリモート [コードスペース] が優先され、次にユーザーが優先されます。 -You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places. +{% data variables.product.prodname_vscode_shortname %} の既定のインターフェイス設定は、2 か所で定義できます。 -* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace. -* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace. +* リポジトリの `.vscode/settings.json` ファイルで定義されたインターフェイス設定は、codespace でワークスペースをスコープとする設定として適用されます。 +* `devcontainer.json` ファイルの `settings` キーで定義されたインターフェイス設定は、codespace でリモート [Codespaces] をスコープとする設定として適用されます。 -## Applying configuration changes to a codespace +## codespace への構成変更の適用 -Changes to a configuration will be applied the next time you create a codespace. However, you can apply your changes to an existing codespace by rebuilding the container. You can do this within a codespace in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application, or you can use {% data variables.product.prodname_cli %}. +構成に対する変更は、次回 codespace を作成するときに適用されます。 ただし、コンテナーをリビルドすることで、既存の codespace に変更を適用できます。 これは、{% data variables.product.prodname_vscode_shortname %} の Web クライアントまたはデスクトップ アプリケーションの codespace 内で行うか、{% data variables.product.prodname_cli %} を使用することができます。 -### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application +### {% data variables.product.prodname_vscode_shortname %} Web クライアントまたはデスクトップ アプリケーションで開発コンテナーをリビルドする {% data reusables.codespaces.rebuild-command %} 1. {% data reusables.codespaces.recovery-mode %} - ![Screenshot of the error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) + ![回復モードに関するエラー メッセージのスクリーンショット](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. + - 作成ログを確認してエラーを診断するには、 **[View creation log]\(作成ログの表示\)** をクリックします。 + - ログで識別されたエラーを修正するには、`devcontainer.json` ファイルを更新します。 + - 変更を適用するには、コンテナーをリビルドします。 -### Using {% data variables.product.prodname_cli %} to rebuild a dev container +### {% data variables.product.prodname_cli %} を使用して開発コンテナーをリビルドする -If you've changed a dev container configuration outside of VS Code (for example, on {% data variables.product.prodname_dotcom_the_website %} or in a JetBrains IDE), you can use {% data variables.product.prodname_cli %} to rebuild the dev container for an existing codespace. +VS Code の外部 (たとえば、{% data variables.product.prodname_dotcom_the_website %} や JetBrains IDE など) で開発コンテナーの構成を変更した場合は、{% data variables.product.prodname_cli %} を使って既存の codespace の開発コンテナーをリビルドできます。 -1. In a terminal, enter the following command. +1. ターミナルで、次のコマンドを入力します。 ``` gh cs rebuild ``` - Your codespaces are listed. + codespace が一覧表示されます。 -1. Use the arrow keys on your keyboard to highlight the required codespace, then press Enter. +1. キーボードの方向キーを使って必要な codespace を強調表示してから、Enter キーを押します。 -## Further reading +## 参考資料 -- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" +- 「[codespaces の事前ビルド](/codespaces/prebuilding-your-codespaces)」 diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index 78d7a8ac2629..44aa07505cf3 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: リポジトリ用のプルリクエストテンプレートの作成 -intro: リポジトリにプルリクエストのテンプレートを追加すると、プロジェクトのコントリビューターはプルリクエストの本体にテンプレートの内容を自動的に見ることになります。 +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145090184' --- -詳細については、「[Issue と pull request テンプレートについて](/articles/about-issue-and-pull-request-templates)」を参照してください。 -サポートしているどのフォルダーでも *PULL_REQUEST_TEMPLATE/* サブディレクトリを作成し、pull request テンプレートを複数含めることができます。また、`template` クエリ パラメーターで pull request の本文に使用するテンプレートを指定できます。 詳細については、「[クエリ パラメーターを使用して pull request を作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)」を参照してください。 +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -ご自分の Organization {% ifversion fpt or ghes or ghec %}または個人用アカウント{% endif %}向けに既定の pull request を作成することができます。 詳細については、「[既定のコミュニティ正常性ファイルの作成](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## プルリクエストテンプレートの追加 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. ファイル名フィールドで: - - pull request テンプレートをリポジトリのルート ディレクトリで表示するには、pull request テンプレートに `pull_request_template.md` という名前を付けます。 - ![ルート ディレクトリの新しい pull request テンプレート名](/assets/images/help/repository/pr-template-file-name.png) - - pull request テンプレートをリポジトリの `docs` ディレクトリで表示するには、pull request テンプレートに `docs/pull_request_template.md` という名前を付けます。 - ![docs ディレクトリの新しい pull request テンプレート](/assets/images/help/repository/pr-template-file-name-docs.png) - - ファイルを非表示のディレクトリに格納するには、pull request テンプレートを `.github/pull_request_template.md` という名前にします。 - ![非表示のディレクトリの新しい pull request テンプレート](/assets/images/help/repository/pr-template-hidden-directory.png) - - pull request テンプレートを複数作成し、`template` クエリ パラメーターを使用して pull request の本文を埋めるテンプレートを指定するには、 *.github/PULL_REQUEST_TEMPLATE/* と入力し、続けてお使いの pull request テンプレートの名前を入力します。 たとえば、「 `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md` 」のように入力します。 ルートまたは `docs/` ディレクトリ内の `PULL_REQUEST_TEMPLATE` サブディレクトリに複数の pull request テンプレートを格納することもできます。 詳細については、[クエリ パラメーターを使用した Issue と pull request の自動化](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)に関するページを参照してください。 - ![非表示ディレクトリ内の新しい複数の pull request テンプレート](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. 新しいファイルの本文にプルリクエストテンプレートを追加します。 そこに盛り込むべき項目として、以下のようなものがあります: - - ご自分のリポジトリ内の [関連する Issue への参照](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。 - - プルリクエストで提案された変更の説明。 - - レビューを行っている提案された変更の責任を負う個人またはチームの [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)。 -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} テンプレートがリポジトリの既定のブランチにマージされると、コラボレーターがテンプレートを使用できるようになります。 +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## 参考資料 +## Further reading -- [Issue と pull request テンプレートについて](/articles/about-issue-and-pull-request-templates) -- [クエリ パラメーターを使用した Issue および pull request の自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) -- [pull request の作成方法](/articles/creating-a-pull-request) +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" 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 fafd93d4dd63..3fe6ee9a0951 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 @@ -1,123 +1,125 @@ --- -title: Getting started with GitHub Copilot in a JetBrains IDE +title: JetBrains IDE で GitHub Copilot の使用を開始する shortTitle: JetBrains IDE -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.' +intro: '{% data variables.product.prodname_copilot %} を JetBrains IDE にインストールし、コメントやコードを記述するときに候補が表示されるようにする方法について説明します。' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: ae879b5834007a34ab0e3a7a45dcae4c1e31bc4f +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185060' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and JetBrains IDEs +## {% data variables.product.prodname_copilot %} と JetBrains IDE について {% data reusables.copilot.procedural-intro %} -If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux. +JetBrains IDE を使用すると、{% data variables.product.prodname_copilot %} からの候補をエディター内で直接表示し、取り入れることができます。 このガイドでは、macOS、Windows、or Linux 用の JetBrains IDE 内で {% data variables.product.prodname_copilot %} を使用する方法を示します。 -## Prerequisites +## 前提条件 {% data reusables.copilot.jetbrains-ides %} -## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE - -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 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) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. - - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**. - ![Screenshot of JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png) +## JetBrains IDE での {% data variables.product.prodname_copilot %} 拡張機能のインストール + +JetBrains IDE で {% data variables.product.prodname_copilot %} を使用するには、{% data variables.product.prodname_copilot %} 拡張機能をインストールする必要があります。 次の手順では、{% data variables.product.prodname_copilot %} プラグインを IntelliJ IDEA にインストールする手順について説明します。 サポートされている別の IDE にインストールする場合、手順が異なる可能性があります。 + +1. JetBrains IDE の **[ファイル]** メニュー (Windows の場合) または IDE for Mac の名前 (たとえば、**PyCharm**、**IntelliJ** など) で、 **[設定]** (Windows の場合) または **[環境設定]** (Mac の場合) をクリックします。 +2. **[設定] または [環境設定]** ダイアログ ボックスの左側のメニューで、 **[プラグイン]** をクリックします。 +3. **[設定] または [環境設定]** ダイアログ ボックスの上部にある **[Marketplace]** をクリックします。 検索バーで、「 **{% data variables.product.prodname_copilot %}** 」を検索し、 **[インストール]** をクリックします。 + ![Marketplace の検索のスクリーンショット](/assets/images/help/copilot/jetbrains-marketplace.png) +1. {% data variables.product.prodname_copilot %} がインストールされたら、 **[IDE を再起動する]** をクリックします。 +1. JetBrains IDE が再起動したら、 **[ツール]** メニューをクリックします。 **[{% data variables.product.prodname_copilot %}]** 、 **[{% data variables.product.prodname_dotcom %} にログイン]** の順にクリックします。 + ![JetBrains の [ツール] メニューのスクリーンショット](/assets/images/help/copilot/jetbrains-tools-menu.png) +1. デバイス コードをコピーしてデバイスの有効化ウィンドウを開くには、[{% data variables.product.prodname_dotcom %} にサインイン] ダイアログ ボックスで、 **[コピーして開く]** をクリックします。 + ![デバイス コードの [コピーして開く] のスクリーンショット](/assets/images/help/copilot/device-code-copy-and-open.png) +1. ブラウザーでデバイスの有効化ウィンドウが開きます。 デバイス コードを貼り付け、 **[続行]** をクリックします。 + + - Windows または Linux でコードを貼り付けるには、Ctrl + v キーを押します。 + - macOS でコードを貼り付けるには、command + v キーを押します。 +1. {% data variables.product.prodname_dotcom %} から、{% data variables.product.prodname_copilot %} に必要なアクセス許可が要求されます。 これらのアクセス許可を承認するには、 **[{% data variables.product.prodname_copilot %} プラグインの承認]** をクリックします。 +1. アクセス許可が承認されたら、JetBrains IDE によって確認が表示されます。 {% data variables.product.prodname_copilot %} の使用を開始するには、 **[OK]** をクリックします。 + ![JetBrains IDE によるアクセス許可の確認のスクリーンショット](/assets/images/help/copilot/jetbrains-ide-confirmation.png) -## Seeing your first suggestion +## 最初の候補を表示する {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} 次のサンプルは Java で記述されていますが、他の言語も同様に動作します。 {% data reusables.copilot.create-java-file %} -1. In the Java file, create a class by typing `class Test`. - {% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary. - ![Screenshot of the Java class body suggestion](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary. +1. Java ファイルで、「`class Test`」と入力してクラスを作成します。 + {% data variables.product.prodname_copilot %} によって、次に示すように、クラス本文の候補が灰色のテキストで自動的に表示されます。 実際に表示される候補はこのとおりではない場合があります。 + ![Java クラス本文の候補のスクリーンショット](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} +1. 関数本文の候補を表示するように {% data variables.product.prodname_copilot %} に要求するには、`main` 関数の角かっこの下に次の行を入力します。 実際に表示される候補はこのとおりではない場合があります。 {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} + ![Java 関数本文の候補のスクリーンショット](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} -{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code. +{% data variables.product.prodname_copilot %} は、コードのコンテキストとスタイルの一致を試みます。 提案されたコードはいつでも編集できます。 -## Seeing alternative suggestions +## 代替候補の表示 {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. -{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -{% data reusables.copilot.see-alternative-suggestions %} +1. 候補を表示するように {% data variables.product.prodname_copilot %} に要求するには、Java ファイルに次の行を入力します。 +{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | OS | 次の候補を表示 | 前の候補を表示 | | :- | :- | :- | | macOS | Option+] | Option+[ | | Windows | Alt+] | Alt+[ | | Linux | Alt+] | Alt+[ | {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## 新しいタブに複数の候補を表示する {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. +1. 候補を表示するように {% data variables.product.prodname_copilot %} に要求するには、Java ファイルに次の行を入力します。 {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -1. Open a new tab with multiple additional suggestions. - - On macOS, press Command+Shift+A, then click **Open GitHub Copilot**, or press Command+Shift+\ to open the new tab immediately. - - On Windows or Linux, press Ctrl+Enter, then click **Open GitHub Copilot**. - ![Screenshot of dialogue to open Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. 複数の追加候補を表示した新しいタブが開きます。 + - macOS では、Command+Shift+Aキーを押して **[GitHub Copilot を開く]** をクリックするか、Command+Shift+\ キーを押して新しいタブをすぐに開きます。 + - Windows または Linux では、Ctrl+Enter キーを押して、 **[GitHub Copilot を開く]** をクリックします。 + ![Copilot を開くためのダイアログのスクリーンショット](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) +1. 候補を受け入れるには、候補の上にある **[ソリューションの受入]** をクリックします。 すべての候補を拒否するには、タブを閉じます。 -## Generating code suggestions from comments +## コメントからコード候補を生成する {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines. +1. Java ファイル内の関数の実装を提案するように {% data variables.product.prodname_copilot %} に要求するには、次の行を入力します。 ```java{:copy} // find all images without alternate text // and give them a red border void process () { ``` - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/comment-suggestion-jetbrains.png) + ![Java 関数本文の候補のスクリーンショット](/assets/images/help/copilot/comment-suggestion-jetbrains.png) -## Enabling and disabling {% data variables.product.prodname_copilot %} +## {% data variables.product.prodname_copilot %} の有効化と無効化 -You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out. +すべての言語、または個々の言語の {% data variables.product.prodname_copilot %} を有効または無効にすることができます。 JetBrains IDE ウィンドウの下部パネルにある {% data variables.product.prodname_copilot %} 状態アイコンは、{% data variables.product.prodname_copilot %} が有効であるか、または無効であるかを示します。 有効の場合、アイコンが強調表示されます。 無効の場合、アイコンは淡色表示されます。 -1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window. - ![Screenshot of the status icon in IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png) -2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing. +1. {% data variables.product.prodname_copilot %} を有効または無効にするには、JetBrains ウィンドウの下部パネルにある状態アイコンをクリックします。 + ![IntelliJ IDEA の状態アイコンのスクリーンショット](/assets/images/help/copilot/status-icon-jetbrains.png) +2. {% data variables.product.prodname_copilot %} を無効にする場合、グローバルに無効にするか、または現在編集しているファイルの言語に対して無効にするかを確認されます。 - - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**. - - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**. - ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) + - {% data variables.product.prodname_copilot %} からの候補をグローバルに無効にするには、 **[入力候補を無効にする]** をクリックします。 + - 指定した言語に対して {% data variables.product.prodname_copilot %} からの候補を無効にするには、 **["_言語_" の入力候補を無効にする]** をクリックします。 + ![{% data variables.product.prodname_copilot %} をグローバルに、または現在の言語に対して無効にするためのオプションのスクリーンショット](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) -## Further reading +## 参考資料 -- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/) -- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) +- [{% data variables.product.prodname_copilot %} Web サイト](https://copilot.github.com/) +- [{% data variables.product.prodname_copilot %} について](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) diff --git a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md index bc783d3b490d..cf8b12d02a5f 100644 --- a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md +++ b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md @@ -1,34 +1,39 @@ --- -title: Getting started with GitHub Copilot in Neovim +title: Neovim で GitHub Copilot の使用を開始する shortTitle: Neovim product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.' +intro: '{% data variables.product.prodname_copilot %} を Neovim にインストールし、コメントやコードを記述するときに候補が表示されるようにする方法について説明します。' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 6296ff5b89e86b4b51cbb04bd9ac4ba91863a1ac +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185068' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Neovim +## {% data variables.product.prodname_copilot %} と Neovim について {% data reusables.copilot.procedural-intro %} -If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. +Neovim を使用すると、{% data variables.product.prodname_copilot %} からの候補をエディター内で直接表示し、取り入れることができます。 -## Prerequisites +## 前提条件 -- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." +- {% data variables.product.prodname_copilot %} を使用するには、アクティブな {% data variables.product.prodname_copilot %} サブスクリプションが必要です。 詳しくは、「[{% data variables.product.prodname_copilot %} の課金について](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)」をご覧ください。 -- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/). +- Neovim で {% data variables.product.prodname_copilot %} を使うには、Neovim と Node.js バージョン 17 以降をインストールする必要があります。 詳細については、[Neovim のドキュメント](https://neovim.io/doc/)と [Node.js の Web サイト](https://nodejs.org/en/)を参照してください。 -## Installing the Neovim extension +## Neovim 拡張機能のインストール {% mac %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal. + - Neovim の組み込みプラグイン マネージャーを使って {% data variables.product.prodname_copilot %} をインストールするには、ターミナルで次のコマンドを入力します。 git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -41,7 +46,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% windows %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash. + - Neovim の組み込みプラグイン マネージャーを使って {% data variables.product.prodname_copilot %} をインストールするには、Git Bash で次のコマンドを入力します。 git clone https://github.com/github/copilot.vim.git ` $HOME/AppData/Local/nvim/pack/github/start/copilot.vim @@ -54,7 +59,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% linux %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command: + - Neovim の組み込みプラグイン マネージャーを使って {% data variables.product.prodname_copilot %} をインストールするには、次のコマンドを入力します。 git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -63,14 +68,14 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% endlinux %} -## Learning to use {% data variables.product.prodname_copilot %} in Neovim +## Neovim で {% data variables.product.prodname_copilot %} を使う方法を学習する -For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command. +Neovim での {% data variables.product.prodname_copilot %} の使用に関するガイダンスについては、プラグインのドキュメントを参照してください。 ドキュメントを表示するには、Neovim を開いて次のコマンドを実行します。 ``` :help copilot ``` -## Further reading +## 参考資料 - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md index 9894db0413d9..35721d3952d1 100644 --- a/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md +++ b/translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md @@ -1,105 +1,109 @@ --- -title: Getting started with GitHub Copilot in Visual Studio Code +title: Visual Studio Code で GitHub Copilot の使用を開始する shortTitle: Visual Studio Code -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, and start seeing suggestions as you write comments and code.' +intro: '{% data variables.product.prodname_vscode %} に {% data variables.product.prodname_copilot %} をインストールし、コメントやコードを記述するときに候補が表示されるようにする方法について説明します。' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 63c670a7cd5263057f79b7761a960854ecac2dd6 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185143' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %} +## {% data variables.product.prodname_copilot %} と {% data variables.product.prodname_vscode %} について {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vscode %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vscode %} for macOS, Windows, or Linux. +{% data variables.product.prodname_vscode %} を使う場合、エディター内に {% data variables.product.prodname_copilot %} の候補を直接表示し、取り入れることができます。 このガイドでは、macOS、Windows、Linux 用の {% data variables.product.prodname_vscode %} 内で {% data variables.product.prodname_copilot %} を使う方法について説明します。 -## Prerequisites +## 前提条件 -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %} download page](https://code.visualstudio.com/Download). +{% data variables.product.prodname_vscode %} で {% data variables.product.prodname_copilot %} を使うには、{% data variables.product.prodname_vscode %} がインストールされている必要があります。 詳細については、[{% data variables.product.prodname_vscode %} のダウンロード ページ](https://code.visualstudio.com/Download)を参照してください。 -## Installing the {% data variables.product.prodname_vscode %} extension +## {% data variables.product.prodname_vscode %} 拡張機能をインストールする -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension. +{% data variables.product.prodname_copilot %} を使うには、最初に {% data variables.product.prodname_vscode %} 拡張機能をインストールする必要があります。 -1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**. - ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) -1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**. -1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**. - ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png) -1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}. - - If you have previously authorized {% data variables.product.prodname_vscode %} for your account on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} will be automatically authorized. - ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png) -1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_vscode %}**. -1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialog box, to confirm the authentication, click **Open**. +1. {% data variables.product.prodname_vscode %} Marketplace で、[{% data variables.product.prodname_copilot %} 拡張機能](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot)ページに移動し、 **[Install]\(インストール\)** をクリックします。 + ![{% data variables.product.prodname_copilot %} 拡張機能 {% data variables.product.prodname_vscode %} をインストールする](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) +1. ポップアップが表示され、{% data variables.product.prodname_vscode %} を開くように求められます。 **[Open {% data variables.product.prodname_vscode %}]** をクリックします。 +1. {% data variables.product.prodname_vscode %} の [Extension: {% data variables.product.prodname_copilot %}] タブの **[Install]\(インストール\)** をクリックします。 + ![{% data variables.product.prodname_vscode %} の [Install]\(インストール\) ボタン](/assets/images/help/copilot/in-visual-studio-code-install-button.png) +1. {% data variables.product.prodname_dotcom %} アカウントで {% data variables.product.prodname_vscode %} を以前に認可していない場合は、{% data variables.product.prodname_vscode %} で {% data variables.product.prodname_dotcom %} にサインインするように求められます。 + - {% data variables.product.prodname_dotcom %} のアカウントで {% data variables.product.prodname_vscode %} を以前に認可している場合は、{% data variables.product.prodname_copilot %} は自動的に認可されます。 + ![{% data variables.product.prodname_vscode %} 認可画面のスクリーン ショット](/assets/images/help/copilot/vsc-copilot-authorize.png) +1. ブラウザーで、{% data variables.product.prodname_dotcom %} から、{% data variables.product.prodname_copilot %} に必要なアクセス許可が要求されます。 これらのアクセス許可を承認するには、 **[{% data variables.product.prodname_vscode %} の認可]** をクリックします。 +1. {% data variables.product.prodname_vscode %} の [{% data variables.product.prodname_vscode %}] ダイアログ ボックスで、認証を確認するには、 **[Open]\(開く\)** をクリックします。 -## Seeing your first suggestion +## 最初の候補を表示する {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} 次のサンプルは JavaScript で記述されていますが、他の言語も同様に動作します。 {% data reusables.copilot.create-js-file %} -1. In the JavaScript 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. JavaScript ファイルで、次の関数ヘッダーを入力します。 次に示すように、{% data variables.product.prodname_copilot %} から自動的に関数本文全体の候補が灰色のテキストで表示されます。 実際に表示される候補はこのとおりではない場合があります。 ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` - ![Screenshot of a first suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) -{% data reusables.copilot.accept-suggestion %} + ![最初の候補のスクリーンショット {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions +## 代替候補の表示 {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. JavaScript ファイルで、次の関数ヘッダーを入力します。 {% data variables.product.prodname_copilot %} による候補が表示されます。 ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | OS | 次の候補を表示 | 前の候補を表示 | | :- | :- | :- | - |macOS|Option (⌥) or Alt+]|Option (⌥) or Alt+[| + |macOS|Option (⌥) または Alt+]|Option (⌥) または Alt+[| |Windows|Alt+]|Alt+[| |Linux|Alt+]|Alt+[| -1. Alternatively, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions. +1. または、候補の上にマウス ポインターを置くと、候補を選択するための{% data variables.product.prodname_copilot %} コマンド パレットが表示されます。 {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## 新しいタブに複数の候補を表示する {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. JavaScript ファイルで、次の関数ヘッダーを入力します。 {% data variables.product.prodname_copilot %} による候補が表示されます。 ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` -1. To open a new tab with multiple additional options, press Ctrl+Enter. -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. 複数の追加オプションを含む新しいタブを開くには、Ctrl+Enter キーを押します。 +1. 候補を受け入れるには、候補の上にある **[Accept Solution]\(ソリューションの受入\)** をクリックします。 すべての候補を拒否するには、タブを閉じます。 -## Generating code suggestions from comments +## コメントからコード候補を生成する {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. JavaScript ファイルで、次のコメントを入力します。 {% data variables.product.prodname_copilot %} による関数の実装の候補が表示されます。 ```javascript{:copy} // find all images without alternate text // and give them a red border function process() { ``` -## Using a framework +## フレームワークの使用 -You can also use {% data variables.product.prodname_copilot %} to generate suggestions for APIs and frameworks. The following example uses {% data variables.product.prodname_copilot %} to create a simple Express server that returns the current time. +{% data variables.product.prodname_copilot %} を使うと、API やフレームワークの候補を生成することもできます。 次の例では、{% data variables.product.prodname_copilot %} を使って、現在の時刻を返す単純な Express サーバーを作成しています。 {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment and then press Enter. {% data variables.product.prodname_copilot %} will suggest an implementation of the Express app. +1. JavaScript ファイルで、次のコメントを入力し、Enter キーを押します。 {% data variables.product.prodname_copilot %} による Express アプリの実装の候補が表示されます。 ```javascript{:copy} // Express server on port 3000 1. To accept each line, press Tab, then Enter. @@ -107,10 +111,10 @@ You can also use {% data variables.product.prodname_copilot %} to generate sugge ```javascript{:copy} // Return the current time ``` -1. To accept each line, press Tab. +1. 各行を受け入れるには、Tab キーを押します。 {% data reusables.copilot.enabling-or-disabling-in-vsc %} -## Further reading +## 参考資料 - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) 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 618bbdb98aab..8fbefa13c8c4 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 @@ -1,84 +1,86 @@ --- -title: Getting started with GitHub Copilot in Visual Studio +title: Visual Studio で GitHub Copilot の使用を開始する shortTitle: Visual Studio product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, and start seeing suggestions as you write comments and code.' +intro: '{% data variables.product.prodname_vs %} に {% data variables.product.prodname_copilot %} をインストールし、コメントやコードを記述するときに候補が表示されるようにする方法について説明します。' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 353095b0b0490cd12da8d853754b524431605819 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185129' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Visual Studio +## {% data variables.product.prodname_copilot %} と Visual Studio について {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vs %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vs %} for Windows. +{% data variables.product.prodname_vs %} を使うと、エディター内に {% data variables.product.prodname_copilot %} による候補が直接表示されるので、取り入れることができます。 このガイドでは、{% data variables.product.prodname_vs %} for Windows 内で {% data variables.product.prodname_copilot %} を使う方法について説明します。 -## Prerequisites +## 前提条件 -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have {% data variables.product.prodname_vs %} 2022 17.2 or later installed. For more information, see the [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) documentation. +{% data variables.product.prodname_vs %} で {% data variables.product.prodname_copilot %} を使うには、{% data variables.product.prodname_vs %} 2022 17.2 以降がインストールされている必要があります。 詳しい情報については、[Visual Studio IDE](https://visualstudio.microsoft.com/vs/) のドキュメントをご覧ください。 {% note %} -**Note**: {% data variables.product.prodname_copilot %} is not currently available for use with Visual Studio for Mac. +**注**: {% data variables.product.prodname_copilot %} は現在、Visual Studio for Mac で使うことはできません。 {% endnote %} -## Installing the {% data variables.product.prodname_vs %} extension +## {% data variables.product.prodname_vs %} 拡張機能をインストールする -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension. -1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**. - ![Screenshot of the Visual Studio toolbar](/assets/images/help/copilot/visual-studio-toolbar.png) -1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**. - ![Screenshot of GitHub Copilot extension for Visual Studio with the download button emphasized](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) -1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}. -1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information. - ![Screenshot of installed extensions in Visual Studio with GitHub Copilot emphasized](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) -1. Open or create a new project in {% data variables.product.prodname_vs %}. -1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**. - ![Screenshot of the Microsoft {% data variables.product.prodname_vs %} dialogue box](/assets/images/help/copilot/vs-auth-dialogue.png) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. +{% data variables.product.prodname_copilot %} を使うには、最初に {% data variables.product.prodname_vs %} 拡張機能をインストールする必要があります。 +1. Visual Studio ツール バーの **[拡張機能]** をクリックし、 **[拡張機能の管理]** をクリックします。 + ![Visual Studio ツール バーのスクリーンショット](/assets/images/help/copilot/visual-studio-toolbar.png) +1. [拡張機能の管理] ウィンドウで、**Visual Studio Marketplace** をクリックし、{% data variables.product.prodname_copilot %} 拡張機能を検索して、 **[ダウンロード]** をクリックします。 + ![Visual Studio 用 GitHub Copilot 拡張機能の [ダウンロード] ボタンが強調されたスクリーンショット](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) +1. [拡張機能の管理] ウィンドウを閉じ、{% data variables.product.prodname_vs %} を終了してもう一度起動します。 +1. 必要に応じて、{% data variables.product.prodname_copilot %} がインストールされ、有効になっていることを確認するには、 **[拡張機能の管理]** に戻り、 **[インストール済み]** をクリックして現在インストールされている拡張機能を表示し、 **{% data variables.product.prodname_copilot %}** をクリックして状態情報を表示します。 + ![Visual Studio でインストール済み拡張機能の GitHub Copilot が強調されているスクリーンショット](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) +1. {% data variables.product.prodname_vs %} で新しいプロジェクトを開くか、作成します。 +1. デバイスのアクティブ化コードをコピーするには、[Microsoft {% data variables.product.prodname_vs %}] ダイアログ ボックスの **[OK]** をクリックします。 + ![[Microsoft {% data variables.product.prodname_vs %}] ダイアログ ボックスのスクリーンショット](/assets/images/help/copilot/vs-auth-dialogue.png) +1. ブラウザーにデバイスのアクティブ化ウィンドウが表示されます。 デバイス コードを貼り付け、 **[続行]** をクリックします。 - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After you approve the permissions, {% data variables.product.prodname_vs %} will show a confirmation. - ![Screenshot of {% data variables.product.prodname_vs %} permissions confirmation](/assets/images/help/copilot/vs-confirmation.png) + - Windows または Linux でコードを貼り付けるには、Ctrl + v キーを押します。 + - macOS でコードを貼り付けるには、command + v キーを押します。 +1. {% data variables.product.prodname_dotcom %} から、{% data variables.product.prodname_copilot %} に必要なアクセス許可が要求されます。 これらのアクセス許可を承認するには、 **[{% data variables.product.prodname_copilot %} プラグインの認可]** をクリックします。 +1. アクセス許可を承認すると、{% data variables.product.prodname_vs %} に確認が表示されます。 + ![{% data variables.product.prodname_vs %} アクセス許可確認のスクリーンショット](/assets/images/help/copilot/vs-confirmation.png) -## Seeing your first suggestion +## 最初の候補を表示する -{% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly. +{% data reusables.copilot.code-examples-limitations %} {% data reusables.copilot.supported-languages %}次のサンプルは C# で記述されていますが、他の言語でも同様に動作します。 {% data reusables.copilot.create-c-file %} -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. +1. C# ファイルに、次の関数シグネチャを入力します。 次に示すように、{% data variables.product.prodname_copilot %} による関数本体全体の候補が自動的に灰色のテキストで表示されます。 実際に表示される候補はこのとおりではない場合があります。 ```csharp{:copy} int CalculateDaysBetweenDates( ``` - ![Screenshot of a first suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) -{% data reusables.copilot.accept-suggestion %} + ![Visual Studio Code の最初の候補のスクリーンショット](/assets/images/help/copilot/first-suggestion-visual-studio.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions -{% data reusables.copilot.alternative-suggestions %} -{% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion. +## 代替候補を表示する +{% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-c-file %} +1. C# ファイルに、次の関数シグネチャを入力します。 {% data variables.product.prodname_copilot %} による候補が表示されます。 ```csharp{:copy} 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. +1. 代替候補が利用可能な場合、これらの代替候補は、Alt + ] (または Alt + [) キーを押して表示できます。 +1. 必要に応じて、候補の上にマウス ポインターを置くと、候補を選べるように {% data variables.product.prodname_copilot %} コマンド パレットが表示されます。 {% data reusables.copilot.accept-or-reject-suggestion %} -## Generating code suggestions from comments +## コメントからコード候補を生成する {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. C# ファイルに、次のコメントを入力します。 {% data variables.product.prodname_copilot %} による関数の実装の候補が表示されます。 ```csharp{:copy} using System.Xml.Linq; @@ -91,6 +93,6 @@ To use {% data variables.product.prodname_copilot %}, you must first install the {% data reusables.copilot.enabling-or-disabling-vs %} -## Further reading +## 参考資料 - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..02bc5329158d --- /dev/null +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: GitHub Desktop からリポジトリのリモート URL を変更する +intro: '取り扱ってるリポジトリに対してのリモートのURLは{% data variables.product.prodname_desktop %}で変更できます。 リポジトリの名前や、リポジトリを所有するユーザ名、またはOrganizationが変更された場合に役立ちます。' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188364' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. **[Remote]\(リモート\)** をクリックし、 **[Primary remote repository]\(プライマリ リモート リポジトリ\)** に目的の URL を入力します。 +![[Primary remote repository]\(プライマリ リモート リポジトリ\) フィールド](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. **[Remote]\(リモート\)** をクリックし、 **[Primary remote repository]\(プライマリ リモート リポジトリ\)** に目的の URL を入力します。 +![[Primary remote repository]\(プライマリ リモート リポジトリ\) フィールド](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index bdb127bd0d09..6d45df7a641c 100644 --- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145117477' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188367' --- 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 4bdb079f53a2..e138243f3773 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 @@ -6,12 +6,12 @@ intro: '{% data variables.product.prodname_github_codespaces %} を割り当て versions: fpt: '*' 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 %}' -ms.openlocfilehash: 6794d20b9ea0153b3baf4bee1a08c68b2ba17456 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 832ab470d13cc741bc4a71e77840c99da5ff3de6 +ms.sourcegitcommit: a35d85531445980b5f04d3fc70180a29dad37f89 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158878' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148189914' --- ## {% data variables.product.prodname_github_codespaces %} について @@ -103,4 +103,4 @@ Organization または Enterprise で {% data variables.product.prodname_github_ ![学生の codespace を表示した教師の [課題の概要]](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -ブラウザーを使用して codespace に接続する場合は、自動保存が自動的に有効になります。 リポジトリに対する変更を保存する場合、変更をコミットしてリモート ブランチにプッシュする必要があります。 既定では、30 分間操作することなく codespace を実行したままにした場合、codespace はタイムアウトになり、実行が停止されます。 データは、最後に変更した時点の状態で保持されます。 codespace のライフサイクルの詳細については、「[Codespace のライフサイクル](/codespaces/developing-in-codespaces/the-codespace-lifecycle)」を参照してください。 +ブラウザーを使用して codespace に接続する場合は、自動保存が自動的に有効になります。 リポジトリに対する変更を保存する場合、変更をコミットしてリモート ブランチにプッシュする必要があります。 既定では、30 分間操作することなく codespace を実行したままにした場合、codespace はタイムアウトになり、実行が停止されます。 データは、最後に変更した時点の状態で保持されます。 codespace のライフサイクルの詳細については、「[Codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle)」を参照してください。 diff --git a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md index 469054ccf767..8b2664b3f907 100644 --- a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -4,12 +4,12 @@ intro: '{% data variables.product.prodname_discussions %} GraphQL APIの使い versions: feature: discussions shortTitle: Use GraphQL for Discussions -ms.openlocfilehash: 1512082737df4c92942a40007d2c75897edb1061 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fd296c4e9390cac3500ba7319cb602366a37e262 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147408844' +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185622' --- {% data variables.product.prodname_discussions %} GraphQL APIを使うと、ディスカッションのポストの取得、作成、編集、削除ができます。 {% data variables.product.prodname_discussions %} の詳細については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。 @@ -72,7 +72,7 @@ enum DiscussionOrderField { ### Repository.discussionCategories -このリポジトリ内で定義されている利用可能なディスカッションのカテゴリを返します。 各リポジトリは、最大で10個のカテゴリを持つことができます。 ディスカッション カテゴリの詳細については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)」を参照してください。 +このリポジトリ内で定義されている利用可能なディスカッションのカテゴリを返します。 各リポジトリは、最大で 25 個のカテゴリを持つことができます。 ディスカッション カテゴリの詳細については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)」を参照してください。 _シグニチャ:_ diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..e2fb6abffce6 --- /dev/null +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: フォーク用のリモート リポジトリの構成 +intro: 'オリジナルのリポジトリと[フォーク内で行った変更を同期する](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)ために、Git の上流リポジトリをポイントするリモートを構成する必要があります。 これにより、オリジナルのリポジトリ内で行った変更をフォークと同期することもできるようになります。' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188376' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. フォーク用に現在構成されたリモートリポジトリを一覧表示します。 + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. フォークと同期する、新しいリモートの "*上流*" リポジトリを指定します。 + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. フォーク用に指定した新しい上流リポジトリを検証します。 + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 553ee36c1a25..66ed53107fb7 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146683662' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188373' --- diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..bf740f97181c 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: フォークを同期する +intro: リポジトリのフォークを最新に保つために上流リポジトリと同期します。 redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188329' --- - -## Syncing a fork branch from the web UI +## Web UI からフォークのブランチを同期する {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. {% data variables.product.product_name %} で、アップストリーム リポジトリと同期するフォークされたリポジトリのメイン ページに移動します。 +2. **[フォークの同期]** ドロップダウンを選択します。 + ![[フォークの同期] ドロップダウンが強調されている](/assets/images/help/repository/sync-fork-dropdown.png) +3. アップストリーム リポジトリからのコミットの詳細を確認し、 **[ブランチを更新]** をクリックします。 + ![[ブランチを更新] ボタンが強調された [フォークの同期] モーダル](/assets/images/help/repository/update-branch-button.png) {% else %} +1. {% data variables.product.product_name %} で、アップストリーム リポジトリと同期するフォークされたリポジトリのメイン ページに移動します。 +2. **[アップストリームのフェッチ]** ドロップダウンを選択します。 + ![[アップストリームのフェッチ] ドロップダウン](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. アップストリーム リポジトリからのコミットの詳細を確認し、 **[フェッチしてマージ]** をクリックします。 + ![[フェッチしてマージ] ボタン](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +アップストリーム リポジトリからの変更によって競合が発生した場合、{% data variables.product.company_short %} は競合を解決するためのプルリクエストを作成するように求められます。 -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## {% data variables.product.prodname_cli %} を使ってフォークのブランチを同期する -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %}{% data variables.product.prodname_cli %} の詳細については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。 -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +親からリモート フォークを更新するには、`gh repo sync -b BRANCHNAME` サブコマンドを使って、フォークとブランチの名前を引数として指定します。 ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +アップストリーム リポジトリからの変更によって競合が発生した場合、{% data variables.product.prodname_cli %} では同期できません。宛先ブランチを上書きするように `-force` フラグを設定できます。 -## Syncing a fork branch from the command line +## コマンド ラインからフォークのブランチを同期する -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +フォークをアップストリーム リポジトリと同期する前に、Git でアップストリーム リポジトリを指すリモートを構成する必要があります。 詳しくは、「[フォーク用のリモート リポジトリの構成](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)」をご覧ください。 {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. ワーキングディレクトリをローカルプロジェクトに変更します。 +3. 上流リポジトリから、ブランチと各ブランチのコミットをフェッチします。 `BRANCHNAME` へのコミットは、ローカル ブランチ `upstream/BRANCHNAME` に格納されます。 ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. フォークのローカルのデフォルト ブランチを確認します。この場合は `main` を使用します。 ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. 上流のデフォルト ブランチ (この場合は `upstream/main`) からの変更をローカルのデフォルト ブランチにマージします。 これにより、ローカルの変更を失うことなく、フォークのデフォルトブランチが上流リポジトリと同期されます。 ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + ローカル ブランチに一意のコミットがなかった場合、Git は早送りを実行します。 詳細については、Git ドキュメントの「[基本的な分岐とマージ](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)」をご覧ください。 ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + ローカル ブランチに一意のコミットがある場合は、競合の解決が必要になる場合があります。 詳細については、「[マージ コンフリクトに対処する](/github/collaborating-with-pull-requests/addressing-merge-conflicts)」を参照してください。 {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**ヒント**: フォークの同期では、リポジトリのローカル コピーだけが更新されます。 {% data variables.location.product_location %} のフォークを更新するには、[変更をプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)する必要があります。 {% endtip %} diff --git a/translations/ja-JP/content/rest/overview/api-versions.md b/translations/ja-JP/content/rest/overview/api-versions.md new file mode 100644 index 000000000000..c8f326b796a2 --- /dev/null +++ b/translations/ja-JP/content/rest/overview/api-versions.md @@ -0,0 +1,54 @@ +--- +title: API のバージョン +shortTitle: API Versions +intro: REST API に対して要求を行う場合は、必ず使用する REST API バージョンを指定する必要があります。 +versions: + feature: api-date-versioning +ms.openlocfilehash: c1209120fab4c4cc26962991ad48b76638627db5 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184403' +--- +## API のバージョン管理について + +{% data reusables.rest-api.about-api-versions %} + +{% ifversion ghes %} + +## {% data variables.product.prodname_ghe_server %} のバージョン管理と REST API のバージョン管理について + +{% data variables.product.prodname_ghe_server %} のバージョンは、REST API のバージョンから切り離されています。 API のバージョンが {% data variables.product.prodname_ghe_server %} のバージョンに含まれている限り、{% data variables.product.prodname_ghe_server %} のバージョンをアップグレードしつつ、同じ REST API バージョンを維持できます。 同様に、選択する新しい REST API のバージョンが {% data variables.product.prodname_ghe_server %} のバージョンで使用できる限り、{% data variables.product.prodname_ghe_server %} のバージョンを更新せずに REST API のバージョンをアップグレードできます。 + +{% data variables.product.prodname_ghe_server %} のリリース ノートには、REST API のバージョンがサポートされなくなるタイミングが記載されます。 詳細については、「[リリース ノート](/admin/release-notes)」を参照してください。 + +{% endif %} + +## API バージョンの指定 + +`X-GitHub-Api-Version` ヘッダーを使用して、API のバージョンを指定する必要があります。 次に例を示します。 + +```shell +$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen +``` + +`X-GitHub-Api-Version` ヘッダーのない要求では、既定で `{{ initialRestVersioningReleaseDate }}` バージョンが使用されます。 + +サポートされなくなった API のバージョンを指定すると、`400` エラーが表示されます。 + +## 新しい API バージョンへのアップグレード + +新しい REST API バージョンにアップグレードする前に、新しい API バージョンの破壊的変更に関する変更ログを読んで、どのような破壊的変更が含まれているかを理解し、その特定の API バージョンにアップグレードする方法の詳細を確認する必要があります。 詳細については、「[破壊的変更](/rest/overview/breaking-changes)」を参照してください。 + +`X-GitHub-Api-Version` ヘッダーで新しい API バージョンを指定するように統合を更新する場合は、統合が新しい API バージョンで動作するために必要な変更を加える必要もあります。 + +統合が更新されたら、統合をテストして、新しい API バージョンで動作することを確認します。 + +## サポートされる API バージョン + +現在、次の REST API バージョンがサポートされています。 + +{% for apiVersion in allVersions[currentVersion].apiVersions %} {{ apiVersion }} {% endfor %} + +API 要求を実行し、サポートされているすべての API バージョンを取得することもできます。 詳しくは、「[すべての API バージョンを取得する](/rest/meta#get-all-api-versions)」を参照してください。 diff --git a/translations/ja-JP/content/rest/overview/breaking-changes.md b/translations/ja-JP/content/rest/overview/breaking-changes.md new file mode 100644 index 000000000000..fdbacb392899 --- /dev/null +++ b/translations/ja-JP/content/rest/overview/breaking-changes.md @@ -0,0 +1,30 @@ +--- +title: 互換性に影響する変更 +shortTitle: Breaking changes +intro: 各 REST API バージョンで導入された破壊的変更について説明します。 +versions: + feature: api-date-versioning +ms.openlocfilehash: 674345b82c5da9b0804fe4a0f62450ff4fbbc3e9 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184406' +--- +## REST API の破壊的変更について + +{% data reusables.rest-api.about-api-versions %} + +API バージョンの詳細については、「[API のバージョン](/rest/overview/api-versions)」を参照してください。 + +## 新しい API バージョンへのアップグレード + +新しい REST API バージョンにアップグレードする前に、新しい API バージョンに対応するこのページのセクションを読んで、どのような破壊的変更が含まれているかを理解し、その API バージョンにアップグレードする方法の詳細を確認する必要があります。 + +`X-GitHub-Api-Version` ヘッダーで新しい API バージョンを指定するように統合を更新する場合は、統合が新しい API バージョンで動作するために必要な変更を加える必要もあります。 + +統合が更新されたら、統合をテストして、新しい API バージョンで動作することを確認します。 + +## {{ initialRestVersioningReleaseDate }} の破壊的変更 + +バージョン `{{ initialRestVersioningReleaseDate }}` は、日付ベースのバージョン管理が導入されてから最初の {% data variables.product.product_name %} REST API のバージョンです。 このバージョンには、破壊的変更は含まれていません。 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 cb4127f07b68..baee262e1397 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 @@ -11,12 +11,12 @@ versions: miniTocMaxHeadingLevel: 3 topics: - API -ms.openlocfilehash: dc16916ada20275d41f23a8bc006cc79ddf51120 -ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.openlocfilehash: 4fd3e2aad72ee0ffc4778a86dc99cd5bb6f9d2c5 +ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148184270' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190400' --- {% ifversion api-date-versioning %} ## API バージョン @@ -262,10 +262,10 @@ REST API を使用して `node_id` を検索し、GraphQL 演算で使用する >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md index bf4b490be59c..27516f7ceb87 100644 --- a/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159046" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189889" --- -codespace はいつでも停止できます。 codespace を停止すると、実行中のすべてのプロセスが停止され、ターミナルの履歴が消去されます。 次に codespace を起動するときに、codespace に保存した変更は引き続き使用できます。 codespace を明示的に停止しない場合、非アクティブからタイムアウトするまで実行され続けます。 詳しくは、「[codespace のライフサイクル](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces)」を参照してください。 +codespace はいつでも停止できます。 codespace を停止すると、実行中のすべてのプロセスが停止され、ターミナルの履歴が消去されます。 次に codespace を起動するときに、codespace に保存した変更は引き続き使用できます。 codespace を明示的に停止しない場合、非アクティブからタイムアウトするまで実行され続けます。 詳しくは、「[codespace のライフサイクル](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces)」を参照してください。 CPU 料金は、実行中の codespace に対してのみ発生します。 停止した codespace には、ストレージ コストのみが発生します。 diff --git a/translations/ja-JP/data/reusables/copilot/copilot-cta-button.md b/translations/ja-JP/data/reusables/copilot/copilot-cta-button.md new file mode 100644 index 000000000000..f22ee75d9527 --- /dev/null +++ b/translations/ja-JP/data/reusables/copilot/copilot-cta-button.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 9f7ac09b688bbe2b74a5cba71d2605365b7e7366 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148185128" +--- +{% data variables.product.prodname_copilot %} を試す {% octicon "link-external" height:16 %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/discussions/repository-category-limit.md b/translations/ja-JP/data/reusables/discussions/repository-category-limit.md index 457b9d5befdd..0c866e3f4018 100644 --- a/translations/ja-JP/data/reusables/discussions/repository-category-limit.md +++ b/translations/ja-JP/data/reusables/discussions/repository-category-limit.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 7b782aa3d23143a62b07aedf0a07df3734173d44 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f58fb9410d93c9e50d33de5f1b12b9d6441ea561 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145137940" +ms.lasthandoff: 11/30/2022 +ms.locfileid: "148185617" --- -各リポジトリまたは Organization は、最大で 10 個のカテゴリを持つことができます。 +各リポジトリまたは組織は、最大で 25 個のカテゴリを持つことができます。 diff --git a/translations/ja-JP/data/reusables/rest-api/about-api-versions.md b/translations/ja-JP/data/reusables/rest-api/about-api-versions.md new file mode 100644 index 000000000000..fc0ffb2c3877 --- /dev/null +++ b/translations/ja-JP/data/reusables/rest-api/about-api-versions.md @@ -0,0 +1,32 @@ +--- +ms.openlocfilehash: dd7c5f37ab5b2d699b47460195e02ae21fca1733 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184397" +--- +{% data variables.product.product_name %} REST API はバージョン管理されています。 API バージョンの名前は、その API バージョンがリリースされた日付に基づいています。 たとえば、API バージョン `{{ initialRestVersioningReleaseDate }}` は {{ initialRestVersioningReleaseDateLong }} にリリースされました。 + +すべての破壊的変更は、新しい API バージョンでリリースされます。 破壊的変更とは、統合を破損する可能性のある変更のことです。 破壊的変更には次のようなものが含まれます。 + +- 操作全体を削除する +- パラメーターを削除または名前変更する +- 応答フィールドを削除または名前変更する +- 新しい必須パラメーターを追加する +- 以前に省略可能だったパラメーターを必須にする +- パラメーターまたは応答フィールドの型を変更する +- 列挙型の値を削除する +- 既存のパラメーターに新しい検証規則を追加する +- 認証または認可の要件を変更する + +追加的な (破壊的でない) 変更は、サポートされているすべての API バージョンで使用できます。 追加的な変更とは、統合を破損しない変更のことです。 追加的な変更には次のようなものが含まれます。 + +- 操作を追加する +- 省略可能なパラメーターを追加する +- 省略可能な要求ヘッダーを追加する +- 応答フィールドを追加する +- 応答ヘッダーを追加する +- 列挙型の値を追加する + +新しい REST API バージョンがリリースされた場合、以前の API バージョンは、新しい API バージョンのリリースから少なくとも 24 か月間はサポートされます。 diff --git a/translations/ja-JP/data/reusables/rest-api/version-header.md b/translations/ja-JP/data/reusables/rest-api/version-header.md new file mode 100644 index 000000000000..5db276d34aa1 --- /dev/null +++ b/translations/ja-JP/data/reusables/rest-api/version-header.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 28c0a6c9cde70105e42feef89486c5c893ebbe72 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184394" +--- +{% ifversion api-date-versioning %}--header "X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}"{% endif %} diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv index 966503bcd1f7..17851aa8771b 100644 --- a/translations/log/msft-ja-resets.csv +++ b/translations/log/msft-ja-resets.csv @@ -512,7 +512,6 @@ translations/ja-JP/content/actions/learn-github-actions/expressions.md,rendering translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error -translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,broken liquid tags translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error @@ -620,7 +619,6 @@ translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-ser translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error -translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,rendering error translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error @@ -666,6 +664,7 @@ translations/ja-JP/content/authentication/connecting-to-github-with-ssh/testing- translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error +translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error @@ -743,6 +742,7 @@ translations/ja-JP/content/code-security/secret-scanning/defining-custom-pattern translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error translations/ja-JP/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error +translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error translations/ja-JP/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error translations/ja-JP/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error @@ -759,7 +759,6 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error -translations/ja-JP/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,rendering error translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md,rendering error translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,rendering error @@ -768,16 +767,12 @@ translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/ translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md,broken liquid tags translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error -translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error translations/ja-JP/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error -translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags -translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags -translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags -translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags +translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/ja-JP/content/copilot/quickstart.md,broken liquid tags translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags @@ -923,7 +918,6 @@ translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/propos translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md,broken liquid tags translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error From 8c52107526c8196e46b2522ff132b48096f74114 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Fri, 2 Dec 2022 09:05:31 -0800 Subject: [PATCH 2/3] New translation batch for pt (#33183) --- translations/log/msft-pt-resets.csv | 18 +- .../adding-labels-to-issues.md | 52 +-- ...saml-single-sign-on-for-your-enterprise.md | 190 ++++++----- .../about-server-statistics.md | 151 ++++----- ...github-packages-with-azure-blob-storage.md | 3 + ...or-security-settings-in-your-enterprise.md | 101 +++--- .../authorizing-oauth-apps.md | 82 ++--- .../githubs-ssh-key-fingerprints.md | 23 +- .../using-ssh-over-the-https-port.md | 8 +- .../secret-scanning-patterns.md | 70 ++-- .../deleting-a-codespace.md | 10 +- .../developing-in-codespaces/index.md | 8 +- .../opening-an-existing-codespace.md | 10 +- .../stopping-and-starting-a-codespace.md | 51 +-- .../codespaces/getting-started/deep-dive.md | 10 +- .../codespaces/getting-started/index.md | 8 +- .../the-codespace-lifecycle.md | 73 +++++ .../pt-BR/content/codespaces/index.md | 8 +- ...stricting-the-base-image-for-codespaces.md | 14 +- .../introduction-to-dev-containers.md | 193 +++++------ ...ll-request-template-for-your-repository.md | 61 ++-- ...-with-github-copilot-in-a-jetbrains-ide.md | 128 ++++---- ...g-started-with-github-copilot-in-neovim.md | 35 +- ...th-github-copilot-in-visual-studio-code.md | 84 ++--- ...ed-with-github-copilot-in-visual-studio.md | 84 ++--- ...rl-for-a-repository-from-github-desktop.md | 33 ++ .../index.md | 8 +- ...github-codespaces-with-github-classroom.md | 10 +- .../using-the-graphql-api-for-discussions.md | 10 +- ...auth-app-and-github-app-access-requests.md | 10 +- ...figuring-a-remote-repository-for-a-fork.md | 43 +++ .../working-with-forks/index.md | 8 +- .../working-with-forks/syncing-a-fork.md | 62 ++-- .../content/rest/overview/api-versions.md | 54 ++++ .../content/rest/overview/breaking-changes.md | 30 ++ .../overview/resources-in-the-rest-api.md | 12 +- .../reusables/apps/reauthorize-apps-saml.md | 9 + .../audit_log/audit-log-action-categories.md | 306 +++++++----------- .../codespaces/stopping-a-codespace.md | 10 +- .../reusables/copilot/copilot-cta-button.md | 9 + .../discussions/repository-category-limit.md | 10 +- .../sso-redirect-release-phase.md | 13 + .../ip-allow-lists-enterprise.md | 14 +- .../org-enterprise-allow-list-interaction.md | 9 + .../organizations/require-ssh-cert.md | 14 +- .../reusables/rest-api/about-api-versions.md | 32 ++ .../data/reusables/rest-api/version-header.md | 9 + 47 files changed, 1232 insertions(+), 958 deletions(-) create mode 100644 translations/pt-BR/content/codespaces/getting-started/the-codespace-lifecycle.md create mode 100644 translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md create mode 100644 translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md create mode 100644 translations/pt-BR/content/rest/overview/api-versions.md create mode 100644 translations/pt-BR/content/rest/overview/breaking-changes.md create mode 100644 translations/pt-BR/data/reusables/apps/reauthorize-apps-saml.md create mode 100644 translations/pt-BR/data/reusables/copilot/copilot-cta-button.md create mode 100644 translations/pt-BR/data/reusables/enterprise-managed/sso-redirect-release-phase.md create mode 100644 translations/pt-BR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md create mode 100644 translations/pt-BR/data/reusables/rest-api/about-api-versions.md create mode 100644 translations/pt-BR/data/reusables/rest-api/version-header.md diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv index 3788dc0d87c0..0e169f40e5ca 100644 --- a/translations/log/msft-pt-resets.csv +++ b/translations/log/msft-pt-resets.csv @@ -495,7 +495,6 @@ translations/pt-BR/content/actions/learn-github-actions/expressions.md,rendering translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error -translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,broken liquid tags translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error @@ -590,7 +589,6 @@ translations/pt-BR/content/admin/identity-and-access-management/using-enterprise translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error -translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags @@ -600,7 +598,6 @@ translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-ser translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error -translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error @@ -620,7 +617,6 @@ translations/pt-BR/content/admin/packages/getting-started-with-github-packages-f translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error -translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error @@ -644,9 +640,9 @@ translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error -translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error @@ -726,6 +722,7 @@ translations/pt-BR/content/code-security/secret-scanning/defining-custom-pattern translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error translations/pt-BR/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error +translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error translations/pt-BR/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error translations/pt-BR/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error translations/pt-BR/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error @@ -742,19 +739,14 @@ translations/pt-BR/content/code-security/supply-chain-security/understanding-you translations/pt-BR/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error -translations/pt-BR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error -translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error -translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags -translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags -translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags -translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags +translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/pt-BR/content/copilot/quickstart.md,broken liquid tags translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags @@ -898,7 +890,6 @@ translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/propos translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error @@ -1043,7 +1034,6 @@ translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-p translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error translations/pt-BR/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags -translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error translations/pt-BR/data/reusables/branches/new-repo-default-branch.md,rendering error @@ -1118,7 +1108,6 @@ translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-poli translations/pt-BR/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md,rendering error translations/pt-BR/data/reusables/git/git-push.md,rendering error -translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md,broken liquid tags translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error translations/pt-BR/data/reusables/large_files/storage_assets_location.md,broken liquid tags translations/pt-BR/data/reusables/large_files/use_lfs_tip.md,rendering error @@ -1130,7 +1119,6 @@ translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md, translations/pt-BR/data/reusables/organizations/member-privileges.md,rendering error translations/pt-BR/data/reusables/organizations/navigate-to-org.md,rendering error translations/pt-BR/data/reusables/organizations/repository-defaults.md,rendering error -translations/pt-BR/data/reusables/organizations/require-ssh-cert.md,broken liquid tags translations/pt-BR/data/reusables/organizations/security-and-analysis.md,rendering error translations/pt-BR/data/reusables/organizations/security.md,rendering error translations/pt-BR/data/reusables/organizations/teams_sidebar.md,rendering error diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 213c2d5c9c6a..7af92d28cf78 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -1,7 +1,7 @@ --- -title: Adding labels to issues +title: Adicionando etiquetas a problemas shortTitle: Add labels to issues -intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.' +intro: 'Você pode usar {% data variables.product.prodname_actions %} para etiquetar problemas automaticamente.' redirect_from: - /actions/guides/adding-labels-to-issues versions: @@ -13,24 +13,28 @@ type: tutorial topics: - Workflows - Project management +ms.openlocfilehash: a3523069b9422ecd8107007ca5e00fb0071dd738 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185558' --- +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +## Introdução -## Introduction +Este tutorial demonstra como usar a [ação `actions/github-script`](https://github.com/marketplace/actions/github-script) em um fluxo de trabalho para rotular os problemas recém-abertos ou reabertos. Por exemplo, você pode adicionar o rótulo `triage` sempre que um problema é aberto ou reaberto. Em seguida, veja todos os problemas que precisam ser triagem filtrando os problemas com o rótulo `triage`. -This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label. +A ação `actions/github-script` permite que você use facilmente a API do {% data variables.product.prodname_dotcom %} em um fluxo de trabalho. -The `actions/github-script` action allows you to easily use the {% data variables.product.prodname_dotcom %} API in a workflow. +No tutorial, primeiro, você criará um arquivo de fluxo de trabalho que usa a [ação `actions/github-script`](https://github.com/marketplace/actions/github-script). Então, você personalizará o fluxo de trabalho para atender às suas necessidades. -In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs. - -## Creating the workflow +## Criar o fluxo de trabalho 1. {% data reusables.actions.choose-repo %} 2. {% data reusables.actions.make-workflow-file %} -3. Copy the following YAML contents into your workflow file. +3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho. ```yaml{:copy} name: Label issues @@ -56,23 +60,23 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git }) ``` -4. Customize the `script` parameter in your workflow file: - - The `issue_number`, `owner`, and `repo` values are automatically set using the `context` object. You do not need to change these. - - Change the value for `labels` to the list of labels that you want to add to the issue. Separate multiple labels with commas. For example, `["help wanted", "good first issue"]`. For more information about labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)." +4. Personalize o parâmetro `script` no seu arquivo do fluxo de trabalho: + - Os valores `issue_number`, `owner` e `repo` são definidos automaticamente com o objeto `context`. Não é necessário alterar esses padrões. + - Altere o valor de `labels` para a lista de rótulos que deseja adicionar ao problema. Separe etiquetas múltiplas com vírgulas. Por exemplo, `["help wanted", "good first issue"]`. Para obter mais informações sobre rótulos, confira "[Como gerenciar rótulos](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)". 5. {% data reusables.actions.commit-workflow %} -## Testing the workflow +## Testar o fluxo de trabalho -Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue. +Toda vez que um problema no seu repositório for aberto ou reaberto, esse fluxo de trabalho adicionará as etiquetas que você especificou ao problema. -Test out your workflow by creating an issue in your repository. +Teste o seu fluxo de trabalho criando um problema no seu repositório. -1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." -2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -3. When the workflow completes, the issue that you created should have the specified labels added. +1. Crie um problema no seu repositório. Para obter mais informações, confira "[Como criar um problema](/github/managing-your-work-on-github/creating-an-issue)". +2. Para ver a execução do fluxo de trabalho que foi acionada criando o problema, veja o histórico de execuções do seu fluxo de trabalho. Para obter mais informações, confira "[Como ver o histórico de execução do fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)". +3. Quando o fluxo de trabalho é concluído, o problema que você criou deve ter as etiquetas especificadas adicionadas. -## Next steps +## Próximas etapas -- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script). -- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." -- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action. +- Para saber sobre mais coisas que podem ser feitas com a ação `actions/github-script`, confira a [documentação da ação `actions/github-script`](https://github.com/marketplace/actions/github-script). +- Para saber mais sobre diferentes eventos que podem disparar seu fluxo de trabalho, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#issues)". +- [Pesquise o GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) para ver exemplos de fluxos de trabalho que usam essa ação. diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 1fe2d098997d..a9232564164e 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configuring SAML single sign-on for your enterprise +title: Configurar o logon único SAML para sua empresa shortTitle: Configure SAML SSO -intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' +intro: 'Você pode controlar e proteger o acesso a {% ifversion ghec %}recursos, como repositórios, problemas e solicitações de pull nas organizações da empresa{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}sua empresa no {% data variables.product.prodname_ghe_managed %}{% endif %} com a {% ifversion ghec %}imposição{% elsif ghes or ghae %}configuração{% endif %} do SSO (logon único) do SAML por meio do IdP (provedor de identidade).' permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.' versions: ghec: '*' @@ -21,11 +21,16 @@ redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise +ms.openlocfilehash: 804ba3b262aae15b862e1a14694b82339c8d34a4 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: '148183953' --- - {% data reusables.enterprise-accounts.emu-saml-note %} -## About SAML SSO +## Sobre o SAML SSO {% ifversion ghec %} @@ -33,11 +38,11 @@ redirect_from: {% data reusables.saml.saml-accounts %} -For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." +Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso com o logon único do SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". {% data reusables.saml.about-saml-enterprise-accounts %} -{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." +{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, confira "[Como ver e gerenciar o acesso do SAML de um usuário à sua conta corporativa](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)". {% data reusables.saml.saml-disabled-linked-identities-removed %} @@ -45,9 +50,9 @@ For more information, see "[About identity and access management with SAML singl {% elsif ghes or ghae %} -SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. +O SAML SSO permite que você controle centralmente e proteja o acesso ao {% data variables.location.product_location %} a partir do seu IdP SAML. Quando um usuário não autenticado visitar {% data variables.location.product_location %} em um navegador, {% data variables.product.product_name %} redirecionará o usuário para seu IdP do SAML para efetuar a autenticação. Depois que o usuário efetua a autenticação com sucesso com uma conta no IdP, o usuário do IdP redireciona o usuário de volta para {% data variables.location.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IdP e, em seguida, concede acesso ao usuário. -After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. +Depois que um usuário efetua a autenticação com sucesso no IdP, a sessão do SAML do usuário para {% data variables.location.product_location %} fica ativa no navegador por 24 horas. Depois de 24 horas, o usuário deve efetuar a autenticação novamente com o seu IdP. {% data reusables.saml.saml-ghes-account-revocation %} @@ -55,171 +60,161 @@ After a user successfully authenticates on your IdP, the user's SAML session for {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". {% endif %} {% endif %} -## Supported identity providers +## Provedores de identidade compatíveis {% data reusables.saml.saml-supported-idps %} {% ifversion ghec %} -## Username considerations with SAML +## Considerações de nome de usuário no SAML -{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." +{% ifversion ghec %} Se você usar {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Para obter mais informações, confira "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". -## Enforcing SAML single-sign on for organizations in your enterprise account +## Aplicar o logon único SAML para organizações na sua conta corporativa -When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +Ao aplicar o logon único SAML SSO para sua empresa, a configuração corporativa substituirá todas as configurações do SAML existentes no nível da organização. {% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, confira "[Como alternar a configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". -When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. +Ao aplicar o SAML SSO para uma organização, {% data variables.product.company_short %} removerá todos os integrantes da organização que não tenham efetuado a autenticação com sucesso com seu IdP do SAML. Ao exigir o SAML SSO para a sua empresa, {% data variables.product.company_short %} não irá remover os integrantes da empresa que não tenham efetuado a autenticação com sucesso com o IdP do SAML. Na próxima vez que um integrante acessar os recursos da empresa, ele deverá efetuar a autenticação com o seu IdP do SAML. -For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)." +Para obter informações mais detalhadas sobre como habilitar o SAML usando o Okta, confira "[Como configurar o logon único do SAML para sua conta corporativa usando o Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)". -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Require SAML authentication**. - ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. -![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. -![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -8. Under **Public Certificate**, paste a certificate to verify SAML responses. -![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. -![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -11. Click **Save**. +5. Em "Logon único do SAML", selecione **Exigir autenticação SAML**. + ![Caixa de seleção para habilitar o SSO do SAML](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. No campo **URL de Logon**, digite o ponto de extremidade HTTPS do IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. +![Campo referente à URL para a qual os membros serão encaminhados após a entrada](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Opcionalmente, no campo **Emissor**, digite a URL do emissor do SAML para verificar a autenticidade das mensagens enviadas. +![Campo referente ao nome do emissor do SAML](/assets/images/help/saml/saml_issuer.png) +8. Em **Certificado Público**, cole um certificado para verificar as respostas do SAML. +![Campo referente ao certificado público do provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) +9. Para verificar a integridade das solicitações do emissor do SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. +![Menus suspensos dos algoritmos de hash Método de Assinatura e Método de resumo usados pelo emissor do SAML](/assets/images/help/saml/saml_hashing_method.png) +10. Antes de habilitar o SSO do SAML para sua empresa, clique em **Testar configuração do SAML** para garantir que as informações que você inseriu estão corretas. ![Botão usado para testar a configuração do SAML antes da imposição](/assets/images/help/saml/saml_test.png) +11. Clique em **Salvar**. {% data reusables.enterprise-accounts.download-recovery-codes %} {% elsif ghes %} -## Configuring SAML SSO +## Configurando o SAML SSO -You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." +Você pode habilitar ou desabilitar a autenticação do SAML para {% data variables.location.product_location %} ou você pode editar uma configuração existente. Você pode ver e editar as configurações de autenticação do {% data variables.product.product_name %} no console de gerenciamento. Para obter mais informações, confira "[Como acessar o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". {% note %} -**Note**: {% data reusables.enterprise.test-in-staging %} +**Observação**: {% data reusables.enterprise.test-in-staging %} {% endnote %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -1. Select **SAML**. +{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} +1. Selecione **SAML**. - ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png) + ![Captura de tela da opção para habilitar a autenticação SAML no console de gerenciamento](/assets/images/enterprise/management-console/auth-select-saml.png) 1. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. + ![Captura de tela da opção para habilitar a autenticação integrada fora do IdP do SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +1. Opcionalmente, para habilitar o SSO de resposta não solicitado, selecione **SSO iniciado pelo IdP**. Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo IdP (provedor de identidade) não solicitada com uma `AuthnRequest`. - ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png) + ![Captura de tela da opção para habilitar resposta não solicitada iniciada pelo IdP](/assets/images/enterprise/management-console/saml-idp-sso.png) {% tip %} - **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. + **Observação**: recomendamos manter esse valor **desmarcado**. Você **só** deverá habilitar esse recurso na rara ocasião em que a implementação do SAML não der suporte ao SSO iniciado pelo provedor de serviços e quando recomendado pelo {% data variables.contact.enterprise_support %}. {% endtip %} -1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}. +1. Selecione **Desabilitar rebaixamento/promoção do administrador** se **não** quiser que o provedor do SAML determine direitos de administrador para os usuários na {% data variables.location.product_location %}. - ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -{%- ifversion ghes > 3.3 %} -1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)." + ![Captura de tela da opção para habilitar a opção para respeitar o atributo do "administrador" do IdP a fim de habilitar ou desabilitar direitos administrativos](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) {%- ifversion ghes > 3.3 %} +1. Opcionalmente, para permitir que a {% data variables.location.product_location %} receba declarações criptografadas do IdP do SAML, selecione **Exigir declarações criptografadas**. Você deve garantir que seu IdP é compatível com declarações e que a criptografia e os métodos de transporte principais no console de gerenciamento correspondem aos valores configurados no seu IdP. Você também deve fornecer o certificado público de {% data variables.location.product_location %} ao IdP. Para obter mais informações, confira "[Como habilitar declarações criptografadas](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)". - ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) -{%- endif %} -1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/). + ![Captura de tela da caixa de seleção "Habilitar declarações criptografadas" na seção "Autenticação" do console de gerenciamento](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) {%- endif %} +1. No campo **URL de logon**, digite o ponto de extremidade HTTP ou HTTPS do IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o host só estiver disponível somente na rede interna, talvez seja necessário [configurar a {% data variables.location.product_location %} para usar servidores de nomes internos](/enterprise/admin/guides/installation/configuring-dns-nameservers/). - ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) -1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}. + ![Captura de tela do campo de texto para a URL de acesso único](/assets/images/enterprise/management-console/saml-single-sign-url.png) +1. Opcionalmente, no campo **Emissor**, digite o nome do emissor do SAML. Fazer isso verifica a autenticidade das mensagens enviadas para {% data variables.location.product_location %}. - ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png) -1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. + ![Screenshot do campo de texto para a URL do emissor do SAML](/assets/images/enterprise/management-console/saml-issuer.png) +1. Nos menus suspensos **Método de Assinatura** e **Método de Hash**, escolha o algoritmo de hash usado pelo emissor do SAML para verificar a integridade das solicitações da {% data variables.location.product_location %}. Especifique o formato com o menu suspenso **Formato de Identificador de Nome**. - ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png) -1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. + ![Captura de tela dos menus suspensos para selecionar a assinatura e o método de resumo](/assets/images/enterprise/management-console/saml-method.png) +1. Em **Certificado de verificação**, clique em **Escolher Arquivo** e escolha um certificado para validar as respostas do SAML do IdP. - ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) -1. Modify the SAML attribute names to match your IdP if needed, or accept the default names. + ![Captura de tela do botão para fazer o upload do certificado de validação do IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) +1. Modifique os nomes do atributo SAML para corresponder ao IdP, se necessário, ou aceite os nomes padrão. - ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png) + ![Captura de tela dos campos para inserir atributos adicionais do SAML](/assets/images/enterprise/management-console/saml-attributes.png) {% elsif ghae %} -## Enabling SAML SSO +## Habilitar o SAML SSO {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. +Os seguintes IdPs fornecem documentação sobre a configuração de do SAML SSO para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. - | IdP | More information | + | IdP | Mais informações | | :- | :- | - | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | -| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | + | Azure AD | "[Configurar a autenticação e o provisionamento para sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | +| Okta | "[Configurar autenticação e provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | -During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)." +Durante a inicialização do {% data variables.product.product_name %}, você deve configurar o {% data variables.product.product_name %} como um SP (provedor de serviço) do SAML no seu IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido. Para obter mais informações, confira "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)". -## Editing the SAML SSO configuration +## Editar a configuração SAML SSO -If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. +Se os detalhes do IdP forem alterados, você deverá editar a configuração SAML SSO para o {% data variables.location.product_location %}. Por exemplo, se o certificado de seu IdP expirar, você poderá editar o valor para o certificado público. {% ifversion ghae %} {% note %} -**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", type the new details for your IdP. - ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) -1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. - ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - - Use the drop-down menus and choose the new signature or digest method. - ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. To ensure that the information you've entered is correct, click **Test SAML configuration**. - !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. Click **Save**. - !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +1. Em "logon único SAML", digite os novos detalhes para o seu IdP. + ![Campos de entrada de texto com detalhes do IdP para configuração do SSO do SAML para uma empresa](/assets/images/help/saml/ae-edit-idp-details.png) +1. Opcionalmente, clique em {% octicon "pencil" aria-label="The edit icon" %} para configurar uma nova assinatura ou método de resumo. + ![Ícone de edição para alterar a assinatura e o método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) + + - Use os menus suspensos e escolha a nova assinatura ou o método de resumo. + ![Menus suspensos para escolha de uma nova assinatura ou um método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. Para garantir que as informações inseridas estão corretas, clique em **Testar configuração do SAML**. + ![Botão "Testar configuração do SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Clique em **Salvar**. + ![Botão "Salvar" da configuração de SSO do SAML](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Opcionalmente, para provisionar e desprovisionar contas de usuário automaticamente para {% data variables.location.product_location %}, reconfigure o provisionamento de usuário com SCIM. Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". {% endif %} {% ifversion ghae %} -## Disabling SAML SSO +## Desabilitar SAML SSO {% warning %} -**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours. +**Aviso**: se você desabilitar o SSO do SAML do {% data variables.location.product_location %}, os usuários sem sessões SSO do SAML existentes não poderão entrar no {% data variables.location.product_location %}. As sessões SAML SSO em {% data variables.location.product_location %} terminam após 24 horas. {% endwarning %} {% note %} -**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Under "SAML single sign-on", unselect **Enable SAML authentication**. - ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) -1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. - !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +1. Em "Logon único do SAML", desmarque **Habilitar autenticação SAML**. + ![Caixa de seleção para "Habilitar autenticação SAML"](/assets/images/help/saml/ae-saml-disabled.png) +1. Para desabilitar o SSO do SAML e exigir o logon com a conta de usuário interna que você criou durante a inicialização, clique em **Salvar**. + ![Botão "Salvar" da configuração de SSO do SAML](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} @@ -227,13 +222,10 @@ If the details for your IdP change, you'll need to edit the SAML SSO configurati {% ifversion ghec or ghes %} -## Further reading +## Leitura adicional {%- ifversion ghec %} -- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)" -{%- endif %} -{%- ifversion ghes %} -- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" -{%- endif %} +- "[Gerenciar o logon único do SAML em sua organização](/organizations/managing-saml-single-sign-on-for-your-organization)" {%- endif %} {%- ifversion ghes %} +- "[Promover ou rebaixar um administrador do site](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" {%- endif %} {% endif %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index a3cb3c1f5bcd..564936f15140 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: About Server Statistics -intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' +title: Sobre estatísticas do servidor +intro: 'Você pode usar {% data variables.product.prodname_server_statistics %} para analisar seus próprios dados agregados do {% data variables.product.prodname_ghe_server %} e nos ajudar a melhorar os produtos {% data variables.product.company_short %}.' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -8,97 +8,102 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics topics: - Enterprise +ms.openlocfilehash: 3d17df54cd5dcf9ad102ab5079794a9bcb3e664b +ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185182' --- +## Sobre os benefícios de {% data variables.product.prodname_server_statistics %} -## About the benefits of {% data variables.product.prodname_server_statistics %} +As {% data variables.product.prodname_server_statistics %} podem ajudar você a prever as necessidades de sua organização, entender como sua equipe trabalha e mostrar o valor obtido do {% data variables.product.prodname_ghe_server %}. -{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. +Depois de habilitadas, as {% data variables.product.prodname_server_statistics %} coleta dados agregados sobre quanto determinados recursos estão sendo usados em sua instância ao longo do tempo. Ao contrário de outros pontos de extremidade da [API Admin Stats](/rest/reference/enterprise-admin#admin-stats), que só retornam dados do dia anterior, as {% data variables.product.prodname_server_statistics %} fornecem dados históricos de todas as métricas de {% data variables.product.prodname_server_statistics %} coletadas desde o dia em que você habilitou o recurso. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_server_statistics %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)". -Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +Ao habilitar {% data variables.product.prodname_server_statistics %}, você está ajudando a criar um {% data variables.product.prodname_dotcom %} melhor. Os dados agregados que você fornecerá nos fornecerão insights sobre como o {% data variables.product.prodname_dotcom %} adiciona valor aos nossos clientes. Essas informações permitem que {% data variables.product.company_short %} tome decisões melhores e mais informadas sobre produtos, beneficiando você. -When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. +## Sobre a segurança de dados -## About data security +Respeitamos seus dados. Nunca transmitiremos dados do {% data variables.location.product_location %} a menos que você primeiro nos tenha dado permissão para fazê-lo. -We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so. +Não coletamos dados pessoais. Também não coletamos nenhum conteúdo do {% data variables.product.company_short %}, como código, problemas, comentários ou conteúdo de solicitação de pull. -We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. +Somente proprietários da conta corporativa ou organização conectada ao {% data variables.product.prodname_ghe_cloud %} podem acessar os dados. -Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. +Somente determinadas métricas de agregação são coletadas em repositórios, problemas, solicitações de pull e outros recursos. Para ver a lista de métricas de agregação coletadas, confira "[Dados coletados de {% data variables.product.prodname_server_statistics %}](#server-statistics-data-collected)". -Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." +As atualizações nas métricas coletadas ocorrerão em versões futuras do {% data variables.product.prodname_ghe_server %} e serão descritas nas [notas sobre a versão do {% data variables.product.prodname_ghe_server %}](/admin/release-notes). Além disso, atualizaremos este artigo com todas as atualizações de métricas. -Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. +Para uma melhor compreensão de como armazenamos e protegemos dados de {% data variables.product.prodname_server_statistics %} dados, confira "[Segurança do GitHub](https://github.com/security)". -For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." +### Sobre retenção e exclusão de dados -### About data retention and deletion +O {% data variables.product.company_short %} coleta dados de {% data variables.product.prodname_server_statistics %} enquanto sua licença do {% data variables.product.prodname_ghe_server %} estiver ativa e o recurso {% data variables.product.prodname_server_statistics %} habilitado. -{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. +Se você quiser excluir seus dados, poderá fazer isso entrando em contato com o Suporte do GitHub, seu representante de conta do {% data variables.product.prodname_dotcom %} ou seu Gerente de Sucesso do Cliente. Geralmente, excluímos dados no período de tempo especificado em nossa política de privacidade. Para obter mais informações, confira [ declaração de privacidade do {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) na documentação do {% data variables.product.prodname_dotcom_the_website %}. -If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. +### Sobre a portabilidade de dados -### About data portability +Como proprietário da organização ou proprietário da empresa no {% data variables.product.prodname_ghe_cloud %}, você pode acessar {% data variables.product.prodname_server_statistics %} exportando os dados em um arquivo CSV ou JSON ou por meio da API REST de {% data variables.product.prodname_server_statistics %}. Para obter mais informações, confira "[Como solicitar {% data variables.product.prodname_server_statistics %} usando a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" ou "[Como exportar {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)". -As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." +## Sobre desabilitar a coleta de dados -## About disabling data collection +Você pode desabilitar o recurso {% data variables.product.prodname_server_statistics %} a qualquer momento. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_server_statistics %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)". -You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." +## Dados coletados de {% data variables.product.prodname_server_statistics %} -## {% data variables.product.prodname_server_statistics %} data collected +Depois de habilitar {% data variables.product.prodname_server_statistics %}, as métricas serão coletadas por meio de um trabalho diário executado no {% data variables.location.product_location %}. As métricas de agregação são armazenadas em sua conta da organização ou da empresa no {% data variables.product.prodname_ghe_cloud %} e não são armazenadas no {% data variables.location.product_location %}. -After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}. +As métricas de agregação a seguir serão coletadas e transmitidas diariamente e representam as contagens totais do dia. -The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day. - -CSV column | Name | Description | +Coluna CSV | Nome | Descrição | ---------- | ---- | ----------- | -A | `github_connect.features_enabled` | Array of {% data variables.product.prodname_github_connect %} features that are enabled for your instance (see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)" ) | -B | `host_name` | The hostname for your instance | -C | `dormant_users.dormancy_threshold` | The length of time a user must be inactive to be considered dormant | -D | `dormant_users.total_dormant_users` | Number of dormant user accounts | -E | `ghes_version` | The version of {% data variables.product.product_name %} that your instance is running | -F | `server_id` | The UUID generated for your instance -G | `collection_date` | The date the metrics were collected | -H | `schema_version` | The version of the database schema used to store this data | -I | `ghe_stats.comments.total_commit_comments` | Number of comments on commits | -J | `ghe_stats.comments.total_gist_comments` | Number of comments on gists | -K | `ghe_stats.comments.total_issue_comments` | Number of comments on issues | -L | `ghe_stats.comments.total_pull_request_comments` | Number of comments on pull requests | -M | `ghe_stats.gists.total_gists` | Number of gists (both secret and public) | -N | `ghe_stats.gists.private_gists` | Number of secret gists | -O | `ghe_stats.gists.public_gists` | Number of public gists | -P | `ghe_stats.hooks.total_hooks` | Number of pre-receive hooks (both active and inactive) | -Q | `ghe_stats.hooks.active_hooks` | Number of active pre-receive hooks | -R | `ghe_stats.hooks.inactive_hooks` | Number of inactive pre-receive hooks | -S | `ghe_stats.issues.total_issues` | Number of issues (both open and closed) | -T | `ghe_stats.issues.open_issues` | Number of open issues | -U | `ghe_stats.issues.closed_issues` | Number of closed issues | -V | `ghe_stats.milestones.total_milestones` | Number of milestones (both open and closed) | -W | `ghe_stats.milestones.open_milestones` | Number of open milestones | -X | `ghe_stats.milestones.closed_milestones` | Number of closed milestones | -Y | `ghe_stats.orgs.total_orgs` | Number of organizations (both enabled and disabled) | -Z | `ghe_stats.orgs.disabled_orgs` | Number of disabled organizations | -AA | `ghe_stats.orgs.total_teams` | Number of teams | -AB | `ghe_stats.orgs.total_team_members` | Number of team members | -AC | `ghe_stats.pages.total_pages` | Number of {% data variables.product.prodname_pages %} sites | -AD | `ghe_stats.pulls.total_pulls` | Number of pull requests | -AE | `ghe_stats.pulls.merged_pulls` | Number of merged pull requests | -AF | `ghe_stats.pulls.mergeable_pulls` | Number of pull requests that are currently mergeable | -AG | `ghe_stats.pulls.unmergeable_pulls` | Number of pull requests that are currently unmergeable | -AH | `ghe_stats.repos.total_repos` | Number of repositories (both upstream repositories and forks) | -AI | `ghe_stats.repos.root_repos` | Number of upstream repositories | -AJ | `ghe_stats.repos.fork_repos` | Number of forks | -AK | `ghe_stats.repos.org_repos` | Number of repositories owned by organizations | -AL | `ghe_stats.repos.total_pushes` | Number of pushes to repositories | -AM | `ghe_stats.repos.total_wikis` | Number of wikis | -AN | `ghe_stats.users.total_users` | Number of user accounts | -AO | `ghe_stats.users.admin_users` | Number of user accounts that are site administrators | -AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspended | - -## {% data variables.product.prodname_server_statistics %} data examples - -To see an example of the headings included in the CSV export for {% data variables.product.prodname_server_statistics %}, download the [{% data variables.product.prodname_server_statistics %} CSV example](/assets/server-statistics-csv-example.csv). - -To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." \ No newline at end of file +Um | `github_connect.features_enabled` | Matriz de recursos de {% data variables.product.prodname_github_connect %} que estão habilitados para sua instância (confira "[Sobre {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#github-connect-features)" ) | +B | `host_name` | O nome do host da instância | +C | `dormant_users.dormancy_threshold` | O tempo que um usuário deve ser inativo para ser considerado inativo | +D | `dormant_users.total_dormant_users` | Número de contas de usuário inativas | +E | `ghes_version` | A versão do {% data variables.product.product_name %} que sua instância está executando | +F | `server_id` | A UUID gerada para sua instância +G | `collection_date` | A data das métricas foram coletadas | +H | `schema_version` | A versão do esquema de banco de dados usada para armazenar esses dados | +I | `ghe_stats.comments.total_commit_comments` | Número de comentários sobre confirmações | +J | `ghe_stats.comments.total_gist_comments` | Número de comentários sobre gists | +K | `ghe_stats.comments.total_issue_comments` | Número de comentários sobre problemas | +L | `ghe_stats.comments.total_pull_request_comments` | Número de comentários sobre solicitações de pull | +M | `ghe_stats.gists.total_gists` | Número de gists (secretos e públicos) | +N | `ghe_stats.gists.private_gists` | Número de gists secretos | +O | `ghe_stats.gists.public_gists` | Número de gists públicos | +P | `ghe_stats.hooks.total_hooks` | Número de ganchos de pré-recebimento (ativos e inativos) | +Q | `ghe_stats.hooks.active_hooks` | Número de ganchos de pré-recebimento ativos | +R | `ghe_stats.hooks.inactive_hooks` | Número de ganchos pré-recebimento inativos | +S | `ghe_stats.issues.total_issues` | Número de problemas (abertos e fechados) | +T | `ghe_stats.issues.open_issues` | Número de problemas em aberto | +U | `ghe_stats.issues.closed_issues` | Número de problemas fechados | +V | `ghe_stats.milestones.total_milestones` | Número de marcos (abertos e fechados) | +W | `ghe_stats.milestones.open_milestones` | Número de marcos abertos | +X | `ghe_stats.milestones.closed_milestones` | Número de marcos fechados | +Y | `ghe_stats.orgs.total_orgs` | Número de organizações (habilitadas e desabilitadas) | +Z | `ghe_stats.orgs.disabled_orgs` | Número de organizações desabilitadas | +AA | `ghe_stats.orgs.total_teams` | Quantidade de equipes | +AB | `ghe_stats.orgs.total_team_members` | Número de membros da equipe | +AC | `ghe_stats.pages.total_pages` | Número de sites do {% data variables.product.prodname_pages %} | +AD | `ghe_stats.pulls.total_pulls` | Número de solicitações de pull | +AE | `ghe_stats.pulls.merged_pulls` | Número de solicitações de pull mescladas | +AF | `ghe_stats.pulls.mergeable_pulls` | Número de solicitações de pull que atualmente são mescladas | +AG | `ghe_stats.pulls.unmergeable_pulls` | Número de solicitações de pull que atualmente são não mescladas | +AH | `ghe_stats.repos.total_repos` | Número de repositórios (repositórios upstream e forks) | +IA | `ghe_stats.repos.root_repos` | Número de repositórios upstream | +AJ | `ghe_stats.repos.fork_repos` | Número de forks | +AK | `ghe_stats.repos.org_repos` | Número de repositórios pertencentes às organizações | +AL | `ghe_stats.repos.total_pushes` | Número de pushes para repositórios | +AM | `ghe_stats.repos.total_wikis` | Número de wikis | +AN | `ghe_stats.users.total_users` | Número de contas de usuário | +AO | `ghe_stats.users.admin_users` | Número de contas de usuário que são administradores de site | +PA | `ghe_stats.users.suspended_users` | Número de contas de usuário suspensas | + +## Exemplos de dados do {% data variables.product.prodname_server_statistics %} + +Para ver um exemplo dos títulos incluídos na exportação CSV para {% data variables.product.prodname_server_statistics %}, baixe o [exemplo de CSV do {% data variables.product.prodname_server_statistics %}](/assets/server-statistics-csv-example.csv). + +Para ver um exemplo do conteúdo de resposta para a API de {% data variables.product.prodname_server_statistics %}, confira "[Como solicitar {% data variables.product.prodname_server_statistics %} usando a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)". diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 6c0ed9c1c5c7..c3b2f0e6f0c6 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Enforcing policies for security settings in your enterprise -intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.' +title: Aplicando políticas para configurações de segurança na sua empresa +intro: É possível impor políticas para gerenciar as configurações de segurança nas organizações da sua empresa ou permitir que as políticas sejam definidas em cada organização. permissions: Enterprise owners can enforce policies for security settings in an enterprise. miniTocMaxHeadingLevel: 3 redirect_from: @@ -21,100 +21,89 @@ topics: - Policies - Security shortTitle: Policies for security settings +ms.openlocfilehash: 7a383ed586d084a7e2562a5927dd198caca65037 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: '148183961' --- +## Sobre políticas para configurações de segurança na sua empresa -## About policies for security settings in your enterprise - -You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. +É possível aplicar políticas para controlar as configurações de segurança das organizações pertencentes à sua empresa em {% data variables.product.product_name %}. Por padrão, os proprietários da organização podem gerenciar as configurações de segurança. {% ifversion ghec or ghes %} -## Requiring two-factor authentication for organizations in your enterprise +## Exigir autenticação de dois fatores para organizações na sua empresa -Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their user accounts. +Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma empresa usem autenticação de dois fatores para proteger suas contas de usuário. -Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)." +Antes de poder exigir a autenticação 2FA para todas as organizações pertencentes à sua empresa, você deve habilitar a autenticação de dois fatores para a sua própria conta. Para obter informações, confira "[Como proteger sua conta com a 2FA (autenticação de dois fatores)](/articles/securing-your-account-with-two-factor-authentication-2fa/)". {% warning %} -**Warnings:** +**Avisos:** -- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their account within three months of their removal from your organization. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)." -- Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their account after you've enabled required two-factor authentication will automatically be removed from the organization. -- If you're the sole owner of an enterprise that requires two-factor authentication, you won't be able to disable 2FA for your user account without disabling required two-factor authentication for the enterprise. +- Se você exigir autenticação de dois fatores para a sua empresa, os integrantes, colaboradores externos e gerentes de cobrança (incluindo contas bot) em todas as organizações pertencentes à sua empresa que não utilizem 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização. Se a autenticação de dois fatores for habilitada para a conta deles em até três meses após a remoção da organização, será possível restabelecer as configurações e os privilégios de acesso deles. Para obter mais informações, confira "[Como restabelecer um ex-membro da sua organização](/articles/reinstating-a-former-member-of-your-organization)". +- Qualquer proprietário da organização, integrante, gerente de cobrança ou colaborador externo em qualquer das organizações pertencentes à sua empresa que desabilite a 2FA para a conta dele depois que você tiver habilitado a autenticação de dois fatores obrigatória será removido automaticamente da organização. +- Se você for o único proprietário de uma empresa que exige autenticação de dois fatores, não poderá desabilitar 2FA para sua conta sem desabilitar a autenticação de dois fatores obrigatória para a empresa. {% endwarning %} -Before you require use of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up 2FA for their accounts. Organization owners can see if members and outside collaborators already use 2FA on each organization's People page. For more information, see "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)." +Antes de exigir o uso da autenticação de dois fatores, é recomendável notificar os integrantes da organização, colaboradores externos e gerentes de cobrança e pedir que eles configurem 2FA nas contas deles. Os proprietários da organização podem ver se integrantes e colaboradores externos já utilizam 2FA na página People (Pessoas) de cada organização. Para obter mais informações, confira "[Como ver se os usuários da sua organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)". -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. Under "Two-factor authentication", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "Two-factor authentication", select **Require two-factor authentication for all organizations in your business**, then click **Save**. - ![Checkbox to require two-factor authentication](/assets/images/help/business-accounts/require-2fa-checkbox.png) -6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**. - ![Confirm two-factor enforcement box](/assets/images/help/business-accounts/confirm-require-2fa.png) -7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. Each person must enable two-factor authentication before they can accept your invitation. +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +4. Em "Two-factor authentication" (Autenticação de dois fatores), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Em "Autenticação de dois fatores", selecione **Exigir a autenticação de dois fatores para todas as organizações na sua empresa** e clique em **Salvar**. + ![Caixa de seleção usada para exigir a autenticação de dois fatores](/assets/images/help/business-accounts/require-2fa-checkbox.png) +6. Se solicitado, leia as informações sobre os integrantes e colaboradores externos que serão removidos das organizações pertencentes à sua empresa. Para confirmar a alteração, digite o nome da empresa e clique em **Remover membros e exigir a autenticação de dois fatores**. + ![Caixa Confirmar a imposição de dois fatores](/assets/images/help/business-accounts/confirm-require-2fa.png) +7. Como alternativa, se algum integrante ou colaborador externo for removido das organizações pertencentes à sua empresa, recomendamos enviar um convite para restabelecer os privilégios e o acesso à organização que ele tinha anteriormente. Cada pessoa precisa habilitar a autenticação de dois fatores para poder aceitar o convite. {% endif %} -## Managing SSH certificate authorities for your enterprise +## Gerenciando as autoridades de certificados de SSH da sua empresa -You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." +Você pode usar as autoridades de certificados SSH (CA) para permitir que os integrantes de qualquer organização pertencente à sua empresa acessem os repositórios da organização usando certificados SSH que você fornecer. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, confira "[Sobre as autoridades de certificação SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)". {% data reusables.organizations.add-extension-to-cert %} -### Adding an SSH certificate authority +### Adicionar uma autoridade certificada de SSH -If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)." +Se você precisar de certificados SSH para sua empresa, os integrantes da empresa deverão usar um URL especial para operações do Git por meio do SSH. Para obter mais informações, confira "[Sobre as autoridades de certificado SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)". -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.organizations.new-ssh-ca %} -{% data reusables.organizations.require-ssh-cert %} +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.new-ssh-ca %} {% data reusables.organizations.require-ssh-cert %} -### Deleting an SSH certificate authority +### Excluir uma autoridade certificada de SSH -Deleting a CA cannot be undone. If you want to use the same CA in the future, you'll need to upload the CA again. +A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no futuro, precisará fazer upload dela novamente. -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.organizations.delete-ssh-ca %} +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.organizations.delete-ssh-ca %} {% ifversion sso-redirect %} -## Managing SSO for unauthenticated users +## Como gerenciar o SSO para usuários não autenticados {% data reusables.enterprise-managed.sso-redirect-release-phase %} -If your enterprise uses {% data variables.product.prodname_emus %}, you can choose what unauthenticated users see when they attempt to access your enterprise's resources. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)." +Se a sua empresa usa {% data variables.product.prodname_emus %}, você pode escolher o que os usuários não autenticados veem ao tentar acessar os recursos da sua empresa. Para obter mais informações sobre o {% data variables.product.prodname_emus %}, confira "[Sobre o {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)". -By default, to hide the existence of private resources, when an unauthenticated user attempts to access your enterprise, {% data variables.product.company_short %} displays a 404 error. +Por padrão, para ocultar a existência de recursos privados, quando um usuário não autenticado tenta acessar sua empresa, o {% data variables.product.company_short %} exibe um erro 404. -To prevent confusion from your developers, you can change this behavior so that users are automatically redirected to single sign-on (SSO) through your identity provider (IdP). When you enable automatic redirects, anyone who visits the URL for any of your enterprise's resources will be able to see that the resource exists. However, they'll only be able to see the resource if they have appropriate access after authenticating with your IdP. +Para evitar confundir os desenvolvedores, você pode alterar esse comportamento para que os usuários sejam redirecionados automaticamente para o SSO (logon único) por meio do IdP (provedor de identidade). Quando você habilita redirecionamentos automáticos, qualquer pessoa que visita a URL de qualquer um dos recursos da sua empresa pode ver que tais recursos existem. No entanto, eles só poderão ver o recurso se tiverem as devidas permissões de acesso após a autenticação no seu IdP. {% note %} -**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.enterprise.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +**Observação:** se um usuário estiver conectado na conta pessoal dele ao tentar acessar qualquer um dos recursos da sua empresa, ele será automaticamente desconectado e redirecionado ao SSO para entrar no {% data variables.enterprise.prodname_managed_user %} dele. Para obter mais informações, confira "[Como gerenciar várias contas](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)". {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Under "Single sign-on settings", select or deselect **Automatically redirect users to sign in**. +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +1. Em "Configurações de logon único", marque ou desmarque **Redirecionar automaticamente os usuários para entrar**. - ![Checkbox to automatically redirect users to sign in](/assets/images/enterprise/security/Enterprise-Redirect-Users-To-Sign-In-Checkbox.png) -{% endif %} + ![Caixa de seleção para redirecionar automaticamente os usuários para entrar](/assets/images/enterprise/security/Enterprise-Redirect-Users-To-Sign-In-Checkbox.png) {% endif %} -## Further reading +## Leitura adicional -- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)" -{%- ifversion ghec %} -- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)" -{%- endif %} -{%- ifversion ghec or ghae %} -- "[Restricting network traffic with an IP allow list with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" -{%- endif %} +- "[Sobre o gerenciamento de identidades e acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)" {%- ifversion ghec %} +- "[Como acessar relatórios de conformidade para sua empresa](/admin/overview/accessing-compliance-reports-for-your-enterprise)" {%- endif %} {%- ifversion ghec or ghae %} +- "[Como restringir o tráfego de rede com uma lista de permissões de IP](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" {%- endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index 3b8a3b97f625..5330936d6a11 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Authorizing OAuth Apps -intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.' +title: Autorizando Aplicativos OAuth +intro: 'Você pode conectar sua identidade do {% data variables.product.product_name %} a aplicativos de terceiros usando o OAuth. Ao autorizar um {% data variables.product.prodname_oauth_app %}, você deve ter certeza de que se trata de um aplicativo confiável, examinar por quem ele foi desenvolvido e analisar os tipos de informação que o aplicativo quer acessar.' redirect_from: - /articles/authorizing-oauth-apps - /github/authenticating-to-github/authorizing-oauth-apps @@ -13,89 +13,95 @@ versions: topics: - Identity - Access management +ms.openlocfilehash: 7d116f8fc5117cdcbdbd5582e007351c47b2d55d +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: '148184017' --- -When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested. +Quando um {% data variables.product.prodname_oauth_app %} quiser identificá-lo por sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, você verá uma página com as informações de contato do desenvolvedor do aplicativo e uma lista dos dados específicos que estão sendo solicitados. {% ifversion fpt or ghec %} {% tip %} -**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}. +**Dica:** você precisa [verificar seu endereço de email](/articles/verifying-your-email-address) antes de autorizar um {% data variables.product.prodname_oauth_app %}. {% endtip %} {% endif %} -## {% data variables.product.prodname_oauth_app %} access +## Acesso do {% data variables.product.prodname_oauth_app %} -{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. +Os {% data variables.product.prodname_oauth_apps %} podem ter acesso de *leitura* ou de *gravação* nos dados do {% data variables.product.product_name %}. -- **Read access** only allows an app to *look at* your data. -- **Write access** allows an app to *change* your data. +- O **acesso de leitura** só permite que um aplicativo *visualize* seus dados. +- O **acesso de gravação** permite que um aplicativo *altere* seus dados. {% tip %} -**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %} +**Dica:** {% data reusables.user-settings.review_oauth_tokens_tip %} {% endtip %} -### About OAuth scopes +### Sobre os escopos do OAuth -*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data. +Os *escopos* são grupos de permissões nomeados que um {% data variables.product.prodname_oauth_app %} pode solicitar para acessar dados públicos e privados. -When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se integre ao {% data variables.product.product_name %}, esse app permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao app, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você quiser usar um aplicativo que solicite o escopo de `user:email`, o aplicativo terá acesso somente leitura aos seus endereços de email privados. Para obter mais informações, confira "[Sobre os escopos dos {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". {% tip %} -**Note:** Currently, you can't scope source code access to read-only. +**Observação:** atualmente, não é possível definir o escopo do acesso ao código-fonte como somente leitura. {% endtip %} {% data reusables.apps.oauth-token-limit %} -### Types of requested data +### Tipos de dados solicitados -{% data variables.product.prodname_oauth_apps %} can request several types of data. +{% data variables.product.prodname_oauth_apps %} pode solicitar vários tipos de dados. -| Type of data | Description | +| Tipo de dados | Descrição | | --- | --- | -| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. | -| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. | -| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. | -| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. | -| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. | -| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. | -| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. | -| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. | -| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %} -| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %} +| Status do commit | Você pode conceder acesso para um app relatar seu status de commit. O acesso ao status do commit permite que os apps determinem se uma compilação foi bem-sucedida em relação a um commit específico. Os apps não terão acesso ao seu código, mas poderão ler e gravar informações de status em relação a um commit específico. | +| Implantações | O acesso ao status da implantação permite que os apps determinem se uma implantação foi bem-sucedida em relação a um commit específico para repositórios públicos e privados. Os apps não terão acesso ao seu código. | +| Gists | O acesso de [gist](https://gist.github.com) permite que os aplicativos leiam ou gravem conteúdo dos seus gists públicos e secretos. | +| Ganchos | O acesso de [webhooks](/webhooks) permite que os aplicativos leiam ou gravem configurações de gancho nos repositórios que você gerencia. | +| Notificações | O acesso à notificação permite que os apps leiam as notificações do {% data variables.product.product_name %}, como comentários sobre problemas ou pull requests. No entanto, os apps continuam sem poder acessar nada nos repositórios. | +| Organizações e equipes | O acesso às organizações e equipes permite que os apps acessem e gerenciem a associação à organização e à equipe. | +| Dados pessoais do usuário | Os dados do usuário incluem informações encontradas no seu perfil de usuário, como nome, endereço de e-mail e localização. | +| Repositórios | As informações de repositório incluem os nomes dos contribuidores, os branches que você criou e os arquivos reais dentro do repositório. Os apps podem solicitar acesso para repositórios públicos ou privados em um nível amplo de usuário. | +| Exclusão de repositório | Os apps podem solicitar a exclusão de repositórios que você administra, mas não terão acesso ao seu código. |{% ifversion projects-oauth-scope %} +| Projetos | Acesso {% data variables.projects.projects_v2 %} de usuário e da organização. Os aplicativos podem solicitar acesso de leitura/gravação ou somente leitura. |{% endif %} -## Requesting updated permissions +## Solicitar permissões atualizadas -When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. +Quando {% data variables.product.prodname_oauth_apps %} solicitar novas permissões de acesso, você será notificado sobre as diferenças entre as permissões atuais e as novas permissões. {% ifversion fpt or ghec %} -## {% data variables.product.prodname_oauth_apps %} and organizations +## {% data variables.product.prodname_oauth_apps %} e organizações -When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of. +Quando você autoriza {% data variables.product.prodname_oauth_app %} para sua conta pessoal, também verá como essa autorização afetará cada organização da qual você é membro. -- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself. +- **Para as organizações *com* restrições de acesso do {% data variables.product.prodname_oauth_app %}, você pode solicitar que os administradores da organização aprovem o aplicativo para uso nessa organização.** Se a organização não aprovar o aplicativo, o aplicativo só poderá acessar os recursos públicos da organização. Se você for um administrador da organização, poderá [aprovar o aplicativo](/articles/approving-oauth-apps-for-your-organization) por conta própria. -- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. +- **Para as organizações *sem* restrições de acesso do {% data variables.product.prodname_oauth_app %}, o aplicativo será autorizado automaticamente para acesso aos recursos dessa organização.** Por esse motivo, você deve ter cuidado com quais {% data variables.product.prodname_oauth_apps %} você aprova para acesso aos recursos da sua conta pessoal, bem como a todos os recursos da organização. -If you belong to any organizations with SAML single sign-on (SSO) enabled, and you have created a linked identity for that organization by authenticating via SAML in the past, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}. +Se você pertencer a qualquer organização com SSO (logon único) SAML habilitado e tiver criado uma identidade vinculada para essa organização autenticando via SAML no passado, deverá ter uma sessão SAML ativa para cada organização sempre que autorizar um {% data variables.product.prodname_oauth_app %}. {% note %} -**Note:** If you're encountering issues with an authorized {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} accessing an organization that is protected by SAML, you may need to revoke the app from your [Authorized {% data variables.product.prodname_github_apps %}](https://github.com/settings/applications) or [Authorized {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/apps/authorizations) page, visit the organization to authenticate and establish an active SAML session, and then attempt to reauthorize the app by accessing it. +**Nota:** se você estiver encontrando problemas com um {% data variables.product.prodname_oauth_app %} ou {% data variables.product.prodname_github_app %} autorizado acessando uma organização protegida por SAML, talvez seja necessário revogar o aplicativo de sua página [{% data variables.product.prodname_github_apps %} autorizado](https://github.com/settings/applications) ou [{% data variables.product.prodname_oauth_apps %} autorizado](https://github.com/settings/apps/authorizations), acessar a organização para autenticar e estabelecer uma sessão SAML ativa e tentar autorizar novamente o aplicativo por meio do acesso. {% endnote %} -## Further reading +## Leitura adicional -- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" -- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" -- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" +- "[Sobre as restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" +- "[Como autorizar Aplicativos do GitHub](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[Suporte ao {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" {% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index 5ef18527a47e..1286785f705f 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -1,6 +1,6 @@ --- -title: Impressões digitais da chave SSH do GitHub -intro: Impressões digitais da chave pública podem ser usadas para validar uma conexão com um servidor remote. +title: GitHub's SSH key fingerprints +intro: Public key fingerprints can be used to validate a connection to a remote server. redirect_from: - /articles/what-are-github-s-ssh-key-fingerprints - /articles/github-s-ssh-key-fingerprints @@ -14,15 +14,20 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: 29f61df463d014e6a72ad7dd21049a2b338b893e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083632' --- -Estas são as impressões digitais de chave pública de {% data variables.product.prodname_dotcom %}: +These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated) - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) + +You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts: + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== +``` + +For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)." diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 92f37fba9d43..7815859b8efc 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -30,7 +30,7 @@ $ ssh -T -p 443 git@ssh.github.com **Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). @@ -71,8 +71,8 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> Are you sure you want to continue connecting (yes/no/[fingerprint])? ``` -It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches -one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches +one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." diff --git a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md index efd0821a80d2..a43693a91c80 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md +++ b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md @@ -1,6 +1,6 @@ --- -title: Padrões de digitalização de segredo -intro: 'Lista de segredos compatíveis e parceiros com quem {% data variables.product.company_short %} trabalha para evitar o uso fraudulento de segredos cometidos acidentalmente.' +title: Secret scanning patterns +intro: 'Lists of supported secrets and the partners that {% data variables.product.company_short %} works with to prevent fraudulent use of secrets that were committed accidentally.' product: '{% data reusables.gated-features.secret-scanning-partner %}' versions: fpt: '*' @@ -13,65 +13,69 @@ topics: - Advanced Security redirect_from: - /code-security/secret-scanning/secret-scanning-partners -ms.openlocfilehash: 68dd1338fc1812cd2fc40ba38949434a04986f86 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578639' --- -{% data reusables.secret-scanning.beta %} {% data reusables.secret-scanning.enterprise-enable-secret-scanning %} + +{% data reusables.secret-scanning.beta %} +{% data reusables.secret-scanning.enterprise-enable-secret-scanning %} {% ifversion fpt or ghec %} -## Sobre padrões de {% data variables.product.prodname_secret_scanning %} +## About {% data variables.product.prodname_secret_scanning %} patterns -{% data variables.product.product_name %} mantém estes conjuntos diferentes de padrões de {% data variables.product.prodname_secret_scanning %}: +{% data variables.product.product_name %} maintains these different sets of {% data variables.product.prodname_secret_scanning %} patterns: -1. **Padrões de parceiros.** Usados para detectar possíveis segredos em todos os repositórios públicos. Para ver detalhes, confira "[Segredos compatíveis para padrões de parceiros](#supported-secrets-for-partner-patterns)". -2. **Padrões de segurança avançados.** Usados para detectar possíveis segredos em repositórios com a {% data variables.product.prodname_secret_scanning %} habilitada. {% ifversion ghec %} Para ver detalhes, confira "[Segredos compatíveis para segurança avançada](#supported-secrets-for-advanced-security)."{% endif %}{% ifversion secret-scanning-push-protection %} -3. **Padrões de proteção por push.** Usados para detectar possíveis segredos em repositórios com {% data variables.product.prodname_secret_scanning %} como uma proteção por push habilitada. Para obter detalhes, confira "[Segredos com suporte para proteção por push](#supported-secrets-for-push-protection)". {% endif %} +1. **Partner patterns.** Used to detect potential secrets in all public repositories. For details, see "[Supported secrets for partner patterns](#supported-secrets-for-partner-patterns)." +2. **Advanced security patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} enabled. {% ifversion ghec %} For details, see "[Supported secrets for advanced security](#supported-secrets-for-advanced-security)."{% endif %}{% ifversion secret-scanning-push-protection %} +3. **Push protection patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} as a push protection enabled. For details, see "[Supported secrets for push protection](#supported-secrets-for-push-protection)."{% endif %} -{% ifversion fpt %} As organizações que usam o {% data variables.product.prodname_ghe_cloud %} com o {% data variables.product.prodname_GH_advanced_security %} podem habilitar a {% data variables.product.prodname_secret_scanning_GHAS %} nos repositórios. Para ver detalhes desses padrões, confira a [documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security). +{% ifversion fpt %} +Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %} can enable {% data variables.product.prodname_secret_scanning_GHAS %} on their repositories. For details of these patterns, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security). {% endif %} -## Segredos compatíveis com padrões de parceiros +## Supported secrets for partner patterns -O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. Para obter mais informações sobre o {% data variables.product.prodname_secret_scanning_partner %}, confira "[Sobre o {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)". +{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers and alerts the relevant service provider whenever a secret is detected in a commit. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)." {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} -{% data reusables.secret-scanning.partner-secret-list-public-repo %} {% endif %} +{% data reusables.secret-scanning.partner-secret-list-public-repo %} +{% endif %} {% ifversion ghec or ghae or ghes %} -## Segredos compatíveis {% ifversion ghec %} para segurança avançada{% endif %} +## Supported secrets{% ifversion ghec %} for advanced security{% endif %} -Quando {% data variables.product.prodname_secret_scanning_GHAS %} está habilitado, {% data variables.product.prodname_dotcom %} digitalia os segredos emitidos pelos seguintes prestadores de serviços. {% ifversion ghec %}Para obter mais informações sobre a {% data variables.product.prodname_secret_scanning_GHAS %}, confira "[Sobre a {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)".{% endif %} +When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %} {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} -Se você usa a API REST para verificação de segredo, pode usar o `Secret type` para relatar segredos de emissores específicos. Para obter mais informações, confira "[Verificação de segredos](/enterprise-cloud@latest/rest/secret-scanning)". +If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)." -{% ifversion ghes or ghae or ghec %} {% note %} +{% ifversion ghes or ghae or ghec %} +{% note %} -**Observação:** você também pode definir padrões personalizados da {% data variables.product.prodname_secret_scanning %} para seu repositório, sua organização ou sua empresa. Para obter mais informações, confira "[Como definir padrões personalizados para a {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)". +**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for your repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -{% data reusables.secret-scanning.partner-secret-list-private-repo %} {% endif %} +{% data reusables.secret-scanning.partner-secret-list-private-repo %} +{% endif %} {% ifversion secret-scanning-push-protection %} -## Segredos com suporte para proteção por push +## Supported secrets for push protection -Atualmente, o {% data variables.product.prodname_secret_scanning_caps %} como uma proteção por push verifica os repositórios em busca de segredos emitidos pelos provedores de serviços a seguir. +{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers. {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %} {% data reusables.secret-scanning.secret-list-private-push-protection %} {% endif %} -## Leitura adicional - -- "[Como proteger seu repositório](/code-security/getting-started/securing-your-repository)" -- "[Como manter sua conta e dados seguros](/github/authenticating-to-github/keeping-your-account-and-data-secure)" {%- ifversion fpt or ghec %} -- "[Programa de parceiros da {% data variables.product.prodname_secret_scanning_caps %}](/developers/overview/secret-scanning-partner-program)" {%- else %} -- "[Programa de parceiros da {% data variables.product.prodname_secret_scanning_caps %}](/free-pro-team@latest/developers/overview/secret-scanning-partner-program)" na documentação do {% data variables.product.prodname_ghe_cloud %} {% endif %} +## Further reading + +- "[Securing your repository](/code-security/getting-started/securing-your-repository)" +- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)" +{%- ifversion fpt or ghec %} +- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)" +{%- else %} +- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/free-pro-team@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation +{% endif %} diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index c18b03c77ac4..55d022a3ab57 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,12 +13,12 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace -ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158658' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188253' --- Você pode excluir um codespace de várias maneiras: no terminal usando a {% data variables.product.prodname_cli %}, no {% data variables.product.prodname_vscode %} ou no navegador da Web. Use as guias deste artigo para ver instruções de cada uma dessas maneiras de excluir um codespace. @@ -135,5 +135,5 @@ Para obter mais informações, clique na guia "{% data variables.product.prodnam Você também pode usar a API REST para excluir codespaces de sua organização. Para obter mais informações, confira "[Organizações de codespaces](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)". ## Leitura adicional -- "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" +- "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)" - "[Como configurar a exclusão automática dos codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)" diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md index c60785b145fb..04bbbde1b659 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159010' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188285' --- diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index ba21f4aac163..675b0b1ec89d 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -10,12 +10,12 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace -ms.openlocfilehash: e7a35c1a7b3a251094bf69fcd401291b69d03eae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159002' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188293' --- {% jetbrains %} @@ -23,7 +23,7 @@ ms.locfileid: '148159002' {% endjetbrains %} -Você pode reabrir um dos codespaces ativos ou interrompidos no {% data variables.product.prodname_dotcom_the_website %} em um IDE JetBrains, no {% data variables.product.prodname_vscode %} ou usando a {% data variables.product.prodname_cli %}. Você não pode reabrir um codespace que foi excluído. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)". +Você pode reabrir um dos codespaces ativos ou interrompidos no {% data variables.product.prodname_dotcom_the_website %} em um IDE JetBrains, no {% data variables.product.prodname_vscode %} ou usando a {% data variables.product.prodname_cli %}. Você não pode reabrir um codespace que foi excluído. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)". Você pode exibir todos os seus codespaces na página "Seus codespaces" em [github.com/codespaces](https://github.com/codespaces). Nesta página, você pode: diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index 6602cce6b44f..59a1d2f8d5a5 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -1,6 +1,6 @@ --- -title: Stopping and starting a codespace -intro: 'You can stop and start your codespace to save resources and to pause work.' +title: Parar e iniciar um codespace +intro: Você pode parar e iniciar o codespace para salvar recursos e pausar o trabalho. versions: fpt: '*' ghec: '*' @@ -10,28 +10,33 @@ topics: - Fundamentals - Developer shortTitle: Stop a codespace +ms.openlocfilehash: c09cd757ac2667c32c26f9b5e7d7a36b8e5431f9 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185080' --- - {% jetbrains %} {% data reusables.codespaces.codespaces-jetbrains-beta-note %} {% endjetbrains %} -## About stopping and starting a codespace +## Como parar e iniciar um codespace {% data reusables.codespaces.stopping-a-codespace %} -Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces. +Independentemente de onde você criou ou acessou os codespaces, eles podem ser vistos e gerenciados no navegador em https://github.com/codespaces. -## Stopping a codespace +## Interrompendo um codespace {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} - 1. To the right of the codespace you want to stop, click the elipsis (**...**). - 1. Click **Stop codespace**. - ![Screenshot of option to stop a codespace](/assets/images/help/codespaces/stop-codespace-webui.png) + 1. À direita do codespace que você deseja parar, clique na elipse ( **...** ). + 1. Clique em **Parar codespace**. + ![Captura de tela da opção para interromper um codespace](/assets/images/help/codespaces/stop-codespace-webui.png) {% endwebui %} @@ -39,7 +44,7 @@ Regardless of where you created or access your codespaces, you can view and mana {% data reusables.cli.cli-learn-more %} - To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed. + Para parar um codespace, use o subcomando `gh codespace stop` e escolha um codespace na lista exibida. ```shell{:copy} gh codespace stop @@ -50,38 +55,38 @@ Regardless of where you created or access your codespaces, you can view and mana {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to stop. +1. Digite `stop` e selecione **Codespaces: Parar o Codespace** na lista de opções. +1. Na lista de codespaces, selecione o codespace que você deseja parar. {% endvscode %} {% jetbrains %} -You can stop a codespace from the "Your codespaces" page (see [the web browser instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) or by using {% data variables.product.prodname_cli %} (see [the CLI instructions](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)). +Você pode interromper um codespace na página "Seus codespaces" (confira [as instruções do navegador da Web](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=webui#stopping-a-codespace)) ou usando {% data variables.product.prodname_cli %} (confira [as instruções da CLI](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace?tool=cli#stopping-a-codespace)). {% endjetbrains %} -## Restarting a codespace +## Como reiniciar um codespace {% webui %} {% data reusables.codespaces.navigate-to-codespaces-page %} -1. Click the name of the codespace you want to restart. -![Screenshot of stopped codespaces](/assets/images/help/codespaces/restart-codespace-webui.png) +1. Clique no nome do codespace que você deseja reiniciar. +![Captura de tela de codespaces parados](/assets/images/help/codespaces/restart-codespace-webui.png) {% endwebui %} {% cli %} -When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser. +Ao reiniciar um codespace, você pode optar por abri-lo no {% data variables.product.prodname_vscode %} ou no navegador. - - To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed. + - Para reiniciar um codespace e abri-lo no {% data variables.product.prodname_vscode %}, use o subcomando `gh codespace code` e escolha o codespace que você deseja reiniciar na lista exibida. ```shell{:copy} gh codespace code ``` - - To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed. + - Para reiniciar um codespace e abri-lo no navegador, use o subcomando `gh codespace open --web` e escolha o codespace que você deseja reiniciar na lista exibida. ```shell{:copy} gh codespace open --web @@ -92,8 +97,8 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% vscode %} {% data reusables.vs-code.open-command-palette %} -1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options. -1. In the list of codespaces, select the codespace you want to restart. +1. Digite `connect` e selecione **Codespaces: Conectar-se ao Codespace** na lista de opções. +1. Na lista de codespaces, selecione o codespace que você deseja reiniciar. {% endvscode %} @@ -103,6 +108,6 @@ When you restart a codespace you can choose to open it in {% data variables.prod {% endjetbrains %} -## Further reading +## Leitura adicional -- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)" +- "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md index 6f5aee4d6218..f19bfc9d1776 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -9,12 +9,12 @@ versions: type: quick_start topics: - Codespaces -ms.openlocfilehash: 5f97a137ec09191d5cbaa9c10aa280e10f11bbc0 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 01e4f3990cc47f61678811f7c4a77b86626fd8a5 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158642' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188261' --- O {% data variables.product.prodname_github_codespaces %} é um ambiente de desenvolvimento instantâneo e baseado na nuvem que usa um contêiner para fornecer linguagens, ferramentas e utilitários de desenvolvimento comuns. Os {% data variables.product.prodname_github_codespaces %} também são configuráveis, o que permite criar um ambiente de desenvolvimento personalizado para o projeto. Ao configurar um ambiente de desenvolvimento personalizado para seu projeto, você pode ter uma configuração de código reproduzível para todos os usuários do seu projeto. @@ -161,4 +161,4 @@ Se você trabalhar nos codespaces em um IDE do JetBrains, poderá adicionar plug - "[Como habilitar os {% data variables.product.prodname_github_codespaces %} na organização](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)" - "[Como gerenciar o custo dos {% data variables.product.prodname_github_codespaces %} na organização](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)" - "[Adicionar uma configuração de contêiner de desenvolvimento ao repositório](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)" -- "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)" +- "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)" diff --git a/translations/pt-BR/content/codespaces/getting-started/index.md b/translations/pt-BR/content/codespaces/getting-started/index.md index 37ed48d51182..807ae3ae268d 100644 --- a/translations/pt-BR/content/codespaces/getting-started/index.md +++ b/translations/pt-BR/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159404' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188269' --- diff --git a/translations/pt-BR/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/pt-BR/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..be1754a14f1c --- /dev/null +++ b/translations/pt-BR/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: O ciclo de vida do codespace +intro: 'É possível realizar o desenvolvimento em um ambiente do {% data variables.product.prodname_github_codespaces %} e manter seus dados ao longo de todo o ciclo de vida do codespace.' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188352' +--- +## Sobre o ciclo de vida de um codespace + +O ciclo de vida de um codespace começa quando você cria um código e termina quando você o exclui. Você pode desconectar-se e reconectar-se a um codespace ativo sem afetar seus processos em execução. Você pode parar e reiniciar o processo sem perder as alterações feitas no seu projeto. + +## Criar um codespace + +Quando você deseja trabalhar em um projeto, você pode optar por criar um novo codespaceou abrir um codespace já existente. Você tem a opção de criar um codespace com base em um branch do projeto sempre que realizar o desenvolvimento no {% data variables.product.prodname_github_codespaces %} ou manter um codespace de longo prazo para um recurso. {% data reusables.codespaces.starting-new-project-template %} Para saber mais, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" e "[Como criar um codespace com base em um modelo](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)". + +{% data reusables.codespaces.max-number-codespaces %} Da mesma forma, se você atingir o número máximo de codespaces ativos e tentar iniciar outro, será solicitado que você encerre um de seus codespaces ativos. + +Se você escolher criar um novo codespace, sempre que você trabalhar em um projeto, você deverá fazer push das alterações regularmente para que todos os novos commits estejam em {% data variables.product.prodname_dotcom %}. Se você optar por usar um codespace de longo prazo para o seu projeto, você deverá retirá-lo do branch padrão do repositório cada vez que começar a trabalhar no seu codespace para que seu ambiente tenha os commits mais recentes. Esse fluxo de trabalho é muito parecido como se você estivesse trabalhando com um projeto na sua máquina local. + +{% data reusables.codespaces.prebuilds-crossreference %} + +## Salvar alterações em um codespace + +Ao conectar-se a um código através da web, a gravação automática é habilitada automaticamente para o editor da web e configurada para salvar as alterações após um atraso. Ao conectar-se a um codespace por meio de {% data variables.product.prodname_vscode %} em execução no seu computador, você deverá habilitar o salvamento automático. Para obter mais informações, confira [Salvar/Salvar Automaticamente](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) na documentação do {% data variables.product.prodname_vscode %}. + +O trabalho será salvo em uma máquina virtual na nuvem. É possível fechar e parar um codespace e retornar ao trabalho salvo mais tarde. Se você tiver alterações não salvas, seu editor solicitará que você as salve antes de sair. No entanto, se o codespace for excluído, o trabalho também será. Para manter seu trabalho, faça commit das alterações e as envie por push ao repositório remoto ou publique-o em um novo repositório remoto, caso o codespace tenha sido criado com base em um modelo. Para obter mais informações, confira "[Como usar o controle do código-fonte no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)". + +## Limites de tempo do {% data variables.product.prodname_github_codespaces %} + +Se você não interagir com o seu codespace em execução ou se você sair do seu codespace sem pará-lo explicitamente, ele irá expirar após um determinado tempo de inatividade e irá parar de executar. Por padrão, um código irá expirar após 30 minutos de inatividade. No entanto, você pode personalizar a duração do período de tempo limite para novos codespaces que você criar. Para obter mais informações sobre como definir o período de tempo limite padrão para seus codespaces, confira "[Como definir o período de tempo limite para o {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)". Para obter mais informações sobre como interromper um codespace, confira "[Como interromper um codespace](#stopping-a-codespace)". + +Quando o tempo de um codespace chega ao limite, os seus dados são preservados da última vez que suas alterações foram salvas. Para obter mais informações, confira "[Como salvar alterações em um codespace](#saving-changes-in-a-codespace)". + +## Reconstruindo um codespace + +Você pode reconstruir um codespace para implementar alterações na configuração do contêiner de desenvolvimento. Para a maioria dos usos, você pode criar um novo codespace como uma alternativa à reconstrução de um codespace. Por padrão, quando você recompila seu codespace, {% data variables.product.prodname_github_codespaces %} reutilizará imagens do cache para acelerar o processo de recompilação. Como alternativa, você pode executar uma recompilação completa, que limpa o cache e recria o contêiner com imagens novas. + +Para obter mais informações, confira "[Introdução aos contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)" e "[Executar uma recompilação completa de um contêiner](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)". + +## Interrompendo um codespace + +{% data reusables.codespaces.stopping-a-codespace %} Para saber mais, confira "[Parar e iniciar um codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)". + +## Excluir um codespace + +Você pode criar um codespace para uma tarefa específica e, em seguida, excluir com segurança o codespace depois que você fizer push das alterações em um branch remoto. + +Se você tentar excluir um codespace com commits git que não foram enviados por push, o seu editor irá notificar você de que você tem alterações que não foram enviadas por push para um branch remoto. Você pode fazer push de todas as alterações desejadas e, em seguida, excluir o seu codespace ou continuar excluindo o seu codespace e todas as alterações que não foram enviadas por commit. Você também pode exportar seu codespace para um novo branch sem criar um novo codespace. Para obter mais informações, confira "[Como exportar alterações para um branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)". + +Os codespaces interrompidos que permanecerem inativos por um período especificado serão excluídos automaticamente. Por padrão, os codespaces inativos são excluídos após 30 dias, mas é possível personalizar o período de retenção deles. Para obter mais informações, confira "[Como configurar a exclusão automática de codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)". + +Se você criar um codespace, ele continuará acumulando encargos de armazenamento até ser excluído, independentemente de estar ativo ou ter sido interrompido. Para obter mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)". A exclusão de um codespace não reduz o valor atual faturável do {% data variables.product.prodname_github_codespaces %}, que é acumulado durante cada ciclo de cobrança mensal. Para obter mais informações, confira "[Como exibir o uso do {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)". + +Para obter mais informações sobre como excluir um codespace, confira "[Como excluir um codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)". + +## Perder a conexão ao usar o {% data variables.product.prodname_github_codespaces %} + +O {% data variables.product.prodname_github_codespaces %} é um ambiente de desenvolvimento baseado na nuvem que requer uma conexão com a Internet. Se você perder a conexão à internet enquanto trabalha em um codespace, você não poderá acessar seu codespace. No entanto, todas as alterações não comprometidas serão salvas. Quando você tiver acesso a uma conexão à internet novamente, você poderá conectar-se ao seu codespace no mesmo estado em que ele foi deixado. Se você tiver uma conexão instável, você deverá se fazer envio por commit e push das suas alterações com frequência. + +Se você geralmente trabalha offline, é possível usar o arquivo `devcontainer.json` com a [extensão "Contêineres de desenvolvimento"](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) para o {% data variables.product.prodname_vscode_shortname %} a fim de compilar e anexar arquivos a um contêiner de desenvolvimento local do seu repositório. Para obter mais informações, confira [Desenvolvimento em um contêiner](https://code.visualstudio.com/docs/remote/containers) na documentação do {% data variables.product.prodname_vscode %}. diff --git a/translations/pt-BR/content/codespaces/index.md b/translations/pt-BR/content/codespaces/index.md index 9a6928615f7b..163c51791c8d 100644 --- a/translations/pt-BR/content/codespaces/index.md +++ b/translations/pt-BR/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160431' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188301' --- diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md index a6999dc35b91..7c249493dba6 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md @@ -9,12 +9,12 @@ versions: type: how_to topics: - Codespaces -ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: f17bb20aa919ca94cd13e14a6f770cea23042b2b +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158994' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188277' --- ## Visão geral @@ -39,7 +39,7 @@ Se a imagem especificada na configuração do contêiner de desenvolvimento não {% note %} **Observações**: -* A política de imagem base só é aplicada quando um codespace é criado. Atualmente, ela não é aplicada quando você recompila um contêiner. Isso será alterado em uma versão futura. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace)". +* A política de imagem base só é aplicada quando um codespace é criado. Atualmente, ela não é aplicada quando você recompila um contêiner. Isso será alterado em uma versão futura. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle#rebuilding-a-codespace)". * A política de imagem base não se aplicará à imagem padrão ou à imagem usada para recuperar um codespace se, em uma configuração de contêiner de desenvolvimento, for introduzido um erro que impeça a recriação do contêiner. {% endnote %} @@ -80,7 +80,7 @@ Por exemplo, você pode criar uma política em toda a organização que restring * "[Como restringir o acesso a tipos de computadores](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" * "[Como restringir a visibilidade das portas encaminhadas](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" * "[Como restringir o período de tempo limite ocioso](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)" - * "[Como restringir o período de retenção de codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)" + * "[Como restringir o período de retenção dos codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)" 1. Depois de concluir a adição de restrições à política, clique em **Salvar**. A política é aplicada quando qualquer pessoa tenta criar um codespace que pode ser cobrado para sua organização. A restrição de imagem base não afeta os codespaces existentes, ativos ou parados. @@ -100,4 +100,4 @@ Você pode excluir ou editar uma política existente. Por exemplo, você talvez 1. Exibir a página "Políticas de codespaces". Para obter mais informações, confira "[Como adicionar uma política para definir as imagens permitidas](#adding-a-policy-to-define-the-allowed-images)". 1. Clique no botão excluir à direita da política que você deseja excluir. - ![Captura de tela do botão excluir de uma política](/assets/images/help/codespaces/policy-delete.png) + ![Captura de tela do botão Excluir de uma política](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index d755ec57f7ab..9e3a1d1eccfe 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -1,6 +1,6 @@ --- -title: Introduction to dev containers -intro: 'When you work in a codespace, the environment you are working in is created using a development container, or dev container, hosted on a virtual machine.' +title: Introdução aos contêineres de desenvolvimento +intro: 'Quando você trabalha em um codespace, o ambiente de trabalho é criado usando um contêiner de desenvolvimento ou um contêiner de desenvolvimento hospedado em uma máquina virtual.' permissions: People with write permissions to a repository can create or edit the codespace configuration. redirect_from: - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project @@ -16,71 +16,76 @@ topics: - Codespaces - Set up - Fundamentals +ms.openlocfilehash: 646f8068e68040f1d12f8155c3ba9e2bdb84c2ca +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185088' --- +## Sobre contêineres de desenvolvimento -## About dev containers +Os contêineres de desenvolvimento ou contêineres de des são contêineres do Docker configurados especificamente para fornecer um ambiente de desenvolvimento completo. Sempre que você trabalha em um codespace, está usando um contêiner de desenvolvimento em uma máquina virtual. -Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine. +Você pode configurar o contêiner de desenvolvimento para um repositório para que os codespaces criados para esse repositório forneçam um ambiente de desenvolvimento personalizado, completo com todas as ferramentas e runtimes necessários para trabalhar em um projeto específico. Se você não definir uma configuração no repositório, {% data variables.product.prodname_github_codespaces %} usará uma configuração padrão, que contém muitas das ferramentas comuns que sua equipe pode precisar para desenvolvimento com seu projeto. Para obter mais informações, confira "[Como usar a configuração de contêiner de desenvolvimento padrão](#using-the-default-dev-container-configuration)". -You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +Os arquivos de configuração para um contêiner de desenvolvimento estão contidos em um diretório `.devcontainer` em seu repositório. Você pode usar {% data variables.product.prodname_vscode %} para adicionar arquivos de configuração para você. Você pode escolher entre uma seleção de configurações predefinidas para vários tipos de projeto. Você pode usá-las sem configurações adicionais ou editar as configurações para refinar o ambiente de desenvolvimento que elas produzem. Para obter mais informações, confira "[Como usar uma configuração de contêiner de desenvolvimento predefinida](#using-a-predefined-dev-container-configuration)". -The configuration files for a dev container are contained in a `.devcontainer` directory in your repository. You can use {% data variables.product.prodname_vscode %} to add configuration files for you. You can choose from a selection of predefined configurations for various project types. You can use these without further configuration, or you can edit the configurations to refine the development environment they produce. For more information, see "[Using a predefined dev container configuration](#using-a-predefined-dev-container-configuration)." +Como alternativa, você pode adicionar seus arquivos de configuração personalizados. Para obter mais informações, confira "[Como criar uma configuração de contêiner de desenvolvimento personalizada](#creating-a-custom-dev-container-configuration)". -Alternatively, you can add your own custom configuration files. For more information, see "[Creating a custom dev container configuration](#creating-a-custom-dev-container-configuration)." +Você pode definir uma única configuração de contêiner de desenvolvimento para um repositório, configurações diferentes para diferentes branches ou várias configurações. Quando várias configurações estão disponíveis, os usuários podem escolher sua configuração preferencial ao criar um codespace. Isso é particularmente útil para grandes repositórios que contêm código-fonte em diferentes linguagens de programação ou para diferentes projetos. Você pode criar uma variedade de configurações que permitem que diferentes equipes trabalhem em um codespace configurado adequadamente para o trabalho que estão realizando. -You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing. - -When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)." +Ao criar um codespace com base em um modelo, você pode começar com um ou mais arquivos de configuração de contêiner de des no workspace. Para configurar ainda mais o ambiente, você pode adicionar ou remover configurações desses arquivos e recompilar o contêiner para aplicar as alterações ao codespace no qual está trabalhando. Se você publicar o codespace em um repositório no {% data variables.product.product_name %}, todos os codespaces criados com base nesse repositório compartilharão a configuração definida. Para obter mais informações, confira "[Como aplicar alterações de configuração a um codespace](#applying-configuration-changes-to-a-codespace)" e "[Como criar um codespace com base em um modelo](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)". ### devcontainer.json -The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file. +O arquivo principal em uma configuração de contêiner de desenvolvimento é o arquivo `devcontainer.json`. Você pode usar esse arquivo para determinar o ambiente de codespaces criados para seu repositório. O conteúdo desse arquivo define um contêiner de desenvolvimento que pode incluir estruturas, ferramentas, extensões e encaminhamento de porta. O arquivo `devcontainer.json` geralmente contém uma referência a um Dockerfile, que normalmente está localizado ao lado do arquivo `devcontainer.json`. -If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +Se você criar um codespace a com base em um repositório sem um arquivo `devcontainer.json` ou se você começar com base em um modelo em branco do {% data variables.product.company_short %}, a configuração padrão do contêiner de des será usada. Para obter mais informações, confira "[Como usar a configuração de contêiner de desenvolvimento padrão](#using-the-default-dev-container-configuration)". -The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`. +O arquivo `devcontainer.json` geralmente está localizado no diretório `.devcontainer` do repositório. Como alternativa, você pode localizá-lo diretamente na raiz do repositório, neste caso o nome do arquivo deve começar com um ponto: `.devcontainer.json`. -If you want to have a choice of dev container configurations in your repository, any alternatives to the `.devcontainer/devcontainer.json` (or `.devcontainer.json`) file must be located in their own subdirectory at the path `.devcontainer/SUBDIRECTORY/devcontainer.json`. For example, you could have a choice of two configurations: +Se você quiser ter opções de configurações de contêiner de desenvolvimento em seu repositório, quaisquer alternativas ao arquivo `.devcontainer/devcontainer.json` (ou `.devcontainer.json` ) devem estar localizadas em seu subdiretório no caminho `.devcontainer/SUBDIRECTORY/devcontainer.json`. Por exemplo, você pode escolher entre duas configurações: * `.devcontainer/database-dev/devcontainer.json` * `.devcontainer/gui-dev/devcontainer.json` -When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory. +Quando você tem vários arquivos `devcontainer.json` em seu repositório, cada codespace é criado a partir de apenas uma das configurações. As configurações não podem ser importadas ou herdadas entre arquivos `devcontainer.json`. Se um arquivo `devcontainer.json` em um subdiretório personalizado tiver arquivos dependentes, como o Dockerfile ou scripts executados por comandos no arquivo `devcontainer.json`, é recomendável que você localize esses arquivos no mesmo subdiretório. -For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." +Para obter informações de como escolher sua configuração de contêiner de des preferencial ao criar um codespace, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)". {% data reusables.codespaces.more-info-devcontainer %} -#### How to use the devcontainer.json +#### Como usar o devcontainer.json. -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. +É útil pensar no arquivo `devcontainer.json` como fornecendo "customização" em vez de "personalização". Você deve incluir apenas itens que todos que trabalham em sua base de código precisam como elementos padrão do ambiente de desenvolvimento, não itens que são preferências pessoais. Itens como linters são bons para padronizar e exigir que todos tenham instalado, então é bom incluí-los em seu arquivo `devcontainer.json`. Itens como decoradores ou temas da interface do usuário são escolhas pessoais que não devem ser colocadas no arquivo `devcontainer.json`. -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)." +Você pode personalizar os codespaces usando dotfiles e a Sincronização de Configurações. Para obter mais informações, confira "[Como personalizar o {% data variables.product.prodname_github_codespaces %} da conta](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)". ### Dockerfile -You can add a Dockerfile as part of your dev container configuration. +Você pode adicionar um Dockerfile como parte da configuração do contêiner de desenvolvimento. -The Dockerfile is a text file that contains the instructions needed to create a Docker container image. This image is used to generate a development container each time someone creates a codespace using the `devcontainer.json` file that references this Dockerfile. The instructions in the Dockerfile typically begin by referencing a parent image on which the new image that will be created is based. This is followed by commands that are run during the image creation process, for example to install software packages. +O Dockerfile é um arquivo de texto que contém as instruções necessárias para criar uma imagem de contêiner do Docker. Essa imagem é usada para gerar um contêiner de desenvolvimento toda vez que alguém cria um codespace usando o arquivo `devcontainer.json` que faz referência a esse Dockerfile. As instruções no Dockerfile geralmente começam fazendo referência a uma imagem pai na qual a nova imagem que será criada se baseia. Isso é seguido por comandos que são executados durante o processo de criação da imagem, por exemplo, para instalar pacotes de software. -The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced. +O Dockerfile para um contêiner de desenvolvimento geralmente está localizado na pasta `.devcontainer`, ao lado do `devcontainer.json` ao qual ele faz referência. {% note %} -**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. For more information, see "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)." +**Observação**: como alternativa ao uso de um Dockerfile, você pode usar a propriedade `image` no arquivo `devcontainer.json` para se referir diretamente a uma imagem existente que deseja usar. A imagem especificada aqui precisa ser permitida nas políticas de imagem da organização definidas. Para obter mais informações, confira "[Como restringir a imagem base dos codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)". Se nem um Dockerfile nem uma imagem forem encontrados, a imagem de contêiner padrão será usada. Para obter mais informações, confira "[Como usar a configuração de contêiner de desenvolvimento padrão](#using-the-default-dev-container-configuration)". {% endnote %} -#### Simple Dockerfile example +#### Exemplo simples do Dockerfile -The following example uses four instructions: +O seguinte exemplo usa quatro instruções: -`ARG` defines a build-time variable. +`ARG` define uma variável de tempo de compilação. -`FROM` specifies the parent image on which the generated Docker image will be based. +`FROM` especifica a imagem pai na qual a imagem do Docker gerada será baseada. -`COPY` copies a file and adds it to the filesystem. +`COPY` copia um arquivo e o adiciona ao sistema de arquivos. -`RUN` updates package lists and runs a script. You can also use a `RUN` instruction to install software, as shown by the commented out instructions. To run multiple commands, use `&&` to combine the commands into a single `RUN` statement. +`RUN` atualiza listas de pacotes e executa um script. Você também pode usar uma instrução `RUN` para instalar o software, conforme mostrado nas instruções comentadas. Para executar vários comandos, use `&&` para combinar os comandos em uma única instrução `RUN`. ```Dockerfile{:copy} ARG VARIANT="16-buster" @@ -97,11 +102,11 @@ COPY library-scripts/github-debian.sh /tmp/library-scripts/ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh ``` -For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation. +Para obter mais informações sobre as instruções do Dockerfile, confira "[Referência do Dockerfile](https://docs.docker.com/engine/reference/builder)" na documentação do Docker. -#### Using a Dockerfile +#### Como usar um Dockerfile -To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property. +Para usar um Dockerfile como parte de uma configuração de contêiner de desenvolvimento, faça referência a ele em seu arquivo `devcontainer.json` usando a propriedade `dockerfile`. ```json{:copy} { @@ -111,134 +116,134 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo } ``` -Various options are available to you if you want to use existing container orchestration in your dev container. For more information, see the "Orchestration options" section of the [Specification](https://containers.dev/implementors/spec/#orchestration-options) on the Development Containers website. +Várias opções estarão disponíveis se você quiser usar a orquestração de contêiner existente no contêiner de desenvolvimento. Para obter mais informações, confira a seção "Opções de orquestração" da [Especificação](https://containers.dev/implementors/spec/#orchestration-options) no site Contêineres de Desenvolvimento. -## Using the default dev container configuration +## Como usar a configuração de contêiner de desenvolvimento padrão -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace using a default Linux image. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs. +Se você não definir uma configuração em seu repositório, {% data variables.product.prodname_dotcom %} cria um codespace usando uma imagem padrão do Linux. Essa imagem do Linux inclui várias versões de runtime para linguagens populares como Python, Node, PHP, Java, Go, C++, Ruby e .NET Core/C#. As versões mais recentes ou LTS dessas linguagens são usadas. Também há ferramentas para dar suporte à ciência de dados e aprendizado de máquina, como o JupyterLab e o Conda. A imagem também inclui outras ferramentas e utilitários de desenvolvedor como Git, GitHub CLI, yarn, openssh e vim. Para ver todas as linguagens, as ferramentas e os runtimes incluídos, use o comando `devcontainer-info content-url` no terminal do codespace e siga a URL gerada pelo comando. -For information about what's included in the default Linux image, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository. +Para obter informações sobre o que está incluído na imagem padrão do Linux, confira o repositório [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal). -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides. +A configuração padrão é uma boa opção se você estiver trabalhando em um pequeno projeto que usa as linguagens e ferramentas que o {% data variables.product.prodname_github_codespaces %} fornece. -## Using a predefined dev container configuration +## Como usar uma configuração de contêiner de desenvolvimento predefinida -If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. +Se você usar os {% data variables.product.prodname_codespaces %} no {% data variables.product.prodname_vscode %} ou em um navegador da Web, poderá criar uma configuração de contêiner de desenvolvimento para o repositório escolhendo opções em uma lista de configurações predefinidas. Essas configurações oferecem definições comuns para tipos de projeto específicos e ajudam a começar a trabalhar rapidamente com uma configuração que já tem as opções de contêiner apropriadas, as configurações do {% data variables.product.prodname_vscode %} e as extensões do {% data variables.product.prodname_vscode %} que devem ser instaladas. -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository. +Usar uma configuração predefinida é uma ótima ideia se você precisa de uma extensão adicional. Você também pode começar com uma configuração predefinida e alterá-la conforme necessário para o seu projeto. Para obter mais informações sobre as definições de contêineres de desenvolvimento predefinidos, confira o repositório [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src). -You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar. +Você pode adicionar uma configuração de contêiner de desenvolvimento predefinida enquanto trabalha em um codespace ou enquanto trabalha em um repositório localmente. Para fazer isso no {% data variables.product.prodname_vscode_shortname %} enquanto você está trabalhando localmente e não está conectado a um codespace, a extensão "Contêineres de Desenvolvimento" precisa estar instalada e habilitada. Para obter mais informações sobre essa extensão, confira [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). O procedimento a seguir descreve o processo quando você está usando um codespace. As etapas no {% data variables.product.prodname_vscode_shortname %} quando você não está conectado a um codespace são muito semelhantes. {% data reusables.codespaces.command-palette-container %} -1. Click the definition you want to use. +1. Clique na definição que você deseja usar. - ![Screenshot of a list of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) + ![Captura de tela da lista de definições de contêiner predefinido](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)." -1. Click **OK**. +1. Siga as instruções para personalizar sua definição. Para obter mais informações sobre as opções usadas para personalizar sua definição, confira "[Como adicionar recursos adicionais ao arquivo `devcontainer.json`](#adding-additional-features-to-your-devcontainerjson-file)". +1. Clique em **OK**. - ![Screenshot of the OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) + ![Captura de tela do botão OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." +1. Se você estiver trabalhando em um codespace, aplique suas alterações clicando em **Recompilar agora** na mensagem na parte inferior direita da janela. Para obter mais informações sobre como recompilar seu contêiner, confira "[Como aplicar alterações à sua configuração](#applying-configuration-changes-to-a-codespace)". - ![Screenshot of a prompt to 'Rebuild now'](/assets/images/help/codespaces/rebuild-prompt.png) + ![Captura de tela de um prompt para 'Recompilar agora'](/assets/images/help/codespaces/rebuild-prompt.png) -### Adding additional features to your `devcontainer.json` file +### Como adicionar outros recursos ao arquivo `devcontainer.json` -{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)." +{% data reusables.codespaces.about-features %} Para obter mais informações, confira "[Como adicionar recursos a um arquivo `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)". -## Creating a custom dev container configuration +## Como criar uma configuração de contêiner de desenvolvimento personalizada -If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file. +Se nenhuma das configurações predefinidas atender às suas necessidades, você poderá criar uma configuração personalizada criando seu arquivo `devcontainer.json`. -* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository. -* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory. +* Se você estiver adicionando um único arquivo `devcontainer.json` que será usado por todos que criarem um codespace de seu repositório, crie o arquivo em um diretório `.devcontainer` na raiz do repositório. +* Se você quiser oferecer aos usuários uma opção de configuração, poderá criar vários arquivos `devcontainer.json` personalizados, cada um localizado em um subdiretório separado do diretório `.devcontainer`. {% note %} - **Notes**: - - You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not. - - {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)." + **Observações**: + - você não pode colocar os arquivos `devcontainer.json` em diretórios mais de um nível abaixo de `.devcontainer`. Por exemplo, um arquivo em `.devcontainer/teamA/devcontainer.json` funcionará, mas `.devcontainer/teamA/testing/devcontainer.json` não funcionará. + - {% data reusables.codespaces.configuration-choice-templates %} Para obter mais informações, confira "[Como configurar um repositório de modelos para os {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)". {% endnote %} - If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." + Se vários arquivos `devcontainer.json` forem encontrados no repositório, eles serão listados na página de opções de criação do codespace. Para obter mais informações, confira "[Como criar um codespace para um repositório](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)". - ![Screenshot of a choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png) + ![Captura de tela de opções de arquivos de configuração](/assets/images/help/codespaces/configuration-file-choice.png) -### Adding a `devcontainer.json` file +### Como adicionar um arquivo `devcontainer.json` -If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}. -1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. -1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**. +Se você ainda não tiver um arquivo `devcontainer.json` no repositório, adicione-o rapidamente por meio do {% data variables.product.prodname_dotcom_the_website %}. +1. Navegue até o repositório e clique na lista suspensa **{% octicon "code" aria-label="The code icon" %} Código**. +1. Na guia **Codespaces**, clique nas reticências ( **...** ) e selecione **Configurar contêiner de desenvolvimento**. - ![Screenshot of the Code dropdown, with "Configure dev container" highlighted](/assets/images/help/codespaces/configure-dev-container.png) + ![Captura de tela da lista suspensa Código, com a opção "Configurar contêiner de desenvolvimento" realçada](/assets/images/help/codespaces/configure-dev-container.png) -A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)." +Um novo arquivo `.devcontainer/devcontainer.json` será aberto no editor. O arquivo conterá algumas propriedades iniciais, incluindo um objeto `features` ao qual você pode adicionar novas ferramentas, bibliotecas ou runtimes. Para obter mais informações, confira "[Como adicionar recursos a um arquivo `devcontainer.json`](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)". -If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev. +Se o repositório já contiver um ou mais arquivos `devcontainer.json`, um clique em **Configurar contêiner de desenvolvimento** abrirá o arquivo `devcontainer.json` existente com a precedência mais alta de acordo com a [especificação](https://containers.dev/implementors/spec/#devcontainerjson) em containers.dev. -### Default configuration selection during codespace creation +### Seleção da configuração padrão durante a criação do codespace -If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default. +Se `.devcontainer/devcontainer.json` ou `.devcontainer.json` existir, será a seleção padrão na lista de arquivos de configuração disponíveis quando você criar um codespace. Se nenhum dos arquivos existir, a configuração de contêiner de desenvolvimento padrão será selecionada por padrão. -![Screenshot of the default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png) +![Captura de tela da opção de configuração padrão selecionada](/assets/images/help/codespaces/configuration-file-choice-default.png) -### Editing the devcontainer.json file +### Como editar o arquivo devcontainer.json. -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +Você pode adicionar e editar as chaves de configuração com suporte no arquivo `devcontainer.json` para especificar aspectos do ambiente do codespace, como quais extensões de {% data variables.product.prodname_vscode_shortname %} serão instaladas. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. +O arquivo `devcontainer.json` é gravado usando o formato JSONC (JSON com comentários). Isso permite que você inclua comentários no arquivo de configuração. Para obter mais informações, confira "[Como editar JSON com {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" na documentação {% data variables.product.prodname_vscode_shortname %}. {% note %} -**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors. +**Observação**: se você usar um linter para validar o arquivo `devcontainer.json`, verifique se está definido como JSONC e não JSON, ou comentários serão relatados como erros. {% endnote %} -### Interface settings for {% data variables.product.prodname_vscode_shortname %} +### Configurações da interface do {% data variables.product.prodname_vscode_shortname %} -You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor. +Você pode definir as configurações da interface do {% data variables.product.prodname_vscode_shortname %}, com três escopos: Workspace, Remoto [Codespaces] e Usuário. Você pode ver esses escopos no editor de Configurações do {% data variables.product.prodname_vscode_shortname %}. -![Screenshot showing the choice of scopes in the Settings editor](/assets/images/help/codespaces/scopes-for-vscode.png) +![Captura de tela mostrando a escolha de escopos no editor de Configurações](/assets/images/help/codespaces/scopes-for-vscode.png) -If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User. +Se uma configuração for definida em vários escopos, as configurações de Workspace serão prioritárias e, em seguida, Repositórios Remotos [Codespaces] e, por fim, Usuário. -You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places. +Você pode definir as configurações padrão da interface do {% data variables.product.prodname_vscode_shortname %} em dois locais. -* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace. -* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace. +* As configurações da interface definidas no arquivo `.vscode/settings.json` no repositório são aplicadas como configurações no escopo do Workspace no codespace. +* As configurações da interface definidas na chave `settings` no arquivo `devcontainer.json` são aplicadas como configurações com escopo Remoto [Codespaces] no codespace. -## Applying configuration changes to a codespace +## Como aplicar alterações de configuração a um codespace -Changes to a configuration will be applied the next time you create a codespace. However, you can apply your changes to an existing codespace by rebuilding the container. You can do this within a codespace in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application, or you can use {% data variables.product.prodname_cli %}. +As alterações em uma configuração serão aplicadas na próxima vez que você criar um codespace. No entanto, você pode aplicar suas alterações a um codespace existente recriando o contêiner. Você pode fazer isso em um codespace no aplicativo da área de trabalho ou no cliente Web do {% data variables.product.prodname_vscode_shortname %}, ou pode usar o {% data variables.product.prodname_cli %}. -### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application +### Como recompilar o contêiner de desenvolvimento no cliente Web ou aplicativo da área de trabalho do {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.rebuild-command %} 1. {% data reusables.codespaces.recovery-mode %} - ![Screenshot of the error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) + ![Captura de tela da mensagem de erro sobre o modo de recuperação](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. + - Para diagnosticar o erro revisando os logs de criação, clique em **Exibir log de criação**. + - Para corrigir os erros identificados nos logs, atualize o arquivo `devcontainer.json`. + - Para aplicar as alterações, reconstrua seu contêiner. -### Using {% data variables.product.prodname_cli %} to rebuild a dev container +### Usando o {% data variables.product.prodname_cli %} para recompilar um contêiner de desenvolvimento -If you've changed a dev container configuration outside of VS Code (for example, on {% data variables.product.prodname_dotcom_the_website %} or in a JetBrains IDE), you can use {% data variables.product.prodname_cli %} to rebuild the dev container for an existing codespace. +Se você tiver alterado uma configuração de contêiner de desenvolvimento fora do VS Code (por exemplo, em {% data variables.product.prodname_dotcom_the_website %} ou em um IDE jetBrains), poderá usar {% data variables.product.prodname_cli %} para recompilar o contêiner de desenvolvimento para um codespace existente. -1. In a terminal, enter the following command. +1. Em um terminal, insira o comando a seguir. ``` gh cs rebuild ``` - Your codespaces are listed. + Seus codespaces estão listados. -1. Use the arrow keys on your keyboard to highlight the required codespace, then press Enter. +1. Use as teclas de direção no teclado para realçar o codespace necessário e pressione Enter. -## Further reading +## Leitura adicional -- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" +- "[Como pré-compilar os codespaces](/codespaces/prebuilding-your-codespaces)" diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index 99aab2edf71a..44aa07505cf3 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: Criar modelos de pull request no repositório -intro: 'Quando você adicionar um modelo de pull request ao repositório, os contribuidores do projeto verão automaticamente o conteúdo do modelo no texto da pull request.' +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084086' --- -Para obter mais informações, confira "[Sobre os modelos de solicitações de pull e de problemas](/articles/about-issue-and-pull-request-templates)". -Crie um subdiretório *PULL_REQUEST_TEMPLATE/* em uma das pastas compatíveis para conter vários modelos de solicitações de pull e use o parâmetro de consulta `template` para especificar o modelo que preencherá o corpo da solicitação de pull. Para obter mais informações, confira "[Como usar parâmetros de consulta para criar uma solicitação de pull](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)". +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -Você pode criar modelos de solicitações de pull padrão para sua conta de organização{% ifversion fpt or ghes or ghec %} ou pessoal {% endif %}. Para obter mais informações, confira "[Como criar um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)". +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## Adicionar um modelo de pull request - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. No campo nome do arquivo: - - Para tornar o modelo de solicitação de pull visível no diretório raiz do repositório, dê ao modelo de solicitação de pull o nome `pull_request_template.md`. - ![Novo nome do modelo de solicitação de pull no diretório raiz](/assets/images/help/repository/pr-template-file-name.png) - - Para tornar o modelo de solicitação de pull visível no diretório `docs` do repositório, dê ao modelo de solicitação de pull o nome `docs/pull_request_template.md`. - ![Novo modelo de solicitação de pull no diretório docs](/assets/images/help/repository/pr-template-file-name-docs.png) - - Para armazenar o arquivo em um diretório oculto, dê ao modelo de solicitação de pull o nome `.github/pull_request_template.md`. - ![Novo modelo de solicitação de pull no diretório oculto](/assets/images/help/repository/pr-template-hidden-directory.png) - - Para criar vários modelos de solicitações de pull e usar o parâmetro de consulta `template` para especificar um modelo para preencher o corpo da solicitação de pull, digite *.github/PULL_REQUEST_TEMPLATE/* e o nome do modelo de solicitação de pull. Por exemplo, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Você também pode armazenar vários modelos de solicitações de pull em um subdiretório `PULL_REQUEST_TEMPLATE` na raiz ou nos diretórios `docs/`. Para obter mais informações, confira "[Sobre a automação para problemas e solicitações de pull com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)". - ![Vários novos modelos de solicitações de pull no diretório oculto](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. No texto do novo arquivo, adicione seu modelo de pull request. Pode conter: - - Uma [referência a um problema relacionado](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) no repositório. - - Uma descrição das alterações propostas na pull request. - - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) da pessoa ou da equipe responsável pela revisão das alterações propostas. -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Os modelos estão disponíveis para os colaboradores quando eles forem mesclados no branch padrão do repositório. +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## Leitura adicional +## Further reading -- "[Sobre modelos de problemas e solicitação de pull](/articles/about-issue-and-pull-request-templates)" -- "[Sobre a automação para problemas e solicitações de pull com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" -- "[Como criar uma solicitação de pull](/articles/creating-a-pull-request)" +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" diff --git a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md index fafd93d4dd63..6b212d15c053 100644 --- a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md +++ b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md @@ -1,123 +1,125 @@ --- -title: Getting started with GitHub Copilot in a JetBrains IDE +title: Introdução ao GitHub Copilot em um IDE JetBrains shortTitle: JetBrains IDE -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.' +intro: 'Saiba como instalar o {% data variables.product.prodname_copilot %} em um IDE JetBrains e começar a ver sugestões enquanto você escreve comentários e código.' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: ae879b5834007a34ab0e3a7a45dcae4c1e31bc4f +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185056' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and JetBrains IDEs +## Sobre o {% data variables.product.prodname_copilot %} e IDEs JetBrains {% data reusables.copilot.procedural-intro %} -If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux. +Se você usar um IDE JetBrains, poderá exibir e incorporar sugestões do {% data variables.product.prodname_copilot %} diretamente no editor. Este guia demonstra como usar o {% data variables.product.prodname_copilot %} dentro de um IDE JetBrains para macOS, Windows ou Linux. -## Prerequisites +## Pré-requisitos {% data reusables.copilot.jetbrains-ides %} -## Installing the {% data variables.product.prodname_copilot %} extension in your JetBrains IDE - -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 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) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. - - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**. - ![Screenshot of JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png) +## Instalar a extensão do {% data variables.product.prodname_copilot %} no seu IDE JetBrains + +Para usar o {% data variables.product.prodname_copilot %} em um IDE JetBrains, você deverá instalar a extensão do {% data variables.product.prodname_copilot %}. O procedimento a seguir guiará você pela instalação do plug-in do {% data variables.product.prodname_copilot %} no IntelliJ IDEA. As etapas para instalar o plug-in em outro IDE com suporte podem ser diferentes. + +1. No IDE JetBrains, no menu **Arquivo** do Windows, ou sob o nome do IDE para Mac (por exemplo, **PyCharm** ou **IntelliJ**), clique em **Configurações** para o Windows ou em **Preferências** para o Mac. +2. No menu esquerdo da caixa de diálogo **Configurações/Preferências**, clique em **Plug-ins**. +3. Na parte superior da caixa de diálogo **Configurações/Preferências**, clique em **Marketplace**. Na barra de pesquisa, pesquise **{% data variables.product.prodname_copilot %}** e clique em **Instalar**. + ![Captura de tela da pesquisa do Marketplace](/assets/images/help/copilot/jetbrains-marketplace.png) +1. Depois que o {% data variables.product.prodname_copilot %} estiver instalado, clique em **Reiniciar IDE**. +1. Depois que o IDE JetBrains for reiniciado, clique no menu **Ferramentas**. Clique em **{% data variables.product.prodname_copilot %}** e clique **Logon no {% data variables.product.prodname_dotcom %}** . + ![Captura de tela do menu de ferramentas do JetBrains](/assets/images/help/copilot/jetbrains-tools-menu.png) +1. Na caixa de diálogo "Entrar no {% data variables.product.prodname_dotcom %}", para copiar o código do dispositivo e abrir a janela de ativação do dispositivo, clique em **Copiar e Abrir**. + ![Captura de tela da cópia e abertura do código do dispositivo](/assets/images/help/copilot/device-code-copy-and-open.png) +1. Uma janela de ativação do dispositivo será aberta no navegador. Cole o código do dispositivo e clique em **Continuar**. + + - Para colar o código no Windows ou Linux, pressione Ctrl+v. + - Pra colar o código no macOS, pressione comando+v. +1. O {% data variables.product.prodname_dotcom %} solicitará as permissões necessárias para o {% data variables.product.prodname_copilot %}. Para aprovar essas permissões, clique em **Autorizar o plug-in do {% data variables.product.prodname_copilot %}** . +1. Depois que as permissões forem aprovadas, o IDE JetBrains mostrará uma confirmação. Para começar a usar o {% data variables.product.prodname_copilot %}, clique em **OK**. + ![Captura de tela da confirmação de permissões do IDE JetBrains](/assets/images/help/copilot/jetbrains-ide-confirmation.png) -## Seeing your first suggestion +## Como ver a primeira sugestão {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} Os exemplos a seguir estão em Java, mas outras linguagens funcionarão da mesma forma. {% data reusables.copilot.create-java-file %} -1. In the Java file, create a class by typing `class Test`. - {% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary. - ![Screenshot of the Java class body suggestion](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary. +1. No arquivo Java, crie uma classe digitando `class Test`. + O {% data variables.product.prodname_copilot %} sugerirá automaticamente um corpo de classe em texto esmaecido, conforme mostrado abaixo. A sugestão exata pode variar. + ![Captura de tela da sugestão do corpo da classe Java](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} +1. Para solicitar que o {% data variables.product.prodname_copilot %} sugira um corpo de função, digite a linha a seguir abaixo do colchete da função `main`. A sugestão exata pode variar. {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) -{% data reusables.copilot.accept-suggestion %} + ![Captura de tela da sugestão do corpo da função Java](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png) {% data reusables.copilot.accept-suggestion %} -{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code. +O {% data variables.product.prodname_copilot %} tentará fazer a correspondência entre o contexto e o estilo do seu código. Você sempre poderá editar o código sugerido. -## Seeing alternative suggestions +## Como ver sugestões alternativas {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. -{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -{% data reusables.copilot.see-alternative-suggestions %} +1. Para solicitar que o {% data variables.product.prodname_copilot %} mostre uma sugestão, digite a linha a seguir no arquivo Java. +{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | Sistema operacional | Ver a próxima sugestão | Ver a sugestão anterior | | :- | :- | :- | - | macOS | Option+] | Option+[ | + | macOS | Opção+] | Opção+[ | | Windows | Alt+] | Alt+[ | | Linux | Alt+] | Alt+[ | {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## Como ver várias sugestões em uma nova guia {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file. +1. Para solicitar que o {% data variables.product.prodname_copilot %} mostre uma sugestão, digite a linha a seguir no arquivo Java. {% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %} -1. Open a new tab with multiple additional suggestions. - - On macOS, press Command+Shift+A, then click **Open GitHub Copilot**, or press Command+Shift+\ to open the new tab immediately. - - On Windows or Linux, press Ctrl+Enter, then click **Open GitHub Copilot**. - ![Screenshot of dialogue to open Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. Abra uma nova guia com várias sugestões adicionais. + - No macOS, pressione Command+Shift+A e clique em **Abrir o GitHub Copilot** ou pressione Command+Shift+\ para abrir a nova guia imediatamente. + - No Windows ou Linux, pressione Ctrl+Enter e clique em **Abrir o GitHub Copilot**. + ![Captura de tela do diálogo para abrir o Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png) +1. Para aceitar uma sugestão, acima da sugestão, clique em **Aceitar Solução**. Para rejeitar todas as sugestões, feche a guia. -## Generating code suggestions from comments +## Como gerar sugestões de código por meio de comentários {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-java-file %} -1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines. +1. Para solicitar que o {% data variables.product.prodname_copilot %} sugira uma implementação de uma função no arquivo Java, digite as linhas a seguir. ```java{:copy} // find all images without alternate text // and give them a red border void process () { ``` - ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/comment-suggestion-jetbrains.png) + ![Captura de tela da sugestão do corpo da função Java](/assets/images/help/copilot/comment-suggestion-jetbrains.png) -## Enabling and disabling {% data variables.product.prodname_copilot %} +## Como habilitar e desabilitar o {% data variables.product.prodname_copilot %} -You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out. +Você pode habilitar ou desabilitar o {% data variables.product.prodname_copilot %} para todas as linguagens ou para linguagens individuais. O ícone de status do {% data variables.product.prodname_copilot %} no painel inferior da janela do IDE JetBrains indica se o {% data variables.product.prodname_copilot %} está habilitado ou desabilitado. Quando habilitado, o ícone fica realçado. Quando desabilitado, o ícone fica esmaecido. -1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window. - ![Screenshot of the status icon in IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png) -2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing. +1. Para habilitar ou desabilitar o {% data variables.product.prodname_copilot %}, clique no ícone de status no painel inferior da janela JetBrains. + ![Captura de tela do ícone de status no IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png) +2. Se você estiver desabilitando o {% data variables.product.prodname_copilot %}, será perguntado se deseja desabilitá-lo globalmente ou para a linguagem do arquivo que está editando no momento. - - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**. - - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**. - ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) + - Para desabilitar as sugestões do {% data variables.product.prodname_copilot %} globalmente, clique em **Desabilitar Preenchimentos**. + - Para desabilitar as sugestões do {% data variables.product.prodname_copilot %} para a linguagem especificada, clique em **Desabilitar Preenchimentos para _LINGUAGEM_**. + ![Captura de tela da opção para desabilitar o {% data variables.product.prodname_copilot %} globalmente ou para a linguagem atual](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png) -## Further reading +## Leitura adicional -- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/) -- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) +- [O site do {% data variables.product.prodname_copilot %}](https://copilot.github.com/) +- [Sobre o {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides) diff --git a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md index bc783d3b490d..8489c2aea278 100644 --- a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md +++ b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md @@ -1,34 +1,39 @@ --- -title: Getting started with GitHub Copilot in Neovim +title: Introdução ao GitHub Copilot no Neovim shortTitle: Neovim product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.' +intro: 'Saiba como instalar o {% data variables.product.prodname_copilot %} no Neovim e passar a ver sugestões enquanto escreve comentários e códigos.' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 6296ff5b89e86b4b51cbb04bd9ac4ba91863a1ac +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185064' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Neovim +## Sobre o {% data variables.product.prodname_copilot %} e o Neovim {% data reusables.copilot.procedural-intro %} -If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. +Usando o Neovim, você pode ver e incorporar sugestões do {% data variables.product.prodname_copilot %} diretamente no editor. -## Prerequisites +## Pré-requisitos -- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." +- Para usar o {% data variables.product.prodname_copilot %}, é preciso ter uma assinatura ativa do {% data variables.product.prodname_copilot %}. Para ver mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)". -- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/). +- Para usar o {% data variables.product.prodname_copilot %} no Neovim, você precisa ter o Neovim e o Node.js versão 17 ou inferior instalados. Para obter mais informações, confira a [documentação do Neovim](https://neovim.io/doc/) e o [site do Node.js](https://nodejs.org/en/). -## Installing the Neovim extension +## Como instalar a extensão do Neovim {% mac %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal. + - Para instalar o {% data variables.product.prodname_copilot %} com o gerenciador de plug-in interno do Neovim, insira o seguinte comando no Terminal. git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -41,7 +46,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% windows %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash. + - Para instalar o {% data variables.product.prodname_copilot %} com o gerenciador de plug-in interno do Neovim, insira o seguinte comando no Git Bash. git clone https://github.com/github/copilot.vim.git ` $HOME/AppData/Local/nvim/pack/github/start/copilot.vim @@ -54,7 +59,7 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% linux %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command: + - Para instalar o {% data variables.product.prodname_copilot %} com o gerenciador de plug-in interno do Neovim, insira o seguinte comando: git clone https://github.com/github/copilot.vim \ ~/.config/nvim/pack/github/start/copilot.vim @@ -63,14 +68,14 @@ If you use a Neovim, you can view and incorporate suggestions from {% data varia {% endlinux %} -## Learning to use {% data variables.product.prodname_copilot %} in Neovim +## Aprendendo a usar o {% data variables.product.prodname_copilot %} no Neovim -For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command. +Para obter diretrizes sobre como usar o {% data variables.product.prodname_copilot %} no Neovim, exiba a documentação do plug-in. Para ver a documentação, abra o Neovim e execute o comando a seguir. ``` :help copilot ``` -## Further reading +## Leitura adicional - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md index 9894db0413d9..6ddb51d31178 100644 --- a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md +++ b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md @@ -1,105 +1,109 @@ --- -title: Getting started with GitHub Copilot in Visual Studio Code +title: Introdução ao GitHub Copilot no Visual Studio Code shortTitle: Visual Studio Code -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, and start seeing suggestions as you write comments and code.' +intro: 'Saiba como instalar o {% data variables.product.prodname_copilot %} no {% data variables.product.prodname_vscode %},e passar a ver sugestões enquanto escreve comentários e códigos.' product: '{% data reusables.gated-features.copilot %}' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 63c670a7cd5263057f79b7761a960854ecac2dd6 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185125' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %} +## Sobre o {% data variables.product.prodname_copilot %} e o {% data variables.product.prodname_vscode %} {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vscode %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vscode %} for macOS, Windows, or Linux. +Usando o {% data variables.product.prodname_vscode %}, você pode ver e incorporar sugestões do {% data variables.product.prodname_copilot %} diretamente no editor. Este guia demonstra como usar o {% data variables.product.prodname_copilot %} dentro do {% data variables.product.prodname_vscode %} para macOS, Windows ou Linux. -## Prerequisites +## Pré-requisitos -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %} download page](https://code.visualstudio.com/Download). +Para usar o {% data variables.product.prodname_copilot %} no {% data variables.product.prodname_vscode %}, o {% data variables.product.prodname_vscode %} precisa estar instalado. Para obter mais informações, confira a [página de download do {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/Download). -## Installing the {% data variables.product.prodname_vscode %} extension +## Como instalar a extensão {% data variables.product.prodname_vscode %} -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension. +Para usar o {% data variables.product.prodname_copilot %}, primeiro você precisa instalar a extensão {% data variables.product.prodname_vscode %}. -1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**. - ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) -1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**. -1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**. - ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png) -1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}. - - If you have previously authorized {% data variables.product.prodname_vscode %} for your account on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} will be automatically authorized. - ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png) -1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_vscode %}**. -1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialog box, to confirm the authentication, click **Open**. +1. No {% data variables.product.prodname_vscode %} Marketplace, acesse a página da [extensão {% data variables.product.prodname_copilot %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) e clique em **Instalar**. + ![Instalar a extensão {% data variables.product.prodname_vscode %} do {% data variables.product.prodname_copilot %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png) +1. Um pop-up será exibido, solicitando que você abra o {% data variables.product.prodname_vscode %}. Clique em **Abrir o {% data variables.product.prodname_vscode %}** . +1. Na guia "Extensão: {% data variables.product.prodname_copilot %}" no {% data variables.product.prodname_vscode %}, clique em **Instalar**. + ![Botão de instalação no {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png) +1. Se você ainda não tiver autorizado o {% data variables.product.prodname_vscode %} na conta do {% data variables.product.prodname_dotcom %}, será solicitado que você entre no {% data variables.product.prodname_dotcom %} no {% data variables.product.prodname_vscode %}. + - Se você já tiver autorizado o {% data variables.product.prodname_vscode %} para sua conta no {% data variables.product.prodname_dotcom %}, o {% data variables.product.prodname_copilot %} será autorizado automaticamente. + ![Captura da tela de autorização do {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/vsc-copilot-authorize.png) +1. No navegador, o {% data variables.product.prodname_dotcom %} solicitará as permissões necessárias para o {% data variables.product.prodname_copilot %}. Para aprovar essas permissões, clique em **Autorizar o {% data variables.product.prodname_vscode %}** . +1. No {% data variables.product.prodname_vscode %}, na caixa de diálogo "{% data variables.product.prodname_vscode %}", para confirmar a autenticação, clique em **Abrir**. -## Seeing your first suggestion +## Como ver a primeira sugestão {% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly. +{% data reusables.copilot.supported-languages %} Os exemplos a seguir estão em JavaScript, mas as outras linguagens funcionarão da mesma forma. {% data reusables.copilot.create-js-file %} -1. In the JavaScript 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. No arquivo JavaScript, digite o cabeçalho da função a seguir. O {% data variables.product.prodname_copilot %} vai sugerir automaticamente um corpo inteiro da função em texto esmaecido, como é mostrado abaixo. A sugestão exata pode variar. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` - ![Screenshot of a first suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) -{% data reusables.copilot.accept-suggestion %} + ![Captura de tela de uma primeira sugestão {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions +## Como ver sugestões alternativas {% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. No arquivo JavaScript, digite o cabeçalho da função a seguir. {% data variables.product.prodname_copilot %} mostrará uma sugestão. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` {% data reusables.copilot.see-alternative-suggestions %} - | OS | See next suggestion | See previous suggestion | + | Sistema operacional | Ver a próxima sugestão | Ver a sugestão anterior | | :- | :- | :- | - |macOS|Option (⌥) or Alt+]|Option (⌥) or Alt+[| + |macOS|Opção (⌥) ou Alt+]|Opção (⌥) ou Alt+[| |Windows|Alt+]|Alt+[| |Linux|Alt+]|Alt+[| -1. Alternatively, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions. +1. Como alternativa, você pode focalizar a sugestão para ver a paleta de comandos do {% data variables.product.prodname_copilot %} e escolher sugestões. {% data reusables.copilot.accept-or-reject-suggestion %} -## Seeing multiple suggestions in a new tab +## Como ver várias sugestões em uma nova guia {% data reusables.copilot.suggestions-new-tab %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion. +1. No arquivo JavaScript, digite o cabeçalho da função a seguir. {% data variables.product.prodname_copilot %} mostrará uma sugestão. ```javascript{:copy} function calculateDaysBetweenDates(begin, end) { ``` -1. To open a new tab with multiple additional options, press Ctrl+Enter. -1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab. +1. Para abrir uma nova guia com várias opções adicionais, pressione Ctrl+Enter. +1. Para aceitar uma sugestão, acima da sugestão, clique em **Aceitar Solução**. Para rejeitar todas as sugestões, feche a guia. -## Generating code suggestions from comments +## Como gerar sugestões de código por meio de comentários {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. No arquivo JavaScript, digite o comentário a seguir. O {% data variables.product.prodname_copilot %} vai sugerir uma implementação da função. ```javascript{:copy} // find all images without alternate text // and give them a red border function process() { ``` -## Using a framework +## Como usar uma estrutura -You can also use {% data variables.product.prodname_copilot %} to generate suggestions for APIs and frameworks. The following example uses {% data variables.product.prodname_copilot %} to create a simple Express server that returns the current time. +Você também pode usar o {% data variables.product.prodname_copilot %} para gerar sugestões de APIs e estruturas. O exemplo a seguir usa o {% data variables.product.prodname_copilot %} para criar um servidor Express simples que retorna a hora atual. {% data reusables.copilot.create-js-file %} -1. In the JavaScript file, type the following comment and then press Enter. {% data variables.product.prodname_copilot %} will suggest an implementation of the Express app. +1. No arquivo JavaScript, digite o comentário a seguir e pressione Enter. O {% data variables.product.prodname_copilot %} vai sugerir uma implementação do aplicativo Express. ```javascript{:copy} // Express server on port 3000 1. To accept each line, press Tab, then Enter. @@ -107,10 +111,10 @@ You can also use {% data variables.product.prodname_copilot %} to generate sugge ```javascript{:copy} // Return the current time ``` -1. To accept each line, press Tab. +1. Para aceitar cada linha, pressione Tab. {% data reusables.copilot.enabling-or-disabling-in-vsc %} -## Further reading +## Leitura adicional - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md index 618bbdb98aab..f183be5b2293 100644 --- a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md +++ b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md @@ -1,84 +1,86 @@ --- -title: Getting started with GitHub Copilot in Visual Studio +title: Introdução ao GitHub Copilot no Visual Studio shortTitle: Visual Studio product: '{% data reusables.gated-features.copilot %}' -intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, and start seeing suggestions as you write comments and code.' +intro: 'Saiba como instalar o {% data variables.product.prodname_copilot %} no {% data variables.product.prodname_vs %},e passar a ver sugestões enquanto escreve comentários e códigos.' versions: feature: copilot topics: - Copilot +ms.openlocfilehash: 353095b0b0490cd12da8d853754b524431605819 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148185121' --- - {% data reusables.copilot.copilot-cta-button %} -## About {% data variables.product.prodname_copilot %} and Visual Studio +## Sobre o {% data variables.product.prodname_copilot %} e o Visual Studio {% data reusables.copilot.procedural-intro %} -If you use {% data variables.product.prodname_vs %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vs %} for Windows. +Usando o {% data variables.product.prodname_vs %}, você pode ver e incorporar sugestões do {% data variables.product.prodname_copilot %} diretamente no editor. Este guia demonstra como usar o {% data variables.product.prodname_copilot %} dentro do {% data variables.product.prodname_vs %} para Windows. -## Prerequisites +## Pré-requisitos -To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have {% data variables.product.prodname_vs %} 2022 17.2 or later installed. For more information, see the [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) documentation. +Para usar o {% data variables.product.prodname_copilot %} no {% data variables.product.prodname_vs %}, você deverá ter o {% data variables.product.prodname_vs %} 2022 17.2 ou posterior instalado. Para obter mais informações, confira a documentação do [IDE do Visual Studio](https://visualstudio.microsoft.com/vs/). {% note %} -**Note**: {% data variables.product.prodname_copilot %} is not currently available for use with Visual Studio for Mac. +**Observação**: o {% data variables.product.prodname_copilot %} não está disponível no momento para uso com Visual Studio para Mac. {% endnote %} -## Installing the {% data variables.product.prodname_vs %} extension +## Como instalar a extensão {% data variables.product.prodname_vs %} -To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension. -1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**. - ![Screenshot of the Visual Studio toolbar](/assets/images/help/copilot/visual-studio-toolbar.png) -1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**. - ![Screenshot of GitHub Copilot extension for Visual Studio with the download button emphasized](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) -1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}. -1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information. - ![Screenshot of installed extensions in Visual Studio with GitHub Copilot emphasized](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) -1. Open or create a new project in {% data variables.product.prodname_vs %}. -1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**. - ![Screenshot of the Microsoft {% data variables.product.prodname_vs %} dialogue box](/assets/images/help/copilot/vs-auth-dialogue.png) -1. A device activation window will open in your browser. Paste the device code, then click **Continue**. +Para usar o {% data variables.product.prodname_copilot %}, você primeiro deve instalar a extensão {% data variables.product.prodname_vs %}. +1. Na barra de ferramentas do Visual Studio, clique em **Extensões** e em **Gerenciar Extensões**. + ![Captura de tela da barra de ferramentas do Visual Studio](/assets/images/help/copilot/visual-studio-toolbar.png) +1. Na janela "Gerenciar Extensões", clique no **Visual Studio Marketplace**, pesquise a extensão do {% data variables.product.prodname_copilot %} e clique em **Baixar**. + ![Captura de tela da extensão do GitHub Copilot para Visual Studio com o botão de download enfatizado](/assets/images/help/copilot/install-copilot-extension-visual-studio.png) +1. Feche a janela "Gerenciar Extensões", saia e inicie {% data variables.product.prodname_vs %}. +1. Opcionalmente, para verificar se o {% data variables.product.prodname_copilot %} está instalado e habilitado, volte para **Gerenciar Extensões**, clique em **Instalado** para exibir suas extensões instaladas no momento e clique em **{% data variables.product.prodname_copilot %}** para ver informações de status. + ![Captura de tela das extensões instaladas no Visual Studio com o GitHub Copilot destacado](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png) +1. Abra ou crie um novo projeto no {% data variables.product.prodname_vs %}. +1. Na caixa de diálogo "Microsoft {% data variables.product.prodname_vs %}", para copiar o código de ativação do dispositivo, clique em **OK**. + ![Captura de tela da caixa de diálogo Microsoft {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-auth-dialogue.png) +1. Uma janela de ativação do dispositivo será aberta no navegador. Cole o código do dispositivo e clique em **Continuar**. - - To paste the code in Windows or Linux, press Ctrl+v. - - To paste the code in macOS, press command+v. -1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**. -1. After you approve the permissions, {% data variables.product.prodname_vs %} will show a confirmation. - ![Screenshot of {% data variables.product.prodname_vs %} permissions confirmation](/assets/images/help/copilot/vs-confirmation.png) + - Para colar o código no Windows ou Linux, pressione Ctrl+v. + - Pra colar o código no macOS, pressione comando+v. +1. O {% data variables.product.prodname_dotcom %} solicitará as permissões necessárias para o {% data variables.product.prodname_copilot %}. Para aprovar essas permissões, clique em **Autorizar o plugin do {% data variables.product.prodname_copilot %}** . +1. Depois de aprovar as permissões, o {% data variables.product.prodname_vs %} mostrará uma confirmação. + ![Captura de tela da confirmação de permissões do {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-confirmation.png) -## Seeing your first suggestion +## Como ver a primeira sugestão -{% data reusables.copilot.code-examples-limitations %} -{% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly. +{% data reusables.copilot.code-examples-limitations %} {% data reusables.copilot.supported-languages %} Os exemplos a seguir estão em C#, mas as outras linguagens funcionarão da mesma forma. {% data reusables.copilot.create-c-file %} -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. +1. No arquivo #C, digite a seguinte assinatura de função. O {% data variables.product.prodname_copilot %} sugerirá automaticamente um corpo inteiro da função em texto esmaecido, como é mostrado abaixo. A sugestão exata pode variar. ```csharp{:copy} int CalculateDaysBetweenDates( ``` - ![Screenshot of a first suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) -{% data reusables.copilot.accept-suggestion %} + ![Captura de tela de uma primeira sugestão do Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png) {% data reusables.copilot.accept-suggestion %} -## Seeing alternative suggestions -{% data reusables.copilot.alternative-suggestions %} -{% data reusables.copilot.create-c-file %} -1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion. +## Como ver sugestões alternativas +{% data reusables.copilot.alternative-suggestions %} {% data reusables.copilot.create-c-file %} +1. No arquivo #C, digite a seguinte assinatura de função. {% data variables.product.prodname_copilot %} will show you a suggestion. ```csharp{:copy} 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. +1. Se sugestões alternativas estiverem disponíveis, você poderá ver essas alternativas pressionando Alt+] (ou Alt+[). +1. Como opção, você pode focalizar a sugestão para ver a paleta de comandos do {% data variables.product.prodname_copilot %} e escolher sugestões. {% data reusables.copilot.accept-or-reject-suggestion %} -## Generating code suggestions from comments +## Gerar sugestões de código por meio de comentários {% data reusables.copilot.generating-suggestions-from-comments %} {% data reusables.copilot.create-c-file %} -1. In the C# file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function. +1. No arquivo C#, digite o comentário a seguir. O {% data variables.product.prodname_copilot %} sugerirá uma implementação da função. ```csharp{:copy} using System.Xml.Linq; @@ -91,6 +93,6 @@ To use {% data variables.product.prodname_copilot %}, you must first install the {% data reusables.copilot.enabling-or-disabling-vs %} -## Further reading +## Leitura adicional - [{% data variables.product.prodname_copilot %}](https://copilot.github.com/) diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..356a40eaa258 --- /dev/null +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: Alterar a URL remota de um repositório do GitHub Desktop +intro: 'É possível alterar a URL remota do repositório com o qual você estiver trabalhando via {% data variables.product.prodname_desktop %}. Você pode fazer isso em caso de alteração do nome do repositório, do nome do usuário ou do nome da organização proprietária do repositório.' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188349' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. Clique em **Remoto** e, em **Repositório remoto primário**, digite a URL desejada. +![Campo de repositório remoto primário](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. Clique em **Remoto** e, em **Repositório remoto primário**, digite a URL desejada. +![Campo de repositório remoto primário](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index e7799a0315b2..8b0e326c35e4 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095167' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188350' --- diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index a8675ae46fa8..be807a1d0887 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -6,12 +6,12 @@ intro: 'Você pode usar os {% data variables.product.prodname_github_codespaces versions: fpt: '*' 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 %}' -ms.openlocfilehash: 6794d20b9ea0153b3baf4bee1a08c68b2ba17456 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 832ab470d13cc741bc4a71e77840c99da5ff3de6 +ms.sourcegitcommit: a35d85531445980b5f04d3fc70180a29dad37f89 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158874' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148189910' --- ## Sobre os {% data variables.product.prodname_github_codespaces %} @@ -103,4 +103,4 @@ Os professores podem exibir o codespace de uma tarefa de cada aluno na página d ![Visão geral da tarefa para o professor com os codespaces do aluno](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -Quando você se conecta a um codespace por meio de um navegador, o salvamento automático é habilitado automaticamente. Se você quiser salvar as alterações no repositório, precisará fazer commit das alterações e efetuar push delas em um branch remoto. Se você deixar o codespace em execução sem interação por 30 minutos por padrão, o codespace atingirá o tempo limite e interromperá a execução. Seus dados serão preservados da última vez que você fez uma alteração. Para obter mais informações sobre o ciclo de vida de um codespace, confira "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle)". +Quando você se conecta a um codespace por meio de um navegador, o salvamento automático é habilitado automaticamente. Se você quiser salvar as alterações no repositório, precisará fazer commit das alterações e efetuar push delas em um branch remoto. Se você deixar o codespace em execução sem interação por 30 minutos por padrão, o codespace atingirá o tempo limite e interromperá a execução. Seus dados serão preservados da última vez que você fez uma alteração. Para obter mais informações sobre o ciclo de vida de um codespace, confira "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle)". diff --git a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md index 02079374815c..883768e116e8 100644 --- a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -4,12 +4,12 @@ intro: 'Aprenda a usar a API do GraphQL de {% data variables.product.prodname_di versions: feature: discussions shortTitle: Use GraphQL for Discussions -ms.openlocfilehash: 1512082737df4c92942a40007d2c75897edb1061 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: fd296c4e9390cac3500ba7319cb602366a37e262 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147408840' +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185611' --- A API do GraphQL do {% data variables.product.prodname_discussions %} permite que você obtenha, crie, edite e exclua publicações de discussão. Para obter mais informações sobre as {% data variables.product.prodname_discussions %}, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". @@ -72,7 +72,7 @@ enum DiscussionOrderField { ### Repository.discussionCategories -Retorna as categorias de discussão disponíveis definidas neste repositório. Cada repositório pode ter até 10 categorias. Para obter mais informações sobre as categorias de discussões, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". +Retorna as categorias de discussão disponíveis definidas neste repositório. Cada repositório pode ter até 25 categorias. Para obter mais informações sobre as categorias de discussões, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". _Assinatura:_ diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md b/translations/pt-BR/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md index 47b0e6775539..4ebb2eff4f36 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md @@ -9,12 +9,12 @@ topics: - GitHub Apps - OAuth Apps shortTitle: Limit app access requests -ms.openlocfilehash: 4ea1bd133dcbabb9e7b3e3cbe65da5ff9c6eabac -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 6c991ecfbdac75f1bb3bb4fdb5ea3a0692f1d040 +ms.sourcegitcommit: 30b0931723b704e219c736e0de7afe0fa799da29 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148007640' +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148186432' --- ## Sobre as solicitações de acesso de integração @@ -22,7 +22,7 @@ Quando as solicitações de acesso de integração estão habilitadas, colaborad Por padrão, as solicitações de acesso de integração estão habilitadas. Se a organização tem um grande número de colaboradores externos, convém desabilitar as solicitações de acesso de integração para reduzir o número de solicitações que você precisa revisar. -## Habilitar ou desabilitar solicitações de acesso de integração +## Habilitando ou desabilitando solicitações de acesso de integração {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.profile.org_member_privileges %} 1. Em "Solicitações de acesso de integração", marque ou desmarque **Permitir solicitações de integração de colaboradores externos** e clique em **Salvar**. diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..7bd5ce39b047 --- /dev/null +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: Configurar um repositório remoto para um fork +intro: 'Você deve configurar um remoto que aponta para o repositório upstream no Git para [sincronizar alterações realizadas em um fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) com o repositório original. Isso também permite sincronizar alterações feitas no repositório original com a bifurcação.' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188354' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. Liste o repositório remote configurado no momento para sua bifurcação. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. Especifique um novo repositório *upstream* remoto que será sincronizado com a bifurcação. + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. Verifique o novo repositório upstream especificado para a bifurcação. + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 998d626542c9..5350180a2f70 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146683658' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188353' --- diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..e4925ec7e717 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: Sincronizar uma bifurcação +intro: Sincronize uma bifurcação de um repositório para mantê-la atualizada com o repositório upstream. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188325' --- - -## Syncing a fork branch from the web UI +## Sincronizar um branch de fork usando a interface do usuário da Web {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream. +2. Selecione a lista suspensa **Sincronizar fork**. + ![Menu suspenso "Sincronizar fork" enfatizado](/assets/images/help/repository/sync-fork-dropdown.png) +3. Revise os detalhes sobre os commits do repositório upstream e clique em **Atualizar branch**. + ![Sincronizar o modal do fork com o botão "Atualizar branch" enfatizado](/assets/images/help/repository/update-branch-button.png) {% else %} +1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream. +2. Selecione o menu suspenso **Buscar upstream**. + ![Menu suspenso "Buscar upstream"](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. Revise os detalhes sobre os commits do repositório upstream e clique em **Buscar e mesclar**. + ![Botão "Buscar e mesclar"](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +Se as alterações do repositório a upstream gerarem conflitos, {% data variables.product.company_short %} solicitará a criação de um pull request para resolver os conflitos. -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## Sincronizar um branch de fork com a {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} Para saber mais sobre a {% data variables.product.prodname_cli %}, confira "[Sobre a {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +Para atualizar o fork remoto por meio do próprio pai, use o subcomando `gh repo sync -b BRANCHNAME` e forneça o nome do fork como argumento. ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +Se as alterações do repositório upstream causarem conflito, a s {% data variables.product.prodname_cli %} não poderá sincronizá-las. Defina o sinalizador `-force` para substituir o branch de destino. -## Syncing a fork branch from the command line +## Sincronizar um branch de fork usando a linha de comando -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +Para sincronizar o fork com um repositório upstream, você precisa configurar um controle remoto que aponte para o repositório upstream no Git. Para obter mais informações, confira "[Como configurar um repositório remoto para um fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)". {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. Altere o diretório de trabalho atual para seu projeto local. +3. Obtenha os branches e os respectivos commits do repositório upstream. Os commits em `BRANCHNAME` serão armazenados no branch `upstream/BRANCHNAME` local. ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. Faça check-out do branch padrão local do fork, neste caso, usamos o `main`. ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. Mescle as alterações do branch padrão upstream, neste caso, `upstream/main`, no branch padrão local. Isso coloca o branch padrão da bifurcação em sincronia com o repositório upstream, sem perder as alterações locais. ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + Se o branch local não tiver commits exclusivos, o Git executará um avanço. Para obter mais informações, confira [Conceitos básicos de branch e mesclagem](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) na documentação do Git. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + Se o branch local tiver commits exclusivos, poderá ser necessário resolver conflitos. Para obter mais informações, confira "[Como resolver conflitos de mesclagem](/github/collaborating-with-pull-requests/addressing-merge-conflicts)". {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**Dica**: a sincronização do fork atualiza apenas a cópia local do repositório. Para atualizar o fork no {% data variables.location.product_location %}, você precisa [efetuar push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). {% endtip %} diff --git a/translations/pt-BR/content/rest/overview/api-versions.md b/translations/pt-BR/content/rest/overview/api-versions.md new file mode 100644 index 000000000000..99da80b734d4 --- /dev/null +++ b/translations/pt-BR/content/rest/overview/api-versions.md @@ -0,0 +1,54 @@ +--- +title: Versões da API +shortTitle: API Versions +intro: Especifique qual versão da API REST usar sempre que fizer uma solicitação à API REST. +versions: + feature: api-date-versioning +ms.openlocfilehash: c1209120fab4c4cc26962991ad48b76638627db5 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184383' +--- +## Sobre o controle de versão da API + +{% data reusables.rest-api.about-api-versions %} + +{% ifversion ghes %} + +## Sobre o controle de versão do {% data variables.product.prodname_ghe_server %} e o controle de versão da API REST + +As versões do {% data variables.product.prodname_ghe_server %} são dissociadas das versões da API REST. Você pode atualizar sua versão do {% data variables.product.prodname_ghe_server %}, mas manter a mesma versão da API REST, desde que a versão da API seja incluída na versão do {% data variables.product.prodname_ghe_server %}. Da mesma forma, você pode atualizar sua versão da API REST sem atualizar sua versão do {% data variables.product.prodname_ghe_server %}, desde que a nova versão da API REST escolhida esteja disponível para sua versão do {% data variables.product.prodname_ghe_server %}. + +As notas sobre a versão do {% data variables.product.prodname_ghe_server %} serão declaradas quando uma versão da API REST não tiver mais suporte. Para obter mais informações, confira as "[Notas sobre a versão](/admin/release-notes)". + +{% endif %} + +## Especificando uma versão da API + +Você deve usar o cabeçalho `X-GitHub-Api-Version` para especificar uma versão da API. Por exemplo: + +```shell +$ curl {% data reusables.rest-api.version-header %} https://api.github.com/zen +``` + +As solicitações sem o cabeçalho `X-GitHub-Api-Version` usarão a versão `{{ initialRestVersioningReleaseDate }}` padrão. + +Se você especificar uma versão da API que não tem mais suporte, receberá um erro `400`. + +## Atualizando para o nova versão da API + +Antes de atualizar para uma nova versão da API REST, leia o log de alterações de alterações interruptivas da nova versão da API para entender quais alterações interruptivas estão incluídas e saber mais sobre como atualizar para essa versão específica da API. Para saber mais, confira "[Alteração interruptiva](/rest/overview/breaking-changes)". + +Ao atualizar sua integração para especificar a nova versão da API no cabeçalho `X-GitHub-Api-Version`, você também precisará fazer as alterações necessárias para que sua integração funcione com a nova versão da API. + +Após a atualização da integração, teste sua integração para verificar se ela funciona com a nova versão da API. + +## Versões de API com suporte + +No momento, há suporte para as seguintes versões da API REST: + +{% for apiVersion in allVersions[currentVersion].apiVersions %} {{ apiVersion }} {% endfor %} + +Você também pode fazer com que uma solicitação de API obtenha todas as versões de API com suporte. Para saber mais, confira "[Obter todas as versões da API](/rest/meta#get-all-api-versions)." diff --git a/translations/pt-BR/content/rest/overview/breaking-changes.md b/translations/pt-BR/content/rest/overview/breaking-changes.md new file mode 100644 index 000000000000..a45146d1399e --- /dev/null +++ b/translations/pt-BR/content/rest/overview/breaking-changes.md @@ -0,0 +1,30 @@ +--- +title: Alterações de quebra +shortTitle: Breaking changes +intro: Saiba mais sobre as alterações interruptivas introduzidas em cada versão da API REST. +versions: + feature: api-date-versioning +ms.openlocfilehash: 674345b82c5da9b0804fe4a0f62450ff4fbbc3e9 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: '148184384' +--- +## Sobre alterações interruptivas na API REST + +{% data reusables.rest-api.about-api-versions %} + +Para obter mais informações sobre as versões da API, confira "[Versões de API](/rest/overview/api-versions)". + +## Atualizando para o nova versão da API + +Antes de atualizar para uma nova versão da API REST, leia a seção nesta página que corresponde à nova versão da API para entender quais alterações interruptivas estão incluídas e saber mais sobre como atualizar para essa versão da API. + +Ao atualizar sua integração para especificar a nova versão da API no cabeçalho `X-GitHub-Api-Version`, você também precisará fazer as alterações necessárias para que sua integração funcione com a nova versão da API. + +Após a atualização da integração, teste sua integração para verificar se ela funciona com a nova versão da API. + +## Alterações interruptivas para {{ initialRestVersioningReleaseDate }} + +A versão `{{ initialRestVersioningReleaseDate }}` é a primeira versão da API REST do {% data variables.product.product_name %} após a introdução do controle de versão baseado em data. Esta versão não inclui nenhuma alteração interruptiva. diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 64346380cc58..2ab6e9bab49b 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -11,12 +11,12 @@ versions: miniTocMaxHeadingLevel: 3 topics: - API -ms.openlocfilehash: dc16916ada20275d41f23a8bc006cc79ddf51120 -ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.openlocfilehash: 4fd3e2aad72ee0ffc4778a86dc99cd5bb6f9d2c5 +ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148184266' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190396' --- {% ifversion api-date-versioning %} ## Versão da API @@ -264,10 +264,10 @@ Em seguida, você pode expandir esses modelos usando algo como ogem [uri_templat >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/pt-BR/data/reusables/apps/reauthorize-apps-saml.md b/translations/pt-BR/data/reusables/apps/reauthorize-apps-saml.md new file mode 100644 index 000000000000..39dc4431d87a --- /dev/null +++ b/translations/pt-BR/data/reusables/apps/reauthorize-apps-saml.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: a95067136ba91760fb48dae77a42cf9b9377dbeb +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184034" +--- +Depois de habilitar o SSO do SAML, as autorizações de {% data variables.product.prodname_oauth_app %} e {% data variables.product.prodname_github_app %} poderão precisar ser revogadas e reautorizadas para acessar a organização. Para obter mais informações, confira "[Autorização do {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps#oauth-apps-and-organizations)". diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md index 0b39c0aba578..7fef7d4ca78c 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md @@ -1,192 +1,116 @@ -| Category name | Description +--- +ms.openlocfilehash: 1dd9305ca2b7cb3e8d25d697de8ae3a83e0c46bb +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148183977" +--- +| Nome da categoria | Descrição |------------------|------------------- -{%- ifversion fpt or ghec %} -| `account` | Contains activities related to an organization account. -| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -{%- endif %} -| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. -{%- ifversion audit-log-streaming %} -| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. -{%- endif %} -{%- ifversion fpt or ghec %} -| `billing` | Contains activities related to an organization's billing. -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `business` | Contains activities related to business settings for an enterprise. -{%- endif %} -{%- ifversion code-security-audit-log-events %} -| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise. -{%- endif %} -{%- ifversion code-security-audit-log-events %} -| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." -{%- endif %} -| `checks` | Contains activities related to check suites and runs. -{%- ifversion fpt or ghec %} -| `codespaces` | Contains activities related to an organization's codespaces. -{%- endif %} -| `commit_comment` | Contains activities related to updating or deleting commit comments. -{%- ifversion ghes %} -| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. -{%- endif %} -| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." -| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. -| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. -{%- ifversion fpt or ghec or ghes %} -| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." -| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. -{%- endif %} -| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. -{%- ifversion fpt or ghec %} -| `discussion` | Contains activities related to team discussions. -| `discussion_comment` | Contains activities related to comments posted in discussions on a team page. -| `discussion_post` | Contains activities related to discussions posted to a team page. -| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page. -{%- endif %} -{%- ifversion ghec or ghes %} -| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. -| `enterprise` | Contains activities related to enterprise settings. -{%- endif %} -{%- ifversion ghec %} -| `enterprise_domain` | Contains activities related to verified enterprise domains. -| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection. -{%- endif %} -{%- ifversion fpt or ghec %} -| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments. -{%- endif %} -{%- ifversion ghae %} -| `external_group` | Contains activities related to Okta groups. -| `external_identity` | Contains activities related to a user in an Okta group. -{%- endif %} -| `gist` | Contains activities related to Gists. -| `hook` | Contains activities related to webhooks. -| `integration` | Contains activities related to integrations in an account. -| `integration_installation` | Contains activities related to integrations installed in an account. -| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization. -{%- ifversion ghec or ghae %} -| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization. -| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. -{%- endif %} -| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository. -| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. -| `issues` | Contains activities related to enabling or disabling issue creation for an organization. -{%- ifversion fpt or ghec %} -| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}. -{%- endif %} -| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." -| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. -| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization. -{%- ifversion ghec or ghes or ghae %} -| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. -{%- endif %} -{%- ifversion fpt or ghec %} -| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. -| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. -{%- endif %} -| `oauth_access` | Contains activities related to OAuth access tokens. -| `oauth_application` | Contains activities related to OAuth Apps. -{%- ifversion fpt or ghec %} -| `oauth_authorization` | Contains activities related to authorizing OAuth Apps. -{%- endif %} -| `org` | Contains activities related to organization membership. -{%- ifversion ghec or ghes or ghae %} -| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." -| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -{%- endif %} -| `organization_default_label` | Contains activities related to default labels for repositories in an organization. -{%- ifversion fpt or ghec or ghes %} -| `organization_domain` | Contains activities related to verified organization domains. -| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise. -{%- endif %} -{%- ifversion fpt or ghec %} -| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. -| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. -| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}. -{%- endif %} -{%- ifversion ghes %} -| `pre_receive_environment` | Contains activities related to pre-receive hook environments. -| `pre_receive_hook` | Contains activities related to pre-receive hooks. -{%- endif %} -{%- ifversion ghes %} -| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise. -{%- endif %} -| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise. -{%- ifversion fpt or ghec %} -| `profile_picture` | Contains activities related to an organization's profile picture. -{%- endif %} -| `project` | Contains activities related to project boards. -| `project_field` | Contains activities related to field creation and deletion in a project board. -| `project_view` | Contains activities related to view creation and deletion in a project board. -| `protected_branch` | Contains activities related to protected branches. -| `public_key` | Contains activities related to SSH keys and deploy keys. -| `pull_request` | Contains activities related to pull requests. -| `pull_request_review` | Contains activities related to pull request reviews. -| `pull_request_review_comment` | Contains activities related to pull request review comments. -| `repo` | Contains activities related to the repositories owned by an organization. -{%- ifversion fpt or ghec %} -| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). -| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." -{%- endif %} -| `repository_image` | Contains activities related to images for a repository. -| `repository_invitation` | Contains activities related to invitations to join a repository. -| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization. -{%- ifversion ghec or ghes or ghae %} -| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -{%- endif %} -{%- ifversion secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} -| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -{%- endif %} -{%- ifversion fpt or ghec %} -| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. -{%- endif %} -| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). -{%- ifversion fpt or ghec %} -| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. -| `required_status_check` | Contains activities related to required status checks for protected branches. -{%- endif %} -{%- ifversion ghec or ghes %} -| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. -{%- endif %} -{%- ifversion custom-repository-roles %} -| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." -| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `security_key` | Contains activities related to security keys registration and removal. -{%- endif %} -{%- ifversion fpt or ghec %} -| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"). -{%- endif %} -{%- ifversion ghec or ghes or ghae %} -| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. -| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources. -{%- endif %}{% ifversion sso-redirect %} -| `sso_redirect` | Contains activities related to automatically redirecting users to sign in (see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)").{% endif %} -| `staff` | Contains activities related to a site admin performing an action. -| `team` | Contains activities related to teams in an organization. -| `team_discussions` | Contains activities related to managing team discussions for an organization. -{%- ifversion ghec %} -| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization. -{%- endif %} -{%- ifversion fpt or ghes %} -| `two_factor_authentication` | Contains activities related to two-factor authentication. -{%- endif %} -| `user` | Contains activities related to users in an enterprise or organization. -{%- ifversion ghec or ghes %} -| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise. -{%- endif %} -| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows. +{%- ifversion fpt or ghec %} | `account` | Contém atividades relacionadas a uma conta da organização. +| `advisory_credit` | Contém atividades relacionadas ao crédito de um colaborador de uma consultoria de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Sobre os avisos de segurança do {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +{%- endif %} | `artifact` | Contém atividades relacionadas aos artefatos de execução de fluxo de trabalho do {% data variables.product.prodname_actions %}. +{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Contém atividades relacionadas aos logs de auditoria de streaming para organizações em uma conta corporativa. +{%- endif %} {%- ifversion fpt or ghec %} | `billing` | Contém atividades relacionadas à cobrança de uma organização. +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Contém atividades relacionadas às configurações corporativas de uma empresa. +{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | Contém as atividades relacionadas ao {% data variables.product.prodname_GH_advanced_security %} em uma empresa. Para obter mais informações, confira "[Como gerenciar os recursos do {% data variables.product.prodname_GH_advanced_security %} na empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)". +| `business_secret_scanning` | Contém as atividades relacionadas a {% data variables.product.prodname_secret_scanning %} em uma empresa. Para obter mais informações, confira "[Como gerenciar os recursos do {% data variables.product.prodname_GH_advanced_security %} na empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)". +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Contém atividades relacionadas aos padrões de {% data variables.product.prodname_secret_scanning %} em uma empresa. +{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | Contém as atividades relacionadas ao recurso de proteção contra push do {% data variables.product.prodname_secret_scanning %} em uma empresa. Para obter mais informações, confira "[Como gerenciar os recursos do {% data variables.product.prodname_GH_advanced_security %} na empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)". +| `business_secret_scanning_push_protection_custom_message` | Contém as atividades relacionadas à mensagem personalizada exibida quando a proteção contra push é disparada em uma empresa. Para obter mais informações, confira "[Como gerenciar os recursos do {% data variables.product.prodname_GH_advanced_security %} na empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)". +{%- endif %} | `checks` | Contém atividades relacionadas aos pacotes de verificação e às execuções. +{%- ifversion fpt or ghec %} | `codespaces` | Contém atividades relacionadas aos codespaces de uma organização. +{%- endif %} | `commit_comment` | Contém atividades relacionadas à atualização ou à exclusão de comentários de commit. +{%- ifversion ghes %} | `config_entry` | Contém atividades relacionadas a definições de configuração. Esses eventos só ficam visíveis no log de auditoria do administrador do site. +{%- endif %} | `dependabot_alerts` | Contém as atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_alerts %} em repositórios existentes. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)". +| `dependabot_alerts_new_repos` | Contém atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_alerts %} em novos repositórios criados na organização. +| `dependabot_repository_access` | Contém atividades relacionadas aos repositórios privados de uma organização que o {% data variables.product.prodname_dependabot %} tem permissão para acessar. +{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates` | Contém as atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_security_updates %} nos repositórios existentes. Para obter mais informações, confira "[Como configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". +| `dependabot_security_updates_new_repos` | Contém atividades de configuração de nível da organização nas {% data variables.product.prodname_dependabot_security_updates %} para os repositórios criados na organização. +{%- endif %} | `dependency_graph` | Contém atividades de configuração no nível da organização dos grafos de dependências nos repositórios. Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +| `dependency_graph_new_repos` | Contém atividades de configuração no nível da organização para novos repositórios criados na organização. +{%- ifversion fpt or ghec %} | `discussion` | Contém atividades relacionadas às discussões da equipe. +| `discussion_comment` | Contém atividades relacionadas aos comentários postados em discussões em uma página da equipe. +| `discussion_post` | Contém atividades relacionadas às discussões postadas em uma página da equipe. +| `discussion_post_reply` | Contém atividades relacionadas às respostas de discussões postadas em uma página da equipe. +{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Contém atividades relacionadas ao {% data variables.product.prodname_github_connect %}. +| `enterprise` | Contém atividades relacionadas às configurações da empresa. +{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Contém atividades relacionadas aos domínios corporativos verificados. +| `enterprise_installation` | Contém atividades relacionadas aos {% data variables.product.prodname_github_app %}s associados a uma conexão corporativa do {% data variables.product.prodname_github_connect %}. +{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Contém atividades relacionadas a ambientes do {% data variables.product.prodname_actions %}. +{%- endif %} {%- ifversion ghae %} | `external_group` | Contém atividades relacionadas aos grupos do Okta. +| `external_identity` | Contém atividades relacionadas a um usuário em um grupo do Okta. +{%- endif %} | `gist` | Contém atividades relacionadas ao Gists. +| `hook` | Contém atividades relacionadas a webhooks. +| `integration` | Contém atividades relacionadas às integrações de uma conta. +| `integration_installation` | Contém atividades relacionadas às integrações instaladas em uma conta. +| `integration_installation_request` | Contém atividades relacionadas às solicitações de membros da organização para proprietários aprovarem integrações para uso na organização. +{%- ifversion ghec or ghae %} | `ip_allow_list` | Contém atividades relacionadas à habilitação ou à desabilitação da lista de permissões de IP para uma organização. +| `ip_allow_list_entry` | Contém atividades relacionadas à criação, à exclusão e à edição de uma entrada na lista de permissões de IP para uma organização. +{%- endif %} | `issue` | Contém atividades relacionadas à fixação, à transferência ou à exclusão de um problema em um repositório. +| `issue_comment` | Contém atividades relacionadas à fixação, à transferência ou à exclusão de comentários em um problema. +| `issues` | Contém atividades relacionadas à habilitação ou à desabilitação da criação de problemas para uma organização. +{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Contém atividades relacionadas à assinatura do Contrato de Desenvolvedor do {% data variables.product.prodname_marketplace %}. +| `marketplace_listing` | Contém atividades relacionadas aos aplicativos de listagem do {% data variables.product.prodname_marketplace %}. +{%- endif %} | `members_can_create_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites do {% data variables.product.prodname_pages %} para repositórios na organização. Para obter mais informações, confira "[Como gerenciar a publicação de sites do {% data variables.product.prodname_pages %} para sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". +| `members_can_create_private_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites privados do {% data variables.product.prodname_pages %} para repositórios na organização. +| `members_can_create_public_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites públicos do {% data variables.product.prodname_pages %} para repositórios na organização. +{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Contém atividades relacionadas à habilitação ou à desabilitação da criação de repositórios para uma organização. +{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Contém atividades de configuração no nível da organização que permitem que os membros da organização vejam insights de dependência. +| `migration` | Contém atividades relacionadas à transferência de dados de um local de *origem* (como uma organização do {% data variables.product.prodname_dotcom_the_website %} ou uma instância do {% data variables.product.prodname_ghe_server %}) para uma instância de *destino* do {% data variables.product.prodname_ghe_server %}. +{%- endif %} | `oauth_access` | Contém atividades relacionadas aos tokens de acesso OAuth. +| `oauth_application` | Contém atividades relacionadas aos Aplicativos OAuth. +{%- ifversion fpt or ghec %} | `oauth_authorization` | Contém atividades relacionadas à autorização de Aplicativos OAuth. +{%- endif %} | `org` | Contém atividades relacionadas à associação a uma organização. +{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Contém atividades relacionadas à autorização de credenciais para uso com o logon único do SAML. +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Contém atividades relacionadas aos padrões personalizados para a verificação de segredos em uma organização. Para obter mais informações, confira "[Como definir padrões personalizados para a verificação de segredos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". +| `org.secret_scanning_push_protection` | Contém atividades relacionadas aos padrões personalizados de verificação de segredos em uma organização. Para obter mais informações, confira "[Como proteger os pushes com a verificação de segredos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". +{%- endif %} | `organization_default_label` | Contém atividades relacionadas aos rótulos padrão em uma organização. +{%- ifversion fpt or ghec or ghes %} | `organization_domain` |Contém atividades relacionadas aos domínios da organização verificados. +| `organization_projects_change` | Contém atividades relacionadas aos quadros de projetos de toda a organização em uma empresa. +{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Contém atividades relacionadas aos domínios personalizados verificados do {% data variables.product.prodname_pages %}. +| `payment_method` | Contém atividades relacionadas à forma de pagamento do {% data variables.product.prodname_dotcom %} de uma organização. +| `prebuild_configuration` | Contém atividades relacionadas às configurações de pré-build do {% data variables.product.prodname_github_codespaces %}. +{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | Contém atividades relacionadas aos ambientes de gancho de pré-recebimento. +| `pre_receive_hook` | Contém atividades relacionadas aos ganchos de pré-recebimento. +{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Contém atividades relacionadas à habilitação do modo privado para uma empresa. +{%- endif %} | `private_repository_forking` | Contém atividades relacionadas à permissão de forks de repositórios privados e internos para um repositório, uma organização ou uma empresa. +{%- ifversion fpt or ghec %} | `profile_picture` | Contém atividades relacionadas à imagem de perfil de uma organização. +{%- endif %} | `project` | Contém atividades relacionadas aos quadros de projetos. +| `project_field` | Contém atividades relacionadas à criação e à exclusão de campos em um quadro de projetos. +| `project_view` | Contém atividades relacionadas à criação e à exclusão de exibições em um quadro de projetos. +| `protected_branch` | Contém atividades relacionadas aos branches protegidos. +| `public_key` | Contém atividades relacionadas às chaves SSH e às chaves de implantação. +| `pull_request` | Contém atividades relacionadas às solicitação de pull. +| `pull_request_review` | Contém atividades relacionadas às revisões de solicitação de pull. +| `pull_request_review_comment` | Contém atividades relacionadas aos comentários de revisão de solicitação de pull. +| `repo` | Contém atividades relacionadas aos repositórios pertencentes a uma organização. +{%- ifversion fpt or ghec %} | `repository_advisory` | Contém atividades de nível do repositório relacionadas às consultorias de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Sobre os avisos de segurança do {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". +| `repository_content_analysis` | Contém atividades relacionadas [à habilitação ou à desabilitação do uso de dados em um repositório privado](/articles/about-github-s-use-of-your-data). +| `repository_dependency_graph` | Contém atividades de nível do repositório relacionadas à habilitação ou à desabilitação do grafo de dependência em um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +{%- endif %} | `repository_image` | Contém atividades relacionadas a imagens para um repositório. +| `repository_invitation` | Contém atividades relacionadas a convites para ingresso em um repositório. +| `repository_projects_change` | Contém atividades relacionadas à habilitação de projetos em um repositório ou em todos os repositórios de uma organização. +{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | Contém atividades de nível do repositório relacionadas à verificação de segredos. Para obter mais informações, confira "[Sobre a verificação de segredos](/github/administering-a-repository/about-secret-scanning)". +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Contém atividades relacionadas a padrões personalizados da verificação de segredos em um repositório. Para obter mais informações, confira "[Como definir padrões personalizados para a verificação de segredos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Contém atividades relacionadas a padrões personalizados da verificação de segredos em um repositório. Para obter mais informações, confira "[Como proteger os pushes com a verificação de segredos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". +{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contém atividades relacionadas à permissão de que os membros da organização alterem a visibilidade do repositório para a organização. +{%- endif %} | `repository_vulnerability_alert` | Contém atividades relacionadas a [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). +{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Contém atividades de configuração no nível do repositório em relação a {% data variables.product.prodname_dependabot_alerts %}. +| `required_status_check` | Contém atividades relacionadas às verificações de status obrigatórias em branches protegidos. +{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Contém atividades relacionadas à restrição de notificações por email para domínios aprovados ou verificados em uma empresa. +{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Contém atividades relacionadas a [funções de repositório personalizadas](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | Contém atividades de configuração de nível da organização para a verificação de segredos em repositórios existentes. Para obter mais informações, confira "[Sobre a verificação de segredos](/github/administering-a-repository/about-secret-scanning)". +| `secret_scanning_new_repos` | Contém atividades de configuração de nível da organização para verificação de segredos para os repositórios criados na organização. +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Contém atividades relacionadas ao registro e à remoção de chaves de segurança. +{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | Contém eventos relacionados a botões de patrocinador (confira "[Como exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)"). +{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Contém atividades relacionadas a uma autoridade de certificação SSH em uma organização ou uma empresa. +| `ssh_certificate_requirement` | Contém atividades relacionadas ao requisito de que os membros usem certificados SSH para acessar recursos da organização. +{%- endif %} {% ifversion sso-redirect %} | `sso_redirect` | Contém atividades relacionadas ao redirecionamento automático de usuários para entrar (confira "[Como aplicar políticas para configurações de segurança em sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)"). {% endif %} | `staff` | Contém atividades relacionadas a um administrador do site que executa uma ação. +| `team` | Contém atividades relacionadas às equipes em uma organização. +| `team_discussions` | Contém atividades relacionadas ao gerenciamento de discussões em equipe em uma organização. +{%- ifversion ghec %} | `team_sync_tenant` | Contém atividades relacionadas à sincronização de equipe com um IdP para uma empresa ou uma organização. +{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Contém atividades relacionadas à autenticação de dois fatores. +{%- endif %} | `user` | Contém atividades relacionadas aos usuários em uma empresa ou organização. +{%- ifversion ghec or ghes %} | `user_license` | Contém atividades relacionadas a um usuário que ocupa uma estação licenciada e que é membro de uma empresa. +{%- endif %} | `workflows` | Contém atividades relacionadas a fluxos de trabalho do {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/data/reusables/codespaces/stopping-a-codespace.md b/translations/pt-BR/data/reusables/codespaces/stopping-a-codespace.md index 0f9abc618d6c..625d8bd9db61 100644 --- a/translations/pt-BR/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/pt-BR/data/reusables/codespaces/stopping-a-codespace.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159042" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189885" --- -Você pode interromper um codespace a qualquer momento. Ao interromper um codespace, todos os processos em execução são interrompidos e o histórico de terminais é limpo. Qualquer alteração salva no seu codespace ainda estará disponível na próxima vez que você iniciá-lo. Se você não interromper explicitamente um codespace, ele continuará sendo executado até que o tempo seja esgotado em razão de inatividade. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces)". +Você pode interromper um codespace a qualquer momento. Ao interromper um codespace, todos os processos em execução são interrompidos e o histórico de terminais é limpo. Qualquer alteração salva no seu codespace ainda estará disponível na próxima vez que você iniciá-lo. Se você não interromper explicitamente um codespace, ele continuará sendo executado até que o tempo seja esgotado em razão de inatividade. Para obter mais informações, confira "[O ciclo de vida do codespace](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces)". Somente a execução de codespaces incorre em encargos de CPU. Um codespace interrompido incorre apenas em custos de armazenamento. diff --git a/translations/pt-BR/data/reusables/copilot/copilot-cta-button.md b/translations/pt-BR/data/reusables/copilot/copilot-cta-button.md new file mode 100644 index 000000000000..7036da88890b --- /dev/null +++ b/translations/pt-BR/data/reusables/copilot/copilot-cta-button.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 9f7ac09b688bbe2b74a5cba71d2605365b7e7366 +ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148185120" +--- +Experimente o {% data variables.product.prodname_copilot %} {% octicon "link-external" height:16 %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/discussions/repository-category-limit.md b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md index ae5dc7b1a6c7..387fde0fbd0d 100644 --- a/translations/pt-BR/data/reusables/discussions/repository-category-limit.md +++ b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md @@ -1,9 +1,9 @@ --- -ms.openlocfilehash: 7b782aa3d23143a62b07aedf0a07df3734173d44 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a +ms.openlocfilehash: f58fb9410d93c9e50d33de5f1b12b9d6441ea561 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145127629" +ms.lasthandoff: 11/30/2022 +ms.locfileid: "148185610" --- -Cada repositório ou organização pode ter até 10 categorias. +Cada repositório ou organização pode ter até 25 categorias. diff --git a/translations/pt-BR/data/reusables/enterprise-managed/sso-redirect-release-phase.md b/translations/pt-BR/data/reusables/enterprise-managed/sso-redirect-release-phase.md new file mode 100644 index 000000000000..af59c06640b6 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-managed/sso-redirect-release-phase.md @@ -0,0 +1,13 @@ +--- +ms.openlocfilehash: f246dbf76575a4338b8fa28ffbd5439c4121505f +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184036" +--- +{% note %} + +**Nota:** o redirecionamento automático de usuários para entrar está atualmente em versão beta para {% data variables.product.prodname_emus %} e sujeito a alterações. + +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md b/translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md index 2ebdbd0ac725..83c2d3936f68 100644 --- a/translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md +++ b/translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md @@ -1,5 +1,13 @@ -When you enable the allow list, the IP addresses you have configured are immediately added to the allow lists of organizations in your enterprise. If you disable the allow list, the addresses are removed from the organization allow lists. +--- +ms.openlocfilehash: f88150299e77eff08e5db75a7ef5bf5bd460328b +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184046" +--- +Ao habilitar a lista de permissões, os endereços IP que você configurou são imediatamente adicionados às listas de permissões de organizações na sua empresa. Se você desabilitar a lista de autorização, os endereços serão removidos da lista de permissões da organização. -{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)." +{% data reusables.identity-and-permissions.org-enterprise-allow-list-interaction %} Para obter mais informações, confira "[Gerenciar endereços IP permitidos para sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)". -You can choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} installed in your enterprise. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by GitHub Apps](#allowing-access-by-github-apps)." +Você pode escolher adicionar automaticamente à sua lista de permissões qualquer endereço IP configurado para {% data variables.product.prodname_github_apps %} instalado na sua empresa. O criador de um {% data variables.product.prodname_github_app %} pode configurar uma lista de permissões para o seu aplicativo, especificando os endereços IP em que o aplicativo é executado. Ao herdar a lista de permissões deles para a sua lista, você evita as solicitações de conexão do aplicativo que está sendo recusado. Para obter mais informações, confira "[Permitir acesso por Aplicativos do GitHub](#allowing-access-by-github-apps)". diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md b/translations/pt-BR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md new file mode 100644 index 000000000000..929a44f3f516 --- /dev/null +++ b/translations/pt-BR/data/reusables/identity-and-permissions/org-enterprise-allow-list-interaction.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 5ce9d5cc32dc07a1fe4ead5b16b75a7b10509467 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184035" +--- +Os proprietários da organização podem adicionar entradas adicionais à lista de permissões para suas organizações, mas não podem gerenciar entradas herdadas da lista de permissões da conta corporativa e os proprietários corporativos não podem gerenciar entradas adicionadas à lista de permissões da organização. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/organizations/require-ssh-cert.md b/translations/pt-BR/data/reusables/organizations/require-ssh-cert.md index f4565b4bff01..e7a023d452e4 100644 --- a/translations/pt-BR/data/reusables/organizations/require-ssh-cert.md +++ b/translations/pt-BR/data/reusables/organizations/require-ssh-cert.md @@ -1,8 +1,16 @@ -1. Optionally, to require members to use SSH certificates, select **Require SSH Certificates**, then click **Save**. - ![Require SSH Certificate checkbox and save button](/assets/images/help/organizations/require-ssh-cert.png) +--- +ms.openlocfilehash: abb4b47406958c1933c5c2bdf7d7e2e2c1091907 +ms.sourcegitcommit: 7a74d5796695bb21c30e4031679253cbc16ceaea +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/28/2022 +ms.locfileid: "148184033" +--- +1. Opcionalmente, para exigir que os membros usem certificados SSH, selecione **Exigir Certificados SSH** e clique em **Salvar**. + ![Caixa de seleção Solicitar Certificado SSH e botão Salvar](/assets/images/help/organizations/require-ssh-cert.png) {% note %} - **Note:** When you require SSH certificates, the requirement does not apply to authorized third-party integrations or to {% data variables.product.prodname_dotcom %} features such as {% data variables.product.prodname_actions %}{% ifversion fpt or ghec %} and {% data variables.product.prodname_codespaces %}{% endif %}, which are trusted environments within the {% data variables.product.prodname_dotcom %} ecosystem. + **Nota:** quando você precisa de certificados SSH, o requisito não se aplica a integrações autorizadas de terceiros ou a recursos do {% data variables.product.prodname_dotcom %}, como {% data variables.product.prodname_actions %}{% ifversion fpt or ghec %} e {% data variables.product.prodname_codespaces %}{% endif %}, que são ambientes confiáveis dentro do ecossistema do {% data variables.product.prodname_dotcom %}. {% endnote %} diff --git a/translations/pt-BR/data/reusables/rest-api/about-api-versions.md b/translations/pt-BR/data/reusables/rest-api/about-api-versions.md new file mode 100644 index 000000000000..9684a7ea9761 --- /dev/null +++ b/translations/pt-BR/data/reusables/rest-api/about-api-versions.md @@ -0,0 +1,32 @@ +--- +ms.openlocfilehash: dd7c5f37ab5b2d699b47460195e02ae21fca1733 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184380" +--- +A API REST do {% data variables.product.product_name %} tem controle de versão. O nome da versão da API é baseado na data em que a versão da API foi lançada. Por exemplo, a versão `{{ initialRestVersioningReleaseDate }}` da API foi lançada em {{ initialRestVersioningReleaseDateLong }}. + +Quaisquer alterações interruptivas serão lançadas em uma nova versão da API. Alterações interruptivas são alterações que podem potencialmente interromper uma integração. As alterações interruptivas incluem: + +- removendo uma operação inteira +- removendo ou renomeando um parâmetro +- removendo ou renomeando um campo de resposta +- adicionando um novo parâmetro obrigatório +- fazendo um parâmetro opcional anteriormente necessário +- alterando o tipo de um parâmetro ou campo de resposta +- removendo valores de enumeração +- adicionando uma nova regra de validação a um parâmetro existente +- alterando os requisitos de autenticação ou autorização + +Quaisquer alterações aditivas (não interruptivas) estarão disponíveis em todas as versões da API com suporte. Alterações aditivas são alterações que não devem interromper uma integração. As alterações aditivas incluem: + +- adicionando uma operação +- adicionando um parâmetro opcional +- adicionando um cabeçalho de solicitação opcional +- adicionando um campo de resposta +- adicionando um cabeçalho de resposta +- adicionando valores de enumeração + +Quando uma nova versão da API REST for lançada, a versão anterior da API terá suporte por pelo menos mais 24 meses após o lançamento da nova versão da API. diff --git a/translations/pt-BR/data/reusables/rest-api/version-header.md b/translations/pt-BR/data/reusables/rest-api/version-header.md new file mode 100644 index 000000000000..4488abf18683 --- /dev/null +++ b/translations/pt-BR/data/reusables/rest-api/version-header.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 28c0a6c9cde70105e42feef89486c5c893ebbe72 +ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/29/2022 +ms.locfileid: "148184379" +--- +{% ifversion api-date-versioning %}--header "X-GitHub-Api-Version:{{ allVersions[currentVersion].latestApiVersion }}"{% endif %} From 34ab8887d61256b4fcd8928569c259f438add32e Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Fri, 2 Dec 2022 09:14:39 -0800 Subject: [PATCH 3/3] New translation batch for cn (#33187) --- translations/log/msft-cn-resets.csv | 4 +- ...card-is-added-to-a-project-board-column.md | 58 ++++++++------- ...github-packages-with-azure-blob-storage.md | 3 + .../githubs-ssh-key-fingerprints.md | 23 +++--- .../using-ssh-over-the-https-port.md | 8 +- .../deleting-a-codespace.md | 10 +-- .../developing-in-codespaces/index.md | 8 +- .../opening-an-existing-codespace.md | 10 +-- .../stopping-and-starting-a-codespace.md | 10 +-- .../codespaces/getting-started/deep-dive.md | 10 +-- .../codespaces/getting-started/index.md | 8 +- .../the-codespace-lifecycle.md | 73 +++++++++++++++++++ .../zh-CN/content/codespaces/index.md | 8 +- ...stricting-the-base-image-for-codespaces.md | 10 +-- ...ll-request-template-for-your-repository.md | 61 ++++++++-------- ...rl-for-a-repository-from-github-desktop.md | 33 +++++++++ .../index.md | 8 +- ...github-codespaces-with-github-classroom.md | 10 +-- ...auth-app-and-github-app-access-requests.md | 8 +- ...figuring-a-remote-repository-for-a-fork.md | 43 +++++++++++ .../working-with-forks/index.md | 8 +- .../working-with-forks/syncing-a-fork.md | 62 ++++++++-------- .../overview/resources-in-the-rest-api.md | 12 +-- .../codespaces/stopping-a-codespace.md | 10 +-- 24 files changed, 330 insertions(+), 168 deletions(-) create mode 100644 translations/zh-CN/content/codespaces/getting-started/the-codespace-lifecycle.md create mode 100644 translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md create mode 100644 translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv index 4f80b2fecc79..e53a40bc1ea6 100644 --- a/translations/log/msft-cn-resets.csv +++ b/translations/log/msft-cn-resets.csv @@ -491,7 +491,6 @@ translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing- translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags -translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error @@ -639,6 +638,7 @@ translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing- translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,broken liquid tags translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,rendering error translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error @@ -742,6 +742,7 @@ translations/zh-CN/content/communities/documenting-your-project-with-wikis/about translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error +translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error translations/zh-CN/content/copilot/quickstart.md,broken liquid tags translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags @@ -886,7 +887,6 @@ translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/propos translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error -translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 25a2c6a964c6..380344daddce 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -1,6 +1,6 @@ --- -title: Removing a label when a card is added to a project board column -intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a {% data variables.projects.projects_v1_board %}.' +title: 将卡片添加到项目板列时删除标签 +intro: '可以使用 {% data variables.product.prodname_actions %} 在议题或拉取请求添加到{% data variables.projects.projects_v1_board %}上的特定列时自动删除标签。' redirect_from: - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column versions: @@ -13,23 +13,27 @@ topics: - Workflows - Project management shortTitle: Remove label when adding card +ms.openlocfilehash: d86d9e5ad198c9cf8811b47f2a6c8a7114e20104 +ms.sourcegitcommit: 4d6d3735d32540cb6de3b95ea9a75b8b247c580d +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148185627' --- +{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} +## 简介 -## Introduction +本教程演示如何使用 [`actions/github-script` 操作](https://github.com/marketplace/actions/github-script)和条件，从已添加到{% data variables.projects.projects_v1_board %}上指定列的议题和拉取请求中删除标签。 例如，可以在项目卡移至 `Done` 列后删除 `needs review` 标签。 -This tutorial demonstrates how to use the [`actions/github-script` action](https://github.com/marketplace/actions/github-script) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a {% data variables.projects.projects_v1_board %}. For example, you can remove the `needs review` label when project cards are moved into the `Done` column. +在本教程中，你将首先创建一个使用 [`actions/github-script` 操作](https://github.com/marketplace/actions/github-script)的工作流文件。 然后，您将自定义工作流以适应您的需要。 -In the tutorial, you will first make a workflow file that uses the [`actions/github-script` action](https://github.com/marketplace/actions/github-script). Then, you will customize the workflow to suit your needs. - -## Creating the workflow +## 创建工作流程 1. {% data reusables.actions.choose-repo %} -2. Choose a {% data variables.projects.projects_v1_board %} that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing {% data variables.projects.projects_v1_board %}, or you can create a new {% data variables.projects.projects_v1_board %}. For more information about creating a project, see "[Creating a {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/creating-a-project-board)." +2. 选择属于存储库的{% data variables.projects.projects_v1_board %}。 此工作流程不能用于属于用户或组织的项目。 可以使用现有{% data variables.projects.projects_v1_board %}，也可以创建新的{% data variables.projects.projects_v1_board %}。 有关创建项目的详细信息，请参阅“[创建{% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/creating-a-project-board)”。 3. {% data reusables.actions.make-workflow-file %} -4. Copy the following YAML contents into your workflow file. +4. 将以下 YAML 内容复制到工作流程文件中。 ```yaml{:copy} name: Remove a label @@ -58,28 +62,28 @@ In the tutorial, you will first make a workflow file that uses the [`actions/git }) ``` -5. Customize the parameters in your workflow file: - - In `github.event.project_card.column_id == '12345678'`, replace `12345678` with the ID of the column where you want to un-label issues and pull requests that are moved there. +5. 自定义工工作流程文件中的参数： + - 在 `github.event.project_card.column_id == '12345678'` 中，将 `12345678` 替换为要取消标记移至其中的议题和拉取请求的列 ID。 - To find the column ID, navigate to your {% data variables.projects.projects_v1_board %}. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`. + 若要查找列 ID，请导航到{% data variables.projects.projects_v1_board %}。 在列标题旁边，请单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击“复制列链接”。 列 ID 是复制的链接末尾的数字。 例如，`24687531` 是 `https://github.com/octocat/octo-repo/projects/1#column-24687531` 的列 ID。 - If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards. - - Change the value for `name` in the `github.rest.issues.removeLabel()` function to the name of the label that you want to remove from issues or pull requests that are moved to the specified column(s). For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)." + 如果想要在多个列上操作，请使用 `||` 分隔条件。 例如，只要项目卡添加到了列 `12345678` 或列 `87654321`，就会使用 `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'`。 这些列可能在不同的项目板上。 + - 将 `github.rest.issues.removeLabel()` 函数中的 `name` 更改为要从移至指定列的议题或拉取请求中删除的标签列表。 有关标签的详细信息，请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。 6. {% data reusables.actions.commit-workflow %} -## Testing the workflow +## 测试工作流程 -Every time a project card on a {% data variables.projects.projects_v1_board %} in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified label from the issue or a pull request. Cards that are notes will not be affected. +每当存储库中{% data variables.projects.projects_v1_board %}上的项目卡移动时，该工作流都会运行。 如果移动的项目卡是议题或拉取请求，并移入指定的列，则该工作流将从议题或拉取请求中删除指定的标签。 记事卡不会受到影响。 -Test your workflow out by moving an issue on your {% data variables.projects.projects_v1_board %} into the target column. +通过将{% data variables.projects.projects_v1_board %}上的议题移到目标列中来测试自己的工作流。 -1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." -2. Label the issue with the label that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)." -3. Add the issue to the {% data variables.projects.projects_v1_board %} column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)." -4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." -5. When the workflow completes, the issue that you added to the project column should have the specified label removed. +1. 在仓库中打开一个议题。 有关详细信息，请参阅“[创建问题](/github/managing-your-work-on-github/creating-an-issue)”。 +2. 标记带有需要工作流删除的标签的议题。 有关详细信息，请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。 +3. 将议题添加到在工作流文件中指定的 {% data variables.projects.projects_v1_board %} 列。 有关详细信息，请参阅“[向 {% data variables.product.prodname_project_v1 %} 添加问题和拉取请求](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)”。 +4. 要查看通过将议题添加到项目所触发的工作流程运行，请查看工作流程运行的历史记录。 有关详细信息，请参阅“[查看工作流运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 +5. 当工作流完成时，添加到项目列的议题中指定的标签应已被删除。 -## Next steps +## 后续步骤 -- To learn more about additional things you can do with the `actions/github-script` action, see the [`actions/github-script` action documentation](https://github.com/marketplace/actions/github-script). -- [Search GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) for examples of workflows using this action. +- 如需详细了解 `actions/github-script` 操作的其他用途，请参阅 [`actions/github-script` 操作文档](https://github.com/marketplace/actions/github-script)。 +- [搜索 GitHub](https://github.com/search?q=%22uses:+actions/github-script%22&type=code) 以获取使用此操作的工作流示例。 diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index a1a74dd1f480..a7060df4d03e 100644 --- a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -31,6 +31,9 @@ Before you can enable and configure {% data variables.product.prodname_registry {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} 1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + + - You must create a storage container prior to setting the container name and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index 61f7630bc138..1286785f705f 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -1,6 +1,6 @@ --- -title: GitHub 的 SSH 密钥指纹 -intro: 公钥指纹可用于验证与远程服务器的连接。 +title: GitHub's SSH key fingerprints +intro: Public key fingerprints can be used to validate a connection to a remote server. redirect_from: - /articles/what-are-github-s-ssh-key-fingerprints - /articles/github-s-ssh-key-fingerprints @@ -14,15 +14,20 @@ topics: - Identity - Access management shortTitle: SSH key fingerprints -ms.openlocfilehash: 29f61df463d014e6a72ad7dd21049a2b338b893e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084654' --- -以下是 {% data variables.product.prodname_dotcom %} 的公钥指纹： +These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) +- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated) - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) + +You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts: + +```text +github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl +github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg= +github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== +``` + +For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)." diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 92f37fba9d43..7815859b8efc 100644 --- a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -30,7 +30,7 @@ $ ssh -T -p 443 git@ssh.github.com **Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`. -{% endnote %} +{% endnote %} If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). @@ -71,8 +71,8 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: > ~/.ssh/known_hosts:32: github.com -> Are you sure you want to continue connecting (yes/no/[fingerprint])? +> Are you sure you want to continue connecting (yes/no/[fingerprint])? ``` -It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches -one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." +It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches +one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)." diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 3ee8f6ea9966..c8f96dfcbbb9 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,12 +13,12 @@ topics: - Fundamentals - Developer shortTitle: Delete a codespace -ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 24b53cc0cead2b6b15894ada4c799abc8e1c6e7a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158659' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188254' --- 可以通过多种方式删除 codespace：在终端中使用 {% data variables.product.prodname_cli %}、在 {% data variables.product.prodname_vscode %} 中或在 Web 浏览器中。 使用本文中的选项卡可显示删除 codespace 的每种方法的说明。 @@ -135,5 +135,5 @@ gh codespace delete --repo octo-org/octo-repo --days 7 还可以使用 REST API 删除组织的 codespace。 有关详细信息，请参阅“[Codespaces 组织](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)”。 ## 延伸阅读 -- [codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle) +- [codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle) - [配置 codespace 的自动删除](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces) diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md index d65c320e278a..a4feaa0f050d 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md @@ -22,11 +22,11 @@ children: - /using-github-codespaces-in-visual-studio-code - /using-github-codespaces-in-your-jetbrains-ide - /using-github-codespaces-with-github-cli -ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 6ace677a68ce7b592ac8ad2a8b83ae4d948b8747 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159011' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188286' --- diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md index a0a418e4d4e9..133d9f166927 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md @@ -10,12 +10,12 @@ topics: - Fundamentals - Developer shortTitle: Open an existing codespace -ms.openlocfilehash: e7a35c1a7b3a251094bf69fcd401291b69d03eae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: b139b7f4e8a696416c97b3c400d09a9f26371b9c +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159003' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188294' --- {% jetbrains %} @@ -23,7 +23,7 @@ ms.locfileid: '148159003' {% endjetbrains %} -您可以在 {% data variables.product.prodname_dotcom_the_website %}、JetBrains IDE 中、{% data variables.product.prodname_vscode %} 中或使用 {% data variables.product.prodname_cli %} 重新打开任何活动或已停止的代码空间。 无法重新打开已删除的 codespace。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle)”。 +您可以在 {% data variables.product.prodname_dotcom_the_website %}、JetBrains IDE 中、{% data variables.product.prodname_vscode %} 中或使用 {% data variables.product.prodname_cli %} 重新打开任何活动或已停止的代码空间。 无法重新打开已删除的 codespace。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)”。 可以在“你的 codespace”页 ([github.com/codespaces](https://github.com/codespaces)) 上查看所有 codespace。 在此页中，可以： diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md index f04016d90711..4988035a859b 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md @@ -10,12 +10,12 @@ topics: - Fundamentals - Developer shortTitle: Stop a codespace -ms.openlocfilehash: c09cd757ac2667c32c26f9b5e7d7a36b8e5431f9 -ms.sourcegitcommit: 7fb7ec2e665856fc5f7cd209b53bd0fb1c9bbc67 +ms.openlocfilehash: 5c34fd5b7d72f52e203cd8f8fdc1871ff6a2f014 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148185081' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188246' --- {% jetbrains %} @@ -110,4 +110,4 @@ ms.locfileid: '148185081' ## 延伸阅读 -- [codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle) +- [codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle) diff --git a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md index 6580b239b284..c8108b671c9e 100644 --- a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md +++ b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md @@ -9,12 +9,12 @@ versions: type: quick_start topics: - Codespaces -ms.openlocfilehash: 5f97a137ec09191d5cbaa9c10aa280e10f11bbc0 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 01e4f3990cc47f61678811f7c4a77b86626fd8a5 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158643' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188262' --- {% data variables.product.prodname_github_codespaces %} 是一个基于云的即时开发环境，它使用容器为你提供用于开发的通用语言、工具和实用程序。 {% data variables.product.prodname_github_codespaces %} 也是可配置的，通过它可为项目创建自定义的开发环境。 通过为项目配置自定义开发环境，可以为项目的所有用户提供可重复的代码空间配置。 @@ -161,4 +161,4 @@ ms.locfileid: '148158643' - [为组织启用 {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization) - [管理组织中的 {% data variables.product.prodname_github_codespaces %} 成本](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization) - [将开发容器配置添加到存储库](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces) -- [codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle) +- [codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle) diff --git a/translations/zh-CN/content/codespaces/getting-started/index.md b/translations/zh-CN/content/codespaces/getting-started/index.md index 0a7a000921c0..fbf49e6931eb 100644 --- a/translations/zh-CN/content/codespaces/getting-started/index.md +++ b/translations/zh-CN/content/codespaces/getting-started/index.md @@ -9,11 +9,11 @@ children: - /quickstart - /the-codespace-lifecycle - /deep-dive -ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: e89c26ddd6606192f93449fbc99660afe1fb2506 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148159766' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188270' --- diff --git a/translations/zh-CN/content/codespaces/getting-started/the-codespace-lifecycle.md b/translations/zh-CN/content/codespaces/getting-started/the-codespace-lifecycle.md new file mode 100644 index 000000000000..1d5fddf415f6 --- /dev/null +++ b/translations/zh-CN/content/codespaces/getting-started/the-codespace-lifecycle.md @@ -0,0 +1,73 @@ +--- +title: codespace 生命周期 +intro: '可以在 {% data variables.product.prodname_github_codespaces %} 环境中进行开发，并在整个 codespace 生命周期中维护数据。' +versions: + fpt: '*' + ghec: '*' +type: overview +topics: + - Codespaces + - Developer +redirect_from: + - /codespaces/developing-in-codespaces/codespaces-lifecycle + - /codespaces/developing-in-codespaces/the-codespace-lifecycle +ms.openlocfilehash: 8f223bce2acf2f6dc6200271397c0d70f28aefe4 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188358' +--- +## 关于代码空间的生命周期 + +代码空间的生命周期从创建代码空间时开始，到删除代码空间时结束。 您可以断开连接并重新连接到活动代码空间，而不会影响其正在运行的进程。 您可以停止并重新启动代码空间，而不会丢失对项目所做的更改。 + +## 创建 codespace + +当您要处理项目时，可以选择创建新代码空间或打开现有代码空间。 你可能希望每次在 {% data variables.product.prodname_github_codespaces %} 中开发时从存储库的分支创建新的 codespace，或者为功能保留长时间运行的 codespace。 {% data reusables.codespaces.starting-new-project-template %} 有关详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)”和“[从模板创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)”。 + +{% data reusables.codespaces.max-number-codespaces %} 同样，如果达到最大活动 codespace 数并尝试启动另一个活动 codespace，系统将提示你停止其中一个活动 codespace。 + +如果选择在每次处理项目时都创建新的代码空间，则应定期推送更改，以便任何新提交都位于 {% data variables.product.prodname_dotcom %} 上。 如果选择对项目使用长时间运行的代码空间，则每次开始在代码空间中工作时，都应从存储库的默认分支中提取代码空间，以便您的环境具有最新的提交。 此工作流程与在本地计算机上处理项目时非常相似。 + +{% data reusables.codespaces.prebuilds-crossreference %} + +## 在代码空间中保存更改 + +当您通过 Web 连接到代码空间时，将自动为 Web 编辑器启用自动保存，并配置为在延迟后保存更改。 当您通过桌面上运行的 {% data variables.product.prodname_vscode %} 连接到代码空间时，必须启用自动保存。 有关详细信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[保存/自动保存](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)。 + +你的工作将保存在云中的虚拟机上。 可以关闭和停止 codespace，稍后返回到保存的工作。 如果您有未保存的更改，编辑器将在退出之前提示您保存这些更改。 但是，如果 codespace 被删除，则你的工作也会被删除。 若要持久保存工作，需要提交更改并将其推送到远程存储库，或者将工作发布到新的远程存储库（如果从模板创建 codespace）。 有关详细信息，请参阅[在 codespace 中使用源代码管理](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)。 + +## {% data variables.product.prodname_github_codespaces %} 超时 + +如果使代码空间在没有交互的情况下保持运行状态，或者退出代码空间而不显式停止它，则代码空间将在一段时间不活动后超时并停止运行。 默认情况下，代码空间将在处于非活动状态 30 分钟后超时，但您可以自定义所创建的新代码空间的超时期限的持续时间。 有关为 codespace 设置默认超时期限的详细信息，请参阅“[为 {% data variables.product.prodname_github_codespaces %} 设置超时期限](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)”。 有关停止 codespace 的详细信息，请参阅“[停止 codespace](#stopping-a-codespace)”。 + +当代码空间超时时，将保留上次保存更改时的数据。 有关详细信息，请参阅“[在 codespace 中保存更改](#saving-changes-in-a-codespace)”。 + +## 重建代码空间 + +可以重新生成 codespace 来实施对开发容器配置的更改。 对于大多数使用，可以创建新的代码空间作为重新构建代码空间的替代方法。 默认情况下，重新生成 codespace 时，{% data variables.product.prodname_github_codespaces %} 将重复使用缓存中的映像，以加快重新生成过程。 或者，可以执行完全重新生成，以清除缓存并使用新映像重新生成容器。 + +有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)”和“[完全重新生成容器](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)”。 + +## 停止代码空间 + +{% data reusables.codespaces.stopping-a-codespace %} 有关详细信息，请参阅“[停止和启动 codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)”。 + +## 删除代码空间 + +您可以为特定任务创建代码空间，然后在将更改推送到远程分支后安全地删除该代码空间。 + +如果您尝试删除包含未填充 git 提交的代码空间，编辑器将通知您有尚未推送到远程分支的更改。 您可以推送任何所需的更改，然后删除代码空间，或继续删除代码空间和任何未提交的更改。 还可以将代码导出到新分支，而无需创建新的代码空间。 有关详细信息，请参阅“[将更改导出到分支](/codespaces/troubleshooting/exporting-changes-to-a-branch)”。 + +将自动删除已停止并在指定时间段内保持非活动状态的 codespace。 默认情况下，非活动 codespace 在 30 天后删除，但你可以自定义 codespace 保持期。 有关详细信息，请参阅“[配置 codespace 的自动删除](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)”。 + +如果创建一个 codespace，无论是处于活动状态还是已停止，它将持续产生存储费用，直到被删除。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)”。 删除 codespace 不会减少 {% data variables.product.prodname_github_codespaces %} 的当前计费金额，该金额在每个月度计费周期内累积。 有关详细信息，请参阅“[查看 {% data variables.product.prodname_github_codespaces %} 使用情况](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)”。 + +有关删除 codespace 的详细信息，请参阅“[删除 codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)”。 + +## 使用 {% data variables.product.prodname_github_codespaces %} 时丢失连接 + +{% data variables.product.prodname_github_codespaces %} 是一个基于云的开发环境，需要连接 Internet。 如果您在代码空间中工作时失去互联网连接，您将无法访问代码空间。 但是，任何未提交的更改将保存。 当您再次接入互联网时，可以按离开时完全相同的状态连接到代码空间。 如果您的互联网连接不稳定，则应经常提交并推送更改。 + +如果知道自己会经常脱机工作，则可以使用[扩展名为“Dev Containers”](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)的 `devcontainer.json` 文件，以便 {% data variables.product.prodname_vscode_shortname %} 生成并附加到存储库的本地开发容器。 有关详细信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[在容器内开发](https://code.visualstudio.com/docs/remote/containers)。 diff --git a/translations/zh-CN/content/codespaces/index.md b/translations/zh-CN/content/codespaces/index.md index fc688669b01d..7c7e4bb1858c 100644 --- a/translations/zh-CN/content/codespaces/index.md +++ b/translations/zh-CN/content/codespaces/index.md @@ -53,11 +53,11 @@ children: - /troubleshooting - /the-githubdev-web-based-editor - /guides -ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 242931386711938cb1eb5e9b84ad66a581ecb1eb +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148160432' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188302' --- diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md index 4fc3ad0c5f10..0238bb390101 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md @@ -9,12 +9,12 @@ versions: type: how_to topics: - Codespaces -ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: f17bb20aa919ca94cd13e14a6f770cea23042b2b +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158995' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188278' --- ## 概述 @@ -39,7 +39,7 @@ ms.locfileid: '148158995' {% note %} **注释**： -* 基础映像策略仅在创建 codespace 时适用。 目前，在重新生成容器时不适用。 将来的版本中可能会发生变化。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace)”。 +* 基础映像策略仅在创建 codespace 时适用。 目前，在重新生成容器时不适用。 将来的版本中可能会发生变化。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle#rebuilding-a-codespace)”。 * 基本映像策略不适用于默认映像，也不适用于在开发容器配置中引入错误导致无法重新生成容器的情况下用于恢复 codespace 的映像。 {% endnote %} diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md index 19664831c8d8..44aa07505cf3 100644 --- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md @@ -1,6 +1,6 @@ --- -title: 为仓库创建拉取请求模板 -intro: 将拉取请求模板添加到仓库后，项目贡献者会自动在拉取请求正文中看到模板的内容。 +title: Creating a pull request template for your repository +intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.' redirect_from: - /articles/creating-a-pull-request-template-for-your-repository - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository @@ -12,44 +12,41 @@ versions: topics: - Community shortTitle: Create a PR template -ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145086515' --- -有关详细信息，请参阅“[关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。 -可以在任何支持的文件夹中创建 PULL_REQUEST_TEMPLATE/ 子目录，以包含多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板。 有关详细信息，请参阅“[使用查询参数创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”。 +For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." + +You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." {% ifversion fpt or ghes or ghec %} -可以为组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}创建默认的拉取请求模板。 有关详细信息，请参阅[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)。 +You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## 添加拉取请求模板 - -{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. 在文件名字段中： - - 若要使拉取请求模板显示在存储库根目录中，请将拉取请求模板命名为 `pull_request_template.md`。 - ![根目录中的新拉取请求模板名称](/assets/images/help/repository/pr-template-file-name.png) - - 若要使拉取请求模板显示在存储库的 `docs` 目录中，请将拉取请求模板命名为 `docs/pull_request_template.md`。 - ![文档目录中的新拉取请求模板](/assets/images/help/repository/pr-template-file-name-docs.png) - - 若要将文件存储在隐藏目录中，请将拉取请求模板命名为 `.github/pull_request_template.md`。 - ![隐藏目录中的新拉取请求模板](/assets/images/help/repository/pr-template-hidden-directory.png) - - 若要创建多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板，请键入“.github/PULL_REQUEST_TEMPLATE/”，后跟拉取请求模板的名称。 例如，`.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`。 也可以在根目录或 `docs/` 目录的 `PULL_REQUEST_TEMPLATE` 子目录中存储多个拉取请求模板。 有关详细信息，请参阅“[关于使用查询参数自动处理问题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)”。 - ![隐藏目录中新的多拉取请求模板](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. 在新文件的正文中，添加您的拉取请求模板。 这可能包括： - - 存储库中[对相关问题的引用](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。 - - 对拉取请求中所提议更改的说明。 - - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) 负责审查提议更改的人员或团队。 -{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} 模板可供协作者用来合并到存储库的默认分支。 +## Adding a pull request template + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field: + - To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`. + ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png) + - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`. + ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png) + - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`. + ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png) + - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)." + ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) +4. In the body of the new file, add your pull request template. This could include: + - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository. + - A description of the changes proposed in the pull request. + - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes. +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## 延伸阅读 +## Further reading -- [关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates) -- [关于使用查询参数自动处理问题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters) -- [创建拉取请求](/articles/creating-a-pull-request) +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating a pull request](/articles/creating-a-pull-request)" diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md new file mode 100644 index 000000000000..8d2ce42fa196 --- /dev/null +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-the-remote-url-for-a-repository-from-github-desktop.md @@ -0,0 +1,33 @@ +--- +title: 在 GitHub Desktop 中更改存储库的远程 URL +intro: '可在 {% data variables.product.prodname_desktop %} 中更改您操作的仓库的远程 URL。 如果仓库已经更名，或者拥有仓库的用户或组织已经改变，您便可执行此操作。' +redirect_from: + - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop + - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop +versions: + fpt: '*' +shortTitle: Change the remote URL for a repository +ms.openlocfilehash: e37c4878c13a9de95520f8e9c1edc9bf6416d46a +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188351' +--- +{% mac %} + +{% data reusables.desktop.mac-repository-settings-menu %} +2. 单击“远程”，然后在“主要远程存储库”下，键入所需的 URL 。 +![主要远程存储库字段](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endmac %} + +{% windows %} + +{% data reusables.desktop.windows-repository-settings-menu %} +2. 单击“远程”，然后在“主要远程存储库”下，键入所需的 URL 。 +![主要远程存储库字段](/assets/images/help/desktop/repository-settings-remote.png) {% data reusables.desktop.repository-settings-save %} + +{% endwindows %} diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md index c312e2ab1f61..afbf95835290 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md @@ -12,11 +12,11 @@ children: - /configuring-notifications-in-github-desktop - /changing-the-remote-url-for-a-repository-from-github-desktop shortTitle: Work with your remote repo -ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: f7e9f1ab5f73aaad29208db01c62815d7a20ba03 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099261' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188357' --- diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index f5015406c055..a68aca47737e 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -6,12 +6,12 @@ intro: '你可以将 {% data variables.product.prodname_github_codespaces %} 用 versions: fpt: '*' 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 %}' -ms.openlocfilehash: 6794d20b9ea0153b3baf4bee1a08c68b2ba17456 -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 832ab470d13cc741bc4a71e77840c99da5ff3de6 +ms.sourcegitcommit: a35d85531445980b5f04d3fc70180a29dad37f89 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: '148158875' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148189911' --- ## 关于 {% data variables.product.prodname_github_codespaces %} @@ -103,4 +103,4 @@ ms.locfileid: '148158875' ![学生 codespace 的教师作业概述](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -通过浏览器连接到 codespace 时，会自动启用自动保存。 如果要将更改保存到存储库，则需要提交更改并将其推送到远程分支。 如果默认情况下允许 codespace 在没有互动的情况下运行 30 分钟，codespace 将超时并停止运行。 将保留上次更改以来的数据。 有关 codespace 生命周期的详细信息，请参阅“[codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle)”。 +通过浏览器连接到 codespace 时，会自动启用自动保存。 如果要将更改保存到存储库，则需要提交更改并将其推送到远程分支。 如果默认情况下允许 codespace 在没有互动的情况下运行 30 分钟，codespace 将超时并停止运行。 将保留上次更改以来的数据。 有关 codespace 生命周期的详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)”。 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md b/translations/zh-CN/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md index cfc32d5f6d9f..732fede02e71 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md @@ -9,12 +9,12 @@ topics: - GitHub Apps - OAuth Apps shortTitle: Limit app access requests -ms.openlocfilehash: 4ea1bd133dcbabb9e7b3e3cbe65da5ff9c6eabac -ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110 +ms.openlocfilehash: 6c991ecfbdac75f1bb3bb4fdb5ea3a0692f1d040 +ms.sourcegitcommit: 30b0931723b704e219c736e0de7afe0fa799da29 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 10/25/2022 -ms.locfileid: '148007894' +ms.lasthandoff: 11/30/2022 +ms.locfileid: '148186433' --- ## 关于集成访问请求 diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md new file mode 100644 index 000000000000..d359c463da3a --- /dev/null +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork.md @@ -0,0 +1,43 @@ +--- +title: 为分支配置远程存储库 +intro: '必须在 Git 中配置指向上游存储库的远程存储库，才能[将你在分支中所做的更改同步](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)到原始存储库。 这也允许您将在原始仓库中所做的更改同步到复刻中。' +redirect_from: + - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /articles/configuring-a-remote-for-a-fork + - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork + - /github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Pull requests +shortTitle: Configure a remote repository +ms.openlocfilehash: 495d3c825356fd69c9130f8a122aa7a8702ff317 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188362' +--- +{% data reusables.command_line.open_the_multi_os_terminal %} +2. 列出当前为复刻配置的远程仓库。 + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + ``` +3. 指定将与分支同步的新远程上游存储库。 + ```shell + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git + ``` +4. 验证为复刻指定的新上游仓库。 + ```shell + $ git remote -v + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + ``` diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md index 0aa48fd2f297..98a6ac33cba4 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md @@ -18,11 +18,11 @@ children: - /syncing-a-fork - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d +ms.openlocfilehash: 0133f7759cb9040a5acb97a7b08c312a55079bda +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '146683659' +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188361' --- diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index c9b479247ebf..556278eb7bd2 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Syncing a fork -intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. +title: 同步复刻 +intro: 同步仓库的复刻以通过上游仓库使其保持最新。 redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,44 +19,48 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. +ms.openlocfilehash: 85b149e26cb65a428d7e9b66aea99d6b62430ae0 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 12/01/2022 +ms.locfileid: '148188326' --- - -## Syncing a fork branch from the web UI +## 从 Web UI 同步分叉分支 {% ifversion syncing-fork-web-ui %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Sync fork** dropdown. - !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) -3. Review the details about the commits from the upstream repository, then click **Update branch**. - ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) -{% else %} -1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. -2. Select the **Fetch upstream** dropdown. - !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. - !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。 +2. 选择“同步分支”下拉菜单。 + ![突出显示“同步分支”下拉菜单](/assets/images/help/repository/sync-fork-dropdown.png) +3. 查看有关上游存储库提交的详细信息，然后单击“更新分支”。 + ![突出显示“更新分支”按钮的同步分支模式](/assets/images/help/repository/update-branch-button.png) {% else %} +1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。 +2. 选择“提取上游”下拉菜单。 + ![“提取上游”下拉菜单](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. 查看有关上游存储库提交的详细信息，然后单击“提取并合并”。 + ![“提取并合并”按钮](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. +如果上游仓库的更改导致冲突，{% data variables.product.company_short %} 将提示您创建拉取请求以解决冲突。 -## Syncing a fork branch with the {% data variables.product.prodname_cli %} +## 使用 {% data variables.product.prodname_cli %} 同步分叉分支 -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} 若要详细了解 {% data variables.product.prodname_cli %}，请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。 -To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. +要从其父级更新远程分支，请使用 `gh repo sync -b BRANCHNAME` 子命令并提供分叉和分支名作为参数。 ```shell $ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. +如果上游存储库的更改导致冲突，则 {% data variables.product.prodname_cli %} 无法同步。你可以设置 `-force` 标志以覆盖目标分支。 -## Syncing a fork branch from the command line +## 从命令行同步分叉分支 -Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git. For more information, see "[Configuring a remote repository for a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)." +必须先在 Git 中配置指向上游存储库的远程库，然后才能将分支与上游存储库同步。 有关详细信息，请参阅“[为分支配置远程存储库](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-repository-for-a-fork)”。 {% data reusables.command_line.open_the_multi_os_terminal %} -2. Change the current working directory to your local project. -3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. +2. 将当前工作目录更改为您的本地仓库。 +3. 从上游仓库获取分支及其各自的提交。 对 `BRANCHNAME` 的提交将保存在本地分支 `upstream/BRANCHNAME` 中。 ```shell $ git fetch upstream @@ -68,14 +72,14 @@ Before you can sync your fork with an upstream repository, you must configure a > * [new branch] main -> upstream/main ``` -4. Check out your fork's local default branch - in this case, we use `main`. +4. 签出分支的本地默认分支，在本例中，我们使用 `main`。 ```shell $ git checkout main > Switched to branch 'main' ``` -5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. +5. 将上游默认分支（在本例中为 `upstream/main`）的更改合并到本地默认分支中。 这会使复刻的默认分支与上游仓库同步，而不会丢失本地更改。 ```shell $ git merge upstream/main @@ -88,7 +92,7 @@ Before you can sync your fork with an upstream repository, you must configure a > create mode 100644 README.md ``` - If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. + 如果本地分支没有任何唯一提交，Git 将执行快速转发。 有关详细信息，请参阅 Git 文档中的[基本分支和合并](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)。 ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -96,10 +100,10 @@ Before you can sync your fork with an upstream repository, you must configure a > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." + 如果本地分支具有唯一提交，则可能需要解决冲突。 有关详细信息，请参阅“[解决合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts)”。 {% tip %} -**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**提示**：同步分支只更新存储库的本地副本。 若要在 {% data variables.location.product_location %} 上更新分支，必须[推送更改](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)。 {% endtip %} diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md index 50c390d5a0a8..5c8dffbcde40 100644 --- a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md @@ -11,12 +11,12 @@ versions: miniTocMaxHeadingLevel: 3 topics: - API -ms.openlocfilehash: dc16916ada20275d41f23a8bc006cc79ddf51120 -ms.sourcegitcommit: d2f0b59ed096b9e68ef8f6fa019cd925165762ec +ms.openlocfilehash: 4fd3e2aad72ee0ffc4778a86dc99cd5bb6f9d2c5 +ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/29/2022 -ms.locfileid: '148184267' +ms.lasthandoff: 12/02/2022 +ms.locfileid: '148190397' --- {% ifversion api-date-versioning %} ## API 版本 @@ -262,10 +262,10 @@ $ curl {% ifversion fpt or ghae or ghec %} >> tmpl.expand => "/notifications" - >> tmpl.expand :all => 1 + >> tmpl.expand all: 1 => "/notifications?all=1" - >> tmpl.expand :all => 1, :participating => 1 + >> tmpl.expand all: 1, participating: 1 => "/notifications?all=1&participating=1" [rfc]: https://datatracker.ietf.org/doc/html/rfc6570 diff --git a/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md b/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md index 15150b186313..6bee45913d50 100644 --- a/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md +++ b/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md @@ -1,12 +1,12 @@ --- -ms.openlocfilehash: 4bdcc6ff93e7671d4dc368fc44784c963f549aae -ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8 +ms.openlocfilehash: 1eac21c20c1be77fe00ea676714a835fdb2e0de7 +ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/09/2022 -ms.locfileid: "148159043" +ms.lasthandoff: 12/01/2022 +ms.locfileid: "148189886" --- -您可以随时停止代码空间。 停止代码空间时，将停止所有正在运行的进程并清除终端历史记录。 下次启动代码空间时，代码空间中的任何已保存更改仍将可用。 如果未明确停止代码空间，它将继续运行，直到它因非活动而超时。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/developing-in-codespaces/the-codespace-lifecycle#timeouts-for-github-codespaces)”。 +您可以随时停止代码空间。 停止代码空间时，将停止所有正在运行的进程并清除终端历史记录。 下次启动代码空间时，代码空间中的任何已保存更改仍将可用。 如果未明确停止代码空间，它将继续运行，直到它因非活动而超时。 有关详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle#timeouts-for-github-codespaces)”。 只有运行的 codespace 才会产生 CPU 费用。 停止的 codespace 仅产生存储成本。