Octomerger Bot
@@ -0,0 +1,240 @@
|
||||
---
|
||||
title: Automating migration with GitHub Actions Importer
|
||||
intro: 'Use {% data variables.product.prodname_actions_importer %} to plan and automate your migration to {% data variables.product.prodname_actions %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Migration
|
||||
- CI
|
||||
- CD
|
||||
shortTitle: Automate migration with {% data variables.product.prodname_actions_importer %}
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data variables.product.prodname_actions_importer %} is currently available as a public preview. Visit the [sign up page](https://github.com/features/actions-importer/signup) to request access to the preview. Once you are granted access you'll be able to use the `gh-actions-importer` CLI extension
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About {% data variables.product.prodname_actions_importer %}
|
||||
|
||||
You can use {% data variables.product.prodname_actions_importer %} to plan and automatically migrate your CI/CD pipelines to {% data variables.product.prodname_actions %} from Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI.
|
||||
|
||||
{% data variables.product.prodname_actions_importer %} is distributed as a Docker container, and uses a [{% data variables.product.prodname_dotcom %} CLI](https://cli.github.com) extension to interact with the container.
|
||||
|
||||
Any workflow that is converted by the {% data variables.product.prodname_actions_importer %} should be inspected for correctness before using it as a production workload. The goal is to achieve an 80% conversion rate for every workflow, however, the actual conversion rate will depend on the makeup of each individual pipeline that is converted.
|
||||
|
||||
## Supported CI platforms
|
||||
|
||||
You can use {% data variables.product.prodname_actions_importer %} to migrate from the following platforms:
|
||||
|
||||
- Azure DevOps
|
||||
- CircleCI
|
||||
- GitLab
|
||||
- Jenkins
|
||||
- Travis CI
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation for each of the supported platforms.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
{% data variables.product.prodname_actions_importer %} has the following requirements:
|
||||
|
||||
- You must have been granted access to the public preview for the {% data variables.product.prodname_actions_importer %}.
|
||||
{%- ifversion ghes < 3.5 or ghae %}
|
||||
- Use a {% data variables.product.pat_generic %} with the `read:packages` scope enabled.
|
||||
{%- else %}
|
||||
- You must have credentials to authenticate to the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}. For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry)."
|
||||
{% endif %}
|
||||
- An environment where you can run Linux-based containers, and can install the necessary tools.
|
||||
- Docker is [installed](https://docs.docker.com/get-docker/) and running.
|
||||
- [{% data variables.product.prodname_dotcom %} CLI](https://cli.github.com) is installed.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The {% data variables.product.prodname_actions_importer %} container and CLI do not need to be installed on the same server as your CI platform.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Installing the {% data variables.product.prodname_actions_importer %} CLI extension
|
||||
|
||||
1. Install the {% data variables.product.prodname_actions_importer %} CLI extension:
|
||||
|
||||
```bash
|
||||
$ gh extension install github/gh-actions-importer
|
||||
```
|
||||
1. Verify that the extension is installed:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer -h
|
||||
Options:
|
||||
-?, -h, --help Show help and usage information
|
||||
|
||||
Commands:
|
||||
update Update to the latest version of the GitHub Actions Importer.
|
||||
version Display the version of the GitHub Actions Importer.
|
||||
configure Start an interactive prompt to configure credentials used to authenticate with your CI server(s).
|
||||
audit Plan your CI/CD migration by analyzing your current CI/CD footprint.
|
||||
forecast Forecast GitHub Actions usage from historical pipeline utilization.
|
||||
dry-run Convert a pipeline to a GitHub Actions workflow and output its yaml file.
|
||||
migrate Convert a pipeline to a GitHub Actions workflow and open a pull request with the changes.
|
||||
```
|
||||
|
||||
### Updating the {% data variables.product.prodname_actions_importer %} CLI
|
||||
|
||||
To ensure you're running the latest version of {% data variables.product.prodname_actions_importer %}, you should regularly run the `update` command:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer update
|
||||
```
|
||||
|
||||
You must be authenticated with the {% data variables.product.prodname_container_registry %} for this command to be successful. Alternatively, you can provide credentials using the `--username` and `--password-stdin` parameters:
|
||||
|
||||
```bash
|
||||
$ echo $GITHUB_TOKEN | gh actions-importer update --username $GITHUB_HANDLE --password-stdin
|
||||
```
|
||||
|
||||
### Authenticating at the command line
|
||||
|
||||
You must configure credentials that allow {% data variables.product.prodname_actions_importer %} to communicate with {% data variables.product.prodname_dotcom %} and your current CI server. You can configure these credentials using environment variables or a `.env.local` file. The environment variables can be configured in an interactive prompt, by running the following command:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer configure
|
||||
```
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation about using environment variables.
|
||||
|
||||
## Using the {% data variables.product.prodname_actions_importer %} CLI
|
||||
|
||||
Use the subcommands of `gh actions-importer` to begin your migration to {% data variables.product.prodname_actions %}, including `audit`, `forecast`, `dry-run`, and `migrate`.
|
||||
|
||||
### Auditing your existing CI pipelines
|
||||
|
||||
The `audit` subcommand can be used to plan your CI/CD migration by analyzing your current CI/CD footprint. This analysis can be used to plan a timeline for migrating to {% data variables.product.prodname_actions %}.
|
||||
|
||||
To run an audit, use the following command to determine your available options:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer audit -h
|
||||
Description:
|
||||
Plan your CI/CD migration by analyzing your current CI/CD footprint.
|
||||
|
||||
[...]
|
||||
|
||||
Commands:
|
||||
azure-devops An audit will output a list of data used in an Azure DevOps instance.
|
||||
circle-ci An audit will output a list of data used in a CircleCI instance.
|
||||
gitlab An audit will output a list of data used in a GitLab instance.
|
||||
jenkins An audit will output a list of data used in a Jenkins instance.
|
||||
travis-ci An audit will output a list of data used in a Travis CI instance.
|
||||
```
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation about running an audit.
|
||||
|
||||
### Forecasting usage
|
||||
|
||||
The `forecast` subcommand reviews historical pipeline usage to create a forecast of {% data variables.product.prodname_actions %} usage.
|
||||
|
||||
To run a forecast, use the following command to determine your available options:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer forecast -h
|
||||
Description:
|
||||
Forecasts GitHub Actions usage from historical pipeline utilization.
|
||||
|
||||
[...]
|
||||
|
||||
Commands:
|
||||
azure-devops Forecasts GitHub Actions usage from historical Azure DevOps pipeline utilization.
|
||||
jenkins Forecasts GitHub Actions usage from historical Jenkins pipeline utilization.
|
||||
gitlab Forecasts GitHub Actions usage from historical GitLab pipeline utilization.
|
||||
circle-ci Forecasts GitHub Actions usage from historical CircleCI pipeline utilization.
|
||||
travis-ci Forecasts GitHub Actions usage from historical Travis CI pipeline utilization.
|
||||
github Forecasts GitHub Actions usage from historical GitHub pipeline utilization.
|
||||
```
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation about running a forecast.
|
||||
|
||||
### Testing the migration process
|
||||
|
||||
The `dry-run` subcommand can be used to convert a pipeline to its {% data variables.product.prodname_actions %} equivalent, and then write the workflow to your local filesystem.
|
||||
|
||||
To perform a dry run, use the following command to determine your available options:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer dry-run -h
|
||||
Description:
|
||||
Convert a pipeline to a GitHub Actions workflow and output its yaml file.
|
||||
|
||||
[...]
|
||||
|
||||
Commands:
|
||||
azure-devops Convert an Azure DevOps pipeline to a GitHub Actions workflow and output its yaml file.
|
||||
circle-ci Convert a CircleCI pipeline to GitHub Actions workflows and output the yaml file(s).
|
||||
gitlab Convert a GitLab pipeline to a GitHub Actions workflow and output the yaml file.
|
||||
jenkins Convert a Jenkins job to a GitHub Actions workflow and output its yaml file.
|
||||
travis-ci Convert a Travis CI pipeline to a GitHub Actions workflow and output its yaml file.
|
||||
```
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation about performing a dry run.
|
||||
|
||||
### Migrating a pipeline to {% data variables.product.prodname_actions %}
|
||||
|
||||
The `migrate` subcommand can be used to convert a pipeline to its GitHub Actions equivalent and then create a pull request with the contents.
|
||||
|
||||
To run a migration, use the following command to determine your available options:
|
||||
|
||||
```bash
|
||||
$ gh actions-importer migrate -h
|
||||
Description:
|
||||
Convert a pipeline to a GitHub Actions workflow and open a pull request with the changes.
|
||||
|
||||
[...]
|
||||
|
||||
Commands:
|
||||
azure-devops Convert an Azure DevOps pipeline to a GitHub Actions workflow and open a pull request with the changes.
|
||||
circle-ci Convert a CircleCI pipeline to GitHub Actions workflows and open a pull request with the changes.
|
||||
gitlab Convert a GitLab pipeline to a GitHub Actions workflow and open a pull request with the changes.
|
||||
jenkins Convert a Jenkins job to a GitHub Actions workflow and open a pull request with the changes.
|
||||
travis-ci Convert a Travis CI pipeline to a GitHub Actions workflow and and open a pull request with the changes.
|
||||
```
|
||||
|
||||
Once you are granted access to the preview, you will be able to access further reference documentation about running a migration.
|
||||
|
||||
## Legal notice
|
||||
|
||||
Portions have been adapted from https://github.com/github/gh-actions-importer/ under the MIT license:
|
||||
|
||||
```
|
||||
MIT License
|
||||
|
||||
Copyright (c) 2022 GitHub
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||
of this software and associated documentation files (the "Software"), to deal
|
||||
in the Software without restriction, including without limitation the rights
|
||||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||
copies of the Software, and to permit persons to whom the Software is
|
||||
furnished to do so, subject to the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be included in all
|
||||
copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
||||
SOFTWARE.
|
||||
```
|
||||
@@ -0,0 +1,70 @@
|
||||
---
|
||||
title: Privately reporting a security vulnerability
|
||||
intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Privately reporting
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
|
||||
Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
|
||||
|
||||
Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
|
||||
|
||||
For security researchers, the benefits of using private vulnerability reporting are:
|
||||
- Less frustration, and less time spent trying to figure out how to contact the maintainer.
|
||||
- A smoother process for disclosing and discussing vulnerability details.
|
||||
- The opportunity to discuss vulnerability details privately with repository maintainer.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Privately reporting a security vulnerability
|
||||
|
||||
Security researchers can privately report a security vulnerability to repository maintainers.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click **Report a vulnerability** to open the advisory form.
|
||||
|
||||
|
||||
|
||||
2. Fill in the advisory details form.
|
||||
{% tip %}
|
||||
|
||||
**Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
|
||||
|
||||
1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
|
||||
|
||||
|
||||
|
||||
The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /security-in-github-codespaces
|
||||
- /performing-a-full-rebuild-of-a-container
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 223d3b146d829f129de39b43b51b6ab9e8aef411
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159197'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180803'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using GitHub Copilot in GitHub Codespaces
|
||||
intro: 'You can use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %} by adding the extension.'
|
||||
title: Verwenden von GitHub Copilot in GitHub Codespaces
|
||||
intro: 'Du kannst {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %} verwenden, indem du die Erweiterung hinzufügst.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,8 +13,13 @@ shortTitle: Copilot in Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/using-copilot-in-codespaces
|
||||
- /codespaces/codespaces-reference/using-github-copilot-in-codespaces
|
||||
ms.openlocfilehash: 6615df6930fa8f27dd8f50c4588d8182b8602549
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158725'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
@@ -23,7 +28,7 @@ redirect_from:
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %} in the {% data variables.product.prodname_vscode_shortname %} web client
|
||||
## Verwenden von {% data variables.product.prodname_copilot %} im {% data variables.product.prodname_vscode_shortname %}-Webclient
|
||||
|
||||
{% data reusables.codespaces.copilot-in-vscode %}
|
||||
|
||||
@@ -31,7 +36,7 @@ redirect_from:
|
||||
|
||||
{% vscode %}
|
||||
|
||||
## Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}
|
||||
## Verwenden von {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.codespaces.copilot-in-vscode %}
|
||||
|
||||
@@ -39,57 +44,57 @@ redirect_from:
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Installing {% data variables.product.prodname_copilot %} in your JetBrains IDE
|
||||
## Installieren von {% data variables.product.prodname_copilot %} in deiner JetBrains-IDE
|
||||
|
||||
[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. For more information, see "[About GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot)."
|
||||
[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), ein KI-Paarprogrammierer, kann in jedem Codespace verwendet werden. Weitere Informationen findest du unter [Informationen zu GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot).
|
||||
|
||||
To use {% data variables.product.prodname_copilot %} in a codespace in your JetBrains IDE, install the [{% data variables.product.prodname_copilot %} plugin](https://plugins.jetbrains.com/plugin/17718-github-copilot) from within your codespace.
|
||||
Wenn du {% data variables.product.prodname_copilot %} in einem Codespace in deiner JetBrains-IDE verwenden möchtest, installiere das [{% data variables.product.prodname_copilot %}-Plug-In](https://plugins.jetbrains.com/plugin/17718-github-copilot) in deinem Codespace.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You must install the {% data variables.product.prodname_copilot %} plugin each time you create a new codespace.
|
||||
**Hinweis**: Du musst das {% data variables.product.prodname_copilot %}-Plug-In jedes Mal installieren, wenn du einen neuen Codespace erstellst.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. In the JetBrains client application, open the Settings (Windows/Linux) or Preferences (Mac) dialog box:
|
||||
1. Öffne in der JetBrains-Clientanwendung das Dialogfeld „Einstellungen (Windows/Linux)“ oder „Einstellungen (Mac)“:
|
||||
|
||||
- **Windows/Linux**: Click **File** and then **Settings** (or press <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd>)
|
||||
- **Mac**: Click **JetBrains Client** in the MacOS menu bar, then click **Preferences** (or press <kbd>command</kbd>+<kbd>,</kbd>)
|
||||
- **Windows/Linux**: Klicke auf **Datei** und dann auf **Einstellungen** (oder drücke <kbd>STRG</kbd>+<kbd>ALT</kbd>+<kbd>S</kbd>).
|
||||
- **Mac**: Klicke in der macOS-Menüleiste auf **JetBrains-Client**, und klicke dann auf **Einstellungen** (oder drücke <kbd>Command</kbd>+<kbd>,</kbd>).
|
||||
|
||||
1. In the left-side menu of the Settings/Preferences dialog box, click **Plugins On Host**. Then click the **Marketplace** tab.
|
||||
1. Klicke im linken Menü des Dialogfelds „Einstellungen/Voreinstellungen“ auf **Plug-Ins auf dem Host**. Klicke auf die Registerkarte **Marketplace**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the search box, type "copilot" then click the **Install** button for the {% data variables.product.prodname_copilot %} plugin.
|
||||
1. Gib im Suchfeld „Copilot“ ein, und klicke dann auf die Schaltfläche **Installieren** für das {% data variables.product.prodname_copilot %}-Plug-In.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Accept** on the "Third-Party Plugins Privacy Note" dialog box.
|
||||
1. Click **Restart IDE**.
|
||||
1. Klicke im Dialogfeld „Datenschutzhinweis für Plug-Ins von Drittanbietern“ auf **Akzeptieren**.
|
||||
1. Klicke auf **IDE neu starten**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Restart** when prompted to confirm that you want to restart the backend IDE that's running remotely. The JetBrains client application will close when you do this.
|
||||
1. Open the codespace again from the JetBrains Gateway application. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide#opening-a-codespace-in-your-jetbrains-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 %}**.
|
||||
1. Klicke auf **Neu starten**, wenn du aufgefordert wirst, zu bestätigen, dass du die Remoteausführung der Back-End-IDE neu starten möchtest. Die JetBrains-Clientanwendung wird geschlossen, wenn du dies tust.
|
||||
1. Öffne den Codespace erneut über die JetBrains Gateway-Anwendung. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} in deiner JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide#opening-a-codespace-in-your-jetbrains-ide).
|
||||
1. Klicke nach dem Neustart deiner JetBrains-IDE auf das Menü **Extras**. Klicke auf **{% data variables.product.prodname_copilot %}** und dann auf **Anmelden bei {% data variables.product.prodname_dotcom %}** .
|
||||
|
||||
|
||||
|
||||
|
||||
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**.
|
||||
1. Um den Gerätecode zu kopieren und das Geräteaktivierungsfenster zu öffnen, klicke im Dialogfeld „Anmelden bei {% data variables.product.prodname_dotcom %}“ auf **Kopieren und öffnen**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
1. Ein Geräteaktivierungsfenster wird in deinem Browser geöffnet. Füge den Gerätecode ein, und klicke dann auf **Weiter**.
|
||||
|
||||
- To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
|
||||
- To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
|
||||
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**.
|
||||
- Um den Code in Windows oder Linux einzufügen, drücke<kbd>STRG</kbd>+<kbd>V</kbd>.
|
||||
- Um den Code in macOS einzufügen, drücke <kbd>BEFEHLSTASTE</kbd>+<kbd>V</kbd>.
|
||||
1. {% data variables.product.prodname_dotcom %} fordert die notwendigen Berechtigungen für {% data variables.product.prodname_copilot %} an. Um diese Berechtigungen zu genehmigen, klicke auf **{% data variables.product.prodname_copilot %}-Plug-In autorisieren**.
|
||||
1. Nach Genehmigung der Berechtigungen zeigt deine JetBrains-IDE eine Bestätigung an. Klicke zum Verwenden von {% data variables.product.prodname_copilot %} auf **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
## Weitere nützliche Informationen
|
||||
|
||||
- "[Getting started with GitHub Copilot in a JetBrains IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide)"
|
||||
- [Erste Schritte mit GitHub Copilot in einer JetBrains-IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide)
|
||||
|
||||
{% endjetbrains %}
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -0,0 +1,72 @@
|
||||
---
|
||||
title: Verwenden des GitHub Codespaces-Plug-Ins für JetBrains
|
||||
shortTitle: Plugin for JetBrains
|
||||
intro: 'Du kannst das {% data variables.product.prodname_github_codespaces %}-Plug-In für die JetBrains-Clientanwendung verwenden, um mehr über deinen Codespace zu erfahren oder diesen zu beenden, wenn du mit der Arbeit fertig bist.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: 8ffd48856a2653f3db3c871122d3acd23c246d7a
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159609'
|
||||
---
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
## Informationen zum {% data variables.product.prodname_github_codespaces %}-Plug-In
|
||||
|
||||
Die JetBrains-Clientanwendung wird gestartet, wenn du eine Verbindung mit einem Codespace in der JetBrains Gateway-Anwendung herstellst. Mit dieser Anwendung kannst du {% data variables.product.prodname_github_codespaces %} mit deiner bevorzugten JetBrains-IDE verwenden. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} in deiner JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide).
|
||||
|
||||
Das {% data variables.product.prodname_github_codespaces %}-Plug-In ist bereits im JetBrains-Client installiert, wenn du über JetBrains Gateway eine Verbindung mit einem Codespace herstellst. Das Plug-In fügt der Benutzeroberfläche das {% data variables.product.prodname_github_codespaces %}-Toolfenster hinzu.
|
||||
|
||||
Klicke unten links im Anwendungsfenster des JetBrains-Clients auf **{% data variables.product.prodname_github_codespaces %}** , um das {% data variables.product.prodname_github_codespaces %}-Toolfenster zu öffnen.
|
||||
|
||||
|
||||
|
||||
## Verwenden des {% data variables.product.prodname_github_codespaces %}-Toolfensters
|
||||
|
||||
Im {% data variables.product.prodname_github_codespaces %}-Toolfenster wird Folgendes angezeigt:
|
||||
* Das Repository, über das du den betreffenden Codespace erstellt hast
|
||||
* Der Anzeigename des Codespace
|
||||
* Der aktuelle Branch
|
||||
* Die Computerspezifikationen
|
||||
* Der Zeitraum, für den der betreffende Codespace im Leerlauf bleiben kann, bis er automatisch beendet wird
|
||||
* Das Alter des Codespace
|
||||
* Der Zeitraum, für den ein beendeter Codespace beibehalten wird, bevor er automatisch gelöscht wird
|
||||
|
||||
Die Symbole oben im {% data variables.product.prodname_github_codespaces %}-Toolfenster verfügen über die folgenden Funktionen.
|
||||
|
||||
* **Aktualisieren des aktiven Codespace**
|
||||
|
||||
|
||||
|
||||
Hier aktualisierst du die Details im {% data variables.product.prodname_github_codespaces %}-Toolfenster. Wenn du beispielsweise über die {% data variables.product.prodname_cli %} den Anzeigenamen geändert hast, kannst du auf diese Schaltfläche klicken, um den neuen Namen anzuzeigen.
|
||||
|
||||
* **Trennen und Beenden**
|
||||
|
||||
|
||||
|
||||
Hier beendest du den Codespace und die Back-End-IDE auf dem Remotecomputer und schließt den lokalen JetBrains-Client.
|
||||
|
||||
* **Verwalten deiner Codespaces aus dem Web**
|
||||
|
||||
|
||||
|
||||
Öffne deine Codespace-Liste unter https://github.com/codespaces.
|
||||
|
||||
* **Anzeigen des Codespace-Erstellungsprotokolls**
|
||||
|
||||
|
||||
|
||||
Öffne das Codespace-Erstellungsprotokoll im Editor-Fenster. Weitere Informationen findest du unter „[{% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs)“.
|
||||
|
||||
* **Neuerstellen des Entwicklungscontainers**
|
||||
|
||||
|
||||
|
||||
Erstelle deinen Codespace neu, um Änderungen anzuwenden, die du an der Entwicklungscontainerkonfiguration vorgenommen hast. Der JetBrains-Client wird geschlossen, und du musst den Codespace erneut öffnen. Weitere Informationen findest du unter [Der Codespace-Lebenszyklus](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace).
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Personalizing GitHub Codespaces for your account
|
||||
title: Personalisieren von GitHub Codespaces für dein Konto
|
||||
shortTitle: Personalize your codespaces
|
||||
intro: 'You can personalize {% data variables.product.prodname_github_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
|
||||
intro: 'Du kannst {% data variables.product.prodname_github_codespaces %} personalisieren, indem du ein `dotfiles`-Repository in {% data variables.product.product_name %} oder die Einstellungssynchronisierung verwendest.'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
|
||||
- /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
|
||||
@@ -15,39 +15,43 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 80b6cd1ee982150c1b3c0a66e1247f6098a97bcb
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160257'
|
||||
---
|
||||
## Informationen zur Personalisierung von {% data variables.product.prodname_codespaces %}
|
||||
|
||||
Bei Verwendung einer Entwicklungsumgebung ist das Anpassen der Einstellungen und Tools an deine Präferenzen und Workflows ein wichtiger Schritt. In {% data variables.product.prodname_github_codespaces %} gibt es zwei mögliche Hauptmethoden zur Personalisierung deiner Codespaces.
|
||||
|
||||
## About personalizing {% data variables.product.prodname_codespaces %}
|
||||
- [Einstellungssynchronisierung](#settings-sync): Du kannst deine {% data variables.product.prodname_vscode %}-Einstellungen zwischen der Desktopanwendung und dem {% data variables.product.prodname_vscode_shortname %}-Webclient synchronisieren.
|
||||
- [Dotfiles:](#dotfiles) Du kannst ein `dotfiles`-Repository verwenden, um Skripts, Shelleinstellungen und andere Konfigurationen anzugeben.
|
||||
|
||||
When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_github_codespaces %} allows for two main ways of personalizing your codespaces.
|
||||
Die Personalisierung von {% data variables.product.prodname_github_codespaces %} gilt für alle Codespaces, die du erstellst.
|
||||
|
||||
- [Settings Sync](#settings-sync) - You can synchronize your {% data variables.product.prodname_vscode %} settings between the desktop application and the {% data variables.product.prodname_vscode_shortname %} web client.
|
||||
- [Dotfiles](#dotfiles) – You can use a `dotfiles` repository to specify scripts, shell preferences, and other configurations.
|
||||
Projektbetreuer können auch eine Standardkonfiguration definieren, die für jeden Codespace eines Repositorys gilt, egal wer ihn erstellt. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} personalization applies to any codespace you create.
|
||||
## Einstellungssynchronisierung
|
||||
|
||||
Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
Mit der Einstellungssynchronisierung kannst du Konfigurationen wie Einstellungen, Tastenkombinationen, Codeschnipsel, Erweiterungen und Benutzeroberflächenstatus zwischen verschiedenen Computern und {% data variables.product.prodname_vscode_shortname %}-Instanzen synchronisieren.
|
||||
|
||||
## Settings Sync
|
||||
Klicke zum Aktivieren der Einstellungssynchronisierung in der linken unteren Ecke der Aktivitätsleiste in {% data variables.product.prodname_vscode %} auf {% octicon "gear" aria-label="The gear icon" %} und anschließend auf **Turn on Settings Sync…** (Einstellungssynchronisierung aktivieren...). Wähle im Dialogfeld die Einstellungen aus, die du synchronisieren möchtest.
|
||||
|
||||
Settings Sync allows you to synchronize configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
|
||||
To enable Settings Sync, in the bottom-left corner of {% data variables.product.prodname_vscode %}'s Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
|
||||
|
||||
|
||||
|
||||
For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Weitere Informationen findest du in der [Anleitung für die Einstellungssynchronisierung](https://code.visualstudio.com/docs/editor/settings-sync) in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation.
|
||||
|
||||
## Dotfiles
|
||||
|
||||
Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your dotfiles repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
|
||||
Dotfiles sind Dateien und Ordner auf UNIX-ähnlichen Systemen, die mit `.` beginnen und von denen die Konfiguration von Anwendungen und Shells auf deinem System gesteuert wird. Du kannst deine 'dotfiles' in einem Repository auf {% data variables.product.prodname_dotcom %} speichern und verwalten. Empfehlungen und Tutorials hinsichtlich der Frage, welche Elemente du in dein Dotfiles-Repository aufnehmen solltest, findest du unter [GitHub und Dotfiles](https://dotfiles.github.io/).
|
||||
|
||||
Your dotfiles repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
|
||||
Dein Dotfiles-Repository könnte Shell-Aliase und -Voreinstellungen beinhalten, sämtliche Werkzeuge, die du installieren möchtest, oder jede andere Codespace-Personalisierung, die du vornehmen möchtest.
|
||||
|
||||
You can configure {% data variables.product.prodname_github_codespaces %} to use dotfiles from any repository you own by selecting that repository in your [personal {% data variables.product.prodname_github_codespaces %} settings](https://github.com/settings/codespaces).
|
||||
Du kannst {% data variables.product.prodname_github_codespaces %} so konfigurieren, dass Dotfiles aus einem beliebigen Repository verwendet werden, das du besitzt, indem du das betreffende Repository in deinen [persönlichen {% data variables.product.prodname_github_codespaces %}-Einstellungen](https://github.com/settings/codespaces) auswählst.
|
||||
|
||||
When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your selected dotfiles repository to the codespace environment, and looks for one of the following files to set up the environment.
|
||||
Wenn du einen neuen Codespace erstellst, wird das ausgewählte Dotfilerepository von {% data variables.product.prodname_dotcom %} in die Codespaceumgebung geklont. Außerdem wird zum Einrichten der Umgebung nach einer der folgenden Dateien gesucht.
|
||||
|
||||
* _install.sh_
|
||||
* _install_
|
||||
@@ -58,48 +62,47 @@ When you create a new codespace, {% data variables.product.prodname_dotcom %} cl
|
||||
* _setup_
|
||||
* _script/setup_
|
||||
|
||||
If none of these files are found, then any files or folders in your selected dotfiles repository starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
|
||||
Wenn keine dieser Dateien gefunden wird, werden alle Dateien oder Ordner in deinem ausgewählten Dotfiles-Repository, die mit `.` beginnen, per Symlink mit dem Verzeichnis `~` oder `$HOME` des Codespaces verknüpft.
|
||||
|
||||
Any changes to your selected dotfiles repository will apply only to each new codespace, and do not affect any existing codespace.
|
||||
Am ausgewählten Dotfiles-Repository vorgenommene Änderungen gelten nur für neue Codespaces und wirken sich nicht auf bestehende Codespaces aus.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the User-scoped settings for {% data variables.product.prodname_vscode_shortname %} with your `dotfiles` repository. You can set default Workspace and Remote [Codespaces] settings for a specific project in the project's repository. For more information, see "[Introduction to dev containers](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
|
||||
**Hinweis:** Derzeit bietet {% data variables.product.prodname_codespaces %} keine Unterstützung für die Personalisierung der Benutzereinstellungen für {% data variables.product.prodname_vscode_shortname %} über dein `dotfiles`-Repository. Du kannst Standardeinstellungen für Workspace (Arbeitsbereich) und Remote [Codespaces] für ein bestimmtes Projekt im Repository des Projekts festlegen. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %}
|
||||
### Aktivieren des Dotfiles-Repositorys für {% data variables.product.prodname_codespaces %}
|
||||
|
||||
You can use your selected dotfiles repository to personalize your {% data variables.product.prodname_github_codespaces %} environment. Once you choose your dotfiles repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_github_codespaces %} settings page.
|
||||
Du kannst dein ausgewähltes Dotfilerepository verwenden, um deine {% data variables.product.prodname_github_codespaces %}-Umgebung zu personalisieren. Nachdem du dein Dotfiles-Repository ausgewählt hast, kannst du deine Skripts, Einstellungen und Konfigurationen hinzufügen. Anschließend musst du deine Dotfiles über deine persönliche {% data variables.product.prodname_github_codespaces %}-Einstellungsseite aktivieren.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
|
||||
**Warnung:** Von Dotfiles können beliebige Skripts ausgeführt werden, die unerwarteten oder böswilligen Code enthalten können. Es wird empfohlen, Skripts vor dem Installieren eines Dotfiles-Repositorys zu überprüfen und so sicherzustellen, dass von den Skripts keine unerwarteten Aktionen ausgeführt werden.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.codespaces-tab %}
|
||||
1. Under "Dotfiles", select **Automatically install dotfiles** so that {% data variables.product.prodname_github_codespaces %} automatically installs your dotfiles into every new codespace you create.
|
||||
|
||||
2. Choose the repository you want to install dotfiles from.
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %}
|
||||
1. Wähle unter „Dotfiles“ die Option **Dotfiles automatisch installieren** aus, damit {% data variables.product.prodname_github_codespaces %} deine Dotfiles automatisch in jedem neuen Codespace installiert, den du erstellst.
|
||||
|
||||
2. Wähle das Repository aus, aus dem du Dotfiles installieren möchtest.
|
||||
|
||||
|
||||
You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces.
|
||||
Du kannst dem Dotfiles-Repository weitere Skripts, Einstellungen und Konfigurationsdateien hinzufügen oder vorhandene Dateien bearbeiten, wann immer du dies möchtest. An Einstellungen vorgenommene Änderungen werden nur von neuen Codespaces übernommen.
|
||||
|
||||
If your codespace fails to pick up configuration settings from dotfiles, see "[Troubleshooting dotfiles for {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces)."
|
||||
Wenn dein Codespace die Konfigurationseinstellungen aus Dotfiles nicht übernimmt, findest du weiterführende Informationen unter [Behandeln von Problemen mit Dotfiles für {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces).
|
||||
|
||||
## Other available settings
|
||||
## Andere verfügbare Einstellungen
|
||||
|
||||
You can also personalize {% data variables.product.prodname_github_codespaces %} using additional options in [your personal settings](https://github.com/settings/codespaces):
|
||||
Du kannst {% data variables.product.prodname_github_codespaces %} auch mithilfe zusätzlicher Optionen in [deinen persönlichen Einstellungen](https://github.com/settings/codespaces) personalisieren:
|
||||
|
||||
- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)."
|
||||
- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
- To set how long a codespace can remain unused before it is automatically stopped, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
- To set the period for which your unused codespaces are retained, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
- To set your default region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
|
||||
- Informationen zum Aktivieren der GPG-Überprüfung findest du unter [Verwalten der GPG-Überprüfung für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces).
|
||||
- Informationen zum Festlegen deines Editors findest du unter [Festlegen deines Standard-Editors für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces).
|
||||
- Informationen zum Festlegen des Zeitraums, für den ein Codespace ungenutzt bleiben kann, bevor er automatisch beendet wird, findest du unter [Festlegen des Timeoutzeitraums für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces).
|
||||
- Informationen zum Festlegen des Zeitraums, für den deine nicht verwendeten Codespaces beibehalten werden, findest du unter [Konfigurieren des automatischen Löschens deiner Codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces).
|
||||
- Informationen zum Festlegen deiner Standardregion findest du unter [Festlegen deiner Standardregion für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces).
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
|
||||
* "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)"
|
||||
* [Erstellen eines neuen Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)
|
||||
* [Ausführliche Informationen zu {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Setting your default editor for GitHub Codespaces
|
||||
title: Festlegen deines Standard-Editors für GitHub Codespaces
|
||||
shortTitle: Set the default editor
|
||||
intro: '{% data reusables.codespaces.about-changing-default-editor %}'
|
||||
versions:
|
||||
@@ -11,40 +11,44 @@ redirect_from:
|
||||
topics:
|
||||
- Codespaces
|
||||
type: how_to
|
||||
ms.openlocfilehash: 5c286ffe8f96d275dc0b20949a87b7ced411c9af
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159606'
|
||||
---
|
||||
|
||||
On the settings page, you can set your editor preference so that when you create a codespace, or open an existing codespace, it is opened in your choice of:
|
||||
* {% data variables.product.prodname_vscode %} (desktop application)
|
||||
* {% data variables.product.prodname_vscode %} (web client application)
|
||||
* JetBrains Gateway - for opening codespaces in a JetBrains IDE
|
||||
* JupyterLab - the web interface for Project Jupyter
|
||||
Auf der Einstellungsseite kannst du deine Editor-Einstellungen so festlegen, dass Codespaces beim Erstellen eines Codespace oder Öffnen eines bereits vorhandenen Codespace in der gewünschten der folgenden Anwendungen geöffnet werden:
|
||||
* {% data variables.product.prodname_vscode %} (Desktopanwendung)
|
||||
* {% data variables.product.prodname_vscode %} (Webclientanwendung)
|
||||
* JetBrains Gateway: Zum Öffnen von Codespaces in einer JetBrains-IDE
|
||||
* JupyterLab: Die Webschnittstelle von Project Jupyter
|
||||
|
||||
{% data reusables.codespaces.template-codespaces-default-editor %}
|
||||
|
||||
If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_github_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
|
||||
Wenn du {% data variables.product.prodname_vscode %} als Standard-Editor für {% data variables.product.prodname_github_codespaces %} verwenden möchtest, musst du {% data variables.product.prodname_vscode %} und die {% data variables.product.prodname_github_codespaces %}-Erweiterung für {% data variables.product.prodname_vscode %} installieren. Weitere Informationen findest du auf der [Downloadseite für {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) und die [{% data variables.product.prodname_github_codespaces %}-Erweiterung im {% data variables.product.prodname_vscode %}-Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
|
||||
|
||||
If you want to work on a codespace in a JetBrains IDE you must install the JetBrains Gateway. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
Wenn du an einem Codespace in einer JetBrains-IDE arbeiten möchtest, musst du JetBrains Gateway installieren. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} in deiner JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide).
|
||||
|
||||
## Setting your default editor
|
||||
## Festlegen deines Standard-Editors
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.codespaces-tab %}
|
||||
1. Under "Editor preference", select the option you want.
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %}
|
||||
1. Wähle unter „Editor-Einstellung“ die gewünschte Option aus.
|
||||
|
||||
|
||||
|
||||
|
||||
* {% data reusables.codespaces.application-installed-locally %}<br><br>
|
||||
|
||||
* If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_github_codespaces %} will automatically open in the desktop application when you next create or open a codespace.
|
||||
* Wenn du **{% data variables.product.prodname_vscode %}** auswählst, wird {% data variables.product.prodname_github_codespaces %} automatisch in der Desktopanwendung geöffnet, wenn du das nächste Mal einen Codespace erstellst oder öffnest.
|
||||
|
||||
You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.<br><br>
|
||||
Möglicherweise musst du den Zugriff sowohl auf deinen Browser als auch auf {% data variables.product.prodname_vscode %} zulassen, damit der Editor erfolgreich geöffnet werden kann.<br><br>
|
||||
|
||||
* If you choose **JetBrains Gateway**, the Gateway application will automatically open when you next create or open a codespace.
|
||||
* Wenn du **JetBrains Gateway** auswählst, wird automatisch die Gateway-Anwendung geöffnet, wenn du das nächste Mal einen Codespace erstellst oder öffnest.
|
||||
|
||||
The first time you open a codespace this way you must give permission to open the application.
|
||||
Beim ersten Öffnen eines Codespace auf diese Weise musst du die Berechtigung zum Öffnen der Anwendung erteilen.
|
||||
|
||||
The Gateway application will open and the codespace will then be automatically selected. You can then choose a JetBrains IDE, if you have not previously done so, and click **Connect** to open the codespace in the JetBrains client. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
Die Gateway-Anwendung wird geöffnet, und der Codespace wird dann automatisch ausgewählt. Anschließend kannst du eine JetBrains-IDE auswählen (sofern noch nicht geschehen) und auf **Verbinden** klicken, um den Codespace im JetBrains-Client zu öffnen. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} in deiner JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide).
|
||||
|
||||
To connect to a codespace from the Gateway application, you must have an SSH server running on the codespace. {% indented_data_reference reusables.codespaces.ssh-server-installed spaces=5 %}
|
||||
Damit über die Gateway-Anwendung eine Verbindung mit einem Codespace hergestellt werden kann, muss in dem Codespace ein SSH-Server ausgeführt werden. {% indented_data_reference reusables.codespaces.ssh-server-installed spaces=5 %}
|
||||
|
||||
* If you choose **JupyterLab**, the JupyterLab application must be installed in the codespaces you open. {% data reusables.codespaces.jupyterlab-in-default-image %}
|
||||
* Wenn du **JupyterLab** auswählst, muss in den von dir geöffneten Codespaces die JupyterLab-Anwendung installiert sein. {% data reusables.codespaces.jupyterlab-in-default-image %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Setting your timeout period for GitHub Codespaces
|
||||
title: Festlegen des Timeoutzeitraums für GitHub Codespaces
|
||||
shortTitle: Set the timeout
|
||||
intro: 'You can set your default timeout for {% data variables.product.prodname_github_codespaces %} in your personal settings page.'
|
||||
intro: 'Du kannst dein Standardtimeout für {% data variables.product.prodname_github_codespaces %} auf der Seite mit deinen persönlichen Einstellungen festlegen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,53 +10,57 @@ topics:
|
||||
type: how_to
|
||||
redirect_from:
|
||||
- /codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces
|
||||
ms.openlocfilehash: 6ca559fefddc34eb6de0441d17344ff8054db509
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159605'
|
||||
---
|
||||
## Informationen zum Leerlauftimeout
|
||||
|
||||
## About the idle timeout
|
||||
|
||||
A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create, or to existing codespaces the next time you start them. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
|
||||
Ein Codespace wird nach einem Inaktivitätszeitraum beendet. Standardmäßig beträgt dieser Zeitraum 30 Minuten. Du kannst jedoch einen längeren oder kürzeren Standardtimeoutzeitraum in deinen persönlichen Einstellungen für {% data variables.product.prodname_dotcom %} angeben. Die aktualisierte Einstellung gilt für alle neuen Codespaces, die du erstellst, oder für vorhandene Codespaces, wenn du sie das nächste Mal startest. Du kannst auch ein Timeout angeben, wenn du {% data variables.product.prodname_cli %} verwendest, um einen Codespace zu erstellen.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
**Warnung**: Die Computenutzung von Codespaces wird für die Dauer abgerechnet, für die ein Codespace aktiv ist. Wenn du keinen Codespace verwendest, er aber weiterhin ausgeführt wird und noch kein Timeout aufgetreten ist, wird dir die Gesamtzeit in Rechnung gestellt, in der der Codespace aktiv war, unabhängig davon, ob du ihn verwendet hast. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing).
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Timeout periods for organization-owned repositories
|
||||
### Timeoutzeiträume für organisationseigene Repositorys
|
||||
|
||||
Organizations can set a maximum idle timeout policy for codespaces created from some or all of their repositories. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting. You will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
Organisationen können eine maximale Leerlauftimeoutrichtlinie für Codespaces festlegen, die aus einigen oder allen eigenen Repositorys erstellt wurden. Wenn eine Organisationsrichtlinie ein maximales Timeout festlegt, das unter dem von dir festgelegten Standardtimeout liegt, wird anstelle deiner Einstellung das Timeout der Organisation verwendet. Du wirst darüber benachrichtigt, nachdem der Codespace erstellt wurde. Weitere Informationen findest du unter [Einschränken des Zeitraums für Leerlauftimeouts](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period).
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Setting your default timeout period
|
||||
## Festlegen des standardmäßigen Timeoutzeitraums
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.codespaces-tab %}
|
||||
1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %}
|
||||
1. Gib unter „Standard-Leerlauftimeout“ die gewünschte Zeit ein, und klicke dann auf **Speichern**. Die Zeit muss zwischen 5 Minuten und 240 Minuten (4 Stunden) liegen.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
## Setting the timeout period for a codespace
|
||||
## Festlegen des Timeoutzeitraums für einen Codespace
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To set the timeout period when you create a codespace, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (4 hours).
|
||||
Um den Timeoutzeitraum festzulegen, wenn du einen Codespace erstellst, verwende das `idle-timeout`-Argument mit dem `codespace create`-Unterbefehl. Gib die Zeit in Minuten an, gefolgt von `m`. Die Zeit muss zwischen 5 Minuten und 240 Minuten (4 Stunden) liegen.
|
||||
|
||||
```shell
|
||||
gh codespace create --idle-timeout 90m
|
||||
```
|
||||
|
||||
If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through {% data variables.product.prodname_cli %}.
|
||||
Wenn du keinen Timeoutzeitraum angibst, wenn du einen Codespace erstellst, wird der Standard-Timeoutzeitraum verwendet. Informationen zum Festlegen eines Standard-Timeoutzeitraums findest du auf dieser Seite auf der Registerkarte „Webbrowser“. Du kannst derzeit keinen Standard-Timeoutzeitraum über {% data variables.product.prodname_cli %} angeben.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
## Setting a timeout period
|
||||
## Festlegen eines Timeoutzeitraums
|
||||
|
||||
You can set your default timeout period in your web browser, on {% data variables.product.prodname_dotcom_the_website %}. Alternatively, if you use {% data variables.product.prodname_cli %} to create a codespace you can set a timeout period for that particular codespace. For more information, click the appropriate tab above.
|
||||
Du kannst auf {% data variables.product.prodname_dotcom_the_website %} deinen standardmäßigen Timeoutzeitraum in deinem Webbrowser festlegen. Wenn du alternativ {% data variables.product.prodname_cli %} verwendest, um einen Codespace zu erstellen, kannst du einen Timeoutzeitraum für diesen bestimmten Codespace festlegen. Weitere Informationen erhältst du, wenn du oben auf die entsprechende Registerkarte klickst.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deleting a codespace
|
||||
intro: You can delete a codespace you no longer need.
|
||||
title: Einen Codespace löschen
|
||||
intro: 'Du kannst einen Codespace löschen, wenn du ihn nicht länger benötigst.'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/deleting-a-codespace
|
||||
- /github/developing-online-with-codespaces/deleting-a-codespace
|
||||
@@ -13,28 +13,33 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Delete a codespace
|
||||
ms.openlocfilehash: c9f1f6eb407c985d8981504de28e39a4bf742f7a
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158661'
|
||||
---
|
||||
|
||||
You can delete a codespace in a variety of ways: in the terminal by using {% data variables.product.prodname_cli %}, in {% data variables.product.prodname_vscode %}, or in your web browser. Use the tabs in this article to display instructions for each of these ways of deleting a codespace.
|
||||
Es gibt verschiedene Möglichkeiten, einen Codespace zu löschen: im Terminal mithilfe der {% data variables.product.prodname_cli %}, in {% data variables.product.prodname_vscode %} oder in deinem Webbrowser. Verwende die Registerkarten in diesem Artikel, um Anweisungen für jede dieser Methoden zum Löschen eines Codespace anzuzeigen.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab.
|
||||
**Hinweis:** Du kannst einen Codespace nicht in der JetBrains Gateway-Instanz, der JetBrains-Clientanwendung oder in JupyterLab löschen.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
Für das Speichern von Codespaces entstehen Kosten. Du solltest daher alle Codespaces löschen, die du nicht mehr benötigst. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %}
|
||||
|
||||
## Deleting a codespace
|
||||
## Einen Codespace löschen
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete**
|
||||
1. Klicke rechts neben dem Codespace, den du löschen möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **{% octicon "trash" aria-label="The trash icon" %} Löschen**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -49,48 +54,48 @@ There are costs associated with storing codespaces. You should therefore delete
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed.
|
||||
Um einen Codespace zu löschen, verwende den Unterbefehl `gh codespace delete`, und wähle dann einen Codespace aus der angezeigten Liste aus.
|
||||
|
||||
```shell
|
||||
gh codespace delete
|
||||
```
|
||||
|
||||
If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `--force` flag to force deletion, avoiding this prompt.
|
||||
Falls noch nicht gespeicherte Änderungen vorliegen, wirst du aufgefordert, den Löschvorgang zu bestätigen. Du kannst das Löschen mit dem Flag `--force` erzwingen, um diese Aufforderung zu vermeiden.
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete).
|
||||
Weitere Informationen zu diesem Befehl findest du im [{% data variables.product.prodname_cli %}-Leitfaden](https://cli.github.com/manual/gh_codespace_delete).
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Bulk deleting codespaces
|
||||
## Massenlöschen von Codespaces
|
||||
|
||||
{% webui %}
|
||||
|
||||
You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
Du kannst {% data variables.product.prodname_cli %} verwenden, um mehrere oder alle deine Codespaces mit einem einzigen Befehl zu löschen. Weitere Informationen findest du auf der Registerkarte „{% data variables.product.prodname_cli %}“ im oberen Bereich dieser Seite.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
Du kannst {% data variables.product.prodname_cli %} verwenden, um mehrere oder alle deine Codespaces mit einem einzigen Befehl zu löschen. Weitere Informationen findest du auf der Registerkarte „{% data variables.product.prodname_cli %}“ im oberen Bereich dieser Seite.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
|
||||
{% cli %}
|
||||
|
||||
You can delete several or all of your codespaces with a single command, using `gh codespace delete` followed by one of these flags:
|
||||
Du kannst mehrere oder alle deine Codespaces mit einem einzigen Befehl löschen, indem du `gh codespace delete` gefolgt von einem dieser Flags verwendest:
|
||||
|
||||
`--all` - Delete all of your codespaces.
|
||||
`--all`: Löscht alle Codespaces.
|
||||
|
||||
`--repo REPOSITORY` - Delete all of your codespaces for this repository. Or use together with the `--days` flag to filter by age of the codespace.
|
||||
`--repo REPOSITORY`: Löscht alle Codespaces für dieses Repository. Alternativ kannst du mit dem Flag `--days` nach dem Alter des Codespace filtern.
|
||||
|
||||
`--days NUMBER` - Delete all of your codespaces that are older than the specified number of days. Can be used together with the `--repo` flag.
|
||||
`--days NUMBER`: Löscht alle Codespaces, deren Alter die angegebene Anzahl von Tagen überschreitet. Kann zusammen mit dem Flag `--repo` verwendet werden.
|
||||
|
||||
By default you are prompted to confirm deletion of any codespaces that contain unsaved changes. You can use the `--force` flag to skip this confirmation.
|
||||
Standardmäßig wirst du aufgefordert, das Löschen aller Codespaces zu bestätigen, die nicht gespeicherte Änderungen enthalten. Du kannst das Flag `--force` verwenden, um diese Bestätigung zu überspringen.
|
||||
|
||||
### Example
|
||||
### Beispiel
|
||||
|
||||
Delete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago.
|
||||
Lösche alle Codespaces für das Repository `octo-org/octo-repo`, die du vor mehr als 7 Tagen erstellt hast.
|
||||
|
||||
```
|
||||
gh codespace delete --repo octo-org/octo-repo --days 7
|
||||
@@ -98,37 +103,37 @@ gh codespace delete --repo octo-org/octo-repo --days 7
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Deleting codespaces in your organization
|
||||
## Löschen der Codespaces in deiner Organisation
|
||||
|
||||
As an organization owner, you can use {% data variables.product.prodname_cli %} to delete any codespace in your organization.
|
||||
Als Organisationsinhaber*in kannst du {% data variables.product.prodname_cli %} verwenden, um alle Codespaces in deiner Organisation zu löschen.
|
||||
|
||||
{% webui %}
|
||||
|
||||
For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
Weitere Informationen findest du auf der Registerkarte „{% data variables.product.prodname_cli %}“ im oberen Bereich dieser Seite.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
|
||||
Weitere Informationen findest du auf der Registerkarte „{% data variables.product.prodname_cli %}“ im oberen Bereich dieser Seite.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
1. Enter one of these commands to display a list of codespaces.
|
||||
* `gh codespace delete --org ORGANIZATION` - Lists the current codespaces in the specified organization.
|
||||
* `gh codespace delete --org ORGANIZATION --user USER` - Lists only those codespaces created by the specified user.
|
||||
You must be an owner of the specified organization.
|
||||
1. In the list of codespaces, navigate to the codespace you want to delete.
|
||||
1. To delete the selected codespace press <kbd>Enter</kbd>.
|
||||
1. Gib einen dieser Befehle ein, um eine Liste der Codespaces anzuzeigen.
|
||||
* `gh codespace delete --org ORGANIZATION` listet die aktuellen Codespaces in der angegebenen Organisation auf.
|
||||
* `gh codespace delete --org ORGANIZATION --user USER` listet nur die Codespaces auf, die vom angegebenen Benutzer erstellt wurden.
|
||||
Du musst ein Inhaber der angegebenen Organisation sein.
|
||||
1. Navigiere in der Liste der Codespaces zu dem Codespace, den du löschen möchtest.
|
||||
1. Drücke die <kbd>EINGABETASTE</kbd>, um den ausgewählten Codespace zu löschen.
|
||||
|
||||
If the codespace contains unsaved changes you will be prompted to confirm deletion.
|
||||
Wenn der Codespace nicht gespeicherte Änderungen enthält, wirst du aufgefordert, die Löschung zu bestätigen.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
You can also use the REST API to delete codespaces for your organization. For more information, see "[Codespaces organizations](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)."
|
||||
Du kannst auch die REST-API verwenden, um Codespaces für deine Organisation zu löschen. Weitere Informationen findest du unter [Codespaces in Organisationen](/rest/codespaces/organizations#delete-a-codespace-from-the-organization).
|
||||
|
||||
## Further reading
|
||||
- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
|
||||
- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
|
||||
## Weitere Informationsquellen
|
||||
- [Der Codespace-Lebenszyklus](/codespaces/developing-in-codespaces/the-codespace-lifecycle)
|
||||
- [Konfigurieren des automatischen Löschens deiner Codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Forwarding ports in your codespace
|
||||
title: Weiterleiten von Ports in deinem Codespace
|
||||
intro: '{% data reusables.codespaces.about-port-forwarding %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -12,76 +12,77 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Forward ports
|
||||
ms.openlocfilehash: 320a2e42d647452056961d4f0f987c3c5db49476
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158909'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## About forwarded ports
|
||||
## Informationen zu weitergeleiteten Ports
|
||||
|
||||
Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging.
|
||||
Portweiterleitung bietet Zugriff auf TCP-Ports, die innerhalb deines Codespace ausgeführt werden. Wenn du beispielsweise eine Webanwendung auf einem bestimmten Port in deinem Codespace ausführst, kannst du diesen Port weiterleiten. Auf diese Weise kannst du über den Browser auf deinem lokalen Computer zum Testen und Debuggen auf die Anwendung zugreifen.
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Under the list of ports, click **Add port**.
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %} {% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Klicke unter der Liste der Ports auf **Port hinzufügen**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the port number or address, then press enter.
|
||||
1. Gib die Portnummer oder Adresse ein, und drücke die EINGABETASTE.
|
||||
|
||||
|
||||
|
||||
|
||||
## Using HTTPS forwarding
|
||||
## Verwenden der HTTPS-Weiterleitung
|
||||
|
||||
By default, {% data variables.product.prodname_github_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed. If you update a port with public visibility to use HTTPS, the port's visibility will automatically change to private.
|
||||
{% data variables.product.prodname_github_codespaces %} leitet Ports standardmäßig mithilfe von HTTP weiter, aber du kannst alle Ports so aktualisieren, dass bei Bedarf das HTTPS verwendet wird. Wenn du einen Port mit öffentlicher Sichtbarkeit zur Verwendung von HTTPS aktualisierst, wird die Sichtbarkeit des Ports automatisch in „privat“ geändert.
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port you want to update, then hover over **Change Port Protocol**.
|
||||
|
||||
1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
|
||||
1. Klicke mit der rechten Maustaste auf den Port, den du aktualisieren möchtest. Zeige anschließend auf **Portprotokoll ändern**.
|
||||
|
||||
1. Wähle das für diesen Port erforderliche Protokoll aus. Das ausgewählte Protokoll wird für die Lebensdauer des Codespaces für diesen Port gespeichert.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
1. Send the copied URL to the person you want to share the port with.
|
||||
1. Klicke mit der rechten Maustaste auf den Port, den du freigeben möchtest. Zeige dann auf das Menü „Portsichtbarkeit“, und wähle entweder **Privat für Organisation** oder **Öffentlich** aus.
|
||||
|
||||
1. Klicke auf das Kopiersymbol rechts neben der lokalen Adresse für den Port.
|
||||
|
||||
1. Sende die kopierte URL an die Person, für die du den Port freigeben möchtest.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %} {% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Under the list of ports, click **Add port**.
|
||||
{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %} {% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Klicke unter der Liste der Ports auf **Port hinzufügen**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the port number or address, then press enter.
|
||||
1. Gib die Portnummer oder Adresse ein, und drücke die EINGABETASTE.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
1. Send the copied URL to the person you want to share the port with.
|
||||
1. Klicke mit der rechten Maustaste auf den Port, den du freigeben möchtest. Zeige dann auf das Menü „Portsichtbarkeit“, und wähle entweder **Privat für Organisation** oder **Öffentlich** aus.
|
||||
|
||||
1. Klicke auf das Kopiersymbol rechts neben der lokalen Adresse für den Port.
|
||||
|
||||
1. Sende die kopierte URL an die Person, für die du den Port freigeben möchtest.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %} {% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -90,37 +91,37 @@ By default, {% data variables.product.prodname_github_codespaces %} forwards por
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
|
||||
Verwende zum Weiterleiten eines Ports den Unterbefehl `gh codespace ports forward`. Ersetze `codespace-port:local-port` durch den Remoteport und den lokalen Port, mit denen du eine Verbindung herstellen möchtest. Nachdem du den Befehl eingegeben hast, kannst du deine Auswahl in der angezeigten Liste der Codespaces treffen.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward CODESPACE-PORT:LOCAL-PORT
|
||||
```
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
Weitere Informationen zu diesem Befehl findest du im [{% data variables.product.prodname_cli %}-Leitfaden](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
|
||||
To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
|
||||
Gib `gh codespace ports` ein, und wähle dann einen Codespace aus, um Details zu weitergeleiteten Ports anzuzeigen.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %}
|
||||
Verwende den Unterbefehl `gh codespace ports visibility`, um die Sichtbarkeit eines weitergeleiteten Ports zu ändern. {% data reusables.codespaces.port-visibility-settings %}
|
||||
|
||||
Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
|
||||
Ersetze `codespace-port` durch die Nummer des weitergeleiteten Ports. Ersetze `setting` durch `private`, `org` oder `public`. Nachdem du den Befehl eingegeben hast, kannst du deine Auswahl in der angezeigten Liste der Codespaces treffen.
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility CODESPACE-PORT:SETTINGS
|
||||
```
|
||||
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
Du kannst mit einem Befehl die Sichtbarkeit mehrerer Ports festlegen. Beispiel:
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org
|
||||
```
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_visibility).
|
||||
Weitere Informationen zu diesem Befehl findest du im [{% data variables.product.prodname_cli %}-Leitfaden](https://cli.github.com/manual/gh_codespace_ports_visibility).
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
|
||||
|
||||
You can see the port labels when you list the forwarded ports for a codespace. To do this, use the `gh codespace ports` command and then select a codespace.
|
||||
Die Portbezeichnungen werden angezeigt, wenn du die weitergeleiteten Ports für einen Codespace auflistest. Verwende hierfür den Befehl `gh codespace ports`, und wähle dann einen Codespace aus.
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
|
||||
|
||||
@@ -128,10 +129,10 @@ You can see the port labels when you list the forwarded ports for a codespace. T
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Forwarding a port
|
||||
## Weiterleiten eines Ports
|
||||
|
||||
For information on how to forward a port in a codespace to a port on your local machine, see the "Port forwarding" section of the "[Security model](https://www.jetbrains.com/help/idea/security-model.html#port_forwarding)" article in the JetBrains documentation.
|
||||
Informationen zum Weiterleiten eines Ports in einem Codespace an einen Port auf deinem lokalen Computer findest du im Abschnitt „Portweiterleitung“ des Artikels [Security model](https://www.jetbrains.com/help/idea/security-model.html#port_forwarding) (Sicherheitsmodell) in der JetBrains-Dokumentation.
|
||||
|
||||
Alternatively, you can use {% data variables.product.prodname_cli %} to forward a port. For more information, click the "{% data variables.product.prodname_cli %}" tab at the top of this page.
|
||||
Alternativ kannst du {% data variables.product.prodname_cli %} verwenden, um einen Port weiterzuleiten. Klicke auf die Registerkarte „{% data variables.product.prodname_cli %}“ oben auf dieser Seite, um weitere Informationen zu erhalten.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using GitHub Codespaces for pull requests
|
||||
title: Verwenden von GitHub Codespaces für Pull Requests
|
||||
shortTitle: Pull requests
|
||||
intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your web browser, or in {% data variables.product.prodname_vscode %} to create pull requests, review pull requests, and address review comments.'
|
||||
intro: 'Du kannst {% data variables.product.prodname_github_codespaces %} in deinem Webbrowser oder in {% data variables.product.prodname_vscode %} verwenden, um Pull Requests zu erstellen und zu überprüfen sowie um auf Reviewkommentare zu antworten.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -12,47 +12,52 @@ topics:
|
||||
- Developer
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/using-codespaces-for-pull-requests
|
||||
ms.openlocfilehash: 6932f8eb9095987bfe808080983970c8807b6d93
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159645'
|
||||
---
|
||||
## Informationen zu Pull Requests in {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
## About pull requests in {% data variables.product.prodname_github_codespaces %}
|
||||
{% data variables.product.prodname_github_codespaces %} bietet dir viele der Möglichkeiten, die du zum Arbeiten mit Pull Requests benötigst:
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} provides you with many of the capabilities you might need to work with pull requests:
|
||||
- [Erstellen eines Pull Requests](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request): Mit Hilfe des Terminals und der Git-Befehle oder der Quellcodeverwaltungsansicht kannst du Pull Requests genau wie auf der {% data variables.product.prodname_dotcom_the_website %} erstellen. Wenn das Repository eine Pull Request-Vorlage verwendet, kannst du dies in der Quellcodeverwaltungsansicht verwenden.
|
||||
- [Öffnen eines Pull Requests](#opening-a-pull-request-in-codespaces): Du kannst einen vorhandenen Pull Request in einem Codespace öffnen, sofern du Codespacezugriff auf den Branch hast, in den gemergt wird.
|
||||
- [Überprüfen eines Pull Requests](#reviewing-a-pull-request-in-codespaces): Nachdem du einen Pull Request in einem Codespace geöffnet hast, kannst du mit der Ansicht „GitHub-Pull Request“ Überprüfungskommentare hinzufügen und Pull Requests genehmigen. Du kannst {% data variables.product.prodname_github_codespaces %} auch verwenden, um [Reviewkommentare anzuzeigen](#view-comments-from-a-review-in-codespaces).
|
||||
|
||||
- [Create a pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Using either the Terminal and Git commands or the Source Control view, you can create pull requests just as you would on {% data variables.product.prodname_dotcom_the_website %}. If the repository uses a pull request template, you'll be able to use this within the Source Control view.
|
||||
- [Open a pull request](#opening-a-pull-request-in-codespaces) – You can open an existing pull request in a codespace, provided you have codespace access to the branch that is being merged in.
|
||||
- [Review a pull request](#reviewing-a-pull-request-in-codespaces) - Once you have opened a pull request in a codespace, you can use the "GitHub Pull Request" view to add review comments and approve pull requests. You can also use {% data variables.product.prodname_github_codespaces %} to [view review comments](#view-comments-from-a-review-in-codespaces).
|
||||
|
||||
## Opening a pull request in {% data variables.product.prodname_codespaces %}
|
||||
## Öffnen eines Pull Requests in {% data variables.product.prodname_codespaces %}
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
|
||||
1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}.
|
||||
1. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**.
|
||||
1. In the {% data variables.product.prodname_codespaces %} tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %})
|
||||
1. Klicke in der Liste der Pull Requests auf den Pull Request, den du in {% data variables.product.prodname_codespaces %} öffnen möchtest.
|
||||
1. Klicke auf der rechten Seite deines Bildschirms auf **{% octicon "code" aria-label="The code icon" %}-Code**.
|
||||
1. Klicke in der Registerkarte {% data variables.product.prodname_codespaces %} auf das Pluszeichen ({% octicon "plus" aria-label="The plus icon" %}).
|
||||
|
||||
|
||||
|
||||
|
||||
A codespace is created for the pull request branch and is opened in your default editor for {% data variables.product.prodname_github_codespaces %}.
|
||||
Es wird ein Codespace für den Pull-Request-Branch erstellt und in deinem Standard-Editor für {% data variables.product.prodname_github_codespaces %} geöffnet.
|
||||
|
||||
## Reviewing a pull request in {% data variables.product.prodname_codespaces %}
|
||||
## Überprüfen eines Pull Requests in {% data variables.product.prodname_codespaces %}
|
||||
|
||||
1. With your default editor set to either {% data variables.product.prodname_vscode %} or {% data variables.product.prodname_vscode %} for Web, open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)" above.
|
||||
2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace.
|
||||
|
||||
3. To review a specific file, click the **Open File** icon in the sidebar.
|
||||
|
||||
4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**.
|
||||
|
||||
5. When you are finished adding review comments, from the sidebar you can choose to either submit the comments, approve the changes, or request changes.
|
||||
|
||||
1. Wenn dein Standard-Editor auf {% data variables.product.prodname_vscode %} oder {% data variables.product.prodname_vscode %} für Web festgelegt ist, öffne den Pull Request in einem Codespace, wie oben unter [Öffnen eines Pull Requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces) beschrieben.
|
||||
2. Klicke in der Aktivitätsleiste auf die Ansicht **GitHub-Pull-Request**. Diese Ansicht wird nur angezeigt, wenn du einen Pull Request in einem Codespace öffnest.
|
||||
|
||||
3. Klicke zum Reviewen einer bestimmten Datei auf das Symbol für **Datei öffnen** in der Randleiste.
|
||||
|
||||
4. Klicke zum Hinzufügen von Überprüfungskommentaren auf das **+** -Symbol neben der Zeilennummer. Gib deinen Überprüfungskommentar ein, und klicke dann auf **Überprüfung starten**.
|
||||
|
||||
5. Wenn du mit dem Hinzufügen von Reviewkommentaren fertig bist, kannst du in der Randleiste auswählen, ob du die Kommentare übermitteln, die Änderungen genehmigen oder Änderungen beantragen möchtest.
|
||||
|
||||
|
||||
For more information on reviewing a pull request, see "[Reviewing proposed changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)."
|
||||
Weitere Informationen zum Überprüfen eines Pull Requests findest du unter [Überprüfen der vorgeschlagenen Änderungen in einem Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)".
|
||||
|
||||
## View comments from a review in {% data variables.product.prodname_codespaces %}
|
||||
## Anzeigen von Kommentaren aus einer Überprüfung in {% data variables.product.prodname_codespaces %}
|
||||
|
||||
Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review.
|
||||
Wenn du Feedback zu einem Pull Request erhalten hast, kannst du [dieses in einem Codespace](#opening-a-pull-request-in-codespaces) in deinem Webbrowser oder in {% data variables.product.prodname_vscode_shortname %} öffnen, um die [Reviewkommentare](#reviewing-a-pull-request-in-codespaces) anzuzeigen. Von dort aus kannst du auf Kommentare antworten, Reaktionen hinzufügen oder die Überprüfung schließen.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Using GitHub Codespaces in Visual Studio Code
|
||||
title: Verwenden von Github Codespaces in Visual Studio Code
|
||||
shortTitle: Visual Studio Code
|
||||
intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.'
|
||||
intro: 'Du kannst in deinem Codespace direkt in {% data variables.product.prodname_vscode %} entwickeln, indem du die Erweiterung für {% data variables.product.prodname_github_codespaces %} mit deinem Konto auf {% data variables.product.product_name %} verbindest.'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
|
||||
- /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
|
||||
@@ -15,70 +15,75 @@ topics:
|
||||
- Codespaces
|
||||
- Visual Studio Code
|
||||
- Developer
|
||||
ms.openlocfilehash: c651620e2795fb29f2b995f745ad3880e99c0f4e
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159601'
|
||||
---
|
||||
|
||||
## About {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}
|
||||
## Informationen zu {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}
|
||||
|
||||
You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. {% data reusables.codespaces.using-codespaces-in-vscode %} For more information on setting up {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)."
|
||||
Du kannst ihre lokale Installation von {% data variables.product.prodname_vscode %} verwenden, um Codespaces zu erstellen, zu verwalten, für die Arbeit zu verwenden und zu löschen. {% data reusables.codespaces.using-codespaces-in-vscode %} Weitere Informationen zur Einrichtung von {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} findest du unter [Voraussetzungen](#prerequisites).
|
||||
|
||||
By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
Wenn du einen neuen Codespace in {% data variables.product.prodname_dotcom_the_website %} erstellst, wird dieser standardmäßig im Browser geöffnet. Wenn neue Codespaces automatisch in {% data variables.product.prodname_vscode_shortname %} geöffnet werden sollen, kannst du den Standard-Editor auf {% data variables.product.prodname_vscode_shortname %} festlegen. Weitere Informationen findest du unter [Festlegen deines Standard-Editors für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces).
|
||||
|
||||
If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync)."
|
||||
Wenn du bevorzugt im Browser arbeitest, aber vorhandene {% data variables.product.prodname_vscode_shortname %}-Erweiterungen, -Designs und -Tastenkombinationen weiterhin verwenden möchtest, kannst du die Einstellungssynchronisierung aktivieren. Weitere Informationen findest du unter [Personalisieren von {% data variables.product.prodname_github_codespaces %} für dein Konto](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync).
|
||||
|
||||
## Prerequisites
|
||||
## Voraussetzungen
|
||||
|
||||
To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later.
|
||||
Wenn du direkt in einem Codespace in {% data variables.product.prodname_vscode_shortname %} entwickeln möchtest, musst du die {% data variables.product.prodname_github_codespaces %}-Erweiterung installieren und dich bei dieser mit deinen {% data variables.product.product_name %}-Anmeldeinformationen anmelden. Für die {% data variables.product.prodname_github_codespaces %}-Erweiterung ist {% data variables.product.prodname_vscode_shortname %} (Release 1.51 von Oktober 2020 oder höher) erforderlich.
|
||||
|
||||
Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
Über den {% data variables.product.prodname_vscode_marketplace %} lässt sich die [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)-Erweiterung installieren. Weitere Informationen findest du unter [Marketplace für Erweiterungen](https://code.visualstudio.com/docs/editor/extension-gallery) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
1. Click **Sign in to {% data variables.product.prodname_dotcom %}...**.
|
||||
1. Klicke auf **Anmelden, um {% data variables.product.prodname_dotcom %}...**
|
||||
|
||||
|
||||
|
||||
|
||||
2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**.
|
||||
3. Sign in to {% data variables.product.product_name %} to approve the extension.
|
||||
2. Um {% data variables.product.prodname_vscode_shortname %} für den Zugriff auf dein {% data variables.product.product_name %}-Konto zu autorisieren, klicke auf **Zulassen**.
|
||||
3. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
1. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**.
|
||||
1. Wähle **{% data variables.product.prodname_github_codespaces %}** im Dropdownmenü „REMOTE-EXPLORER“ aus.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Sign in to view {% data variables.product.prodname_codespaces %}**.
|
||||
1. Klicke auf **Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**.
|
||||
1. Sign in to {% data variables.product.product_name %} to approve the extension.
|
||||
1. Um {% data variables.product.prodname_vscode_shortname %} für den Zugriff auf dein {% data variables.product.product_name %}-Konto zu autorisieren, klicke auf **Zulassen**.
|
||||
1. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
## Creating a codespace in {% data variables.product.prodname_vscode_shortname %}
|
||||
## Erstellen eines Codespaces in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data reusables.codespaces.creating-a-codespace-in-vscode %}
|
||||
|
||||
## Opening a codespace in {% data variables.product.prodname_vscode_shortname %}
|
||||
## Öffnen eines Codespaces in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
1. Under "Codespaces", click the codespace you want to develop in.
|
||||
1. Click the Connect to Codespace icon.
|
||||
1. Klicke unter „Codespaces“ auf den Codespace, in dem du entwickeln möchtest.
|
||||
1. Klicke auf das Symbol „Connect to Codespace" (Verbinde zu Codespace).
|
||||
|
||||
|
||||
|
||||
|
||||
## Changing the machine type in {% data variables.product.prodname_vscode_shortname %}
|
||||
## Ändern des Computertyps in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time.
|
||||
{% data reusables.codespaces.codespaces-machine-types %} Du kannst den Computertyp deines Codespaces jederzeit ändern.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
**Hinweis:** {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -86,22 +91,22 @@ Use the {% data variables.product.prodname_vscode_marketplace %} to install the
|
||||
|
||||
{% data reusables.codespaces.about-changing-storage-size %}
|
||||
|
||||
## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %}
|
||||
## Löschen eines Codespaces in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
{% data reusables.codespaces.deleting-a-codespace-in-vscode %}
|
||||
|
||||
## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %}
|
||||
## Wechseln zum Insider-Build von {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_github_codespaces %}.
|
||||
Du kannst den [Insider-Build von {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) in {% data variables.product.prodname_github_codespaces %} verwenden.
|
||||
|
||||
1. In bottom left of your {% data variables.product.prodname_github_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**.
|
||||
2. From the list, select "Switch to Insiders Version".
|
||||
1. Klicke unten links im {% data variables.product.prodname_github_codespaces %}-Fenster auf **{% octicon "gear" aria-label="The settings icon" %} Einstellungen**.
|
||||
2. Wähle in der Liste „Zur Insiderversion wechseln“ aus.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Once selected, {% data variables.product.prodname_github_codespaces %} will continue to open in Insiders Version.
|
||||
3. Nach dem Auswählen wird {% data variables.product.prodname_github_codespaces %} in der Insider-Version geöffnet.
|
||||
|
||||
## Further reading
|
||||
## Weitere nützliche Informationen
|
||||
|
||||
- "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)"
|
||||
- "[Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)"
|
||||
- [Verwenden der {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)
|
||||
- [Verwenden von {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)
|
||||
|
||||
@@ -0,0 +1,138 @@
|
||||
---
|
||||
title: Verwenden von GitHub Codespaces in der JetBrains-IDE
|
||||
shortTitle: JetBrains IDEs
|
||||
intro: 'Du kannst JetBrains Gateway verwenden, um eine Verbindung mit deinem Codespace herzustellen und in deiner bevorzugten JetBrains-IDE zu arbeiten.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Developer
|
||||
ms.openlocfilehash: f522bf481e932f9735560ee4a1fec21944ced2e7
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159729'
|
||||
---
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
## Informationen zu {% data variables.product.prodname_codespaces %} in JetBrains-IDEs
|
||||
|
||||
Wenn du eine JetBrains-IDE zum Arbeiten an deinem Code verwendest, kannst du die Vorteile des Arbeitens in einem Codespace nutzen. Hierfür wird die JetBrains Gateway-Anwendung verwendet.
|
||||
|
||||
Nach der Installation von JetBrains Gateway kannst du JetBrains als Standard-Editor festlegen. Wenn du anschließend einen Codespace über {% data variables.product.prodname_dotcom_the_website %} öffnest, wird immer JetBrains Gateway gestartet, und du kannst deine JetBrains-IDE auswählen und eine Verbindung zum Codespace herstellen.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: In JetBrains Gateway sind nur vorhandene Codespaces verfügbar. Du kannst Codespaces auf {% data variables.product.prodname_dotcom_the_website %} oder mit der {% data variables.product.prodname_cli %} erstellen. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Verbindungsherstellung mit JetBrains für die Remoteentwicklung
|
||||
|
||||
Du kannst einen Codespace folgendermaßen in deiner JetBrains-IDE verwenden:
|
||||
|
||||
* Wähle in der JetBrains Gateway-Anwendung einen aktiven oder beendeten Codespace aus.
|
||||
* Wähle anschließend aus, welche JetBrains-IDE verwendet werden soll.
|
||||
* Die ausgewählte JetBrains-IDE wird dann auf den virtuellen Remotecomputer heruntergeladen, der deinen Codespace und den Quellcode hostet.
|
||||
* Die schlanke JetBrains-Clientanwendung wird dann auf den lokalen Computer heruntergeladen und gestartet.
|
||||
* Die Clientanwendung stellt eine Verbindung mit der vollständigen Back-End-IDE her.
|
||||
* Du kannst in der Clientanwendung genau wie in einer lokalen Umgebung an deinem Code arbeiten.
|
||||
|
||||
## Voraussetzungen
|
||||
|
||||
Du benötigst Folgendes, um in einem Codespaces in einer JetBrains-IDE zu arbeiten:
|
||||
|
||||
* Eine gültige JetBrains-Lizenz
|
||||
* Die JetBrains Gateway-Anwendung
|
||||
* {% data variables.product.prodname_cli %} 2.18.0 oder höher
|
||||
* Einen vorhandenen Codespace, der einen SSH-Server ausführt
|
||||
|
||||
### JetBrains-Lizenz
|
||||
|
||||
Du benötigst eine Lizenz für mindestens eine der unterstützten JetBrains-IDEs, um über JetBrains Gateway eine Verbindung mit einem Codespace herzustellen.
|
||||
|
||||
### JetBrains Gateway
|
||||
|
||||
Du kannst JetBrains Gateway über die Anwendung „JetBrains Toolbox“ installieren und aktualisieren.
|
||||
|
||||
1. Lade [JetBrains Toolbox](https://www.jetbrains.com/toolbox-app) herunter, und installiere die Anwendung.
|
||||
1. Öffne JetBrains Toolbox.
|
||||
1. Suche in der Liste der verfügbaren Tools nach **Gateway**, und klicke auf **Installieren**.
|
||||
|
||||
|
||||
|
||||
### {% data variables.product.prodname_cli %}
|
||||
|
||||
Das {% data variables.product.prodname_github_codespaces %}-Plug-In für JetBrains Gateway erfordert, dass {% data variables.product.prodname_cli %} 2.18.0 oder höher installiert und konfiguriert ist, bevor ein Codespace über JetBrains Gateway geöffnet werden kann.
|
||||
|
||||
Verwende diesen Befehl, um die Version von {% data variables.product.prodname_cli %} zu überprüfen:
|
||||
|
||||
```shell{:copy}
|
||||
gh --version
|
||||
```
|
||||
|
||||
Weitere Informationen findest du unter [Informationen zur GitHub-CLI](/github-cli/github-cli/about-github-cli).
|
||||
|
||||
### Codespace mit ausgeführtem SSH-Server
|
||||
|
||||
Es muss ein Codespace vorhanden sein, mit dem eine Verbindung hergestellt werden kann. {% data reusables.codespaces.ways-to-create-a-codespace %} Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository).
|
||||
|
||||
{% data reusables.codespaces.ssh-server-installed %}
|
||||
|
||||
Weitere Informationen zur Datei `devcontainer.json` und dem Standardcontainerimage findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: Hilfe beim Herstellen einer Verbindung mit deinem Codespace über SSH findest du unter [Problembehandlung für {% data variables.product.prodname_github_codespaces %}-Clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients?tool=jetbrains#ssh-connection-issues).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Einrichten von JetBrains Gateway
|
||||
|
||||
Wenn du JetBrains Gateway zum ersten Mal für {% data variables.product.prodname_github_codespaces %} verwendest, musst du das {% data variables.product.prodname_codespaces %}-Plug-In installieren. Außerdem musst du JetBrains Gateway den Zugriff auf {% data variables.product.prodname_dotcom_the_website %} über dein {% data variables.product.prodname_dotcom %}-Konto gestatten.
|
||||
|
||||
1. Öffne die Anwendung „JetBrains Gateway“.
|
||||
1. Klicke unter **Weitere Anbieter installieren** auf den **Installationslink** für {% data variables.product.prodname_github_codespaces %}.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf **Mit Codespace verbinden**.
|
||||
|
||||
|
||||
|
||||
1. Klicke im Dialogfeld „Willkommen bei JetBrains Gateway“ auf **Mit {% data variables.product.prodname_dotcom %} anmelden**.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf das Symbol neben dem einmaligen Code, um ihn zu kopieren, und klicke dann auf den Anmeldelink.
|
||||
|
||||
|
||||
|
||||
1. Wenn du derzeit nicht bei {% data variables.product.prodname_dotcom %} angemeldet bist, wird die Anmeldeseite angezeigt.
|
||||
* Gib deine Anmeldedaten ein, und klicke auf **Anmelden**.
|
||||
* Authentifiziere dich, zum Beispiel durch die Eingabe eines Zwei-Faktor-Authentifizierungscodes.
|
||||
1. Füge auf der Seite „Geräteaktivierung“ den kopierten Code ein, und klicke auf **Weiter**.
|
||||
1. Wenn du Organisationen angehörst, klicke auf der angezeigten Seite auf „Einmaliges Anmelden bei deiner Organisation“. Klicke neben den Organisationen, für die der Zugriff durch JetBrains Gateway autorisiert werden soll, auf **Autorisieren**. Klicke dann auf **Weiter**.
|
||||
1. Klicke auf der Seite „{% data variables.product.prodname_github_codespaces %} für JetBrains autorisieren“ auf **{% data variables.product.prodname_dotcom %} autorisieren**.
|
||||
1. Kehre zur JetBrains Gateway-Anwendung zurück, und öffne einen Codespace aus der Liste der derzeit aktiven oder beendeten Codespaces. Weitere Informationen findest du in Schritt 3 des folgenden Verfahrens.
|
||||
|
||||
## Öffnen eines Codespaces in deiner JetBrains-IDE
|
||||
|
||||
{% data reusables.codespaces.opening-codespace-in-jetbrains %}
|
||||
|
||||
Wenn du zum ersten Mal eine Verbindung mit einem Codespace herstellst, wird die Back-End-IDE auf den Remotecomputer heruntergeladen. Dies kann einige Minuten dauern. Wenn du das nächste Mal eine Verbindung mit demselben Codespace herstellst, ist dieser Schritt nicht erforderlich, sodass der Verbindungsvorgang beschleunigt wird.
|
||||
|
||||
Anschließend wird die Back-End-IDE gestartet. Auch dieser Schritt ist in Zukunft nicht erforderlich, wenn du eine Verbindung mit einer Back-End-IDE herstellst, die noch ausgeführt wird.
|
||||
|
||||
Dann wird die Clientanwendung gestartet.
|
||||
|
||||
## Weitere nützliche Informationen
|
||||
|
||||
- [Entwicklung in einem Codespace](/codespaces/developing-in-codespaces/developing-in-a-codespace)
|
||||
- [Verwenden des {% data variables.product.prodname_github_codespaces %}-Plug-Ins für JetBrains](/codespaces/codespaces-reference/using-the-github-codespaces-plugin-for-jetbrains)
|
||||
- [Verwenden von {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)
|
||||
- [Problembehandlung für {% data variables.product.prodname_github_codespaces %}-Clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients?tool=jetbrains)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using source control in your codespace
|
||||
intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
|
||||
title: Verwenden der Quellcodeverwaltung in deinem Codespace
|
||||
intro: 'Nachdem du Änderungen an einer Datei in deinem Codespace vorgenommen hast, kannst du die Änderungen schnell übernehmen und ein Update an das Remoterepository pushen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,37 +10,42 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Source control
|
||||
ms.openlocfilehash: 513bf0729e1f04bf93f45999b2fa9e45231add5c
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159641'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## About source control in {% data variables.product.prodname_github_codespaces %}
|
||||
## Informationen zur Quellcodeverwaltung in {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from a remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
|
||||
Du kannst alle Git-Aktionen ausführen, die du direkt in deinem Codespace benötigst. Du kannst beispielsweise Änderungen aus einem Remoterepository fetchen, Branches wechseln, einen neuen Branch erstellen, Änderungen committen und pushen und einen Pull Request erstellen. Du kannst das integrierte Terminal in deinem Codespace verwenden, um Git-Befehle einzugeben, oder du kannst auf Symbole und Menüoptionen klicken, um alle gängigen Git-Aufgaben abzuschließen. In diesem Leitfaden wird erläutert, wie du die grafische Benutzeroberfläche für die Quellcodeverwaltung verwendest.
|
||||
|
||||
{% vscode %}
|
||||
|
||||
For more information about Git support in {% data variables.product.prodname_vscode %}, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation.
|
||||
Weitere Informationen zur Git-Unterstützung in {% data variables.product.prodname_vscode %} findest du unter [Verwenden der Versionskontrolle in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support) in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
Source control in the {% data variables.product.prodname_vscode %} web client uses the same workflow as the {% data variables.product.prodname_vscode %} desktop application. For more information, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation.
|
||||
Die Quellcodeverwaltung im {% data variables.product.prodname_vscode %}-Webclient verwendet denselben Workflow wie die {% data variables.product.prodname_vscode %}-Desktopanwendung. Weitere Informationen findest du unter [Verwenden der Versionskontrolle in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support) in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
|
||||
Ein typischer Workflow zum Aktualisieren einer Datei mit {% data variables.product.prodname_github_codespaces %} sieht so aus:
|
||||
|
||||
* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
|
||||
* In your codespace, create a new branch to work on.
|
||||
* Make your changes and save them.
|
||||
* Commit the change.
|
||||
* Raise a pull request.
|
||||
* Erstelle im Standardbranch deines Repositorys auf {% data variables.product.prodname_dotcom %} einen Codespace. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository).
|
||||
* Erstelle in deinem Codespace einen neuen Branch, an dem du arbeiten möchtest.
|
||||
* Nimm deine Änderungen vor, und speichere sie.
|
||||
* Führe für die Änderung einen Commit aus.
|
||||
* Auslösen eines Pull Requests
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -56,67 +61,67 @@ A typical workflow for updating a file using {% data variables.product.prodname_
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Creating or switching branches
|
||||
## Erstellen oder Wechseln von Branches
|
||||
|
||||
1. Click the branch name at the right side of the status bar.
|
||||
1. Klicke auf der Statusleiste rechts auf den Branchnamen.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the pop-up menu, do one of the following:
|
||||
* To create a new branch based on the current branch, click the name of the current branch, then choose **New Branch**.
|
||||
1. Führe im Popupmenü einen der folgenden Schritte aus:
|
||||
* Um basierend auf dem aktuellen Branch einen neuen Branch zu erstellen, klicke auf den Namen des aktuellen Branchs und dann auf **Neuer Branch**.
|
||||
|
||||
|
||||
|
||||
|
||||
Enter a name for the new branch and click **Create**.
|
||||
Gib einen Namen für den neuen Branch ein, und klicke dann auf **Erstellen**.
|
||||
|
||||
|
||||
|
||||
|
||||
* To check out an existing branch, start typing the name of the branch you want to check out. Click the branch from the list, then click **Checkout**.
|
||||
* Um einen vorhandenen Branch auszuchecken, gib den Namen des Branchs ein, den du auschecken möchtest. Klicke in der Liste auf den Branch und dann auf **Auschecken**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
|
||||
**Tipp:** Wenn eine Person vor Kurzem eine Datei im Remoterepository geändert hat, wird diese Änderung im Branch, zu dem du gewechselt bist, möglicherweise erst angezeigt, wenn du die Änderungen in deinen Codespace pullst.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
## Committing your changes
|
||||
## Committen deiner Änderungen
|
||||
|
||||
1. At the right side of the navigation bar, click the check mark.
|
||||
1. Klicke auf der Navigationsleiste rechts auf das Häkchen.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Commit Changes dialog box, enter a commit message.
|
||||
1. Click **Commit**.
|
||||
1. Gib im Dialogfeld „Änderungen committen“ eine Commitnachricht ein.
|
||||
1. Klicke auf **Commit ausführen**.
|
||||
|
||||
Alternatively, click the down arrow beside **Commit** and click **Commit and Push**.
|
||||
Alternativ kannst du auf den nach unten zeigenden Pfeil neben **Commit** und dann auf **Commit und Push** klicken.
|
||||
|
||||
|
||||
|
||||
|
||||
## Pulling changes from the remote repository
|
||||
## Pullen von Änderungen aus einem Remoterepository
|
||||
|
||||
You can pull changes from the same branch on the remote repository and apply those changes to the copy of the repository you are working on in your codespace.
|
||||
Du kannst Änderungen aus demselben Branch im Remoterepository pullen und diese Änderungen auf die Kopie des Repositorys anwenden, an dem du in deinem Codespace arbeitest.
|
||||
|
||||
1. At the right side of the navigation bar, click the downward pointing arrow.
|
||||
1. Klicke rechts auf der Navigationsleiste auf den nach unten zeigenden Pfeil.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Update Project dialog box, choose whether you want to merge or rebase the incoming changes.
|
||||
1. Wähle im Dialogfeld „Projekt aktualisieren“ aus, ob du eingehende Änderungen mergen oder ein Rebase ausführen möchtest.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **OK**.
|
||||
1. Klicke auf **OK**.
|
||||
|
||||
## Pushing changes to your remote repository
|
||||
## Pushen von Änderungen an dein Remoterepository
|
||||
|
||||
You can push changes you've saved and committed. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
|
||||
Du kannst Änderungen pushen, die du gespeichert und committet hast. Dadurch werden die Änderungen im Upstreambranch im Remoterepository angewendet. Du kannst diese Methode nutzen, wenn du noch nicht bereit bist, einen Pull Request zu erstellen oder wenn du lieber einen Pull Request auf {% data variables.product.prodname_dotcom %} erstellen möchtest.
|
||||
|
||||
1. At the right side of the navigation bar, click the upward pointing arrow.
|
||||
1. Klicke rechts auf der Navigationsleiste auf den nach oben zeigenden Pfeil.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Push Commits dialog box, click **Push**.
|
||||
1. Klicke im Dialogfeld „Commits pushen“ auf **Push**.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 'Quickstart for {% data variables.product.prodname_github_codespaces %}'
|
||||
title: 'Schnellstartanleitung für {% data variables.product.prodname_github_codespaces %}'
|
||||
shortTitle: 'Quickstart for {% data variables.product.prodname_codespaces %}'
|
||||
intro: 'Try out {% data variables.product.prodname_github_codespaces %} in 5 minutes.'
|
||||
intro: 'Teste {% data variables.product.prodname_github_codespaces %} in fünf Minuten.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -11,103 +11,108 @@ topics:
|
||||
- Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-quickstart
|
||||
ms.openlocfilehash: f35fa87711ff3a7c33ed252d0d1e87865af619bc
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158653'
|
||||
---
|
||||
## Einführung
|
||||
|
||||
## Introduction
|
||||
In diesem Leitfaden erstellst du einen Codespace aus einem Vorlagenrepository und erkundest einige der wesentlichen Features, die dir im Codespace zur Verfügung stehen. Du arbeitest in der Browserversion von {% data variables.product.prodname_vscode %}, die zunächst der Standard-Editor für {% data variables.product.prodname_github_codespaces %} ist. Nachdem du diesen Schnellstart ausprobiert hast, kannst du {% data variables.product.prodname_codespaces %} in anderen Editoren verwenden und den Standard-Editor ändern. Die Links findest du am Ende dieses Leitfadens.
|
||||
|
||||
In this guide, you'll create a codespace from a template repository and explore some of the essential features available to you within the codespace. You'll work in the browser version of {% data variables.product.prodname_vscode %}, which is initially the default editor for {% data variables.product.prodname_github_codespaces %}. After trying out this quickstart you can use {% data variables.product.prodname_codespaces %} in other editors, and you can change the default editor. Links are provided at the end of this guide.
|
||||
In diesem Schnellstart erfährst du, wie du einen Codespace erstellst, eine Verbindung mit einem weitergeleiteten Port herstellst, um deine ausgeführte Anwendung anzuzeigen, deinen Codespace in einem neuen Repository veröffentlichst und dein Setup mit Erweiterungen personalisierst.
|
||||
|
||||
From this quickstart, you'll learn how to create a codespace, connect to a forwarded port to view your running application, publish your codespace to a new repository, and personalize your setup with extensions.
|
||||
Weitere Informationen zur genauen Funktionsweise von {% data variables.product.prodname_github_codespaces %} findest du im Begleitleitfaden [Fundierte Einblicke in {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive).
|
||||
|
||||
For more information on exactly how {% data variables.product.prodname_github_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
|
||||
## Erstellen des Codespace
|
||||
|
||||
## Creating your codespace
|
||||
|
||||
1. Navigate to the [github/haikus-for-codespaces](https://github.com/github/haikus-for-codespaces) template repository.
|
||||
1. Navigiere zum Vorlagenrepository [github/haikus-for-codespaces](https://github.com/github/haikus-for-codespaces).
|
||||
{% data reusables.codespaces.open-template-in-codespace-step %}
|
||||
|
||||
## Running the application
|
||||
## Ausführen der Anwendung
|
||||
|
||||
Once your codespace is created, the template repository will be automatically cloned into it. Now you can run the application and launch it in a browser.
|
||||
Sobald dein Codespace erstellt ist, wird dein Vorlagenrepository automatisch hinein geklont. Jetzt kannst du die Anwendung ausführen und in einem Browser starten.
|
||||
|
||||
1. When the terminal becomes available, enter the command `npm run dev`. This example uses a Node.js project, and this command runs the script labeled "dev" in the `package.json` file, which starts up the web application defined in the sample repository.
|
||||
1. Sobald das Terminal geöffnet wird, gib den Befehl `npm run dev` ein. In diesem Beispiel wird ein Node.js-Projekt verwendet, und dieser Befehl führt das Skript mit der Bezeichnung „dev“ in der Datei `package.json` aus, die die im Beispielrepository definierte Webanwendung startet.
|
||||
|
||||
|
||||
|
||||
|
||||
If you're following along with a different application type, enter the corresponding start command for that project.
|
||||
Wenn du mit einem anderen Anwendungstyp arbeitest, gib den entsprechenden Startbefehl für dieses Projekt ein.
|
||||
|
||||
2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to let you know it has been forwarded.
|
||||
2. Wenn deine Anwendung gestartet wird, erkennt der Codespace den Port, auf dem die Anwendung ausgeführt wird, und zeigt eine Eingabeaufforderung an, um dir mitzuteilen, dass sie weitergeleitet wurde.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Open in Browser** to view your running application in a new tab.
|
||||
3. Klicke auf **Im Browser öffnen**, um deine ausgeführte Anwendung auf einer neuen Registerkarte anzuzeigen.
|
||||
|
||||
## Edit the application and view changes
|
||||
## Bearbeiten der Anwendung und Anzeigen von Änderungen
|
||||
|
||||
1. Switch back to your codespace and open the `haikus.json` file by clicking it in the Explorer.
|
||||
1. Wechsle zurück zu deinem Codespace, und öffne die Datei `haikus.json`, indem du im Explorer darauf klickst.
|
||||
|
||||
2. Edit the `text` field of the first haiku to personalize the application with your own haiku.
|
||||
2. Bearbeite das `text`-Feld des ersten Haikus, um die Anwendung mit deinem eigenen Haiku zu personalisieren.
|
||||
|
||||
3. Go back to the running application tab in your browser and refresh to see your changes.
|
||||
3. Gehe zurück zur Registerkarte der ausgeführten Anwendung in deinem Browser und aktualisiere sie, um deine Änderungen zu sehen.
|
||||
|
||||
{% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port.
|
||||
{% octicon "light-bulb" aria-label="The lightbulb icon" %} Wenn du die Registerkarte geschlossen hast, öffne den Bereich „Ports“, und klicke auf das Symbol **Im Browser öffnen** für den ausgeführten Port.
|
||||
|
||||
|
||||
|
||||
|
||||
## Committing and pushing your changes
|
||||
## Commit und Push deiner Änderungen
|
||||
|
||||
Now that you've made a few changes, you can use the integrated terminal or the source view to publish your work to a new repository.
|
||||
Nachdem du nun einige Änderungen vorgenommen hast, kannst du das integrierte Terminal oder die Quellansicht verwenden, um deine Arbeit in einem neuen Repository zu veröffentlichen.
|
||||
|
||||
{% data reusables.codespaces.source-control-display-dark %}
|
||||
1. To stage your changes, click **+** next to the `haikus.json` file, or next to **Changes** if you've changed multiple files and you want to stage them all.
|
||||
1. Klicke zum Sagen einer Änderungen auf **+** neben der Datei `haikus.json` oder neben **Änderungen**, wenn du mehrere Dateien geändert hast und sie alle stagen möchtest.
|
||||
|
||||
|
||||
|
||||
|
||||
2. To commit your staged changes, type a commit message describing the change you've made, then click **Commit**.
|
||||
2. Gib eine Commitnachricht ein, die die von dir vorgenommene Änderung beschreibt, und klicke dann auf **Commit**, um deine gestageten Änderungen zu committen.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Publish Branch**.
|
||||
3. Klicke auf **Branch veröffentlichen**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. In the "Repository Name" dropdown, type a name for your new repository, then select **Publish to {% data variables.product.company_short %} private repository** or **Publish to {% data variables.product.company_short %} public repository**.
|
||||
4. Gib in der Dropdownliste „Repositoryname“ einen Namen für dein neues Repository ein, und wähle dann **Im privaten Repository {% data variables.product.company_short %} veröffentlichen** oder **Im öffentlichen Repository {% data variables.product.company_short %} veröffentlichen** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
The owner of the new repository will be the {% data variables.product.prodname_dotcom %} account with which you created the codespace.
|
||||
5. In the pop-up that appears in the lower right corner of the editor, click **Open on {% data variables.product.company_short %}** to view the new repository on {% data variables.product.prodname_dotcom_the_website %}. In the new repository, view the `haikus.json` file and check that the change you made in your codespace has been successfully pushed to the repository.
|
||||
Der Besitzer des neuen Repositorys ist das {% data variables.product.prodname_dotcom %}-Konto, mit dem du den Codespace erstellt hast.
|
||||
5. Klicke im Popupfenster, das in der unteren rechten Ecke des Editors angezeigt wird, auf **In {% data variables.product.company_short %} öffnen**, um das neue Repository für {% data variables.product.prodname_dotcom_the_website %} anzuzeigen. Zeige die Datei `haikus.json` im neuen Repository an, und überprüfe, ob die in deinem Codespace vorgenommene Änderung erfolgreich in das Repository gepusht wurde.
|
||||
|
||||
|
||||
|
||||
|
||||
## Personalizing with an extension
|
||||
## Personalisieren mit einer Erweiterung
|
||||
|
||||
When you connect to a codespace using the browser, or the {% data variables.product.prodname_vscode %} desktop application, you can access the Visual Studio Code Marketplace directly from the editor. For this example, you'll install a {% data variables.product.prodname_vscode_shortname %} extension that alters the theme, but you can install any extension that's useful for your workflow.
|
||||
Wenn du über den Browser oder die {% data variables.product.prodname_vscode %}-Desktopanwendung eine Verbindung mit einem Codespace herstellst, kannst du direkt über den Editor auf den Visual Studio Code-Marketplace zugreifen. In diesem Beispiel installierst du eine {% data variables.product.prodname_vscode_shortname %}-Erweiterung, die das Design ändert. Du kannst jedoch jede Erweiterung installieren, die für deinen Workflow nützlich ist.
|
||||
|
||||
1. In the left sidebar, click the Extensions icon.
|
||||
1. In the search bar, type `fairyfloss` and click **Install**.
|
||||
1. Klicke auf der linken Randleiste auf das Symbol „Erweiterungen“.
|
||||
1. Gib in der Suchleiste ein `fairyfloss`, und klicke auf **Installieren**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select the `fairyfloss` theme by selecting it from the list.
|
||||
1. Wähle das `fairyfloss`-Design aus, indem du es in der Liste auswählst.
|
||||
|
||||
|
||||
|
||||
|
||||
If you are using a codespace in the browser, or in the {% data variables.product.prodname_vscode %} desktop application, and you have [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) turned on, any changes you make to your editor setup in the current codespace, such as changing your theme or keyboard bindings, are automatically synced to any instances of {% data variables.product.prodname_vscode %} that are signed into your {% data variables.product.prodname_dotcom %} account and to any other codespaces you create.
|
||||
Wenn du einen Codespace im Browser oder in der {% data variables.product.prodname_vscode %}-Desktopanwendung verwendest, und du die [Einstellungssynchronisierung](https://code.visualstudio.com/docs/editor/settings-sync) aktiviert hast, werden alle Änderungen, die du am Editor-Setup im aktuellen Codespace vornimmst (z. B. Änderungen an deinem Design oder deinen Tastenzuordnungen) automatisch mit allen Instanzen von {% data variables.product.prodname_vscode %}, die bei deinem {% data variables.product.prodname_dotcom %}-Konto angemeldet sind, und allen anderen von dir erstellten Codespaces synchronisiert.
|
||||
|
||||
## Next steps
|
||||
## Nächste Schritte
|
||||
|
||||
You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_codespaces %}.
|
||||
Du hast deine erste Anwendung in einem Codespace erfolgreich erstellt, personalisiert und ausgeführt, aber es gibt so viel mehr zu entdecken! Hier findest du einige hilfreiche Ressourcen für deine nächsten Schritte mit {% data variables.product.prodname_github_codespaces %}.
|
||||
|
||||
* "[Deep dive](/codespaces/getting-started/deep-dive)": This quickstart presented some of the features of {% data variables.product.prodname_github_codespaces %}. The deep dive looks at these areas from a technical standpoint.
|
||||
* "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)": These guides provide information on setting up your repository to use {% data variables.product.prodname_github_codespaces %} with specific languages.
|
||||
* "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)": This guide provides details on creating a custom configuration for {% data variables.product.prodname_codespaces %} for your project.
|
||||
* [Fundierte Einblicke](/codespaces/getting-started/deep-dive): In diesem Schnellstart werden einige Features von {% data variables.product.prodname_github_codespaces %} vorgestellt. Hier erhältst du fundierte technische Einblicke.
|
||||
* [Hinzufügen einer Entwicklungscontainerkonfiguration zu deinem Repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces): Diese Leitfäden enthalten Informationen zum Einrichten deines Repositorys für die Verwendung von {% data variables.product.prodname_github_codespaces %} mit bestimmten Sprachen.
|
||||
* [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers): Dieser Leitfaden enthält Details zum Erstellen einer benutzerdefinierten Konfiguration für {% data variables.product.prodname_codespaces %} für dein Projekt.
|
||||
|
||||
## Further reading
|
||||
## Weitere nützliche Informationen
|
||||
|
||||
* "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
|
||||
* "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
* "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)"
|
||||
* "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)"
|
||||
* "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
* "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
* [Aktivieren von {% data variables.product.prodname_github_codespaces %} für deine Organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)
|
||||
* [Verwenden von {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)
|
||||
* [Verwenden von {% data variables.product.prodname_github_codespaces %} in deiner JetBrains-IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)
|
||||
* [Verwenden von {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)
|
||||
* [Festlegen deines Standard-Editors für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces).
|
||||
* [Verwalten der Kosten von {% data variables.product.prodname_github_codespaces %} in deiner Organisation](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Managing GitHub Codespaces for your organization
|
||||
title: Verwalten von GitHub Codespaces für deine Organisation
|
||||
allowTitleToDifferFromFilename: true
|
||||
shortTitle: Managing your organization
|
||||
intro: 'You can manage and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.'
|
||||
intro: 'Du kannst verwalten und überprüfen, wie Benutzer in deiner Organisation {% data variables.product.prodname_github_codespaces %} nutzen können.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -20,5 +20,11 @@ children:
|
||||
- /restricting-the-visibility-of-forwarded-ports
|
||||
- /restricting-the-idle-timeout-period
|
||||
- /restricting-the-retention-period-for-codespaces
|
||||
ms.openlocfilehash: 7b8b9211a8bcafdcfb3fb2b037ea6362e8ecb27f
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158637'
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,103 @@
|
||||
---
|
||||
title: Einschränken des Basisimages für Codespaces
|
||||
shortTitle: Restrict base image
|
||||
intro: 'Du kannst angeben, welche Basisimages für neue Codespaces verwendet werden können, die in deiner Organisation erstellt werden.'
|
||||
permissions: 'To manage image constraints for an organization''s codespaces, you must be an owner of the organization.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: 1da438a680dd3e60c1deeec46a98fbcf48f84e5b
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158997'
|
||||
---
|
||||
## Übersicht
|
||||
|
||||
Wenn du einen Codespace erstellen, wird automatisch ein Docker-Container auf einem virtuellen Remotecomputer erstellt. Dieser Docker-Container wird aus einem Docker-Image erstellt. Das Image ist im Grunde eine Vorlage für Docker-Container und bestimmt viele Aspekte der vom Codespace bereitgestellten resultierenden Umgebung.
|
||||
|
||||
Du kannst auswählen, welches Image du für deine Codespaces verwenden möchtest, indem du es in der Entwicklungscontainerkonfiguration für ein Repository angibst. Dazu kannst du z. B. die Eigenschaft `image` in der Datei `devcontainer.json` verwenden.
|
||||
|
||||
```json{:copy}
|
||||
"image": "mcr.microsoft.com/vscode/devcontainers/javascript-node:18",
|
||||
```
|
||||
|
||||
Weitere Informationen findest du in der [Entwicklungscontainerspezifikation](https://containers.dev/implementors/json_reference/) auf „containers.dev“.
|
||||
|
||||
Wenn du kein Image in der Entwicklungscontainerkonfiguration für ein Repository angibst, wird das Standardimage verwendet. Das Standardimage enthält eine Reihe von Runtimeversionen für gängige Programmiersprachen und häufig verwendete Tools. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration).
|
||||
|
||||
Als Organisationsbesitzer*in kannst du eine Richtlinie hinzufügen, mit der eingeschränkt wird, welche Images für Codespaces verwendet werden können, die in deiner Organisation erstellt werden.
|
||||
|
||||
Wenn das in der Entwicklungscontainerkonfiguration angegebene Image nicht mit einem der zulässigen Images übereinstimmt, wird die folgende Meldung angezeigt, wenn versucht wird, einen Codespace für das Repository zu erstellen:
|
||||
|
||||
> Codespace konnte nicht erstellt werden: Das Basisimage „DETAILS FROM DEV CONTAINER CONFIGURATION“ ist basierend auf einer vom Organisationsadministrator festgelegten Organisationsrichtlinie nicht zulässig.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweise**:
|
||||
* Die Basisimagerichtlinie wird nur angewendet, wenn ein Codespace erstellt wird. Aktuell wird sie nicht angewendet, wenn ein Container neu erstellt wird. Dies wird in einem zukünftigen Release geändert. Weitere Informationen findest du unter [Der Codespace-Lebenszyklus](/codespaces/developing-in-codespaces/the-codespace-lifecycle#rebuilding-a-codespace).
|
||||
* Die Basisimagerichtlinie gilt nicht für das Standardimage oder das Image, das zum Wiederherstellen eines Codespaces verwendet wird, wenn ein Fehler in einer Entwicklungscontainerkonfiguration auftritt, der verhindert, dass der Container neu erstellt wird.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Festlegen von organisationsweiten und repositoryspezifischen Richtlinien
|
||||
|
||||
Wenn du eine Richtlinie erstellst, wählst du aus, ob sie für alle Repositorys in deiner Organisation oder nur für angegebene gilt. Wenn du eine organisationsweite Richtlinie festlegst, müssen alle Richtlinien, die du für einzelne Repositorys festlegst, mit der auf Organisationsebene festgelegten Einschränkung übereinstimmen. Durch das Hinzufügen von Richtlinien wird die Wahl des Images nicht weniger, sondern stärker eingeschränkt.
|
||||
|
||||
Du kannst beispielsweise eine organisationsweite Richtlinie erstellen, die das Basisimage auf eines von zehn angegebenen Images beschränkt. Du kannst dann eine Richtlinie für Repository A festlegen, die das Image auf eine Teilmenge von nur zwei der auf Organisationsebene angegebenen Images beschränkt. Das Angeben zusätzlicher Images für Repository A hat keine Auswirkungen, da diese Images nicht in der Richtlinie auf Organisationsebene angegeben sind. Wenn du eine organisationsweite Richtlinie hinzufügst, solltest du sie auf die größte Auswahl von Images festlegen, die für ein Repository in deiner Organisation verfügbar ist. Du kannst dann repositoryspezifische Richtlinien hinzufügen, um die Auswahl weiter einzuschränken.
|
||||
|
||||
{% data reusables.codespaces.codespaces-org-policies-note %}
|
||||
|
||||
## Hinzufügen einer Richtlinie zum Definieren der zulässigen Images
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.codespaces.codespaces-org-policies %}
|
||||
1. Klicke auf **Einschränkung hinzufügen**, und wähle **Basisimages** aus.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf {% octicon "pencil" aria-label="The edit icon" %}, um die Einschränkung zu bearbeiten.
|
||||
|
||||
|
||||
|
||||
1. Gib im Feld „Zulässige Werte“ die vollständige URL eines Images ein, das du zulassen möchtest.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: Du musst eine Image-URL angeben, die genau mit dem in einer Entwicklungscontainerkonfiguration angegebenen Wert übereinstimmt.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Klicke auf die Schaltfläche mit dem Pluszeichen ({% octicon "plus" aria-label="The plus icon" %}), um den Wert hinzuzufügen.
|
||||
1. Wiederhole bei Bedarf die vorherigen beiden Schritte, um weitere Image-URLs hinzuzufügen.
|
||||
{% data reusables.codespaces.codespaces-policy-targets %}
|
||||
1. Wenn du der Richtlinie eine weitere Einschränkung hinzufügen möchtest, klicke auf **Einschränkung hinzufügen**, und wähle eine andere Einschränkung aus. Informationen zu anderen Einschränkungen findest du unter:
|
||||
* [Einschränken des Zugriffs auf Computertypen](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)
|
||||
* [Einschränken der Sichtbarkeit weitergeleiteter Ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)
|
||||
* [Einschränken des Zeitraums für Leerlauftimeouts](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)
|
||||
* [Einschränken des Aufbewahrungszeitraums für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)
|
||||
1. Nachdem du deiner Richtlinie Einschränkungen hinzugefügt hast, klicke auf **Speichern**.
|
||||
|
||||
Die Richtlinie wird angewendet, wenn versucht wird, einen neuen Codespace zu erstellen, der für deine Organisation abrechenbar ist. Die Basisimageeinschränkung wirkt sich nicht auf vorhandene, aktive oder beendete Codespaces aus.
|
||||
|
||||
## Bearbeiten einer Richtlinie
|
||||
|
||||
Du kannst eine vorhandenen Richtlinie bearbeiten. Beispielsweise kannst du Einschränkungen einer Richtlinie hinzufügen oder daraus entfernen.
|
||||
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Definieren der zulässigen Images](#adding-a-policy-to-define-the-allowed-images).
|
||||
1. Klicke auf den Namen der Richtlinie, die du bearbeiten möchtest.
|
||||
1. Klicke auf das Stiftsymbol ({% octicon "pencil" aria-label="The edit icon" %}) neben der Einschränkung „Basisimages“.
|
||||
1. Füge Image-URLs hinzu oder entferne sie.
|
||||
1. Klicke auf **Speichern**.
|
||||
|
||||
## Löschen einer Richtlinie
|
||||
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Definieren der zulässigen Images](#adding-a-policy-to-define-the-allowed-images).
|
||||
1. Klicke rechts neben der Richtlinie, die du löschen möchten, auf die Schaltfläche „Löschen“.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Restricting the idle timeout period
|
||||
title: Einschränken des Zeitraums für Leerlauftimeouts
|
||||
shortTitle: Restrict timeout periods
|
||||
intro: You can set a maximum timeout period for any codespaces owned by your organization.
|
||||
intro: Du kannst einen maximalen Timeoutzeitraum für alle Codespaces im Besitz deiner Organisation festlegen.
|
||||
permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -9,77 +9,80 @@ versions:
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: b07d1834078b065eee89acdb84e0e80a2db1e8a6
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158989'
|
||||
---
|
||||
## Übersicht
|
||||
|
||||
## Overview
|
||||
Bei Codespaces tritt nach 30 Minuten Inaktivität standardmäßig ein Timeout auf. Wenn bei einem Codespace ein Timeout auftritt, wird er beendet, und es werden keine Gebühren mehr für die Computenutzung berechnet.
|
||||
|
||||
By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage.
|
||||
Die persönlichen Einstellungen von {% data variables.product.prodname_dotcom %}-Benutzer*innen ermöglichen ihnen das Definieren eines benutzerdefinierten Timeoutzeitraums für die von ihnen erstellten Codespaces. Dieser Zeitraum kann länger sein als der Standardzeitraum von 30 Minuten. Weitere Informationen findest du unter [Festlegen deines Timeoutzeitraums für {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces).
|
||||
|
||||
The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
|
||||
|
||||
As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces created for repositories owned by your organization. This can help you to limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for the codespaces for all repositories owned by your organization, or for the codespaces of specific repositories.
|
||||
Als Organisationsbesitzer solltest du eventuell Einschränkungen für den maximalen Timeoutzeitraum für Codespaces konfigurieren, die für Repositorys im Besitz deiner Organisation erstellt werden. Dies kann helfen, Kosten im Zusammenhang mit Codespaces zu begrenzen, bei denen nach langen Zeiträumen von Inaktivität Timeouts auftreten. Du kannst ein maximales Timeout für die Codespaces für alle Repositorys im Besitz deiner Organisation oder für die Codespaces bestimmter Repositorys festlegen.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization.
|
||||
**Hinweis:** Einschränkungen für maximale Leerlauftimeouts gelten nur für Codespaces, die sich im Besitz deiner Organisation befinden.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
Weitere Informationen zu den Preisen für die Computenutzung von {% data variables.product.prodname_github_codespaces %} findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing).
|
||||
|
||||
### Behavior when you set a maximum idle timeout constraint
|
||||
### Verhalten, wenn eine Einschränkung für das maximale Leerlauftimeout festgelegt ist
|
||||
|
||||
If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed:
|
||||
Wenn das Standard-Leerlauftimeout in den persönlichen Einstellungen auf 90 Minuten festlegt und dann ein Codespace für ein Repository mit einer Einschränkung für das maximale Leerlauftimeout von 60 Minuten gestartet wird, tritt beim Codespace nach 60 Minuten Inaktivität ein Timeout auf. Wenn die Codespaceerstellung abgeschlossen ist, wird eine Meldung angezeigt, die dies erläutert:
|
||||
|
||||
> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy.
|
||||
> Das Leerlauftimeout für diesen Codespace ist gemäß den Richtlinien deiner Organisation auf 60 Minuten festgelegt.
|
||||
|
||||
### Setting organization-wide and repository-specific policies
|
||||
### Festlegen von organisationsweiten und repositoryspezifischen Richtlinien
|
||||
|
||||
When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied.
|
||||
Wenn du eine Richtlinie erstellst, wählst du aus, ob sie für alle Repositorys in deiner Organisation oder nur für angegebene Repositorys gilt. Wenn du eine organisationsweite Richtlinie mit einer Timeouteinschränkung erstellst, müssen die Timeouteinschränkungen in allen Richtlinien, die auf bestimmte Repositorys ausgerichtet sind, innerhalb der für die gesamte Organisation konfigurierten Einschränkung liegen. Der kürzeste Timeoutzeitraum in einer organisationsweiten Richtlinie, einer auf bestimmte Repositorys ausgerichteten Richtlinie oder in den persönlichen Einstellungen einer Person wird angewendet.
|
||||
|
||||
If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization.
|
||||
Wenn du eine organisationsweite Richtlinie mit einer Timeouteinschränkung hinzufügst, solltest du das Timeout auf den längsten zulässigen Zeitraum festlegen. Anschließend kannst du separate Richtlinien hinzufügen, die das maximale Timeout für bestimmte Repositorys in deiner Organisation auf einen kürzeren Zeitraum festlegen.
|
||||
|
||||
{% data reusables.codespaces.codespaces-org-policies-note %}
|
||||
|
||||
## Adding a policy to set a maximum idle timeout period
|
||||
## Hinzufügen einer Richtlinie zum Festlegen eines maximalen Zeitraums für Leerlauftimeouts
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.codespaces.codespaces-org-policies %}
|
||||
1. Click **Add constraint** and choose **Maximum idle timeout**.
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.codespaces.codespaces-org-policies %}
|
||||
1. Klicke auf **Einschränkung hinzufügen**, und wähle **Maximales Leerlauftimeout** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
|
||||
1. Klicke auf {% octicon "pencil" aria-label="The edit icon" %}, um die Einschränkung zu bearbeiten.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**.
|
||||
1. Gib die maximale Anzahl von Minuten ein, die Codespaces inaktiv bleiben können, bevor ein Timeout auftritt. Klicke anschließend auf **Speichern**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.codespaces-policy-targets %}
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
|
||||
* "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
|
||||
* "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
|
||||
* "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)"
|
||||
* "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
|
||||
1. After you've finished adding constraints to your policy, click **Save**.
|
||||
1. Wenn du der Richtlinie eine weitere Einschränkung hinzufügen möchtest, klicke auf **Einschränkung hinzufügen**, und wähle eine andere Einschränkung aus. Informationen zu anderen Einschränkungen findest du hier:
|
||||
* [Einschränken des Zugriffs auf Computertypen](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)
|
||||
* [Einschränken des Basisimages für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)
|
||||
* [Einschränken der Sichtbarkeit weitergeleiteter Ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)
|
||||
* [Einschränken des Aufbewahrungszeitraums für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)
|
||||
1. Nachdem du deiner Richtlinie Einschränkungen hinzugefügt hast, klicke auf **Speichern**.
|
||||
|
||||
The policy will be applied to all new codespaces that are billable to your organization. The timeout constraint is also applied to existing codespaces the next time they are started.
|
||||
Die Richtlinie wird auf alle neu erstellten Codespaces angewendet, die deiner Organisation in Rechnung gestellt werden. Die Timeouteinschränkung wird beim nächsten Start auch auf vorhandene Codespaces angewendet.
|
||||
|
||||
## Editing a policy
|
||||
## Bearbeiten einer Richtlinie
|
||||
|
||||
You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
|
||||
Du kannst eine vorhandenen Richtlinie bearbeiten. Beispielsweise kannst du Einschränkungen einer Richtlinie hinzufügen oder daraus entfernen.
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
|
||||
1. Click the name of the policy you want to edit.
|
||||
1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Maximum idle timeout" constraint.
|
||||
1. Make the required changes then click **Save**.
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Festlegen eines maximalen Zeitraums für Leerlauftimeouts](#adding-a-policy-to-set-a-maximum-idle-timeout-period).
|
||||
1. Klicke auf den Namen der Richtlinie, die du bearbeiten möchtest.
|
||||
1. Klicke auf das Stiftsymbol ({% octicon "pencil" aria-label="The edit icon" %}) neben der Einschränkung „Maximales Leerlauftimeout“.
|
||||
1. Nimm die erforderlichen Änderungen vor, und klicke dann auf **Speichern**.
|
||||
|
||||
## Deleting a policy
|
||||
## Löschen einer Richtlinie
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
|
||||
1. Click the delete button to the right of the policy you want to delete.
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Festlegen eines maximalen Zeitraums für Leerlauftimeouts](#adding-a-policy-to-set-a-maximum-idle-timeout-period).
|
||||
1. Klicke rechts neben der Richtlinie, die du löschen möchten, auf die Schaltfläche „Löschen“.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Restricting the visibility of forwarded ports
|
||||
title: Einschränken der Sichtbarkeit weitergeleiteter Ports
|
||||
shortTitle: Restrict port visibility
|
||||
intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization.
|
||||
intro: 'Du kannst Einschränkungen für die Sichtbarkeitsoptionen festlegen, die Benutzer*innen auswählen können, wenn sie Ports der Codespaces in deiner Organisation weiterleiten.'
|
||||
permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -9,73 +9,76 @@ versions:
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: ad670b43e0ac2a80e43048ffa61e0c83a8d12130
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158973'
|
||||
---
|
||||
## Übersicht
|
||||
|
||||
## Overview
|
||||
Normalerweise kannst du innerhalb eines Codespace Ports privat (nur an dich selbst), an Mitglieder deiner Organisation oder öffentlich (an alle Personen mit der URL) weiterleiten. Weitere Informationen findest du unter [Weiterleiten von Ports in Codespaces](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace).
|
||||
|
||||
Typically, within a codespace you are able to forward ports privately (only to yourself), to members of your organization, or publicly (to anyone with the URL). For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
|
||||
Als Organisationsbesitzer kannst du Einschränkungen für die Sichtbarkeitsoptionen konfigurieren, die Benutzer bei der Weiterleitung von Ports festlegen können. Aus Sicherheitsgründen kannst du z. B. die Weiterleitung öffentlicher Porte untersagen. Dazu definierst du eine oder mehrere Richtlinien in den Einstellungen von {% data variables.product.prodname_github_codespaces %} für deine Organisation.
|
||||
|
||||
As an organization owner, you may want to configure constraints on the visibility options users can set when forwarding ports. For example, for security reasons, you may want to disallow public port forwarding. You do this by defining one or more policies in the {% data variables.product.prodname_github_codespaces %} settings for your organization.
|
||||
### Verhalten beim Festlegen einer Einschränkung der Portsichtbarkeit
|
||||
|
||||
### Behavior when you set a port visibility constraint
|
||||
|
||||
If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints.
|
||||
Wenn vorhandene Codespaces nicht mehr mit einer von dir definierten Richtlinie übereinstimmen, werden diese Codespaces weiter verwendet, bis sie gestoppt werden oder ein Timeout eintritt. Wenn der Benutzer den Codespace fortsetzt, unterliegt er den Richtlinieneinschränkungen.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_github_codespaces %} to continue working as designed, for example to forward SSH on port 22.
|
||||
**Hinweis**: Du kannst die Weiterleitung an private Ports nicht deaktivieren, da {% data variables.product.prodname_github_codespaces %} diese benötigt, um weiterhin wie vorgesehen zu funktionieren, z. B. um SSH zu Port 22 weiterzuleiten.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Setting organization-wide and repository-specific policies
|
||||
### Festlegen von organisationsweiten und repositoryspezifischen Richtlinien
|
||||
|
||||
When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of visibility options more, not less, restrictive.
|
||||
Wenn du eine Richtlinie erstellst, wählst du aus, ob sie für alle Repositorys in deiner Organisation oder nur für angegebene gilt. Wenn du eine organisationsweite Richtlinie festlegst, müssen alle Richtlinien, die du für einzelne Repositorys festlegst, mit der auf Organisationsebene festgelegten Einschränkung übereinstimmen. Durch das Hinzufügen von Richtlinien wird die Wahl der Sichtbarkeitsoptionen nicht weniger, sondern stärker eingeschränkt.
|
||||
|
||||
For example, you could create an organization-wide policy that restricts the visibility options to organization only. You can then set a policy for Repository A that disallows both public and organization visibility, which would result in only private port forwarding being available for this repository. Setting a policy for Repository A that allowed both public and organization would result in only organization visibility, because the organization-wide policy does not allow public visibility.
|
||||
Du kannst z. B. eine organisationsweite Richtlinie erstellen, die die Sichtbarkeitsoptionen auf die Organisation beschränkt. Dann kannst du eine Richtlinie für Repository A festlegen, die sowohl die öffentliche Sichtbarkeit als auch die Sichtbarkeit in der Organisation nicht zulässt, was dazu führen würde, dass nur die Privatportweiterleitung für dieses Repository verfügbar ist. Die Festlegung einer Richtlinie für Repository A, die sowohl die öffentliche als auch die Sichtbarkeit innerhalb der Organisation zulässt, würde dazu führen, dass nur die Sichtbarkeit innerhalb der Organisation gegeben ist, da die organisationsweite Richtlinie keine öffentliche Sichtbarkeit zulässt.
|
||||
|
||||
If you add an organization-wide policy, you should set it to the most lenient visibility option that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
|
||||
Wenn du eine organisationsweite Richtlinie hinzufügst, solltest du sie auf die großzügigste Sichtbarkeitsoption festlegen, die für ein Repository in deiner Organisation verfügbar ist. Du kannst dann repositoryspezifische Richtlinien hinzufügen, um die Auswahl weiter einzuschränken.
|
||||
|
||||
{% data reusables.codespaces.codespaces-org-policies-note %}
|
||||
|
||||
## Adding a policy to limit the port visibility options
|
||||
## Hinzufügen einer Richtlinie zum Einschränken der Portsichtbarkeitsoptionen
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.codespaces.codespaces-org-policies %}
|
||||
1. Click **Add constraint** and choose **Port visibility**.
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.codespaces.codespaces-org-policies %}
|
||||
1. Klicke auf **Einschränkung hinzufügen**, und wähle **Portsichtbarkeit** aus.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
|
||||
1. Klicke auf {% octicon "pencil" aria-label="The edit icon" %}, um die Einschränkung zu bearbeiten.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Clear the selection of the port visibility options (**Org** or **Public**) that you don't want to be available.
|
||||
1. Lösche die Auswahl der Portsichtbarkeitsoptionen (**Org** oder **Öffentlich**), die nicht verfügbar sein sollen.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.codespaces-policy-targets %}
|
||||
1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
|
||||
* "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
|
||||
* "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
|
||||
* "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)"
|
||||
* "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
|
||||
1. After you've finished adding constraints to your policy, click **Save**.
|
||||
1. Wenn du der Richtlinie eine weitere Einschränkung hinzufügen möchtest, klicke auf **Einschränkung hinzufügen**, und wähle eine andere Einschränkung aus. Informationen zu anderen Einschränkungen findest du unter:
|
||||
* [Einschränken des Zugriffs auf Computertypen](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)
|
||||
* [Einschränken des Basisimages für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)
|
||||
* [Einschränken des Zeitraums für Leerlauftimeouts](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)
|
||||
* [Einschränken des Aufbewahrungszeitraums für Codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)
|
||||
1. Nachdem du deiner Richtlinie Einschränkungen hinzugefügt hast, klicke auf **Speichern**.
|
||||
|
||||
The policy will be applied to all new codespaces that are billable to your organization. The port visibility constraint is also applied to existing codespaces the next time they are started.
|
||||
Die Richtlinie wird auf alle neu erstellten Codespaces angewendet, die deiner Organisation in Rechnung gestellt werden. Die Portsichtbarkeitseinschränkung wird beim nächsten Start auch auf vorhandene Codespaces angewendet.
|
||||
|
||||
## Editing a policy
|
||||
## Bearbeiten einer Richtlinie
|
||||
|
||||
You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
|
||||
Du kannst eine vorhandenen Richtlinie bearbeiten. Beispielsweise kannst du Einschränkungen einer Richtlinie hinzufügen oder daraus entfernen.
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
|
||||
1. Click the name of the policy you want to edit.
|
||||
1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Port visibility" constraint.
|
||||
1. Make the required changes then click **Save**.
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Einschränken der Portsichtbarkeitsoptionen](#adding-a-policy-to-limit-the-port-visibility-options).
|
||||
1. Klicke auf den Namen der Richtlinie, die du bearbeiten möchtest.
|
||||
1. Klicke auf das Stiftsymbol ({% octicon "pencil" aria-label="The edit icon" %}) neben der Einschränkung „Portsichtbarkeit“.
|
||||
1. Nimm die erforderlichen Änderungen vor, und klicke dann auf **Speichern**.
|
||||
|
||||
## Deleting a policy
|
||||
## Löschen einer Richtlinie
|
||||
|
||||
1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
|
||||
1. Click the delete button to the right of the policy you want to delete.
|
||||
1. Zeige die Seite „Codespacerichtlinien“ an. Weitere Informationen findest du unter [Hinzufügen einer Richtlinie zum Einschränken der Portsichtbarkeitsoptionen](#adding-a-policy-to-limit-the-port-visibility-options).
|
||||
1. Klicke rechts neben der Richtlinie, die du löschen möchtest, auf die Schaltfläche „Löschen“.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Reviewing your security logs for GitHub Codespaces
|
||||
title: Überprüfen deiner Sicherheitsprotokolle für GitHub Codespaces
|
||||
shortTitle: Security logs
|
||||
intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_github_codespaces %}.'
|
||||
intro: 'Du kannst das Sicherheitsprotokoll verwenden, um alle Aktionen im Zusammenhang mit {% data variables.product.prodname_github_codespaces %} zu überprüfen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,19 +11,22 @@ topics:
|
||||
- Security
|
||||
redirect_from:
|
||||
- /codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces
|
||||
ms.openlocfilehash: 51cd11f123cbc2b6b67e089d65bc68d3441aa5b8
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159677'
|
||||
---
|
||||
## Informationen zu Sicherheitsprotokollen für {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
|
||||
Wenn du eine Aktion im Zusammenhang mit {% data variables.product.prodname_github_codespaces %} in einem Repository ausführst, das deinem persönlichen Konto angehört, kannst du die Aktionen im Sicherheitsprotokoll überprüfen. Informationen zum Zugreifen auf das Protokoll findest du unter [Überprüfen des Sicherheitsprotokolls](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log).
|
||||
|
||||
## About security logs for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
|
||||
When you perform an action related to {% data variables.product.prodname_github_codespaces %} in repositories owned by your personal account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
|
||||
Das Sicherheitsprotokoll enthält Details darüber, wann du welche Aktion ausgeführt hast. Informationen zu {% data variables.product.prodname_github_codespaces %}-Aktionen findest du unter [{% data variables.product.prodname_codespaces %}-Kategorieaktionen](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions).
|
||||
|
||||
|
||||
## Weitere Informationsquellen
|
||||
|
||||
The security log includes details on what action occurred and when you performed it. For information about {% data variables.product.prodname_github_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
|
||||
- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)"
|
||||
- „[Überprüfen der Überwachungsprotokolle deiner Organisation für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)“
|
||||
- [{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Setting up your C# (.NET) project for GitHub Codespaces
|
||||
title: Einrichten deines C#-Projekts (.NET) für GitHub Codespaces
|
||||
shortTitle: Setting up your C# (.NET) project
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.'
|
||||
intro: 'Beginne mit deinem C#-Projekt (.NET) in {% data variables.product.prodname_github_codespaces %}, indem du einen benutzerdefinierten Entwicklungscontainer erstellst.'
|
||||
redirect_from:
|
||||
- /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
|
||||
versions:
|
||||
@@ -12,122 +12,126 @@ topics:
|
||||
- Codespaces
|
||||
hasExperimentalAlternative: true
|
||||
hidden: true
|
||||
ms.openlocfilehash: 10282aedf3bdb239fa238e546c2fc6280787a6a0
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158613'
|
||||
---
|
||||
## Einführung
|
||||
|
||||
## Introduction
|
||||
In diesem Leitfaden wird veranschaulicht, wie du dein C#-Projekt (.NET) in {% data reusables.codespaces.setting-up-project-intro %} einrichtest.
|
||||
|
||||
This guide shows you how to set up your C# (.NET) project {% data reusables.codespaces.setting-up-project-intro %}
|
||||
### Voraussetzungen
|
||||
|
||||
### Prerequisites
|
||||
- Du solltest über ein vorhandenes C#-Projekt (.NET) in einem Repository auf {% data variables.product.prodname_dotcom_the_website %} verfügen. Wenn du über kein Projekt verfügst, kannst du dieses Tutorial mit dem folgenden Beispiel verwenden: https://github.com/2percentsilk/dotnet-quickstart.
|
||||
- {% data variables.product.prodname_github_codespaces %} muss für deine Organisation aktiviert sein.
|
||||
|
||||
- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
|
||||
- You must have {% data variables.product.prodname_github_codespaces %} enabled for your organization.
|
||||
## Schritt 1: Öffnen deines Projekt in einem Codespace
|
||||
|
||||
## Step 1: Open your project in a codespace
|
||||
1. Verwende das Dropdownmenü **{% octicon "code" aria-label="The code icon" %}-Code** unter dem Repositorynamen, und klicke auf der Registerkarte **Codespaces** auf das Pluszeichen ({% octicon "plus" aria-label="The plus icon" %}).
|
||||
|
||||
1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}).
|
||||
|
||||
|
||||
|
||||
|
||||
When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
|
||||
Wenn du einen Codespace erstellst, wird dein Projekt auf einer Remote-VM erstellt, die dir zugewiesen ist. Der Container für deinen Codespace verfügt standardmäßig über viele Fragen und Runtimes (einschließlich .NET). Er enthält außerdem gängige Tools wie Git, Wget, rsync, OpenSSH und nano.
|
||||
|
||||
{% data reusables.codespaces.customize-vcpus-and-ram %}
|
||||
|
||||
## Step 2: Add a dev container configuration to your repository from a template
|
||||
## Schritt 2: Hinzufügen einer Entwicklungscontainerkonfiguration zu deinem Repository aus einer Vorlage
|
||||
|
||||
The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} comes with the latest .NET version and common tools preinstalled. However, we recommend that you configure your own dev container to include all of the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository.
|
||||
Im Standardentwicklungscontainer für {% data variables.product.prodname_github_codespaces %} sind die aktuelle .NET-Version und gängige Tools bereits vorinstalliert. Es wird jedoch empfohlen, einen eigenen Entwicklungscontainer zu konfigurieren, der alle Tools und Skripts enthält, die für dein Projekt erforderlich sind. Dadurch wird eine vollständig reproduzierbare Umgebung für alle {% data variables.product.prodname_github_codespaces %}-Benutzer in deinem Repository bereitgestellt.
|
||||
|
||||
{% data reusables.codespaces.setup-custom-devcontainer %}
|
||||
|
||||
{% data reusables.codespaces.command-palette-container %}
|
||||
1. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL.
|
||||
|
||||
1. Click the recommended version of .NET.
|
||||
|
||||
1. Accept the default option to add Node.js to your customization.
|
||||
|
||||
{% data reusables.codespaces.rebuild-command %}
|
||||
1. Klicke für dieses Beispiel auf **C# (.NET)**. Wenn du zusätzliche Features benötigst, kannst du einen beliebigen für C# (.NET) spezifischen Container oder eine Kombination aus Tools wie C# (.NET) und MS SQL auswählen.
|
||||
|
||||
1. Klicke auf die empfohlene .NET-Version.
|
||||
|
||||
1. Akzeptiere die Standardoption, um deiner Anpassung Node.js hinzuzufügen.
|
||||
 {% data reusables.codespaces.rebuild-command %}
|
||||
|
||||
### Anatomy of your dev container
|
||||
### Struktur des Dev-Containers
|
||||
|
||||
Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
|
||||
Durch das Hinzufügen der Vorlage des C#-Entwicklungscontainers (.NET) wird ein `.devcontainer`-Ordner mit den folgenden Dateien zum Stammverzeichnis des Projektrepositorys hinzugefügt:
|
||||
|
||||
- `devcontainer.json`
|
||||
- Dockerfile
|
||||
|
||||
The newly added `devcontainer.json` file defines a few properties that are described after the sample.
|
||||
Die neu hinzugefügte `devcontainer.json`-Datei definiert einige Eigenschaften, die nach dem Beispiel beschrieben werden.
|
||||
|
||||
#### devcontainer.json
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "C# (.NET)",
|
||||
"build": {
|
||||
"dockerfile": "Dockerfile",
|
||||
"args": {
|
||||
// Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
|
||||
"VARIANT": "5.0",
|
||||
// Options
|
||||
"INSTALL_NODE": "true",
|
||||
"NODE_VERSION": "lts/*",
|
||||
"INSTALL_AZURE_CLI": "false"
|
||||
}
|
||||
},
|
||||
"name": "C# (.NET)",
|
||||
"build": {
|
||||
"dockerfile": "Dockerfile",
|
||||
"args": {
|
||||
// Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
|
||||
"VARIANT": "5.0",
|
||||
// Options
|
||||
"INSTALL_NODE": "true",
|
||||
"NODE_VERSION": "lts/*",
|
||||
"INSTALL_AZURE_CLI": "false"
|
||||
}
|
||||
},
|
||||
|
||||
// Set *default* container specific settings.json values on container create.
|
||||
"settings": {
|
||||
"terminal.integrated.shell.linux": "/bin/bash"
|
||||
},
|
||||
// Set *default* container specific settings.json values on container create.
|
||||
"settings": {
|
||||
"terminal.integrated.shell.linux": "/bin/bash"
|
||||
},
|
||||
|
||||
// Add the IDs of extensions you want installed when the container is created.
|
||||
"extensions": [
|
||||
"ms-dotnettools.csharp"
|
||||
],
|
||||
// Add the IDs of extensions you want installed when the container is created.
|
||||
"extensions": [
|
||||
"ms-dotnettools.csharp"
|
||||
],
|
||||
|
||||
// Use 'forwardPorts' to make a list of ports inside the container available locally.
|
||||
// "forwardPorts": [5000, 5001],
|
||||
// Use 'forwardPorts' to make a list of ports inside the container available locally.
|
||||
// "forwardPorts": [5000, 5001],
|
||||
|
||||
// [Optional] To reuse of your local HTTPS dev cert:
|
||||
//
|
||||
// 1. Export it locally using this command:
|
||||
// * Windows PowerShell:
|
||||
// dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
|
||||
// * macOS/Linux terminal:
|
||||
// dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
|
||||
//
|
||||
// 2. Uncomment these 'remoteEnv' lines:
|
||||
// "remoteEnv": {
|
||||
// "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
|
||||
// "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
|
||||
// },
|
||||
//
|
||||
// 3. Start the container.
|
||||
//
|
||||
// 4. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer.
|
||||
//
|
||||
// 5. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https".
|
||||
//
|
||||
// [Optional] To reuse of your local HTTPS dev cert:
|
||||
//
|
||||
// 1. Export it locally using this command:
|
||||
// * Windows PowerShell:
|
||||
// dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
|
||||
// * macOS/Linux terminal:
|
||||
// dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
|
||||
//
|
||||
// 2. Uncomment these 'remoteEnv' lines:
|
||||
// "remoteEnv": {
|
||||
// "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
|
||||
// "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
|
||||
// },
|
||||
//
|
||||
// 3. Start the container.
|
||||
//
|
||||
// 4. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer.
|
||||
//
|
||||
// 5. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https".
|
||||
//
|
||||
|
||||
// Use 'postCreateCommand' to run commands after the container is created.
|
||||
// "postCreateCommand": "dotnet restore",
|
||||
// Use 'postCreateCommand' to run commands after the container is created.
|
||||
// "postCreateCommand": "dotnet restore",
|
||||
|
||||
// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
|
||||
"remoteUser": "vscode"
|
||||
// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
|
||||
"remoteUser": "vscode"
|
||||
}
|
||||
```
|
||||
|
||||
- **name** - You can name our dev container anything, this is just the default.
|
||||
- **build** - The build properties.
|
||||
- **dockerfile** - In the `build` object, `dockerfile` contains the path to the Dockerfile that was also added from the template.
|
||||
- **name**: Du kannst deinem Entwicklungscontainer einen beliebigen Namen geben. Dies ist nur der Standardname.
|
||||
- **build**: Hierbei handelt es sich um die Buildeigenschaften.
|
||||
- **dockerfile**: Im `build`-Objekt enthält `dockerfile` den Pfad zu der Dockerfile-Datei, die ebenfalls aus der Vorlage hinzugefügt wurde.
|
||||
- **args**
|
||||
- **variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
|
||||
- **settings** - These are {% data variables.product.prodname_vscode %} settings.
|
||||
- **terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
|
||||
- **extensions** - These are extensions included by default.
|
||||
- **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
|
||||
- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
|
||||
- **postCreateCommand** - Use this to run commands that aren't defined in the Dockerfile, after your codespace is created.
|
||||
- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
|
||||
- **variant:** Diese Datei enthält nur ein Buildargument, das die .NET Core-Version angibt, die du verwenden möchtest.
|
||||
- **settings:** Hierbei handelt es sich um die {% data variables.product.prodname_vscode %}-Einstellungen.
|
||||
- **terminal.integrated.shell.linux**: Auch wenn Bash hier standardmäßig verwendet wird, kannst du andere Terminalshells verwenden, indem du diese Einstellung bearbeitest.
|
||||
- **extensions**: Diese Erweiterungen sind standardmäßig enthalten.
|
||||
- **ms-dotnettools.csharp:** Die Microsoft-C#-Erweiterung bietet umfassende Unterstützung für die Entwicklung in C# (einschließlich Features wie unter anderem IntelliSense, Linten, Debuggen, Codenavigation, Codeformatierung, Refactoring, Variablen-Explorer und Test-Explorer).
|
||||
- **forwardPorts:** Alle hier aufgeführten Ports werden automatisch weitergeleitet. Weitere Informationen findest du unter [Weiterleiten von Ports in Codespaces](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace).
|
||||
- **postCreateCommand**: Verwende dies, um Befehle auszuführen, die nicht in der Dockerfile-Datei definiert sind, nachdem dein Codespace erstellt wurde.
|
||||
- **remoteUser:** Du führst Vorgänge standardmäßig als vscode-Benutzer*in aus, du kannst diese Option aber auch auf das Stammverzeichnis festlegen.
|
||||
|
||||
#### Dockerfile
|
||||
|
||||
@@ -155,26 +159,26 @@ RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-d
|
||||
# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
|
||||
```
|
||||
|
||||
You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
|
||||
Du kannst das Dockerfile verwenden, um zusätzliche Containerebenen zum Definieren von Betriebssystempaketen, Knotenversionen oder globalen Paketen hinzuzufügen, die im Container enthalten sein sollen.
|
||||
|
||||
## Step 3: Modify your devcontainer.json file
|
||||
## Schritt 3: Bearbeiten der devcontainer.json-Datei
|
||||
|
||||
With your dev container configuration added and a basic understanding of what everything does, you can now make changes to customize your environment further. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
|
||||
Mit der hinzugefügten Entwicklungscontainerkonfiguration und einem grundlegenden Verständnis der Funktionen kannst du nun Änderungen vornehmen, um deine Umgebung weiter anzupassen. In diesem Beispiel fügen wir Eigenschaften hinzu, um Erweiterungen und deine Projektabhängigkeiten zu installieren, wenn der Codespace gestartet wird.
|
||||
|
||||
1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
|
||||
1. Wähle im Explorer die `devcontainer.json`-Datei aus der Struktur aus, und öffne sie. Möglicherweise musst du den Ordner `.devcontainer` erweitern, um diese anzuzeigen.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
|
||||
2. Aktualisiere die `extensions`-Liste in deiner `devcontainer.json`-Datei, um einige Erweiterungen hinzuzufügen, die beim Arbeiten mit deinem Projekt nützlich sind.
|
||||
|
||||
```json{:copy}
|
||||
"extensions": [
|
||||
"ms-dotnettools.csharp",
|
||||
"streetsidesoftware.code-spell-checker",
|
||||
],
|
||||
"ms-dotnettools.csharp",
|
||||
"streetsidesoftware.code-spell-checker",
|
||||
],
|
||||
```
|
||||
|
||||
3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
|
||||
3. Hebe die Auskommentierung für `postCreateCommand` auf, um Abhängigkeiten als Teil des Codespace-Einrichtungsvorgangs wiederherzustellen.
|
||||
|
||||
```json{:copy}
|
||||
// Use 'postCreateCommand' to run commands after the container is created.
|
||||
@@ -187,26 +191,26 @@ With your dev container configuration added and a basic understanding of what ev
|
||||
|
||||
{% data reusables.codespaces.rebuild-reason %}
|
||||
|
||||
5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
|
||||
5. Stelle sicher, dass deine Änderungen erfolgreich angewendet wurden, indem du überprüfst, ob die Erweiterung „Code Spell Checker“ installiert wurde.
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 4: Run your application
|
||||
## Schritt 4: Ausführen der Anwendung
|
||||
|
||||
In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application.
|
||||
Im vorherigen Abschnitt hast du `postCreateCommand` verwendet, um mehrere Pakete über den `dotnet restore`-Befehl zu installieren. Mit den jetzt installierten Abhängigkeiten kannst du die Anwendung ausführen.
|
||||
|
||||
1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
|
||||
1. Führe deine Anwendung aus, indem du `F5` drückst oder im Terminal `dotnet watch run` eingibst.
|
||||
|
||||
2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses.
|
||||
2. Wenn dein Projekt gestartet wird, sollte in der unteren rechten Ecke von {% data variables.product.prodname_vscode_shortname %} eine Popupbenachrichtigung angezeigt werden, die eine Aufforderung zum Herstellen einer Verbindung mit dem Port enthält, den dein Projekt verwendet.
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 5: Commit your changes
|
||||
## Schritt 5: Committen der Änderungen
|
||||
|
||||
{% data reusables.codespaces.committing-link-to-procedure %}
|
||||
|
||||
## Next steps
|
||||
## Nächste Schritte
|
||||
|
||||
You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_github_codespaces %}. Here are some additional resources for more advanced scenarios.
|
||||
Du solltest jetzt mit der Entwicklung deines C#-Projekts (.NET) in {% data variables.product.prodname_github_codespaces %} beginnen können. Im Folgenden findest du einige zusätzliche Ressourcen für erweiterte Szenarios:
|
||||
|
||||
{% data reusables.codespaces.next-steps-adding-devcontainer %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Codespaces logs
|
||||
intro: 'Overview of the logs used by {% data variables.product.prodname_github_codespaces %}.'
|
||||
title: GitHub Codespaces-Protokolle
|
||||
intro: 'Dieser Artikel bietet eine Übersicht über die von {% data variables.product.prodname_github_codespaces %} verwendeten Protokolle.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,50 +11,55 @@ topics:
|
||||
shortTitle: Codespaces logs
|
||||
redirect_from:
|
||||
- /codespaces/troubleshooting/codespaces-logs
|
||||
ms.openlocfilehash: f5cd482888f58f85a051bb9b6e2c5d7c026ed9a9
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159690'
|
||||
---
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
Information on {% data variables.product.prodname_github_codespaces %} is output to various logs:
|
||||
Informationen zu {% data variables.product.prodname_github_codespaces %} werden in verschiedenen Protokollen ausgegeben:
|
||||
|
||||
{% webui %}
|
||||
|
||||
- Codespace logs
|
||||
- Creation logs
|
||||
- Browser console logs (for the {% data variables.product.prodname_vscode_shortname %} web client)
|
||||
- Codespaceprotokolle
|
||||
- Erstellungsprotokolle
|
||||
- Browserkonsolenprotokolle (für den {% data variables.product.prodname_vscode_shortname %}-Webclient)
|
||||
|
||||
Extension logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}. Click the "{% data variables.product.prodname_vscode %}" tab above for details.
|
||||
Erweiterungsprotokolle sind verfügbar, wenn du {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} verwendest. Klicke oben auf die Registerkarte „{% data variables.product.prodname_vscode %}“, um weitere Informationen zu erhalten.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
- Codespace logs
|
||||
- Creation logs
|
||||
- Extension logs (for the {% data variables.product.prodname_vscode_shortname %} desktop application)
|
||||
- Codespaceprotokolle
|
||||
- Erstellungsprotokolle
|
||||
- Erweiterungsprotokolle (für die {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung)
|
||||
|
||||
Browser logs are available if you are using {% data variables.product.prodname_github_codespaces %} in your browser. Click the "Web browser" tab above for details.
|
||||
Browserprotokolle sind verfügbar, wenn du {% data variables.product.prodname_github_codespaces %} in deinem Browser verwendest. Klicke oben auf die Registerkarte „Webbrowser“, um weitere Informationen zu erhalten.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
- Codespace logs
|
||||
- Creation logs
|
||||
- Codespaceprotokolle
|
||||
- Erstellungsprotokolle
|
||||
|
||||
Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details.
|
||||
Weitere Protokolle sind verfügbar, wenn du {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} oder in deinem Webbrowser verwendest. Klicke auf die Registerkarten oben, um weitere Informationen zu erhalten.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
- Creation logs
|
||||
- Erstellungsprotokolle
|
||||
|
||||
Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details.
|
||||
Weitere Protokolle sind verfügbar, wenn du {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} oder in deinem Webbrowser verwendest. Klicke auf die Registerkarten oben, um weitere Informationen zu erhalten.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -62,10 +67,10 @@ Other logs are available if you are using {% data variables.product.prodname_git
|
||||
|
||||
{% data reusables.codespaces.codespace-logs %}
|
||||
|
||||
1. If you are using {% data variables.product.prodname_github_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
|
||||
1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
|
||||
1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
|
||||
1. If you are using {% data variables.product.prodname_github_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine.
|
||||
1. Wenn du {% data variables.product.prodname_github_codespaces %} im Browser verwendest, stelle sicher, dass du mit dem Codespace verbunden bist, den du debuggen möchtest.
|
||||
1. Öffne die {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und gib **Protokolle exportieren** ein. Wähle **Codespaces: Protokolle exportieren** in der Liste aus, um die Protokolle herunterzuladen.
|
||||
1. Lege fest, wo das ZIP-Archiv der Protokolle gespeichert werden soll, und klicke dann auf **Speichern** (Desktop) oder **OK** (Web).
|
||||
1. Wenn du {% data variables.product.prodname_github_codespaces %} im Browser verwendest, klicke in der Explorer-Ansicht mit der rechten Maustaste auf das ZIP-Archiv mit den Protokollen und dann mit der linken Maustaste auf **Herunterladen...** um es auf deinen lokalen Computer herunterzuladen.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -73,8 +78,8 @@ Other logs are available if you are using {% data variables.product.prodname_git
|
||||
|
||||
{% data reusables.codespaces.codespace-logs %}
|
||||
|
||||
1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
|
||||
1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
|
||||
1. Öffne die {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und gib **Protokolle exportieren** ein. Wähle **Codespaces: Protokolle exportieren** in der Liste aus, um die Protokolle herunterzuladen.
|
||||
1. Lege fest, wo das ZIP-Archiv der Protokolle gespeichert werden soll, und klicke dann auf **Speichern** (Desktop) oder **OK** (Web).
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -82,28 +87,28 @@ Other logs are available if you are using {% data variables.product.prodname_git
|
||||
|
||||
{% data reusables.codespaces.codespace-logs %}
|
||||
|
||||
Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode_shortname %} or in a browser.
|
||||
Derzeit kannst du nicht mit {% data variables.product.prodname_cli %} auf diese Protokolle zugreifen. Öffne den Codespace in {% data variables.product.prodname_vscode_shortname %} oder in einem Browser, um auf sie zuzugreifen.
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Creation logs
|
||||
## Erstellungsprotokolle
|
||||
|
||||
These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
|
||||
Diese Protokolle enthalten Informationen zum Container und zum Entwicklungscontainer sowie zu deren Konfiguration. Sie sind beim Debuggen von Konfigurations- und Setupproblemen hilfreich.
|
||||
|
||||
{% webui %}
|
||||
|
||||
1. Connect to the codespace you want to debug.
|
||||
2. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
|
||||
1. Stelle eine Verbindung mit dem Codespace her, den du debuggen möchtest.
|
||||
2. Öffne die {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und gib **Erstellungsprotokolle** ein. Wähle **Codespaces: Erstellungsprotokolle anzeigen** in der Liste aus, um die Datei `creation.log` zu öffnen.
|
||||
|
||||
If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
|
||||
Wenn du das Protokoll für den Support freigeben möchtest, kannst du den Text aus dem Erstellungsprotokoll in einen Text-Editor kopieren und die Datei lokal speichern.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
|
||||
Öffne die {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und gib **Erstellungsprotokolle** ein. Wähle **Codespaces: Erstellungsprotokolle anzeigen** in der Liste aus, um die Datei `creation.log` zu öffnen.
|
||||
|
||||
If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
|
||||
Wenn du das Protokoll für den Support freigeben möchtest, kannst du den Text aus dem Erstellungsprotokoll in einen Text-Editor kopieren und die Datei lokal speichern.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -111,15 +116,15 @@ If you want to share the log with support, you can copy the text from the creati
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
|
||||
Zum Anzeigen des Erstellungsprotokolls verwendest du den Unterbefehl `gh codespace logs`. Nachdem du den Befehl eingegeben hast, kannst du deine Auswahl in der Liste der Codespaces treffen, die angezeigt wird.
|
||||
|
||||
```shell
|
||||
gh codespace logs
|
||||
```
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
|
||||
Weitere Informationen zu diesem Befehl findest du [im {% data variables.product.prodname_cli %}-Leitfaden](https://cli.github.com/manual/gh_codespace_logs).
|
||||
|
||||
If you want to share the log with support, you can save the output to a file:
|
||||
Wenn du das Protokoll für den Support freigeben möchtest, kannst du die Ausgabe in einer Datei speichern:
|
||||
|
||||
```shell
|
||||
gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
|
||||
@@ -129,44 +134,44 @@ gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
|
||||
|
||||
{% vscode %}
|
||||
|
||||
## Extension logs
|
||||
## Erweiterungsprotokolle
|
||||
|
||||
These logs are available for {% data variables.product.prodname_vscode_shortname %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_github_codespaces %} extension or {% data variables.product.prodname_vscode_shortname %} editor are having issues that prevent creation or connection.
|
||||
Diese Protokolle sind nur für Benutzer*innen der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung verfügbar. Sie sind nützlich, wenn du vermutest, dass Probleme mit der {% data variables.product.prodname_github_codespaces %}-Erweiterung oder dem {% data variables.product.prodname_vscode_shortname %}-Editor die Erstellung oder das Herstellen der Verbindung verhindern.
|
||||
|
||||
1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette.
|
||||
1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer.
|
||||
1. Öffne in {% data variables.product.prodname_vscode_shortname %} die Befehlspalette.
|
||||
1. Gib **Protokolle** ein, und wähle **Entwickler: Erweiterungsprotokolle öffnen** in der Liste aus, um den Erweiterungsprotokollordner im Datei-Explorer deines Systems zu öffnen.
|
||||
|
||||
From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode_shortname %}. You will see logs for {% data variables.product.prodname_github_codespaces %}, {% data variables.product.prodname_dotcom %} Authentication, and Git, in addition to any other extensions you have enabled.
|
||||
In dieser Ansicht kannst du auf Protokolle zugreifen, die von den verschiedenen Erweiterungen generiert wurden, die du in {% data variables.product.prodname_vscode_shortname %} verwendest. Es werden Protokolle für {% data variables.product.prodname_github_codespaces %}, {% data variables.product.prodname_dotcom %} Authentication und Git sowie für alle anderen Erweiterungen, die du aktiviert hast, angezeigt.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Browser console logs
|
||||
## Browserkonsolenprotokolle
|
||||
|
||||
These logs are useful only if you want to debug problems with using {% data variables.product.prodname_github_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_github_codespaces %}.
|
||||
Diese Protokolle sind nur hilfreich, wenn du Probleme bei der Verwendung von {% data variables.product.prodname_github_codespaces %} im Browser debuggen möchtest. Sie sind nützlich zum Debuggen von Problemen bei der Erstellung und beim Herstellen einer Verbindung mit {% data variables.product.prodname_github_codespaces %}.
|
||||
|
||||
1. In the browser window for the codespace you want to debug, open the developer tools window.
|
||||
1. Display the "Console" tab and click **errors** in the left sidebar to show only the errors.
|
||||
1. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine.
|
||||
|
||||
1. Öffne das Fenster mit den Entwicklertools in dem Browserfenster für den Codespace, den du debuggen möchtest.
|
||||
1. Wechsle zur Registerkarte „Konsole“, und klicke in der linken Randleiste auf **Fehler**, um nur die Fehler anzuzeigen.
|
||||
1. Klicke im Protokollbereich auf der rechten Seite mit der rechten Maustaste, und wähle **Speichern unter** aus, um eine Kopie der Fehler auf deinem lokalen Computer zu speichern.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
|
||||
1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the log icon.
|
||||
1. Klicke im {% data variables.product.prodname_github_codespaces %}-Toolfenster auf das Protokollsymbol.
|
||||
|
||||
|
||||
|
||||
|
||||
## JetBrains logs
|
||||
## JetBrains-Protokolle
|
||||
|
||||
You can download logs for the remote JetBrains IDE and the local client application by going to the **Help** menu in the JetBrains client application and clicking **Collect Host and Client Logs**.
|
||||
Du kannst Protokolle für die JetBrains-Remote-IDE und die lokale Clientanwendung herunterladen, indem du in der JetBrains-Clientanwendung zum Menü **Help** (Hilfe) navigierst und auf **Collect Host and Client Logs** (Host- und Clientprotokolle sammeln) klickst.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
## Further reading
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
|
||||
- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)"
|
||||
- „[Überprüfen der Überwachungsprotokolle deiner Organisation für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)“
|
||||
- [Überprüfen deiner Sicherheitsprotokolle für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Troubleshooting creation and deletion of codespaces
|
||||
intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.'
|
||||
title: Problembehandlung beim Erstellen und Löschen von Codespaces
|
||||
intro: 'In diesem Artikel findest du Schritte zur Behandlung gängiger Probleme, die beim Erstellen oder Löschen von Codespaces auftreten können, einschließlich Speicher- und Konfigurationsproblemen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -8,89 +8,94 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Creation and deletion
|
||||
ms.openlocfilehash: 09c3a73ec5e41f0170f1d3cd66df139bb2a497e5
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158693'
|
||||
---
|
||||
## Erstellen von Codespaces
|
||||
|
||||
## Creating codespaces
|
||||
### Kein Zugriff zum Erstellen eines Codespace
|
||||
{% data variables.product.prodname_github_codespaces %} ist nicht für alle Repositorys verfügbar. Wenn die Optionen zum Erstellen eines Codespace nicht angezeigt werden, ist {% data variables.product.prodname_github_codespaces %} für dieses Repository eventuell nicht verfügbar. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#access-to-codespaces).
|
||||
|
||||
### No access to create a codespace
|
||||
{% data variables.product.prodname_github_codespaces %} is not available for all repositories. If the options for creating a codespace are not displayed, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#access-to-codespaces)."
|
||||
Vorausgesetzt, du hast noch verbleibende monatliche enthaltene Nutzung von {% data variables.product.prodname_github_codespaces %} in deinem persönlichen Konto oder eine Zahlungsmethode sowie ein Ausgabenlimit eingerichtet, kannst du Codespaces für öffentliche Repositorys erstellen. Du kannst jedoch nur dann einen Codespace für ein privates Repository erstellen, wenn du Änderungen an das Repository pushen oder das Repository forken kannst.
|
||||
|
||||
Provided you have remaining monthly included usage of {% data variables.product.prodname_github_codespaces %} on your personal account, or you have set up a payment method and a spending limit, you will be able to create codespaces for public repositories. However, you can only create a codespace for a private repository if you can push changes to the repository, or you can fork the repository.
|
||||
Weitere Informationen zur enthaltenen Nutzung bei persönlichen Konten und zum Festlegen eines Ausgabenlimits findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces) und [Verwalten von Ausgabenlimits für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces).
|
||||
|
||||
For more information about included usage for personal accounts, and setting a spending limit, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)" and "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
### Codespace wird beim Erstellen nicht geöffnet.
|
||||
|
||||
### Codespace does not open when created
|
||||
Du erstellst einen Codespace, aber dieser wird nicht geöffnet:
|
||||
|
||||
If you create a codespace and it does not open:
|
||||
1. Versuche, die Seite neu zu laden, falls ein Zwischenspeicherungs- oder Berichtsproblem aufgetreten ist.
|
||||
2. Navigiere zur {% data variables.product.prodname_github_codespaces %}-Seite (https://github.com/codespaces ), und überprüfe, ob der neue Codespace hier aufgeführt ist. Der Prozess hat den Codespace vielleicht erfolgreich erstellt, hat dies jedoch nicht an deinen Browser gemeldet. Wenn der neue Codespace aufgelistet ist, kannst du ihn direkt über diese Seite öffnen.
|
||||
3. Versuche erneut, den Codespace für das Repository zu erstellen, um einen vorübergehenden Kommunikationsfehler auszuschließen.
|
||||
|
||||
1. Try reloading the page in case there was a caching or reporting problem.
|
||||
2. Go to your {% data variables.product.prodname_github_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page.
|
||||
3. Retry creating the codespace for the repository to rule out a transient communication failure.
|
||||
Wenn du immer noch keinen Codespace für ein Repository erstellen kannst, in dem {% data variables.product.prodname_github_codespaces %} verfügbar ist, {% data reusables.codespaces.contact-support %}.
|
||||
|
||||
If you still cannot create a codespace for a repository where {% data variables.product.prodname_github_codespaces %} is available, {% data reusables.codespaces.contact-support %}
|
||||
### Fehler beim Erstellen des Codespace
|
||||
|
||||
### Codespace creation fails
|
||||
|
||||
If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
|
||||
Wenn beim Erstellen eines Codespace ein Fehler auftritt, ist dies wahrscheinlich auf ein temporäres Infrastrukturproblem in der Cloud zurückzuführen, z. B. auf ein Problem beim Bereitstellen eines virtuellen Computers für den Codespace. Ein weniger häufiger Grund für Fehler ist, wenn das Erstellen des Containers länger als eine Stunde dauert. In diesem Fall wird der Build abgebrochen, und für das Erstellen des Codespace wird ein Fehler ausgegeben.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
**Hinweis:** Ein Codespace, der nicht erfolgreich erstellt wurde, kann nie verwendet werden und sollte gelöscht werden. Weitere Informationen findest du unter [Löschen eines Codespace](/codespaces/developing-in-codespaces/deleting-a-codespace).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you create a codespace and the creation fails:
|
||||
Wenn du einen Codespace erstellst und dabei ein Fehler auftritt, führe Folgendes durch:
|
||||
|
||||
1. Check {% data variables.product.prodname_dotcom %}'s [Status page](https://githubstatus.com) for any active incidents.
|
||||
1. Go to [your {% data variables.product.prodname_github_codespaces %} page](https://github.com/codespaces), delete the codespace, and create a new codespace.
|
||||
1. If the container is building, look at the logs that are streaming and make sure the build is not stuck. A container build that takes longer than one hour will be canceled, resulting in a failed creation.
|
||||
1. Überprüfe die [Statusseite](https://githubstatus.com) von {% data variables.product.prodname_dotcom %} auf aktive Incidents.
|
||||
1. Wechsle zu [deiner {% data variables.product.prodname_github_codespaces %}-Seite](https://github.com/codespaces), lösche den Codespace, und erstelle einen neuen Codespace.
|
||||
1. Wenn der Container erstellt wird, sieh dir die Protokolle an, die gestreamt werden, und stelle sicher, dass der Build nicht hängen geblieben ist. Ein Containerbuild, der länger als eine Stunde dauert, wird abgebrochen, was zu einem Fehler bei der Erstellung führt.
|
||||
|
||||
One common scenario where this could happen is if you have a script running that is prompting for user input and waiting for an answer. If this is the case, remove the interactive prompt so that the build can complete non-interactively.
|
||||
Dieses Szenario tritt häufig auf, wenn ein Skript ausgeführt wird, das zur Benutzereingabe auffordert und auf eine Antwort wartet. Wenn dies der Fall ist, entferne die interaktive Eingabeaufforderung, damit der Build nicht-interaktiv abgeschlossen werden kann.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: To view the logs during a build:
|
||||
* In the browser, click **View logs.**
|
||||
**Hinweis**: So zeigst du die Protokolle während eines Builds an:
|
||||
* Klicke im Browser auf **Protokolle anzeigen**.
|
||||
|
||||
|
||||
|
||||
|
||||
* In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed.
|
||||
* Klicke in der VS Code-Desktopanwendung unter „Remoteverbindung einrichten“ auf **Codespace erstellen**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
2. Wenn das Erstellen eines Containers sehr lange dauert, solltest du Prebuilds verwenden, um das Erstellen von Codespaces zu beschleunigen. Weitere Informationen findest du unter [Konfigurieren von Prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds).
|
||||
|
||||
## Deleting codespaces
|
||||
## Löschen von Codespaces
|
||||
|
||||
A codespace can only be deleted by:
|
||||
* The person who created the codespace.
|
||||
* An organization owner for an organization-owned codespace.
|
||||
* Automatic deletion at the end of a retention period.
|
||||
Ein Codespace kann nur wie folgt gelöscht werden:
|
||||
* Durch den oder die Ersteller*in des Codespace
|
||||
* Durch einen oder eine Organisationsbesitzer*in im Fall eines organisationseigenen Codespace
|
||||
* Durch automatisches Löschen am Ende eines Aufbewahrungszeitraums
|
||||
|
||||
For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)" and "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
Weitere Informationen findest du unter [Löschen eines Codespace](/codespaces/developing-in-codespaces/deleting-a-codespace) und [Konfigurieren des automatischen Löschens deiner Codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces).
|
||||
|
||||
## Container storage
|
||||
## Containerspeicher
|
||||
|
||||
When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try running any of the following commands in the {% data variables.product.prodname_github_codespaces %} terminal to free up storage space.
|
||||
Beim Erstellen eines Codespace verfügt er über eine begrenzte Speichermenge, und im Laufe der Zeit ist es möglicherweise erforderlich, Speicherplatz freizugeben. Führe einen der folgenden Befehle im {% data variables.product.prodname_github_codespaces %}-Terminal aus, um Speicherplatz freizugeben.
|
||||
|
||||
- Remove packages that are no longer used by using `sudo apt autoremove`.
|
||||
- Clean the apt cache by using `sudo apt clean`.
|
||||
- See the top 10 largest files in the codespace with`sudo find / -printf '%s %p\n'| sort -nr | head -10`.
|
||||
- Delete unneeded files, such as build artifacts and logs.
|
||||
- Entferne mithilfe von `sudo apt autoremove` Pakete, die nicht mehr verwendet werden.
|
||||
- Bereinige den apt-Cache mithilfe von `sudo apt clean`.
|
||||
- Zeige die zehn größten Dateien im Codespace mit `sudo find / -printf '%s %p\n'| sort -nr | head -10` an.
|
||||
- Lösche nicht benötigte Dateien, z. B. Buildartefakte und Protokolle.
|
||||
|
||||
Some more destructive options:
|
||||
Einige destruktivere Optionen:
|
||||
|
||||
- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes).
|
||||
- Remove untracked files from working tree: `git clean -i`.
|
||||
- Entferne nicht verwendete Docker-Images, Netzwerke und Container mithilfe von`docker system prune`. (Füge `-a` an, wenn du alle Images entfernen möchtest, und `--volumes`, wenn du alle Volumes entfernen möchtest.)
|
||||
- Entferne nicht nachverfolgte Dateien aus der Arbeitsstruktur: `git clean -i`.
|
||||
|
||||
## Configuration
|
||||
## Konfiguration
|
||||
|
||||
{% data reusables.codespaces.recovery-mode %}
|
||||
|
||||
```
|
||||
This codespace is currently running in recovery mode due to a container error.
|
||||
```
|
||||
Review the creation logs and update the dev container configuration as needed. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)."
|
||||
Überprüfe die Erstellungsprotokolle, und aktualisiere nach Bedarf die Entwicklungscontainerkonfiguration. Weitere Informationen findest du unter „[{% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs)“.
|
||||
|
||||
You can then try restarting the codespace, or rebuilding the container. For more information on rebuilding the container, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
|
||||
Anschließend kannst du versuchen, den Codespace neu zu starten oder den Container neu zu erstellen. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
|
||||
@@ -0,0 +1,118 @@
|
||||
---
|
||||
title: Problembehandlung bei GitHub Codespaces-Clients
|
||||
shortTitle: Codespaces clients
|
||||
intro: 'In diesem Artikel findest du Informationen zum Behandeln von Problemen mit Clients, die du für {% data variables.product.prodname_github_codespaces %} verwendest.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/troubleshooting/troubleshooting-codespaces-clients
|
||||
ms.openlocfilehash: 682160b3b92960487c0709fc411fc2143d18f415
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159590'
|
||||
---
|
||||
{% jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
## Problembehandlung bei dem {% data variables.product.prodname_vscode %}-Webclient
|
||||
|
||||
Wenn bei der Verwendung von {% data variables.product.prodname_github_codespaces %} in einem Browser, der nicht auf Chromium basiert, Probleme auftreten, wechsle zu einem Chromium-basierten Browser wie Google Chrome oder Microsoft Edge. Alternativ kannst du das [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen)-Repository auf bekannte Browserprobleme überprüfen, indem du nach Issues suchst, die den Namen deines Browsers tragen, beispielsweise [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) oder [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari).
|
||||
|
||||
Wenn Probleme bei der Verwendung von {% data variables.product.prodname_github_codespaces %} in einem Browser auftreten, der auf Chromium basiert, kannst du überprüfen, ob ein anderes bekanntes Problem mit {% data variables.product.prodname_vscode_shortname %} im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen)-Repository auftritt.
|
||||
|
||||
### Unterschiede zum lokalen Arbeiten in {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
Wenn du einen Codespace in deinem Browser mit dem {% data variables.product.prodname_vscode_shortname %}-Webclient öffnest, wirst du einige Unterschiede gegenüber der Arbeit in einem lokalen Arbeitsbereich in der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung feststellen. Beispielsweise unterscheiden sich einige Tastenzuordnungen, oder sie fehlen, und einige Erweiterungen verhalten sich möglicherweise anders. Eine Zusammenfassung findest du unter [Bekannte Einschränkungen und Anpassungen](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
Du kannst nach bekannten Issues suchen und neue Issues über die {% data variables.product.prodname_vscode_shortname %}-Benutzeroberfläche im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces)-Repository protokollieren.
|
||||
|
||||
### {% data variables.product.prodname_vscode %} Insiders
|
||||
|
||||
{% data variables.product.prodname_vscode %} Insiders ist das am häufigsten verwendete Release von {% data variables.product.prodname_vscode_shortname %}. Es verfügt über alle aktuellen Features und Fehlerkorrekturen. Darin können jedoch gelegentlich neue Probleme auftreten, die zu einem fehlerhaften Build führen.
|
||||
|
||||
Wenn du einen Insiders-Build verwendest und Fehler auftreten, solltest du zu {% data variables.product.prodname_vscode %} Stable wechseln und es erneut versuchen.
|
||||
|
||||
Klicke unten links im Editor auf {% octicon "gear" aria-label="The manage icon" %}, und wähle **Zur stabilen Version wechseln...** aus. Wenn der {% data variables.product.prodname_vscode_shortname %}-Webclient nicht lädt oder das {% octicon "gear" aria-label="The manage icon" %}-Symbol nicht angezeigt wird, kannst du den Wechsel zu {% data variables.product.prodname_vscode %} Stable erzwingen, indem du `?vscodeChannel=stable` an deine Codespace-URL anfügst und den Codespace unter dieser URL lädst.
|
||||
|
||||
Wenn das Problem in {% data variables.product.prodname_vscode %} Stable nicht behoben wurde, suche nach bekannten Issues, und protokolliere bei Bedarf über die {% data variables.product.prodname_vscode_shortname %}-Benutzeroberfläche einen neuen Issue im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces)-Repository.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
## Behandeln von Problemen mit {% data variables.product.prodname_vscode_shortname %}
|
||||
|
||||
Wenn du einen Codespace in der {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung öffnest, wirst du vielleicht einige Unterschiede zur Arbeit in einem lokalen Arbeitsbereich feststellen, aber die Benutzeroberfläche sollte ähnlich sein.
|
||||
|
||||
Wenn Probleme auftreten, kannst du nach bekannten Issues suchen und neue Issues über die {% data variables.product.prodname_vscode_shortname %}-Benutzeroberfläche im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces)-Repository protokollieren.
|
||||
|
||||
### {% data variables.product.prodname_vscode %} Insiders
|
||||
|
||||
{% data variables.product.prodname_vscode %} Insiders ist das am häufigsten verwendete Release von {% data variables.product.prodname_vscode_shortname %}. Es verfügt über alle aktuellen Features und Fehlerkorrekturen. Darin können jedoch gelegentlich neue Probleme auftreten, die zu einem fehlerhaften Build führen.
|
||||
|
||||
Wenn du einen Insiders-Build verwendest und Fehler auftreten, solltest du zu {% data variables.product.prodname_vscode %} Stable wechseln und es erneut versuchen.
|
||||
|
||||
Du kannst zu {% data variables.product.prodname_vscode %} Stable wechseln, indem du die {% data variables.product.prodname_vscode %} Insiders-Anwendung schließt, die {% data variables.product.prodname_vscode %} Stable-Anwendung öffnest und deinen Codespace erneut öffnest.
|
||||
|
||||
Wenn das Problem in {% data variables.product.prodname_vscode %} Stable nicht behoben wurde, suche nach bekannten Issues, und protokolliere bei Bedarf über die {% data variables.product.prodname_vscode_shortname %}-Benutzeroberfläche einen neuen Issue im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces)-Repository.
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
{% jetbrains %}
|
||||
|
||||
## Problembehandlung bei JetBrains-IDEs
|
||||
|
||||
### Leistungsprobleme
|
||||
|
||||
Ein {% data variables.product.prodname_github_codespaces %}-Computertyp mit mindestens vier Kernen wird für die Ausführung einer der JetBrains-IDEs empfohlen. Weitere Informationen zu Computertypen findest du unter [Ändern des Computertyps für deinen Codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace).
|
||||
|
||||
Wenn du einen Computer mit vier oder mehr Kernen verwendest und die Leistung in JetBrains beeinträchtigt erscheint, musst du möglicherweise die maximale Java-Heapgröße erhöhen.
|
||||
|
||||
Es wird empfohlen, die maximale Heapgröße auf einen Wert zwischen 2862 MiB (3 GB) und 60 % des RAM des Remotehosts festzulegen.
|
||||
|
||||
Im Folgenden findest du einige Anhaltspunkte für den Anfang, die du je nach Größe der Codebasis und dem für deine Anwendung benötigten Arbeitsspeicher anpassen kannst. Wenn du beispielsweise über eine große oder komplizierte Codebasis verfügst, musst du die Heapgröße möglicherweise weiter erhöhen. Wenn du über eine größere Anwendung verfügst, kannst du eine niedrigere Heapgröße festlegen, um mehr Arbeitsspeicher für die Anwendung zu erhalten.
|
||||
|
||||
| Computertyp | Maximale Heapgröße |
|
||||
| -------------- | ----------------- |
|
||||
| Vier Kerne | 3GB |
|
||||
| Acht Kerne | 4 GB |
|
||||
| 16 oder 32 Kerne | 8 GB |
|
||||
|
||||
1. Klicke links neben der Navigationsleiste oben im Anwendungsfenster auf den Namen des Codespaces.
|
||||
|
||||
|
||||
|
||||
1. Notiere dir auf der Registerkarte „Leistung“ die Details zu CPU-Auslastung und Arbeitsspeicher. Diese geben an, ob der Computer überlastet ist.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf die Registerkarte „Einstellungen“, und bearbeite die Heapgröße, und erhöhe sie auf nicht mehr als 60 % des verfügbaren Arbeitsspeichers für deinen Codespace.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf **Speichern und neu starten**.
|
||||
|
||||
### SSH-Verbindungsprobleme
|
||||
|
||||
Um eine Verbindung über den SSH-Server herzustellen, der in deinem Codespace ausgeführt wird, musst du über einen SSH-Schlüssel in deinem `~/.ssh`-Verzeichnis (macOS und Linux) oder `%HOMEPATH%\.ssh`-Verzeichnis (Windows) verfügen, der deinem {% data variables.product.prodname_dotcom %}-Konto bereits hinzugefügt wurde. Wenn du keine Schlüssel in diesem Verzeichnis hast, generiert {% data variables.product.prodname_cli %} Schlüssel für dich. Weitere Informationen findest du unter [Hinzufügen eines neuen SSH-Schlüssels zu deinem {% data variables.product.prodname_dotcom %}-Konto](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account?platform=windows&tool=webui).
|
||||
|
||||
Wenn Probleme bei der Schlüsselüberprüfung auftreten, aktualisiere deine Version von {% data variables.product.prodname_cli %}. Weitere Informationen findest du in den [Upgradeanweisungen](https://github.com/cli/cli#installation) in der INFODATEI für {% data variables.product.prodname_cli %}.
|
||||
|
||||
### JetBrains-IDE-Probleme
|
||||
|
||||
Hilfe zu Problemen, die speziell die von dir verwendete JetBrains-IDE oder die JetBrains Gateway-Anwendung betreffen, findest du unter [Produktsupport](https://www.jetbrains.com/support/) auf der JetBrains-Website.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Migrieren von {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'Du kannst deine {% data variables.projects.projects_v1_board %}s in die neue Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren.'
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,53 +10,57 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109688'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Hinweise:**
|
||||
|
||||
- Wenn das Projekt, das du migrierst, mehr als 1.200 Elemente enthält, werden offene Issues priorisiert, gefolgt von offenen Pull Requests und dann Hinweisen. Der verbleibende Platz wird für geschlossene Issues sowie gemergte und geschlossene Pull Requests genutzt. Elemente, die aufgrund dieses Grenzwerts nicht migriert werden können, werden ins Archiv verschoben. Wenn der Archivgrenzwert von 10.000 Elementen erreicht ist, werden keine weiteren Elemente migriert.
|
||||
- Hinweiskarten werden in Issueentwürfe konvertiert, der Inhalt wird im Textkörper des Issueentwurfs gespeichert. Wenn Informationen fehlen sollten, mache alle verborgenen Felder sichtbar. Weitere Informationen findest du unter [Anzeigen und Ausblenden von Feldern](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields).
|
||||
- Automatisierungen werden nicht migriert.
|
||||
- Selektierung, Archiv und Aktivität werden nicht migriert.
|
||||
- Nach der Migration bleiben das neue migrierte Projekt und das alte Projekt nicht mehr synchronisiert.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Informationen zur Projektmigration
|
||||
|
||||
Du kannst deine Projektboards zur neuen Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren und Tabellen, mehrere Ansichten, neue Automatisierungsoptionen und leistungsstarke Feldtypen ausprobieren. Weitere Informationen findest du unter [Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
|
||||
|
||||
## Migrieren des Projektboards einer Organisation
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. Klicke auf der linken Seite auf **Projekte (klassisch)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrieren eines Benutzerprojektboards
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. Klicke oben auf deiner Profilseite in der Hauptnavigation auf {% octicon "project" aria-label="The project board icon" %} **Projekte**.
|
||||
|
||||
1. Klicke über der Liste der Projekte auf **Projekte (klassisch)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrieren eines Repositoryprojektboards
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Projekte auf Repositoryebene werden von {% data variables.projects.projects_v2_caps %} nicht unterstützt. Wenn du ein Repositoryprojektboard migrierst, wird es entweder in die Organisation oder in das persönliche Konto migriert, zu dem das Repositoryprojekt gehört, und das migrierte Projekt wird an das ursprüngliche Repository angeheftet.
|
||||
**Notes:**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. Klicke unter dem Namen des Repositorys auf {% octicon "project" aria-label="The project board icon" %} **Projekte**.
|
||||
|
||||
1. Klicke auf **Projekte (klassisch)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
## About project migration
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
## Migrating an organization project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: Informationen zu den Feldern „Nachverfolgungen“ und „Nachverfolgt von“
|
||||
shortTitle: About Tracks and Tracked-by fields
|
||||
intro: Du kannst die Teilaufgaben der Issues in deinen Projekten anzeigen.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2-tasklists
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 74cd26d20882a00ac8c7ac1d109cc6810286cec6
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159658'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
Du kannst die Felder „Nachverfolgungen“ und „Nachverfolgt von“ für deine Projekte aktivieren, um die Beziehungen zwischen deinen Issues anzuzeigen, während du Teilaufgaben zu Aufgabenlisten hinzufügst. Weitere Informationen zum Erstellen von Issuehierarchien in Aufgabenlisten findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/about-tasklists).
|
||||
|
||||
Das Feld „Nachverfolgt von“ kann verwendet werden, um Elemente für eine Ansicht zu gruppieren, die die Teilaufgaben der einzelnen Issues und die für deren Abschluss erforderlichen Arbeiten klar zeigt. Weitere Informationen findest du unter [Gruppieren nach Feldwerten im Tabellenlayout](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#grouping-by-field-values-in-table-layout).
|
||||
|
||||
Außerdem kannst du nach dem Feld „Nachverfolgt von“ filtern, um nur Elemente anzuzeigen, die durch bestimmte Issues nachverfolgt werden. Beginne entweder mit dem Eingeben von „tracked-by“, und wähle ein Issue aus der Liste aus, oder gib den Filter unten vollständig ein, wenn du das Repository und die Issuenummer kennst.
|
||||
|
||||
```
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
Um den Filter zu verwenden, ersetze `<OWNER>` durch den Repositorybesitzer, `<REPO>` durch den Repositorynamen und `<ISSUE NUMBER>` durch die Issuenummer. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
|
||||
|
||||
### Aktivieren des Felds „Nachverfolgt von“
|
||||
|
||||
Du kannst das Feld „Nachverfolgt von“ aktivieren, um zu sehen, welche Issues ein Element in deinem Projekt nachverfolgen.
|
||||
|
||||
1. Klicke in der Tabellenansicht im Feld ganz rechts auf {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
|
||||
1. Klicke unter „Verborgene Felder“ auf **Nachverfolgt von**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Aktivieren des Felds „Nachverfolgungen“
|
||||
|
||||
Du kannst das Feld „Nachverfolgungen“ aktivieren, um zu sehen, welche anderen Issues ein Element in deinem Projekt nachverfolgt.
|
||||
|
||||
1. Klicke in der Tabellenansicht im Feld ganz rechts auf {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
|
||||
1. Klicke unter „Verborgene Felder“ auf **Nachverfolgungen**.
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: Umbenennen benutzerdefinierter Felder
|
||||
intro: 'Hier erfährst du mehr über das Umbenennen bereits vorhandener benutzerdefinierter Felder in deinem {% data variables.projects.project_v2 %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
redirect_from:
|
||||
- /issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields
|
||||
ms.openlocfilehash: 45520fab579af228685443e0aa9ab563289325f1
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159741'
|
||||
---
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Klicke auf den Namen des benutzerdefinierten Felds, das du umbenennen möchtest.
|
||||
|
||||
1. Gib unter „Feldname“ den neuen Namen für das Feld ein.
|
||||
|
||||
1. Drücke die <kbd>Eingabetaste</kbd>, um die Änderungen zu speichern.
|
||||
@@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Informationen zur Codesuche (Betaversion) auf GitHub
|
||||
intro: 'Mit der neuen Codesuche (Betaversion) kannst du überall auf GitHub Code durchsuchen, durch diesen navigieren und ihn verstehen.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: github-code-search
|
||||
topics:
|
||||
- GitHub search
|
||||
ms.openlocfilehash: 8bf3232e87de2fc773f69bf5047e75ab0e52c7e2
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160225'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** {% data reusables.search.code-search-code-view-beta-note %}
|
||||
|
||||
{% data reusables.search.code-view-link %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Informationen zur neuen Codesuche (Betaversion)
|
||||
|
||||
Mit der neuen Codesuche (Betaversion) kannst du schnell auf {% data variables.product.prodname_dotcom_the_website %} deinen eigenen Code, den deines Teams und den Code der Open-Source-Community durchsuchen, durch diesen Code navigieren und ihn verstehen. Dieses Suchmodul ist so konzipiert, dass es skalierbar und codeorientiert ist und das Durchsuchen von Code überall auf GitHub mithilfe von regulären Ausdrücken, booleschen Operatoren, speziellen Qualifizierern und der Symbolsuche unterstützt. Weitere Informationen zur Syntax für die neue Codesuche (Betaversion) findest du unter [Grundlegendes zur Syntax für die Codesuche (Betaversion) auf GitHub](/search-github/github-code-search/understanding-github-code-search-syntax).
|
||||
|
||||
Neben dem neuen Suchmodul für Code umfasst die Codesuche (Betaversion) auch neue Features für die Suchschnittstelle auf {% data variables.product.prodname_dotcom_the_website %}, z. B. Vorschläge, Vervollständigungen und die Möglichkeit, deine Suchen zu speichern. Dank der neuen Suchschnittstelle kannst du das Gesuchte schneller und leichter finden. Weitere Informationen findest du unter [Verwenden der Codesuche (Betaversion) auf GitHub](/search-github/github-code-search/using-github-code-search).
|
||||
|
||||
{% data reusables.search.non-code-search-explanation %}
|
||||
|
||||
Die neue Codesuche (Betaversion) ist eng mit einer umgestalteten Codeansicht (Betaversion) auf {% data variables.product.prodname_dotcom_the_website %} integriert. {% data reusables.search.code-view-link %}
|
||||
|
||||
Wenn du Zugriff auf die neue Codesuche (Betaversion) und die neue Codeansicht erhalten möchtest, kannst du dich für die [Warteliste](https://github.com/features/code-search-code-view/signup) registrieren.
|
||||
|
||||
## Aktivieren und Deaktivieren der neuen Codesuche und Codeansicht (Betaversion)
|
||||
|
||||
{% data reusables.search.enabling-and-disabling-code-search-and-view-beta %}
|
||||
|
||||
## Einschränkungen
|
||||
|
||||
Wir haben bereits viele öffentliche Repositorys für die neue Codesuche (Betaversion) indiziert und werden auch noch weitere indizieren. Darüber hinaus werden die privaten Repositorys von GitHub-Benutzer*innen, die die Betaversion nutzen, indiziert und für Betabenutzer*innen durchsuchbar gemacht, die bereits Zugriff auf diese privaten Repositorys auf GitHub.com haben. Sehr große Repositorys werden derzeit jedoch möglicherweise noch nicht indiziert, und es wird auch nicht alles an Code indiziert.
|
||||
|
||||
Derzeit gelten die folgenden Einschränkungen für indizierten Code:
|
||||
- Übernommener und generierter Code ist ausgenommen (wird mit [Enry](https://github.com/go-enry/go-enry) ermittelt).
|
||||
- Leere Dateien und Dateien mit einer Größe von mehr als 350 KB sind ausgenommen.
|
||||
- Nur UTF-8-codierte Dateien sind eingeschlossen.
|
||||
- Sehr große Repositorys werden möglicherweise nicht indiziert.
|
||||
|
||||
Derzeit wird die Suche nach Code nur im Standardbranch eines Repositorys unterstützt.
|
||||
|
||||
Die Anzahl der Ergebnisse für eine Suche mit der neuen Codesuche (Betaversion) ist auf 100 Ergebnisse (10 Seiten) beschränkt. Das Sortieren von Ergebnissen für die Codesuche wird derzeit nicht unterstützt. Diese Einschränkung gilt nur für das Durchsuchen von Code mit der neuen Codesuche (Betaversion) und nicht für andere Arten von Suchen.
|
||||
|
||||
Die neue Codesuche (Beta) unterstützt das Suchen nach Symboldefinitionen in Code, z. B. Funktions- oder Klassendefinitionen, mithilfe des Qualifizierers `symbol:`. Beachte jedoch, dass mit dem Qualifizierer `symbol:` nur nach Definitionen und nicht nach Verweisen gesucht wird und noch nicht alle Symboltypen und Sprachen vollständig unterstützt werden. Eine Liste der unterstützten Sprachen findest du unter [Qualifizierer „symbol:“](/search-github/github-code-search/understanding-github-code-search-syntax#symbol-qualifier).
|
||||
|
||||
## Feedback und Support
|
||||
|
||||
In unserem [Diskussionsforum](https://github.com/orgs/community/discussions/categories/code-search-and-navigation) kannst du Feedback zur neuen Codesuche (Betaversion) anzeigen und geben.
|
||||
@@ -0,0 +1,81 @@
|
||||
---
|
||||
title: Verwenden der Codesuche (Betaversion) auf GitHub
|
||||
intro: 'In der upgegradeten Suchschnittstelle kannst du Vorschläge, Vervollständigungen und gespeicherte Suchen verwenden, um auf {% data variables.product.prodname_dotcom_the_website %} schnell zu finden, wonach du suchst.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: github-code-search
|
||||
topics:
|
||||
- GitHub search
|
||||
ms.openlocfilehash: 7578dd05f251b1df23fbd64c63d04e533f7fa9ef
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160201'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** {% data reusables.search.code-search-code-view-beta-note %}
|
||||
|
||||
{% data reusables.search.code-search-link %} {% data reusables.search.code-view-link %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Informationen zur Verwendung der neuen Codesuche (Betaversion)
|
||||
|
||||
Sobald du Zugriff auf die Betaversion der neuen Codesuche hast, indiziert GitHub alle Repositorys, deren Besitzer*in du bist, sowie alle Repositorys in Organisationen, deren Mitglied du bist, unabhängig davon, ob es sich um öffentliche, private oder interne Repositorys handelt. Dies bedeutet, dass du neben den öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %}, die bereits indiziert sind, auch alle deine Repositorys durchsuchen kannst. Nur Benutzer*innen mit der Berechtigung zum Anzeigen deines Codes auf {% data variables.product.prodname_dotcom_the_website %} können deinen Code in Suchergebnissen sehen. Forks werden genauso indiziert und sind genauso durchsuchbar wie andere Repositorys.
|
||||
|
||||
Nicht der gesamte Code wird indiziert. Außerdem kannst du derzeit nur die Standardbranches von Repositorys durchsuchen. Weitere Informationen zu bekannten Einschränkungen findest du unter [Informationen zur Codesuche (Betaversion) auf GitHub](/search-github/github-code-search/about-github-code-search#limitations).
|
||||
|
||||
Die Betaversion der neuen Codesuche ist in die Betaversion der neuen Codeansicht integriert. {% data reusables.search.code-view-link %}
|
||||
|
||||
## Verwenden der Suchleiste
|
||||
|
||||
Neben dem neuen Suchmodul für Code umfasst die Betaversion auch eine upgegradete Suchschnittstelle auf {% data variables.product.prodname_dotcom_the_website %}. Wenn du Vorschläge, Vervollständigungen und gespeicherte Suchen nutzt, kannst du das Gesuchte oft schnell finden, ohne dass du die Abfrage vollständig eintippen oder die Suchergebnisseite anzeigen musst.
|
||||
|
||||
Weitere Informationen zur Suchsyntax für die neue Codesuche (Betaversion) findest du unter [Grundlegendes zur Syntax für die Codesuche (Betaversion) auf GitHub](/search-github/github-code-search/understanding-github-code-search-syntax).
|
||||
|
||||
{% data reusables.search.non-code-search-explanation %}
|
||||
|
||||
1. Klicke im oberen Navigationsbereich von {% data variables.product.prodname_dotcom_the_website %} auf die Suchleiste.
|
||||
1. Unter der Suchleiste wird nun eine nach Kategorien sortierte Liste mit Vorschlägen angezeigt, die die letzten Suchen enthält sowie vorgeschlagene Repositorys, Teams und Projekte, auf die du Zugriff hast. Du kannst auch eine Liste der von dir erstellten gespeicherten Suchen anzeigen. Weitere Informationen zu gespeicherten Suchen findest du unter [Erstellen und Verwalten gespeicherter Suchen](#creating-and-managing-saved-searches).
|
||||
|
||||
|
||||
|
||||
Wenn du auf einen der Vorschläge klickst, wirst du direkt zu der Seite für diesen Vorschlag weitergeleitet (z. B. zum Repository oder zur Projektseite). Wenn du auf eine der letzten Suchen oder eine gespeicherte Suche klickst, wird je nach Art der Suche entweder die Suchabfrage in der Suchleiste angezeigt oder du wirst zur Suchergebnisseite für den jeweiligen Suchbegriff weitergeleitet.
|
||||
|
||||
1. Sobald du beginnst, eine Suchabfrage einzutippen, wird dir eine Liste mit passenden Vervollständigungen und Vorschlägen für deine Abfrage angezeigt. Du kannst auf einen der Vorschläge klicken, um zu einem bestimmten Ort zu springen. Wenn du mehr Qualifizierer eingibst, werden dir spezifischere Vorschläge angezeigt, z. B. Codedateien, zu denen du direkt springen kannst.
|
||||
|
||||
|
||||
|
||||
1. Du kannst auch nach dem Eintippen deiner Abfrage die EINGABETASTE drücken, um zur vollständigen Suchergebnisansicht zu navigieren. In dieser Ansicht werden dir alle Übereinstimmungen angezeigt. Außerdem verfügt sie über eine grafische Benutzeroberfläche zum Anwenden von Filtern. Weitere Informationen findest du unter [Verwenden der Suchergebnisansicht](#using-the-search-results-view).
|
||||
|
||||
## Erstellen und Verwalten gespeicherter Suchen
|
||||
|
||||
1. Klicke im oberen Navigationsbereich von {% data variables.product.prodname_dotcom_the_website %} auf die Suchleiste, und beginne mit dem Eintippen einer Suchabfrage (oder tippe irgendeinen Buchstaben ein).
|
||||
1. Unter der Suchleiste sollte nun der Abschnitt „Gespeicherte Suchen“ angezeigt werden. Klicke auf {% octicon "plus-circle" aria-label="The plus-circle icon" %} **Gespeicherte Suche erstellen**.
|
||||
|
||||
|
||||
|
||||
1. Gib im Popupfenster den gewünschten Namen für die Abfrage sowie die Abfrage ein, die du speichern möchtest. Klicke auf **Gespeicherte Suche erstellen**.
|
||||
|
||||
|
||||
|
||||
1. Wenn du noch mal auf die Suchleiste klickst, kannst du deine gespeicherte Suche nun im Abschnitt „Gespeicherte Suchen“ unter der Suchleiste sehen. Durch Klicken auf einen Eintrag für eine gespeicherte Suche wird die betreffende Abfrage in der Suchleiste hinzugefügt, und die Vorschläge werden entsprechend gefiltert.
|
||||
|
||||
|
||||
|
||||
- Wenn du eine gespeicherte Suche bearbeiten möchtest, klicke im Abschnitt „Gespeicherte Suchen“ rechts neben dieser gespeicherten Suche auf {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
- Wenn du eine gespeicherte Suche löschen möchtest, klicke rechts neben dieser gespeicherten Suche auf {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
|
||||
|
||||
## Verwenden der Suchergebnisansicht
|
||||
|
||||
Die Suchergebnisansicht gibt es bereits bei der klassischen Suche auf GitHub. Für die meisten Arten von Suchen (bis auf die Suche nach Code) ist die Funktionsweise identisch. Sobald die Betaversion der neuen Codesuche aktiviert ist, verfügt die Suchergebnisseite über eine umgestaltete Benutzeroberfläche und enthält Filter, die im neuen Suchmodul für Code unterstützt werden, z. B. Pfad- und Symbolfilter.
|
||||
|
||||
Zum Erstellen einer Suchabfrage sowie zum Anzeigen und Filtern von Ergebnissen über eine grafische Benutzeroberfläche kannst du eine der folgenden Seiten verwenden: {% data variables.search.search_page_url %} oder {% data variables.search.advanced_url %}. Wenn du nach dem Eintippen einer Suchabfrage in der Suchleiste die EINGABETASTE drückst, wirst du ebenfalls zur Suchergebnisansicht weitergeleitet.
|
||||
|
||||
In der Suchergebnisansicht kannst du zwischen verschiedenen Arten von Suchergebnissen wechseln. Hierzu gehören unter anderem Code, Issues, Pull Requests und Repositorys. Du kannst auch Filter anzeigen und verwenden.
|
||||
|
||||
|
||||
@@ -1,7 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: 7d64df6146c09aa6cd5fc997ccb96022fab29501
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159229"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Note:** You must set a non-zero spending limit on your personal, organization, or enterprise account before the account can be billed for use of {% data variables.product.prodname_github_codespaces %}.
|
||||
**Hinweis:** Du musst ein Ausgabenlimit ungleich Null für dein persönliches, Organisations- oder Unternehmenskonto festlegen, bevor dem Konto das Verwenden von {% data variables.product.prodname_github_codespaces %} in Rechnung gestellt werden kann.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
By default, all accounts have a {% data variables.product.prodname_github_codespaces %} spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, codespaces can always be created and used if the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD.
|
||||
Standardmäßig gilt für alle Konten ein Ausgabenlimit von 0 USD für {% data variables.product.prodname_github_codespaces %}. Dadurch wird verhindert, dass neue Codespaces erstellt oder vorhandene Codespaces geöffnet werden, wenn dies für dein persönliches, Organisations- oder Unternehmenskonto mit Kosten verbunden ist. Für persönliche Konten können immer dann Codespaces erstellt und verwendet werden, wenn das Konto das Limit seiner monatlichen inklusiven Nutzung nicht erreicht hat. Für Organisationen und Unternehmen bedeutet das Standardausgabenlimit, dass es in einen Wert über 0 USD geändert werden muss, damit Personen Codespaces erstellen können, die der Organisation oder dem übergeordneten Unternehmen in Rechnung gestellt werden.
|
||||
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
ms.openlocfilehash: 0193cb7b3950276f157e8ef2a84a958278cfc800
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159738"
|
||||
---
|
||||
1. Klicke über der Dateiliste auf **Diese Vorlage verwenden**, und wähle dann **In einem Codespace öffnen** aus.
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: cdfaf83aa2910a79f44435c6674a9b2ba53d9ec3
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159665"
|
||||
---
|
||||
Verifizierte Schüler*innen und Studierende können {% data variables.product.prodname_github_codespaces %} bis zu einer festgelegten Nutzungsmenge pro Monat für persönliche Konten kostenlos nutzen. Die Speichermenge und Anzahl von Kernstunden, die von Schüler*innen und Studierenden pro Monat genutzt werden können, entspricht der jeweils bei {% data variables.product.prodname_pro %}-Konten enthaltenen Menge bzw. Anzahl. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces).
|
||||
@@ -1,10 +1,2 @@
|
||||
---
|
||||
ms.openlocfilehash: 55a01fbe1358fc0fffc11f146b973d79242c5235
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148109606"
|
||||
---
|
||||
1. Klicke unter deinem Organisationsnamen auf {% octicon "project" aria-label="The Projects icon" %} **Projekte**.
|
||||
{% ifversion fpt or ghes or ghec %}  {% else %}  {% endif %}
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -1,10 +1,18 @@
|
||||
- To filter for any match of multiple values (an OR query), separate the values with a comma. For example `label:"good first issue",bug` will list all issues labelled `good first issue` or `bug`.
|
||||
- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
|
||||
- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
|
||||
- To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
|
||||
- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
|
||||
- To filter for the previous, current, or next iteration of an iteration field, use `@previous`, `@current`, or `@next`. For example, `iteration:@current`.
|
||||
- To filter for items assigned to the viewer, use `@me`. For example, `assignee:@me`. Anyone using this view will see items assigned to themselves.
|
||||
- To filter by when an item was last updated, use `last-updated:` followed by the number of days. This filter only supports `{number}days` (or `1day` for a single day) as a unit. For example, `last-updated:7days` will only show items that were last updated 7 or more days ago.
|
||||
- To filter date and number fields, use `>`, `>=`, `<`, `<=`, and `..` range queries. For example: `target:2022-03-01..2022-03-15`. For more information, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)." {% ifversion projects-v2-tasklists %}
|
||||
- To filter for issues tracked by a specified issue, use `tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"` and replace `<OWNER>` with the repository owner, `<REPO>` with the repository name, and `<ISSUE NUMBER>` with the issue number. {% endif %}
|
||||
---
|
||||
ms.openlocfilehash: 9106c4a2e538e62d23cd0aa2e417758376f6ffcd
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148158853"
|
||||
---
|
||||
- Um nach einer Übereinstimmung mehrerer Werte zu filtern (eine OR-Abfrage), trennst du die Werte mit einem Komma. Zum Beispiel werden durch `label:"good first issue",bug` alle Issues mit der Bezeichnung `good first issue` oder `bug` aufgelistet.
|
||||
- Um nach fehlenden Werten zu filtern, stellst du deinem Filter `-` voran. Zum Beispiel zeigt `-label:"bug"` nur Elemente an, die nicht die Bezeichnung `bug` aufweisen.
|
||||
- Um nach allen fehlenden Werten zu filtern, gibst du `no:` gefolgt von dem Feldnamen ein. Mit `no:assignee` werden zum Beispiel nur Elemente angezeigt, die keine zugewiesenen Personen enthalten.
|
||||
- Um nach dem Zustand zu filtern, gibst du `is:` ein. Zum Beispiel: `is: issue` oder `is:open`.
|
||||
- Trenne mehrere Filter durch ein Leerzeichen. Zum Beispiel werden mit `status:"In progress" -label:"bug" no:assignee` nur Elemente angezeigt, die den Status `In progress` aufweisen, nicht die Bezeichnung `bug` tragen und keine zugewiesene Person umfassen.
|
||||
- Um nach der vorherigen, aktuellen oder nächsten Iteration eines Iterationsfelds zu filtern, verwende `@previous`, `@current` oder `@next`. Beispiel: `iteration:@current`.
|
||||
- Um nach Objekten zu filtern, die der anzeigenden Person zugewiesen sind, verwende `@me`. Beispiel: `assignee:@me`. Alle Personen, die diese Ansicht verwenden, sehen die ihnen zugewiesenen Elemente.
|
||||
- Um danach zu filtern, wann ein Element zuletzt aktualisiert wurde, verwendest du `last-updated:` gefolgt von der Anzahl der Tage. Dieser Filter unterstützt nur `{number}days` (oder `1day` für einen einzelnen Tag) als Einheit. Beispielsweise zeigt `last-updated:7days` nur Elemente an, die vor sieben oder mehr Tagen aktualisiert wurden.
|
||||
- Um Datums- und Zahlenfelder zu filtern, verwendest du die Bereichsabfragen `>`, `>=`, `<`, `<=` und `..`. Beispiel: `target:2022-03-01..2022-03-15`. Weitere Informationen findest du unter [Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). {% ifversion projects-v2-tasklists %}
|
||||
- Um nach Issues zu filtern, die durch einen angegebenen Issue nachverfolgt werden, verwende `tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"`, und ersetze `<OWNER>` durch den Repositorybesitzer, `<REPO>` durch den Repositorynamen und `<ISSUE NUMBER>` durch die Nummer des Issues. {% endif %}
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
ms.openlocfilehash: 56c01942ad1ac3496b9875a039a091676e3fc51e
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159706"
|
||||
---
|
||||
Wenn du von der Warteliste für die Nutzung der Betaversion ausgewählt wirst, erhältst du eine E-Mail. Sobald dir Zugriff gewährt wurde, werden die Betaversion der neuen Codesuche und der Codeansicht für dein Konto automatisch aktiviert.
|
||||
|
||||
Du kannst die Betaversion auf {% data variables.product.prodname_dotcom_the_website %} jederzeit deaktivieren oder aktivieren. Beachte, dass diese Einstellung sowohl für die Codesuche als auch für die Codeansicht gilt.
|
||||
|
||||
{% data reusables.feature-preview.feature-preview-setting %}
|
||||
1. Klicke rechts neben „Neue Codesuche und Codeansicht (Betaversion)“ auf **Aktivieren** oder **Deaktivieren**.
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
ms.openlocfilehash: 76133fe9416c92282de821d12e88432cdc1b5452
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159557"
|
||||
---
|
||||
Ein privates Melden von Sicherheitsrisiken ermöglicht es Sicherheitsforscher*innen, Sicherheitsrisiken leicht über ein einfaches Formular direkt an dich zu melden.
|
||||
|
||||
Wenn ein*e Sicherheitsforscher*in eine Sicherheitslücke privat meldet, wirst du benachrichtigt und kannst die Meldung akzeptieren, weitere Fragen stellen oder die Meldung ablehnen. Wenn du die Meldung akzeptierst, bist du bereit, gemeinsam mit dem bzw. der Sicherheitsforscher*in privat an einem Fix für das Sicherheitsrisiko zu arbeiten.
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /security-in-github-codespaces
|
||||
- /performing-a-full-rebuild-of-a-container
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 223d3b146d829f129de39b43b51b6ab9e8aef411
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159196'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180802'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About GitHub Global Campus for students
|
||||
intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.'
|
||||
title: À propos de GitHub Global Campus pour les étudiants
|
||||
intro: '{% data variables.product.prodname_education %} offre aux étudiants une expérience réelle avec un accès gratuit à différents outils de développement à partir des partenaires de {% data variables.product.prodname_dotcom %}.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-github-education-for-students
|
||||
- /github/teaching-and-learning-with-github-education/about-github-education-for-students
|
||||
@@ -10,40 +10,46 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: For students
|
||||
ms.openlocfilehash: 198f0354e63721a4763e8fa32f832a19b2dac9d9
|
||||
ms.sourcegitcommit: 3abdbdbb47a9319f20e11845e9c2d8a7fce63422
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 11/15/2022
|
||||
ms.locfileid: '148165096'
|
||||
---
|
||||
Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience.
|
||||
L’utilisation de {% data variables.product.prodname_dotcom %} pour vos projets scolaires est un moyen pratique de collaborer avec d’autres personnes et de créer un portefeuille reflétant une expérience réelle.
|
||||
|
||||
Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for {% data variables.product.prodname_education %} student benefits. Your {% data variables.product.prodname_education %} student benefits and resources are all included in {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits, all in one place. For more information, see "[Apply to GitHub Global Campus as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)" and [{% data variables.product.prodname_education %}](https://education.github.com/).
|
||||
Toute personne qui a un compte {% data variables.product.prodname_dotcom %} peut collaborer dans des dépôts publics et privés illimités avec {% data variables.product.prodname_free_user %}. En tant qu’étudiant, vous pouvez aussi demander un accès aux avantages Étudiant {% data variables.product.prodname_education %}. Vos avantages et ressources Étudiant {% data variables.product.prodname_education %} sont tous inclus dans {% data variables.product.prodname_global_campus %}, portail qui vous permet d’accéder à vos avantages Éducation à un seul et même endroit. Pour plus d’informations, consultez « [Demander à rejoindre GitHub Global Campus en tant qu’étudiant](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student) » et [{% data variables.product.prodname_education %}](https://education.github.com/).
|
||||
|
||||
Before applying for Global Campus, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)."
|
||||
Avant de demander à rejoindre Global Campus, vérifiez si votre communauté d’apprentissage figure déjà parmi nos partenaires en tant qu’école {% data variables.product.prodname_campus_program %}. Pour plus d’informations, consultez « [À propos de {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program) ».
|
||||
|
||||
If you're a member of a school club, a teacher can apply for {% data variables.product.prodname_global_campus %} so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
|
||||
Si vous êtes membre d’un club scolaire, un enseignant peut demander à rejoindre {% data variables.product.prodname_global_campus %} afin que votre équipe puisse collaborer en utilisant {% data variables.product.prodname_team %}, qui permet d’avoir un nombre illimité d’utilisateurs et de dépôts privés, gratuitement. Pour plus d’informations, consultez « [Demander à rejoindre {% data variables.product.prodname_global_campus %} en tant qu’enseignant](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher) ».
|
||||
|
||||
Once you are a verified {% data variables.product.prodname_global_campus %} student, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
|
||||
Une fois que vous êtes un étudiant {% data variables.product.prodname_global_campus %} vérifié, vous pouvez accéder à {% data variables.product.prodname_global_campus %} quand vous voulez en vous rendant sur le site web [{% data variables.product.prodname_education %}](https://education.github.com).
|
||||
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_global_campus %} features for students
|
||||
## Fonctionnalités {% data variables.product.prodname_global_campus %} pour les étudiants
|
||||
|
||||
{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, students can:
|
||||
- Connect with a local Campus Expert. For more information on campus experts, see "[About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts)."
|
||||
- Explore and claim offers for free industry tools from the [Student Developer Pack](https://education.github.com/pack).
|
||||
- See upcoming in-person and virtual events for students, curated by {% data variables.product.prodname_education %} and student leaders.
|
||||
- View assignments from [GitHub Classroom](https://classroom.github.com/) with upcoming due dates.
|
||||
- Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
|
||||
- Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)."
|
||||
{% data variables.product.prodname_global_campus %} est un portail à partir duquel vous pouvez accéder à vos avantages et ressources {% data variables.product.prodname_education %} à un seul et même endroit. Dans le portail {% data variables.product.prodname_global_campus %}, les étudiants peuvent :
|
||||
- Contacter un expert Campus local. Pour plus d’informations sur les experts Campus, consultez « [À propos des experts Campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts) ».
|
||||
- Explorer et demander des offres concernant les outils gratuits du [Pack développeur étudiant](https://education.github.com/pack).
|
||||
- Découvrir les événements physiques et virtuels à venir pour les étudiants, organisés par {% data variables.product.prodname_education %} et les leaders étudiants.
|
||||
- Voir les devoirs de [GitHub Classroom](https://classroom.github.com/) et les prochaines dates d’échéance.
|
||||
- Rester informé des centres d’intérêt de la communauté en re-regardant les épisodes récents de [Campus TV](https://www.twitch.tv/githubeducation). Campus TV est créée par {% data variables.product.prodname_dotcom %} et les leaders de la communauté étudiante et peut être regardée en direct ou à la demande.
|
||||
- Découvrir les dépôts créés par les étudiants dans GitHub Community Exchange. Pour plus d’informations, consultez « [À propos de GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange) ».
|
||||
|
||||
{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits.
|
||||
- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
|
||||
- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
|
||||
Les étudiants {% data variables.product.prodname_global_campus %} reçoivent également les avantages {% data variables.product.prodname_dotcom %} suivants.
|
||||
- **{% data variables.product.prodname_copilot %}** : les étudiants vérifiés reçoivent un abonnement gratuit à {% data variables.product.prodname_copilot %}. Vous serez automatiquement informé de l’abonnement gratuit quand vous visiterez la page d’abonnement à {% data variables.product.prodname_copilot %} dans les paramètres de votre compte. Pour plus d’informations sur l’abonnement à {% data variables.product.prodname_copilot %} et son utilisation, consultez « [Gestion de votre abonnement {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot) » et « [À propos de {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot) ».
|
||||
- **{% data variables.product.prodname_github_codespaces %}** : {% data reusables.education.student-codespaces-benefit %} Pour plus d’informations sur la prise en main de {% data variables.product.prodname_github_codespaces %}, consultez « [Vue d’ensemble de {% data variables.product.prodname_github_codespaces %}](/codespaces/overview) ».
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
|
||||
**Remarque :** {% data reusables.education.note-on-student-codespaces-usage %} Pour plus d’informations, consultez « [Utilisation de {% data variables.product.prodname_github_codespaces %} avec {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom) ».
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
## Pour aller plus loin
|
||||
|
||||
- "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)"
|
||||
- "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)"
|
||||
- « [À propos de {% data variables.product.prodname_global_campus %} pour les enseignants](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers) »
|
||||
- « [À propos de {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange) »
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Migration depuis {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'Vous pouvez migrer votre {% data variables.projects.projects_v1_board %} vers la nouvelle expérience de {% data variables.product.prodname_projects_v2 %}.'
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,53 +10,57 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108704'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Remarques :**
|
||||
|
||||
- Si le projet que vous migrez contient plus de 1 200 éléments, les problèmes ouverts sont priorisés, suivis des demandes de tirage ouvertes, puis des notes. L’espace restant est utilisé pour les problèmes fermés, les demandes de tirage fusionnées et les demandes de tirage fermées. Les éléments qui ne peuvent pas être migrés en raison de cette limite sont déplacés vers l’archive. Si la limite d’archivage de 10 000 éléments est atteinte, aucun élément supplémentaire n’est migré.
|
||||
- Notez que les cartes sont converties en brouillons de problème et que le contenu est enregistré dans le corps du brouillon. Si des informations apparaissent manquantes, affichez les champs masqués. Pour plus d’informations, consultez « [Affichage et masquage des champs](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields) ».
|
||||
- L’automatisation n’est pas migrée.
|
||||
- Le tri, l’archivage et l’activité ne sont pas migrés.
|
||||
- Après la migration, le nouveau projet migré et l’ancien projet ne restent pas synchronisés.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## À propos de la migration des projets
|
||||
|
||||
Vous pouvez migrer vos panneaux de projet vers la nouvelle expérience de {% data variables.product.prodname_projects_v2 %} et essayer des tableaux, plusieurs vues, les nouvelles options d’automatisation et des types de champs performants. Pour plus d’informations, consultez « [À propos des projets](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) ».
|
||||
|
||||
## Migration d’un tableau de projet d’organisation
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. Sur la gauche, cliquez sur **Projets (classique)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migration d’un tableau de projet d’utilisateur
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. En haut de votre page de profil, dans le volet de navigation principal, cliquez sur {% octicon "project" aria-label="The project board icon" %} **Projets**.
|
||||
|
||||
1. Au-dessus de la liste des projets, cliquez sur **Projets (classique)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migration d’un tableau de projet de dépôt
|
||||
|
||||
{% note %}
|
||||
|
||||
**Remarque :** {% data variables.projects.projects_v2_caps %} ne prend pas en charge les projets de niveau dépôt. Lorsque vous migrez un tableau de projet de dépôt, celui-ci migre vers l’organisation ou le compte personnel propriétaire du projet de dépôt, tandis que le projet migré est épinglé au dépôt d’origine.
|
||||
**Notes:**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. Sous le nom de votre référentiel, cliquez sur {% octicon "project" aria-label="The project board icon" %} **Projets**.
|
||||
|
||||
1. Cliquez sur **Projets (classique)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
## About project migration
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
## Migrating an organization project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -1,10 +1,2 @@
|
||||
---
|
||||
ms.openlocfilehash: 55a01fbe1358fc0fffc11f146b973d79242c5235
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: fr-FR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148108660"
|
||||
---
|
||||
1. Sous le nom de votre organisation, cliquez sur {% octicon "project" aria-label="The Projects icon" %} **Projets**.
|
||||
{% ifversion fpt or ghes or ghec %}  {% else %}  {% endif %}
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /security-in-github-codespaces
|
||||
- /performing-a-full-rebuild-of-a-container
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 223d3b146d829f129de39b43b51b6ab9e8aef411
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159199'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180805'
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
title: 컨테이너의 전체 다시 빌드 수행
|
||||
intro: 디스크 공간이 부족하거나 개발 컨테이너 구성이 새 codespace에서 작동하는지 확인하려는 경우 컨테이너의 전체 다시 빌드를 수행할 수 있습니다.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Full rebuilds
|
||||
ms.openlocfilehash: f844d5f92073adf01c3b1a1100e6fe1912b2d7ad
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180852'
|
||||
---
|
||||
## 컨테이너 다시 빌드 정보
|
||||
|
||||
codespace에서 작업하는 경우 개발 환경은 가상 머신에서 실행되는 Docker 컨테이너입니다. codespace 내에서 개발 컨테이너 구성을 변경하고 해당 변경 내용을 현재 codespace에 적용하려면 컨테이너를 다시 빌드해야 합니다.
|
||||
|
||||
기본적으로 컨테이너를 다시 빌드할 때 {% data variables.product.prodname_github_codespaces %}은 컨테이너의 이전 빌드에서 캐시된 이미지를 다시 사용하여 빌드 프로세스를 가속화합니다. 이는 일반적으로 다음과 같은 이유로 개발 컨테이너 구성에 대한 변경 내용을 구현하는 가장 빠른 방법입니다.
|
||||
- {% data variables.product.prodname_github_codespaces %}은(는) 컨테이너 레지스트리에서 이미지를 다시 사용하는 대신 캐시의 이미지를 다시 사용할 수 있습니다.
|
||||
- 개발 컨테이너 기능 및 Dockerfile 지침과 같이 컨테이너를 빌드하는 방법을 정의하는 개발 컨테이너 구성의 부분은 캐시의 이미지 계층에서 이미 구현되었을 수 있으므로 이러한 프로세스가 다시 실행될 때까지 기다릴 필요가 없습니다. 그러나 컨테이너가 빌드된 후 실행되는 구성의 명령(예: `onCreateCommand`)이 다시 실행됩니다.
|
||||
|
||||
경우에 따라 컨테이너의 전체 다시 빌드를 수행할 수 있습니다. 전체 다시 빌드를 사용하여 {% data variables.product.prodname_github_codespaces %}는 캐시에서 모든 Docker 컨테이너, 이미지 및 볼륨을 정리한 다음 새로 끌어온 이미지로 컨테이너를 다시 빌드합니다. 구성에 정의된 모든 설정이 다시 실행되어 새 이미지 계층이 생성됩니다. 다음과 같은 상황에서 캐시된 이미지로 컨테이너를 다시 빌드하는 여러 번 반복한 후에 전체 다시 빌드를 수행할 수 있습니다.
|
||||
|
||||
- 구성에 정의된 설정이 캐시된 이미지에 종속되지 않고 누군가가 구성에 따라 새 codespace를 만들 때 필요에 따라 실행되도록 하려고 합니다. 예를 들어 코드스페이스로 마지막으로 끌어온 이후 기본 이미지에서 종속성이 제거되었을 수 있습니다.
|
||||
- 예를 들어 디스크 공간이 부족하거나 스토리지 요금을 최소화하려는 경우 캐시에서 사용하는 디스크 공간을 확보하려고 합니다. 기본 이미지를 여러 번 변경했거나, 구성을 여러 번 반복하거나, Docker Compose를 사용하여 여러 컨테이너를 실행하는 경우 이미지 캐시에서 상당한 양의 디스크 공간을 사용할 수 있습니다.
|
||||
|
||||
## 전체 다시 빌드 수행
|
||||
|
||||
{% data variables.product.prodname_vscode %}에서 전체 다시 빌드를 수행할 수 있습니다.
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
1. "다시 빌드"를 입력하고 **Codespaces: 전체 컨테이너 다시 빌드를** 선택합니다.
|
||||
|
||||
|
||||
|
||||
## 전체 다시 빌드를 통해 데이터 유지
|
||||
|
||||
codespace의 디렉터리에 포함된 `/workspaces` 모든 파일 및 폴더는 항상 다시 빌드를 통해 유지됩니다. 전체 다시 빌드를 통해 이 디렉터리의 콘텐츠를 유지하기 위해 설정을 변경하거나 구성을 추가할 필요가 없습니다.
|
||||
|
||||
전체 다시 빌드를 통해 디렉터리 외부의 `/workspaces` 파일을 유지하려는 경우 컨테이너의 원하는 위치에 영구 디렉터리에 대한 기호 링크(symlink)를 만들 수 있습니다. 예를 들어 `/workspaces/.devcontainer` 디렉터리에서 다시 빌드 간에 유지되는 `config` 디렉터리를 만들 수 있습니다. 그런 다음 `config` 디렉터리와 그 내용을 `devcontainer.json` 파일에 `postCreateCommand`로 symlink할 수 있습니다.
|
||||
|
||||
```json
|
||||
{
|
||||
"image": "mcr.microsoft.com/vscode/devcontainers/base:alpine",
|
||||
"postCreateCommand": ".devcontainer/postCreate.sh"
|
||||
}
|
||||
```
|
||||
|
||||
아래 예제 `postCreate.sh` 파일에서 `config` 디렉터리의 내용은 홈 디렉터리에 기호적으로 연결됩니다.
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
ln -sf $PWD/.devcontainer/config $HOME/config && set +x
|
||||
```
|
||||
|
||||
## 추가 정보
|
||||
- [개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the Visual Studio Code Command Palette in GitHub Codespaces
|
||||
intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in {% data variables.product.prodname_github_codespaces %}.'
|
||||
title: Github Codespaces에서 Visual Studio Code 명령 팔레트 사용
|
||||
intro: '{% data variables.product.prodname_vscode %}의 명령 팔레트 기능을 사용하여 {% data variables.product.prodname_github_codespaces %}의 여러 명령에 액세스할 수 있습니다.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -12,62 +12,67 @@ shortTitle: VS Code Command Palette
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
|
||||
ms.openlocfilehash: acd462dd1c0b60dced529d7471b9c8638e2f6e91
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180813'
|
||||
---
|
||||
## {% data variables.product.prodname_vscode_command_palette %} 정보
|
||||
|
||||
## About the {% data variables.product.prodname_vscode_command_palette %}
|
||||
{% data variables.product.prodname_vscode_command_palette_shortname %}는 {% data variables.product.prodname_vscode %}의 초점 기능 중 하나이며 {% data variables.product.prodname_github_codespaces %}에서 사용할 수 있습니다. 명령 팔레트를 사용하면 {% data variables.product.prodname_github_codespaces %} 및 {% data variables.product.prodname_vscode_shortname %}에 대한 많은 명령에 액세스할 수 있습니다. {% data variables.product.prodname_vscode_command_palette_shortname %} 사용에 대한 자세한 내용은 {% data variables.product.prodname_vscode_shortname %} 설명서의 “[사용자 인터페이스](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)”를 참조하세요.
|
||||
|
||||
The {% data variables.product.prodname_vscode_command_palette_shortname %} is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in {% data variables.product.prodname_github_codespaces %}. The Command Palette allows you to access many commands for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
## {% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스
|
||||
|
||||
## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
여러 가지 방법으로 {% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스할 수 있습니다.
|
||||
|
||||
You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways.
|
||||
- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd>(Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>(Windows/Linux).
|
||||
|
||||
- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
|
||||
Note that this command is a reserved keyboard shortcut in Firefox.
|
||||
이 명령은 Firefox에서 예약된 바로 가기 키입니다.
|
||||
- <kbd>F1</kbd>
|
||||
- From the Application Menu, click **View > Command Palette…**.
|
||||
- 애플리케이션 메뉴에서 **보기 > 명령 팔레트…** 를 클릭합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
## Commands for {% data variables.product.prodname_codespaces %}
|
||||
## {% data variables.product.prodname_codespaces %}에 대한 명령
|
||||
|
||||
To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces".
|
||||
{% data variables.product.prodname_github_codespaces %}와 관련된 모든 명령을 보려면 [{% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스](#accessing-the-command-palette)한 다음 “Codespaces”를 입력하기 시작합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
### Suspending or stopping a codespace
|
||||
### codespace 일시 중단 또는 중지
|
||||
|
||||
If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes.
|
||||
새 비밀을 추가하거나 컴퓨터 유형을 변경하는 경우 codespace를 중지하고 다시 시작하여 변경 내용을 적용해야 합니다.
|
||||
|
||||
To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**.
|
||||
codespace의 컨테이너를 일시 중단하거나 중지하려면 [{% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스](#accessing-the-command-palette)한 다음 “stop”을 입력하기 시작합니다. **Codespaces: 현재 codespace 중지** 를 선택합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
### Adding a predefined dev container configuration
|
||||
### 미리 정의된 개발 컨테이너 구성 추가
|
||||
|
||||
To add a predefined dev container configuration, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
||||
미리 정의된 개발 컨테이너 구성을 추가하려면 [{% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스](#accessing-the-command-palette)한 다음 " 개발 컨테이너"를 입력하기 시작합니다. **Codespaces: 개발 컨테이너 구성 파일 추가...** 를 선택합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
### Rebuilding a codespace
|
||||
### Codespace 다시 빌드
|
||||
|
||||
If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes.
|
||||
개발 컨테이너를 추가하거나 구성 파일(`devcontainer.json` 및 `Dockerfile`)을 편집하는 경우 변경 내용을 적용하려면 codespace를 다시 빌드해야 합니다.
|
||||
|
||||
To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
컨테이너를 다시 빌드하려면 [{% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스](#accessing-the-command-palette)한 다음 “rebuild”를 입력하기 시작합니다. **Codespaces: 컨테이너 다시 빌드** 를 선택합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
### Codespaces logs
|
||||
### Codespaces 로그
|
||||
|
||||
You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs.
|
||||
{% data variables.product.prodname_vscode_command_palette_shortname %}를 사용하여 codespace 만들기 로그에 액세스하거나 모든 로그를 내보낼 수 있습니다.
|
||||
|
||||
To retrieve the logs for {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_github_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup.
|
||||
{% data variables.product.prodname_github_codespaces %}에 대한 로그를 검색하려면 [{% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스](#accessing-the-command-palette)한 후 "log" 입력을 시작합니다. **Codespaces: 로그 내보내** 기를 선택하여 {% data variables.product.prodname_github_codespaces %}과 관련된 모든 로그를 내보내거나 **Codespaces: 만들기 로그 보기를** 선택하여 설정과 관련된 로그를 봅니다.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
## 추가 정보
|
||||
|
||||
- "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
- "[{% data variables.product.prodname_vscode %}에서 {% data variables.product.prodname_github_codespaces %} 사용](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: The codespace lifecycle
|
||||
intro: 'You can develop in a {% data variables.product.prodname_github_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.'
|
||||
title: codespace 수명 주기
|
||||
intro: '{% data variables.product.prodname_github_codespaces %} 환경에서 개발하고 전체 codespace 수명 주기 동안 데이터를 유지 관리할 수 있습니다.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,58 +10,63 @@ topics:
|
||||
- Developer
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/codespaces-lifecycle
|
||||
ms.openlocfilehash: 660ced63e34c6de8025c65946542baca43534cfe
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180797'
|
||||
---
|
||||
## Codespace의 수명 주기 정보
|
||||
|
||||
## About the lifecycle of a codespace
|
||||
Codespace의 수명 주기는 Codespace를 만들 때 시작되고 Codespace를 삭제할 때 종료됩니다. 실행 중인 프로세스에 영향을 주지 않고 활성 Codespace의 연결을 끊고 다시 연결할 수 있습니다. 프로젝트에서 변경한 내용에 손실 없이 Codespace를 중지하고 다시 시작할 수 있습니다.
|
||||
|
||||
The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
|
||||
## codespace 만들기
|
||||
|
||||
## Creating a 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) 참조하세요.
|
||||
|
||||
When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your repository each time you develop in {% data variables.product.prodname_github_codespaces %} or keep a long-running codespace for a feature. {% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
{% data reusables.codespaces.max-number-codespaces %} 마찬가지로 활성 코드스페이스의 최대 수에 도달하고 다른 코드스페이스를 시작하려고 하면 활성 코드스페이스 중 하나를 중지하라는 메시지가 표시됩니다.
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %} Similarly, if you reach the maximum number of active codespaces and you try to start another, you are prompted to stop one of your active codespaces.
|
||||
|
||||
If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
|
||||
프로젝트에서 작업할 때마다 새 Codespace를 만들도록 선택한 경우 새 커밋이 {% data variables.product.prodname_dotcom %}에 있도록 변경 내용을 정기적으로 푸시해야 합니다. 프로젝트에 대해 장기 실행 Codespace를 사용하도록 선택하는 경우 환경에 최신 커밋이 있도록 Codespace에서 작업을 시작할 때마다 리포지토리의 기본 분기에서 끌어와야 합니다. 이 워크플로는 로컬 컴퓨터에 있는 프로젝트를 작업하는 경우와 매우 유사합니다.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Saving changes in a codespace
|
||||
## Codespace의 변경 내용 저장
|
||||
|
||||
When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
웹을 통해 Codespace에 연결하면 자동 저장이 웹 편집기에서 자동으로 활성화되고 지연 후 변경 내용을 저장하도록 구성됩니다. 데스크톱에서 실행되는 {% data variables.product.prodname_vscode %}를 통해 Codespace에 연결하는 경우 자동 저장을 사용 설정해야 합니다. 자세한 내용은 {% data variables.product.prodname_vscode %} 설명서의 [저장/자동 저장](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)을 참조하세요.
|
||||
|
||||
Your work will be saved on a virtual machine in the cloud. You can close and stop a codespace and return to the saved work later. If you have unsaved changes, your editor will prompt you to save them before exiting. However, if your codespace is deleted, then your work will be deleted too. To persist your work, you will need to commit your changes and push them to your remote repository, or publish your work to a new remote repository if you created your codespace from a template. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)."
|
||||
작업은 클라우드의 가상 머신에 저장됩니다. codespace를 닫고 중지하고 나중에 저장된 작업으로 돌아갈 수 있습니다. 저장되지 않은 변경 내용이 있는 경우 편집기에 종료하기 전에 저장하라는 메시지가 표시됩니다. 그러나 codespace가 삭제되면 작업도 삭제됩니다. 작업을 유지하려면 변경 내용을 커밋하고 원격 리포지토리에 푸시하거나 템플릿에서 codespace를 만든 경우 새 원격 리포지토리에 작업을 게시해야 합니다. 자세한 내용은 “[codespace에서 소스 제어 사용](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”을 참조하세요.
|
||||
|
||||
## Timeouts for {% data variables.product.prodname_github_codespaces %}
|
||||
## {% data variables.product.prodname_github_codespaces %}에 대한 시간 제한
|
||||
|
||||
If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
상호 작용 없이 Codespace를 실행 상태로 두거나 Codespace를 명시적으로 중지하지 않고 종료하는 경우 Codespace는 비활성 기간 후에 시간 초과되고 실행을 중지합니다. 기본적으로 Codespace는 30분 동안 활동이 없으면 시간 제한이 적용되지만 사용자가 만든 새 Codespace의 시간 제한 기간은 사용자 지정할 수 있습니다. Codespace의 기본 시간 제한 기간을 설정하는 방법에 대한 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %}의 시간 제한 기간 설정](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)”을 참조하세요. Codespace를 중지하는 방법에 대한 자세한 내용은 “[Codespace 중지](#stopping-a-codespace)”를 참조하세요.
|
||||
|
||||
When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
|
||||
Codespace가 시간 초과되면 변경 내용이 마지막으로 저장된 시점부터 데이터가 보존됩니다. 자세한 내용은 “[Codespace의 변경 내용 저장](#saving-changes-in-a-codespace)”을 참조하세요.
|
||||
|
||||
## Rebuilding a codespace
|
||||
## Codespace 다시 빌드
|
||||
|
||||
You can rebuild your codespace to implement changes to your dev container configuration. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. By default, when you rebuild your codespace, {% data variables.product.prodname_github_codespaces %} will reuse images from your cache to speed up the rebuild process. Alternatively, you can perform a full rebuild, which clears your cache and rebuilds the container with fresh images.
|
||||
codespace를 다시 빌드하여 개발 컨테이너 구성에 대한 변경 내용을 구현할 수 있습니다. 대부분의 경우 Codespace를 다시 빌드하는 대신 새 Codespace를 만들면 됩니다. 기본적으로 codespace를 다시 빌드할 때 {% data variables.product.prodname_github_codespaces %}은 캐시의 이미지를 다시 사용하여 다시 빌드 프로세스를 가속화합니다. 또는 캐시를 지우고 새 이미지로 컨테이너를 다시 빌드하는 전체 다시 빌드를 수행할 수 있습니다.
|
||||
|
||||
For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)" and "[Performing a full rebuild of a container](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)."
|
||||
자세한 내용은 "[개발 컨테이너 소개](/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).
|
||||
|
||||
## Stopping a codespace
|
||||
## Codespace 중지
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %} For more information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)."
|
||||
{% data reusables.codespaces.stopping-a-codespace %} 자세한 내용은 "[codespace 중지 및 시작"을 참조하세요](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace).
|
||||
|
||||
## Deleting a codespace
|
||||
## Codespace 삭제
|
||||
|
||||
You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
|
||||
특정 작업에 대한 Codespace를 만들고 변경 내용을 원격 분기에 푸시한 후 Codespace를 안전하게 삭제할 수 있습니다.
|
||||
|
||||
If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
|
||||
푸시되지 않은 git 커밋이 있는 Codespace를 삭제하려고 하면 편집기에서 원격 분기에 푸시되지 않은 변경 내용이 있음을 알립니다. 원하는 변경 내용을 푸시한 다음, Codespace를 삭제하거나, Codespace와 커밋되지 않은 변경 내용을 계속 삭제할 수 있습니다. 새 Codespace를 만들지 않고 코드를 새 분기로 내보낼 수도 있습니다. 자세한 내용은 “[분기로 변경 내용 내보내기](/codespaces/troubleshooting/exporting-changes-to-a-branch)”를 참조하세요.
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
지정된 기간 동안 중지되고 비활성 상태로 유지된 Codespace는 자동으로 삭제됩니다. 기본적으로 비활성 codespace는 30일 후에 삭제되지만 codespace 보존 기간을 사용자 지정할 수 있습니다. 자세한 내용은 “[내 Codespace의 자동 삭제 구성](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)”을 참조하세요.
|
||||
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
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)”를 참조하세요.
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
Codespace 삭제에 대한 자세한 내용은 “[Codespace 삭제](/codespaces/developing-in-codespaces/deleting-a-codespace)”를 참조하세요.
|
||||
|
||||
## Losing the connection while using {% data variables.product.prodname_github_codespaces %}
|
||||
## {% data variables.product.prodname_github_codespaces %}을(를) 사용하는 동안 연결 끊기
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
{% data variables.product.prodname_github_codespaces %}은(는) 클라우드 기반 개발 환경이며 인터넷에 연결해야 합니다. Codespace에서 작업하는 동안 인터넷에 대한 연결이 끊어지면 Codespace에 액세스할 수 없습니다. 그러나 커밋되지 않은 변경 내용은 저장됩니다. 인터넷에 다시 연결하게 되면 Codespace가 남아 있는 상태와 정확히 동일한 상태로 Codespace에 연결할 수 있습니다. 인터넷 연결이 불안정한 경우 변경 내용을 자주 커밋하고 푸시해야 합니다.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
오프라인으로 작업하는 경우가 많다는 것을 알고 있는 경우 {% data variables.product.prodname_vscode_shortname %}에 대한 ["개발 컨테이너" 확장](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)을 참조하세요.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Adding features to a devcontainer.json file
|
||||
title: devcontainer.json 파일에 기능 추가
|
||||
shortTitle: Adding features
|
||||
intro: With features, you can quickly add tools, runtimes, or libraries to your dev container configuration.
|
||||
intro: '기능을 사용하면 도구, 런타임 또는 라이브러리를 개발 컨테이너 구성에 빠르게 추가할 수 있습니다.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,34 +10,39 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
ms.openlocfilehash: 7e72739e93e83995d86baf19d62f7bf2e1c5b6bc
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180829'
|
||||
---
|
||||
{% data reusables.codespaces.about-features %} 이 문서의 탭을 사용하여 이러한 각 기능 추가 방법에 대한 지침을 표시합니다.
|
||||
|
||||
{% data reusables.codespaces.about-features %} Use the tabs in this article to display instructions for each of these ways of adding features.
|
||||
|
||||
## Adding features to a `devcontainer.json` file
|
||||
## 파일에 기능 `devcontainer.json` 추가
|
||||
|
||||
{% webui %}
|
||||
|
||||
1. Navigate to your repository on {% data variables.product.prodname_dotcom_the_website %}, find your `devcontainer.json` file, and click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
|
||||
1. {% data variables.product.prodname_dotcom_the_website %}에서 리포지토리로 이동하여 파일을 찾 `devcontainer.json` 은 다음 {% octicon "pencil" aria-label="The edit icon" %}을 클릭하여 파일을 편집합니다.
|
||||
|
||||
If you don't already have a `devcontainer.json` file, you can create one now. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
|
||||
1. To the right of the file editor, in the **Marketplace** tab, browse or search for the feature you want to add, then click the name of the feature.
|
||||
파일이 아직 `devcontainer.json` 없는 경우 지금 만들 수 있습니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)”를 참조하세요.
|
||||
1. 파일 편집기 오른쪽의 **Marketplace** 탭에서 추가하려는 기능을 찾아보거나 검색한 다음 기능의 이름을 클릭합니다.
|
||||
|
||||
|
||||
3. Under "Installation," click the code snippet to copy it to your clipboard, then paste the snippet into the `features` object in your `devcontainer.json` file.
|
||||
|
||||
3. "설치"에서 코드 조각을 클릭하여 클립보드에 복사한 다음, 코드 조각을 파일의 `features` 개체에 `devcontainer.json` 붙여넣습니다.
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
...
|
||||
"ghcr.io/devcontainers/features/terraform:1": {},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. By default, the latest version of the feature will be used. To choose a different version, or configure other options for the feature, expand the properties listed under "Options" to view the available values, then add the options by manually editing the object in your `devcontainer.json` file.
|
||||
1. 기본적으로 기능의 최신 버전이 사용됩니다. 다른 버전을 선택하거나 기능에 대한 다른 옵션을 구성하려면 "옵션" 아래에 나열된 속성을 확장하여 사용 가능한 값을 확인한 다음 파일의 개체를 수동으로 편집하여 옵션을 추가합니다 `devcontainer.json` .
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
@@ -47,11 +52,11 @@ topics:
|
||||
"tflint": "latest"
|
||||
},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. Commit the changes to your `devcontainer.json` file.
|
||||
1. 변경 내용을 파일에 커밋합니다 `devcontainer.json` .
|
||||
|
||||
The configuration changes will take effect in new codespaces created from the repository. To make the changes take effect in existing codespaces, you will need to pull the updates to the `devcontainer.json` file into your codespace, then rebuild the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
|
||||
구성 변경 내용은 리포지토리에서 만든 새 codespace에 적용됩니다. 기존 codespace에서 변경 내용을 적용하려면 파일에 대한 업데이트를 `devcontainer.json` codespace로 끌어온 다음 codespace에 대한 컨테이너를 다시 빌드해야 합니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)”를 참조하세요.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -59,21 +64,21 @@ The configuration changes will take effect in new codespaces created from the re
|
||||
|
||||
{% note %}
|
||||
|
||||
To add features 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).
|
||||
코드스페이스에 연결되지 않고 로컬로 작업하는 동안 {% 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).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
2. Start typing "Configure" and select **Codespaces: Configure Dev Container Features**.
|
||||
2. "구성"을 입력하고 **Codespaces: Dev Container Features 구성** 을 선택합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Update your feature selections, then click **OK**.
|
||||
3. 기능 선택을 업데이트한 다음 **확인** 을 클릭합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
4. If you're working in a codespace, a prompt will appear in the lower-right corner. To rebuild the container and apply the changes to the codespace you're working in, click **Rebuild Now**.
|
||||
4. codespace에서 작업하는 경우 오른쪽 아래 모서리에 프롬프트가 표시됩니다. 컨테이너를 다시 빌드하고 작업 중인 codespace에 변경 내용을 적용하려면 **지금 다시 빌드** 를 클릭합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
||||
@@ -8,12 +8,12 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Creation and deletion
|
||||
ms.openlocfilehash: 09c3a73ec5e41f0170f1d3cd66df139bb2a497e5
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 4a12c848fa7400ec336f5ad086eb4d2858a431f0
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158695'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180821'
|
||||
---
|
||||
## codespace 만들기
|
||||
|
||||
@@ -98,4 +98,4 @@ This codespace is currently running in recovery mode due to a container error.
|
||||
```
|
||||
만들기 로그를 검토하고 필요에 따라 개발 컨테이너 구성을 업데이트합니다. 자세한 내용은 “[{% data variables.product.prodname_github_codespaces %} 로그](/codespaces/troubleshooting/github-codespaces-logs)”를 참조하세요.
|
||||
|
||||
그런 다음 codespace를 다시 시작하거나 컨테이너를 다시 빌드할 수 있습니다. 자세한 내용은 “[개발 컨테이너 소개](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)”를 참조하세요.
|
||||
그런 다음 codespace를 다시 시작하거나 컨테이너를 다시 빌드할 수 있습니다. 컨테이너를 다시 빌드하는 방법에 대한 자세한 내용은 "[개발 컨테이너 소개"를 참조하세요.](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: '{% data variables.product.prodname_projects_v1 %}에서 마이그레이션'
|
||||
intro: '{% data variables.projects.projects_v1_board %}를 새 {% data variables.product.prodname_projects_v2 %} 환경으로 마이그레이션할 수 있습니다.'
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,53 +10,57 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148109687'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**참고:**
|
||||
|
||||
- 마이그레이션하는 프로젝트에 1,200개 이상의 항목이 포함된 경우 열려 있는 이슈에 높은 우선 순위가 지정되고, 그 다음에는 열린 끌어오기 요청 및 메모가 표시됩니다. 나머지 공간은 종결된 이슈, 병합된 끌어오기 요청 및 닫힌 끌어오기 요청에 사용됩니다. 이 제한으로 인해 마이그레이션할 수 없는 항목은 보관 파일로 이동됩니다. 보관 제한인 10,000개 항목에 도달하면 추가 항목이 마이그레이션되지 않습니다.
|
||||
- 메모 카드는 초안 이슈로 변환되고 내용은 초안 이슈의 본문에 저장됩니다. 정보가 누락된 것으로 표시되면 숨겨진 필드를 표시합니다. 자세한 내용은 “[필드 표시 및 숨기기](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)”를 참조하세요.
|
||||
- 자동화는 마이그레이션되지 않습니다.
|
||||
- 심사, 보관 및 작업은 마이그레이션되지 않습니다.
|
||||
- 마이그레이션 후에는 새로 마이그레이션된 프로젝트와 이전 프로젝트가 동기화된 상태로 유지되지 않습니다.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 프로젝트 마이그레이션 정보
|
||||
|
||||
프로젝트 보드를 모든 새 {% data variables.product.prodname_projects_v2 %} 환경으로 마이그레이션하고 테이블, 여러 보기, 새 자동화 옵션, 강력한 필드 형식을 사용해 볼 수 있습니다. 자세한 내용은 “[프로젝트 정보](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”를 참조하세요.
|
||||
|
||||
## 조직 프로젝트 보드 마이그레이션
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. 왼쪽에서 **프로젝트(클래식)** 를 클릭합니다.
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## 사용자 프로젝트 보드 마이그레이션
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. 프로필 페이지의 상단에 있는 기본 탐색에서 {% octicon "project" aria-label="The project board icon" %} **프로젝트** 를 클릭합니다.
|
||||
|
||||
1. 프로젝트 목록 위에서 **프로젝트(클래식)** 를 클릭합니다.
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## 리포지토리 프로젝트 보드 마이그레이션
|
||||
|
||||
{% note %}
|
||||
|
||||
**참고:** {% data variables.projects.projects_v2_caps %}는 리포지토리 수준 프로젝트를 지원하지 않습니다. 리포지토리 프로젝트 보드를 마이그레이션하면 리포지토리 프로젝트를 소유하는 조직 또는 개인 계정으로 마이그레이션되고 마이그레이션된 프로젝트는 원래 리포지토리에 고정됩니다.
|
||||
**Notes:**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. 리포지토리 이름에서 {% octicon "project" aria-label="The project board icon" %} **프로젝트** 를 클릭합니다.
|
||||
|
||||
1. **프로젝트(클래식)** 를 클릭합니다.
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
## About project migration
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
## Migrating an organization project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -10,12 +10,12 @@ redirect_from:
|
||||
type: overview
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 768234aa5e6c9cfbca6a6144a80ac2868f3316ce
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 3190379652fe1c95b8ea6ec7f864c44b72d9a7f7
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158863'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180763'
|
||||
---
|
||||
## {% data variables.product.prodname_projects_v2 %} 정보
|
||||
|
||||
@@ -27,7 +27,7 @@ ms.locfileid: '148158863'
|
||||
|
||||
### 항목에 메타데이터 추가
|
||||
|
||||
사용자 지정 필드를 사용하여 문제에 메타데이터를 추가하고, 요청을 끌어오고, 문제 초안을 작성하고, 항목 특성에 대한 보다 풍부한 보기를 빌드할 수 있습니다. 현재 문제 및 끌어오기 요청에 대해 존재하는 기본 제공 메타데이터(담당자, 마일스톤, 레이블 등)로 제한되지 않습니다. 예를 들어 다음 메타데이터를 사용자 지정 필드로 추가할 수 있습니다.
|
||||
사용자 지정 필드를 사용하여 이슈, 끌어오기 요청 및 초안 문제에 메타데이터를 추가하고 항목 특성에 대한 보다 풍부한 보기를 빌드할 수 있습니다. 현재 문제 및 끌어오기 요청에 대해 존재하는 기본 제공 메타데이터(담당자, 마일스톤, 레이블 등)로 제한되지 않습니다. 예를 들어 다음 메타데이터를 사용자 지정 필드로 추가할 수 있습니다.
|
||||
|
||||
- 목표 배달 날짜를 추적하는 날짜 필드.
|
||||
- 작업의 복잡성을 추적하는 숫자 필드.
|
||||
@@ -41,9 +41,9 @@ ms.locfileid: '148158863'
|
||||
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
작업 목록을 사용하여 문제의 계층 구조를 빌드하고, 문제를 더 작은 하위 작업으로 나누고, 문제 간에 새로운 관계를 만들 수 있습니다. 자세한 내용은 "[작업 목록 정보](/issues/tracking-your-work-with-issues/about-tasklists)"를 참조하세요.
|
||||
작업 목록을 사용하여 문제의 계층 구조를 빌드하고, 문제를 더 작은 하위 작업으로 나누고, 문제 간에 새 관계를 만들 수 있습니다. 자세한 내용은 "[작업 목록 정보"를 참조하세요.](/issues/tracking-your-work-with-issues/about-tasklists)
|
||||
|
||||
이러한 관계는 프로젝트의 추적됨 및 트랙 필드뿐만 아니라 문제에 표시됩니다. 다른 문제로 추적되는 문제를 기준으로 필터링할 수 있으며, 테이블 보기를 추적 기준 필드별로 그룹화하여 하위 작업 목록의 모든 부모 문제를 표시할 수도 있습니다.
|
||||
이러한 관계는 프로젝트의 추적 기준 및 트랙 필드뿐만 아니라 문제에 표시됩니다. 다른 문제로 추적되는 문제를 기준으로 필터링할 수 있으며, 테이블 뷰를 추적 기준 필드별로 그룹화하여 하위 작업 목록의 모든 부모 문제를 표시할 수도 있습니다.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 트랙 및 추적 기준 필드 정보
|
||||
shortTitle: About Tracks and Tracked-by fields
|
||||
title: 필드별 트랙 및 추적 정보
|
||||
shortTitle: About Tracks and Tracked by fields
|
||||
intro: 프로젝트에서 문제의 하위 작업을 볼 수 있습니다.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -8,26 +8,26 @@ versions:
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 74cd26d20882a00ac8c7ac1d109cc6810286cec6
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 44c1fcf3ed4495b57a0f2dbe3e92076f0e815502
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160038'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180747'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
작업 목록에 하위 작업을 추가할 때 프로젝트에서 트랙 및 추적 기준 필드를 사용하도록 설정하여 문제 간의 관계를 확인할 수 있습니다. 작업 목록에서 문제 계층을 만드는 방법에 대한 자세한 내용은 "[작업 목록 정보](/issues/tracking-your-work-with-issues/about-tasklists)"를 참조하세요.
|
||||
작업 목록에 하위 작업을 추가할 때 프로젝트의 트랙 및 추적 기준 필드를 사용하도록 설정하여 문제 간의 관계를 확인할 수 있습니다. 작업 목록에서 문제 계층을 만드는 방법에 대한 자세한 내용은 "[작업 목록 정보](/issues/tracking-your-work-with-issues/about-tasklists)"를 참조하세요.
|
||||
|
||||
추적 기준 필드를 사용하여 항목을 그룹화하여 각 문제의 하위 작업과 항목을 완료하는 데 필요한 작업을 명확하게 보여 주는 보기를 만들 수 있습니다. 자세한 내용은 "[테이블 레이아웃의 필드 값별로 그룹화"를 참조하세요](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#grouping-by-field-values-in-table-layout).
|
||||
추적 기준 필드를 사용하여 항목을 그룹화하여 각 문제의 하위 작업과 항목을 완료하는 데 필요한 작업을 명확하게 보여 주는 보기를 만들 수 있습니다. 자세한 내용은 "[테이블 레이아웃의 필드 값별 그룹화"를 참조하세요](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#grouping-by-field-values-in-table-layout).
|
||||
|
||||
추적 기준 필드를 기준으로 필터링하여 특정 문제로 추적되는 항목만 표시할 수도 있습니다. "tracked-by" 입력을 시작하고 목록에서 문제를 선택하거나 리포지토리 및 문제 번호를 알고 있는 경우 아래 필터를 전체로 입력할 수 있습니다.
|
||||
추적 기준 필드를 기준으로 필터링하여 특정 문제에 의해 추적되는 항목만 표시할 수도 있습니다. "tracked-by" 입력을 시작하고 목록에서 문제를 선택하거나 리포지토리 및 문제 번호를 알고 있는 경우 아래 필터를 전체로 입력할 수 있습니다.
|
||||
|
||||
```
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
필터를 사용하려면 를 리포지토리 소유자로, `<REPO>` 를 리포지토리 이름으로, `<ISSUE NUMBER>` 를 문제 번호로 바꿉 `<OWNER>` 다. 자세한 내용은 “[프로젝트 필터링](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)”을 참조하세요.
|
||||
필터를 사용하려면 를 리포지토리 소유자, `<REPO>` 리포지토리 이름으로, `<ISSUE NUMBER>` 를 문제 번호로 바꿉 `<OWNER>` 다. 자세한 내용은 “[프로젝트 필터링](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)”을 참조하세요.
|
||||
|
||||
### 추적 기준 필드 사용
|
||||
|
||||
|
||||
@@ -6,12 +6,12 @@ versions:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /early-access/issues/about-tasklists
|
||||
ms.openlocfilehash: e35065ae4de634bb7a2da815e0a860c7c0b92234
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 69cdde1bb071f963b1a2f58ef1227bc96ab9d869
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160128'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180787'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
@@ -27,21 +27,11 @@ ms.locfileid: '148160128'
|
||||
|
||||
### {% data variables.projects.projects_v2 %}과의 통합 정보
|
||||
|
||||
프로젝트의 측면 패널에는 이동 경로 메뉴의 계층 구조에 문제의 위치가 표시되므로 작업 목록에 포함된 문제를 탐색할 수 있습니다. 프로젝트 보기에 트랙 및 추적 기준 필드를 추가하여 문제 간의 관계를 빠르게 확인할 수도 있습니다. 자세한 내용은 "[트랙 및 추적 기준 필드 정보"를 참조하세요](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
프로젝트의 측면 패널에는 이동 경로 메뉴의 계층 구조에 문제의 위치가 표시되므로 작업 목록에 포함된 문제를 탐색할 수 있습니다. 프로젝트 보기에 트랙 및 추적 기준 필드를 추가하여 문제 간의 관계를 빠르게 확인할 수도 있습니다. 자세한 내용은 "[필드별 트랙 및 추적 정보"를 참조하세요](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
|
||||
## 작업 목록 만들기
|
||||
|
||||
작업 목록을 만들려면 "작업 목록 추가" 단추를 사용하거나 Markdown 문제를 편집할 수 있습니다.
|
||||
|
||||
### "작업 목록 추가" 단추를 사용하여 작업 목록 만들기
|
||||
|
||||
작업 목록을 만들기 위해 편집할 수 있는 문제 설명의 맨 아래에 **있는 {% octicon "checklist" aria-label="The checklist icon" %} 작업 목록 추가** 단추를 클릭합니다.
|
||||
|
||||
|
||||
|
||||
### Markdown을 사용하여 작업 목록 만들기
|
||||
|
||||
문제 설명에서 Markdown을 사용하여 작업 목록을 만들 수 있습니다. 펜스 코드 블록을 만들고 여는 백틱 옆에 포함합니다 `[tasklist]` . 각 항목 `- [ ]` 앞에 다른 문제 또는 텍스트에 대한 링크를 포함하고 있습니다. 필요에 따라 제목을 목록 맨 위에 Markdown 헤더로 포함할 수 있습니다.
|
||||
문제 설명에서 Markdown을 사용하여 작업 목록을 만들 수 있습니다. 펜스 코드 블록을 만들고 여는 백틱 옆에 포함합니다 `[tasklist]` . 그런 다음 각 항목의 서문 앞에 `- [ ]` 다른 문제 또는 텍스트에 대한 링크를 포함할 수 있습니다. 필요에 따라 제목을 목록 맨 위에 Markdown 헤더로 포함할 수 있습니다.
|
||||
|
||||
````
|
||||
```[tasklist]
|
||||
@@ -50,10 +40,11 @@ ms.locfileid: '148160128'
|
||||
- [ ] Draft issue title
|
||||
```
|
||||
````
|
||||
|
||||
Markdown은 {% data variables.product.product_name %}에 의해 작업 목록으로 렌더링됩니다. 그런 다음, UI를 사용하여 변경하고 문제 및 초안 문제를 추가할 수 있습니다. 문제 설명을 편집하는 경우 Markdown을 직접 수정하거나 Markdown을 복사하여 다른 문제의 작업 목록을 복제할 수 있습니다.
|
||||
|
||||
서식 지정 도구 모음에서 {% octicon "checklist" aria-label="The checklist icon" %}을 클릭하여 새 문제를 만들거나 문제 설명을 편집할 때 작업 목록을 삽입할 수도 있습니다.
|
||||
|
||||
|
||||
|
||||
## 작업 목록에 문제 추가
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 17226308ffb5d7144dfe62d79f1f6cd3a1f63819
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180855"
|
||||
---
|
||||
1. Shift<kbd>명령</kbd>+<kbd>P</kbd>(Mac) 또는 <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd></kbd>+ P(Windows/Linux)를 사용하여 {% data variables.product.prodname_vscode_command_palette_shortname %}에 액세스합니다.<kbd></kbd>
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 0083a6bd4cd85d02754b449ecccdfa22f52cc358
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180860"
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**팁:** 경우에 따라 전체 다시 빌드를 수행하여 캐시를 지우고 새 이미지로 컨테이너를 다시 빌드할 수 있습니다. 자세한 내용은 "[컨테이너의 전체 다시 빌드 수행"을 참조하세요](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container).
|
||||
|
||||
{% endtip %}
|
||||
@@ -1,5 +1,13 @@
|
||||
1. Access the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
---
|
||||
ms.openlocfilehash: 9a1e503111789036b99e1f31b9078bb28e4d57f8
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180847"
|
||||
---
|
||||
1. {% data variables.product.prodname_vscode_command_palette_shortname %}(<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd>(Mac)/<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>(Windows/Linux))에 액세스한 다음 “rebuild”라고 입력을 시작합니다. **codespace: 컨테이너 다시 빌드** 를 선택합니다.
|
||||
|
||||
|
||||
|
||||
|
||||
{% indented_data_reference reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
@@ -1,10 +1,2 @@
|
||||
---
|
||||
ms.openlocfilehash: 55a01fbe1358fc0fffc11f146b973d79242c5235
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148109605"
|
||||
---
|
||||
1. 조직 이름에서 {% octicon "project" aria-label="The Projects icon" %} **프로젝트** 를 클릭합니다.
|
||||
{% ifversion fpt or ghes or ghec %}  프로젝트 탭 {% else %}  프로젝트 탭 {% endif %}
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 989d63ee95229407cd3c3b05f5cfb41bd9038aee
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 23da81a1051f71cceb256e281271dc5eff03d7b2
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ko-KR
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159961"
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180755"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**참고:** 프로젝트의 작업 목록 및 트랙 및 추적 기준 필드는 현재 프라이빗 베타로 제공되며 변경될 수 있습니다. 작업 목록을 시도하고 새 필드를 사용하려는 경우 [대기 목록에](https://aka.ms/tasklist-roadmap-signup) 조인할 수 있습니다.
|
||||
**참고:** 작업 목록 및 프로젝트 필드별로 추적되는 트랙은 현재 프라이빗 베타로 제공되며 변경될 수 있습니다. 작업 목록을 시도하고 새 필드를 사용하려는 경우 [대기 목록에](https://aka.ms/tasklist-roadmap-signup) 조인할 수 있습니다.
|
||||
|
||||
{% endnote %}
|
||||
@@ -576,7 +576,7 @@ translations/zh-CN/content/admin/identity-and-access-management/using-built-in-a
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
|
||||
@@ -725,6 +725,7 @@ translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-
|
||||
translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
|
||||
@@ -748,7 +749,6 @@ 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/syntax-for-githubs-form-schema.md,broken liquid tags
|
||||
translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
|
||||
translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
|
||||
translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
|
||||
@@ -787,7 +787,7 @@ translations/zh-CN/content/education/manage-coursework-with-github-classroom/int
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
|
||||
@@ -820,7 +820,6 @@ translations/zh-CN/content/get-started/quickstart/github-glossary.md,broken liqu
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/about-git-rebase.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/github-mobile.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error
|
||||
translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
@@ -844,12 +843,13 @@ translations/zh-CN/content/graphql/reference/unions.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
|
||||
@@ -937,6 +937,7 @@ translations/zh-CN/content/repositories/releasing-projects-on-github/managing-re
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
|
||||
translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/apps/oauth-applications.md,rendering error
|
||||
translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
|
||||
@@ -962,7 +963,7 @@ translations/zh-CN/content/rest/guides/traversing-with-pagination.md,rendering e
|
||||
translations/zh-CN/content/rest/guides/working-with-comments.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/migrations/source-imports.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/overview/api-previews.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/troubleshooting.md,broken liquid tags
|
||||
@@ -1135,6 +1136,7 @@ translations/zh-CN/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/member-privileges.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/navigate-to-org.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/organization-wide-project.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/organizations/repository-defaults.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/security-and-analysis.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/security.md,rendering error
|
||||
|
||||
|
@@ -484,6 +484,7 @@ translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assi
|
||||
translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
|
||||
translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
|
||||
translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
translations/de-DE/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
|
||||
translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
|
||||
translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md,rendering error
|
||||
translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
|
||||
@@ -572,7 +573,7 @@ translations/de-DE/content/admin/identity-and-access-management/using-built-in-a
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
|
||||
@@ -740,6 +741,7 @@ translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-
|
||||
translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
|
||||
translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
|
||||
translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
|
||||
translations/de-DE/content/code-security/security-overview/about-the-security-overview.md,rendering error
|
||||
translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
|
||||
@@ -753,39 +755,22 @@ translations/de-DE/content/code-security/supply-chain-security/understanding-you
|
||||
translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
|
||||
translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/getting-started/quickstart.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
|
||||
translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
|
||||
translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md,broken liquid tags
|
||||
translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md,rendering error
|
||||
translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
|
||||
translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
|
||||
translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
|
||||
@@ -849,7 +834,7 @@ translations/de-DE/content/education/manage-coursework-with-github-classroom/int
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,broken liquid tags
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
|
||||
translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
|
||||
translations/de-DE/content/education/quickstart.md,rendering error
|
||||
@@ -911,6 +896,7 @@ translations/de-DE/content/graphql/reference/unions.md,rendering error
|
||||
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
|
||||
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,broken liquid tags
|
||||
translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
|
||||
translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md,rendering error
|
||||
@@ -1167,7 +1153,6 @@ translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-
|
||||
translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
|
||||
translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
|
||||
@@ -1256,6 +1241,7 @@ translations/de-DE/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/member-privileges.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/navigate-to-org.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/organization-wide-project.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/organizations/repository-defaults.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/security-and-analysis.md,rendering error
|
||||
translations/de-DE/data/reusables/organizations/security.md,rendering error
|
||||
@@ -1278,7 +1264,6 @@ translations/de-DE/data/reusables/pages/sidebar-pages.md,rendering error
|
||||
translations/de-DE/data/reusables/project-management/choose-visibility.md,rendering error
|
||||
translations/de-DE/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/projects/graphql-ghes.md,rendering error
|
||||
translations/de-DE/data/reusables/projects/projects-filters.md,broken liquid tags
|
||||
translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
|
||||
translations/de-DE/data/reusables/pull_requests/default_merge_option.md,rendering error
|
||||
translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
|
||||
|
||||
|
@@ -566,7 +566,7 @@ translations/fr-FR/content/admin/identity-and-access-management/using-built-in-a
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/fr-FR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,rendering error
|
||||
@@ -825,13 +825,12 @@ translations/fr-FR/content/discussions/managing-discussions-for-your-community/m
|
||||
translations/fr-FR/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
|
||||
translations/fr-FR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
|
||||
translations/fr-FR/content/discussions/quickstart.md,rendering error
|
||||
translations/fr-FR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,broken liquid tags
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
|
||||
translations/fr-FR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
|
||||
translations/fr-FR/content/education/quickstart.md,rendering error
|
||||
@@ -893,6 +892,7 @@ translations/fr-FR/content/graphql/reference/unions.md,rendering error
|
||||
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
|
||||
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/fr-FR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/fr-FR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,broken liquid tags
|
||||
translations/fr-FR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/fr-FR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
|
||||
translations/fr-FR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md,rendering error
|
||||
@@ -1235,6 +1235,7 @@ translations/fr-FR/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/member-privileges.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/navigate-to-org.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/organization-wide-project.md,broken liquid tags
|
||||
translations/fr-FR/data/reusables/organizations/repository-defaults.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/security-and-analysis.md,rendering error
|
||||
translations/fr-FR/data/reusables/organizations/security.md,rendering error
|
||||
|
||||
|
@@ -763,17 +763,14 @@ translations/ko-KR/content/code-security/supply-chain-security/understanding-you
|
||||
translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
|
||||
translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
|
||||
translations/ko-KR/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/ko-KR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
|
||||
translations/ko-KR/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md,rendering error
|
||||
translations/ko-KR/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,rendering error
|
||||
translations/ko-KR/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,broken liquid tags
|
||||
translations/ko-KR/content/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide.md,rendering error
|
||||
translations/ko-KR/content/codespaces/getting-started/deep-dive.md,rendering error
|
||||
translations/ko-KR/content/codespaces/getting-started/quickstart.md,rendering error
|
||||
translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,rendering error
|
||||
translations/ko-KR/content/codespaces/overview.md,rendering error
|
||||
translations/ko-KR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,rendering error
|
||||
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file.md,broken liquid tags
|
||||
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,rendering error
|
||||
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
|
||||
translations/ko-KR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,rendering error
|
||||
@@ -898,6 +895,7 @@ translations/ko-KR/content/graphql/reference/unions.md,rendering error
|
||||
translations/ko-KR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
|
||||
translations/ko-KR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/ko-KR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/ko-KR/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,broken liquid tags
|
||||
translations/ko-KR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,rendering error
|
||||
translations/ko-KR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md,rendering error
|
||||
@@ -1158,7 +1156,6 @@ translations/ko-KR/data/reusables/codespaces/customize-vcpus-and-ram.md,broken l
|
||||
translations/ko-KR/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
|
||||
translations/ko-KR/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
|
||||
translations/ko-KR/data/reusables/codespaces/publishing-template-codespaces.md,rendering error
|
||||
translations/ko-KR/data/reusables/codespaces/rebuild-command.md,broken liquid tags
|
||||
translations/ko-KR/data/reusables/codespaces/secrets-on-start.md,broken liquid tags
|
||||
translations/ko-KR/data/reusables/command_line/provide-an-access-token.md,rendering error
|
||||
translations/ko-KR/data/reusables/copilot/config-enable-copilot-in-neovim.md,rendering error
|
||||
@@ -1244,6 +1241,7 @@ translations/ko-KR/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/member-privileges.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/navigate-to-org.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/organization-wide-project.md,broken liquid tags
|
||||
translations/ko-KR/data/reusables/organizations/repository-defaults.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/restricted-app-access-requests.md,rendering error
|
||||
translations/ko-KR/data/reusables/organizations/security-and-analysis.md,rendering error
|
||||
|
||||
|
@@ -817,12 +817,9 @@ translations/ru-RU/content/code-security/supply-chain-security/understanding-you
|
||||
translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
|
||||
translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,rendering error
|
||||
translations/ru-RU/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
|
||||
translations/ru-RU/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/overview.md,rendering error
|
||||
translations/ru-RU/content/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags
|
||||
translations/ru-RU/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,rendering error
|
||||
translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
|
||||
@@ -947,6 +944,7 @@ translations/ru-RU/content/issues/organizing-your-work-with-project-boards/manag
|
||||
translations/ru-RU/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/ru-RU/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/ru-RU/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md,rendering error
|
||||
translations/ru-RU/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,broken liquid tags
|
||||
translations/ru-RU/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags
|
||||
translations/ru-RU/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,rendering error
|
||||
translations/ru-RU/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
@@ -1249,7 +1247,6 @@ translations/ru-RU/data/reusables/codespaces/codespaces-monthly-billing.md,rende
|
||||
translations/ru-RU/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
|
||||
translations/ru-RU/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
|
||||
translations/ru-RU/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
|
||||
translations/ru-RU/data/reusables/codespaces/rebuild-command.md,broken liquid tags
|
||||
translations/ru-RU/data/reusables/codespaces/secrets-on-start.md,broken liquid tags
|
||||
translations/ru-RU/data/reusables/command_line/provide-an-access-token.md,rendering error
|
||||
translations/ru-RU/data/reusables/copilot/config-enable-copilot-in-neovim.md,rendering error
|
||||
|
||||
|
@@ -12,11 +12,11 @@ children:
|
||||
- /security-in-github-codespaces
|
||||
- /performing-a-full-rebuild-of-a-container
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 223d3b146d829f129de39b43b51b6ab9e8aef411
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159200'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180806'
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Выполнение полного перестроения контейнера
|
||||
intro: 'Если у вас недостаточно места на диске или вы хотите убедиться, что конфигурация контейнера разработки будет работать в новых пространствах кода, можно выполнить полное перестроение контейнера.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Full rebuilds
|
||||
ms.openlocfilehash: f844d5f92073adf01c3b1a1100e6fe1912b2d7ad
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180851'
|
||||
---
|
||||
## Сведения о перестроении контейнера
|
||||
|
||||
При работе в codespace среда разработки представляет собой контейнер Docker, который выполняется на виртуальной машине. Если вы вносите изменения в конфигурацию контейнера разработки из codespace и хотите применить эти изменения к текущему codespace, необходимо перестроить контейнер.
|
||||
|
||||
По умолчанию при перестроении контейнера {% data variables.product.prodname_github_codespaces %} ускорит процесс сборки, повторно используя кэшированные образы из предыдущих сборок контейнера. Обычно это самый быстрый способ реализовать изменения в конфигурации контейнера разработки по следующим причинам.
|
||||
- {% data variables.product.prodname_github_codespaces %} может повторно использовать образы в кэше, а не удалять их из реестров контейнеров.
|
||||
- Части конфигурации контейнера разработки, определяющие способ сборки контейнера, такие как функции контейнера разработки и инструкции Dockerfile, возможно, уже реализованы на уровнях образов в кэше, поэтому вам не придется ждать повторного запуска этих процессов. (Однако команды в конфигурации, которые выполняются после сборки контейнера, например `onCreateCommand`, будут выполняться снова.)
|
||||
|
||||
Иногда может потребоваться выполнить полную перестройку контейнера. При полном перестроении {% data variables.product.prodname_github_codespaces %} очищает все контейнеры, образы и тома Docker из кэша, а затем перестраивает контейнер с новыми извлеченными образами. Вся настройка, определенная в конфигурации, будет выполняться снова, создавая новые слои образов. Вы можете выполнить полную перестройку после многих итераций перестроения контейнера с кэшируемыми образами в таких ситуациях, как показано ниже.
|
||||
|
||||
- Необходимо убедиться, что настройка, определенная в конфигурации, не зависит от кэшированных образов и будет выполняться по мере необходимости, когда кто-то создает новое пространство кода на основе конфигурации. Например, зависимость может быть удалена из базового образа с момента последнего извлечения в codespace.
|
||||
- Вы хотите освободить дисковое пространство, используемое кэшем, например, если у вас мало места на диске или вы хотите свести к минимуму расходы на хранилище. Кэш образов может использовать значительный объем дискового пространства, если вы несколько раз меняли базовый образ, если вы внесли большое количество итеративных изменений в конфигурацию или если вы используете несколько контейнеров с Docker Compose.
|
||||
|
||||
## Выполнение полного перестроения
|
||||
|
||||
Полное перестроение можно выполнить в {% data variables.product.prodname_vscode %}.
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
1. Начните вводить "Перестроение" и выберите **Codespaces: Полный контейнер перестроения**.
|
||||
|
||||
|
||||
|
||||
## Сохранение данных при полном перестроении
|
||||
|
||||
Все файлы и папки, содержащиеся в каталоге `/workspaces` codespace, всегда сохраняются при перестроении. Вам не нужно изменять параметры или добавлять конфигурацию, чтобы сохранить содержимое этого каталога при полной перестройке.
|
||||
|
||||
Если вы хотите сохранить файлы за пределами `/workspaces` каталога при полном перестроении, можно создать в нужном расположении в контейнере символьную ссылку (символьную ссылку) на постоянный каталог. Например, в каталоге `/workspaces/.devcontainer` можно создать каталог `config`, который будет сохранен при перестроении. Затем вы можете связать символьной ссылкой каталог `config` и его содержимое как `postCreateCommand` в файле `devcontainer.json`.
|
||||
|
||||
```json
|
||||
{
|
||||
"image": "mcr.microsoft.com/vscode/devcontainers/base:alpine",
|
||||
"postCreateCommand": ".devcontainer/postCreate.sh"
|
||||
}
|
||||
```
|
||||
|
||||
В приведенном ниже примере файла `postCreate.sh` содержимое каталога `config` связано символической ссылкой с домашним каталогом.
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
ln -sf $PWD/.devcontainer/config $HOME/config && set +x
|
||||
```
|
||||
|
||||
## Дополнительные материалы
|
||||
- [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using the Visual Studio Code Command Palette in GitHub Codespaces
|
||||
intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in {% data variables.product.prodname_github_codespaces %}.'
|
||||
title: Использование палитры команд Visual Studio Code в GitHub Codespaces
|
||||
intro: 'Функцию палитры команд {% data variables.product.prodname_vscode %} можно использовать для выполнения многих команд {% data variables.product.prodname_github_codespaces %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -12,62 +12,67 @@ shortTitle: VS Code Command Palette
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
|
||||
ms.openlocfilehash: acd462dd1c0b60dced529d7471b9c8638e2f6e91
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180814'
|
||||
---
|
||||
## Сведения о {% data variables.product.prodname_vscode_command_palette %}
|
||||
|
||||
## About the {% data variables.product.prodname_vscode_command_palette %}
|
||||
{% data variables.product.prodname_vscode_command_palette_shortname %} является одним из основных компонентов {% data variables.product.prodname_vscode %} и доступен для использования в {% data variables.product.prodname_github_codespaces %}. Палитра команд позволяет получить доступ ко многим командам для {% data variables.product.prodname_github_codespaces %} и {% data variables.product.prodname_vscode_shortname %}. Дополнительные сведения об использовании {% data variables.product.prodname_vscode_command_palette_shortname %} см. в разделе [Пользовательский интерфейс](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) в документации по {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
The {% data variables.product.prodname_vscode_command_palette_shortname %} is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in {% data variables.product.prodname_github_codespaces %}. The Command Palette allows you to access many commands for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
## Доступ к {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
|
||||
## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %}
|
||||
Доступ к {% data variables.product.prodname_vscode_command_palette_shortname %} можно получить разными способами.
|
||||
|
||||
You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways.
|
||||
- <kbd>SHIFT</kbd>+<kbd>COMMAND</kbd>+<kbd>P</kbd> (Mac) / <kbd>CTRL</kbd>+<kbd>SHIFT</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
|
||||
- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
|
||||
|
||||
Note that this command is a reserved keyboard shortcut in Firefox.
|
||||
Обратите внимание, что эта команда является зарезервированным сочетанием клавиш в Firefox.
|
||||
- <kbd>F1</kbd>
|
||||
- From the Application Menu, click **View > Command Palette…**.
|
||||
- В меню приложения выберите пункт **Вид > Палитра команд...** .
|
||||
|
||||
|
||||
|
||||
|
||||
## Commands for {% data variables.product.prodname_codespaces %}
|
||||
## Команды для {% data variables.product.prodname_codespaces %}
|
||||
|
||||
To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces".
|
||||
Чтобы просмотреть все команды, связанные с {% data variables.product.prodname_github_codespaces %}, [откройте{% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), а затем начните вводить "Codespaces".
|
||||
|
||||
|
||||
|
||||
|
||||
### Suspending or stopping a codespace
|
||||
### Приостановка или остановка codespace
|
||||
|
||||
If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes.
|
||||
Если вы добавите новый секрет или измените тип компьютера, вам придется остановить и перезапустить пространство кода, чтобы применить изменения.
|
||||
|
||||
To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**.
|
||||
Чтобы приостановить или остановить контейнер codespace, [откройте {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) и начните вводить "остановить". Выберите **Codespaces: остановить текущее codespace**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Adding a predefined dev container configuration
|
||||
### Добавление предопределенной конфигурации контейнера разработки
|
||||
|
||||
To add a predefined dev container configuration, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
||||
Чтобы добавить предопределенную конфигурацию контейнера разработки, [получите доступ к {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), а затем начните вводить "контейнер разработки". Выберите **Codespaces: добавление файлов конфигурации для контейнера разработки...** .
|
||||
|
||||
|
||||
|
||||
|
||||
### Rebuilding a codespace
|
||||
### Перестроение codespace
|
||||
|
||||
If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes.
|
||||
Если вы добавите контейнер разработки или измените любой из файлов конфигурации (`devcontainer.json` и `Dockerfile`), вам придется перестроить codespace, чтобы применить изменения.
|
||||
|
||||
To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
Чтобы перестроить контейнер, [откройте {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) и начните вводить "перестроить". Выберите **Codespaces: перестроить контейнер**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
### Codespaces logs
|
||||
### Журналы Codespaces
|
||||
|
||||
You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs.
|
||||
Вы можете использовать {% data variables.product.prodname_vscode_command_palette_shortname %} для доступа к журналам создания codespace или экспорта всех журналов.
|
||||
|
||||
To retrieve the logs for {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_github_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup.
|
||||
Чтобы получить журналы для {% data variables.product.prodname_github_codespaces %}, [откройте {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), а затем начните вводить "log". Выберите **Codespaces: Экспорт журналов** , чтобы экспортировать все журналы, связанные с {% data variables.product.prodname_github_codespaces %}, или выберите **Codespaces: просмотр журналов создания** , чтобы просмотреть журналы, связанные с установкой.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
## Дополнительные материалы
|
||||
|
||||
- "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
- [Использование {% data variables.product.prodname_github_codespaces %} в {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: The codespace lifecycle
|
||||
intro: 'You can develop in a {% data variables.product.prodname_github_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.'
|
||||
title: Жизненный цикл codespace
|
||||
intro: 'Вы можете разрабатывать в среде {% data variables.product.prodname_github_codespaces %} и поддерживать данные на протяжении всего жизненного цикла codespace.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,58 +10,63 @@ topics:
|
||||
- Developer
|
||||
redirect_from:
|
||||
- /codespaces/developing-in-codespaces/codespaces-lifecycle
|
||||
ms.openlocfilehash: 660ced63e34c6de8025c65946542baca43534cfe
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180798'
|
||||
---
|
||||
## Сведения о жизненном цикле пространства кода
|
||||
|
||||
## About the lifecycle of a codespace
|
||||
Жизненный цикл пространства кода начинается при его создании и заканчивается при его удалении. Вы можете отключиться и переподключиться к активному пространству кода, не затрагивая выполняемые процессы. Вы можете остановить и перезапустить пространство кода без потери изменений, внесенных в проект.
|
||||
|
||||
The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
|
||||
## Создание codespace
|
||||
|
||||
## Creating a codespace
|
||||
Когда вы собираетесь работать над проектом, вы можете создать новое пространство кода или открыть существующее. Вам может потребоваться создать новое пространство кода из ветви репозитория при каждой разработке в {% data variables.product.prodname_github_codespaces %} или сохранить длительное пространство кода для функции. {% 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).
|
||||
|
||||
When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your repository each time you develop in {% data variables.product.prodname_github_codespaces %} or keep a long-running codespace for a feature. {% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
{% data reusables.codespaces.max-number-codespaces %} Аналогичным образом, если вы достигнете максимального количества активных сред codespace и попытаетесь запустить еще одну среду, вам будет предложено остановить одну из активных сред codespace.
|
||||
|
||||
{% data reusables.codespaces.max-number-codespaces %} Similarly, if you reach the maximum number of active codespaces and you try to start another, you are prompted to stop one of your active codespaces.
|
||||
|
||||
If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
|
||||
Если вы решили создавать новое пространство кода каждый раз при работе над проектом, следует регулярно отправлять изменения, чтобы все новые фиксации были включены в {% data variables.product.prodname_dotcom %}. Если вы решили использовать для своего проекта долгосрочное пространство кода, то должны выполнять вытягивание из ветви по умолчанию репозитория каждый раз, когда начинаете работать в пространстве кода, чтобы в вашей среде присутствовали последние фиксации. Этот рабочий процесс очень похож на работу с проектом на локальном компьютере.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Saving changes in a codespace
|
||||
## Сохранение изменений в пространстве кода
|
||||
|
||||
When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
При подключении к пространству кода через Интернет для веб редактора автоматически включается автосохранение и настраивается сохранение изменений после задержки. При подключении к пространству кода через {% data variables.product.prodname_vscode %}, работающий на вашем компьютере, необходимо самостоятельно включить автосохранение. Дополнительные сведения см. в разделе [Сохранение и автосохранение](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) документации по {% data variables.product.prodname_vscode %}.
|
||||
|
||||
Your work will be saved on a virtual machine in the cloud. You can close and stop a codespace and return to the saved work later. If you have unsaved changes, your editor will prompt you to save them before exiting. However, if your codespace is deleted, then your work will be deleted too. To persist your work, you will need to commit your changes and push them to your remote repository, or publish your work to a new remote repository if you created your codespace from a template. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)."
|
||||
Ваша работа будет сохранена на виртуальной машине в облаке. Вы можете закрыть и остановить codespace, а затем вернуться к сохраненной работе. Если у вас есть несохраненные изменения, перед выходом редактор предложит сохранить их. Однако при удалении codespace работа также будет удалена. Чтобы сохранить работу, необходимо зафиксировать изменения и отправить их в удаленный репозиторий или опубликовать работу в новом удаленном репозитории, если вы создали codespace на основе шаблона. Дополнительные сведения см. в статье [Использование системы управления версиями в кодовом пространстве](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace).
|
||||
|
||||
## Timeouts for {% data variables.product.prodname_github_codespaces %}
|
||||
## Время ожидания для {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
|
||||
Если вы оставите свое пространство кода работающим без взаимодействия или если выйдете из него, не остановив его явно, после некоторого периода бездействия время ожидания истечет, и пространство кода остановит работу. По умолчанию время ожидания пространства кода истекает через 30 минут бездействия, но вы можете настроить другое время ожидания для вновь создаваемых пространств кода. Дополнительные сведения о настройке времени ожидания по умолчанию для пространств кода см. в разделе [Настройка времени ожидания для {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces). Дополнительные сведения об остановке пространства кода см. в разделе [Остановка пространства кода](#stopping-a-codespace).
|
||||
|
||||
When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
|
||||
При истечении времени ожидания пространства кода данные сохраняются с момента последнего сохранения изменений. Дополнительные сведения см. в разделе [Сохранение изменений в пространстве кода](#saving-changes-in-a-codespace).
|
||||
|
||||
## Rebuilding a codespace
|
||||
## Перестроение пространства кода
|
||||
|
||||
You can rebuild your codespace to implement changes to your dev container configuration. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. By default, when you rebuild your codespace, {% data variables.product.prodname_github_codespaces %} will reuse images from your cache to speed up the rebuild process. Alternatively, you can perform a full rebuild, which clears your cache and rebuilds the container with fresh images.
|
||||
Вы можете перестроить codespace, чтобы реализовать изменения в конфигурации контейнера разработки. В большинстве случаев вместо перестроения пространства кода можно просто создать новое пространство кода. По умолчанию при перестроении codespace {% data variables.product.prodname_github_codespaces %} будет повторно использовать образы из кэша, чтобы ускорить процесс перестроения. Кроме того, можно выполнить полную перестройку, которая очищает кэш и перестраивает контейнер со свежими образами.
|
||||
|
||||
For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)" and "[Performing a full rebuild of a container](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container)."
|
||||
Дополнительные сведения см. в разделах [Общие сведения о контейнерах разработки](/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).
|
||||
|
||||
## Stopping a codespace
|
||||
## Остановка пространства кода
|
||||
|
||||
{% data reusables.codespaces.stopping-a-codespace %} For more information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)."
|
||||
{% data reusables.codespaces.stopping-a-codespace %} Дополнительные сведения см. в разделе [Остановка и запуск codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace).
|
||||
|
||||
## Deleting a codespace
|
||||
## Удаление codespace
|
||||
|
||||
You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
|
||||
Вы можете создать пространство кода для конкретной задачи, а затем безопасно удалить его после отправки изменений в удаленную ветвь.
|
||||
|
||||
If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
|
||||
Если вы попытаетесь удалить пространство кода с неотправленными фиксациями git, редактор сообщит вам, что имеются изменения, которые не были отправлены в удаленную ветвь. Вы можете отправить все необходимые изменения, а затем удалить пространство кода или продолжить, чтобы удалить пространство кода и все незафиксированные изменения. Вы также можете экспортировать код в новую ветвь, не создавая новое пространство кода. Дополнительные сведения см. в разделе [Экспорт изменений в ветвь](/codespaces/troubleshooting/exporting-changes-to-a-branch).
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
Codespace, которые были остановлены и остаются неактивными в течение указанного периода времени, будут удалены автоматически. По умолчанию неактивные codespace удаляются через 30 дней, но вы можете настроить период хранения codespace. Дополнительные сведения см. в статье [Настройка автоматического удаления сред codespace](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces).
|
||||
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
Если вы создадите 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).
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
Дополнительные сведения об удалении пространства кода см. в разделе [Удаление пространства кода](/codespaces/developing-in-codespaces/deleting-a-codespace).
|
||||
|
||||
## Losing the connection while using {% data variables.product.prodname_github_codespaces %}
|
||||
## Потеря подключения при использовании {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
{% data variables.product.prodname_github_codespaces %} — это облачная среда разработки, для которой требуется подключение к Интернету. Если во время работы в пространстве кода произойдет потеря подключения к Интернету, вы не сможете получить доступ к своему пространству кода. Однако все незафиксированные изменения будут сохранены. Когда подключение к Интернету будет восстановлено, вы сможете подключиться к пространству кода в том же состоянии, в котором оно было оставлено. Если ваше подключение к Интернету нестабильно, следует чаще фиксировать и отправлять изменения.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
Если вы знаете, что часто работаете в автономном режиме, вы можете использовать файл `devcontainer.json` с [расширением "Контейнеры разработки"](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) для {% data variables.product.prodname_vscode_shortname %} для сборки и подключения к локальному контейнеру разработки для репозитория. Дополнительные сведения см. в разделе [Разработка в контейнере](https://code.visualstudio.com/docs/remote/containers) в документации по {% data variables.product.prodname_vscode %}.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Adding features to a devcontainer.json file
|
||||
title: Добавление компонентов в файл devcontainer.json
|
||||
shortTitle: Adding features
|
||||
intro: With features, you can quickly add tools, runtimes, or libraries to your dev container configuration.
|
||||
intro: 'С помощью функций вы можете быстро добавлять средства, среды выполнения или библиотеки в конфигурацию контейнера разработки.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,34 +10,39 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
ms.openlocfilehash: 7e72739e93e83995d86baf19d62f7bf2e1c5b6bc
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180830'
|
||||
---
|
||||
{% data reusables.codespaces.about-features %} Используйте вкладки в этой статье, чтобы отобразить инструкции для каждого из этих способов добавления функций.
|
||||
|
||||
{% data reusables.codespaces.about-features %} Use the tabs in this article to display instructions for each of these ways of adding features.
|
||||
|
||||
## Adding features to a `devcontainer.json` file
|
||||
## Добавление компонентов в `devcontainer.json` файл
|
||||
|
||||
{% webui %}
|
||||
|
||||
1. Navigate to your repository on {% data variables.product.prodname_dotcom_the_website %}, find your `devcontainer.json` file, and click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
|
||||
1. Перейдите в репозиторий на {% data variables.product.prodname_dotcom_the_website %}, найдите `devcontainer.json` файл и щелкните {% octicon "pencil" aria-label="The edit icon" %}, чтобы изменить файл.
|
||||
|
||||
If you don't already have a `devcontainer.json` file, you can create one now. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
|
||||
1. To the right of the file editor, in the **Marketplace** tab, browse or search for the feature you want to add, then click the name of the feature.
|
||||
Если у `devcontainer.json` вас еще нет файла, его можно создать. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration).
|
||||
1. Справа от редактора файлов на вкладке **Marketplace** найдите или найдите функцию, которую вы хотите добавить, а затем щелкните имя функции.
|
||||
|
||||
|
||||
3. Under "Installation," click the code snippet to copy it to your clipboard, then paste the snippet into the `features` object in your `devcontainer.json` file.
|
||||
|
||||
3. В разделе "Установка" щелкните фрагмент кода, чтобы скопировать его в буфер обмена, а затем вставьте его в `features` объект в файле `devcontainer.json` .
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
...
|
||||
"ghcr.io/devcontainers/features/terraform:1": {},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. By default, the latest version of the feature will be used. To choose a different version, or configure other options for the feature, expand the properties listed under "Options" to view the available values, then add the options by manually editing the object in your `devcontainer.json` file.
|
||||
1. По умолчанию будет использоваться последняя версия компонента. Чтобы выбрать другую версию или настроить другие параметры компонента, разверните свойства, перечисленные в разделе "Параметры", чтобы просмотреть доступные значения, а затем добавьте параметры, вручную изменив объект в файле `devcontainer.json` .
|
||||
|
||||
|
||||
|
||||
|
||||
```JSON
|
||||
"features": {
|
||||
@@ -47,11 +52,11 @@ topics:
|
||||
"tflint": "latest"
|
||||
},
|
||||
...
|
||||
}
|
||||
}
|
||||
```
|
||||
1. Commit the changes to your `devcontainer.json` file.
|
||||
1. Зафиксируйте изменения в `devcontainer.json` файле.
|
||||
|
||||
The configuration changes will take effect in new codespaces created from the repository. To make the changes take effect in existing codespaces, you will need to pull the updates to the `devcontainer.json` file into your codespace, then rebuild the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
|
||||
Изменения конфигурации вступают в силу в новых пространствах кода, созданных из репозитория. Чтобы изменения вступили в силу в существующих codespaces, необходимо извлечь обновления `devcontainer.json` файла в codespace, а затем перестроить контейнер для codespace. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -59,21 +64,21 @@ The configuration changes will take effect in new codespaces created from the re
|
||||
|
||||
{% note %}
|
||||
|
||||
To add features 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).
|
||||
Чтобы добавить компоненты в {% data variables.product.prodname_vscode_shortname %} во время работы локально и не подключены к codespace, необходимо установить и включить расширение "Контейнеры разработки". Дополнительные сведения об этом расширении см. в [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.command-pallette %}
|
||||
2. Start typing "Configure" and select **Codespaces: Configure Dev Container Features**.
|
||||
2. Начните вводить "Настроить" и выберите **Codespaces: Configure Dev Container Features (Codespaces: Configure Dev Container Features).**
|
||||
|
||||
|
||||
|
||||
|
||||
3. Update your feature selections, then click **OK**.
|
||||
3. Измените выбранные компоненты, а затем нажмите кнопку **ОК**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. If you're working in a codespace, a prompt will appear in the lower-right corner. To rebuild the container and apply the changes to the codespace you're working in, click **Rebuild Now**.
|
||||
4. Если вы работаете в codespace, в правом нижнем углу появится запрос. Чтобы перестроить контейнер и применить изменения к пространству кода, в который вы работаете, нажмите кнопку **Перестроить сейчас**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
||||
@@ -8,12 +8,12 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Creation and deletion
|
||||
ms.openlocfilehash: 09c3a73ec5e41f0170f1d3cd66df139bb2a497e5
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 4a12c848fa7400ec336f5ad086eb4d2858a431f0
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158696'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180822'
|
||||
---
|
||||
## Создание codespace
|
||||
|
||||
@@ -98,4 +98,4 @@ This codespace is currently running in recovery mode due to a container error.
|
||||
```
|
||||
Просмотрите журналы создания и при необходимости обновите конфигурацию контейнера разработки. Дополнительные сведения см. в статье [Журналы {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/github-codespaces-logs).
|
||||
|
||||
Затем можно попробовать перезапустить codespace или перестроить контейнер. Дополнительные сведения см. в статье [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
Затем можно попробовать перезапустить codespace или перестроить контейнер. Дополнительные сведения о перестроении контейнера см. в разделе [Общие сведения о контейнерах разработки](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Миграция с {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'Вы можете перенести {% data variables.projects.projects_v1_board %} в новый интерфейс {% data variables.product.prodname_projects_v2 %}.'
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,53 +10,57 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148110074'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Примечания.**
|
||||
|
||||
- Если переносимый проект содержит более 1200 элементов, открытые проблемы будут приоритизированы по открытым запросам на вытягивание, а затем заметкам. Оставшееся пространство будет использоваться для закрытых проблем, объединенных запросов на вытягивание и закрытых запросов на вытягивание. Элементы, которые не могут быть перенесены из-за этого ограничения, будут перемещены в архив. Если достигнут предел архива в 10 000 элементов, дополнительные элементы не будут переноситься.
|
||||
- Карточки заметок преобразуются в черновики проблем, и содержимое сохраняется в тексте черновика. Если информация отсутствует, сделайте все скрытые поля видимыми. Дополнительные сведения см. в разделе [Отображение и скрытие полей](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields).
|
||||
- Автоматизация не будет перенесена.
|
||||
- Рассмотрение, архивация и действие не будут перенесены.
|
||||
- После миграции новый перенесенный проект и старый проект не будут синхронизированы.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Сведения о миграции проекта
|
||||
|
||||
Вы можете перенести доски проектов в новый интерфейс {% data variables.product.prodname_projects_v2 %} и испытать таблицы, использование нескольких представлений, новые параметры автоматизации и эффективные типы полей. Дополнительные сведения см. в разделе [Сведения о проектах](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
|
||||
|
||||
## Миграция доски проекта организации
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. В левой части экрана щелкните **Проекты (классическая версия)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Перенос доски проекта пользователя
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. В верхней части страницы своего профиля в главной области навигации щелкните {% octicon "project" aria-label="The project board icon" %} **Проекты**.
|
||||
|
||||
1. Над списком проектов щелкните **Проекты (классическая версия)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Перенос доски проекта в репозитории
|
||||
|
||||
{% note %}
|
||||
|
||||
**Примечание.** {% data variables.projects.projects_v2_caps %} не поддерживает проекты уровня репозитория. При миграции доска проекта репозитория будет перенесена в учетную запись организации или личную учетную запись, владеющую проектом репозитория, и перенесенный проект будет закреплен в исходном репозитории.
|
||||
**Notes:**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. Щелкните {% octicon "project" aria-label="The project board icon" %} **Проекты** под названием своего репозитория.
|
||||
|
||||
1. Щелкните **Проекты (классическая версия)** .
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
## About project migration
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
## Migrating an organization project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -10,12 +10,12 @@ redirect_from:
|
||||
type: overview
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 768234aa5e6c9cfbca6a6144a80ac2868f3316ce
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 3190379652fe1c95b8ea6ec7f864c44b72d9a7f7
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158864'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180764'
|
||||
---
|
||||
## Сведения о {% data variables.product.prodname_projects_v2 %}
|
||||
|
||||
@@ -25,9 +25,9 @@ ms.locfileid: '148158864'
|
||||
|
||||
Проекты создаются на основе проблем и запросов на вытягивание, которые вы добавляете, создавая прямые ссылки между проектом и работой. Данные автоматически синхронизируются с проектом при внесении изменений, обновлении представлений и диаграмм. Интеграция работает и в обратном порядке: при изменении сведений о запросе на вытягивание или проблеме из проекта соответствующая информация отражается в запросе на вытягивание или проблеме. Например, измените назначаемого пользователя в проекте, и это изменение отобразится в вашей проблеме. Эту интеграцию можно усилить — сгруппируйте проект по уполномоченным и измените назначение проблемы, перетащив ее в другую группу.
|
||||
|
||||
### Добавление метаданных к элементам
|
||||
### Добавление метаданных в элементы
|
||||
|
||||
Настраиваемые поля можно использовать для добавления метаданных в проблемы, запросы на вытягивание и черновики проблем, а также для создания более полного представления атрибутов элемента. Вы не ограничены встроенными метаданными (уполномоченный, веха, метки и т. д.), которые в настоящее время существуют для проблем и запросов на вытягивание. Например, можно добавить следующие метаданные в качестве настраиваемых полей:
|
||||
Настраиваемые поля можно использовать для добавления метаданных к проблемам, запросам на вытягивание и черновикам проблем, а также для создания более полного представления атрибутов элементов. Вы не ограничены встроенными метаданными (уполномоченный, веха, метки и т. д.), которые в настоящее время существуют для проблем и запросов на вытягивание. Например, можно добавить следующие метаданные в качестве настраиваемых полей:
|
||||
|
||||
- Поле даты для отслеживания целевых дат публикации.
|
||||
- Числовое поле для отслеживания сложности задачи.
|
||||
@@ -43,7 +43,7 @@ ms.locfileid: '148158864'
|
||||
|
||||
Списки задач можно использовать для создания иерархий проблем, разделения проблем на более мелкие подзадачи и создания новых связей между проблемами. Дополнительные сведения см. в разделе [Сведения о списках задач](/issues/tracking-your-work-with-issues/about-tasklists).
|
||||
|
||||
Эти связи отображаются в проблеме, а также в полях Отслеживаемые и Отслеживаемые в проектах. Вы можете отфильтровать проблемы, которые отслеживаются по другой проблеме, а также сгруппировать представления таблиц по полю Отслеживаемые, чтобы отобразить все родительские проблемы со списком их подзадач.
|
||||
Эти связи отображаются в проблеме, а также в полях Отслеживается по и Отслеживается в ваших проектах. Вы можете отфильтровать проблемы, которые отслеживаются по другой проблеме, а также сгруппировать представления таблиц по полю Отслеживаются, чтобы отобразить все родительские проблемы со списком их подзадач.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Сведения о полях Track и Tracked-by
|
||||
shortTitle: About Tracks and Tracked-by fields
|
||||
title: Сведения о дорожках и отслеживаемых по полям
|
||||
shortTitle: About Tracks and Tracked by fields
|
||||
intro: Вы можете просмотреть подзадачи проблем в проектах.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -8,30 +8,30 @@ versions:
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
ms.openlocfilehash: 74cd26d20882a00ac8c7ac1d109cc6810286cec6
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 44c1fcf3ed4495b57a0f2dbe3e92076f0e815502
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160037'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180748'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
Вы можете включить поля Track и Tracked-by в проектах, чтобы увидеть связи между проблемами при добавлении подзадач в списки задач. Дополнительные сведения о создании иерархий проблем в списках задач см. в разделе [Сведения о списках задач](/issues/tracking-your-work-with-issues/about-tasklists).
|
||||
Вы можете включить поля Track и Tracked by в проектах, чтобы увидеть связи между проблемами при добавлении подзадач в списках задач. Дополнительные сведения о создании иерархий проблем в списках задач см. в разделе [Сведения о списках задач](/issues/tracking-your-work-with-issues/about-tasklists).
|
||||
|
||||
Поле Отслеживаемое можно использовать для группировки элементов, создавая представление, в которое четко отображаются подзадачи каждой проблемы и работа, необходимая для их завершения. Дополнительные сведения см. в разделе [Группирование по значениям полей в макете таблицы](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#grouping-by-field-values-in-table-layout).
|
||||
Поле Отслеживается по можно использовать для группировки элементов, создавая представление, в которое четко отображаются подзадачи каждой проблемы и работа, необходимая для их завершения. Дополнительные сведения см. в разделе [Группирование по значениям полей в макете таблицы](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#grouping-by-field-values-in-table-layout).
|
||||
|
||||
Можно также выполнить фильтрацию по полю Отслеживаемое, чтобы отобразить только элементы, которые отслеживаются определенными проблемами. Начните вводить "отслеживается" и выберите проблему из списка или, если вы знаете репозиторий и номер проблемы, вы можете ввести фильтр ниже в полном объеме.
|
||||
Вы также можете отфильтровать по полю Отслеживаемые, чтобы отобразить только элементы, которые отслеживаются определенными проблемами. Либо начните вводить "tracked-by" и выберите проблему из списка, либо, если вы знаете репозиторий и номер проблемы, вы можете ввести фильтр ниже в полном объеме.
|
||||
|
||||
```
|
||||
tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
```
|
||||
|
||||
Чтобы использовать фильтр, замените `<OWNER>` на владельца репозитория, `<REPO>` на имя репозитория и `<ISSUE NUMBER>` на номер проблемы. Дополнительные сведения см. в статье [Фильтрация проектов](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
|
||||
Чтобы использовать фильтр, замените `<OWNER>` владельцем репозитория, `<REPO>` именем репозитория и `<ISSUE NUMBER>` номером проблемы. Дополнительные сведения см. в статье [Фильтрация проектов](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
|
||||
|
||||
### Включение поля отслеживаемого
|
||||
### Включение поля Отслеживается по
|
||||
|
||||
Вы можете включить поле Отслеживаемое, чтобы узнать, какие проблемы отслеживают элемент в проекте.
|
||||
Вы можете включить поле Отслеживаемое по, чтобы узнать, какие проблемы отслеживают элемент в проекте.
|
||||
|
||||
1. В представлении таблицы в самом правом заголовке поля щелкните {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
@@ -39,18 +39,18 @@ tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
|
||||
|
||||
1. В разделе "Скрытые поля" нажмите кнопку **Отслеживать**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Включение поля "Дорожки"
|
||||
|
||||
Вы можете включить поле Треки, чтобы узнать, какие другие проблемы отслеживает элемент в проекте.
|
||||
Вы можете включить поле "Дорожки", чтобы узнать, какие другие проблемы отслеживает элемент в проекте.
|
||||
|
||||
1. В представлении таблицы в самом правом заголовке поля щелкните {% octicon "plus" aria-label="the plus icon" %}.
|
||||
|
||||
|
||||
|
||||
1. В разделе "Скрытые поля" щелкните **Треки**.
|
||||
1. В разделе "Скрытые поля" щелкните **Дорожки**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -6,12 +6,12 @@ versions:
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /early-access/issues/about-tasklists
|
||||
ms.openlocfilehash: e35065ae4de634bb7a2da815e0a860c7c0b92234
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 69cdde1bb071f963b1a2f58ef1227bc96ab9d869
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148160129'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180788'
|
||||
---
|
||||
{% data reusables.projects.tasklists-release-stage %}
|
||||
|
||||
@@ -21,27 +21,17 @@ ms.locfileid: '148160129'
|
||||
|
||||
Списки задач создаются на основе предыдущей итерации [списков задач бета-версии](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists), сохраняя возможность преобразовывать элементы в проблемы, отображать ход выполнения списка задач и создавать связь "отслеживается" между проблемами.
|
||||
|
||||
Проблемы, добавленные в списки задач, будут автоматически заполнены для отображения их назначенных пользователей и всех примененных меток.
|
||||
Проблемы, которые вы добавляете в списки задач, будут автоматически заполнены для отображения их назначенных и примененных меток.
|
||||
|
||||
|
||||
|
||||
|
||||
### Сведения об интеграции с {% data variables.projects.projects_v2 %}
|
||||
|
||||
На боковой панели проекта отображается место проблемы в иерархии в меню навигации, что позволяет перемещаться по проблемам, включенным в списки задач. Вы также можете добавить поля Track и Tracked-by в представления проекта, чтобы быстро увидеть связи между проблемами. Дополнительные сведения см. в разделе [Сведения о дорожках и отслеживаемых полях](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
На боковой панели проекта отображается место проблемы в иерархии в меню навигации, что позволяет просматривать проблемы, включенные в списки задач. Вы также можете добавить поля Track (Отслеживаемые) и Tracked by (Отслеживаемые по) в представления проекта, чтобы быстро увидеть связи между проблемами. Дополнительные сведения см. в разделе [Сведения о дорожках и отслеживаемых по полям](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields).
|
||||
|
||||
## Создание списков задач
|
||||
|
||||
Чтобы создать список задач, можно использовать кнопку "Добавить список задач" или отредактировать проблему Markdown.
|
||||
|
||||
### Создание списка задач с помощью кнопки "Добавить список задач"
|
||||
|
||||
Нажмите кнопку **{% octicon "checklist" aria-label="The checklist icon" %} Добавить список задач** в нижней части описания проблемы, которую можно изменить, чтобы создать список задач.
|
||||
|
||||
|
||||
|
||||
### Создание списка задач с помощью Markdown
|
||||
|
||||
Вы можете использовать Markdown в описании проблемы для создания списка задач. Создайте блок кода с ограждением и включите `[tasklist]` рядом с начальными обратными словами. Предваряет каждый элемент `- [ ]` и включает ссылки на другие проблемы или текст. При необходимости можно добавить заголовок Markdown в верхней части списка.
|
||||
Список задач можно создать с помощью Markdown в описании проблемы. Создайте блок кода с ограждением и включите `[tasklist]` рядом с начальными обратными тиками. Затем вы можете перед каждым элементом `- [ ]` добавить ссылки на другие проблемы или текст. При необходимости можно добавить заголовок в качестве заголовка Markdown в верхней части списка.
|
||||
|
||||
````
|
||||
```[tasklist]
|
||||
@@ -50,10 +40,11 @@ ms.locfileid: '148160129'
|
||||
- [ ] Draft issue title
|
||||
```
|
||||
````
|
||||
Ваш Markdown будет отображаться {% data variables.product.product_name %} в виде списка задач. Затем можно внести изменения и добавить проблемы и черновики проблем с помощью пользовательского интерфейса. Если вы измените описание проблемы, вы сможете изменить Markdown напрямую или скопировать Markdown, чтобы дублировать список задач в других проблемах.
|
||||
|
||||
Ваш Markdown будет отображаться {% data variables.product.product_name %} в виде списка задач. Затем можно внести изменения и добавить проблемы и черновик проблем с помощью пользовательского интерфейса. Если вы измените описание проблемы, вы сможете изменить Markdown напрямую или скопировать Markdown, чтобы дублировать список задач в других проблемах.
|
||||
|
||||
Вы также можете щелкнуть {% octicon "checklist" aria-label="The checklist icon" %} на панели инструментов форматирования, чтобы вставить список задач при создании новой проблемы или изменении описания проблемы.
|
||||
|
||||
|
||||
|
||||
## Добавление проблем в список задач
|
||||
|
||||
@@ -61,24 +52,24 @@ ms.locfileid: '148160129'
|
||||
|
||||
|
||||
|
||||
1. Выберите проблему, чтобы добавить ее в список задач.
|
||||
1. Выберите проблему для добавления в список задач.
|
||||
|
||||
* Чтобы добавить недавно обновленную проблему из репозитория, щелкните ее в раскрывающемся списке или выберите ее с помощью клавиш со стрелками и нажмите клавишу <kbd>ВВОД</kbd>.
|
||||
|
||||
|
||||
|
||||
* Чтобы найти проблему в репозитории, начните вводить название проблемы или номер проблемы и щелкните результат или выберите ее с помощью клавиш со стрелками и нажмите клавишу <kbd>ВВОД</kbd>.
|
||||
* Чтобы найти проблему в репозитории, начните вводить название проблемы или номер проблемы и щелкните результат или используйте клавиши со стрелками, чтобы выбрать ее и нажать клавишу <kbd>ВВОД</kbd>.
|
||||
|
||||
|
||||
|
||||
* Чтобы добавить проблему напрямую, используя ее URL-адрес, вставьте URL-адрес проблемы и нажмите клавишу <kbd>ВВОД</kbd>.
|
||||
* Чтобы добавить проблему непосредственно с помощью ЕЕ URL-адреса, вставьте URL-адрес проблемы и нажмите клавишу <kbd>ВВОД</kbd>.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Создание черновиков проблем в списке задач
|
||||
|
||||
Черновики вопросов полезны для быстрого захвата идей, которые впоследствии можно преобразовать в проблемы. В отличие от проблем и запросов на вытягивание, на которые ссылается репозиторий, черновые проблемы существуют только в списке задач.
|
||||
Черновики вопросов полезны для быстрого захвата идей, которые позже можно преобразовать в проблемы. В отличие от проблем и запросов на вытягивание, на которые ссылаются ваши репозитории, черновики проблем существуют только в списке задач.
|
||||
|
||||
1. В нижней части списка задач щелкните **Добавить элемент в задачи**.
|
||||
|
||||
@@ -86,12 +77,12 @@ ms.locfileid: '148160129'
|
||||
|
||||
1. Введите название черновика проблемы и нажмите клавишу <kbd>ВВОД</kbd>.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Преобразование черновиков проблем в проблемы в списке задач
|
||||
|
||||
Вы можете преобразовать черновик проблем в проблемы. Проблемы создаются в том же репозитории, что и родительская проблема списка задач.
|
||||
Черновики вопросов можно преобразовать в проблемы. Проблемы создаются в том же репозитории, что и родительская проблема списка задач.
|
||||
|
||||
1. Рядом с черновиком проблемы, которую вы хотите преобразовать, щелкните {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
||||
|
||||
@@ -134,13 +125,13 @@ ms.locfileid: '148160129'
|
||||
|
||||
## Копирование списка задач
|
||||
|
||||
При копировании списка задач с помощью параметра "Копировать Markdown" {% data variables.product.product_name %} копирует Markdown в буфер обмена и включает имя проблемы, чтобы вы могли вставлять список задач за пределы GitHub без потери контекста.
|
||||
При копировании списка задач с помощью параметра "Копировать Markdown" {% data variables.product.product_name %} копирует Markdown в буфер обмена и включает имя проблемы, чтобы можно было вставить список задач за пределами GitHub без потери контекста.
|
||||
|
||||
1. В правом верхнем углу списка задач щелкните {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
||||
|
||||
|
||||
|
||||
1. В меню выберите **Копировать markdown**.
|
||||
1. В меню выберите команду **Копировать Markdown**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 17226308ffb5d7144dfe62d79f1f6cd3a1f63819
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180856"
|
||||
---
|
||||
1. Получите доступ к {% data variables.product.prodname_vscode_command_palette_shortname %} с<kbd>помощью команды</kbd>+ <kbd>SHIFT</kbd>+<kbd>P</kbd> (Mac) или <kbd>CTRL</kbd>+<kbd>SHIFT</kbd>+<kbd>P</kbd> (Windows или Linux).
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 0083a6bd4cd85d02754b449ecccdfa22f52cc358
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180859"
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**Совет:** Иногда может потребоваться выполнить полную перестройку, чтобы очистить кэш и перестроить контейнер со свежими образами. Дополнительные сведения см. в разделе [Выполнение полного перестроения контейнера](/codespaces/codespaces-reference/performing-a-full-rebuild-of-a-container).
|
||||
|
||||
{% endtip %}
|
||||
@@ -1,5 +1,13 @@
|
||||
1. Access the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
||||
---
|
||||
ms.openlocfilehash: 9a1e503111789036b99e1f31b9078bb28e4d57f8
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180848"
|
||||
---
|
||||
1. Откройте {% data variables.product.prodname_vscode_command_palette_shortname %}, нажав сочетание клавиш <kbd>SHIFT</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) или <kbd>CTRL</kbd>+<kbd>SHIFT</kbd>+<kbd>P</kbd> (Windows/Linux), а затем начните вводить строку "перестроить". Выберите **Codespaces: перестроить контейнер**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% indented_data_reference reusables.codespaces.full-rebuild-tip %}
|
||||
|
||||
@@ -1,6 +1,2 @@
|
||||
1. Under your organization name, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
ms.openlocfilehash: 989d63ee95229407cd3c3b05f5cfb41bd9038aee
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 23da81a1051f71cceb256e281271dc5eff03d7b2
|
||||
ms.sourcegitcommit: f5ec7f52d2945ba8b7c14f8f604e4784a8feda19
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: "148159962"
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: "148180756"
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Примечание:** Списки задач, дорожки и поля отслеживания для проектов в настоящее время находятся в закрытой бета-версии и могут быть изменены. Если вы хотите попробовать списки задач и использовать новые поля, вы можете присоединиться к [списку ожидания](https://aka.ms/tasklist-roadmap-signup).
|
||||
**Примечание:** Списки задач и отслеживаемые поля для проектов в настоящее время находятся в закрытой бета-версии и могут быть изменены. Если вы хотите попробовать списки задач и использовать новые поля, вы можете присоединиться к [списку ожидания](https://aka.ms/tasklist-roadmap-signup).
|
||||
|
||||
{% endnote %}
|
||||
@@ -0,0 +1,70 @@
|
||||
---
|
||||
title: Privately reporting a security vulnerability
|
||||
intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Privately reporting
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
|
||||
Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
|
||||
|
||||
Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
|
||||
|
||||
For security researchers, the benefits of using private vulnerability reporting are:
|
||||
- Less frustration, and less time spent trying to figure out how to contact the maintainer.
|
||||
- A smoother process for disclosing and discussing vulnerability details.
|
||||
- The opportunity to discuss vulnerability details privately with repository maintainer.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Privately reporting a security vulnerability
|
||||
|
||||
Security researchers can privately report a security vulnerability to repository maintainers.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click **Report a vulnerability** to open the advisory form.
|
||||
|
||||
|
||||
|
||||
2. Fill in the advisory details form.
|
||||
{% tip %}
|
||||
|
||||
**Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
|
||||
|
||||
1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
|
||||
|
||||
|
||||
|
||||
The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
|
||||
@@ -12,11 +12,11 @@ children:
|
||||
- /security-in-github-codespaces
|
||||
- /performing-a-full-rebuild-of-a-container
|
||||
- /disaster-recovery-for-github-codespaces
|
||||
ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: 223d3b146d829f129de39b43b51b6ab9e8aef411
|
||||
ms.sourcegitcommit: 3ff64a8c8cf70e868c10105aa6bbf6cd4f78e4d3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159195'
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180801'
|
||||
---
|
||||
|
||||
|
||||
@@ -1,27 +1,32 @@
|
||||
---
|
||||
title: Syntax for GitHub's form schema
|
||||
intro: 'You can use {% data variables.product.company_short %}''s form schema to configure forms for supported features.'
|
||||
title: GitHub 表单架构的语法
|
||||
intro: '您可以使用 {% data variables.product.company_short %} 的表单架构来配置支持的功能。'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
topics:
|
||||
- Community
|
||||
ms.openlocfilehash: 3a8a21f04582b87741ef80755e92fbc859921bb5
|
||||
ms.sourcegitcommit: 06d16bf9a5c7f3e7107f4dcd4d06edae5971638b
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179667'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change.
|
||||
注意：{% data variables.product.company_short %} 的表单架构目前为 beta 版本，可能会有变动。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About {% data variables.product.company_short %}'s form schema
|
||||
## 关于 {% data variables.product.company_short %} 的表单架构
|
||||
|
||||
You can use {% data variables.product.company_short %}'s form schema to configure forms for supported features. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)."
|
||||
您可以使用 {% data variables.product.company_short %} 的表单架构来配置支持的功能。 有关详细信息，请参阅“[为存储库配置问题模板](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)”。
|
||||
|
||||
A form is a set of elements for requesting user input. You can configure a form by creating a YAML form definition, which is an array of form elements. Each form element is a set of key-value pairs that determine the type of the element, the properties of the element, and the constraints you want to apply to the element. For some keys, the value is another set of key-value pairs.
|
||||
表单是请求用户输入的一组元素。 您可以通过创建 YAML 表单定义（这是一个表单元素阵列）来配置表单。 每个表单元素是一组确定元素类型、元素属性以及要应用于元素的约束的键值对。 对于某些键，值是另一组键值对。
|
||||
|
||||
For example, the following form definition includes four form elements: a text area for providing the user's operating system, a dropdown menu for choosing the software version the user is running, a checkbox to acknowledge the Code of Conduct, and Markdown that thanks the user for completing the form.
|
||||
例如，以下表单定义包括四种表单元素：用于提供用户操作系统的文本区域、用于选择用户运行的软件版本的下拉菜单、用于确认行为准则的复选框以及感谢用户完成表单的 Markdown。
|
||||
|
||||
```yaml{:copy}
|
||||
- type: textarea
|
||||
@@ -55,48 +60,48 @@ For example, the following form definition includes four form elements: a text a
|
||||
value: "Thanks for completing our form!"
|
||||
```
|
||||
|
||||
## Keys
|
||||
## 密钥
|
||||
|
||||
For each form element, you can set the following keys.
|
||||
对于每个表单元素，您可以设置以下键。
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `type` | The type of element that you want to define. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | <ul><li>`checkboxes`</li><li>`dropdown`</li><li>`input`</li><li>`markdown`</li><li>`textarea`</li></ul> |
|
||||
| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} If provided, the `id` is the canonical identifier for the field in URL query parameter prefills. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `attributes` | A set of key-value pairs that define the properties of the element. | Required | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `validations` | A set of key-value pairs that set constraints on the element. | Optional | Map | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `type` | 您想要定义的元素类型。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | <ul><li>`checkboxes`</li><li>`dropdown`</li><li>`input`</li><li>`markdown`</li><li>`textarea`</li></ul> |
|
||||
| `id` | 元素的标识符，除非 `type` 设置为 `markdown`。 {% data reusables.form-schema.id-must-be-unique %} 如果提供，`id` 是 URL 查询参数预填中字段的规范标识符。 | 可选 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `attributes` | 定义元素属性的一组键值对。 | 必需 | 映射 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `validations` | 设置元素约束的一组键值对。 | 可选 | 映射 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
|
||||
You can choose from the following types of form elements. Each type has unique attributes and validations.
|
||||
您可以从以下类型的表单元素中选择。 每个类型都有唯一的属性和验证。
|
||||
|
||||
| Type | Description |
|
||||
| 类型 | 说明 |
|
||||
| ---- | ----------- |
|
||||
| [`markdown`](#markdown) | Markdown text that is displayed in the form to provide extra context to the user, but is **not submitted**. |
|
||||
| [`textarea`](#textarea) | A multi-line text field. |
|
||||
| [`input`](#input) | A single-line text field. |
|
||||
| [`dropdown`](#dropdown) | A dropdown menu. |
|
||||
| [`checkboxes`](#checkboxes) | A set of checkboxes. |
|
||||
| [`markdown`](#markdown) | Markdown 文本显示在表单中，为用户提供额外的上下文，但并未提交。 |
|
||||
| [`textarea`](#textarea) | 多行文本字段。 |
|
||||
| [`input`](#input) | 单行文本字段。 |
|
||||
| [`dropdown`](#dropdown) | 下拉菜单。 |
|
||||
| [`checkboxes`](#checkboxes) | 一组复选框。 |
|
||||
|
||||
### `markdown`
|
||||
|
||||
You can use a `markdown` element to display Markdown in your form that provides extra context to the user, but is not submitted.
|
||||
可以使用 `markdown` 元素在表单中显示 Markdown，为用户提供额外的上下文，但不提交。
|
||||
|
||||
#### Attributes
|
||||
#### 属性
|
||||
|
||||
{% data reusables.form-schema.attributes-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `value` | The text that is rendered. Markdown formatting is supported. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `value` | 渲染的文本。 支持 Markdown 格式。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes.
|
||||
提示：YAML 处理将哈希符号视为评论。 要插入 Markdown 标题，请用引号括住文本。
|
||||
|
||||
For multi-line text, you can use the pipe operator.
|
||||
对于多行文本，您可以使用竖线运算符。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
#### Example
|
||||
#### 示例
|
||||
|
||||
```YAML{:copy}
|
||||
body:
|
||||
@@ -111,29 +116,29 @@ body:
|
||||
|
||||
### `textarea`
|
||||
|
||||
You can use a `textarea` element to add a multi-line text field to your form. Contributors can also attach files in `textarea` fields.
|
||||
可以使用 `textarea` 元素向表单添加多行文本字段。 参与者还可以在 `textarea` 字段中附加文件。
|
||||
|
||||
#### Attributes
|
||||
#### 属性
|
||||
|
||||
{% data reusables.form-schema.attributes-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | A description of the text area to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `placeholder` | A semi-opaque placeholder that renders in the text area when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `value` | Text that is pre-filled in the text area. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `render` | If a value is provided, submitted text will be formatted into a codeblock. When this key is provided, the text area will not expand for file attachments or Markdown editing. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Languages known to {% data variables.product.prodname_dotcom %}. For more information, see [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). |
|
||||
| `label` | 预期用户输入的简短描述，也以表单形式显示。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | 提供上下文或指导的文本区域的描述，以表单形式显示。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `placeholder` | 半透明的占位符，在文本区域空白时呈现。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `value` | 在文本区域中预填充的文本。 | 可选 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `render` | 如果提供了值，提交的文本将格式化为代码块。 提供此键时，文本区域将不会扩展到文件附件或 Markdown 编辑。 | 可选 | String | {% octicon "dash" aria-label="The dash icon" %} | {% data variables.product.prodname_dotcom %} 已知的语言。 有关详细信息，请参阅[语言 YAML 文件](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)。 |
|
||||
|
||||
#### Validations
|
||||
#### 验证
|
||||
|
||||
{% data reusables.form-schema.validations-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
{% data reusables.form-schema.required-key %}
|
||||
|
||||
#### Example
|
||||
#### 示例
|
||||
|
||||
```YAML{:copy}
|
||||
body:
|
||||
@@ -154,28 +159,28 @@ body:
|
||||
|
||||
### `input`
|
||||
|
||||
You can use an `input` element to add a single-line text field to your form.
|
||||
可以使用 `input` 元素向表单添加单行文本字段。
|
||||
|
||||
#### Attributes
|
||||
#### 属性
|
||||
|
||||
{% data reusables.form-schema.attributes-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | A description of the field to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `placeholder` | A semi-transparent placeholder that renders in the field when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `value` | Text that is pre-filled in the field. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `label` | 预期用户输入的简短描述，也以表单形式显示。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | 提供上下文或指导的字段的描述，以表单形式显示。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `placeholder` | 半透明的占位符，在字段空白时呈现。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `value` | 字段中预填的文本。 | 可选 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
|
||||
#### Validations
|
||||
#### 验证
|
||||
|
||||
{% data reusables.form-schema.validations-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
{% data reusables.form-schema.required-key %}
|
||||
|
||||
#### Example
|
||||
#### 示例
|
||||
|
||||
```YAML{:copy}
|
||||
body:
|
||||
@@ -191,28 +196,28 @@ body:
|
||||
|
||||
### `dropdown`
|
||||
|
||||
You can use a `dropdown` element to add a dropdown menu in your form.
|
||||
可以使用 `dropdown` 元素在表单中添加下拉菜单。
|
||||
|
||||
#### Attributes
|
||||
#### 属性
|
||||
|
||||
{% data reusables.form-schema.attributes-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | A description of the dropdown to provide extra context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `multiple` | Determines if the user can select more than one option. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `options` | An array of options the user can choose from. Cannot be empty and all choices must be distinct. | Required | String array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `label` | 预期用户输入的简短描述，以表单形式显示。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | 提供上下文或指导的下拉列表的描述，以表单形式显示。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `multiple` | 确定用户是否可以选择多个选项。 | 可选 | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `options` | 用户可以选择的选项阵列。 不能为空，所有选择必须是不同的。 | 必需 | 字符串数组 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
|
||||
#### Validations
|
||||
#### 验证
|
||||
|
||||
{% data reusables.form-schema.validations-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
{% data reusables.form-schema.required-key %}
|
||||
|
||||
#### Example
|
||||
#### 示例
|
||||
|
||||
```YAML{:copy}
|
||||
body:
|
||||
@@ -231,29 +236,29 @@ body:
|
||||
|
||||
### `checkboxes`
|
||||
|
||||
You can use the `checkboxes` element to add a set of checkboxes to your form.
|
||||
可以使用 `checkboxes` 元素向表单添加一组复选框。
|
||||
|
||||
#### Attributes
|
||||
#### 属性
|
||||
|
||||
{% data reusables.form-schema.attributes-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | A description of the set of checkboxes, which is displayed in the form. Supports Markdown formatting. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `options` | An array of checkboxes that the user can select. For syntax, see below. | Required | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `label` | 预期用户输入的简短描述，以表单形式显示。 | 必须 | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `description` | 复选框集的描述，以表单形式显示。 支持 Markdown 格式。 | 可选 | String | 空字符串 | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
| `options` | 用户可以选择的复选框阵列。 有关语法，请参阅下文。 | 必需 | 数组 | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
|
||||
|
||||
{% data reusables.form-schema.options-syntax %}
|
||||
|
||||
#### Validations
|
||||
#### 验证
|
||||
|
||||
{% data reusables.form-schema.validations-intro %}
|
||||
|
||||
| Key | Description | Required | Type | Default | Valid values |
|
||||
| 密钥 | 说明 | 必选 | 类型 | 默认 | 有效值 |
|
||||
| --- | ----------- | -------- | ---- | ------- | ------- |
|
||||
{% data reusables.form-schema.required-key %}
|
||||
|
||||
#### Example
|
||||
#### 示例
|
||||
|
||||
```YAML{:copy}
|
||||
body:
|
||||
@@ -268,6 +273,6 @@ body:
|
||||
- label: Linux
|
||||
```
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- [YAML](https://yaml.org)
|
||||
|
||||
@@ -1,43 +1,49 @@
|
||||
---
|
||||
title: Splitting a subfolder out into a new repository
|
||||
title: 将子文件夹拆分成新仓库
|
||||
redirect_from:
|
||||
- /articles/splitting-a-subpath-out-into-a-new-repository
|
||||
- /articles/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/using-git/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
|
||||
intro: You can turn a folder within a Git repository into a brand new repository.
|
||||
intro: 您可以将 Git 仓库内的文件夹变为全新的仓库。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Splitting a subfolder
|
||||
ms.openlocfilehash: e99c1c1411b335837b478b32f085596ec4f5fc0f
|
||||
ms.sourcegitcommit: 46eac8c63f52669996a9c832f2abf04864dc89ba
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/18/2022
|
||||
ms.locfileid: '148172907'
|
||||
---
|
||||
If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
|
||||
如果您创建仓库的新克隆副本，则将文件夹拆分为单独的仓库时不会丢失任何 Git 历史记录或更改。
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
|
||||
2. Change the current working directory to the location where you want to create your new repository.
|
||||
2. 将当前工作目录更改为您要创建新仓库的位置。
|
||||
|
||||
4. Clone the repository that contains the subfolder.
|
||||
4. 克隆包含该子文件夹的仓库。
|
||||
```shell
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME
|
||||
```
|
||||
|
||||
4. Change the current working directory to your cloned repository.
|
||||
4. 将当前工作目录更改为您克隆的仓库。
|
||||
```shell
|
||||
$ cd REPOSITORY-NAME
|
||||
```
|
||||
|
||||
5. To filter out the subfolder from the rest of the files in the repository, install [`git-filter-repo`](https://github.com/newren/git-filter-repo), then run `git filter-repo` with the following arguments.
|
||||
- `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
|
||||
5. 若要从存储库中的其余文件中筛选出子文件夹，请安装 [`git-filter-repo`](https://github.com/newren/git-filter-repo)，然后使用以下参数运行 `git filter-repo`。
|
||||
- `FOLDER-NAME`：项目中要在其中创建单独存储库的文件夹。
|
||||
|
||||
{% windows %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Windows users should use `/` to delimit folders.
|
||||
提示：Windows 用户应使用 `/` 来分隔文件夹。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -50,33 +56,33 @@ If you create a new clone of the repository, you won't lose any of your Git hist
|
||||
> Ref 'refs/heads/BRANCH-NAME' was rewritten
|
||||
```
|
||||
|
||||
The repository should now only contain the files that were in your subfolder(s).
|
||||
现在，该仓库应仅包含您的子文件夹中的文件。
|
||||
|
||||
6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
|
||||
6. 在 {% data variables.product.product_name %} 上[新建存储库](/articles/creating-a-new-repository/)。
|
||||
|
||||
7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
|
||||
|
||||
|
||||
7. 在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} 的快速设置页面上的新存储库顶部，单击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程存储库 URL。
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
提示：有关 HTTPS 和 SSH URL 之间区别的信息，请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
|
||||
8. 检查仓库现有的远程名称。 例如，`origin` 或 `upstream` 是两个常见的选项。
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push)
|
||||
```
|
||||
|
||||
9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
|
||||
9. 使用现有的远程名称和您在步骤 7 中复制的远程仓库 URL 为新仓库设置新的远程 URL。
|
||||
```shell
|
||||
git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git
|
||||
```
|
||||
|
||||
10. Verify that the remote URL has changed with your new repository name.
|
||||
10. 使用新仓库名称验证远程 URL 是否已更改。
|
||||
```shell
|
||||
$ git remote -v
|
||||
# Verify new remote URL
|
||||
@@ -84,7 +90,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
|
||||
> origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push)
|
||||
```
|
||||
|
||||
11. Push your changes to the new repository on {% data variables.product.product_name %}.
|
||||
11. 将您的更改推送到 {% data variables.product.product_name %} 上的新仓库。
|
||||
```shell
|
||||
git push -u origin BRANCH-NAME
|
||||
```
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: '从 {% data variables.product.prodname_projects_v1 %} 中迁移'
|
||||
intro: '可以将 {% data variables.projects.projects_v1_board %} 迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验。'
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,53 +10,57 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108703'
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**注意：**
|
||||
|
||||
- 如果你要迁移的项目包含超过 1200 个项，则未结的问题将优先，接着是未解决的拉取请求，然后是注释。 剩余的空间将用于已解决的问题、已合并的请求拉取和已解决的拉取请求。 由于此限制而无法迁移的项将被移动到存档。 如果达到 10,000 个项的存档限制，则不会迁移其他项。
|
||||
- 注释卡被转换为草稿问题，内容被保存到草稿问题的正文中。 如果信息出现缺失，请使任何隐藏的字段可见。 有关详细信息，请参阅“[显示和隐藏字段](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)”。
|
||||
- 不会迁移自动化。
|
||||
- 不会迁移会审、存档和活动。
|
||||
- 迁移后，新迁移的项目和旧项目不会保持同步。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 关于项目迁移
|
||||
|
||||
可以将项目板迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验，并试用表格、多个视图、新的自动化选项和强大的字段类型。 有关详细信息，请参阅“[关于项目](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”。
|
||||
|
||||
## 迁移组织项目板
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. 在左侧，单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## 迁移用户项目板
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
|
||||
|
||||
1. 在项目列表上方，单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## 迁移存储库项目板
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：{% data variables.projects.projects_v2_caps %} 不支持存储库级别的项目。 当你迁移存储库项目板时，它将迁移到拥有存储库项目的组织或个人帐户，并且迁移的项目将被固定到原始存储库。
|
||||
**Notes:**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. 在存储库名称下，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
|
||||
|
||||
1. 单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
## About project migration
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
## Migrating an organization project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 查看文件
|
||||
intro: 可以查看原始文件内容或跟踪对文件中各行的更改，了解文件的各个部分如何随时间演变。
|
||||
title: Viewing a file
|
||||
intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
|
||||
redirect_from:
|
||||
- /articles/using-git-blame-to-trace-changes-in-a-file
|
||||
- /articles/tracing-changes-in-a-file
|
||||
@@ -16,54 +16,48 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: View files and track file changes
|
||||
ms.openlocfilehash: bc27fc67cfd18eb20f8c612b81f4d6dd5da20913
|
||||
ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '146680987'
|
||||
---
|
||||
## 查看或复制原始文件内容
|
||||
## Viewing or copying the raw file content
|
||||
|
||||
使用原始视图，可以查看或复制不带任何样式的文件原始内容。
|
||||
With the raw view, you can view or copy the raw content of a file without any styling.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. 单击要查看的文件。
|
||||
2. 在文件视图的右上角，单击“原始”。
|
||||
|
||||
3. （可选）若要复制原始文件内容，请在文件视图右上角单击“{% octicon "copy" aria-label="The copy icon" %}”。
|
||||
1. Click the file that you want to view.
|
||||
2. In the upper-right corner of the file view, click **Raw**.
|
||||
|
||||
3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
|
||||
|
||||
## 查看文件的逐行修订历史记录
|
||||
## Viewing the line-by-line revision history for a file
|
||||
|
||||
使用追溯视图时，可以查看整个文件的逐行修订历史记录，也可以单击 {% octicon "versions" aria-label="The prior blame icon" %} 查看文件中某一行的修订历史记录。 每次单击 {% octicon "versions" aria-label="The prior blame icon" %} 后，将看到该行以前的修订信息，包括提交更改的人员和时间。
|
||||
With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
|
||||
|
||||
|
||||
|
||||
|
||||
在文件或拉取请求中，还可以使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} 菜单查看所选行或行范围的 Git 追溯。
|
||||
In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
提示：在命令行上，还可以使用 `git blame` 查看文件内各行的修订历史记录。 有关详细信息，请参阅 [Git 的 `git blame` 文档](https://git-scm.com/docs/git-blame)。
|
||||
**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. 单击以打开您想要查看其行历史记录的文件。
|
||||
3. 在文件视图的右上角，单击“追溯”以打开追溯视图。
|
||||
|
||||
4. 若要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到你想查看的更改。
|
||||
|
||||
2. Click to open the file whose line history you want to view.
|
||||
3. In the upper-right corner of the file view, click **Blame** to open the blame view.
|
||||
|
||||
4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
|
||||
|
||||
|
||||
{% ifversion blame-ignore-revs %}
|
||||
|
||||
## 忽略追溯视图中的提交
|
||||
## Ignore commits in the blame view
|
||||
|
||||
`.git-blame-ignore-revs` 文件中指定的所有修订（必须位于存储库的根目录中）利用 Git 的 `git blame --ignore-revs-file` 配置设置从追溯视图中隐藏。 有关详细信息，请参阅 Git 文档中的 [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt)。
|
||||
All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
|
||||
|
||||
1. 在存储库的根目录中，创建一个名为 `.git-blame-ignore-revs` 的文件。
|
||||
2. 在该文件中添加要从追溯视图中排除的提交哈希。 建议按如下所示构建文件（包括评论）：
|
||||
1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
|
||||
2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
|
||||
|
||||
```ini
|
||||
# .git-blame-ignore-revs
|
||||
@@ -73,22 +67,26 @@ ms.locfileid: '146680987'
|
||||
69d029cec8337c616552756310748c4a507bd75a
|
||||
```
|
||||
|
||||
3. 提交并推送更改。
|
||||
3. Commit and push the changes.
|
||||
|
||||
现在，访问追溯视图时，追溯中将不会包含列出的修订。 你会看到“忽略 .git-blame-ignore-revs 中的修订”横幅，表明某些提交可能已隐藏：
|
||||
Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
|
||||
|
||||
|
||||
|
||||
|
||||
当一些提交对代码进行大量更改时，这非常有用。 也可以在本地运行 `git blame` 时使用该文件：
|
||||
This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
|
||||
|
||||
```shell
|
||||
git blame --ignore-revs-file .git-blame-ignore-revs
|
||||
```
|
||||
|
||||
还可以配置本地 git，使其始终忽略该文件中的修订：
|
||||
You can also configure your local git so it always ignores the revs in that file:
|
||||
|
||||
```shell
|
||||
git config blame.ignoreRevsFile .git-blame-ignore-revs
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Bypassing `.git-blame-ignore-revs` in the blame view
|
||||
|
||||
If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
|
||||
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: 1a9ef3b5c648f6cbc07e2c22dbb360163c28bd0d
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: "148179837"
|
||||
---
|
||||
1. 单击“更新作业”。
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: ea90a8f3dc173dba123032b4555f4d7df19d63bd
|
||||
ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/17/2022
|
||||
ms.locfileid: "148169563"
|
||||
---
|
||||
1. 在边栏的“安全性”部分中，单击“{% octicon "checklist" aria-label="The checklist icon" %} 合规性”。
|
||||
@@ -1,10 +1,2 @@
|
||||
---
|
||||
ms.openlocfilehash: 55a01fbe1358fc0fffc11f146b973d79242c5235
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: "148108659"
|
||||
---
|
||||
1. 在组织名称下，单击 {% octicon "project" aria-label="The Projects icon" %}“项目”。
|
||||
{% ifversion fpt or ghes or ghec %}{% else %}{% endif %}
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-label="The Projects icon" %}{% else %}{% octicon "project" aria-label="The Projects icon" %}{% endif %} **Projects**.
|
||||
{% ifversion projects-v2 %}{% else %}{% endif %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
ms.openlocfilehash: cd91a98e6cb0da73a24f7f6e682b67ec25b406d4
|
||||
ms.sourcegitcommit: 24427fe609677b2c58137b1d9d63869d0872daf4
|
||||
ms.openlocfilehash: 7843dd2811e3645b6c9ea979fd3cb54a14b151f0
|
||||
ms.sourcegitcommit: 8d6f272d8b5da44e3a29ad8d99013c10a5c91b35
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/04/2022
|
||||
ms.locfileid: "148134790"
|
||||
ms.lasthandoff: 11/17/2022
|
||||
ms.locfileid: "148172034"
|
||||
---
|
||||
Partner | 支持的密钥
|
||||
--- | ---
|
||||
@@ -23,6 +23,8 @@ Azure | Azure CosmosDB 可识别密钥
|
||||
Azure | Azure DevOps {% data variables.product.pat_generic_title_case %}
|
||||
Azure | Azure ML 工作室（经典）Web 服务密钥
|
||||
Azure | Azure SAS 令牌
|
||||
Azure | Azure 搜索管理密钥
|
||||
Azure | Azure 搜索查询密钥
|
||||
Azure | Azure 服务管理证书
|
||||
Azure | Azure SQL 连接字符串
|
||||
Azure | Azure 存储帐户密钥
|
||||
|
||||
Reference in New Issue
Block a user