diff --git a/translations/de-DE/content/codespaces/about-codespaces.md b/translations/de-DE/content/codespaces/about-codespaces.md deleted file mode 100644 index 68715f7153..0000000000 --- a/translations/de-DE/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Über Codespaces -intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Informationen zu {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -![Ein Open-Codespace](/assets/images/help/codespaces/codespace-overview.png) - -A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings. - -Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development. - -### A consistent environment - -You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials. - -While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -### Fast and personal onboarding - -With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**. - -![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature. - -Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - -Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs. - -### A secure environment - -{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Entwickler können von überall her einen Beitrag leisten, von jedem Rechner aus, einschließlich Tablets oder Chromebooks, und es besteht keine Notwendigkeit, lokale Kopien des geistigen Eigentums zu verwalten. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`. - -Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### Informationen zur Abrechnung für {% data variables.product.prodname_codespaces %} - -{% data reusables.codespaces.about-billing-for-codespaces %} Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)“. - -### Der Beta-Phase beitreten - -Eine begrenzte Anzahl von Personen wird eingeladen, der Beta-Phase beizutreten. To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### Kontaktiere uns zu {% data variables.product.prodname_codespaces %} - -Wenn Du bei der Verwendung von {% data variables.product.prodname_codespaces %} Probleme entdeckst, lies bitte „[Fehlerbehebung Deines Codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion. diff --git a/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index f621a80494..0000000000 --- a/translations/de-DE/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: About billing for Codespaces -intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -Updates on the billing model for Codespaces will be shared in an upcoming announcement. diff --git a/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index 75be9e6f73..0000000000 --- a/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Allowing your codespace to access a private image registry -intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry. - -When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)." - -For example, if you had a private image registry in Azure, you could create the following secrets: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/de-DE/content/codespaces/codespaces-reference/index.md b/translations/de-DE/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index f454770178..0000000000 --- a/translations/de-DE/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Referenz -intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index acea2d4a85..0000000000 --- a/translations/de-DE/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Fehlerbehebung Deines Codespace -intro: Use this guide to help you troubleshoot common issues with your codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Known Limitations - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### {% data variables.product.prodname_vscode %} troubleshooting - -Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience. - - -### Configuration troubleshooting - -{% data reusables.codespaces.recovery-mode %} - -``` -This codespace is currently running in recovery mode due to a container error. -``` - -Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -### dotfiles troubleshooting - -- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles. -- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned. - - If your dotfiles were cloned, try manually re-running your install script to verify it's executable. - - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**. - - -### Browser troubleshooting - -Wenn Du bei der Verwendung eines nicht Chromium-basierten Browsers auf Probleme stößt, versuche auf einen Chromium-basierenden Browser zu wechseln oder suche nach bekannten Issues für Deinen Browser im `microsoft/vscode`-Repository, indem Du nach Problemen suchst, die mit dem Namen Deines Browsers gekennzeichnet sind, wie etwa [`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 Du bei der Verwendung eines Chromium-basierten Browsers auf Probleme stößt, kannst Du im [`microsoft/vscode`](https://github.com/microsoft/vscode/issues)-Repository.prüfen, ob du ein anderes bekanntes Problem mit {% data variables.product.prodname_vscode %} erlebst. - -### Container storage troubleshooting - -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 any of the following items to free up storage space. - -- Remove packages that are no longer by using `sudo apt autoremove` -- Clean the apt cache by using `sudo apt clean` -- Delete unneeded files like build artifacts and logs (these are very project-dependent) -- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10` - -More destructive options: -- 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` - -### Kontakt - -Wenn Du immer noch Hilfe benötigst, kannst Du uns kontaktieren. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)." diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 75ed888220..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Erstellen eines Codespace -intro: 'Du kannst einen Codespace in einem Repository-Branch erstellen, um Online zu entwickeln.' -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Über die Codespace Erstellung - -You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)." - - -When you create a codespace, a number of steps happen to enable full access to your development environment. - -- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches. -- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created. -- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository. -- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." -- Your Docker container, `docker-compose`, or other initialization is run. -- At this point, the codespace is marked as available and you can connect. -- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up. - - The codespace shares ports added in the `devcontainer.json` file. - - The codespace runs anything specified in `postCreateCommand`. - - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - - Finally, the codespace does a full clone of the repo so you have full access to it. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Erstellen eines Codespace - -{% data reusables.repositories.navigate-to-repo %} -2. Benutze das „Branch"-Dropdownmenü unterhalb des Repository-Namens und wähle den Branch, für den Du einen Codespace erstellen willst. - - ![Dropdownmenü „Branch"](/assets/images/help/codespaces/branch-drop-down.png) - -3. Benutze das {% octicon "download" aria-label="The download icon" %} **Code**-Dropdownmenü unterhalb des Repository-Namens und wähle **Open with Codespaces** (Eröffnen mit Codespaces). - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index dd74d3eecc..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Einen Codespace löschen -intro: 'Du kannst einen Codespace löschen, wenn Du ihn nicht länger benötigst.' -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png) - - Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces). - -2. 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** ![Schaltfläche „Delete" (Löschen)](/assets/images/help/codespaces/delete-codespace.png) - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)." diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index 51fca79f66..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: In einem Codespace entwickeln -intro: 'Du kannst einen Codespace auf {% data variables.product.product_name %} eröffnen und dann mithilfe der {% data variables.product.prodname_vscode %}-Funktionen entwickeln.' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About development with {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Side Bar - By default, this area shows your project files in the Explorer. -2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them. -3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it. -4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. -5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. - -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} Weitere Informationen findest Du unter „[Fehlerbehebung Deines Codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -#### Personalizing your codespace - -{% data reusables.codespaces.about-personalization %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Konto personalisieren](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)." - -{% data reusables.codespaces.apply-devcontainer-changes %} Weitere Informationen findest du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -#### Running your app from a codespace -{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)." - -#### Committing your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Navigating to an existing codespace - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Klicke auf den Namen des Codespace, in dem Du entwickeln möchtest. ![Name des Codespace](/assets/images/help/codespaces/click-name-codespace.png) - -Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 63e2a73681..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Forwarding ports in your codespace -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About forwarded ports - -Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application. - -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000. - -![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) - -You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration. - -### Forwarding a port - -You can manually forward a port that wasn't forwarded automatically. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) - -### Labeling a port - -You can label a port to make the port more easily identifiable in a list. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Sharing a port - -If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) -1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Send the copied URL to the person you want to share the port with. - -### Adding a port to the codespace configuration - -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index 08438c8895..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: In einem Codespace entwickeln -intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index 406824a7cf..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Using Codespaces in Visual Studio Code -intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_github_codespaces %}-Erweiterung 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 - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Vorrausetzungen - -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. - -Du kannst {% data variables.product.prodname_vs %}-Marketplace verwenden, um die [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)-Erweiterung zu installieren. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation. - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Klicke auf **Sign in to view {% data variables.product.prodname_dotcom %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen). -4. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen. - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![Die {% data variables.product.prodname_codespaces %}-Kopfzeile](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). ![Anmelden, um {% data variables.product.prodname_codespaces %} anzuzeigen](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen). -5. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen. - -{% endwindows %} - -### Creating a codespace in {% data variables.product.prodname_vscode %} - -After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) -### Einen Codespace in {% data variables.product.prodname_vscode %} eröffnen - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Under "Codespaces", click the codespace you want to develop in. -3. Klicke auf das Symbol „Connect to Codespace" (Verbinde zu Codespace). ![Symbol „Connect to Codespace" (Verbinde mit Codespace) in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Changing the machine type in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -You can change the machine type of your codespace at any time. - -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). -2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -1. Under "Codespaces", right-click the codespace you want to delete. -2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index 11d7279d92..0000000000 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -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. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About source control in {% data variables.product.prodname_codespaces %} - -You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the 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. - -Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." - -A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: - -* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -* In your codespace, create a new branch to work on. -* Make your changes and save them. -* Commit the change. -* Raise a pull request. - -### Creating or switching branches - -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace. - -{% endtip %} - -### Pulling changes from the remote repository - -You can pull changes from the remote repository into your codespace at any time. - -{% data reusables.codespaces.source-control-display-dark %} -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. In the drop-down menu, click **Pull**. - -If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -### Setting your codespace to automatically fetch new changes - -You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes. - -If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy. - -1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png) -1. In the menu, slick **Settings**. -1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png) -1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png) -1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**. - -### Committing your changes - -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Raising a pull request - -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Klicke auf **Create** (Erstellen). - -### Pushing changes to your remote repository - -You can push the changes you've made. 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 %}. - -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. In the drop-down menu, click **Push**. diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index 0355417f9b..0000000000 --- a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Getting started with your C# (.NET) project in Codespaces -shortTitle: Getting started with your C# (.NET) project -allowTitleToDifferFromFilename: true -intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Einführung - -This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Vorrausetzungen - -- 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_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - -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. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 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. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - You can name our dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - - **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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed. - - ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application. - -1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Nächste Schritte: - -You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 55c1c30565..0000000000 --- a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Getting started with your Java project in Codespaces -shortTitle: Getting started with your Java project -intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Einführung - -This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Vorrausetzungen - -- You should have an existing Java 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/microsoft/vscode-remote-try-java -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - -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 Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm. - -1. Run your application by pressing `F5`. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Nächste Schritte: - -You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 1117c53786..0000000000 --- a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Getting started with your Node.js project in Codespaces -shortTitle: Getting started with your Node.js project -intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### Einführung - -This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Vorrausetzungen - -- You should have an existing JavaScript, Node.js, or TypeScript 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/microsoft/vscode-remote-try-node -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Node.js**. If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm. - -1. Run your start command in the terminal with`npm start`. - - ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Nächste Schritte: - -You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index d3ee56ad84..0000000000 --- a/translations/de-DE/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Getting started with your Python project in Codespaces -shortTitle: Getting started with your Python project -intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### Einführung - -This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Vorrausetzungen - -- You should have an existing Python 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/python-quickstart. -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // 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` is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **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-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), 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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed. - - ![Extensions list](/assets/images/help/codespaces/python-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application. - -1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Nächste Schritte: - -You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md b/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index 396851c0bb..0000000000 --- a/translations/de-DE/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Getting Started with {% data variables.product.prodname_codespaces %}' -intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/guides.md b/translations/de-DE/content/codespaces/guides.md deleted file mode 100644 index b719006750..0000000000 --- a/translations/de-DE/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Codespaces guides -shortTitle: Leitfäden -intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/de-DE/content/codespaces/index.md b/translations/de-DE/content/codespaces/index.md deleted file mode 100644 index d7c9926f2c..0000000000 --- a/translations/de-DE/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: GitHub Codespaces Documentation -beta_product: true -shortTitle: GitHub Codespaces -intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index 7d7055b862..0000000000 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Managing Codespaces for your organization -intro: 'You can manange and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index f3d0f9eb29..0000000000 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Managing access and security for your organization's codespaces -shortTitle: Managing access and security for your organization -intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Organization owners can manage which repositories a codespace can access. - -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. - -To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index 846a64b7e1..0000000000 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Managing encrypted secrets for your repository and organization for Codespaces -shortTitle: Managing secrets for your repository and organization -intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About secrets - -Secrets are encrypted environment variables that you create in an organization or repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace. - -Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. - - {% data reusables.codespaces.secret-precedence %} - -#### Einschränkungen für Geheimnisse - -You can store up to 100 secrets per organization and 100 secrets per repository. - -Geheimnisse sind auf 64 KB beschränkt. - -### Adding secrets for a repository - -To create secrets for an organization repository, you must have administrator access. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. At the top of the page, click **New repository secret**. -1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein. -1. Geben Sie den Wert für Ihr Geheimnis ein. -1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). - -### Adding secrets for an organization - -Beim Erstellen eines geheimen Schlüssels in einer Organisation können Sie eine Richtlinie verwenden, um einzuschränken, welche Repositorys auf diesen geheimen Schlüssel zugreifen können. Sie können z. B. Zugriff auf alle Repositorys gewähren oder den Zugriff auf nur private Repositorys oder eine angegebene Liste von Repositorys beschränken. - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. At the top of the page, click **New organization secret**. -1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein. -1. Geben Sie den **Value** für Ihr Geheimnis ein. -1. Wählen Sie im **Repository-Zugriff** Dropdownliste eine Zugriffsrichtlinie aus. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png) -1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). - -### Überprüfen des Zugriffs auf Geheimnisse auf Organisationsebene - -You can check which access policies are applied to a secret in your organization. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Die Liste der Geheimnisse enthält alle konfigurierten Berechtigungen und Richtlinien. Ein Beispiel: ![Geheimliste](/assets/images/help/settings/actions-org-secrets-list.png) -1. Weitere Informationen zu den konfigurierten Berechtigungen für jeden geheimen Schlüssel finden Sie unter **Aktualisieren**. diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index f8c2c9ac71..0000000000 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Managing user permissions for your organization -intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}. -permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### About user permissions for {% data variables.product.prodname_codespaces %} - -Organization owners can control which users in your organization can create and use codespaces. - -To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users. - -By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select one of the following options: - - * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}. - * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}. - * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}. - - ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index c438a70311..0000000000 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Reviewing your organization's audit logs for Codespaces -shortTitle: Reviewing your organization's audit logs -intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)." - -![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) - -The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/index.md b/translations/de-DE/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 142e6c292d..0000000000 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing your codespaces -intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 2241dd5ecf..0000000000 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing access and security for your codespaces -intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index 9e34c2e376..0000000000 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Managing encrypted secrets for your codespaces -intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### About encrypted secrets for {% data variables.product.prodname_codespaces %} - -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. - -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers -- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. - - {% data reusables.codespaces.secret-precedence %} - -#### Einschränkungen für Geheimnisse - -You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}. - -Geheimnisse sind auf 64 KB beschränkt. - -### Adding a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). - -### Editing a secret - -You can update the value of an existing secret, and you can change which repositories can access a secret. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Klicke auf **Save changes** (Änderungen speichern). - -### Deleting a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Lies die Warnung, dann klicke auf **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index c9492f1760..0000000000 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Managing GPG verification for Codespaces -intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index f7e213e258..0000000000 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Reviewing your security logs for Codespaces -shortTitle: Reviewing your security logs -intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### About security logs for {% data variables.product.prodname_codespaces %} - -When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user 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)." - -![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) - -The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/de-DE/content/codespaces/quickstart.md b/translations/de-DE/content/codespaces/quickstart.md deleted file mode 100644 index ce704597cf..0000000000 --- a/translations/de-DE/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Quickstart for GitHub Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### Einführung - -In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. - -The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles. - -### Creating your codespace - -1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces). - -2. Benutze das {% octicon "download" aria-label="The download icon" %} **Code**-Dropdownmenü unterhalb des Repository-Namens und wähle **Open with Codespaces** (Eröffnen mit Codespaces). - - ![Schaltfläche „Open with Codespaces" (Eröffnen mit Codespaces)](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png) - -### Run the application - -With your project open in a codespace, you can now run the application and launch it in a browser. - -1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository. - - ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Click **Open in Browser** to view your running application in a new tab. - -### Personalize with a theme extension - -Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow. - -1. In the left sidebar, click the Extensions icon. - -2. In the search bar, enter `fairyfloss` and install the fairyfloss extension. - - ![Add an extension](/assets/images/help/codespaces/add-extension.png) - -3. Select the `fairyfloss` theme by selecting it from the list. - - ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) - -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalize with dotfiles - -If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation. - -This example guides you through creating a dotfiles repository for your codespaces. - -1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/). - -2. Fork the repository to your account and ensure it's public. - - Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization. - -3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text. - - ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png) - -### Next Steps - -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_codespaces %}. - - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages - - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project. diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index c2e18a3030..0000000000 --- a/translations/de-DE/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Codespace für Dein Projekt konfigurieren -intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About dev containers - -A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project. - -{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`. - -For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation. - -#### Dockerfile - -A Dockerfile also lives in the `.devcontainer` folder. - -You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -You can use the `RUN` instruction to install any software and `&&` to join commands. - -Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation. - -### Using the default configuration - -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs. - -Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository. - -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides. - - -### Using a predefined container configuration - -Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. - -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup. - -1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. -1. Klicke auf **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png) - - -### Erstellen einer benutzerdefinierten Codespace-Konfiguration - -If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} - -In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. - -{% data reusables.codespaces.vscode-settings-order %} - -Du kannst die Standard-Editor-Einstellungen für {% data variables.product.prodname_vscode %} an zwei Orten festlegen. - -* Editor-Einstellungen, die in `.vscode/settings.json` definiert sind, werden als _Workspace_-bezogene Einstellungen im Codespace angewendet. -* Editor--Einstellungen, die im `settings`-Schlüssel in der `devcontainer.json`-Datei definiert sind, werden als as _Remote [Codespaces]_-bezogene Einstellungen im Codespace angewendet. - -After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." - - - - -### Applying changes to your configuration - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %} diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index f47cc82ec3..0000000000 --- a/translations/de-DE/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Setting up your codespace -intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 18f3605d23..0000000000 --- a/translations/de-DE/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Codespaces für Dein Konto personalisieren -intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About personalizing {% data variables.product.prodname_codespaces %} - -When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces. - -- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations. - -{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create. - -Projektbetreuer können auch eine Standardkonfiguration definieren, die für jeden Codespace eines Repositorys gilt, egal wer ihn erstellt. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -### Settings Sync - -Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}. - -Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync. - -![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation. - -### Dotfiles - -'Dotfiles' sind Dateien und Verzeichnisse auf Unix-ähnlichen Systemen, die mit `.` beginnen und die die Konfiguration von Anwendungen und Shells auf Deinem System kontrollieren. Du kannst Deine 'dotfiles' in einem Repository auf {% data variables.product.prodname_dotcom %} speichern und verwalten. Für Ratschläge und Tutorials dazu, was Du in Deinem `dotfiles`-Repository hinzufügen solltest, siehe [GitHub does dotfiles](https://dotfiles.github.io/) (GitHub benutzt 'dotfiles'). - -Wenn Dein Benutzerkonto auf {% data variables.product.prodname_dotcom %} ein öffentliches Repository mit Namen `dotfiles` besitzt, wird {% data variables.product.prodname_dotcom %} dieses Repository automatisch nutzen, um Deine Codespace-Umgebung zu personalisieren. Private `dotfiles`-Repositorys sind momentan nicht unterstützt. - -Dein `dotfiles`-Repository könnte Deine Shell-Aliase und -Voreinstellungen beinhalten, sämtliche Werkzeuge, die Du installieren möchtest, oder jede andere Codespace-Personalisierung, die Du machen willst. - -Wenn Du einen neuen Codespace erstellst, klont {% data variables.product.prodname_dotcom %} Dein `dotfiles`-Repository in die Codespace-Umgebung und sucht nach einer der folgenden Dateien, um die Umgebung einzurichten. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -Wenn keine dieser Dateien gefunden wird, werden Dateien oder Ordner in `dotfiles`, die mit einem `.` beginnen, symbolisch zum `~`- or `$HOME`-Verzeichnis des Codespace verknüpft. - -Änderungen an Deinem `dotfiles`-Repository gelten nur für neue Codespaces und verändern bestehende Codespaces nicht. - -{% note %} - -**Hinweis:** Derzeit unterstützt {% data variables.product.prodname_codespaces %} kein personalisieren der _Benutzer_ Einstellungen für den {% data variables.product.prodname_vscode %}-Editor mit Deinem `dotfiles`-Repository. Du kannst Standardeinstellungen für den _Arbeitsbereich _ und die _Remote [Codespaces]_ für ein bestimmtes Projekt in einem Projekt-Repository festlegen. Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Projekt konfigurieren](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)." - -{% endnote %} - -You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." - -### Weiterführende Informationen - -* „[Ein neues Repository erstellen](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/de-DE/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/de-DE/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 8a1128db5e..0000000000 --- a/translations/de-DE/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} is free to use during the beta. When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage. diff --git a/translations/de-DE/data/reusables/codespaces/about-configuration.md b/translations/de-DE/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 728a09052c..0000000000 --- a/translations/de-DE/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -Du kannst eine Standard-Codespace-Konfiguration für Dein Repository erstellen, welche die Umgebung jedes neuen Codespace bestimmt, den jemand für dieses Repository erstellt. The configuration defines a development container that can include frameworks, tools, extensions, and port forwarding. diff --git a/translations/de-DE/data/reusables/codespaces/about-personalization.md b/translations/de-DE/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index 12c6c4dcc7..0000000000 --- a/translations/de-DE/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Die Personalisierung kann Shell-Präferenzen und zusätzliche Werkzeuge beinhalten. diff --git a/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md b/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 39b29dc4a0..0000000000 --- a/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -You can forward ports in your codespace to test and debug your application. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 8031bfb4af..0000000000 --- a/translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/beta-functionality-limited.md b/translations/de-DE/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 9b0644a2c9..0000000000 --- a/translations/de-DE/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -Während der Beta-Phase ist die Funktionalität limitiert. -- {% data reusables.codespaces.use-chrome %} -- Nur eine einzige Größe von Codespace ist verfügbar. -- Nur Linux-Container werden unterstützt. -- Ein Codespace kann nicht vollständig wiederaufgenommen werden. Prozesse, die zum Zeitpunkt des Stopps des Codespace ausgeführt wurden, werden nicht neu gestartet. diff --git a/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index 7f3cc83952..0000000000 --- a/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. Klicke in der linken Seitenleiste von {% data variables.product.prodname_vscode %} auf das „Remote Explorer"-Symbol. ![Das „Remote Explorer"-Symbol in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/codespace-config-order.md b/translations/de-DE/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index e02e59bf04..0000000000 --- a/translations/de-DE/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Deine `dotfiles`-Personalisierung wird vor der Standard-Codespace-Konfiguration eines Repositorys angewendet. diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index 9ba14a8df7..0000000000 --- a/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Jeder Codespace ist mit einem spezifischen Branch eines Repositorys verbunden. diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md b/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index a9f41f0c21..0000000000 --- a/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Jeder von Dir erstellte Codespace steht nur Dir zur Verfügung. Niemand sonst kann in Deinem Codespace arbeiten. diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md b/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index 475114c1c5..0000000000 --- a/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.{% note %} - -**Note:** {% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types: - -* **Basic** for updating a file and raising a pull request -* **Standard** for editing a website -* **Premium** for high compute tasks such as data analysis diff --git a/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md b/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 87bfa539ff..0000000000 --- a/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users. - -For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/de-DE/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index 4d10268bd3..0000000000 --- a/translations/de-DE/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -Du kannst pro Repository oder sogar pro Branch mehr als einen Codespace erstellen. However, each user account has a two-codespace limit during limited public beta. Wenn Du das Limit erreicht hast und einen neuen Codespace erstellen möchtest, musst Du zuerst einen Codespace löschen. diff --git a/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index f6f389132b..0000000000 --- a/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -Du kannst Dich direkt aus {% data variables.product.prodname_vscode %} mit Deinem Codespace verbinden. For more information, see "[Using Codespaces in {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." diff --git a/translations/de-DE/data/reusables/codespaces/devcontainer-location.md b/translations/de-DE/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index 196fc006be..0000000000 --- a/translations/de-DE/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -This file can be located in the root of the repository or in a folder called `.devcontainer`. If the file is located in the root of the repository, the filename must begin with a period: `.devcontainer.json`. diff --git a/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces.md b/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index f13ff1cd8c..0000000000 --- a/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. Klicke zuoberst auf einer beliebigen Seite auf **Codespaces**. ![{% data variables.product.prodname_codespaces %}-Link in der Kopfzeile](/assets/images/help/codespaces/header-link.png) diff --git a/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index fed860897b..0000000000 --- a/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/de-DE/data/reusables/codespaces/rebuild-command.md b/translations/de-DE/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index ea9e45b032..0000000000 --- a/translations/de-DE/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/recovery-mode.md b/translations/de-DE/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index fa4e73d013..0000000000 --- a/translations/de-DE/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/release-stage.md b/translations/de-DE/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 4eb00a36b8..0000000000 --- a/translations/de-DE/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Hinweis:** {% data variables.product.prodname_codespaces %} befindet sich derzeit in der eingeschränkten Beta-Phase und kann sich jederzeit verändern. Weitere Informationen zum Beitritt zur Beta-Phase findest Du unter „[Über {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." - -{% endnote %} diff --git a/translations/de-DE/data/reusables/codespaces/secret-precedence.md b/translations/de-DE/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index 582b91c1aa..0000000000 --- a/translations/de-DE/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/secrets-naming.md b/translations/de-DE/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index f19197f144..0000000000 --- a/translations/de-DE/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -Die folgenden Regeln gelten für geheime Namen: - -* Geheime Namen dürfen nur alphanumerische Zeichen (`[a-z]`, `[A-Z]`, `[0-9]`) oder Unterstriche (`_`) enthalten. Leerzeichen sind nicht zulässig. -* Geheime Namen dürfen nicht mit dem `GITHUB_` -Präfix beginnen. -* Geheime Namen dürfen nicht mit einer Zahl beginnen. -* Secret names are not case-sensitive. -* Geheime Namen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/secrets-on-start.md b/translations/de-DE/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index c4a5bf3b41..0000000000 --- a/translations/de-DE/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md b/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index 90b3503dcd..0000000000 --- a/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display.md b/translations/de-DE/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index 09917cd3c8..0000000000 --- a/translations/de-DE/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. - - ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/type-port-label.md b/translations/de-DE/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 498c9eb752..0000000000 --- a/translations/de-DE/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/unsupported-repos.md b/translations/de-DE/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index ac3f7622a2..0000000000 --- a/translations/de-DE/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -Während der Beta-Phase werden private Repositorys von Organisationen oder Repositorys von Organisation, die SAML Single Sign-On verlangen, nicht unterstützt. diff --git a/translations/de-DE/data/reusables/codespaces/use-chrome.md b/translations/de-DE/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index 06e3da3183..0000000000 --- a/translations/de-DE/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -Für die beste Erfahrung mit {% data variables.product.prodname_codespaces %} empfehlen wir die Verwendung eines Chromium-basierten Browsers wie beispielsweise Google Chrome oder Microsoft Edge. diff --git a/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md b/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index 77d8f0ba9e..0000000000 --- a/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -You can edit code, debug, and use Git commands while developing in a codespace with {% data variables.product.prodname_vscode %}. Weitere Informationen findest Du in der [{% data variables.product.prodname_vscode %}-Dokumentation](https://code.visualstudio.com/docs). diff --git a/translations/de-DE/data/reusables/codespaces/vscode-settings-order.md b/translations/de-DE/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 197cf0c2f0..0000000000 --- a/translations/de-DE/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -Wenn Du die Editor-Einstellungen für {% data variables.product.prodname_vscode %} konfigurierst, stehen Dir drei Bereiche zur Verfügung: _Workspace_ (Arbeitsbereich), _Remote [Codespaces]_ (Remote-Codespace) und _User_ (Benutzer). Wenn eine Einstellung in mehreren Bereichen definiert ist, haben _Workspace_-Einstellungen erste Priorität, danach _Remote [Codespaces]_- und dann _User_-Einstellungen. diff --git a/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index afb626e71c..0000000000 --- a/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index a5e98437c0..0000000000 --- a/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**. - - !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/gated-features/codespaces.md b/translations/de-DE/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 0e77303c76..0000000000 --- a/translations/de-DE/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespaces sind für Benutzerkonten mit {% data variables.product.prodname_free_user %} oder {% data variables.product.prodname_pro %} verfügbar. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/de-DE/data/reusables/organizations/click-codespaces.md b/translations/de-DE/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index 6a15dd7757..0000000000 --- a/translations/de-DE/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index ae43f35c1f..0000000000 --- a/translations/de-DE/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md b/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index 82cb0fbffe..0000000000 --- a/translations/de-DE/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/user_settings/codespaces-tab.md b/translations/de-DE/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index e4908fcf75..0000000000 --- a/translations/de-DE/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/es-ES/content/codespaces/about-codespaces.md b/translations/es-ES/content/codespaces/about-codespaces.md deleted file mode 100644 index 966ea3fc6e..0000000000 --- a/translations/es-ES/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Acerca de Codespaces -intro: '{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo en línea configurable que hospeda {% data variables.product.prodname_dotcom %} y que impulsa {% data variables.product.prodname_vscode %}, el cual te permite desarrollar integralmente desde la nube.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo configurable en la nube que está disponible en tu buscador dentro de {% data variables.product.prodname_dotcom %} o a través de {% data variables.product.prodname_vscode %}. - -![Un codespace abierto](/assets/images/help/codespaces/codespace-overview.png) - -Un codespace incluye todo lo que necesitan los desarrolladores para desarrollar en un repositorio específico, incluyendo la experiencia de editar en {% data variables.product.prodname_vscode %} y los lenguajes, herramientas y utilidades comunes. {% data variables.product.prodname_codespaces %} es completamente configurable, lo cual te permite crear un ambiente de desarrollo personalizado para tu proyecto y le permite a los desarrolladores personalizar su experiencia con extensiones y ajustes de dotfile. - -Los codespaces ofrecen muchos beneficios para los equipos al permitir un ambiente consistente a través de todo tu equipo, una incorporación rápida y la creación de un espacio de desarrollo seguro. - -### Un ambiente consistente - -Puedes crear solo una configuración de codespace que defina el ambiente (o _contenedor dev_) de cada codespace nuevo que cualquiera pueda crear para tu repositorio. Una vez que hagas una configuración, los desarrolladores no tienen que preocuparse por instalar las herramientas correctas para comentar, revisar o contribuir. Ellos ya tendrán un ambiente estandarizado disponible tan pronto creen un codespace desde el repositorio. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -Para obtener ayuda en iniciar con las configuraciones para lenguajes específicos, consulta los tutoriales de [Inicio](/codespaces/getting-started-with-codespaces). - -Si bien cada codespace de tu repositorio tiene un ambiente de desarrollo consistente, los desarrolladores pueden utilizar los {% data variables.product.prodname_codespaces %} donde sea que los necesiten – en {% data variables.product.prodname_dotcom %} o a través de {% data variables.product.prodname_vscode %}. - -### Incorporación rápida y personal - -Si tienes configurado un [contenedor de dev](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) en tu repositorio, cualquier desarrollador puede integrarse rápidamente con el ambiente de desarrollo correcto para tu proyecto si utilizan el {% octicon "download" aria-label="The download icon" %} menú desplegable de **Código** y seleccionan **Abrir con codespaces**. - -![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -Como resultado de estandarizar en un ambiente de desarrollador repetible, los desarrolladores puede iniciar con codespaces nuevos sin hacer ninguna configuración manual y no necesitan dar mantenimiento contínuo para su ambiente de desarrollo. Se puede crear un codespace nuevo cuando inicias una característica nueva. - -Los desarrolladores también pueden personalizar algunos aspectos del ambiente de un codespace utilizando un repositorio de [dotfiles](https://dotfiles.github.io/tutorials/) y la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync). La personalización puede incluir preferencias de shell, herramientas adicionales, configuraciones de editor y extensiones tales como Live Share. Las personalizaciones que hagas se almacenan por usuario, así que cada codespace que abra un desarrollador tendrá su ambiente listo. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". - -Ya que se puede acceder a {% data variables.product.prodname_codespaces %} desde el buscador, los desarrolladores pueden trabajar en varios proyectos si cambian de pestaña. - -### Un ambiente seguro - -{% data variables.product.prodname_codespaces %} permite el desarrollo en la nube en vez de localmente. Esto crea una fuente única y rastreable de verdad. Los desarrolladores pueden contribuir desde donde sea, en cualquier máquina, incluyendo tablets o Chromebooks, y no es necesario mantener copias locales o propiedad intelectual. Los desarrolladores siempre tienen que iniciar sesión y contar con acceso tanto a {% data variables.product.prodname_codespaces %} como a los repositorios específcos. Estos permisos se pueden revocar en cualquier momento. Tan pronto revoques los accesos, estos desarrolladores perderán cualquier tipo de acceso a los recursos protegidos. Adicionalmente, los desarrolladores autenticados crean pistas de auditoría para que sepas quién hace qué. Para obtener más información sobre acceso y seguridad, consulta la sección "[Administrar el acceso y seguridad de los codespaces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". - -Utilizar {% data variables.product.prodname_codespaces %} es lo más seguro cuando todos los miembros de tu equipo lo están utilizando. Esto significa que no hay necesidad de clonar el repositorio en una máquina local y que los desarrolladores no necesitan instalar nada localmente como `root`. - -Los desarrolladores y administradores organizacionales también pueden configurar los ajustes para agregar secretos cifrados y habilitar la verificación de GPG. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados de los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Administrar la verificación GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### Acerca de la facturación para {% data variables.product.prodname_codespaces %} - -{% data reusables.codespaces.about-billing-for-codespaces %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)". - -### Unirse al beta - -Se invitará a una cantidad limitada de personas para unirse al beta. To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### Contáctanos para conocer sobre {% data variables.product.prodname_codespaces %} - -Si encuentras problemas al utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Solución de problemas para tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -Si aún necesitas ayuda o tienes algún tipo de retroalimentación sobre los {% data variables.product.prodname_codespaces %}, utiliza el debate de [Retroalimentación de los Codespaces](https://github.com/github/feedback/discussions/categories/codespaces-feedback). diff --git a/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index 5eeae1969c..0000000000 --- a/translations/es-ES/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Acerca de la facturación para Codespaces -intro: 'Cuando {% data variables.product.prodname_codespaces %} se hace generalmente disponible, se te cobrará por el almacenamiento y uso del procesamiento.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -Las actualizaciónes sobre el modelo de facturación para Codespaces se compartirán en un anuncio siguiente. diff --git a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index bd50b986ac..0000000000 --- a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Permitir que tu codespace acceda a una imagen de registro privada -intro: 'Puedes utilizar secretos para permitir que los {% data variables.product.prodname_codespaces %} accedan a un registro de imagen privada' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Un registro es un espacio seguro para almacenar y administrar imágenes privadas de contenedores, tales como el Registro de Contenedores de Azure o DockerHub. Puedes crear secretos en GitHub para almacenar los detalles de acceso para un registro privado y utilizarlos para otorgar acceso a tu codespace para las imágenes que se almacenan en el registro. - -Cuando ejecutas un codespace, {% data variables.product.prodname_codespaces %} verifica tres secretos, los cuales definen el nombre de servidor, nombre de usuario y token de acceso personal (PAT) para un registro de contenedor. Si se encuentran estos secretos, {% data variables.product.prodname_codespaces %} hará que el registro esté disponible dentro de tu codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -Puedes almacenar los secretos a nivel de repositorio, organización o usuario, lo cual te permite compartirlos de forma segura entre diferentes codespaces. Cuando creas un conjunto de secretos para un registro de imagen privado, necesitas reemplazar el "<*>” del nombre con un identificador consistente. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" y "[Administrar los secretos cifrados de tu repositorio y organización para los Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)". - -Por ejemplo, si tienes un registro de imagen privada en Azure, puedes crear los siguientes secretos: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Ejemplo de secreto de registro de imagen](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/es-ES/content/codespaces/codespaces-reference/index.md b/translations/es-ES/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index 22ad3e1567..0000000000 --- a/translations/es-ES/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Referencia -intro: 'Esta sección contiene referencias que te permitirán tener éxito con {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index a812a94ca0..0000000000 --- a/translations/es-ES/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Solucionar problemas de tu codespace -intro: Utiliza esta guía para ayudarte a solucionar los problemas comunes de tu codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Limitantes conocidas - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### Solución de problemas de {% data variables.product.prodname_vscode %} - -Utiliza las **Propuestas** en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) para registrar o conocer las propuestas que hay sobre la experiencia con {% data variables.product.prodname_vscode %}. - - -### Solución de problemas para la configuración - -{% data reusables.codespaces.recovery-mode %} - -``` -Este codespace se ejecuta acutalmente en modo de recuperación debido a un error del contenedor. -``` - -Revisa las bitácoras de creación, actualiza la configuración como lo requieras y ejecuta **Codespaces: Rebuild Container** en la paleta de comandos para volver a intentarlo. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". - -### Solución de problemas de dotfiles - -- Asegúrate que tu repositorio de dotfiles sea público. Si tienes secretos o datos sensibles que quieras utilizar en tu codespace, utiliza los [Secretos de codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) en vez de los dotfiles privados. -- Verifica `/workspaces/.codespaces/.persistedshare/dotfiles` para ver si se clonaron tus dotfiles. - - Si se clonaron tus dotfiles, intenta volver a ejecutar tu script de instalación manualmente para verificar si es ejecutable. - - Si tus dotfiles ni se clonaron, verifica `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` para ver si hubo un problema al clonarlos. -- Verifica `/workspaces/.codespaces/.persistedshare/creation.log` para encontrar problemas posibles. Como alternativa, puedes ver el `creation.log` si navegas a la paleta de comandos e ingresas **Codespaces: View Creation Log**. - - -### Solución de problemas del buscador - -Si encuentras problemas al utilizar un buscador que no se base en Chromium, intenta cambiar a uno que sí se base en él, o revisa los problemas conocidos de tu buscador en el repositorio `microsoft/vscode` buscando los problemas etiquetados con el nombre del buscador, tales como [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) o [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). - -Si encuentras problemas al utilizar un buscador basado en Chromium, puedes revisar si estás experimentando otro problema conocido con {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). - -### Solución de problemas el almacenamiento de contenedores - -Cuando creas un codespace, este tiene una cantidad de almacenamiento finita y, con el tiempo, podría que necesites liberar espacio. Intenta cualquiera de los siguientes elementos para liberar espacio de almacenamiento. - -- Elimina los paquetes que ya no se utilizan con `sudo apt autoremove` -- Limpia el caché de apt utilizando `sudo apt clean` -- Borra los archivos innecesarios como artefactos de compilación y bitácoras (estos dependen mucho del proyecto) -- Consulta los 10 archivos más grandes en el codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10` - -Más opciones destructivas: -- Elimina las imágenes de Docker, redes y contenedores sin utilizar con `docker system prune` (adjunta una `-a` si quieres eliminar todas las imágenes, y `--volumes` si quieres eliminar todos los volúmenes) -- Elimina los archivos no rastreados del árbol de trabajo: `git clean -i` - -### Contáctanos - -Si aún necesitas ayuda, puedes contactarnos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)". diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 36c5a3414f..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Crear un codespace -intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea. -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de la creación de codespaces - -Puedes crear un codespace ya sea en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Los codespaces se asocian con una rama específica de un repositorio y este repositorio no puede estar vacío. {% data reusables.codespaces.concurrent-codespace-limit %} Para obtener más información, consulta la sección "[Borrar un codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". - - -Cuando creas un codespace, suceden ciertos pasos para habilitar el acceso completo a tu ambiente de desarrollo. - -- Se asignan los recursos tales como MV y almacenamiento para tu contenedor. Se crea una MV cada vez que creas o inicias un codespace para garantizar que siempre tengas las versiones y parches de seguridad más recientes. -- {% data variables.product.prodname_codespaces %} recibe información de tu repositorio, rama, confirmaciones, tu repositorio de dotfiles público y de cualquier secreto que hayas creado. -- {% data variables.product.prodname_codespaces %} ejecuta un clon llano del repositorio. -- Si tienes uno en tu repositorio, {% data variables.product.prodname_codespaces %} ejecutará el archivo `devcontainer.json`. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". -- Se ejecuta tu contenedor de Docker, `docker-compose` u otra inicialización. -- En este punto, el codespace se marca como disponible y puedes conectarte. -- Una vez que el codespace se hace disponible, dependiendo de los comandos del contenedor dev, el codespace seguirá con algunas configuraciones. - - El codespace comparte los puertos que se agregaron en el archivo `devcontainer.json`. - - El codespace ejecuta lo que sea que se haya especificado en `postCreateCommand`. - - Los {% data variables.product.prodname_codespaces %} clonan tu repositorio de dotfiles en el ambiente de codespaces y buscan un archivo de instalación. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". - - Por fin, el codespace hace un clone integral del repositorio para que tengas acceso total a él. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Crear un codespace - -{% data reusables.repositories.navigate-to-repo %} -2. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear un codespace. - - ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png) - -3. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. Para crear un codespace utilizando un tipo de máquina estándar, haz clic en {% octicon "plus" aria-label="The plus icon" %}**Codespace nuevo**. - - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index 7b83d0416c..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Borrar un codespace -intro: Puedes borrar un codespace que ya no necesites. -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Navega al repositorio en donde creaste el codespace. Selecciona **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** y lugo haz clic en {% octicon "gear" aria-label="The Settings gear" %}. Esto mostrará todos los {% data variables.product.prodname_codespaces %} que hayas creado en el repositorio. ![Pestaña de codespaces](/assets/images/help/codespaces/codespaces-manage.png) - - Como alternativa, puedes ver cada codespace que pertenezca a tu cuenta de usuario en [github.com/codespaces](https://github.com/codespaces). - -2. A la derecha del codespace que quieres borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar {% octicon "trash" aria-label="The trash icon" %}** ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png) - -### Borrar un codespace en {% data variables.product.prodname_vscode %} - -Para obtener más información sobre borrar un codespace en {% data variables.product.prodname_vscode %}, consulta la sección "[Utilizar Codespaces en Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)". diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index 461bf24cdc..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Desarrollar en un codespace -intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca del desarrollo con {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} te proporciona la experiencia completa de desarrollo de {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Resumen de codespace con anotaciones](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Barra lateral - Predeterminadamente, esta área te muestra los archivos de tu proyexcto en el explorador. -2. Barra de actividad - Esto muestra las vistas y te proporciona una forma de cambiar entre ellas. Puedes volver a ordenar las vistas si las arrastras y las sueltas. -3. Editor - Aquí es donde editas tus archivos. Puedes utilzar la pestaña para que cada editor la posicione exactamente donde la necesitas. -4. Paneles - Aquí es donde puedes ver la información de salida y depuración, así como el lugar predeterminado para la Terminal integrada. -5. Barra de estado - Esta área te proporciona información útil sobre tu codespace y proyecto. Por ejemplo, el nombre de rama, los puertos configurados y más. - -Para obtener más información sobre cómo utilizar {% data variables.product.prodname_vscode %}, consulta la [Guía de interface de usuario](https://code.visualstudio.com/docs/getstarted/userinterface) en la documentación de {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -#### Personalizar tu codespace - -{% data reusables.codespaces.about-personalization %} Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)". - -{% data reusables.codespaces.apply-devcontainer-changes %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". - -#### Ejecutar tu app desde un codespace -{% data reusables.codespaces.about-port-forwarding %} Para obtener más información, consulta la sección "[Abrir puertos en tu codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)". - -#### Configramr tus cambios - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Navegar a un codespace existente - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Da clic en el nombre del codespace en el cual quieras desarrollar. ![Nombre del codespace](/assets/images/help/codespaces/click-name-codespace.png) - -Como alternativa, puedes ver cualquier codespace activo para un repositorio si navegas al repositorio en el que se hizo y seleccionas **Codespaces {% octicon "codespaces" aria-label="The codespaces icon" %}**. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 073026b8f2..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Reenviar puertos en tu codespace -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de los puertos reenviados - -La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web en el puerto 4000, puedes acceder a esta desde tu buscador para probarla y depurarla. - -Cuando una aplicación que se ejecuta en un codespace da salida a la consola a un puerto, el {% data variables.product.prodname_codespaces %} detecta el patrón de URL del host local y reenvía el puerto automáticamente. Puedes hacer clic en la URL de la terminal para abrir el puerto en un buscador. Por ejemplo, si una aplicación da como salida `http://127.0.0.1:4000` o `http://localhost:4000` en la consola, la bitácora convertirá la salida automáticamente en una URL para el puerto 4000 en la que se puede dar clic. - -![Reenvío automático de puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) - -También puedes reenviar un puerto manualmente, etiquetar puertos reenviados, compartir puertos reenviados públicamente y agregar puertos reenviados a la configuración del codespace. - -### Reenviar un puerto - -Puedes reenviar manualmente a un puerto que no se haya reenviado automáticamente. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Debajo de la lista de puertos, haz clic en **Agregar puerto**. ![Botón de agregar puerto](/assets/images/help/codespaces/add-port-button.png) -1. Teclea el número de puerto o de dirección y luego presiona enter. ![Botón de caja de texto para teclear el puerto](/assets/images/help/codespaces/port-number-text-box.png) - -### Etiquetar un puerto - -Puedes etiquetar un puerto para hacerlo más fácil de identificar en una lista. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Pasa el mouse sobre el puerto que quieras etiquetar y luego haz clic en el icono de etiqueta. ![Icono de etiqueta para el puerto](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Compartir un puerto - -Si quieres compartir un puerto reenviado con otros, puedes hacerlo público. Después de que lo haces público, cualquiera con la URL del puerto puede ver la aplicación que se ejecuta sin necesidad de autenticarse. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Haz clic derecho en el puerto que quieres compartir y luego en **Hacer público**. ![Opción para hacer el puerto público en el menú de clic derecho](/assets/images/help/codespaces/make-public-option.png) -1. A la derecha de la dirección local del puerto, haz clic en el icono de copiar. ![Copiar el icono para la URL del puerto](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Envía la URL copiada a la persona con la que quieras compartir el puerto. - -### Agregar el peurto a la configuración del codespace - -Puedes agregar un puerto reenviado a la configuración de {% data variables.product.prodname_codespaces %} del repositorio para que este pueda reenviarse automáticamente a todos los codespaces que se crearon desde el repositorio. Después de que actualizas la configuración, cualquier codespace creado debe reconstruirse para que el cambio se aplique. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". - -Puedes configurar manualmente los puertos reenviados en un archivo `.devcontainer.json` utilizando la propiedad `forwardPorts` o puedes utilizar el panel "Puertos" en tu codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Haz clic derecho en el puerto que quieras agregar a la configuración del codespace y luego haz clic en **Configurar etiqueta y actualizar devcontainer.json**. ![Opción para configurar una etiqueta y agregar el puerto a devcntainer.json en el menú de clic derecho](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index f0b7554478..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Desarrollar en un codespace -intro: 'Crea un codespace para comenzar a desarrollar tu proyecto dentro de un ambiente dedicado en la nube. Puedes utilizar puertos reenviados para ejecutar tu aplicación e incluso utilizar codespaces dentro de {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index d23fcf4096..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Utilizar codespaces en Visual Studio Code -intro: 'Puedes desarrollar tu codespace directamente en {% data variables.product.prodname_vscode %} si conectas la extensión de {% data variables.product.prodname_github_codespaces %} con tu cuenta en {% data variables.product.product_name %}.' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Prerrequisitos - -Para hacer desarrollos en un codespace directamente desde {% data variables.product.prodname_vscode %}, debes ingresar en la extensión de {% data variables.product.prodname_github_codespaces %}. La extensión de {% data variables.product.prodname_github_codespaces %} requiere el lanzamiento 1.51 de octubre de 2020 de {% data variables.product.prodname_vscode %} o superior. - -Utiliza {% data variables.product.prodname_vs %} Marketplace para instalar la extensión de [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obtener más información, consulta la sección[Extensión de Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) en la documentación de {% data variables.product.prodname_vscode %}. - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Da clic en **Registrarse para ver {% data variables.product.prodname_dotcom %}...**. ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**. -4. Regístrate en {% data variables.product.product_name %} para aprobar la extensión. - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Utiliza el menú desplegable de "REMOTE EXPLORER" y luego da clic en **{% data variables.product.prodname_github_codespaces %}**. ![El encabezado {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Da clic en **Registrarse para ver {% data variables.product.prodname_codespaces %}...**. ![Registrarse para ver {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. Para autorizar a {% data variables.product.prodname_vscode %} para acceder a tu cuenta en {% data variables.product.product_name %}, da clic en **Permitir**. -5. Regístrate en {% data variables.product.product_name %} para aprobar la extensión. - -{% endwindows %} - -### Crear un codespace en {% data variables.product.prodname_vscode %} - -Despuès de que conectas tu cuenta de {% data variables.product.product_name %} a la extensiòn de {% data variables.product.prodname_github_codespaces %}, puedes desarrollar en un codespace que hayas creado en {% data variables.product.product_name %} o en {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Da clic en el icono de Agregar y luego en **Crear codespace nuevo**. ![La opciòn de crear un codespace nuevo en {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Teclea y luego da clic en el nombre del repositorio en el que quieras desarrollar. ![Buscar un repositorio para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Da clic en la rama en la que quieras desarrollar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Haz clic en el tipo de máquina en la que quieres desarrollar. ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png) -### Abrir un codespace en {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Debajo de "Codespaces", da clic en el codespace en el que quieras desarrollar. -3. Da clic en en el icono de conexión al codespace. ![Icono de conectarse al codespace en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Cambiar el tipo de máquina en {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -Puedes cambiar el tipo de máquina de tu codespace en cualquier momento. - -1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos (`shift command P` / `shift control P`). -2. Busca y selecciona "Codespaces: Cambiar mi tipo de máquina". ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Haz clic en el codespace que quieras cambiar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Elige el tipo de máquina que quieres utilizar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -Si el codespace se está ejecutando actualmente, se mostrará un mensaje que pregunta si te gustaría reiniciar y reconectarte con tu codespace ahora. Haz clic en **Sí** en caso de que quieras cambiar el tipo de máquina que se utiliza para este codespace inmediatamente. Si haces clic en **No** o si el codespace no se está ejecutando actualmente, el cambio se reflejará la próxima vez que este se reinicie. - -### Borrar un codespace en {% data variables.product.prodname_vscode %} - -1. Debajo de "Codespaces", da clic derecho en el codespace que quieras borrar. -2. En el menù desplegable, da clic en **Borrar codespace**. ![Borrar un codespace en {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index 780e16af30..0000000000 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Utilizar el control de código fuente en tu codespace -intro: 'Después de hacer cambios en un archivo de tu codespace, puedes confirmar los cambios rápidamente y subir tu actualización al repositorio remoto.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca del control de código fuente en {% data variables.product.prodname_codespaces %} - -Puedes llevar a cabo todas las acciones de Git que necesites directamente dentro de tu codespace. Por ejemplo, puedes recuperar cambios del repositorio remoto, cambiar de rama, crear una rama nueva, confirmar y subir cambios y crear solicitudes de cambios. Puedes utilizar la terminal integrada dentro de tu codespace para ingresar comandos de Git o puedes hacer clic en los iconos u opciones de menú para completar las tareas más comunes de Git. Esta guía te explica cómo utilizar la interface de usuario gráfica para el control de código fuente. - -El control de fuentes en {% data variables.product.prodname_github_codespaces %} utiliza el mismo flujo de trabajo que {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección de la documentación de {% data variables.product.prodname_vscode %} "[Utilizar el control de versiones en VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". - -Un flujo de trabajo típico para actualizar un archivo utilizando {% data variables.product.prodname_github_codespaces %} sería: - -* Desde la rama predeterminada de tu repositorio en {% data variables.product.prodname_dotcom %}, crea un codespace. Consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -* En tu codespace, crea una rama nueva para trabajar en ella. -* Haz tus cambios y guárdalos. -* Confirma el cambio. -* Levanta una solicitud de cambios. - -### Crear o cambiar de rama - -1. Si la rama actual no se muestra en la barra de estado, en la parte inferior de tu codespace, haz clic derecho en la barra de estado y selecciona **Control de código fuente**. -1. Haz clic en el nombre de rama en la barra de estado. ![La rama en la barra de estado](/assets/images/help/codespaces/branch-in-status-bar.png) -1. En el menú desplegable, haz clic en la rama a la que quieras cambiar o ingresa el nombre de una rama nueva y haz clic en **Crear rama nueva**. ![Elige del menú de la rama](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Tip**: Si alguien cambió un archivo en el repositorio remoto, en la rama a la cual te cambiaste, no verás estos cambios hasta que los extraigas hacia tu codespace. - -{% endtip %} - -### Extraer cambios del repositorio remoto - -Puedes extraer cambios del repositorio remoto hacia tu codespace en cualquier momento. - -{% data reusables.codespaces.source-control-display-dark %} -1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. En el menú desplegable, haz clic en **Extraer**. - -Si algún contenedor dev cambió desde que creaste el codespace, puedes aplicar los cambios si recompilas el contenedor para el codespace. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". - -### Configurar tu codespace para que recupere los cambios nuevos automáticamente - -Puedes configurar tu codespace para que recupere automáticamente los detalles de cualquier confirmación nueva que se haya hecho al repositorio remoto. Esto te permite ver si tu copia local del repositorio está desactualizada, en cuyo caso, podrías elegir extraer los cambios nuevos. - -Si la operación de búsqueda detecta cambios nuevos en el repositorio remoto, verás la cantidad de confirmaciones nuevas en la barra de estado. Luego podrás extraer los cambios en tu copia local. - -1. Haz clic en el botón de **Administrar** en la parte inferior de la barra de actividad. ![Botón de administrar](/assets/images/help/codespaces/manage-button.png) -1. En el menú, haz clic en **Ajustes**. -1. En la página de ajustes, busca: `autofetch`. ![Buscar la recuperación automática](/assets/images/help/codespaces/autofetch-search.png) -1. Para recuperar los detalles de las actualizaciones para todos los remotos registrados para el repositorio actual, configura **Git: Autofetch** en `all`. ![Habilitar la recuperación automática en Git](/assets/images/help/codespaces/autofetch-all.png) -1. Si quieres cambiar la cantidad de segundos entre cada recuperación automática, edita el valor de **Git: Autofetch Period**. - -### Configramr tus cambios - -{% data reusables.codespaces.source-control-display-dark %} -1. Para probar tus cambios, haz clic en **+** junto al archivo que cambiaste o junto a **Cambios** si cambiaste archivos múltiples y quieres probarlos todos. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Teclea un mensaje de confirmación que describa el cambio que hiciste. ![Barra de control de código fuente con un mensaje de confirmación](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. Para confirmar tus cambios planeados, haz clic en la marca de verificación en la parte superior de la barra lateral del control de código fuente. ![Haz clic en el icono de verificación](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Levantar una solicitud de cambios - -1. Después de haber confirmado los cambios en tu copia local del repositorio, haz clic en el icono de **Crear solicitud de cambios**. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Verifica que el repositorio y la rama local desde la que estás haciendo la fusión y la rama y repositorio remotos hacia los que estés haciendo la fusión sean correctos. Después, asigna un nombre y descripción a la solicitud de cambios. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Da clic en **Crear**. - -### Subir cambios a tu repositorio remoto - -Puedes subir los cambios que has hecho. Esto aplica a aquellos de la rama ascendente en el repositorio remoto. Puede que necesites hacer eso si aún no estás listo para crear una solicitud de cambios o si prefieres crearla en {% data variables.product.prodname_dotcom %}. - -1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. En el menú desplegable, haz clic en **Subir**. diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index d074a19501..0000000000 --- a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Iniciar con tu proyecto de C# (.NET) en Codespaces -shortTitle: Iniciar con tu proyecto de C# (.NET) -allowTitleToDifferFromFilename: true -intro: 'Inicia con tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introducción - -Esta guía te muestra cómo configurar tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. - -#### Prerrequisitos - -- Debes tener un proyecto existente de C# (.NET) en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/2percentsilk/dotnet-quickstart. -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. - -### Paso 1: Abre tu proyecto en un codespace - -1. Navega al repositorio de tu proyecto. Utiliza el menú desplegable de {% octicon "download" aria-label="The download icon" %}**Código** y selecciona **Abrir con Codespaces**. Si no ves esta opción, tu proyecto no está disponible para {% data variables.product.prodname_codespaces %}. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para crear un codespace nuevo, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor de tu codespace tiene muchos lenguajes de programación y tiempos de ejecución, incluyendo a .NET. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. - -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. - -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla - -El contenedor predeterminado para los codespaces tiene la última versión de .NET y las herramientas más recientes preinstaladas. Sin embargo, te exhortamos a que configures un contenedor personalizado para que puedas diseñar las herramientas y scripts que se ejecutan como parte de la creación de un codespace para que satisfagan las necesidades de tu proyecto y garanticen un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} en tu repositorio. - -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Accede a la paleta de comandos (`shift command P` / `shift control P`), y luego comienza a teclear "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. Para este ejemplo, haz clic en **C# (.NET)**. Si necesitas características adicionales puedes seleccionar cualquier contenedor que sea específico para C# (.NET) o una combinación de herramientas tales como C# (.NET) y MS SQL. ![Selecciona la opción de C# (.NET) de la lista](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Haz clic en la versión recomendada de .NET. ![Selección de la versión de.NET](/assets/images/help/codespaces/add-dotnet-version.png) -4. Acepta la opción predeterminada para agregar a Node.js a tu personalización. ![Agregar la selección Node.js](/assets/images/help/codespaces/dotnet-options.png) -5. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomía de tu contenedor dev - -El agregar la plantilla de contenedor dev de C# (.NET) agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: - -- `devcontainer.json` -- Dockerfile - -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, `dockerfile` es una referencia al Dockerfile que también se agregó desde la plantilla. - - **Args** - - **Variant**: Este archivo solo contiene el argumento de compilación, el cual es la versión de .NET Core que queremos utilizar. -- **Settings** - Esta es la configuración de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **ms-dotnettools.csharp** - La extensión de C# de Microsoft proporciona soporte enriquecido para desarrollar en C#, incluyendo características tales como IntelliSense, limpieza de código, depuración, navegación de código, formateo de código, refactorización, explorador de variables, explorador de pruebas y más. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar cualquier cosa después de que llegas a tu codespace y esto no se define en el Dockerfile, como `dotnet restore`, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de vscode, pero puedes configurar esto como root opcionalmente. - -##### Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro contenedor. - -### Paso 3: Modifica tu archivo devcontainer.json - -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y restablecer las dependencias de tu proyecto cuando se lance tu codespace. - -1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. - - !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Actualiza tu lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Deja de comentar el `postCreateCommand` para restablecer las dependencias como parte del proceso de configuración del codespace. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. Para volver a compilar tu contenedor y aplicar los cambios del devcontainer.json, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. - - ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. - -5. Verifica que tus cambios se hayan aplicado con éxito verificando que se haya instalado la extensión "Code Spell Checker". - - ![Lista de extensiones](/assets/images/help/codespaces/dotnet-extensions.png) - -### Paso 4: Ejecuta tu aplicación - -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de pip3. Ahora que instalamos nuestras dependencias, podemos ejecutar nuestra aplicación. - -1. Ejecuta tu aplicación presionando `F5` o ingresando `dotnet watch run` en tu terminal. - -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. - - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/python-port-forwarding.png) - -### Paso 5: Confirma tus cambios - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Pasos siguientes - -Ahora debes estar listo para comenzar a desarrollar tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. - -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 22850354b6..0000000000 --- a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Iniciar con tu proyecto de Java en Codespaces -shortTitle: Iniciar con tu proyecto de Java -intro: 'Inica con tu proyecto de Java en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introducción - -Esta guía te muestra cómo configurar tu proyecto de Java en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. - -#### Prerrequisitos - -- Debes tener un proyecto de Java existente en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/microsoft/vscode-remote-try-java -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. - -### Paso 1: Abre tu proyecto en un codespace - -1. Navega al repositorio de tu proyecto. Utiliza el menú desplegable de {% octicon "download" aria-label="The download icon" %}**Código** y selecciona **Abrir con Codespaces**. Si no ves esta opción, tu proyecto no está disponible para {% data variables.product.prodname_codespaces %}. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para crear un codespace nuevo, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo Java, nvm, npm, y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. - -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. - -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla - -El contenedor predeterminado para los codespaces viene con la última versión de Java, adminsitradores de paquetes (Maven, Gradle) y otras herramientas comunes preinstaladas. Sin embargo, te recomendamos que configures un contenedor personalizado para definir las herramientas y scripts que necesita tu proyecto. Esto garantizará un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} de tu repositorio. - -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Accede a la paleta de comandos (`shift command P` / `shift control P`), y luego comienza a teclear "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. Para este ejemplo, haz clic en **Java**. En la práctica, podrías seleccionar cualquier contenedor que sea específico de Java o una combinación de herramientas tales como Java y Azure Functions. ![Selecciona la opción de Java de la lista](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Haz clic en la versión recomendada de Java. ![Selección de la versión de Java](/assets/images/help/codespaces/add-java-version.png) -5. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomía de tu contenedor dev - -El agregar la plantilla de contenedor dev de Java agrega una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: - -- `devcontainer.json` -- Dockerfile - -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, dockerfile es una referencia al Dockerfile que también se agregó desde la plantilla. - - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la versión de Java que se pasa al Dockerfile. -- **Settings** - Estos son los ajustes de {% data variables.product.prodname_vscode %} que puedes configurar. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **Vscjava.vscode-java-pack** - El paquete de extensión de Java proporciona extensiones populares para que puedas comenzar a desarrollar en Java. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar lo que sea después de que llegas a tu codespace, lo cual no está definido en tu Dockerfile, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de `vscode`, pero puedes configurar esto como `root` opcionalmente. - -##### Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de Java o paquetes globales que queremos incluir en nuestro Dockerfile. - -### Paso 3: Modifica tu archivo devcontainer.json - -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y tus dependencias de pryecto cuando se lance tu codespace. - -1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. - - !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - Para obtener más información sobre las propiedades de `devcontainer.json`, consulta las [referencias de devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) en los documentos de Visual Studio Code. - -3. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. - - ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. - - -### Paso 4: Ejecuta tu aplicación - -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de npm. Ahora puedes utilizar esto para ejecutar nuestra aplicación con npm. - -1. Ejecuta tu aplicación presionando `F5`. - -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. - - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Paso 5: Confirma tus cambios - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Pasos siguientes - -Ahora debes estar listo para desarrollar tu proyecto de Java en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. - -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 403ead5f3e..0000000000 --- a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Iniciar con tu proyecto de Node.js en Codespaces -shortTitle: Iniciar con tu proyecto de Node.js -intro: 'Inicia con tu proyecto de JavaScript, Node.js o TypeScript en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### Introducción - -Esta guía te muestra cómo configurar tu proyecto de JavaScript, Node.js o TypeScript en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. - -#### Prerrequisitos - -- Debes tener un proyecto existente de JavaScript, Node.js, TypeScript en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/microsoft/vscode-remote-try-node -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. - -### Paso 1: Abre tu proyecto en un codespace - -1. Navega al repositorio de tu proyecto. Utiliza el menú desplegable de {% octicon "download" aria-label="The download icon" %}**Código** y selecciona **Abrir con Codespaces**. Si no ves esta opción, tu proyecto no está disponible para {% data variables.product.prodname_codespaces %}. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para crear un codespace nuevo, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo a Node.js, JavaScript, TypeScript, nvm, npm y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. - -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. - -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -### Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla - -El contenedor predeterminado de codespaces será compatible para ejecutar proyectos de Node.js como [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) fuera de la caja. Al configurar un contenedor personalizado, puedes personalizar las herramientas y scripts que se ejecutan como parte de la creación de codespaces y asegurarte de que haya un ambiente integralmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} en tu repositorio. - -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Accede a la paleta de comandos (`shift command P` / `shift control P`), y luego comienza a teclear "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. Para este ejemplo, haz clic en **Node.js**. Si necesitas características adicionales, puedes seleccionar cualquier contenedor que sea específico para Node o una combinación de herramientas tales como Node y MongoDB. ![Selecciona la opción Node de la lista](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Haz clic en la versión recomendada de Node.js. ![Selección de la versión de Node.js](/assets/images/help/codespaces/add-node-version.png) -5. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomía de tu contenedor dev - -El agregar la plantilla de contenedor dev de Node.js agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: - -- `devcontainer.json` -- Dockerfile - -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **dockerfile** - En el objeto de compilación, dockerfile es una referencia al Dockerfile que también se agregó desde la plantilla. - - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la variante de nodo que queremos utilizar y que se pasa en el Dockerfile. -- **Settings** - Estos son los ajustes de {% data variables.product.prodname_vscode %} que puedes configurar. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **Dbaeumer.vscode-eslint** - ES lint es una extención genial para limpiar código, pero para JavaScript, hay varias extensiones buenas en Marketplace que también podrías incluir. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar lo que sea después de que llegas a tu codespace, lo cual no está definido en tu Dockerfile, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de vscode, pero puedes configurar esto como root opcionalmente. - -##### Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro Dockerfile. - -### Paso 3: Modifica tu archivo devcontainer.json - -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás propiedades para instalar npm cuando tu codespace se lance y haga una lista de puertos dentro del contenedor que está disponible localmente. - -1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. - - !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - Para obtener más información sobre las propiedades de `devcontainer.json`, consulta la [ referencia de devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) en los documentos de {% data variables.product.prodname_vscode %}. - -3. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. - - ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que los confirmes los en el repositorio. Si algo falla, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes volver a compilar para seguir ajustando tu contenedor. - - -### Paso 4: Ejecuta tu aplicación - -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de npm. Ahora puedes utilizar esto para ejecutar nuestra aplicación con npm. - -1. Ejecuta tu comando de inicio en la terminal con `npm start`. - - ![npm start en la terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. - - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Paso 5: Confirma tus cambios - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Pasos siguientes - -Ahora debes estar listo para comenzar a desarrollar tu proyecto de JavaScript en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. - -- [Administrar secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index 13357e581d..0000000000 --- a/translations/es-ES/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Iniciar con tu proyecto de Python en Codespaces -shortTitle: Iniciar con tu proyecto de Python -intro: 'Iniciar con tu proyecto de Python en {% data variables.product.prodname_codespaces %} creando un contenedor de dev personalizado.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### Introducción - -Esta guía te muestra cómo configurar tu proyecto de Python en {% data variables.product.prodname_codespaces %}. Te mostrará un ejemplo de cómo abrir tu proyecto en un codespace y cómo agregar y modificar una configuración de contenedor de dev desde una plantilla. - -#### Prerrequisitos - -- Debes tener un proyecto existente de Python en un repositorio de {% data variables.product.prodname_dotcom_the_website %}. Si no tienes un proyecto, puedes probar este tutorial con el siguiente ejemplo: https://github.com/2percentsilk/python-quickstart. -- Debes tener {% data variables.product.prodname_codespaces %} habilitado en tu organización. - -### Paso 1: Abre tu proyecto en un codespace - -1. Navega al repositorio de tu proyecto. Utiliza el menú desplegable de {% octicon "download" aria-label="The download icon" %}**Código** y selecciona **Abrir con Codespaces**. Si no ves esta opción, tu proyecto no está disponible para {% data variables.product.prodname_codespaces %}. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para crear un codespace nuevo, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - -Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo a Node.js, JavaScript, TypeScript, nvm, npm y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. - -Puedes personalizar tu codespace si ajustas la cantidad de vCPU y RAM, [agregando dotfiles para personalizar tu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account) o modificando las herramientas y scripts instalados. - -{% data variables.product.prodname_codespaces %} utiliza un archivo denominado `devcontainer.json` para almacenar configuraciones. Cuando se lanzan, los {% data variables.product.prodname_codespaces %} utilizan el archivo para instalar cualquier herramienta, dependencia u otro tipo de configuración que pueda necesitarse para el proyecto. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Paso 2: Agrega un contenedor de dev a tu codespace desde una plantilla - -El contenedor predeterminado de codespaces viene con la última versión de Python, administradores de paquete (pip, Miniconda), y otras herramientas comunes preinstaladas. Sin embargo, te recomendamos que configures un contenedor personalizado para definir las herramientas y scripts que necesita tu proyecto. Esto garantizará un ambiente totalmente reproducible para todos los usuarios de {% data variables.product.prodname_codespaces %} de tu repositorio. - -Para configurar tu proyecto con un contenedor personalizado, necesitarás utilizar un archivo `devcontainer.json` para definir el ambiente. En {% data variables.product.prodname_codespaces %}, puedes agregarlo ya sea desde una plantilla o puedes crear el tuyo propio. Para obtener más información sobre contenedores dev, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Accede a la paleta de comandos (`shift command P` / `shift control P`), y luego comienza a teclear "dev container". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. Para este ejemplo, haz clic en **Python 3**. Si necesitas características adicionales, puedes seleccionar cualquier contenedor que sea específico para Python o una combinación de herramientas tales como Python 3 y PostgreSQL. ![Selecciona la opción Python de la lista](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Haz clic en la versión recomendada de Python. ![Selección de la versión Python](/assets/images/help/codespaces/add-python-version.png) -4. Acepta la opción predeterminada para agregar a Node.js a tu personalización. ![Agregar la selección Node.js](/assets/images/help/codespaces/add-nodejs-selection.png) -5. Para volver a compilar tu contenedor, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomía de tu contenedor dev - -El agregar la plantilla de contenedor dev de Python agregará una carpeta de `.devcontainer` a la raíz del repositorio de tu proyecto con los siguientes archivos: - -- `devcontainer.json` -- Dockerfile - -El archivo `devcontainer.json` recién agregado define unas cuantas propiedades que se describen después de la muestra. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - Puedes nombrar a tu contenedor dev como quieras, esto es solo lo predeterminado. -- **Build** - Las propiedades de compilación. - - **Dockerfile** - En el objeto de compilación, `dockerfile` es una referencia al Dockerfile que también se agregó desde la plantilla. - - **Args** - - **Variant**: Este archivo solo contiene un argumento de compilación, el cual es la variante de nodo que queremos utilizar y que se pasa en el Dockerfile. -- **Settings** - Esta es la configuración de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Si bien bash es lo predeterminado aquí, podrías utilizar otros shells de terminal si lo modificas. -- **Extensions** - Estas son las extensiones que se incluyen predeterminadamente. - - **ms-python.python** - La extensión de Python de Microsoft te proporciona una compatibilidad enriquecida para el lenguaje Python (para todas las versiones compatibles del lenguaje: >=3.6), incluyendo las característcas tales como IntelliSense, limpieza, depuración, navegación de código, formateo de código, refactorización, explorador de variables, explorador de pruebas y más. -- **forwardPorts** - Cualquier puerto que se liste aquí se reenviará automáticamente. -- **postCreateCommand** - Si quieres ejecutar cualquier cosa después de que llegues a tu codespace y que no se defina en el Dockerfile, como `pip3 install -r requirements`, puedes hacerlo aquí. -- **remoteUser** - Predeterminadamente, lo estás ejecutando como el usuario de `vscode`, pero puedes configurar esto como `root` opcionalmente. - -##### Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Puedes utilizar este Dockerfile para agregar capas de contenedor adicionales y especificar paquetes de SO, versiones de nodo o paquetes globales que queremos incluir en nuestro contenedor. - -### Paso 3: Modifica tu archivo devcontainer.json - -Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo que hace cada cosa, puedes hacer cambios para configurarlo para tu ambiente. En este ejemplo, agregarás porpiedades para instalar extensiones y tus dependencias de pryecto cuando se lance tu codespace. - -1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. - - !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Actualiza la lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Quita el comentario de `postCreateCommand` para instalar automáticamente los requisitos como parte del proceso de configuración de codespaces. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. Para volver a compilar tu contenedor y aplicar los cambios del devcontainer.json, accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclear "rebuild". Haz clic en **Codespaces: Rebuild Container**. - - ![Opción de recompilar contenedor](/assets/images/help/codespaces/codespaces-rebuild.png) - - Reconstruir dentro de tu codespace garantiza que tus cambios funcionan como se espera antes de que confirmes los cambios en el repositorio. Si algo resulta en un fallo, se te colocará en un codespace con un contenedor de recuperación desde el cual puedes reconstruir para seguir ajustando tu contenedor. - -5. Verifica tus cambios en donde se aplicaron con éxito verificando que se hayan instalado las extensiones "Code Spell Checker" y "Flask Snippet". - - ![Lista de extensiones](/assets/images/help/codespaces/python-extensions.png) - -### Paso 4: Ejecuta tu aplicación - -En la sección anterior, utilizaste `postCreateCommand` para instalar un conjunto de paquetes a través de pip3. Ahora que instalaste tus dependencias, puedes ejecutar tu aplicación. - -1. Ejecuta tu aplicación presionando `F5` o ingresando `python -m flask run` en la terminal del codespace. - -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. - - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/python-port-forwarding.png) - -### Paso 5: Confirma tus cambios - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Pasos siguientes - -Ahora debes estar listo para comenzar a desarrollar tu proyecto de Python en {% data variables.product.prodname_codespaces %}. Aquí tienes algunos recursos adicionales para situaciones más avanzadas. - -- [Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Administrar la verificación GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md b/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index f81ad81438..0000000000 --- a/translations/es-ES/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Iniciar con {% data variables.product.prodname_codespaces %}' -intro: 'Aprende cómo iniciar con los {% data variables.product.prodname_codespaces %}, incluyendo cómo configurar y hacer ajustes para lenguajes específicos.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md deleted file mode 100644 index 35c01d51c0..0000000000 --- a/translations/es-ES/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Guías de codespaces -shortTitle: Guías -intro: 'Aprende cómo sacar el mayor provecho de los {% data reusables.gated-features.codespaces %} de GitHub' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/es-ES/content/codespaces/index.md b/translations/es-ES/content/codespaces/index.md deleted file mode 100644 index 084fcf5a37..0000000000 --- a/translations/es-ES/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Documentación de Codespaces de GitHub -beta_product: true -shortTitle: Acerca de GitHub Codespaces -intro: 'Crea un codespace o comienza a desarrollar en un ambiente de desarrollo seguro, configurable y dedicado que funciona donde y como tu quieras.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index e244090735..0000000000 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Managing Codespaces for your organization -intro: 'Puedes administrar y revisar la forma en que los usuarios de tu organización pueden utilizar {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index 2c95617994..0000000000 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Administrar el acceso y la seguridad para los codespaces de tu organización -shortTitle: Administrar el acceso y la seguridad para tu organización -intro: 'Puedes administrar los repositorios de tu organización a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Los propietarios de la organización pueden administrar a qué repositorios pueden acceder los codespaces. - -Predeterminadamente, un codespace solo puede acceer al repositorio en donde se creó. Cuando habilitas el acceso y la seguridad de un repositorio que pertenece a tu orgnización, cualquier codespace que se cree para dicho repositorio también tendrá permisos de lectura y escritura en el resto de los repositorios que pertenezcan a esa misma organización y a los cuales pueda acceder el creador de dicho codespace. Si quieres restringir los repositorios a los cuales puede acceder un codespace, puedes limitarlos a ya sea el repositorio en donde se creó el codespace o a algunos repositorios específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. - -Para administrar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Administrar permisos de usuarios para tu organización](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)". - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Debajo de "Acceso y seguridad", selecciona la configuración que quieras para tu organización.![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. Si eliges "Repositorios seleccionados"; entonces selecciona el menú desplegable y da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que pertenecen a tu organización. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de los repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index e47627cba0..0000000000 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Administrar los secretos cifrados de tu repositorio y organización para los Codespaces -shortTitle: Administrar los secretos de tu repositorio y organización -intro: 'Los secretos cifrados te permiten almacenar información sensible en tu organización, repositorio o {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de los secretos - -Los secretos son variables de ambiente cifradas que creas en una organización o repositorio. Los secretos que creas están disponibles para utilizarse en {% data variables.product.prodname_codespaces %}. GitHub utiliza una [caja sellada de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para cifrar los secretos antes de que lleguen a GitHub y solo los decifra cuando los utilizas en un codespace. - -Los secretos a nivel organizacional te permiten compartir secretos entre repositorios múltiples, lo cual reduce la necesidad de crear secretos duplicados. Puedes utilizar las políticas de acceso para controlar qué repositorios pueden utilizar los secretos de la organización. - -{% data reusables.codespaces.secrets-on-start %} - -#### Nombrar secretos - -{% data reusables.codespaces.secrets-naming %} Por ejemplo, un secreto que se creó a nivel de repositorio debe tener un nombre único en dicho repositorio y uno que se haya cerado a nivel organizacional debe tener un nombre único en dicho nivel. - - {% data reusables.codespaces.secret-precedence %} - -#### Límites para los secretos - -Puedes almacenar hasta 100 secretos por organización y 100 por repositorio. - -Los secretos tienen un tamaño máximo de 64 KB. - -### Agregar secretos para un repositorio - -Para crear secretos para un repositorio de la organización, debes tener acceso adminsitrativo. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Navega hacia la parte inferior de la página y, debajo de **Secretos**, selecciona **Codespaces**. ![Opción de codespaces in la barra lateral](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. En la parte superior de la página, haz clci en **Secreto de repositorio nuevo**. -1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. -1. Ingresa el valor de tu secreto. -1. Haz clic en **Agregar secreto** (Agregar secreto). - -### Agregar secretos para una organización - -Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos. - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Navega hacia la parte inferior de la página y, debajo de **Secretos**, selecciona **Codespaces**. ![Opción de codespaces in la barra lateral](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. En la parte superior de la página, haz clic en **Nuego secreto de organización**. -1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. -1. Ingresa el **Valor** para tu secreto. -1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. ![Lista de acceso a los repositorios con los repositorios privados seleccionados](/assets/images/help/codespaces/secret-repository-access.png) -1. Haz clic en **Agregar secreto** (Agregar secreto). - -### Revisar el acceso a los secretos de nivel organizacional - -Puedes revisar qué políticas de acceso se aplican a un secreto en tu organización. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: ![Lista de secretos](/assets/images/help/settings/actions-org-secrets-list.png) -1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**. diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index 13e9c83c31..0000000000 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Administrar los permisos de usuario para tu organización -intro: 'Puedes controlar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de los permisos de usuario para {% data variables.product.prodname_codespaces %} - -Los propietarios de organización pueden controlar qué usuarios de tu organización pueden crear y utilizar codespaces. - -Para utilizar codespaces en tu organización, tus usuarios deben tener por lo menos acceso de escritura en los repositorios en donde quieren utilizarlos. Puedes habilitar los codespaces para todos los usuarios en tu organización o solo para algunos específicos. - -Predeterminadamente, un codespace solo puede acceer al repositorio en donde se creó. Si quieres que los codespaces de tu organización puedan acceder a otros repositorios de organización a los que puede acceder el creador de dichos codespaces, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". - -### Configurar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Debajo de "Permisos de usuario", selecciona una de las siguientes opciones: - - * **Inhabilitado** para no permitir que los miembros de la organización utilicen {% data variables.product.prodname_codespaces %}. - * **Permitir para todos los usuarios** para permitir que todos los miembros de tu organización utilicen los {% data variables.product.prodname_codespaces %}. - * **Usuarios selectos** para seleccionar miembros específicos de la organización que puedan utilizar {% data variables.product.prodname_codespaces %}. - - ![Botones radiales de "Permisos de usuario"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index 502a2f8262..0000000000 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Revisar las bitácoras de auditoría de tu organización para los codespaces -shortTitle: Revisar las bitácoras de auditoría de tu organización -intro: 'Puedes utilizar la bitácora de auditoría para revisar todas las acciones relacionadas con los {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -Cuando algún miembro de tu organización lleva a cabo una acción relacionada con los {% data variables.product.prodname_codespaces %}, puedes revisar las acciones en la bitácora de auditoría. Para obtener más información sobre cómo acceder a la bitácora, consulta la sección "[Revisar tu bitácora de auditoría](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)". - -![Bitácora de auditoría con información de los codespaces](/assets/images/help/settings/codespaces-audit-log-org.png) - -La bitácora de auditoría incluye detalles tales como quién realizó la acción, qué fue esa acción y cuándo se llevó a cabo. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)". diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 15e85b7fb6..0000000000 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar tus codespaces -intro: 'Puedes utilizar los ajustes de {% data variables.product.prodname_github_codespaces %} para administrar la información que pudiera necesitar tu codespace.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 3008eab46f..0000000000 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar el acceso y la seguridad de tus codespaces -intro: 'Puedes administrar los repositorios a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Cuando habilitas el acceso y la seguridad de un repositorio que pertenezca a tu cuenta de usuario, cualquier codespace que se cree para este tendrá permisos de escritura en el resto de los repositorios que te pertenezcan. Si quieres restringir los repositorios a los que puede acceder un codespace, puedes limitarlos a ya sea el repositorio para el cual se abrió el codespace o a repositorios específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Debajo de "Acceso y seguridad"; selecciona la configuración que quieras para tu cuenta de usurio. ![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. Si eliges "Repositorios seleccionados", selecciona el menú desplegable y luego da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que te pertenecen. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de tus repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index 38cda61c72..0000000000 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Administrar secretos cifrados para tus codespaces -intro: 'Puedes almacenar información sensible, como los tokens, a la cual quieras acceder en tus codespaces en forma de variables de ambiente.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### Acerca de los secretos cifrados para los {% data variables.product.prodname_codespaces %} - -Puedes agregar a tu cuenta de usuario los secretos cifrados que quieras utilizar en tus codespaces. Por ejemplo, puede que quieras almacenar y acceder a la siguiente información sensible en forma de un secreto cifrado. - -- Tokens de acceso personal para los servicios en la nube -- Entidades de servicio -- Identificadores de suscripción -- [Credenciales para un registro de imagen privada](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -Puedes elegir qué repositorios deben tener acceso a cada secreto. Posteriormente, puedes utilizar el secreto en cualquier codespace que crees para un repositorio que tenga acceso a él. - -{% data reusables.codespaces.secrets-on-start %} - -#### Nombrar secretos - -{% data reusables.codespaces.secrets-naming %} Por ejemplo, un secreto que se crea a nivel de repositorio debe tener un nombre único en este. - - {% data reusables.codespaces.secret-precedence %} - -#### Límites para los secretos - -Puedes almacenar hasta 100 secretos para los {% data variables.product.prodname_codespaces %}. - -Los secretos tienen un tamaño máximo de 64 KB. - -### Agregar un secreto - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. A la derecha de "Secretos de los codespaces", da clic en **Secreto nuevo**. ![Botón de "Secreto nuevo"](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Debajo de "Nombre", teclea un nombre para tu secreto. ![Caja de texto de "Nombre"](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Haz clic en **Agregar secreto** (Agregar secreto). - -### Editar un secreto - -Puedes actualizar el valor de un secreto existente y puedes cambiar qué repositorios pueden acceder a un secreto. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Debajo de "Secretos de los codespaces"; a la derecha del secreto que quieras editar, da clic en **Actualizar**. ![Botón de "Actualizar"](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Debajo de "Valor", da clic en **Ingresar un valor nuevo**. ![Enlace de "Ingresar un valor nuevo"](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Opcionalmente, para eliminar el acceso del secreto a un repositorio, deselecciona el repositorio. ![Casillas de verificación para eliminar el acceso a los repositorios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Haz clic en **Guardar cambios**. - -### Borrar un secreto - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Debajo de "Secretos de los codespaces", a la derecha del secreto que quieras borrar, da clic en **Borrar**. ![Botón de "Borrar"](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Lee la advertencia y da clic en **OK**. ![Confirmación para borrar un secreto](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index 53853f7633..0000000000 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Administrar la verificación de GPG para los Codespaces -intro: 'Puedes permitir que {% data variables.product.company_short %} utilice automáticamente GPG para firmar las confirmaciones que haces en tus codespaces para que otras personas puedan tener la confianza de que los cambios vienen de una fuente confiable.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Después de que habilitas la verificación de GPG, {% data variables.product.company_short %} firmará automáticamente las confirmaciones que hagas en los {% data variables.product.prodname_codespaces %} y éstas tendrán un estado de verificado en {% data variables.product.product_name %}. Predeterminadamente, la verificación GPG se encuentra inhabilitada para los codespaces que creas. Puedes elegir permitir la verificación de GPG para todos los repositorios o para repositorios específicos. Habilita la verificación GPG únicamente para los repositorios en los cuales confías. Para obtener más información acerca de las confirmaciones firmadas por {% data variables.product.product_name %}, consulta la sección "[Acerca de la verificación de firmas de las confirmaciones](/github/authenticating-to-github/about-commit-signature-verification)". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Debajo de "verificación GPG", selecciona la configuración que quieras para la verificación de GPG. ![Botones radiales para administrar la verificación GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. Si eliges "Repositorios seleccionados"; selecciona el menú desplegable y luego da clic en el repositorio para el cual quieras habilitar la verificación de GPG. Repite esto para todos los repositorios en los cuales quieras habilitar la verificación GPG. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index 6fd4b55253..0000000000 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Revisar las bitácoras de seguridad de los Codespaces -shortTitle: Revisar tus bitácoras de seguridad -intro: 'Puedes utilizar la bitácora de seguridad para revisar todas las acciones relacionadas con los {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de las bitácoras de seguridad para los {% data variables.product.prodname_codespaces %} - -Cuando realizas una acción relacionada con {% data variables.product.prodname_codespaces %} en los repositorios que le pertenecen a tu cuenta de usuario, puedes revisar las acciones en la bitácora de seguridad. Para obtener más información sobre acceder a la bitácora, consulta la sección "[Revisar tu bitácora de seguridad](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)". - -![bitácora de seguridad con información sobre los codespaces](/assets/images/help/settings/codespaces-audit-log.png) - -La bitácora de seguridad incluye detalles de qué acción ocurrió y cuándo la realizaste. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/es-ES/content/codespaces/quickstart.md b/translations/es-ES/content/codespaces/quickstart.md deleted file mode 100644 index e52bbb80ef..0000000000 --- a/translations/es-ES/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Guía de inicio rápido para los Codespaces de GitHub -intro: 'Prueba los {% data variables.product.prodname_codespaces %} en 5 minutos o menos.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### Introducción - -En esta guía, crearás un codespace desde el [repositorio de muestra](https://github.com/2percentsilk/haikus-for-codespaces) y explorarás algunas de las características esenciales disponibles para ti dentro del codespace. - -El siguiente ejemplo muestra cómo crear un codespace, conectarlo a un puerto reenviado para ver tu aplicación en ejecución y personalizar tu configuración con extensiones adicionales y dotfiles. - -### Crea tu codespace - -1. Navega a la página principal del [repositorio de muestra](https://github.com/2percentsilk/haikus-for-codespaces). - -2. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**. - - ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. Para crear un codespace, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. - - ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - -### Ejecuta la aplicación - -Con tu proyecto abierto en un codespace, ahora puedes ejecutar la aplicación y lanzarla en un buscador. - -1. Inicia la aplicación ingresando `npm run dev` en la terminal. Este comando ejecuta el script `dev` en el archivo package.json e inicia la aplicación web que se define en el repositorio de muestra. - - ![npm run dev en la temrinal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. Cuando tu proyecto inicia, debes ver una alerta en la esquina inferior derecha con un mensaje para conectarte al puerto que utiliza tu proyecto. - - ![Notificación de reenvío de puertos](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Haz clic en **Abrir en el buscador** para ver tu aplicación que se está ejecutando en una pestaña nueva. - -### Personalización con una extensión de tema - -Dentro de un codespace, tienes acceso al Visual Studio Code Marketplace. En este ejemplo, instalarás una extensión que alterará el tema, pero puedes instalar cualquier extensión que sea útil para tu flujo de trabajo. - -1. En la barra lateral, haz clic en el icono de extensiones. - -2. En la barra de búsqueda, ingresa `fairyfloss` e instala la extensión de fairyfloss. - - ![Agregar una extensión](/assets/images/help/codespaces/add-extension.png) - -3. Selecciona el tema `fairyfloss` seleccionándolo de la lista. - - ![Seleccionar el tema de fairyfloss](/assets/images/help/codespaces/fairyfloss.png) - -4. Los cambios que hagas a tu configuración de editor en el codespace actual, tales como el tema y los enlaces de teclado, se sincronizarán automáticamente a otros codespaces a través de la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalización con dotfiles - -Si tu cuenta de usuario de GitHub es propietaria de un repositorio público denominado dotfiles, GitHub lo utilizará automáticamente para personalizar tu ambiente de codespace durante su creación. - -Este ejemplo te orienta para crear un repositorio de dotfiles para tus codespaces. - -1. Navega al [repositorio de dotfiles](https://github.com/aw-test-93/dotfiles/) de muestra. - -2. Bifurca el repositorio hacia tu cuenta y asegúrate de que sea público. - - Verifica que el repositorio que creaste en tu cuenta se llame dotfiles, por ejemplo `yourname/dotfiles`. Cualquier otro nombre ocasionará que {% data variables.product.prodname_codespaces %} ignore la personalización del repositorio. - -3. El crear un codespace nuevo desde el [repositorio de aplicación de muestra](https://github.com/2percentsilk/haikus-for-codespaces) como actualizaciones de dotfile solo se aplica en el momento de la creación. Los dotfiles de ejemplo cambiarán el símbolo de sistema para que muestre texto en negritas morado y azul. - - ![Personalizar el símbolo de sistema](/assets/images/help/codespaces/custom-prompt.png) - -### Siguientes pasos - -Creaste, personalizaste y ejecutaste exitosamente tu primer aplicación dentro de un codespace, pero ¡hay mucho más que explorar! Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_codespaces %}. - - "[Guías de inicio](/codespaces/getting-started-with-codespaces)" Para utilizar {% data variables.product.prodname_codespaces %} con lenguajes específicos - - [Crear una configuración personalizada](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) para configurar {% data variables.product.prodname_codespaces %} para tu proyecto. diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index cc82c1843f..0000000000 --- a/translations/es-ES/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -title: Configurar Codespaces para tu proyecto -intro: 'Puedes utilizar un archivo de `devcontainer.json` para definir un ambiente de {% data variables.product.prodname_codespaces %} para tu repositorio.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de los contenedores dev - -Un contenedor de desarrollo o contenedor dev es el ambiente que utilizan los {% data variables.product.prodname_codespaces %} para proporcionar las herramientas y tiempos de ejecución que necesita tu proyecto para su desarrollo. Cuando trabajas con un contenedor de dev en los {% data variables.product.prodname_codespaces %}, puedes ya sea [utilizar la configuración predeterminada](#using-the-default-configuration), [utilizar una configuración predeterminada](#using-a-pre-defined-container-configuration) o [crear tu propia configuración](#creating-a-custom-codespace-configuration). La opción que elijas dependerá de las herramientas, tiempos de ejecución, dependencias y flujos de trabajo que el usuario pudiese necesitar para tener éxito en tu proyecto. - -{% data variables.product.prodname_codespaces %} permite la personalización por proyecto y por rama con un archivo `devcontainer.json`. Este archivo de configuración determina el ambiente de cada codespace nuevo que cualquier persona cree en tu repositorio definiendo un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y reenvío de puertos. También puede utilizarse un Dockerfile junto con el archivo `devcontainer.json` en la carpeta `.devcontainer` para definir todo lo que se necesita para crear una imagen de contenedor. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -Puedes utilizar tu `devcontainer.json` para configurar los ajustes predeterminados para todo el ambiente de codespaces, incluyendo el editor, pero también puedes configurar ajustes específicos del editor para [espacios de trabajo](https://code.visualstudio.com/docs/editor/workspaces) individuales de un codespace en un archivo llamado `.vscode/settings.json`. - -Para obtener más información sobre la configuración y propiedades que puedes configurar en un `devcontainer.json`, consulta la [referencia a devcontainer.json](https://aka.ms/vscode-remote/devcontainer.json) en la documentación de {% data variables.product.prodname_vscode %}. - -#### Dockerfile - -Un Dockerfile también vive en la carpeta `.devcontainer`. - -Puedes agregar un Dockerfile a tu proyecto para definir una imagen de contenedor e instalar software. En el Dockerfile, puedes utilizar `FROM` para especificar la imagen de contenedor. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -Puedes utilizar la instrucción e `RUN` para instalar cualquier software y `&&` para unir comandos. - -Referencia tu Dockerfile en tu archivo de `devcontainer.json` utilizando la propiedad `dockerfile`. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -Para obtener más información sobre cómo utilizar un Dockerfile en un contenedor de dev, consulta la sección [Crear un contenedor de desarrollo](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) en la documentación de {% data variables.product.prodname_vscode %}. - -### Utilizar la configuración predeterminada - -Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace con una imagen base de Linux. La imagen base de Linux incluye lenguajes y tiempos de ejecución como Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, y Rust. También incluye otras herramientas y utilidades de desarrollador como git, el CLI de GitHub, yarn, openssh y vim. Para ver todos los lenguajes, tiempos de ejecución y herramientas que se incluyen, utiliza el comando `devcontainer-info content-url` dentro de tu terminal del codespace y sigue la url que este produce. - -Como alternativa, para obtener más información sobre todo lo que incluye la imagen básica de Linux, consulta el archivo más reciente del repositorio [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). - -La configuración predeterminada es una buena opción si estás trabajando en un proyecto pequeño que utilice los lenguajes y herramientas que proporciona {% data variables.product.prodname_codespaces %}. - - -### Utilizar una configuración de contenedor predefinida - -Las definiciones predefinidas de contenedores incluyen una configuración común para u tipo de proyecto en particular y pueden ayudarte a iniciar rápidamente con una configuración que ya tenga las opciones adecuadas del contenedor, los ajustes de {% data variables.product.prodname_vscode %} y las extensiones de {% data variables.product.prodname_vscode %} que deben estar instaladas. - -Utilizar una configuración predefinida es una gran idea si necesitas extensibilidad adicional. También puedes iniciar con una configuración predefinida y modificarla conforme lo requieras de acuerdo con los ajustes de tu proyecto. - -1. Para acceder a la paleta de comandos, en la esquina superior izquierda, selecciona el menú de aplicaciones y haz clic en **Paleta de comandos...** desde el menú de **Ver** y luego comienza a teclear "Codespaces: Add Development Container Configuration Files...". Haz clic en **Codespaces: Agregar archivos de configuración de contenedores de desarrollo...** !["Codespaces: Agregar archivos de configuración de contenedores de desarrollo..." en la paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Haz clic en la definición que quieras utilizar. ![Lista de definiciones de contenedores predefinidas](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Sigue los mensajes para personalizar tu definición. -1. Haz clic en **OK** (aceptar). ![Botón de OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. Para aplicar los cambios, en la esquina inferior derecha de la pantalla, haz clic en **Reconstruir ahora**. Para obtener más información sbre reconstruir tu contenedor, consulta la sección "[Acplicar los cambios a tu configuración](#applying-changes-to-your-configuration)". !["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/rebuild-prompt.png) - - -### Crear una configuración personalizada para un codespace - -Si ninguna de las configuraciones predefinidas satisface tus necesidades, puedes crear una configuración personalizada si agregas un archivo `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} - -En el archivo, puedes utilizar las [llaves de configuración compatibles](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) para especificar los aspectos del ambiente del codespace, como cuáles extensiones de {% data variables.product.prodname_vscode %} se instalarán. - -{% data reusables.codespaces.vscode-settings-order %} - -Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares. - -* La configuración del editor que se definió en `.vscode/settings.json` se aplica como una configuración con alcance de _Workspace_- en este codespace. -* La configuración del editor que se definió en la clave `settings` en `devcontainer.json` se aplica como una configuración con alcance de _Remote [Codespaces]_ en este codespace. - -Después de actualizar el archivo `devcontainer.json`, puedes reconstruir el contenedor para que tu codespace aplique los cambios. Para obtener más información, consulta la sección "[Aplicar cambios a tu configuración](#applying-changes-to-your-configuration)". - - - - -### Aplicar cambios a tu configuración - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %}!["Codespaces: Reconstruir contenedor" en la paleta de comandos](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Arreglar los errores en la configuración. ![Mensaje de error sobre el modo de recuperación](/assets/images/help/codespaces/recovery-mode-error-message.png) - - Para diagnosticar el error revisando la bitácora de creación, haz clic en **Ver bitácora de creación**. - - Para arreglar los errores que se identificaron en las bitácoras, actualiza tu archivo `devcontainer.json`. - - Para aplicar los cambios, vuelve a crear tu contenedor. {% data reusables.codespaces.rebuild-command %} diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index b78007e4ab..0000000000 --- a/translations/es-ES/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Configurar tu codespace -intro: '{% data variables.product.prodname_codespaces %} es un ambiente dedicado para ti. Puedes configurar tu codespace con un contenedor dev para instalar tus dependencias o puedes agregar un dotfile para personalizar la los ajustes de usuario.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 0572327747..0000000000 --- a/translations/es-ES/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Personalizar Codespaces para tu cuenta -intro: 'Puedes personalizar {% data variables.product.prodname_codespaces %} utilizando un repositorio de `dotfiles` en {% data variables.product.product_name %} o utilizando la sincronización de ajustes.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de personalizar los {% data variables.product.prodname_codespaces %} - -Cuando utilizas cualquier ambiente de desarrollo, personalizar las configuraciones y herramientas de acuerdo con tus preferencias y flujos de trabajo es un paso importante. {% data variables.product.prodname_codespaces %} permite dos formas principales de personalizar tus codespaces. - -- [Sincronización de ajustes](#settings-sync) - Puedes utilizar y compartir los ajustes de {% data variables.product.prodname_vscode %} entre {% data variables.product.prodname_codespaces %} y otras instancias de {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – Puedes utilizar un repositorio público de `dotfiles` para especificar scripts, preferencias de shell y otras configuraciones. - -La personalización de {% data variables.product.prodname_codespaces %} aplica a cualquier codespace que crees. - -Los mantenendores de proyecto también pueden definir una configuración predeterminada que aplique a cada codespace para un repositorio que cree alguien más. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -### Sincronización de ajustes - -La configuración de ajustes te permite compartir configuraciones tales como configuraciones, atajos de teclado, fragmentos de código, extensiones y estados de IU entre máquinas e instancias de {% data variables.product.prodname_vscode %}. - -La sincronización de ajustes está activada predeterminadamente. Para configurar cualquier ajuste, en la esquina inferior izquierda de la barra de actividad, selecciona el {% octicon "gear" aria-label="The gear icon" %} y haz clic en **La sincronización de ajustes está activa**. Desde el diálogo, puedes elegir configurar, mostrar los ajustes y datos o apagar la sincronización de ajustes. - -![La opción de sincronización de ajustes en el menú de administración](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -Para obtener más información, consulta la [Guía de sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) en la documentación de {% data variables.product.prodname_vscode %}. - -### Dotfiles - -Los Dotfiles son archivos y carpetas de sistemas parecidos a Unix que comienzan con `.` y que controlan la configuración de aplicaciones y shells de tu sistema. Puedes alamacenar y administrar tus dotfiles en un repositorio en {% data variables.product.prodname_dotcom %}. Para encontrar consejos y tutoriales sobre qué incluir en tu repositorio de `dotfiles`, consulta la sección [GitHub maneja dotfiles](https://dotfiles.github.io/). - -Si tu cuenta de usuario en {% data variables.product.prodname_dotcom %} es propietaria de un repositorio público llamado `dotfiles`, {% data variables.product.prodname_dotcom %} utilizará este repositorio automáticamente para personalizar el ambiente de tu codespace. Actualmente, no son compatibles los repositorios `dotfiles` privados. - -Tu repositorio `dotfiles` puede incluir los alias de tu shell y tus preferencias, cualquier herramienta que quieras instalar, o cualquier otra personalización del codespace que quieras hacer. - -Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} clona tu repositorio `dotfiles` hacia el ambiente del codespace, y busca uno de los siguientes archivos para configurar el ambiente. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -Si no encuentra alguno de estos archivos, entonces cualquier archivo o carpeta en `dotfiles` que comience con `.` se enlazará simbólicamente al directorio `~` o `$HOME` del codespace. - -Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada codespace nuevo, y no afectará a ningún codespace existente. - -{% note %} - -**Nota:** Actualmente, {% data variables.product.prodname_codespaces %} no es compatible con la personalización de la configuración de _Usuario_ para el editor de {% data variables.product.prodname_vscode %} con tu repositorio de `dotfiles`. Puedes configurar ajustes predeterminados de _Workspace_ y _Remote [Codespaces]_ para un proyecto específico en el repositorio de éste. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)". - -{% endnote %} - -También puedes configurar los ajustes para que tu cuenta de usuario agregue secretos cifrados, habilite la verificación de GPG y permita a tus codespaces acceder a otros repositorios. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", y "[Ad,omostrar el acceso y la seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". - -### Leer más - -* "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". diff --git a/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 6df432813b..0000000000 --- a/translations/es-ES/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} es de uso gratuito durante el beta. Cuando {% data variables.product.prodname_codespaces %} se hace generalmente disponible, se te cobrará por el almacenamiento y uso del procesamiento. diff --git a/translations/es-ES/data/reusables/codespaces/about-configuration.md b/translations/es-ES/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 3ceca47b26..0000000000 --- a/translations/es-ES/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear una configuración predeterminada de codespaces para tu repositorio, la cual determine el ambiente de cada codespace nuevo que alguien cree para este repositorio. La configuración define un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y redireccionamiento de puertos. diff --git a/translations/es-ES/data/reusables/codespaces/about-personalization.md b/translations/es-ES/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index ac99999c8c..0000000000 --- a/translations/es-ES/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -También puedes utilizar un repositorio de [dotfiles](https://dotfiles.github.io/tutorials/) y [Sincronizar la configuración](https://code.visualstudio.com/docs/editor/settings-sync) para personalizar los aspectos del ambiente de codespaces para cualquier codespace que crees. La personalización puede incluir preferencias de shell y herramientas adicionales. diff --git a/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md b/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index b010026461..0000000000 --- a/translations/es-ES/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -Puedes reenviar los puertos en tu codespace para probar y depurar tu aplicación. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 8ea4f5ec25..0000000000 --- a/translations/es-ES/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -Después de que cambia la configuración de los {% data variables.product.prodname_codespaces %} para un repositorio, puedes aplicar los cambios a un codespace existente si vuelves a compilar el contenedor para el codespace. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md b/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 2181e82fea..0000000000 --- a/translations/es-ES/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -Durante el beta, la funcionalidad será limitada. -- {% data reusables.codespaces.use-chrome %} -- Úicamente estará disponible un tamaño único de codespace. -- Únicamente serán compatibles los contenedores Linux. -- Un codespace no se puede reanudar completamente. Los procesos que estuvieran ejecutándose al momento en el que se paró un codespace no se reiniciarán. diff --git a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index f4f8c50435..0000000000 --- a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/codespace-config-order.md b/translations/es-ES/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index bed5b60232..0000000000 --- a/translations/es-ES/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Tu personalización de `dotfiles` se aplica antes de una configuración predeterminada de codespaces de un repositorio. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index 0133ab3010..0000000000 --- a/translations/es-ES/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Cada codespace se asocia con una rama específica de un repositorio. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md b/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index f26636327f..0000000000 --- a/translations/es-ES/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Cada codespace que crees está únicamente disponible para ti. Nadie más puede trabajar en tu codespace. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md b/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index a131bcd48a..0000000000 --- a/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -Puedes ejecutar tu codespace en una selección de tres tipos de máquina remota: Básica, Estándar o Premium. Cada una de estas tiene un nivel de recursos y de facturación diferentes.{% note %} - -**Nota:**{% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -El cambiar entre tipos de máquina te proporciona la flexibilidad para elegir los recursos más adecuados para tu trabajo. Algunas tareas podrían requerir tipos de máquina diferentes: - -* **Básico** para actualizar un archivo y levantar una solicitud de cambios -* **Estándar** para editar un sitio web -* **Premium** para tareas de cálculos altos tales como análilsis de datos diff --git a/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md b/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 5212de0bf3..0000000000 --- a/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -Una vez que hayas hecho cambios a tu codespace, ya sea de código nuevo o de cambios de configuración, necesitarás confirmar tus cambios. El confirmar los cambios en tu repositorio garantiza que cualquiera que cree un codespace desde este repositorio tendrá la misma configuración. Esto también significa que cualquier personalización que hagas, tal como agregar extensiones de {% data variables.product.prodname_vscode %}, aparecerá para todos los usuarios. - -Para obtener más información, consulta la sección "[Utilizar el control de código fuente en tu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)" \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index d74e19de2e..0000000000 --- a/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de dos codespaces durante el beta público limitado. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. diff --git a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index 363dffdd70..0000000000 --- a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección "[Utilizar codespaces en {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". diff --git a/translations/es-ES/data/reusables/codespaces/devcontainer-location.md b/translations/es-ES/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index 4108e47069..0000000000 --- a/translations/es-ES/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -Este archivo puede ubicarse en la raíz del repositorio o en una carpeta que se llame `.devcontainer`. Si el archivo se ubica en la raíz del repositorio, el nombre del archivo debe comenzar con un punto: `.devcontainer.json`. diff --git a/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md b/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index 639c7df307..0000000000 --- a/translations/es-ES/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de cualquier página, da clic en **Codespaces**. ![Enlace de {% data variables.product.prodname_codespaces %} en el encabezado](/assets/images/help/codespaces/header-link.png) diff --git a/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index 4203c5929f..0000000000 --- a/translations/es-ES/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu codespace, debajo del editor de texto, haz clic en "Puertos". ![Pestaña de puertos](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/es-ES/data/reusables/codespaces/rebuild-command.md b/translations/es-ES/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index 4c2882e4f1..0000000000 --- a/translations/es-ES/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -Accede a la paleta de comandos (`shift command P` / `shift control P`) y luego comienza a teclare "Codespaces: Rebuild Container". Haz clic en **Codespaces: Rebuild Container**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/recovery-mode.md b/translations/es-ES/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index 0059dc812e..0000000000 --- a/translations/es-ES/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -Si los cambios a la configuración de tu codespace causan un error de contenedor, este se ejecutará en modo de recuperación y verás un mensaje de error. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/release-stage.md b/translations/es-ES/data/reusables/codespaces/release-stage.md deleted file mode 100644 index f03425ab0c..0000000000 --- a/translations/es-ES/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". - -{% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/secret-precedence.md b/translations/es-ES/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index 45cdc14d0e..0000000000 --- a/translations/es-ES/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -Si un secreto con el mismo nombre existe en varios niveles, aquél en el nivel más bajo tomará presedencia. Por ejemplo, si un secreto a nivel de organización tiene el mismo nombre que un secreto a nivel de repositorio, entonces el secreto a nivel de repositorio tomará precedencia. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/secrets-naming.md b/translations/es-ES/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index 22f2c730a6..0000000000 --- a/translations/es-ES/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -Las siguientes reglas aplican a los nombres secretos: - -* Los nombres secretos solo contienen caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) o guiones bajos (`_`). No se permiten espacios. -* Los nombres secretos no deben comenzar con el prefijo `GITHUB_`. -* Los nombres secretos no deben comenzar con un número. -* Los nombres de secreto no distinguen entre mayúsculas y minúsculas. -* Los nombres secretos deben ser únicos en el nivel en el que se hayan creado. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/secrets-on-start.md b/translations/es-ES/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index d30cf9e54f..0000000000 --- a/translations/es-ES/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -Una vez que hayas creado un secreto, estará disponible cuando creas un codespace nuevo o cuando reinicias el codespace. Para utilizar un secreto que acabas de crear en un codespace actual, necesitarás suspenderlo y reanudarlo. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md b/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index f8f8cf287e..0000000000 --- a/translations/es-ES/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra de actividad, haz clic en la vista de **Control de código fuente**. ![Vista de control de código fuente](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/source-control-display.md b/translations/es-ES/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index fe78e1c886..0000000000 --- a/translations/es-ES/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. En la barra de actividad, haz clic en la vista de **Control de código fuente**. - - ![Vista de control de código fuente](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/type-port-label.md b/translations/es-ES/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index ec2eb93c12..0000000000 --- a/translations/es-ES/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea una etiqueta para tu puerto y luego presiona enter. ![Caja de texto para teclear la etiqueta para el puerto](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/unsupported-repos.md b/translations/es-ES/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index e39868b20f..0000000000 --- a/translations/es-ES/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -Durante el beta, no serán compatibles los repositorios privados que pertenezcan a las organizaciones o cualquier repositorio perteneciente a una organización que requiera el inicio de sesión único de SAML. diff --git a/translations/es-ES/data/reusables/codespaces/use-chrome.md b/translations/es-ES/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index cb55835480..0000000000 --- a/translations/es-ES/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -Para una mejor experiencia con {% data variables.product.prodname_codespaces %}, te recomenamos utilizar un buscador basado en Chromium, como Google Chrome o Microsoft Edge. diff --git a/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md b/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index 17af192cf7..0000000000 --- a/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -Puedes editar código, depurar y utilizar comandos de git mientras que desarrollas en un codespace con {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs). diff --git a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 1519e4c06f..0000000000 --- a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras los ajustes de editor para {% data variables.product.prodname_vscode %}, hay tres alcances disponibles: _Espacio de trabajo_, _[Codespaces] Remotos _, y _Usuario_. Si una configuración se define en varios alcances, los ajustes de _espacio de trabajo_ tomarán prioridad, luego los de _[Codespaces] Remotos_, y luego los de _Usuario_. diff --git a/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index 9b9097d84a..0000000000 --- a/translations/es-ES/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Puedes ver cualquier codespace disponible que hayas creado en [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index 9b01d062d6..0000000000 --- a/translations/es-ES/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. En la esquina superior derecha de {% data variables.product.product_name %}, haz clic en tu foto de perfil y luego haz clic en **Tus codespaces**. - - ![Opción de menú 'Tus codespaces'](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/gated-features/codespaces.md b/translations/es-ES/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 4a8a8cf28b..0000000000 --- a/translations/es-ES/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespaces está disponible para las cuentas de usuario que utilicen {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/organizations/click-codespaces.md b/translations/es-ES/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index 3e41713050..0000000000 --- a/translations/es-ES/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Codespaces**. ![Pestaña de "Codespaces" en la barra lateral izquierda](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index 250d772614..0000000000 --- a/translations/es-ES/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona el menú desplegable de "Acceso al repositorio" y luego da clic en aquél a cuyo secreto quieras acceder. Repite esto para cada repositorio del cual quieras tener acceso al secreto. ![Menú desplegable de "Acceso al repositorio"](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md b/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index 246e6ab228..0000000000 --- a/translations/es-ES/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Valor", teclea el valor de tu secreto. ![Caja de texto de "Valor"](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md b/translations/es-ES/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index 69002607f8..0000000000 --- a/translations/es-ES/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Codespaces**. ![Pestaña de Codespaces en la barra lateral de la configuración de usuario](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/about-configuration.md b/translations/es-XL/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 3ceca47b26..0000000000 --- a/translations/es-XL/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear una configuración predeterminada de codespaces para tu repositorio, la cual determine el ambiente de cada codespace nuevo que alguien cree para este repositorio. La configuración define un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y redireccionamiento de puertos. diff --git a/translations/es-XL/data/reusables/codespaces/about-personalization.md b/translations/es-XL/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index af73ae7810..0000000000 --- a/translations/es-XL/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -También puedes personalizar los aspectos del ambiente de un codespace para cad acodespace que tu cuenta cree. La personalización puede incluir preferencias de shell y herramientas adicionales. diff --git a/translations/es-XL/data/reusables/codespaces/beta-functionality-limited.md b/translations/es-XL/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 2181e82fea..0000000000 --- a/translations/es-XL/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -Durante el beta, la funcionalidad será limitada. -- {% data reusables.codespaces.use-chrome %} -- Úicamente estará disponible un tamaño único de codespace. -- Únicamente serán compatibles los contenedores Linux. -- Un codespace no se puede reanudar completamente. Los procesos que estuvieran ejecutándose al momento en el que se paró un codespace no se reiniciarán. diff --git a/translations/es-XL/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/es-XL/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index f4f8c50435..0000000000 --- a/translations/es-XL/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/codespace-config-order.md b/translations/es-XL/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index bed5b60232..0000000000 --- a/translations/es-XL/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Tu personalización de `dotfiles` se aplica antes de una configuración predeterminada de codespaces de un repositorio. diff --git a/translations/es-XL/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/es-XL/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index d77b4cdcd1..0000000000 --- a/translations/es-XL/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Cada codespace se asocia con una rama específica de un repositorio. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/codespaces-are-personal.md b/translations/es-XL/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 6e45142a3c..0000000000 --- a/translations/es-XL/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Cada codespace que crees está únicamente disponible para ti. Nadie más puede trabajar en tu codespace. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/es-XL/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index d74e19de2e..0000000000 --- a/translations/es-XL/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de dos codespaces durante el beta público limitado. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. diff --git a/translations/es-XL/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/es-XL/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index c81fa5c6bf..0000000000 --- a/translations/es-XL/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección "[Conectarte a tu codespace desde {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/navigate-to-codespaces.md b/translations/es-XL/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index 32549a2737..0000000000 --- a/translations/es-XL/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de cualquier página, da clic en **Codespaces**. ![Enlace de {% data variables.product.prodname_codespaces %} en el encabezado](/assets/images/help/codespaces/header-link.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/release-stage.md b/translations/es-XL/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 3e5bd7ee69..0000000000 --- a/translations/es-XL/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. Par obtener más información acerca de unirse al beta, consulta "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". - -{% endnote %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/unsupported-repos.md b/translations/es-XL/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index 771da183c1..0000000000 --- a/translations/es-XL/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -Durante el beta, no serán compatibles los repositorios privados que pertenezcan a las organizaciones o cualquier repositorio perteneciente a una organización que requiera el inicio de sesión único de SAML. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/codespaces/use-chrome.md b/translations/es-XL/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index cb55835480..0000000000 --- a/translations/es-XL/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -Para una mejor experiencia con {% data variables.product.prodname_codespaces %}, te recomenamos utilizar un buscador basado en Chromium, como Google Chrome o Microsoft Edge. diff --git a/translations/es-XL/data/reusables/codespaces/use-visual-studio-features.md b/translations/es-XL/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index 87d2140753..0000000000 --- a/translations/es-XL/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -Después de que abras un codespace, puedes desarrollar utilizando las características de {% data variables.product.prodname_vscode %} tales como edición de texto, depuración, y comandos de Git. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs). diff --git a/translations/es-XL/data/reusables/codespaces/vscode-settings-order.md b/translations/es-XL/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 1519e4c06f..0000000000 --- a/translations/es-XL/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras los ajustes de editor para {% data variables.product.prodname_vscode %}, hay tres alcances disponibles: _Espacio de trabajo_, _[Codespaces] Remotos _, y _Usuario_. Si una configuración se define en varios alcances, los ajustes de _espacio de trabajo_ tomarán prioridad, luego los de _[Codespaces] Remotos_, y luego los de _Usuario_. diff --git a/translations/es-XL/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/es-XL/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index 6dfb46c028..0000000000 --- a/translations/es-XL/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Puedes ver cada codespace que pertenezca a tu cuenta de usuario en [github.com/codespaces](https://github.com/codespaces). \ No newline at end of file diff --git a/translations/es-XL/data/reusables/gated-features/codespaces.md b/translations/es-XL/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 4a8a8cf28b..0000000000 --- a/translations/es-XL/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespaces está disponible para las cuentas de usuario que utilicen {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ja-JP/content/codespaces/about-codespaces.md b/translations/ja-JP/content/codespaces/about-codespaces.md deleted file mode 100644 index 6aa9285b62..0000000000 --- a/translations/ja-JP/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: codespace について -intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### {% data variables.product.prodname_codespaces %} について - -{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -![codespace（オープン）](/assets/images/help/codespaces/codespace-overview.png) - -A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings. - -Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development. - -### A consistent environment - -You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。 - -For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials. - -While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -### Fast and personal onboarding - -With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**. - -![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature. - -Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - -Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs. - -### A secure environment - -{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. 開発者は、タブレットや Chromebook など、あらゆるマシンでどこからでも貢献でき、知的財産のローカルコピーを保持する必要はありません。 Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`. - -Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### {% data variables.product.prodname_codespaces %}の支払いについて - -{% data reusables.codespaces.about-billing-for-codespaces %} 詳細は「[{% data variables.product.prodname_codespaces %} の支払いについて](/github/developing-online-with-codespaces/about-billing-for-codespaces)」を参照してください。 - -### ベータに参加する - -限られたユーザのみがベータ参加のために招待されます。 To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### {% data variables.product.prodname_codespaces %} について問い合わせる - -{% data variables.product.prodname_codespaces %} の使用時に問題が発生した場合は、「[codespace のトラブルシューティング](/github/developing-online-with-codespaces/troubleshooting-your-codespace)」を参照してください。 - -さらにサポートをご希望の場合、または {% data variables.product.prodname_codespaces %} に関するフィードバックがある場合は、[Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) ディスカッションをご利用ください。 diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index db47ed9a9c..0000000000 --- a/translations/ja-JP/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Codespaces の支払いについて -intro: '{% data variables.product.prodname_codespaces %} が一般提供されると、ストレージとコンピューティングの使用量に対して課金されます。' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -Updates on the billing model for Codespaces will be shared in an upcoming announcement. diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index 75be9e6f73..0000000000 --- a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Allowing your codespace to access a private image registry -intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry. - -When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)." - -For example, if you had a private image registry in Azure, you could create the following secrets: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/index.md b/translations/ja-JP/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index c03d45ed2f..0000000000 --- a/translations/ja-JP/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: リファレンス -intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index d3c63a0817..0000000000 --- a/translations/ja-JP/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: codespace のトラブルシューティング -intro: Use this guide to help you troubleshoot common issues with your codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Known Limitations - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### {% data variables.product.prodname_vscode %} troubleshooting - -Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience. - - -### Configuration troubleshooting - -{% data reusables.codespaces.recovery-mode %} - -``` -This codespace is currently running in recovery mode due to a container error. -``` - -Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)」を参照してください。 - -### dotfiles troubleshooting - -- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles. -- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned. - - If your dotfiles were cloned, try manually re-running your install script to verify it's executable. - - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**. - - -### Browser troubleshooting - -Chromium ベースではないブラウザを使用しているときに問題が発生した場合は、Chromium ベースのブラウザに切り替えるか、または、[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) や [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari) などのブラウザのラベルが付いた問題を検索して、`microsoft/vscode` リポジトリでブラウザの既知の問題を確認します。 - -Chromium ベースのブラウザの使用中に問題が発生した場合は、[`microsoft/vscode`](https://github.com/microsoft/vscode/issues) リポジトリの {% data variables.product.prodname_vscode %} で別の既知の問題が発生しているかどうかを確認できます。 - -### Container storage troubleshooting - -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 any of the following items to free up storage space. - -- Remove packages that are no longer by using `sudo apt autoremove` -- Clean the apt cache by using `sudo apt clean` -- Delete unneeded files like build artifacts and logs (these are very project-dependent) -- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10` - -More destructive options: -- 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` - -### 弊社にお問い合わせください - -さらなるサポートが必要な場合は、お問い合わせください。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)」を参照してください。 diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 6b755d6c3a..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: codespace を作成する -intro: リポジトリのブランチの codespace を作成して、オンラインで開発できます。 -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### codespace の作成について - -You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)." - - -When you create a codespace, a number of steps happen to enable full access to your development environment. - -- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches. -- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created. -- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository. -- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。 -- Your Docker container, `docker-compose`, or other initialization is run. -- At this point, the codespace is marked as available and you can connect. -- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up. - - The codespace shares ports added in the `devcontainer.json` file. - - The codespace runs anything specified in `postCreateCommand`. - - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - - Finally, the codespace does a full clone of the repo so you have full access to it. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### codespace を作成する - -{% data reusables.repositories.navigate-to-repo %} -2. リポジトリ名の下で、[Branch] ドロップダウンメニューを使用して、codespace を作成するブランチを選択します。 - - ![[Branch] ドロップダウンメニュー](/assets/images/help/codespaces/branch-drop-down.png) - -3. リポジトリ名の下で、{% octicon "download" aria-label="The download icon" %} [**Code**] ドロップダウンメニューを使用して、[**Open with Codespaces**] を選択します。 - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index e0d10bc664..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: codespace を削除する -intro: 不要になった codespace を削除することができます。 -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png) - - Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces). - -2. 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** ![削除ボタン](/assets/images/help/codespaces/delete-codespace.png) - -### {% data variables.product.prodname_vscode %} で Codespaces を削除する - -For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)." diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index 578df95279..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: codespace で開発する -intro: '{% data variables.product.product_name %} で codespace を開き、{% data variables.product.prodname_vscode %} の機能を使用して開発できます。' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About development with {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Side Bar - By default, this area shows your project files in the Explorer. -2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them. -3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it. -4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. -5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. - -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} 詳しい情報については、「[codespace のトラブルシューティング](/github/developing-online-with-codespaces/troubleshooting-your-codespace)」を参照してください。 - -#### Personalizing your codespace - -{% data reusables.codespaces.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)」を参照してください。 - -{% data reusables.codespaces.apply-devcontainer-changes %}詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)」を参照してください。 - -#### Running your app from a codespace -{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)." - -#### Committing your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Navigating to an existing codespace - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. 開発する codespace の名前をクリックします。 ![codespace の名前](/assets/images/help/codespaces/click-name-codespace.png) - -Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 31d6915005..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Forwarding ports in your codespace -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About forwarded ports - -ポート転送を使用すると、Codespaces 内で実行されている TCP ポートにアクセスできます。 For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application. - -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. たとえば、アプリケーションが `http://127.0.0.1:4000` または `http://localhost:4000` をコンソールに出力する場合、ログは出力をポート 4000 のクリック可能な URL に自動的に変換します。 - -![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) - -You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration. - -### Forwarding a port - -You can manually forward a port that wasn't forwarded automatically. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) - -### Labeling a port - -You can label a port to make the port more easily identifiable in a list. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Sharing a port - -If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) -1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Send the copied URL to the person you want to share the port with. - -### Adding a port to the codespace configuration - -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)」を参照してください。 - -You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index fb2c11562a..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: codespace で開発する -intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index ba5c1d5918..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Visual Studio Code で Codespaces を使用する -intro: '{% data variables.product.product_name %} のアカウントに {% data variables.product.prodname_github_codespaces %} 機能拡張を接続することにより、{% data variables.product.prodname_vscode %} で codespace を直接開発できます。' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 必要な環境 - -{% data variables.product.prodname_vscode %} の Codespaces で直接開発するには、{% data variables.product.prodname_github_codespaces %} 機能拡張にサインインする必要があります。 {% data variables.product.prodname_github_codespaces %} 機能拡張には、{% data variables.product.prodname_vscode %} October 2020 Release 1.51 以降が必要です。 - -{% data variables.product.prodname_vs %} Marketplace を使用して、[{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 機能拡張をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。 - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. [**Sign in to view {% data variables.product.prodname_dotcom %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。 -4. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。 - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. [REMOTE EXPLORER] ドロップダウンを使用して、[**{% data variables.product.prodname_github_codespaces %}**] をクリックします。 ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. [**Sign in to view {% data variables.product.prodname_codespaces %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。 -5. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。 - -{% endwindows %} - -### {% data variables.product.prodname_vscode %} で Codespaces を作成する - -{% data variables.product.product_name %} アカウントを {% data variables.product.prodname_github_codespaces %} 機能拡張に接続した後、{% data variables.product.product_name %} または {% data variables.product.prodname_vscode %} で作成した Codespaces で開発できます。 - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. [Add] アイコンをクリックしてから、[**Create New Codespace**] をクリックします。 ![{% data variables.product.prodname_codespaces %} の [Create New Codespace] オプション](/assets/images/help/codespaces/create-codespace-vscode.png) -3. 入力し、開発するリポジトリの名前をクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのリポジトリを検索する](/assets/images/help/codespaces/choose-repository-vscode.png) -4. 開発するブランチをクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the machine type you want to develop in. ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png) -### {% data variables.product.prodname_vscode %} で codespace を開く - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. [Codespaces] で、開発するコードスペースをクリックします。 -3. [Connect to Codespace] アイコンをクリックします。 ![{% data variables.product.prodname_vscode %} の [Connect to Codespace] アイコン](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Changing the machine type in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -You can change the machine type of your codespace at any time. - -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). -2. Search for and select "Codespaces: Change Machine Type." ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Click the codespace that you want to change. ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Choose the machine type you want to use. ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. - -### {% data variables.product.prodname_vscode %} で Codespaces を削除する - -1. [Codespaces] で、削除するコードスペースを右クリックします。 -2. ドロップダウンメニューで、[**Delete Codespace**] をクリックします。 ![{% data variables.product.prodname_dotcom %} で Codespaces を削除する](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index b6603ff12a..0000000000 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -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. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About source control in {% data variables.product.prodname_codespaces %} - -You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the 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. - -Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." - -A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: - -* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -* In your codespace, create a new branch to work on. -* Make your changes and save them. -* Commit the change. -* Raise a pull request. - -### Creating or switching branches - -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace. - -{% endtip %} - -### Pulling changes from the remote repository - -You can pull changes from the remote repository into your codespace at any time. - -{% data reusables.codespaces.source-control-display-dark %} -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. In the drop-down menu, click **Pull**. - -If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -### Setting your codespace to automatically fetch new changes - -You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes. - -If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy. - -1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png) -1. In the menu, slick **Settings**. -1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png) -1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png) -1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**. - -### Committing your changes - -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Raising a pull request - -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. ** Create（作成）**をクリックしてください。 - -### Pushing changes to your remote repository - -You can push the changes you've made. 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 %}. - -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. In the drop-down menu, click **Push**. diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index 05f3bb6766..0000000000 --- a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Getting started with your C# (.NET) project in Codespaces -shortTitle: Getting started with your C# (.NET) project -allowTitleToDifferFromFilename: true -intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### はじめに - -This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 必要な環境 - -- 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_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - -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. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 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. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - You can name our dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - - **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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed. - - ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application. - -1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 次のステップ - -You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 4daa52e258..0000000000 --- a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Getting started with your Java project in Codespaces -shortTitle: Getting started with your Java project -intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### はじめに - -This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 必要な環境 - -- You should have an existing Java 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/microsoft/vscode-remote-try-java -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - -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 Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm. - -1. Run your application by pressing `F5`. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 次のステップ - -You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 2ef0866b92..0000000000 --- a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Getting started with your Node.js project in Codespaces -shortTitle: Getting started with your Node.js project -intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### はじめに - -This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 必要な環境 - -- You should have an existing JavaScript, Node.js, or TypeScript 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/microsoft/vscode-remote-try-node -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Node.js**. If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm. - -1. Run your start command in the terminal with`npm start`. - - ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 次のステップ - -You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index 76e42cb726..0000000000 --- a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Getting started with your Python project in Codespaces -shortTitle: Getting started with your Python project -intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### はじめに - -This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 必要な環境 - -- You should have an existing Python 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/python-quickstart. -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // 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` is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **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-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), 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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". **Codespaces: Rebuild Container**をクリックしてください。 - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed. - - ![Extensions list](/assets/images/help/codespaces/python-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application. - -1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 次のステップ - -You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md b/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index 396851c0bb..0000000000 --- a/translations/ja-JP/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Getting Started with {% data variables.product.prodname_codespaces %}' -intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md deleted file mode 100644 index 8a154aebe1..0000000000 --- a/translations/ja-JP/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Codespaces guides -shortTitle: ガイド -intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/ja-JP/content/codespaces/index.md b/translations/ja-JP/content/codespaces/index.md deleted file mode 100644 index d7c9926f2c..0000000000 --- a/translations/ja-JP/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: GitHub Codespaces Documentation -beta_product: true -shortTitle: GitHub Codespaces -intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index 7d7055b862..0000000000 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Managing Codespaces for your organization -intro: 'You can manange and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index 4e31f7fa17..0000000000 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Managing access and security for your organization's codespaces -shortTitle: Managing access and security for your organization -intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Organization owners can manage which repositories a codespace can access. - -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. 信頼するリポジトリに対してのみ、アクセスとセキュリティを有効にしてください。 - -To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. [Access and security] で、あなたの Organization の設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの Organization が所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 その他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index aac26610da..0000000000 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Managing encrypted secrets for your repository and organization for Codespaces -shortTitle: Managing secrets for your repository and organization -intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About secrets - -Secrets are encrypted environment variables that you create in an organization or repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace. - -Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. - - {% data reusables.codespaces.secret-precedence %} - -#### シークレットの制限 - -You can store up to 100 secrets per organization and 100 secrets per repository. - -シークレットの容量は最大64 KBです。 - -### Adding secrets for a repository - -To create secrets for an organization repository, you must have administrator access. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. At the top of the page, click **New repository secret**. -1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 -1. シークレットの値を入力します。 -1. [**Add secret（シークレットの追加）**] をクリックします。 - -### Adding secrets for an organization - -Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. At the top of the page, click **New organization secret**. -1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 -1. シークレットの **Value（値）** を入力します。 -1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png) -1. [**Add secret（シークレットの追加）**] をクリックします。 - -### Organizationレベルのシークレットへのアクセスの確認 - -You can check which access policies are applied to a secret in your organization. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: ![シークレットリスト](/assets/images/help/settings/actions-org-secrets-list.png) -1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。 diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index fee663a78c..0000000000 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Managing user permissions for your organization -intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### About user permissions for {% data variables.product.prodname_codespaces %} - -Organization owners can control which users in your organization can create and use codespaces. - -To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users. - -By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select one of the following options: - - * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}. - * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}. - * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}. - - ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index c438a70311..0000000000 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Reviewing your organization's audit logs for Codespaces -shortTitle: Reviewing your organization's audit logs -intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)." - -![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) - -The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 142e6c292d..0000000000 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing your codespaces -intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 8717f53157..0000000000 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing access and security for your codespaces -intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. 信頼するリポジトリに対してのみ、アクセスとセキュリティを有効にしてください。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. [Access and security] で、あなたのユーザアカウントの設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 所有するその他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index 0cbfa2b388..0000000000 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Managing encrypted secrets for your codespaces -intro: 環境変数を介してコードスペースにアクセスする、トークンなどの機密情報を保存できます。 -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### {% data variables.product.prodname_codespaces %} の暗号化されたシークレットについて - -コードスペースで使用するユーザアカウントに、暗号化されたシークレットを追加できます。 たとえば、次のような機密情報を暗号化されたシークレットとして保存しアクセスするとよいでしょう。 - -- クラウドサービスへの個人アクセストークン -- サービスプリンシパル -- プラン識別子 -- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -各シークレットにアクセスできるリポジトリを選択できます。 そして、シークレットへのアクセス権があるリポジトリ用に作成した任意のコードスペースでそのシークレットを使用できます。 - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. - - {% data reusables.codespaces.secret-precedence %} - -#### シークレットの制限 - -You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}. - -シークレットの容量は最大64 KBです。 - -### シークレットを追加する - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. [Codespaces secrets] の右にある [**New secret**] をクリックします。 ![[New secret] ボタン](/assets/images/help/settings/codespaces-new-secret-button.png) -1. [Name] で、シークレットの名前を入力します。 ![[Name] テキストボックス](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. [**Add secret（シークレットの追加）**] をクリックします。 - -### シークレットを編集する - -既存のシークレットの値を更新したり、シークレットがアクセスできるリポジトリを変更したりすることができます。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. [Codespaces secrets] で、編集するシークレットの右にある [**Update**] をクリックします。 ![[Update] ボタン](/assets/images/help/settings/codespaces-secret-update-button.png) -1. [Value] にある [**enter a new value**] をクリックします。 ![[enter a new value] リンク](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. リポジトリへのシークレットのアクセス権を削除する場合は、リポジトリを選択解除します。 ![リポジトリへのアクセス権を削除するチェックボックス](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. [**Save changes**] をクリックします。 - -### シークレットを削除する - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. [Codespaces secrets] で、削除するシークレットの右にある [**Delete**] をクリックします。 ![[Delete] ボタン](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. 警告を読んで、**OK**をクリックしてください。 ![シークレットの削除の確認](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index 6702951351..0000000000 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Codespaces の GPG 検証を管理する -intro: '変更が信頼できるソースからのものであることを他の人々が確信できるよう、コードスペースで作成したコミットに GPG を自動的に使用して署名するよう {% data variables.product.company_short %} に許可できます。' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -GPG 検証を有効にすると、{% data variables.product.company_short %} は {% data variables.product.prodname_codespaces %} であなたが作成したコミットに自動的に署名し、そのコミットは {% data variables.product.product_name %} で検証済みのステータスとなります。 デフォルトでは、GPG 検証は作成されたコードスペースに対して無効になっています。 GPG 検証を、すべてのリポジトリに対して許可するか特定のリポジトリに対して許可するか選択できます。 GPG 検証は、信頼するリポジトリに対してのみ有効にしてください。 {% data variables.product.product_name %} が署名したコミットに関する詳しい情報については、「[コミット署名の検証について](/github/authenticating-to-github/about-commit-signature-verification)」を参照してください。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. [GPG verification] で、GPG 検証の設定を選択します。 ![GPG 検証を管理するラジオボタン](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、GPG 検証を有効にするリポジトリをクリックします。 GPG 検証を有効にするすべてのリポジトリについて、同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index f7e213e258..0000000000 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Reviewing your security logs for Codespaces -shortTitle: Reviewing your security logs -intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### About security logs for {% data variables.product.prodname_codespaces %} - -When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user 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)." - -![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) - -The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/ja-JP/content/codespaces/quickstart.md b/translations/ja-JP/content/codespaces/quickstart.md deleted file mode 100644 index 825bb68b93..0000000000 --- a/translations/ja-JP/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Quickstart for GitHub Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### はじめに - -In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. - -The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles. - -### Creating your codespace - -1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces). - -2. リポジトリ名の下で、{% octicon "download" aria-label="The download icon" %} [**Code**] ドロップダウンメニューを使用して、[**Open with Codespaces**] を選択します。 - - ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png) - -### Run the application - -With your project open in a codespace, you can now run the application and launch it in a browser. - -1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository. - - ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Click **Open in Browser** to view your running application in a new tab. - -### Personalize with a theme extension - -Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow. - -1. In the left sidebar, click the Extensions icon. - -2. In the search bar, enter `fairyfloss` and install the fairyfloss extension. - - ![Add an extension](/assets/images/help/codespaces/add-extension.png) - -3. Select the `fairyfloss` theme by selecting it from the list. - - ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) - -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalize with dotfiles - -If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation. - -This example guides you through creating a dotfiles repository for your codespaces. - -1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/). - -2. Fork the repository to your account and ensure it's public. - - Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization. - -3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text. - - ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png) - -### Next Steps - -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_codespaces %}. - - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages - - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project. diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index 57b5f640ad..0000000000 --- a/translations/ja-JP/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: プロジェクトの Codespace の設定 -intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About dev containers - -A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project. - -{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`. - -For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation. - -#### Dockerfile - -A Dockerfile also lives in the `.devcontainer` folder. - -You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -You can use the `RUN` instruction to install any software and `&&` to join commands. - -Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation. - -### Using the default configuration - -リポジトリで設定を定義しない場合、{% data variables.product.prodname_dotcom %} はベースの Linux イメージを使用して Codespaces を作成します。 The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs. - -Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository. - -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides. - - -### Using a predefined container configuration - -Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. - -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup. - -1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. -1. [**OK**] をクリックします。 ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png) - - -### カスタム codespace 設定を作成する - -If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} - -In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. - -{% data reusables.codespaces.vscode-settings-order %} - -2 つの場所で {% data variables.product.prodname_vscode %} のデフォルトのエディタ設定を定義できます。 - -* `.vscode/settings.json` で定義されたエディタ設定は、_Workspace_ スコープの設定として codespace に適用されます。 -* `devcontainer.json` の`設定`キーで定義されたエディタ設定は、codespace の _リモート [Codespaces]_ スコープ設定として適用されます。 - -After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." - - - - -### Applying changes to your configuration - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %} diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index f47cc82ec3..0000000000 --- a/translations/ja-JP/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Setting up your codespace -intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 2543e9f4f8..0000000000 --- a/translations/ja-JP/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: アカウントの Codespaces をパーソナライズする -intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About personalizing {% data variables.product.prodname_codespaces %} - -When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces. - -- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations. - -{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create. - -プロジェクトのメンテナは、ユーザが作成したリポジトリのすべての codespace に適用されるデフォルト設定を定義することもできます。 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)」を参照してください。 - -### Settings Sync - -Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}. - -Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync. - -![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation. - -### Dotfiles - -ドットファイルは、`.` で始まる Unix ライクなシステム上のファイルとフォルダであり、システム上のアプリケーションとシェルの設定を制御します。 ドットファイルは、{% data variables.product.prodname_dotcom %} のリポジトリに保存して管理できます。 `dotfiles` リポジトリに含める内容に関するアドバイスとチュートリアルについては、「[GitHub does dotfiles](https://dotfiles.github.io/)」をご覧ください。 - -{% data variables.product.prodname_dotcom %} のユーザアカウントが `dotfiles` というパブリックリポジトリを所有している場合、{% data variables.product.prodname_dotcom %} は自動的にこのリポジトリを使用して、codespace 環境をパーソナライズします。 プライベート `dotfiles` リポジトリは現在サポートされていません。 - -`dotfiles` リポジトリには、シェルのエイリアスと設定、インストールするツール、またはその他の codespace パーソナライゼーションを含めることができます。 - -新しいコードスペースを作成すると、{% data variables.product.prodname_dotcom %} は `dotfiles` リポジトリを codespace 環境にクローンし、次のいずれかのファイルを探して環境をセットアップします。 - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -これらのファイルがいずれも見つからない場合、`.` で始まる `dotfiles` 内のファイルまたはフォルダは、codespace の `~` または `$HOME` ディレクトリにシンボリックリンクされます。 - -`dotfiles` リポジトリへの変更は、新しい codespace ごとにのみ適用され、既存の codespace には影響しません。 - -{% note %} - -**注釈:** 現在、{% data variables.product.prodname_codespaces %} は、`dotfiles` リポジトリを使用した {% data variables.product.prodname_vscode %} エディタの_ユーザ_設定のパーソナライズをサポートしていません。 プロジェクトのリポジトリ内の特定のプロジェクトに対して、デフォルトの _ワークスペース_および_リモート [Codespaces]_ を設定できます。 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)」を参照してください。 - -{% endnote %} - -ユーザアカウントに対し、暗号化されたシークレットを追加したり、GPG 検証を有効にしたり、Codespaces が他のリポジトリアクセスできたりするように設定することもできます。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} の暗号化されたシークレットを管理する](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)」、「[{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)」、および「[{% data variables.product.prodname_codespaces %} のアクセス権限およびセキュリティを管理する](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)」を参照してください。 " - -### 参考リンク - -* 「[新しいリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)」 diff --git a/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index edfafd8e2f..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %}はベータの間、無料で利用できます。 {% data variables.product.prodname_codespaces %} が一般提供されると、ストレージとコンピューティングの使用量に対して課金されます。 diff --git a/translations/ja-JP/data/reusables/codespaces/about-configuration.md b/translations/ja-JP/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 4d7fc068b5..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -リポジトリのデフォルトのcodespace設定を作成し、そのリポジトリで作成されたすべての新しいcodespaceの環境を決定できます。 この設定は、フレームワーク、ツール、機能拡張、ポートフォワーディングを含む開発コンテナを定義します。 diff --git a/translations/ja-JP/data/reusables/codespaces/about-personalization.md b/translations/ja-JP/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index bfa56b8edc..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -[dotfiles](https://dotfiles.github.io/tutorials/)リポジトリと[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)を使用して、作成した任意のcodespace環境の様々な面をパーソナライズすることもできます。 パーソナライズには、シェルの環境設定や追加のツールが含まれます。 diff --git a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md b/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 81e2b5041c..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -アプリケーションのテストとデバッグのために、codespace中のポートをフォワードできます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 325636d0f9..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -リポジトリのための{% data variables.product.prodname_codespaces %}の設定が変更された後、codespaceのコンテナをリビルドしてその変更を既存のcodespaceに適用できます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/beta-functionality-limited.md b/translations/ja-JP/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 7a4feb947f..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -ベータの期間中、機能は制限されています。 -- {% data reusables.codespaces.use-chrome %} -- codespaceのサイズは1つだけしか利用できません。 -- Linuxコンテナのみサポートされています。 -- codespaceは完全に再開可能ではありません。 codespaceが停止された時に実行中だったプロセスは、再開されません。 diff --git a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index 4400acc1c9..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. {% data variables.product.prodname_vscode %}の左サイドバーで、 Remote Explorerのアイコンをクリックしてください。 ![{% data variables.product.prodname_vscode %}のRemote Explorerアイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/codespace-config-order.md b/translations/ja-JP/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index f751373676..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -`dotfiles`のパーソナライゼーションは、リポジトリのデフォルトのcodespace設定よりも先に適用されます。 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/ja-JP/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index 06d2a0b13e..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -各codespaceはリポジトリの特定ブランチと関連づけられます。 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-are-personal.md b/translations/ja-JP/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 3b8cd5ea26..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -各コードスペースは、作成者だけが利用できます。 他者のcodespaceで作業することはできません。 diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index cd09a0cb7c..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -codespaceは、Basic、Standard、Premiumの3種類のリモートマシンから選択して実行できます。 これらはそれぞれ、異なるレベルのリソースと支払い層を持っています。{% note %} - -**注釈:** {% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -マシンタイプを切り替えることで、作業に最も適したリソースを柔軟に選択できます。 特待のタスクでは、様々なマシンタイプが必要になることがあります。 - -* ファイルの更新とPull Requestの作成に対しては**Basic** -* Webサイトの編集に対しては**Standard** -* データ分析のような高負荷のコンピューティングタスクに対しては**Premium** diff --git a/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 737d91787e..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -新しいコードであれ、設定の変更であれ、codespaceに変更を加えたら、その変更をコミットしたくなるでしょう。 リポジトリに変更をコミットすれば、このリポジトリからcodespaceを作成する他の人が、同じ設定になることを保証できます。 これはまた、{% data variables.product.prodname_vscode %}機能拡張の追加など、あなたが行うすべてのカスタマイズが、すべてのユーザに対して現れるようになるということでもあります。 - -詳しい情報については「[codespaceでのソースコントロールの利用](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index e24bc48f26..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -リポジトリごと、さらにはブランチごとに1つ以上のcodespaceを作成できます。 しかし、限定パブリックベータの間は、ユーザアカウントごとに2つのcodespaceという制限があります。 この制限に達した場合に新しいcodespaceを作成したいなら、まずcodespaceを削除しなければなりません。 diff --git a/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index c7761ac154..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_vscode %}から直接codespaceに接続できます。 詳しい情報については「[{% data variables.product.prodname_vscode %}でのCodespacesの利用](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/codespaces/devcontainer-location.md b/translations/ja-JP/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index ca21d7fe6f..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -このファイルは、リポジトリのルートもしくは`.devcontainer`というフォルダに置くことができます。 このファイルがリポジトリのルートに置かれた場合、ファイル名は`.devcontainer.json`というようにピリオドで始まらなければなりません。 diff --git a/translations/ja-JP/data/reusables/codespaces/navigate-to-codespaces.md b/translations/ja-JP/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index 46fba2d291..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. 任意のページの上部で**Codespaces**をクリックしてください。 ![ヘッダの{% data variables.product.prodname_codespaces %}リンク](/assets/images/help/codespaces/header-link.png) diff --git a/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index f4722c8f52..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. codespaceで、テキストエディタの下で"Ports（ポート）"をクリックしてください。 ![ポートタブ](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md b/translations/ja-JP/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index 0c6f3d536b..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -コマンドパレットにアクセス（`shift command P` / `shift control P`）し、続いて"Codespaces: Rebuild Container"と入力していってください。 **Codespaces: Rebuild Container**をクリックしてください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md b/translations/ja-JP/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index c3e876cf70..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -codespaceの設定の変更でコンテナエラーが生じた場合、codespaceはリカバリモードで動作し、エラーメッセージが表示されます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/release-stage.md b/translations/ja-JP/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 304cbc403c..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータへの参加に関する詳しい情報については「[{% data variables.product.prodname_codespaces %}について](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)」を参照してください。 - -{% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md b/translations/ja-JP/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index 7494d533a1..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -複数のレベルで同じ名前のシークレットが存在する場合、低いレベルのシークレットが優先されます。 たとえば、Organization レベルのシークレット名がリポジトリレベルのシークレット名と同じ場合、リポジトリレベルのシークレット名が優先されます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/secrets-naming.md b/translations/ja-JP/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index 7edc62b31f..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -シークレットの名前には次のルールが適用されます。 - -* シークレット名には、英数字（`[a-z]`、`[A-Z]`、`[0-9]`）または下線（`_`）のみを含めることができます。 スペースは使用できません。 -* シークレット名の最初を `GITHUB_` プレフィックスにすることはできません。 -* シークレット名の最初を数字にすることはできません。 -* シークレット名は大文字と小文字を区別しません。 -* シークレット名は、作成されたレベルで一意である必要があります。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md b/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index 6c20d574b1..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -シークレットを作成すると、新しいcodespaceを作成したり、codespaceを再起動したりすれば、利用できるようになります。 現在のcodespaeで作成したばかりのシークレットを使うには、codespeceをサスペンドして再開する必要があります。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md b/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index 2a62311454..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. Activityバーで、**Source Control（ソースコントロール）**ビューをクリックしてください。 ![ソースコントロールビュー](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-display.md b/translations/ja-JP/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index 537d6acc2e..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Activityバーで、**Source Control（ソースコントロール）**ビューをクリックしてください。 - - ![ソースコントロールビュー](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/type-port-label.md b/translations/ja-JP/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 99b9f6faa7..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. ポートのラベルを入力し、Enterを押してください。 ![ポートのラベルを入力するためのテキストボックス](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/unsupported-repos.md b/translations/ja-JP/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index a7046ae35a..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -ベータの期間、Organizationが所有するプライベートリポジトリ、あるいはSAMLシングルサインオンを必要とするOrganizationが所有するリポジトリはサポートされません。 diff --git a/translations/ja-JP/data/reusables/codespaces/use-chrome.md b/translations/ja-JP/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index 46ce3acf0e..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %}での最善の体験のためには、Google ChromeあるいはMicrosoft EdgeのようなChromiumベースのブラウザを使うことをおすすめします。 diff --git a/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md b/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index 20b4c76baf..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_vscode %}でcodespace内で開発をする間に、コードを編集し、デバッグし、Gtiのコマンドを使うことができます。 詳しい情報については[{% data variables.product.prodname_vscode %}のドキュメンテーション](https://code.visualstudio.com/docs)を参照してください。 diff --git a/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md b/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index bec24daf60..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_vscode %}のエディタ設定を行う際には、_Workspace_、_Remote [Codespaces]_、_User_という3つのスコープが利用できます。 複数のスコープ内で定義された設定については、_Workspace_の設定が優先され、次が_Remote [Codespaces]_、そして_User_となります。 diff --git a/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index 4d6c6dd0bd..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -作成した利用可能なすべてのcodespaceは[github.com/codespaces](https://github.com/codespaces)で見ることができます。 diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index c2b4268878..0000000000 --- a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. {% data variables.product.product_name %}の右上で、自分のプロフィール写真をクリックし、続いて**Your codespaces（自分のcode spaces）**をクリックしてください。 - - !['自分のcodespaces'メニューオプション](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gated-features/codespaces.md b/translations/ja-JP/data/reusables/gated-features/codespaces.md deleted file mode 100644 index a7d9ed1133..0000000000 --- a/translations/ja-JP/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespacesは、{% data variables.product.prodname_free_user %}もしくは{% data variables.product.prodname_pro %}を使っているユーザアカウントで利用できます。 {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ja-JP/data/reusables/organizations/click-codespaces.md b/translations/ja-JP/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index 3c7ff3a042..0000000000 --- a/translations/ja-JP/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. 左のサイドバーで**Codespaces**をクリックしてください。 ![左のサイドバー内の"Codespaces"タブ](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index 5fbef30671..0000000000 --- a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. "Repository access（リポジトリアクセス）"ドロップダウンメニューを選択し、続いてシークレットへアクセスしたいリポジトリをクリックしてください。 シークレットにアクセスしたいすべてのリポジトリに対して繰り返してください。 !["リポジトリアクセス"ドロップダウンメニュー](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md b/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index adb80f1285..0000000000 --- a/translations/ja-JP/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. "Value（値）"の下で、シークレットの値を入力してください。 !["値"テキストボックス](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md b/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index 1c2363d30c..0000000000 --- a/translations/ja-JP/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. 左のサイドバーで**Codespaces**をクリックしてください。 ![ユーザ設定サイドバーのCodespacesタブ](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/ko-KR/content/codespaces/about-codespaces.md b/translations/ko-KR/content/codespaces/about-codespaces.md deleted file mode 100644 index b7fc37f8ef..0000000000 --- a/translations/ko-KR/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: About Codespaces -intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -![An open codespace](/assets/images/help/codespaces/codespace-overview.png) - -A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings. - -Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development. - -### A consistent environment - -You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials. - -While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -### Fast and personal onboarding - -With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**. - -![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature. - -Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - -Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs. - -### A secure environment - -{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Developers can contribute from anywhere, on any machine, including tablets or Chromebooks, and there is no need to maintain local copies of intellectual property. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`. - -Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### About billing for {% data variables.product.prodname_codespaces %} - -{% data reusables.codespaces.about-billing-for-codespaces %} For more information, see "[About billing for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)." - -### Joining the beta - -A limited number of people will be invited to join the beta. To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### Contacting us about {% data variables.product.prodname_codespaces %} - -If you encounter problems using {% data variables.product.prodname_codespaces %}, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion. diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index f621a80494..0000000000 --- a/translations/ko-KR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: About billing for Codespaces -intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -Updates on the billing model for Codespaces will be shared in an upcoming announcement. diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index 75be9e6f73..0000000000 --- a/translations/ko-KR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Allowing your codespace to access a private image registry -intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry. - -When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)." - -For example, if you had a private image registry in Azure, you could create the following secrets: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/index.md b/translations/ko-KR/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index a19771efe4..0000000000 --- a/translations/ko-KR/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Reference -intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index 2e91229596..0000000000 --- a/translations/ko-KR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Troubleshooting your codespace -intro: Use this guide to help you troubleshoot common issues with your codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Known Limitations - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### {% data variables.product.prodname_vscode %} troubleshooting - -Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience. - - -### Configuration troubleshooting - -{% data reusables.codespaces.recovery-mode %} - -``` -This codespace is currently running in recovery mode due to a container error. -``` - -Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -### dotfiles troubleshooting - -- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles. -- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned. - - If your dotfiles were cloned, try manually re-running your install script to verify it's executable. - - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**. - - -### Browser troubleshooting - -If you encounter issues while using a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). - -If you encounter issues while using a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository. - -### Container storage troubleshooting - -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 any of the following items to free up storage space. - -- Remove packages that are no longer by using `sudo apt autoremove` -- Clean the apt cache by using `sudo apt clean` -- Delete unneeded files like build artifacts and logs (these are very project-dependent) -- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10` - -More destructive options: -- 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` - -### 문의처 - -If you still need help, you can contact us. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)." diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 19fc36dfc5..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Creating a codespace -intro: You can create a codespace for a branch in a repository to develop online. -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About codespace creation - -You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)." - - -When you create a codespace, a number of steps happen to enable full access to your development environment. - -- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches. -- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created. -- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository. -- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." -- Your Docker container, `docker-compose`, or other initialization is run. -- At this point, the codespace is marked as available and you can connect. -- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up. - - The codespace shares ports added in the `devcontainer.json` file. - - The codespace runs anything specified in `postCreateCommand`. - - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - - Finally, the codespace does a full clone of the repo so you have full access to it. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Creating a codespace - -{% data reusables.repositories.navigate-to-repo %} -2. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for. - - ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png) - -3. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index e6784b3775..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Deleting a codespace -intro: You can delete a codespace you no longer need. -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png) - - Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces). - -2. 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** ![Delete button](/assets/images/help/codespaces/delete-codespace.png) - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)." diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index a3ae678e34..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Developing in a codespace -intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About development with {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Side Bar - By default, this area shows your project files in the Explorer. -2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them. -3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it. -4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. -5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. - -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -#### Personalizing your codespace - -{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)." - -{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -#### Running your app from a codespace -{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)." - -#### Committing your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Navigating to an existing codespace - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Click the name of the codespace you want to develop in. ![Name of codespace](/assets/images/help/codespaces/click-name-codespace.png) - -Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 7965bfc793..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Forwarding ports in your codespace -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About forwarded ports - -Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application. - -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000. - -![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) - -You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration. - -### Forwarding a port - -You can manually forward a port that wasn't forwarded automatically. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) - -### Labeling a port - -You can label a port to make the port more easily identifiable in a list. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Sharing a port - -If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) -1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Send the copied URL to the person you want to share the port with. - -### Adding a port to the codespace configuration - -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index 555995eabc..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Developing in a codespace -intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index f9d0fa00c3..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Using Codespaces in Visual Studio Code -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 빌드전 요구 사양 - -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. - -Use the {% data variables.product.prodname_vs %} 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 %} documentation. - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -4. Sign in to {% data variables.product.product_name %} to approve the extension. - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -5. Sign in to {% data variables.product.product_name %} to approve the extension. - -{% endwindows %} - -### Creating a codespace in {% data variables.product.prodname_vscode %} - -After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) -### Opening a codespace in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Under "Codespaces", click the codespace you want to develop in. -3. Click the Connect to Codespace icon. ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Changing the machine type in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -You can change the machine type of your codespace at any time. - -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). -2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -1. Under "Codespaces", right-click the codespace you want to delete. -2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index 1ef48ef4f9..0000000000 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -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. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About source control in {% data variables.product.prodname_codespaces %} - -You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the 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. - -Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." - -A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: - -* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -* In your codespace, create a new branch to work on. -* Make your changes and save them. -* Commit the change. -* Raise a pull request. - -### Creating or switching branches - -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace. - -{% endtip %} - -### Pulling changes from the remote repository - -You can pull changes from the remote repository into your codespace at any time. - -{% data reusables.codespaces.source-control-display-dark %} -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. In the drop-down menu, click **Pull**. - -If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -### Setting your codespace to automatically fetch new changes - -You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes. - -If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy. - -1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png) -1. In the menu, slick **Settings**. -1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png) -1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png) -1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**. - -### Committing your changes - -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Raising a pull request - -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Click **Create**. - -### Pushing changes to your remote repository - -You can push the changes you've made. 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 %}. - -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. In the drop-down menu, click **Push**. diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index 762b944b79..0000000000 --- a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Getting started with your C# (.NET) project in Codespaces -shortTitle: Getting started with your C# (.NET) project -allowTitleToDifferFromFilename: true -intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 빌드전 요구 사양 - -- 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_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 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. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - You can name our dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - - **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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed. - - ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application. - -1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 다음 단계 - -You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 2416d6abaa..0000000000 --- a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Getting started with your Java project in Codespaces -shortTitle: Getting started with your Java project -intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 빌드전 요구 사양 - -- You should have an existing Java 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/microsoft/vscode-remote-try-java -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm. - -1. Run your application by pressing `F5`. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 다음 단계 - -You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 8843fe5e05..0000000000 --- a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Getting started with your Node.js project in Codespaces -shortTitle: Getting started with your Node.js project -intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 빌드전 요구 사양 - -- You should have an existing JavaScript, Node.js, or TypeScript 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/microsoft/vscode-remote-try-node -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Node.js**. If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm. - -1. Run your start command in the terminal with`npm start`. - - ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 다음 단계 - -You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index 7af44493d7..0000000000 --- a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Getting started with your Python project in Codespaces -shortTitle: Getting started with your Python project -intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### 빌드전 요구 사양 - -- You should have an existing Python 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/python-quickstart. -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // 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` is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **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-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), 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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed. - - ![Extensions list](/assets/images/help/codespaces/python-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application. - -1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 다음 단계 - -You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md b/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index 396851c0bb..0000000000 --- a/translations/ko-KR/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Getting Started with {% data variables.product.prodname_codespaces %}' -intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/guides.md b/translations/ko-KR/content/codespaces/guides.md deleted file mode 100644 index 9a56c01990..0000000000 --- a/translations/ko-KR/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Codespaces guides -shortTitle: 안내서 -intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/ko-KR/content/codespaces/index.md b/translations/ko-KR/content/codespaces/index.md deleted file mode 100644 index d7c9926f2c..0000000000 --- a/translations/ko-KR/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: GitHub Codespaces Documentation -beta_product: true -shortTitle: GitHub Codespaces -intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index 7d7055b862..0000000000 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Managing Codespaces for your organization -intro: 'You can manange and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index f3d0f9eb29..0000000000 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Managing access and security for your organization's codespaces -shortTitle: Managing access and security for your organization -intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Organization owners can manage which repositories a codespace can access. - -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. - -To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index 7f5cb98c71..0000000000 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Managing encrypted secrets for your repository and organization for Codespaces -shortTitle: Managing secrets for your repository and organization -intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About secrets - -Secrets are encrypted environment variables that you create in an organization or repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace. - -Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. - - {% data reusables.codespaces.secret-precedence %} - -#### Limits for secrets - -You can store up to 100 secrets per organization and 100 secrets per repository. - -Secrets are limited to 64 KB in size. - -### Adding secrets for a repository - -To create secrets for an organization repository, you must have administrator access. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. At the top of the page, click **New repository secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the value for your secret. -1. Click **Add secret**. - -### Adding secrets for an organization - -When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. At the top of the page, click **New organization secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the **Value** for your secret. -1. From the **Repository access** dropdown list, choose an access policy. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png) -1. Click **Add secret**. - -### Reviewing access to organization-level secrets - -You can check which access policies are applied to a secret in your organization. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. The list of secrets includes any configured permissions and policies. 예시: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png) -1. For more details on the configured permissions for each secret, click **Update**. diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index f8c2c9ac71..0000000000 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Managing user permissions for your organization -intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}. -permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### About user permissions for {% data variables.product.prodname_codespaces %} - -Organization owners can control which users in your organization can create and use codespaces. - -To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users. - -By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select one of the following options: - - * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}. - * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}. - * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}. - - ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index c438a70311..0000000000 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Reviewing your organization's audit logs for Codespaces -shortTitle: Reviewing your organization's audit logs -intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)." - -![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) - -The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 142e6c292d..0000000000 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing your codespaces -intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 44504fbaa6..0000000000 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing access and security for your codespaces -intro: You can manage the repositories that {% data variables.product.prodname_codespaces %} can access. -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index 6ad3cdee4a..0000000000 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Managing encrypted secrets for your codespaces -intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### About encrypted secrets for {% data variables.product.prodname_codespaces %} - -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. - -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers -- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. - - {% data reusables.codespaces.secret-precedence %} - -#### Limits for secrets - -You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}. - -Secrets are limited to 64 KB in size. - -### Adding a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Click **Add secret**. - -### Editing a secret - -You can update the value of an existing secret, and you can change which repositories can access a secret. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Click **Save changes**. - -### Deleting a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index c9492f1760..0000000000 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Managing GPG verification for Codespaces -intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index f7e213e258..0000000000 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Reviewing your security logs for Codespaces -shortTitle: Reviewing your security logs -intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### About security logs for {% data variables.product.prodname_codespaces %} - -When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user 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)." - -![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) - -The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/ko-KR/content/codespaces/quickstart.md b/translations/ko-KR/content/codespaces/quickstart.md deleted file mode 100644 index aa93c46407..0000000000 --- a/translations/ko-KR/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Quickstart for GitHub Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. - -The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles. - -### Creating your codespace - -1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces). - -2. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -### Run the application - -With your project open in a codespace, you can now run the application and launch it in a browser. - -1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository. - - ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Click **Open in Browser** to view your running application in a new tab. - -### Personalize with a theme extension - -Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow. - -1. In the left sidebar, click the Extensions icon. - -2. In the search bar, enter `fairyfloss` and install the fairyfloss extension. - - ![Add an extension](/assets/images/help/codespaces/add-extension.png) - -3. Select the `fairyfloss` theme by selecting it from the list. - - ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) - -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalize with dotfiles - -If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation. - -This example guides you through creating a dotfiles repository for your codespaces. - -1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/). - -2. Fork the repository to your account and ensure it's public. - - Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization. - -3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text. - - ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png) - -### Next Steps - -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_codespaces %}. - - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages - - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project. diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index 37ebec2c4c..0000000000 --- a/translations/ko-KR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Configuring Codespaces for your project -intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About dev containers - -A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project. - -{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`. - -For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation. - -#### Dockerfile - -A Dockerfile also lives in the `.devcontainer` folder. - -You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -You can use the `RUN` instruction to install any software and `&&` to join commands. - -Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation. - -### Using the default configuration - -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs. - -Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository. - -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides. - - -### Using a predefined container configuration - -Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. - -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup. - -1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. -1. Click **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png) - - -### Creating a custom codespace configuration - -If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} - -In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. - -{% data reusables.codespaces.vscode-settings-order %} - -You can define default editor settings for {% data variables.product.prodname_vscode %} in two places. - -* Editor settings defined in `.vscode/settings.json` are applied as _Workspace_-scoped settings in the codespace. -* Editor settings defined in the `settings` key in `devcontainer.json` are applied as _Remote [Codespaces]_-scoped settings in the codespace. - -After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." - - - - -### Applying changes to your configuration - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %} diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index f47cc82ec3..0000000000 --- a/translations/ko-KR/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Setting up your codespace -intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 66cabd7dc4..0000000000 --- a/translations/ko-KR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Personalizing Codespaces for your account -intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About personalizing {% data variables.product.prodname_codespaces %} - -When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces. - -- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations. - -{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create. - -Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -### Settings Sync - -Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}. - -Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync. - -![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation. - -### 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/). - -If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} automatically uses this repository to personalize your codespace environment. Private `dotfiles` repositories are not currently supported. - -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. - -When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory. - -Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace. - -{% note %} - -**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor 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 "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)." - -{% endnote %} - -You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." - -### 더 읽을거리 - -* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/ko-KR/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/ko-KR/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 8a1128db5e..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} is free to use during the beta. When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage. diff --git a/translations/ko-KR/data/reusables/codespaces/about-configuration.md b/translations/ko-KR/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 398b2495a6..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -You can create a default codespace configuration for your repository that determines the environment of every new codespace anyone creates for that repository. The configuration defines a development container that can include frameworks, tools, extensions, and port forwarding. diff --git a/translations/ko-KR/data/reusables/codespaces/about-personalization.md b/translations/ko-KR/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index 958370ebd8..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Personalization can include shell preferences and additional tools. diff --git a/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md b/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 39b29dc4a0..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -You can forward ports in your codespace to test and debug your application. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 8031bfb4af..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/beta-functionality-limited.md b/translations/ko-KR/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 25501d28f0..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -During the beta, functionality is limited. -- {% data reusables.codespaces.use-chrome %} -- Only a single size of codespace is available. -- Only Linux containers are supported. -- A codespace is not fully resumable. Processes that were running at the time the codespace was stopped will not be restarted. diff --git a/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index 5e0618af02..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/codespace-config-order.md b/translations/ko-KR/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index e785e51c45..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Your `dotfiles` personalization is applied before a repository's default codespace configuration. diff --git a/translations/ko-KR/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/ko-KR/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index 146beb47e8..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Each codespace is associated with a specific branch of a repository. diff --git a/translations/ko-KR/data/reusables/codespaces/codespaces-are-personal.md b/translations/ko-KR/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 771fe3f97c..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Each codespace you create is only available to you. No one else can work in your codespace. diff --git a/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md b/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index 475114c1c5..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.{% note %} - -**Note:** {% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types: - -* **Basic** for updating a file and raising a pull request -* **Standard** for editing a website -* **Premium** for high compute tasks such as data analysis diff --git a/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 87bfa539ff..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users. - -For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/ko-KR/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index 40126da0da..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -You can create more than one codespace per repository or even per branch. However, each user account has a two-codespace limit during limited public beta. If you've reached the limit and want to create a new codespace, you must delete a codespace first. diff --git a/translations/ko-KR/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/ko-KR/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index 045387a57b..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -You can connect to your codespace directly from {% data variables.product.prodname_vscode %}. For more information, see "[Using Codespaces in {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." diff --git a/translations/ko-KR/data/reusables/codespaces/devcontainer-location.md b/translations/ko-KR/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index 196fc006be..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -This file can be located in the root of the repository or in a folder called `.devcontainer`. If the file is located in the root of the repository, the filename must begin with a period: `.devcontainer.json`. diff --git a/translations/ko-KR/data/reusables/codespaces/navigate-to-codespaces.md b/translations/ko-KR/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index 4ba7c260e0..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. At the top of any page, click **Codespaces**. ![{% data variables.product.prodname_codespaces %} link in header](/assets/images/help/codespaces/header-link.png) diff --git a/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index fed860897b..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/ko-KR/data/reusables/codespaces/rebuild-command.md b/translations/ko-KR/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index ea9e45b032..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/recovery-mode.md b/translations/ko-KR/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index fa4e73d013..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/release-stage.md b/translations/ko-KR/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 57e551dd72..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." - -{% endnote %} diff --git a/translations/ko-KR/data/reusables/codespaces/secret-precedence.md b/translations/ko-KR/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index 582b91c1aa..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/secrets-naming.md b/translations/ko-KR/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index eddb8aa7f5..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -The following rules apply to secret names: - -* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed. -* Secret names must not start with the `GITHUB_` prefix. -* Secret names must not start with a number. -* Secret names are not case-sensitive. -* Secret names must be unique at the level they are created at. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md b/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index c4a5bf3b41..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md b/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index 90b3503dcd..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-display.md b/translations/ko-KR/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index 09917cd3c8..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. - - ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/type-port-label.md b/translations/ko-KR/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 498c9eb752..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/unsupported-repos.md b/translations/ko-KR/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index 03fd9189d9..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -During the beta, private repositories owned by organizations or any repositories owned by an organization that requires SAML single sign-on are not supported. diff --git a/translations/ko-KR/data/reusables/codespaces/use-chrome.md b/translations/ko-KR/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index c44bb64faf..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -For the best experience with {% data variables.product.prodname_codespaces %}, we recommend using a Chromium-based browser, like Google Chrome or Microsoft Edge. diff --git a/translations/ko-KR/data/reusables/codespaces/use-visual-studio-features.md b/translations/ko-KR/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index a5b1cf9151..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -You can edit code, debug, and use Git commands while developing in a codespace with {% data variables.product.prodname_vscode %}. For more information, see the [{% data variables.product.prodname_vscode %} documentation](https://code.visualstudio.com/docs). diff --git a/translations/ko-KR/data/reusables/codespaces/vscode-settings-order.md b/translations/ko-KR/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index fc4b840129..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -When you configure editor settings for {% data variables.product.prodname_vscode %}, there are three scopes available: _Workspace_, _Remote [Codespaces]_, and _User_. If a setting is defined in multiple scopes, _Workspace_ settings take priority, then _Remote [Codespaces]_, then _User_. diff --git a/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index afb626e71c..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index a5e98437c0..0000000000 --- a/translations/ko-KR/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**. - - !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/gated-features/codespaces.md b/translations/ko-KR/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 1423451c5e..0000000000 --- a/translations/ko-KR/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespaces is available for user accounts using {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ko-KR/data/reusables/organizations/click-codespaces.md b/translations/ko-KR/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index 6a15dd7757..0000000000 --- a/translations/ko-KR/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index ae43f35c1f..0000000000 --- a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md b/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index 82cb0fbffe..0000000000 --- a/translations/ko-KR/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md b/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index e4908fcf75..0000000000 --- a/translations/ko-KR/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/content/codespaces/about-codespaces.md b/translations/pt-BR/content/codespaces/about-codespaces.md deleted file mode 100644 index 817bcd0fef..0000000000 --- a/translations/pt-BR/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Sobre os Codespaces -intro: '{% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento on-line configurável, hospedado por {% data variables.product.prodname_dotcom %} e alimentado por {% data variables.product.prodname_vscode %}, que permite que você se desenvolva inteiramente na nuvem.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre o {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento da nuvem configurável disponível no seu navegador em {% data variables.product.prodname_dotcom %} ou por meio de {% data variables.product.prodname_vscode %}. - -![Um codespace aberto](/assets/images/help/codespaces/codespace-overview.png) - -Um codespace inclui tudo o que os desenvolvedores precisam desenvolver para um repositório específico, incluindo a {% data variables.product.prodname_vscode %} experiência de edição e linguagens comuns, ferramentas e utilitários. {% data variables.product.prodname_codespaces %} é completamente configurável, permite que você crie um ambiente de desenvolvimento personalizado para seu projeto, e também que os desenvolvedores personalizem sua experiência com extensões e configurações do dotfile. - -Os codespaces oferecem muitos benefícios para as equipes, o que permite um ambiente consistente em toda a sua equipe, integração rápida e criação de um espaço seguro para o desenvolvimento. - -### Um ambiente consistente - -É possível criar uma configuração de codespace único que define o ambiente (ou o _contêiner de desenvolvimento_) de cada novo código que qualquer pessoa criar para seu repositório. Uma vez definida uma configuração, os desenvolvedores não precisam se preocupar em instalar as ferramentas certas para comentar, revisar ou contribuir. Um ambiente padronizado já está disponível para eles assim que eles criam um codespace do repositório. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -Para obter ajuda para começar com configurações para linguagens específicas, consulte os tutoriais de [introdução](/codespaces/getting-started-with-codespaces). - -Embora todos os códigos criados a partir do seu repositório possuam um ambiente de desenvolvimento consistente, os desenvolvedores podem usar {% data variables.product.prodname_codespaces %} onde quiserem – em {% data variables.product.prodname_dotcom %} ou por meio de {% data variables.product.prodname_vscode %}. - -### Integração rápida e pessoal - -Com um contêiner de desenvolvimento [](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configurado no seu repositório, todos os novos desenvolvedores podem integrar rapidamente com o ambiente de desenvolvimento correto para o seu projeto usando o menu suspenso {% octicon "download" aria-label="The download icon" %} **Code**e selecionando **Abrir com os codespaces**. - -![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -Como resultado da padronização em um ambiente de desenvolvedor reproduzível. Os desenvolvedores podem começar com um novo código sem fazer qualquer configuração manual e não precisam fazer a manutenção contínua do seu ambiente de desenvolvedores. É possível criar um novo codespace ao iniciar um novo recurso. - -Os desenvolvedores também podem personalizar aspectos do seu ambiente de código usando um [dotfiles](https://dotfiles.github.io/tutorials/) repositório e [sincronização de onfigurações](https://code.visualstudio.com/docs/editor/settings-sync). A personalização pode incluir preferências shell, ferramentas adicionais, configurações de editor e extensões, como Live Share. Personalizações pessoais são armazenadas por usuário. Portanto, cada código que um desenvolvedor abrir terá seu ambiente pronto para ser usado. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". - -Como {% data variables.product.prodname_codespaces %} pode ser acessado no navegador, os desenvolvedores podem trabalhar em vários projetos, alternando entre abas. - -### Um ambiente seguro - -{% data variables.product.prodname_codespaces %} permite que os desenvolvedores façam o desenvolvimento na nuvem em vez de no local. Isso cria uma fonte única e rastreável de verdade. Os desenvolvedores podem contribuir de qualquer lugar, em qualquer máquina, incluindo tablets ou Chromebooks, e não há necessidade de manter cópias locais da propriedade intelectual. Desenvolvedores sempre precisam estar conectados e ter acesso a {% data variables.product.prodname_codespaces %} e a repositórios específicos. Estas permissões podem ser revogadas a qualquer momento. Assim que você revogar o acesso, esses desenvolvedores perderão todo o acesso a recursos protegidos. Além disso, os desenvolvedores autenticados criam trilhas de auditoria para que você saiba quem está fazendo o quê. Para obter mais informações sobre acesso e segurança, consulte "[Gerenciar o acesso e a segurança para os códigos de sua organização](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". - -Usar {% data variables.product.prodname_codespaces %} é o mais seguro quando todos os integrantes da sua equipe o estão usando. Isso significa que não há necessidade de clonar o repositório para uma máquina local e que os desenvolvedores não precisam instalar localmente como `raiz`. - -Os desenvolvedores e administradores de organização também podem definir as configurações para adicionar segredos criptografados e habilitar a verificação GPG. Para obter mais informações, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### Sobre a cobrança do {% data variables.product.prodname_codespaces %} - -{% data reusables.codespaces.about-billing-for-codespaces %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)". - -### Juntar-se ao beta - -Um número limitado de pessoas será convidado a participar do beta. To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### Entre em contato conosco com relação a {% data variables.product.prodname_codespaces %} - -Se você tiver algum problema ao usar {% data variables.product.prodname_codespaces %}, consulte "[Solucionar problemas do seu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -Se você ainda precisa de ajuda ou tem feedback sobre {% data variables.product.prodname_codespaces %}, use a discussão de [Feedback para codespaces](https://github.com/github/feedback/discussions/categories/codespaces-feedback). diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index 2ade0c66f6..0000000000 --- a/translations/pt-BR/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Sobre a cobrança para codespaces -intro: 'Quando {% data variables.product.prodname_codespaces %} se torna geralmente disponível, você será cobrado para armazenamento e uso de computação.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -As atualizações do modelo de cobrança para codespaces serão compartilhadas em um próximo anúncio. diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index 2946135002..0000000000 --- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Permitir que seu codespace acesse um registro de imagens privadas -intro: 'Você pode usar segredos para permitir que {% data variables.product.prodname_codespaces %} acesse um registro de imagens privada' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Um registro é um espaço seguro para armazenar e gerenciar imagens de contêineres privadas, como Azure Container Registry ou DockerHub. Você pode criar segredos no GitHub para armazenar os detalhes de acesso de um registro privado e usá-los para dar ao seu código acesso as imagens armazenadas no registro. - -Ao iniciar iniciar um código, {% data variables.product.prodname_codespaces %} verifica três segredos, que definem o nome do servidor, o nome de usuário e o token de acesso pessoal (PAT) para um registro do contêiner. Se estes segredos forem encontrados, {% data variables.product.prodname_codespaces %} disponibilizará o registro dentro do seu codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -É possível armazenar segredos a nível do usuário, repositório ou organização, permitindo que você os compartilhe de forma segura entre diferentes codespaces. Ao criar um conjunto de segredos para um registro de imagem privado, você precisa substituir o "<*>" no nome por um identificador consistente. Para mais informações, consulte "[Gerenciar segredos criptografados para seus códigos](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" e "[Gerenciar segredos criptografados para seu repositório e organização para os codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)". - -Por exemplo, se você tiver um registro de imagens privadas no Azure, você poderá criar os seguintes segredos: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Exemplo de segredo do registro de imagem](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/index.md b/translations/pt-BR/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index e974c8ed9b..0000000000 --- a/translations/pt-BR/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Referência -intro: 'Esta seção contém referências que permitirão seu sucesso com {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index 3ca3eecf87..0000000000 --- a/translations/pt-BR/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Solucionar problemas do seu codespace -intro: Use este guia para ajudá-lo a resolver problemas comuns com seu codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Limitações conhecidas - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### Solução de problemas de {% data variables.product.prodname_vscode %} - -Use **Problemas** no [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) para verificar problemas conhecidos ou registrar problemas sobre a experiência de {% data variables.product.prodname_vscode %}. - - -### Solução de problemas de configuração - -{% data reusables.codespaces.recovery-mode %} - -``` -Este codespace está em execução em modo de recuperação devido a um erro no contêiner. -``` - -Revise os registros de criação, atualize a configuração conforme necessário e execute **Codespaces: Rebuild Container** na paleta de comandos para tentar novamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". - -### solução de problemas dotfiles - -- Certifique-se de que seu repositório dotfiles seja público. Se você tem segredos ou dados confidenciais que você deseja usar em seu código, use [segredos de codespaces ](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) em vez dos dotfiles privados. -- Verifique `/workspaces/.codespaces/.persistedshare/dotfiles` para ver se seus dotfiles foram clonados. - - Se seus dotfiles foram clonados, tente reexecutar manualmente seu script de instalação para verificar se ele é executável. - - Se seus dotfiles não foram clonados, verifique `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` para ver se havia um problema com a clonagem. -- Verifique `/workspaces/.codespaces/.persistedshare/creation.log` com relação a possíveis problemas. Como alternativa, você pode ver o `creation.log` acessando a paleta de comandos e inserindo os **Codespaces: View Creation Log**. - - -### Solução de problemas do navegador - -Se você encontrar problemas ao usar um navegador que não se baseie no Chromium, tente alternar para um navegador baseado no Chromium ou verifique se há problemas conhecidos com seu navegador no repositório `microsoft/vscode` procurando por problemas etiquetados com o nome do seu navegador, como, por exemplo, [`fogo-fogo`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) ou [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). - -Se você encontrar problemas ao usar um navegador baseado em Chromium, você poderá verificar se você está tendo outro problema conhecido com {% data variables.product.prodname_vscode %} no repositório [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). - -### Solução de problemas de armazenamento do contêiner - -Ao criar um codespace, ele terá uma quantidade limitada de armazenamento e, após um tempo, poderá ser necessário que você libere espaço. Experimente qualquer um dos seguintes itens para liberar espaço de armazenamento. - -- Remova pacotes que não são mais usando `sudo apt autoremove` -- Limpe o cache apt usando `sudo apt clean` -- Exclua arquivos desnecessários, como artefatos de compilação e registros (estes são muito dependentes do projeto) -- Veja os 10 principais arquivos no codespace: `sudo find / -printf '%s %p\n'├sort -nr ├head -10` - -Mais opções para exclusão: -- Remova imagens não utilizadas do Docker, redes, e contêineres utilizando o `docker system prune` (insira `-a` se desejar remover todas as imagens, e `--volumes` se desejar remover todos os volumes) -- Remova os arquivos não rastreados da árvore de trabalho: `git clean -i` - -### Entrar em contato - -Se precisar de ajuda, você poderá entrar em contato conosco. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)." diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 4056e6b0f5..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Criar um codespace -intro: Você pode criar um codespace para uma branch em um repositório para fazer o desenvolvimento on-line. -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre a criação do codespace - -Você pode criar um codespace em {% data variables.product.prodname_dotcom_the_website %} ou em {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Os codespaces são associados a um branch específico de um repositório e o repositório não pode estar vazio. {% data reusables.codespaces.concurrent-codespace-limit %} Para obter mais informações, consulte "[Excluir um codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". - - -Ao criar um codespace, várias etapas acontecem para permitir o acesso total ao seu ambiente de desenvolvimento. - -- Recursos como uma VM e armazenamento para seu contêiner foram atribuídos. Uma nova VM é criada toda vez que você criar ou iniciar um codespace para garantir que você sempre tenha as versões mais recentes e patch de segurança. -- {% data variables.product.prodname_codespaces %} recebe informações sobre o seu repositório, branch, commits, seu repositório dotfiles público e quaisquer segredos que você tenha criado. -- {% data variables.product.prodname_codespaces %} executa um clone raso do repositório. -- Se você tiver um no seu repositório, {% data variables.product.prodname_codespaces %} irá executar o arquivo `devcontainer.json`. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". -- Seu contêiner Docker, `docker-compose`, ou outra inicialização é executada. -- Neste ponto, o codespace está marcado como disponível e você pode conectar-se. -- Assim que o codespace for disponibilizado, dependendo dos comandos no devcontainer, o codespace continuará com algumas configurações. - - O codespace compartilha as portas adicionadas no arquivodevcontainer.json.`. -
  • O codespace executa qualquer coisa especificada em postCreateCommand`. - - {% data variables.product.prodname_codespaces %} clona o repositório do dotfiles no ambiente de código e procura um arquivo de instalação. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". - - Por fim, o código do repositório faz um clone completo para que você tenha acesso total ao mesmo. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Criar um codespace - -{% data reusables.repositories.navigate-to-repo %} -2. No nome do repositório, use o menu suspenso "Branch", e selecione o branch para o qual você deseja criar um codespace. - - ![Menu suspenso do branch](/assets/images/help/codespaces/branch-drop-down.png) - -3. No nome do repositório, use o menu suspenso do {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com os espaços de código**. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. Para criar um codespace usando um tipo de máquina padrão, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. - - ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index b994587165..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Excluir um codespace -intro: Você pode excluir um codespace de que você não precisa mais. -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Acesse o repositório onde você criou o codespace. Selecione **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** e, em seguida, clique em {% octicon "gear" aria-label="The Settings gear" %}. Isto irá exibir todo o {% data variables.product.prodname_codespaces %} que você criou no repositório. ![Aba Codespaces](/assets/images/help/codespaces/codespaces-manage.png) - - Como alternativa, você pode ver todos os códigos existentes na sua conta de usuário em [github.com/codespaces](https://github.com/codespaces). - -2. À direita do código que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, depois em **{% octicon "trash" aria-label="The trash icon" %} Apagar** ![Botão excluir](/assets/images/help/codespaces/delete-codespace.png) - -### Excluir um codespace em {% data variables.product.prodname_vscode %} - -Para obter informações sobre como excluir um codespace em {% data variables.product.prodname_vscode %}, consulte "[Usando codespaces no Visual Studio](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)". diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index c5794bd14d..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Desenvolver em um codespace -intro: 'Você pode abrir um codespace em {% data variables.product.product_name %} e, em seguida, desenvolver usando os recursos do {% data variables.product.prodname_vscode %}.' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre o desenvolvimento com {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} fornece a você a experiência completa de desenvolvimento de {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Visão geral do codespace com anotações](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Barra lateral - Por padrão, esta área mostra os arquivos do seu projeto no Explorador. -2. Barra de Atividades - Exibe a visualização e fornece uma maneira de alternar entre elas. Você pode reordenar as Visualizações arrastando e soltando-as. -3. Editor - É aqui que você edita seus arquivos. Você pode usar a aba para cada editor para posicioná-lo exatamente onde você precisa. -4. Painéis - É aqui que você pode visualizar as informações de saída e depuração, bem como o local padrão para o Terminal integrado. -5. Barra de Status - Esta área fornece informações úteis sobre seu codespace e projeto. Por exemplo, o nome da agência, portas configuradas e muito mais. - -Para obter mais informações sobre como usar {% data variables.product.prodname_vscode %}, consulte o [Guia da Interface do Usuário](https://code.visualstudio.com/docs/getstarted/userinterface) na documentação de {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} Para obter mais informações, consulte "[Solucionar problemas do seu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -#### Personalizando seu codespace - -{% data reusables.codespaces.about-personalization %} Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)". - -{% data reusables.codespaces.apply-devcontainer-changes %} Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para o seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". - -#### Executando seu aplicativo a partir de um codespace -{% data reusables.codespaces.about-port-forwarding %} Para obter mais informações, consulte "[Encaminhar portas no seu codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)". - -#### Fazendo commit das suas alterações - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Acessar um codespace existente - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Clique no nome do codespace em que você deseja desenvolver. ![Nome do codespace](/assets/images/help/codespaces/click-name-codespace.png) - -Como alternativa, você pode ver quaisquer codespaces ativos para um repositório, acessando o repositório no qual ele foi criado e selecionando **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index aed71274fa..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Encaminhar portas no seu código -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre as portas encaminhadas - -O redirecionamento de porta dá acesso a portas TCP que estão em execução no seu codespace. Por exemplo, se você estiver executando um aplicativo web na porta 4000, você poderá acessá-lo a partir do seu navegador para testar e depurar o aplicativo. - -Quando um aplicativo que se executa dentro de um codespace tem uma saída na porta para o console, o {% data variables.product.prodname_codespaces %} detecta o padrão do URL do host local e encaminha a porta automaticamente. Você pode clicar na URL no terminal para abrir a porta em um navegador. Por exemplo, se um aplicativo gerar `http://127.0.0.:4000` ou `http://localhost:4000` para o console, o registro irá converter automaticamente a saída em uma URL para a porta 4000 em que se pode clicar. - -![Encaminhamento de porta automático](/assets/images/help/codespaces/automatic-port-forwarding.png) - -Você também pode encaminhar uma porta manualmente, etiquetar portas encaminhadas, compartilhar portas anunciadas publicamente e adicionar portas encaminhadas para a configuração do código. - -### Encaminhar uma porta - -Você pode encaminhar manualmente uma porta que não foi encaminhada automaticamente. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Na lista de portas, clique em **Adicionar porta**. ![Botão adicionar porta](/assets/images/help/codespaces/add-port-button.png) -1. Digite o número da porta ou endereço e, em seguida, pressione enter. ![Caixa de texto para o botão digitar porta](/assets/images/help/codespaces/port-number-text-box.png) - -### Etiquetar uma porta - -Você pode etiquetar uma porta para tornar a porta mais facilmente identificável em uma lista. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Passe o mouse sobre a porta que você deseja etiquetar, em seguida, clique no ícone da etiqueta. ![Ícone da etiqueta para a porta](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Compartilhar uma porta - -Se você quiser compartilhar uma porta encaminhada com outras pessoas, você poderá tornar a porta pública. Após tornar uma porta pública, qualquer pessoa com a URL da porta poderá ver o aplicativo em execução sem precisar efetuar a autenticação. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Clique com o botão direito na porta que você deseja compartilhar e clique em **Tornar pública**. ![Opção para tornar a porta pública no menu com o clique com o botão direito](/assets/images/help/codespaces/make-public-option.png) -1. À direita do endereço local para a porta, clique no ícone copiar. ![Copiar ícone para o URL de porta](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Envie a URL copiada para a pessoa com quem você deseja compartilhar a porta. - -### Adicionar uma porta à configuração do código - -É possível adicionar uma porta encaminhada para a configuração {% data variables.product.prodname_codespaces %} do repositório para que a porta seja automaticamente encaminhada para todos os códigos criados a partir do repositório. Depois de atualizar a configuração, todos os codespaces criados anteriormente deverão ser reconstruídos para que a alteração seja aplicada. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". - -Você pode configurar manualmente as portas predefinidas em um arquivo `.devcontainer.json` usando a propriedade `forwardPorts`, ou você pode usar o painel "Portas" no seu codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Clique com o botão direito na porta que você deseja adicionar à configuração do codespace e, em seguida, clique em **Definir etiqueta e atualizar devcontainer.json**. ![Opção para definir a etiqueta e adicionar a porta ao devcontainer.json no menu com o clique no botão direito](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index 81f828b37f..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Desenvolver em um codespace -intro: 'Crie um codespace para começar a desenvolver seu projeto dentro de um ambiente de nuvem dedicado. Você pode usar portas encaminhadas para executar o seu aplicativo e até mesmo usar codespaces dentro de {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index 39324761fc..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Usar espaços de código no Visual Studio Code -intro: 'Você pode desenvolver seu codespace diretamente em {% data variables.product.prodname_vscode %}, conectando a extensão de {% data variables.product.prodname_github_codespaces %} à sua conta no {% data variables.product.product_name %}.' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Pré-requisitos - -Para desenvolver em um código diretamente em {% data variables.product.prodname_vscode %}, você deve inscrever-se na extensão de {% data variables.product.prodname_github_codespaces %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode %}. - -Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}. - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_dotcom %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -4. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Utilize o menu suspenso "EXPLORADOR REMOTO" e clique em **{% data variables.product.prodname_github_codespaces %}**. ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Clique em **Iniciar sessão para visualizar {% data variables.product.prodname_codespaces %}...**. ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -5. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. - -{% endwindows %} - -### Criar um codespace em {% data variables.product.prodname_vscode %} - -Depois de conectar sua conta de {% data variables.product.product_name %} à extensão de {% data variables.product.prodname_github_codespaces %}, você pode desenvolver em um codespace que você criou no {% data variables.product.product_name %} ou em {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Clique no ícone Adicionar e, em seguida, clique em **Criar novo codespace**. ![A opção "Criar novo codespace" em {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Digite e, em seguida, clique no nome do repositório no qual você deseja desenvolver. ![Pesquisar um repositório para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Clique no branch que você deseja desenvolver. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Clique no tipo de máquina na qual você deseja desenvolver. ![Tipos de instância para um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) -### Abrir um codespace em {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Em "Codedespaces", clique no código que você deseja desenvolver. -3. Clique no ícone Conectar-se ao Codespace. ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Alterar o tipo da máquina em {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -Você pode alterar o tipo de máquina do seu codespace a qualquer momento. - -1. Em {% data variables.product.prodname_vscode %}, abra a Paleta de Comando (`shift comando P` / `shift control P`). -2. Pesquise e selecione "Codespaces: Alterar tipo de máquina." ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Clique no codespace que você deseja alterar. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Escolha o tipo de máquina que você quer usar. ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -Se o codespace estiver sendo executado, será exibida uma mensagem perguntando se você deseja reiniciar e reconectar-se ao seu codespace agora. Clique em **Sim** se desejar mudar o tipo de máquina utilizado para este codespace imediatamente. Se você clicar em **Não**, ou se o código não estiver em execução, a alteração entrará em vigor na próxima vez que o codespace for reiniciado. - -### Excluir um codespace em {% data variables.product.prodname_vscode %} - -1. Em "Codedespaces", clique com o botão direito no código que você deseja excluir. -2. No menu suspenso, clique em **Excluir o codespace**. ![Excluir um codespace em {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index e569ca38b1..0000000000 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Usando controle de origem no seu codespace -intro: 'Depois de fazer alterações em um arquivo no seu código, você pode fazer um commit rápido das alterações e fazer push da sua atualização para o repositório remoto.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre o controle de origem em {% data variables.product.prodname_codespaces %} - -Você pode executar todas as ações do Git necessárias diretamente no seu codespace. Por exemplo, é possível obter alterações do repositório remoto, alternar os branches, criar um novo branch, fazer commit, fazer push e criar um pull request. Você pode usar o terminal integrado dentro do seu codespace para inserir nos comandos do Git, ou você pode clicar em ícones e opções de menu para realizar todas as tarefas mais comuns do Git. Este guia explica como usar a interface gráfica de usuário para controle de origem. - -O controle de origem em {% data variables.product.prodname_github_codespaces %} usa o mesmo fluxo de trabalho que {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte a documentação {% data variables.product.prodname_vscode %}"[Usando Controle de Versão no Código VS](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". - -Um fluxo de trabalho típico para atualizar um arquivo que usa {% data variables.product.prodname_github_codespaces %} seria: - -* A partir do branch padrão do seu repositório em {% data variables.product.prodname_dotcom %}, crie um codespace. Consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -* No seu código, crie uma nova agência para trabalhar. -* Faça suas alterações e salve-as. -* Faça commit da alteração. -* Abra um pull request. - -### Criar ou trocar de branches - -1. Se o branch atual não for mostrado na barra de status, na parte inferior do seu codespace, clique com o botão direito na barra de status e selecione **Controle de origem**. -1. Clique no nome do branch na barra de status. ![O branch na barra de status](/assets/images/help/codespaces/branch-in-status-bar.png) -1. No menu suspenso, clique no branch para o qual você deseja alternar ou digite o nome de um novo branch e clique em **Criar novo branch**. ![Escolha no menu do branch](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Dica**: Se alguém alterou um arquivo no repositório remoto, no branch para o qual você mudou, você não verá essas alterações até você fazer pull das alterações no seu codespace. - -{% endtip %} - -### Fazer pull das alterações do repositório remoto - -Você pode fazer pull das alterações do repositório remoto para seu codespace a qualquer momento. - -{% data reusables.codespaces.source-control-display-dark %} -1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. No menu suspenso, clique em **Pull**. - -Se um contêiner de desenvolvimento foi alterado desde que você criou o codespace, você poderá aplicar as alterações reconstruindo o contêiner para o codespace. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". - -### Configurar o seu codespace para buscar novas alterações automaticamente - -É possível definir seu codespace para obter automaticamente os detalhes de quaisquer novos commits que tenham sido criados no repositório remoto. Isso permite que você veja se sua cópia local do repositório está desatualizada. Nesse caso, você pode optar por fazer pull das novas alterações. - -Se a operação de busca detectarem novas alterações no repositório remoto, você verá o número de novos commits na barra de status. Você pode fazer pull das alterações para a sua cópia local. - -1. Clique no botão **Gerenciar** na parte inferior da barra de atividades. ![Botão Gerenciar](/assets/images/help/codespaces/manage-button.png) -1. No menu, clique em **Configurações**. -1. Na página de configurações, pesquise por: `Autofetch`. ![Pesquisar por busca automática](/assets/images/help/codespaces/autofetch-search.png) -1. Para buscar os detalhes das atualizações para todos os controles remotos registrados no repositório atual, defina **Git: Autofetch** como `todos`. ![Habilite a busca automática do Git](/assets/images/help/codespaces/autofetch-all.png) -1. Se você deseja alterar o número de segundos entre cada busca automática, edite o valor de **Git: Período de Autofetch**. - -### Fazendo commit das suas alterações - -{% data reusables.codespaces.source-control-display-dark %} -1. Para testar suas alterações, clique **+** ao lado do arquivo que você alterou, ou ao lado de **Alterações** se você mudou vários arquivos e quiser testar todos. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Digite uma mensagem do commit que descreve a alteração que você fez. ![Barra lateral do controle de origem com uma mensagem de commit](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. Para fazer commit das alterações em fase de preparação, clique na marca de seleção na parte superior da barra lateral de controle de origem. ![Clique no ícone da marca de verificação](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Abrindo um pull request - -1. Depois de realizar alterações na sua cópia local do repositório, clique no ícone **Criar Pull Request**. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Verifique se o branch local e o repositório do qual você está fazendo merge, o branch remoto e o repositório no qual você está fazendo merge estão corretos. Em seguida, dê ao pull request um título e uma descrição. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Clique em **Criar**. - -### Fazer push das alterações para o seu repositório remoto - -Você pode fazer push das alterações que fez. Isso aplica essas alterações ao branch upstream no repositório remoto. Você pode querer fazer isso se ainda não estiver pronto para criar um pull request, ou se você preferir criar um pull request em {% data variables.product.prodname_dotcom %}. - -1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. No menu suspenso, clique em **Push**. diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index c7498569a5..0000000000 --- a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Primeiros passos com o seu projeto C# (.NET) em codespaces -shortTitle: Primeiros passos com o seu projeto C# (.NET) -allowTitleToDifferFromFilename: true -intro: 'Primeiros passos com o seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introdução - -Este guia mostra como configurar seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo. - -#### Pré-requisitos - -- Você deve ter um projeto C# (.NET) existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/2percentsilk/dotnet-quickstart. -- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização. - -### Etapa 1: Abra o seu projeto em um codespace - -1. Acesse o repositório do seu projeto. Use o menu suspenso {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com Codespaces**. Se você não vir esta opção, seu projeto não está disponível para {% data variables.product.prodname_codespaces %}. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para criar um novo codespace, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - -Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu codespace têm várias linguagens e tempos de execução, incluindo .NET. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. - -Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados. - -{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo - -O contêiner de codespaces padrão vem com a versão mais recente do .NET e as ferramentas mais comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para que possa personalizar as ferramentas e scripts que são executados como parte da criação do codespace para as necessidades do seu projeto e garantir um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} no seu repositório. - -Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar codespaces para o seu projeto ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Acesse a paleta de comandos (`shift comando P` / `shift control P`) e, em seguida, comece a digitar "dev container". Clique em **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** !["Codespaces: Adicionar arquivos de configuração de Contêiner de Desenvolvimento..." na paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. Para este exemplo, clique em **C# (.NET)**. Se você precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para o C# (.NET) ou uma combinação de ferramentas como C# (.NET) e MS SQL. ![Selecione a opção C# (.NET) na lista](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Clique na versão recomendada do .NET. ![Seleção da versão .NET](/assets/images/help/codespaces/add-dotnet-version.png) -4. Aceite a opção padrão para adicionar Node.js à sua personalização. ![Adicionar seleção de Node.js](/assets/images/help/codespaces/dotnet-options.png) -5. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomia do seu contêiner de desenvolvimento - -A adição do modelo de contêiner de C# (.NET) adiciona uma pasta de contêiner de desenvolvimento `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos: - -- `devcontainer.json` -- arquivo Docker - -O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "dotnet restore", - - // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Nome** - Você pode dar qualquer nome ao nosso contêiner de desenvolvimento. Este é apenas o padrão. -- **Build** - As propriedades de compilação. - - **Arquivo Docker** - No objeto de compilação, `arquivo Docker` é uma referência ao arquivo arquivo Docker que também foi adicionado a partir do template. - - **Args** - - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a versão do .NET Core que queremos usar. -- **Configurações** - Estas são as configurações de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação. -- **Extensões** - Estas são extensões incluídas por padrão. - - **ms-dotnettools.csharp** - A extensão Microsoft C# fornece amplo suporte para o desenvolvimento em C#, incluindo funcionalidades como IntelliSense, links, depuração, navegação de código, formatação de código, refatoração, explorador de variáveis, explorador de testes e muito mais. -- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente. -- **postCreateCommand** - Se você quiser executar qualquer coisa depois de parar no seu codespace, isso não estará definido no arquivo Docker como a `Dotnet restore`. Você pode fazer isso aqui. -- **remoteUser** - Por padrão, você está executando como usuário do vscode, mas, opcionalmente, você pode definir isso como root. - -##### arquivo Docker - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do OS, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso contêiner. - -### Etapa 3: Modifique seu arquivo devcontainer.json - -Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e restaurar as dependências do seu projeto quando o seu codespace for iniciado. - -1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. - - !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Atualize a sua lista de `extensões` no seu arquivo `devcontainer.json` para adicionar algumas extensões úteis ao trabalhar com o seu projeto. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Remova o comentário o `postCreateCommand` para restaurar as dependências como parte do processo de configuração do codespace. - - ```json{:copy} - // Use 'postCreateCommand' para executar os comandos após a criação do contêiner. - "postCreateCommand": "dotnet restore", - ``` - -4. Para reconstruir seu contêiner e aplicar as alterações do devcontainer.json, acesse a paleta de comandos (`shift comando P` / `shift control P`). Em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. - - ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - - A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner. - -5. Verifique se suas alterações foram aplicadas com sucesso verificando se a extensão "Code Spell Checker" foi instalada. - - ![Lista de extensões](/assets/images/help/codespaces/dotnet-extensions.png) - -### Etapa 4: Execute o seu aplicativo - -Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via pip3. Com nossas dependências agora instaladas, podemos executar nosso aplicativo. - -1. Execute seu aplicativo pressionando `F5` ou inserindo `dotnet watch run` no seu terminal. - -2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa. - - ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/python-port-forwarding.png) - -### Etapa 5: Faça commit das suas alterações - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Próximas etapas - -Agora você deve estar pronto para começar a desenvolver seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados. - -- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 40d9a18919..0000000000 --- a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Primeiros passos com o seu projeto Java no Codespaces -shortTitle: Primeiros passos para seu projeto Java -intro: 'Dê os primeiros passos com o seu projeto Java em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introdução - -Este guia mostra como configurar seu projeto Java em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo. - -#### Pré-requisitos - -- Você deve ter um projeto Java existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/microsoft/vscode-remote-try-java -- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização. - -### Etapa 1: Abra o seu projeto em um codespace - -1. Acesse o repositório do seu projeto. Use o menu suspenso {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com Codespaces**. Se você não vir esta opção, seu projeto não está disponível para {% data variables.product.prodname_codespaces %}. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para criar um novo codespace, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - -Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner do seu código possui muitas linguagens e tempos de execução, incluindo Java, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. - -Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados. - -{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo - -O contêiner de codespaces padrão vem com a versão mais recente do Java, gerenciadores de pacotes (Maven, Gradle) e outras ferramentas comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para definir as ferramentas e scripts de que seu projeto precisa. Isso garantirá um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} do seu repositório. - -Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar espaços de códigos para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Acesse a paleta de comandos (`shift comando P` / `shift control P`) e, em seguida, comece a digitar "dev container". Clique em **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** !["Codespaces: Adicionar arquivos de configuração de Contêiner de Desenvolvimento..." na paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. Para este exemplo, clique em **Java**. Na prática, você pode selecionar qualquer contêiner específico para Java ou uma combinação de ferramentas como Java e Azure Functions. ![Selecione a opção Java na lista](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Clique na versão recomendada do Java. ![Seleção da versão Java](/assets/images/help/codespaces/add-java-version.png) -5. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomia do seu contêiner de desenvolvimento - -A adição do modelo de contêiner de desenvolvimento Java adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos: - -- `devcontainer.json` -- arquivo Docker - -O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. Consulte https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Nome** - Você pode dar qualquer nome ao seu contêiner de desenvolvimento. Este é apenas o padrão. -- **Build** - As propriedades de compilação. - - **Arquivo Docker** - No objeto de compilação, o arquivo Docker é uma referência ao arquivo Docker que também foi adicionado a partir do template. - - **Args** - - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a versão de Java que é passada para o arquivo Docker. -- **Configurações** - Estas são configurações de {% data variables.product.prodname_vscode %} que você pode definir. - - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação. -- **Extensões** - Estas são extensões incluídas por padrão. - - **Vscjava.vscode-java-pack** - O pacote de extensão Java fornece extensões populares para o desenvolvimento do Java para você começar. -- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente. -- **postCreateCommand** - Se você quiser executar qualquer coisa depois de chegar ao seu codespace que não está definido no arquivo Docker, você poderá fazer isso aqui. -- **remoteUser** - Por padrão, você está executando como usuário do `vscode`, mas, opcionalmente, você pode definir isso como `root`. - -##### arquivo Docker - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Você pode usar o arquivo arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do sistema operacional, versões do Java ou pacotes globais que queremos que sejam incluídos no nosso arquivo Docker. - -### Etapa 3: Modifique seu arquivo devcontainer.json - -Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e dependências do seu projeto quando seu codespace for iniciado. - -1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que sair da pasta `.devcontainer` para vê-la. - - !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - Para obter mais informações sobre as propriedades `devcontainer.json`, consulte a [referência devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) na documentação do Visual Studio Code. - -3. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. - - ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - - A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner. - - -### Etapa 4: Execute o seu aplicativo - -Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via npm. Agora você pode usar isso para executar nosso aplicativo com npm. - -1. Execute o seu aplicativo pressionando `F5`. - -2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa. - - ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Etapa 5: Faça commit das suas alterações - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Próximas etapas - -Agora você deve estar pronto para começar a desenvolver seu projeto Java em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados. - -- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 45f859a5eb..0000000000 --- a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Primeiros passos com o seu projeto Node.js em Codedespaces -shortTitle: Primeiros passos para o seu projeto Node.js -intro: 'Comece com seu projeto JavaScript, Node.js ou TypeScript em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### Introdução - -Este guia mostra como configurar seu projeto JavaScript, Node.js ou TypeScript em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo. - -#### Pré-requisitos - -- Você deve ter um projeto existente de JavaScript, Node.js ou TypeScript em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/microsoft/vscode-remote-try-node -- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização. - -### Etapa 1: Abra o seu projeto em um codespace - -1. Acesse o repositório do seu projeto. Use o menu suspenso {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com Codespaces**. Se você não vir esta opção, seu projeto não está disponível para {% data variables.product.prodname_codespaces %}. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para criar um novo codespace, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - -Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu código possui muitas linguagens e tempos de execução, incluindo Node.js, JavaScript, Typescript, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. - -Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados. - -{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -### Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo - -O contêiner de codespaces padrão será compatível com a execução de projetos de Node.js como [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) fora da caixa. Ao configurar um contêiner personalizado, você poderá personalizar as ferramentas e scripts que são executados como parte da criação de código e garantir um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} no seu repositório. - -Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Acesse a paleta de comandos (`shift comando P` / `shift control P`) e, em seguida, comece a digitar "dev container". Clique em **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** !["Codespaces: Adicionar arquivos de configuração de Contêiner de Desenvolvimento..." na paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. Para este exemplo, clique em **Node.js**. Se você precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para o Node ou uma combinação de ferramentas como Node e MongoDB. ![Selecione a opção Node na lista](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Clique na versão recomendada do Node.js. ![Seleção de versão do Node.js](/assets/images/help/codespaces/add-node-version.png) -5. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomia do seu contêiner de desenvolvimento - -A adição do modelo de contêiner de desenvolvimento do Node.js adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos: - -- `devcontainer.json` -- arquivo Docker - -O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Nome** - Você pode dar qualquer nome ao seu contêiner de desenvolvimento. Este é apenas o padrão. -- **Build** - As propriedades de compilação. - - **Arquivo Docker** - No objeto de compilação, o arquivo Docker é uma referência ao arquivo Docker que também foi adicionado a partir do modelo. - - **Args** - - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a variante de nó que queremos usar e que é passada para o arquivo Docker. -- **Configurações** - Estas são configurações de {% data variables.product.prodname_vscode %} que você pode definir. - - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação. -- **Extensões** - Estas são extensões incluídas por padrão. - - <**Dbaeumer.vscode-eslint** - ES lint é uma ótima extensão para linting, mas para o JavaScript, há uma série de ótimas extensões do Marketplace que você também pode incluir. -- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente. -- **postCreateCommand** - Se você quiser executar qualquer coisa depois de chegar ao seu codespace que não está definido no arquivo Docker, você poderá fazer isso aqui. -- **remoteUser** - Por padrão, você está executando como usuário do vscode, mas, opcionalmente, você pode definir isso como root. - -##### arquivo Docker - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do sistema operacional, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso arquivo Docker. - -### Etapa 3: Modifique seu arquivo devcontainer.json - -Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar o npm quando seu codespace for lançado e para fazer uma lista de portas dentro do contêiner disponível localmente. - -1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que sair da pasta `.devcontainer` para vê-la. - - !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - Para obter mais informações sobre as propriedades `devcontainer.json`, consulte a referência de [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) na documentação de {% data variables.product.prodname_vscode %}. - -3. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. - - ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - - A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner. - - -### Etapa 4: Execute o seu aplicativo - -Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via npm. Agora você pode usar isso para executar nosso aplicativo com npm. - -1. Execute seu comando inicial no terminal com`npm start`. - - ![início do npm no terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa. - - ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Etapa 5: Faça commit das suas alterações - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Próximas etapas - -Agora você deve estar pronto para começar a desenvolver seu projeto JavaScript em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados. - -- [Gerenciar segredos criptografados para seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index b18e320ba7..0000000000 --- a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Primeiros passos para seu projeto Python no Codedespaces -shortTitle: Primeiros passos para seu projeto Python -intro: 'Dê os primeiros passos com seu projeto Python em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### Introdução - -Este guia mostra como configurar seu projeto Python em {% data variables.product.prodname_codespaces %}. Ele irá apresentar a você um exemplo de abertura de seu projeto em um codespace e adicionar e modificar uma configuração de contêiner de desenvolvimento a partir de um modelo. - -#### Pré-requisitos - -- Você deve ter um projeto Python existente em um repositório em {% data variables.product.prodname_dotcom_the_website %}. Se você não tiver um projeto, você poderá tentar este tutorial com o seguinte exemplo: https://github.com/2percentsilk/python-quickstart. -- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização. - -### Etapa 1: Abra o seu projeto em um codespace - -1. Acesse o repositório do seu projeto. Use o menu suspenso {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com Codespaces**. Se você não vir esta opção, seu projeto não está disponível para {% data variables.product.prodname_codespaces %}. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. Para criar um novo codespace, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - -Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu código possui muitas linguagens e tempos de execução, incluindo Node.js, JavaScript, Typescript, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. - -Você pode personalizar o seu codespace ajustando a quantidade de vCPUs e RAM, [adicionando dotfiles para personalizar seu ambiente](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)ou modificando as ferramentas e scripts instalados. - -{% data variables.product.prodname_codespaces %} usa um arquivo denominado `devcontainer.json` para armazenar configurações. Ao iniciar, {% data variables.product.prodname_codespaces %} usa o arquivo para instalar quaisquer ferramentas, dependências ou outro conjunto que possa ser necessário para o projeto. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -### Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo - -O contêiner de códigos padrão vem com a versão mais recente do Python, gerenciadores de pacotes (pip, Miniconda) e outras ferramentas comuns pré-instaladas. No entanto, recomendamos que você configure um contêiner personalizado para definir as ferramentas e scripts de que seu projeto precisa. Isso garantirá um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} do seu repositório. - -Para configurar seu projeto com um contêiner personalizado, você deverá usar um arquivo `devcontainer.json` para definir o ambiente. Em {% data variables.product.prodname_codespaces %}, você pode adicionar isto a partir de um modelo ou você pode criar o seu próprio. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Configurar espaços de códigos para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - - -1. Acesse a paleta de comandos (`shift comando P` / `shift control P`) e, em seguida, comece a digitar "dev container". Clique em **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** !["Codespaces: Adicionar arquivos de configuração de Contêiner de Desenvolvimento..." na paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. Para este exemplo, clique em **Python 3**. Se precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para Python ou uma combinação de ferramentas como Python 3 e PostgresSQL. ![Selecione a opção Python na lista](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Clique na versão recomendada do Python. ![Seleção de versão Python](/assets/images/help/codespaces/add-python-version.png) -4. Aceite a opção padrão para adicionar Node.js à sua personalização. ![Adicionar seleção de Node.js](/assets/images/help/codespaces/add-nodejs-selection.png) -5. Para reconstruir seu contêiner, acesse a paleta de comandos (`shift command P` / `shift control P`) e, em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomia do seu contêiner de desenvolvimento - -A adição do modelo de contêiner de desenvolvimento do Python adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos: - -- `devcontainer.json` -- arquivo Docker - -O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // Comment out connect as root instead. Mais informações: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Nome** - Você pode dar qualquer nome ao nosso contêiner de desenvolvimento. Este é apenas o padrão. -- **Build** - As propriedades de compilação. - - **Arquivo Docker** - No objeto de compilação, `arquivo Docker` é uma referência ao arquivo arquivo Docker que também foi adicionado a partir do template. - - **Args** - - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a variante de nó que queremos usar e que é passada para o arquivo Docker. -- **Configurações** - Estas são as configurações de {% data variables.product.prodname_vscode %}. - - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação. -- **Extensões** - Estas são extensões incluídas por padrão. - - **ms-python. ython** - A extensão Microsoft Python fornece um amplo suporte para a linguagem do Python (para todas as versões ativamente compatíveis da linguagem: >=3.), incluindo recursos como IntelliSense, linting, depuração, navegação de código, formatação de código, refatoração, explorador de variáveis, explorador de teste e muito mais. -- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente. -- **postCreateCommand** - Se você quiser executar qualquer coisa depois de pousar no seu codespace, isso não está definido no arquivo Docker como `pip3 install -r requirements`. Você pode fazer isso aqui. -- **remoteUser** - Por padrão, você está executando como usuário do `vscode`, mas, opcionalmente, você pode definir isso como `root`. - -##### arquivo Docker - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -Você pode usar o arquivo Docker para adicionar camadas adicionais de contêiner para especificar os pacotes do OS, versões de nó ou pacotes globais que queremos que sejam incluídos no nosso contêiner. - -### Etapa 3: Modifique seu arquivo devcontainer.json - -Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do que tudo faz, agora você pode fazer alterações para configurá-lo para o seu ambiente. Neste exemplo, você irá adicionar propriedades para instalar extensões e dependências do seu projeto quando o seu codespace for iniciado. - -1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. - - !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/devcontainers-options.png) - -2. Atualize a lista de extensões `` no seu arquivo `devcontainer.json` para adicionar algumas extensões que são úteis ao trabalhar com seu projeto. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Remova o comentário o `postCreateCommand` para instalar automaticamente os requisitos como parte do processo de configuração dos codespaces. - - ```json{:copy} - // Use 'postCreateCommand' para executar os comandos após a criação do contêiner. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. Para reconstruir seu contêiner e aplicar as alterações do devcontainer.json, acesse a paleta de comandos (`shift comando P` / `shift control P`). Em seguida, comece a digitar "recriar". Click **Codespaces: Rebuild Container**. - - ![Opção de reconstruir contêiner](/assets/images/help/codespaces/codespaces-rebuild.png) - - A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner. - -5. Verifique se suas alterações foram aplicadas com sucesso verificando se as extensões Code Spell Checker e Flask Snippet foram instaladas. - - ![Lista de extensões](/assets/images/help/codespaces/python-extensions.png) - -### Etapa 4: Execute o seu aplicativo - -Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes via pip3. Com suas dependências agora instaladas, você pode executar seu aplicativo. - -1. Execute seu aplicativo pressionando `F5` ou digitando `python -m Flask run` no terminal do codespace. - -2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa. - - ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/python-port-forwarding.png) - -### Etapa 5: Faça commit das suas alterações - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Próximas etapas - -Agora você deve estar pronto para começar a desenvolver seu projeto Python em {% data variables.product.prodname_codespaces %}. Aqui estão alguns recursos adicionais para cenários mais avançados. - -- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Encaminhar portas no seu código](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md b/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index b2758f02e6..0000000000 --- a/translations/pt-BR/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Primeiros passos com {% data variables.product.prodname_codespaces %}' -intro: 'Aprenda como dar os primeiros passos com {% data variables.product.prodname_codespaces %}, incluindo a configuração para linguagens específicas.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md deleted file mode 100644 index b636a380bc..0000000000 --- a/translations/pt-BR/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Guias de codespaces -shortTitle: Guias -intro: 'Aprenda a aproveitar ao máximo o GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/pt-BR/content/codespaces/index.md b/translations/pt-BR/content/codespaces/index.md deleted file mode 100644 index f116c2d0e6..0000000000 --- a/translations/pt-BR/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Documentação do GitHub Codespaces -beta_product: true -shortTitle: GitHub Codespaces -intro: 'Crie um codespace para começar a desenvolver em um ambiente seguro, configurável e dedicado de desenvolvimento que funcione como e onde você desejar.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index 1f1ff2585b..0000000000 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Gerenciando codespaces para a sua organização -intro: 'Você pode gerenciar e revisar como os usuários da sua organização podem usar {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index 5fe3cf097a..0000000000 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Gerenciar os codespaces de acesso e segurança da sua organização -shortTitle: Gerenciar o acesso e a segurança da sua organização -intro: 'Você pode gerenciar os repositórios na sua organização que {% data variables.product.prodname_codespaces %} pode acessar.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Os proprietários da organização podem gerenciar quais repositórios um codespace pode acessar. - -Por padrão, um codespace só pode acessar o repositório onde foi criado. Ao habilitar o acesso e a segurança de um repositório pertencente à sua organização, todos os codespaces que forem criados para esse repositório também terão permissões de leitura e gravação para todos os outros repositórios que a organização possui e o criador de codespace terá permissões para acessar. Se você deseja restringir os repositórios que um codespace pode acessar, você pode limitá-lo ao repositório em que o codespace foi criado ou a repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia. - -Para gerenciar quais usuários na sua organização podem usar {% data variables.product.prodname_codespaces %}, consulte "[Gerenciar permissões de usuário para a sua organização](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)". - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Em "Acesso e segurança", selecione a configuração que você deseja para a sua organização. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para permitir que os codespaces do repositório acessem outros repositórios pertencentes à sua organização. Repita isso para todos os repositórios cujos códigos você deseja que acessem outros repositórios. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index 92260550e5..0000000000 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Gerenciar segredos criptografados para o seu repositório e organização para codespaces -shortTitle: Gerenciar segredos para o seu repositório e organização -intro: 'Os segredos criptografados permitem que você armazene informações confidenciais na sua organização, repositório ou {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre segredos - -Segredos são variáveis de ambiente criptografadas que você cria em uma organização ou repositório. Os segredos que você criou estão disponíveis para uso em {% data variables.product.prodname_codespaces %}. O GitHub usa uma [caixa protegida pela libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para criptografar segredos antes que eles cheguem ao GitHub e só descriptografa quando você os usa em um codespace. - -Os segredos no nível da organização permitem que você compartilhe segredos entre vários repositórios, o que reduz a necessidade de criar segredos duplicados. Você pode usar políticas de acesso para controlar quais repositórios podem usar segredos da organização. - -{% data reusables.codespaces.secrets-on-start %} - -#### Nomeando segredos - -{% data reusables.codespaces.secrets-naming %} Por exemplo, um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório, e um segredo criado no nível da organização deve ter um nome exclusivo nesse nível. - - {% data reusables.codespaces.secret-precedence %} - -#### Limites para segredos - -Você pode armazenar até 100 segredos por organização e 100 segredos por repositório. - -Os segredos são limitados a 64 kB. - -### Adicionar segredos para um repositório - -Para criar segredos para um repositório da organização, você deve ter acesso de administrador. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Desça a barra de rolagem e, em **Segredos**, selecione **Codespaces**. ![Opção de codespace na barra lateral](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. Na parte superior da página, clique em **Novo segredo de repositório**. -1. Digite um nome para o seu segredo na caixa de entrada **Nome**. -1. Insira o valor para o seu segredo. -1. Clique em **Add secret** (Adicionar segredo). - -### Adicionar segredos para uma organização - -Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios. - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Desça a barra de rolagem e, em **Segredos**, selecione **Codespaces**. ![Opção de codespace na barra lateral](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. Na parte superior da página, clique em **Novo segredo de organização**. -1. Digite um nome para o seu segredo na caixa de entrada **Nome**. -1. Insira o **Valor** para o seu segredo. -1. Na lista suspensa **Acesso do repositório**, escolha uma política de acesso. ![Lista de Acesso ao Repositório com repositórios privados selecionados](/assets/images/help/codespaces/secret-repository-access.png) -1. Clique em **Add secret** (Adicionar segredo). - -### Rever o acesso para os segredos do nível da organização - -Você pode verificar quais políticas de acesso são aplicadas a um segredo na sua organização. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. A lista de segredos inclui quaisquer permissões e políticas configuradas. Por exemplo: ![Lista de segredos](/assets/images/help/settings/actions-org-secrets-list.png) -1. Para obter mais detalhes sobre as permissões configuradas para cada segredo, clique em **Atualizar**. diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index 632a2c1fcc..0000000000 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Gerenciar permissões de usuário para sua organização -intro: 'Você pode controlar quais usuários da sua organização podem usar {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre as permissões de usuário para {% data variables.product.prodname_codespaces %} - -Os proprietários da organização podem controlar quais usuários da sua organização podem criar e usar cdespaces. - -Para usar codespaces na sua organização, os usuários devem ter pelo menos acesso de gravação aos repositórios onde desejam usar o codespace. Você pode habilitar os codespaces para todos os usuários da sua organização ou apenas para usuários específicos. - -Por padrão, um codespace só pode acessar o repositório onde foi criado. Se você quiser que os codespaces na sua organização possam acessar outros repositórios da organização que o criador do codespace possa acessar, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". - -### Configurar quais usuários da sua organização podem usar {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Em "Permissões de usuário", selecione uma das seguintes opções: - - * **Desabilitado** para não permitir que nenhum integrante da organização use {% data variables.product.prodname_codespaces %}. - * **Permitir para todos os usuários** para permitir que todos os integrantes da sua organização usem {% data variables.product.prodname_codespaces %}. - * **Usuários selecionados** para selecionar integrantes específicos da organização para usar {% data variables.product.prodname_codespaces %}. - - ![Botões de opção para "Permissões do usuário"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index f6de804a4a..0000000000 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Revisando os logs de auditoria da sua organização para os codespaces -shortTitle: Revisando os logs de auditoria da sua organização -intro: 'Você pode usar o log de auditoria para revisar todas as ações relacionadas a {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -Quando qualquer integrante da sua organização executa uma ação relacionada a {% data variables.product.prodname_codespaces %}, você poderá revisar as ações no log de auditoria. Para obter informações sobre acesso ao registro, consulte "[Revisar seu log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)". - -![Log de auditoria com informações sobre codespaces](/assets/images/help/settings/codespaces-audit-log-org.png) - -O log de auditoria inclui detalhes como quem realizou a ação, qual foi a ação e quando a ação foi realizada. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 37f45202c0..0000000000 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Gerenciar seus codespaces -intro: 'Você pode usar as configurações de {% data variables.product.prodname_github_codespaces %} para gerenciar informações que seu codespace possa precisar.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 9e78cc2d97..0000000000 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Gerenciar os codespaces de acesso e segurança para os seus codespaces -intro: 'Você pode gerenciar os repositórios que {% data variables.product.prodname_codespaces %} pode acessar.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Ao habilitar o acesso e a segurança de um repositório pertencente à sua conta de usuário, todos os códigos que forem criados para esse repositório terão permissões de leitura e gravação em todos os outros repositórios que você possui. Se você deseja restringir os repositórios que um código pode acessar, você pode limitá-lo tanto para o repositório no qual o código foi aberto ou para repositórios específicos. Você só deve habilitar o acesso e a segurança para repositórios nos quais confia. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Em "Acesso e segurança", selecione a configuração que deseja para sua conta de usuário. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. Se você escolher "repositórios selecionados", selecione o menu suspenso e clique em um repositório para permitir que os codespaces do repositório tenham acesso a outros repositórios dos quais você é proprietário. Repita para todos os repositórios cujos codespaces você deseja que acessem outros repositórios dos quais você é proprietário. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index cec02842a1..0000000000 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Gerenciar segredos criptografados para seus codespaces -intro: 'Você pode armazenar informações confidenciais, como tokens, que você deseja acessar nos seus codespaces por meio de variáveis de ambiente.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### Sobre os segredos criptografados para {% data variables.product.prodname_codespaces %} - -Você pode adicionar segredos criptografados à sua conta de usuário que deseja usar nos seus codespaces. Por exemplo, você pode querer armazenar e acessar as seguintes informações confidenciais como segredos criptografados. - -- Tokens de acesso pessoal para os serviços da nuvem -- Entidades de serviço -- Identificadores da assinatura -- [Credenciais para um registro de imagens privado](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -Você pode escolher quais repositórios devem ter acesso a cada segredo. Em seguida, você pode usar o segredo em qualquer código que criar para um repositório que tiver acesso ao segredo. - -{% data reusables.codespaces.secrets-on-start %} - -#### Nomeando segredos - -{% data reusables.codespaces.secrets-naming %} Por exemplo, um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório. - - {% data reusables.codespaces.secret-precedence %} - -#### Limites para segredos - -Você pode armazenar até 100 segredos para {% data variables.product.prodname_codespaces %}. - -Os segredos são limitados a 64 kB. - -### Adicionar um segredo - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. À direita dos "Segredos dos codespaces", clique em **Novo segredo**. ![Botão "Novo segredo"](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Em "Nome", digite um nome para seu segredo. ![Caixa de texto "Nome"](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Clique em **Add secret** (Adicionar segredo). - -### Editar um segredo - -Você pode atualizar o valor de um segredo existente, bem como alterar quais repositórios podem acessar um segredo. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Em "Segredos do codespace", à direita do segredo que você deseja editar, clique em **Atualizar**. ![Botão "Atualizar"](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Em "Valor", clique em **Inserir um novo valor**. ![Link "Inserir um novo valor"](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Opcionalmente, para remover o acesso do segredo a um repositório, desmarque o repositório. ![Caixas de seleção para remover acesso aos repositórios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Clique em **Save changes** (Salvar alterações). - -### Excluir um segredo - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Em "Segredos dos codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Leia o alerta e clique em **OK**. ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index 5a604802b7..0000000000 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Gerenciar a verificação de GPG de codespaces -intro: 'Você pode permitir que {% data variables.product.company_short %} use o GPG automaticamente para assinar os commits que você faz nos seus codespaces para que outras pessoas possam confiar que as alterações vêm de uma fonte de confiança.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Depois que você habilitar a verificação do GPG, {% data variables.product.company_short %} assinará automaticamente os commits que você fizer em {% data variables.product.prodname_codespaces %}, e os commits terão um status de verificado em {% data variables.product.product_name %}. Por padrão, a verificação do GPG está desabilitada para os codespaces que você criar. Você pode optar por permitir a verificação do GPG para todos os repositórios ou repositórios específicos. Habilite apenas a verificação do GPG para repositórios nos quais você confia. Para obter mais informações sobre commits assinado por {% data variables.product.product_name %}, consulte "[Sobre a verificação de assinatura do commit](/github/authenticating-to-github/about-commit-signature-verification)". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Em "Verificação do GPG, selecione a configuração que deseja para verificação do GPG. ![Botões de opção para gerenciar a verificação do GPG](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para o qual deseja habilitar a verificação do GPG. Repita esse procedimento para todos os repositórios para os quais você deseja habilitar a verificação do GPG. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index 9a65963203..0000000000 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Revisando os logs de segurança dos codespaces -shortTitle: Revisando seus logs de segurança -intro: 'Você pode usar o log de segurança para revisar todas as ações relacionadas a {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre os logs de segurança de {% data variables.product.prodname_codespaces %} - -Quando você executar uma ação relacionada a {% data variables.product.prodname_codespaces %} em repositórios pertencentes à sua conta de usuário, você poderá revisar as ações no log de segurança. Para obter informações sobre acesso ao registro, consulte "[Revisar seu log de segurança](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)". - -![log de segurança com informações de codespaces](/assets/images/help/settings/codespaces-audit-log.png) - -O log de segurança inclui detalhes sobre qual ação ocorreu e quando você a executou. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/pt-BR/content/codespaces/quickstart.md b/translations/pt-BR/content/codespaces/quickstart.md deleted file mode 100644 index efc99504e0..0000000000 --- a/translations/pt-BR/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Início rápido para o GitHub Codespaces -intro: 'Experimente {% data variables.product.prodname_codespaces %} em 5 minutos ou menos.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### Introdução - -Neste guia, você criará um codespace a partir do [repositório de amostra](https://github.com/2percentsilk/haikus-for-codespaces) e explorará algumas das funcionalidades essenciais disponíveis para você dentro do codespace. - -O exemplo a seguir mostra como criar um codespace, conectar-se a uma porta encaminhada para visualizar o seu aplicativo de execução e personalizar sua configuração com extensões e dotfiles. - -### Criando seu codespace - -1. Acesse a página principal do [repositório de amostra](https://github.com/2percentsilk/haikus-for-codespaces). - -2. No nome do repositório, use o menu suspenso do {% octicon "download" aria-label="The download icon" %} **Código** e selecione **Abrir com os espaços de código**. - - ![Botão de abrir com codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. Para criar um codespace, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. - - ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - -### Execute o aplicativo - -Com o seu projeto aberto em um codespace, agora você pode executar o aplicativo e abri-lo em um navegador. - -1. Inicie o aplicativo digitando `npm run dev` no terminal. Este comando executa o script `dev` no arquivo package.json e inicia o aplicativo web definido no repositório de exemplo. - - ![npm run dev no terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa. - - ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Clique em **Abrir no navegador** para visualizar seu aplicativo em execução em uma nova aba. - -### Personalize com uma extensão de tema - -Dentro de um codespace, você tem acesso ao Marketplace do Visual Studio Code. Para este exemplo, você instalará uma extensão que altera o tema, mas você pode instalar qualquer extensão que seja útil para o seu fluxo de trabalho. - -1. Na barra lateral esquerda, clique no ícone Extensões. - -2. Na barra de pesquisa, digite `fairyfloss` e instale a extensão fairyfloss. - - ![Adicionar extensão](/assets/images/help/codespaces/add-extension.png) - -3. Selecione o tema `fairyfloss` selecionando-o na lista. - - ![Selecionar tema fairyfloss](/assets/images/help/codespaces/fairyfloss.png) - -4. Alterações feitas na sua configuração de editor no espaço do código atual, como ligações de tema e teclado, são sincronizadas automaticamente em outros códigos por meio de [Sincronizar configurações](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalizar com dotfiles - -Se a sua conta de usuário no GitHub possuir um dotfiles com nome de repositório público, o GitHub usará automaticamente esse repositório para personalizar seu ambiente de código durante a criação de um codespace. - -Este exemplo apresenta a você a criação de um repositório de dotfiles para os seus codespaces. - -1. Acesse a amostra do [repositório de dotfiles](https://github.com/aw-test-93/dotfiles/). - -2. Bifurque o repositório na sua conta e certifique-se de que seja público. - - Verifique se o repositório criado na sua conta tem o nome dotfiles, por exemplo `yourname/dotfiles`. Qualquer outro nome fará com que o {% data variables.product.prodname_codespaces %} ignore o repositório para personalização. - -3. Crie um novo codespace a partir do [repositório do aplicativo de amostra](https://github.com/2percentsilk/haikus-for-codespaces) já que as atualizações do dotfile só serão aplicadas no momento da criação. Os arquivos de exemplo irão alterar o prompt de comando para texto roxo e azul em negrito. - - ![Instrução de comando personalizado](/assets/images/help/codespaces/custom-prompt.png) - -### Próximos passos - -Você criou com sucesso, personalizou e executou seu primeiro aplicativo em um codespace, mas há muito mais para explorar! Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_codespaces %}. - - "[Guias dos primeiros passos](/codespaces/getting-started-with-codespaces)" para usar {% data variables.product.prodname_codespaces %} com linguagens específicas - - [Crie uma configuração personalizada](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) para configurar {% data variables.product.prodname_codespaces %} para o seu projeto. diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index 39e6656481..0000000000 --- a/translations/pt-BR/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -title: Configurar codespaces para seu projeto -intro: 'Você pode usar um arquivo `devcontainer.json` para definir um ambiente de {% data variables.product.prodname_codespaces %} para o seu repositório.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre contêineres de desenvolvimento - -Um contêiner de desenvolvimento, ou dev container, é o ambiente que {% data variables.product.prodname_codespaces %} usa para fornecer as ferramentas e tempos de execução de que seu projeto precisa para desenvolvimento. Ao trabalhar com um contêiner de desenvolvimento em {% data variables.product.prodname_codespaces %} você pode [usar a configuração padrão](#using-the-default-configuration), [usar uma configuração pré-definida](#using-a-pre-defined-container-configuration), ou [criar sua própria configuração](#creating-a-custom-codespace-configuration). A opção escolhida depende das ferramentas, tempo de execução, dependências e fluxos de trabalho que um usuário pode precisar para ter sucesso com seu projeto. - -{% data variables.product.prodname_codespaces %} permite a personalização em uma base por projeto e por branch com um arquivo `devcontainer.json`. Este arquivo de configuração determina o ambiente de cada novo codespace que alguém criar para o repositório, definindo um contêiner de desenvolvimento que pode incluir estruturas, ferramentas, extensões e encaminhamento de porta. Um arquivo Docker também pode ser usado ao lado do arquivo `devcontainer.json` na pasta `devcontainer` para definir tudo o que é necessário para criar uma imagem de contêiner. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -Você pode usar o seu `devcontainer.json` para definir as configurações padrão para todo o ambiente do codespace, incluindo o editor, mas você também pode definir configurações específicas do editor para áreas de trabalho individuais [](https://code.visualstudio.com/docs/editor/workspaces) em um codespace em um arquivo denominado `.vscode/settings.json`. - -Para obter informações sobre as configurações e propriedades que você pode definir em um `devcontainer.json`, consulte [referência do devcontainer.json](https://aka.ms/vscode-remote/devcontainer.json) na documentação de {% data variables.product.prodname_vscode %}. - -#### arquivo Docker - -Um arquivo Docker também mora na pasta `.devcontainer`. - -Você pode adicionar um arquivo Docker ao seu projeto para definir uma imagem de contêiner e instalar software. No arquivo Docker, você pode usar `DE` para especificar a imagem do contêiner. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -Você pode usar a instrução `EXECUTAR` para instalar qualquer software e `&&` para unir comandos. - -Faça referência ao seu arquivo Docker no arquivo `devcontainer.json` usando a propriedade `arquivo Docker`. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -Para obter mais informações sobre como usar um arquivo Docker em um contêiner de desenvolvimento, consulte [Criar um contêiner de desenvolvimento](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) na documentação de {% data variables.product.prodname_vscode %}. - -### Usando a configuração padrão - -Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um código com uma imagem-base do Linux. A imagem de base do Linux inclui linguagens e tempos de execução como Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby e Rust. Ela também inclui outras ferramentas e utilitários para desenvolvedores como git, GitHub CLI, yarn, openssh, e vim. Para ver todas as linguagens, tempos de execução e as ferramentas que são incluídas, use o comando `devcontainer-info content-url` dentro do seu terminal de código e siga a url que o comando emite. - -Como alternativa, para obter mais informações sobre tudo o que está incluído na imagem de base do Linux, consulte o arquivo mais recente no repositório [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). - -A configuração padrão é uma boa opção se você estiver trabalhando em um pequeno projeto que usa as linguagens e ferramentas que {% data variables.product.prodname_codespaces %} fornece. - - -### Usando uma configuração de contêiner predefinida - -Definições de contêiner predefinidas incluem uma configuração comum para um tipo específico de projeto e podem ajudar você rapidamente a dar os primeiros passos com uma configuração que já tem as opções de contêiner apropriadas, {% data variables.product.prodname_vscode %} configurações, e extensões de {% data variables.product.prodname_vscode %} que devem ser instaladas. - -Usar uma configuração predefinida é uma ótima ideia se você precisa de uma extensão adicional. Você também pode começar com uma configuração predefinida e alterá-la conforme necessário para a configuração do seu projeto. - -1. Para acessar a paleta de comando, no canto superior esquerdo, selecione o Menu de Aplicativos e clique em **Paleta de Comando…** no menu **Exibir** e, em seguida, comece a digitar "Codespaces: Adicionar arquivos de configuração do Container do Desenvolvimento...". Clique em **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** !["Codespaces: Adicionar arquivos de configuração de Contêiner de Desenvolvimento..." na paleta de comandos](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Clique na definição que você deseja usar. ![Lista de definições de contêiner predefinidas](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Siga as instruções para personalizar sua definição. -1. Clique em **OK**. ![Botão OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. Para aplicar as alterações, no canto inferior direito da tela, clique em **Reconstruir agora**. Para obter mais informações sobre a reconstrução do seu contêiner, consulte "[Aplicar alterações na sua configuração](#applying-changes-to-your-configuration)". !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/rebuild-prompt.png) - - -### Criar uma configuração personalizada de codespace - -Se nenhuma das configurações predefinidas atender às suas necessidades, você poderá criar uma configuração personalizada adicionando um arquivo `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} - -No arquivo, você pode usar [chaves de configuração compatíveis](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) para especificar aspectos do ambiente do código, como quais extensões de {% data variables.product.prodname_vscode %} serão instaladas. - -{% data reusables.codespaces.vscode-settings-order %} - -Você pode definir as configurações de editor-padrão para {% data variables.product.prodname_vscode %} em dois lugares. - -* As configurações do editor definidas em `.vscode/settings.json` são aplicadas como configurações do escopo do _espaço de trabalho_ no codespace. -* Configurações do editor definidas na chave `Configurações` no `devcontainer.json` são aplicadas como configuração de escopo _Remote [Codespaces]_ nesse codespace. - -Depois de atualizar o arquivo `devcontainer.json`, você poderá reconstruir o contêiner para o seu código aplicar as alterações. Para obter mais informações, consulte "[Aplicar alterações à sua configuração](#applying-changes-to-your-configuration)". - - - - -### Aplicando alterações à sua configuração - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -!["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Corrija os erros na configuração. ![Mensagem de erro sobre modo de recuperação](/assets/images/help/codespaces/recovery-mode-error-message.png) - - Para diagnosticar o erro revisando os registros de criação, clique em **Visualizar registro de criação**. - - Para corrigir os erros identificados nos registros, atualize seu arquivo devcontainer.json..
    • -
  • Para aplicar as alterações, reconstrua seu contêiner. {% data reusables.codespaces.rebuild-command %}
    • - diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index a7b5422d88..0000000000 --- a/translations/pt-BR/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Configurar seu codespace -intro: '{% data variables.product.prodname_codespaces %} é um ambiente dedicado a você. Você pode configurar seu codespace com um contêiner de desenvolvimento para instalar suas dependências ou você pode adicionar um dotfile para personalizar as configurações de usuário.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 7e26409864..0000000000 --- a/translations/pt-BR/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Personalizar os codespaces para a sua conta -intro: 'Você pode personalizar {% data variables.product.prodname_codespaces %} usando um repositório `dotfiles` em {% data variables.product.product_name %} ou usando Configurações de Sincronização.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### Sobre a personalização de {% data variables.product.prodname_codespaces %} - -Ao usar qualquer ambiente de desenvolvimento, a personalização das configurações e ferramentas para suas preferências e fluxos de trabalho é uma etapa importante. {% data variables.product.prodname_codespaces %} permite duas formas principais de personalizar seus codespaces. - -- [Configurações de sincronização](#settings-sync) - Você pode usar e compartilhar as configurações {% data variables.product.prodname_vscode %} entre {% data variables.product.prodname_codespaces %} e outras instâncias de {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) - Você pode usar um repositório `dotfiles` público para especificar scripts, preferências do shell e outras configurações. - -A personalização de {% data variables.product.prodname_codespaces %} aplica-se a qualquer codespace que você criar. - -Os mantenedores do projeto também podem definir uma configuração-padrão que se aplica a todos os codespaces de um repositório, criados por qualquer pessoa. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -### Configurações de sincronização - -A sincronização de configurações permite que você compartilhe configurações como configurações, atalhos de teclado, snippets, extensões e estado da interface de usuário entre as máquinas e instâncias de {% data variables.product.prodname_vscode %}. - -Sincronização de configurações encontra-se ativada por padrão. Para definir qualquer configuração, no canto inferior esquerdo da barra de atividades, selecione {% octicon "gear" aria-label="The gear icon" %} e clique em **As configurações de sincronização estão ativadas**. Na caixa de diálogo, você pode optar por configurar, mostrar configurações e dados ou desabilitar a sincronização de configurações. - -![Opção de configuração de sincronização no menu de gerenciamento](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -Para obter mais informações, consulte o [Guia de sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) na documentação de {% data variables.product.prodname_vscode %}. - -### Dotfiles - -Os Dotfiles são arquivos e pastas de sistemas de tipo Unix, que começam com `.` e controlam a configuração de aplicativos e shells no seu sistema. Você pode armazenar e gerenciar seus dotfiles em um repositório no {% data variables.product.prodname_dotcom %}. Para obter aconselhamento e tutoriais sobre o que incluir no repositório `dotfiles`, consulte [GitHub gerencia dotfiles](https://dotfiles.github.io/). - -Se sua conta de usuário no {% data variables.product.prodname_dotcom %} possui um repositório público denominado `dotfiles`, o {% data variables.product.prodname_dotcom %} usa este repositório automaticamente para personalizar seu ambiente de codespace. Atualmente, não são compatíveis os repositórios privados `dotfiles`. - -O seu repositório `dotfiles` pode incluir os alias e preferências do seu shell, quaisquer ferramentas que você deseja instalar ou qualquer outra personalização de codespace que desejar fazer. - -Ao criar um novo codespace, o {% data variables.product.prodname_dotcom %} clona seus repositórios de `dotfiles` para o ambiente do codespace e procura por um dos seguintes arquivos para configurar o ambiente. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -Se nenhum desses arquivos for encontrado, quaisquer arquivos ou pastas nos `dotfiles` que comecem com `.` será vinculado simbolicamente ao diretório `~` ou `$HOME` do codespace. - -Quaisquer alterações no repositório de `dotfiles` serão aplicadas apenas a cada novo codespace e não afetarão nenhum codespace existente. - -{% note %} - -**Observação:** Atualmente, o {% data variables.product.prodname_codespaces %} não é compatível com a personalização das configurações do _Usuário_ para o editor de {% data variables.product.prodname_vscode %} com o repositório `dotfiles`. É possível definir as configurações-padrão do _espaço de trabalho_ e _Remote [Codespaces]_ para um projeto específico no repositório do projeto. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codespaces %} para seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)". - -{% endnote %} - -Você também pode definir as configurações para que a sua conta de usuário adicione segredos criptografados, habilitar a verificação de GPG e permitir que os seus codespaces acessem outros repositórios. Para obter mais informações, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Gerenciar verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)" e "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". - -### Leia mais - -* "[Criar um repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/pt-BR/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/pt-BR/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 20d799122a..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} é grátis para usar durante a beta. Quando {% data variables.product.prodname_codespaces %} se torna geralmente disponível, você será cobrado para armazenamento e uso de computação. diff --git a/translations/pt-BR/data/reusables/codespaces/about-configuration.md b/translations/pt-BR/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 1435705ccf..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -Você pode criar uma configuração padrão de codespace para o seu repositório que determina o ambiente de cada novo codespace que alguém criar para esse repositório. A configuração define um contêiner de desenvolvimento que pode incluir estruturas, ferramentas, extensões e encaminhamento de porta. diff --git a/translations/pt-BR/data/reusables/codespaces/about-personalization.md b/translations/pt-BR/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index 067c6e3fee..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. A personalização pode incluir preferências de shell e ferramentas adicionais. diff --git a/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md b/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 39b29dc4a0..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -You can forward ports in your codespace to test and debug your application. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 8031bfb4af..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/beta-functionality-limited.md b/translations/pt-BR/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 1dfa5d641f..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -Durante a beta, a funcionalidade é limitada. -- {% data reusables.codespaces.use-chrome %} -- Apenas um tamanho único de espaço de código está disponível. -- Somente os contêineres Linux são suportados. -- Um codespace não é totalmente recuperável. Os processos que estavam em execução no momento em que o código foi interrompido não serão reiniciados. diff --git a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index c45d078f12..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. Em {% data variables.product.prodname_vscode %}, na barra lateral esquerda, clique no ícone Remote Explorer. ![O ícone do Remote Explorer em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/codespace-config-order.md b/translations/pt-BR/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index 41081172b3..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Sua personalização `dotfiles` é aplicada antes da configuração de código padrão de um repositório. diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/pt-BR/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index aaee1d9d17..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Cada código é associado a um branch específico de um repositório. diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-are-personal.md b/translations/pt-BR/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 9d77e536f7..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Cada espaço de código que criar só está disponível para você. Ninguém mais pode trabalhar no seu espaço de código. diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md b/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index b66b4193f5..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Cada uma delas tem um nível diferente de recursos e uma camada diferente de cobrança.{% note %} - -**Observação:** {% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types: - -* **Basic** for updating a file and raising a pull request -* **Standard** for editing a website -* **Premium** for high compute tasks such as data analysis diff --git a/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md b/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 87bfa539ff..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users. - -For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index 477b0489b1..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. No entanto, cada conta de usuário tem um limite de dois codespaces durante um beta público limitado. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. diff --git a/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index be18129c85..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -Você pode se conectar ao seu código diretamente de {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Usar codespaces no {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". diff --git a/translations/pt-BR/data/reusables/codespaces/devcontainer-location.md b/translations/pt-BR/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index 5af86ddcf1..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -Este arquivo pode ser localizado na raiz do repositório ou em uma pasta denominada `.devcontainer`. Se o arquivo estiver localizado na raiz do repositório, o nome do arquivo deve começar com um ponto: `.devcontainer.json`. diff --git a/translations/pt-BR/data/reusables/codespaces/navigate-to-codespaces.md b/translations/pt-BR/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index a85e3a30f6..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. Na parte superior da página, clique em **Codespaces**. ![{% data variables.product.prodname_codespaces %} link no cabeçalho](/assets/images/help/codespaces/header-link.png) diff --git a/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index fed860897b..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/pt-BR/data/reusables/codespaces/rebuild-command.md b/translations/pt-BR/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index ea9e45b032..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/recovery-mode.md b/translations/pt-BR/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index fa4e73d013..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/release-stage.md b/translations/pt-BR/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 50df2085af..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Observação:** {% data variables.product.prodname_codespaces %} está atualmente em versão beta pública limitada e sujeito a alterações. Para obter mais informações sobre fontes de publicação, consulte "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." - -{% endnote %} diff --git a/translations/pt-BR/data/reusables/codespaces/secret-precedence.md b/translations/pt-BR/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index d5102fd3fa..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -Se existir um segredo com o mesmo nome em vários níveis, o segredo no nível inferior tem prioridade. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/secrets-naming.md b/translations/pt-BR/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index 0b93679cdf..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -As regras a seguir aplicam-se aos nomes dos segredos: - -* Os nomes dos segredos podem conter apenas caracteres alfanuméricos (`[a-z]`, `[A-Z]`, `[0-9]`) or sublinhado (`_`). Não são permitidos espaços. -* Os nomes dos segredos não devem começar com o prefixo `GITHUB_`. -* Os nomes dos segredos não devem começar com um número. -* Nomes dos segredos não diferenciam maiúsculas de minúsculas. -* Os nomes dos segredos devem ser únicos no nível em que são criados. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md b/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index c4a5bf3b41..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md b/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index 90b3503dcd..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-display.md b/translations/pt-BR/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index 09917cd3c8..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. - - ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/type-port-label.md b/translations/pt-BR/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 498c9eb752..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/unsupported-repos.md b/translations/pt-BR/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index ee7d7ce651..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -Durante o beta, repositórios privados pertencentes a organizações ou quaisquer repositórios pertencentes a uma organização que exijam um único login SAML, não são suportados. diff --git a/translations/pt-BR/data/reusables/codespaces/use-chrome.md b/translations/pt-BR/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index cc675512cc..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -Para a melhor experiência com {% data variables.product.prodname_codespaces %}, recomendamos o uso de um navegador baseado no Chromium, como o Google Chrome ou a Microsoft Edge. diff --git a/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md b/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index 428e0b5879..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -Você pode editar código, depurar e usar comandos do Git ao mesmo tempo que faz o desenvolvimento em um codespace com {% data variables.product.prodname_vscode %}. For more information, see the [{% data variables.product.prodname_vscode %} documentation](https://code.visualstudio.com/docs). diff --git a/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md b/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 56dc36a4e4..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -Ao configurar as configurações de editor para {% data variables.product.prodname_vscode %}, há três escopos disponíveis: _Workspace_, _Remote [Codespaces]_, e _User_. Se uma configuração for definida em vários escopos, as configurações do _Workspace_ têm prioridade e, em seguida _Remote [Codespaces]_, depois _User_. diff --git a/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index afb626e71c..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index a5e98437c0..0000000000 --- a/translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**. - - !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/gated-features/codespaces.md b/translations/pt-BR/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 08708dce57..0000000000 --- a/translations/pt-BR/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Os espaços de códigos estão disponíveis para contas de usuário usando {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/pt-BR/data/reusables/organizations/click-codespaces.md b/translations/pt-BR/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index ff78601d0b..0000000000 --- a/translations/pt-BR/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. Na barra lateral esquerda, clique em **Codespaces**. ![Aba "Codespaces" na barra lateral esquerda](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index b534205357..0000000000 --- a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecione o menu suspenso "Acesso ao repositório" e, em seguida, clique em um repositório que você quer que tenha acesso ao segredo. Repita esse procedimento para cada repositório que você quer que tenha acesso ao segredo. ![Menu suspenso "Acesso ao repositório"](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md b/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index 4f3a6b3291..0000000000 --- a/translations/pt-BR/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. Em "Valor", digite o valor do seu segredo. ![Caixa de texto "Valor"](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md b/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index 7a99dc6de4..0000000000 --- a/translations/pt-BR/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Na barra lateral esquerda, clique em **Codespaces**. ![Aba de codespaces na barra lateral de configurações do usuário](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/ru-RU/content/codespaces/about-codespaces.md b/translations/ru-RU/content/codespaces/about-codespaces.md deleted file mode 100644 index b7fc37f8ef..0000000000 --- a/translations/ru-RU/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: About Codespaces -intro: '{% data variables.product.prodname_codespaces %} is a configurable online development environment, hosted by {% data variables.product.prodname_dotcom %} and powered by {% data variables.product.prodname_vscode %}, that allows you to develop entirely in the cloud.' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} is a configurable cloud development environment available in your browser on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -![An open codespace](/assets/images/help/codespaces/codespace-overview.png) - -A codespace includes everything developers need to develop for a specific repository, including the {% data variables.product.prodname_vscode %} editing experience and common languages, tools, and utilities. {% data variables.product.prodname_codespaces %} is completely configurable, allowing you to create a customized development environment for your project, and allowing developers to personalize their experience with extensions and dotfile settings. - -Codespaces offers many benefits to teams by allowing for a consistent environment across your entire team, fast onboarding, and creating a secure space for development. - -### A consistent environment - -You can create a single codespace configuration that defines the environment (or _dev container_) of every new codespace that anyone creates for your repository. Once you've made a configuration, developers don’t have to worry about installing the right tools to comment, review, or contribute. A standardized environment is already available for them as soon as they create a codespace from the repository. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -For help getting started with configurations for specific languages, see the [Getting Started](/codespaces/getting-started-with-codespaces) tutorials. - -While every codespace created from your repository has a consistent development environment, developers can use {% data variables.product.prodname_codespaces %} wherever they need it – on {% data variables.product.prodname_dotcom %} or through {% data variables.product.prodname_vscode %}. - -### Fast and personal onboarding - -With a [dev container](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers) configured in your repository, any new developer can quickly onboard with the correct development environment for your project by using the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and selecting **Open with Codespaces**. - -![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -As a result of standardizing on a repeatable developer environment, developers can get started with a new codespace without doing any manual configuration and do not need to do continued maintenance of their developer environment. A new codespace can be created when starting a new feature. - -Developers can also personalize aspects of their codespace environment by using a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and extensions, such as Live Share. Personal customizations are stored on a per-user basis, so every codespace a developer opens has their environment ready to go. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - -Because {% data variables.product.prodname_codespaces %} can be accessed in the browser, developers can work on multiple projects by switching between tabs. - -### A secure environment - -{% data variables.product.prodname_codespaces %} allows developers to develop in the cloud instead of locally. This creates one single, trackable, source of truth. Developers can contribute from anywhere, on any machine, including tablets or Chromebooks, and there is no need to maintain local copies of intellectual property. Developers always have to be logged in and provided with access to both {% data variables.product.prodname_codespaces %} and specific repositories. These permissions can be revoked at any time. As soon as you revoke access, those developers will lose all access to protected resources. In addition, authenticated developers create audit trails so you know who is doing what. For more information on access and security, see "[Managing access and security for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -Using {% data variables.product.prodname_codespaces %} is the most secure when all members of your team are using it. It means that there is no need to clone the repository onto a local machine and that developers don't need to install locally as `root`. - -Developers and organization administrators can also configure settings to add encrypted secrets and enable GPG verification. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". - -### About billing for {% data variables.product.prodname_codespaces %} - -{% data reusables.codespaces.about-billing-for-codespaces %} For more information, see "[About billing for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-billing-for-codespaces)." - -### Joining the beta - -A limited number of people will be invited to join the beta. To join the waitlist, see [Sign up for the Codespaces beta](https://github.com/features/codespaces/signup). - -### Contacting us about {% data variables.product.prodname_codespaces %} - -If you encounter problems using {% data variables.product.prodname_codespaces %}, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -If you still need help or have feedback about {% data variables.product.prodname_codespaces %}, use the [Codespaces Feedback](https://github.com/github/feedback/discussions/categories/codespaces-feedback) discussion. diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index f621a80494..0000000000 --- a/translations/ru-RU/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: About billing for Codespaces -intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -Updates on the billing model for Codespaces will be shared in an upcoming announcement. diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index 75be9e6f73..0000000000 --- a/translations/ru-RU/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Allowing your codespace to access a private image registry -intro: 'You can use secrets to allow {% data variables.product.prodname_codespaces %} to access a private image registry' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -A registry is a secure space for storing and managing private container images, such as Azure Container Registry or DockerHub. You can create secrets in GitHub to store the access details for a private registry and use them to give your codespace access to images stored in the registry. - -When you launch a codespace, {% data variables.product.prodname_codespaces %} checks for three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_codespaces %} will make the registry available inside your codespace. - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -You can store secrets at the user, repository, or organization-level, allowing you to share them securely between different codespaces. When you create a set of secrets for a private image registry, you need to replace the “<*>” in the name with a consistent identifier. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" and "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)." - -For example, if you had a private image registry in Azure, you could create the following secrets: - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/index.md b/translations/ru-RU/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index 2aef87d83a..0000000000 --- a/translations/ru-RU/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Reference -intro: 'This section contains references that will allow you to be successful with {% data variables.product.prodname_codespaces %}' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index 6284b0674a..0000000000 --- a/translations/ru-RU/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Troubleshooting your codespace -intro: Use this guide to help you troubleshoot common issues with your codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Known Limitations - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### {% data variables.product.prodname_vscode %} troubleshooting - -Use **Issues** in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository to check for known issues or to log issues about the {% data variables.product.prodname_vscode %} experience. - - -### Configuration troubleshooting - -{% data reusables.codespaces.recovery-mode %} - -``` -This codespace is currently running in recovery mode due to a container error. -``` - -Review the creation logs, update the configuration as needed, and run **Codespaces: Rebuild Container** in the command palette to retry. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -### dotfiles troubleshooting - -- Make sure your dotfiles repository is public. If you have secrets or sensitive data you want to use in your codespace, use [Codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) instead of private dotfiles. -- Check `/workspaces/.codespaces/.persistedshare/dotfiles` to see if your dotfiles were cloned. - - If your dotfiles were cloned, try manually re-running your install script to verify it's executable. - - If your dotfiles weren't cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -- Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. Alternatively, you can view the `creation.log` by navigating to the command palette and entering **Codespaces: View Creation Log**. - - -### Browser troubleshooting - -If you encounter issues while using a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as[`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). - -If you encounter issues while using a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository. - -### Container storage troubleshooting - -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 any of the following items to free up storage space. - -- Remove packages that are no longer by using `sudo apt autoremove` -- Clean the apt cache by using `sudo apt clean` -- Delete unneeded files like build artifacts and logs (these are very project-dependent) -- See the top 10 largest files in the codespace: `sudo find / -printf '%s %p\n'| sort -nr | head -10` - -More destructive options: -- 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` - -### Contact us - -If you still need help, you can contact us. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)." diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index 19fc36dfc5..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Creating a codespace -intro: You can create a codespace for a branch in a repository to develop online. -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About codespace creation - -You can create a codespace on either {% data variables.product.prodname_dotcom_the_website %} or in {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.codespaces-are-personal %} - -Codespaces are associated with a specific branch of a repository and the repository cannot be empty. {% data reusables.codespaces.concurrent-codespace-limit %} For more information, see "[Deleting a codespace](/github/developing-online-with-codespaces/deleting-a-codespace)." - - -When you create a codespace, a number of steps happen to enable full access to your development environment. - -- Resources such as a VM and storage for your container are assigned. A new VM is created every time you create or start a codespace to ensure that you always have the latest versions and security patches. -- {% data variables.product.prodname_codespaces %} recieves information about your repository, branch, commits, your public dotfiles repository, and any secrets that you have created. -- {% data variables.product.prodname_codespaces %} executes a shallow clone of the repository. -- If you have one in your repository, {% data variables.product.prodname_codespaces %} runs the `devcontainer.json` file. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." -- Your Docker container, `docker-compose`, or other initialization is run. -- At this point, the codespace is marked as available and you can connect. -- Once the codespace is made available, depending on the commands in the devcontainer, the codespace will continue with some set up. - - The codespace shares ports added in the `devcontainer.json` file. - - The codespace runs anything specified in `postCreateCommand`. - - {% data variables.product.prodname_codespaces %} clones your dotfiles repository to the codespaces environment and looks for an install file. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." - - Finally, the codespace does a full clone of the repo so you have full access to it. - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Creating a codespace - -{% data reusables.repositories.navigate-to-repo %} -2. Under the repository name, use the "Branch" drop-down menu, and select the branch you want to create a codespace for. - - ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png) - -3. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. To create a codespace using a Standard machine type, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index 7140114c9f..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Deleting a codespace -intro: You can delete a codespace you no longer need. -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. Navigate to the repository where you created the codespace. Select **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces** and then click {% octicon "gear" aria-label="The Settings gear" %}. This will display all {% data variables.product.prodname_codespaces %} that you have created in the repository. ![Codespaces tab](/assets/images/help/codespaces/codespaces-manage.png) - - Alternatively, you can see every codespace owned by your user account at [github.com/codespaces](https://github.com/codespaces). - -2. 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** ![Delete button](/assets/images/help/codespaces/delete-codespace.png) - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -For information on deleting a codespace in {% data variables.product.prodname_vscode %}, see "[Using Codespaces in Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)." \ No newline at end of file diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index a3ae678e34..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Developing in a codespace -intro: 'You can open a codespace on {% data variables.product.product_name %}, then develop using {% data variables.product.prodname_vscode %}''s features.' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About development with {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %} - -![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. Side Bar - By default, this area shows your project files in the Explorer. -2. Activity Bar - This displays the Views and provides you with a way to switch between them. You can reorder the Views by dragging and dropping them. -3. Editor - This is where you edit your files. You can use the tab for each editor to position it exactly where you need it. -4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. -5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. - -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting your codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)." - -#### Personalizing your codespace - -{% data reusables.codespaces.about-personalization %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)." - -{% data reusables.codespaces.apply-devcontainer-changes %} For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." - -#### Running your app from a codespace -{% data reusables.codespaces.about-port-forwarding %} For more information, see "[Forwarding ports in your codespace](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)." - -#### Committing your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Navigating to an existing codespace - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. Click the name of the codespace you want to develop in. ![Name of codespace](/assets/images/help/codespaces/click-name-codespace.png) - -Alternatively, you can see any active codespaces for a repository by navigating to the repository in which it was made and selecting **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**. diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 7965bfc793..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Forwarding ports in your codespace -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About forwarded ports - -Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000, you can access the application from your browser to test and debug the application. - -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal to open the port in a browser. For example, if an application outputs `http://127.0.0.1:4000` or `http://localhost:4000` to the console, the log would automatically convert the output to a clickable URL for port 4000. - -![Automatic port forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) - -You can also forward a port manually, label forwarded ports, share fowarded ports publicly, and add forwarded ports to the codespace configuration. - -### Forwarding a port - -You can manually forward a port that wasn't forwarded automatically. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Under the list of ports, click **Add port**. ![Add port button](/assets/images/help/codespaces/add-port-button.png) -1. Type the port number or address, then press enter. ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png) - -### Labeling a port - -You can label a port to make the port more easily identifiable in a list. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Hover over the port you want to label, then click the label icon. ![Label icon for port](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### Sharing a port - -If you want to share a forwarded port with others, you can make the port public. After you make a port public, anyone with the port's URL can view the running application without needing to authenticate. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to share, then click **Make Public**. ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png) -1. To the right of the local address for the port, click the copy icon. ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png) -1. Send the copied URL to the person you want to share the port with. - -### Adding a port to the codespace configuration - -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -You can manually configure fowarded ports in a `.devcontainer.json` file using the `forwardPorts` property, or you can use the "Ports" panel in your codespace. - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. Right click the port you want to add to the codespace configuration, then click **Set Label and Update devcontainer.json**. ![Option to set label and add port to devcontainer.json in the right-click menu](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index 555995eabc..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Developing in a codespace -intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use forwarded ports to run your application and even use codespaces inside {% data variables.product.prodname_vscode %}' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index 3cac79d040..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Using Codespaces in Visual Studio Code -intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### Требования - -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. - -Use the {% data variables.product.prodname_vs %} 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 %} documentation. - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -4. Sign in to {% data variables.product.product_name %} to approve the extension. - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**. ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -5. Sign in to {% data variables.product.product_name %} to approve the extension. - -{% endwindows %} - -### Creating a codespace in {% data variables.product.prodname_vscode %} - -After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_github_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}. - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the machine type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) -### Opening a codespace in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Under "Codespaces", click the codespace you want to develop in. -3. Click the Connect to Codespace icon. ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### Changing the machine type in {% data variables.product.prodname_vscode %} - -{% data reusables.codespaces.codespaces-machine-types %} - -You can change the machine type of your codespace at any time. - -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). -2. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. Click the codespace that you want to change. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Choose the machine type you want to use. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -If the codespace is currently running, a message is displayed asking if you would like to restart and reconnect to your codespace now. Click **Yes** if you want to change the machine type used for this codespace immediately. If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. - -### Deleting a codespace in {% data variables.product.prodname_vscode %} - -1. Under "Codespaces", right-click the codespace you want to delete. -2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index 0754b0ad6d..0000000000 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -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.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### About source control in {% data variables.product.prodname_codespaces %} - -You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the 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. - -Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." - -A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: - -* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." -* In your codespace, create a new branch to work on. -* Make your changes and save them. -* Commit the change. -* Raise a pull request. - -### Creating or switching branches - -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**Tip**: If someone has changed a file on the remote repository, in the branch you switched to, you will not see those changes until you pull the changes into your codespace. - -{% endtip %} - -### Pulling changes from the remote repository - -You can pull changes from the remote repository into your codespace at any time. - -{% data reusables.codespaces.source-control-display-dark %} -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. In the drop-down menu, click **Pull**. - -If a dev container has been changed since you created the codespace you can apply the changes by rebuilding the container for the codespace. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." - -### Setting your codespace to automatically fetch new changes - -You can set your codespace to automatically fetch details of any new commits that have been made to the remote repository. This allows you to see whether your local copy of the repository is out of date, in which case you may choose to pull in the new changes. - -If the fetch operation detects new changes on the remote repository, you'll see the number of new commits in the status bar. You can then pull the changes into your local copy. - -1. Click the **Manage** button at the bottom of the Activity Bar. ![Manage button](/assets/images/help/codespaces/manage-button.png) -1. In the menu, slick **Settings**. -1. On the Settings page, search for: `autofetch`. ![Search for autofetch](/assets/images/help/codespaces/autofetch-search.png) -1. To fetch details of updates for all remotes registered for the current repository, set **Git: Autofetch** to `all`. ![Enable Git autofetch](/assets/images/help/codespaces/autofetch-all.png) -1. If you want to change the number of seconds between each automatic fetch, edit the value of **Git: Autofetch Period**. - -### Committing your changes - -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### Raising a pull request - -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Click **Create**. - -### Pushing changes to your remote repository - -You can push the changes you've made. 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 %}. - -1. At the top of the side bar, click the ellipsis (**...**). ![Ellipsis button for View and More Actions](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. In the drop-down menu, click **Push**. diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index 4b7bfcf855..0000000000 --- a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Getting started with your C# (.NET) project in Codespaces -shortTitle: Getting started with your C# (.NET) project -allowTitleToDifferFromFilename: true -intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your C# (.NET) project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Требования - -- 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_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest .NET version and common tools preinstalled. However, we encourage you to set up a custom container so you can tailor the tools and scripts that run as part of codespace creation to your project's needs and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 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. ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. Click the recommended version of .NET. ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Файл Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - You can name our dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, `dockerfile` is a reference to the Dockerfile that was also added from the template. - - **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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `dotnet restore`, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Файл Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and restore your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed. - - ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via pip3. With our dependencies now installed, we can run our application. - -1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Дальнейшие шаги - -You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index 8169ac2a3e..0000000000 --- a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Getting started with your Java project in Codespaces -shortTitle: Getting started with your Java project -intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your Java project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Требования - -- You should have an existing Java 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/microsoft/vscode-remote-try-java -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Java, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions. ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. Click the recommended version of Java. ![Java version selection](/assets/images/help/codespaces/add-java-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Файл Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Файл Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`. - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) on the Visual Studio Code docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm. - -1. Run your application by pressing `F5`. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Дальнейшие шаги - -You should now be ready start developing your Java project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index fe41bc2570..0000000000 --- a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: Getting started with your Node.js project in Codespaces -shortTitle: Getting started with your Node.js project -intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Требования - -- You should have an existing JavaScript, Node.js, or TypeScript 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/microsoft/vscode-remote-try-node -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. By setting up a custom container you can customize the tools and scripts that run as part of codespace creation and ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. For this example, click **Node.js**. If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB. ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. Click the recommended version of Node.js. ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Файл Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - You can name your dev container anything, this is just the default. -- **Build** - The build properties. - - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **Settings** - These are {% data variables.product.prodname_vscode %} settings that you can set. - - **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. - - **Dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include. -- **forwardPorts** - Any ports listed here will be forwarded automatically. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, you can do that here. -- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root. - -##### Файл Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our Dockerfile. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally. - -1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to exand the `.devcontainer` folder to see it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Add the following lines to your `devcontainer.json` file after `extensions`: - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - For more information on `devcontainer.json` properties, see the [devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) in the {% data variables.product.prodname_vscode %} docs. - -3. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm. - -1. Run your start command in the terminal with`npm start`. - - ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Дальнейшие шаги - -You should now be ready start developing your JavaScript project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index 9df77249c6..0000000000 --- a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: Getting started with your Python project in Codespaces -shortTitle: Getting started with your Python project -intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -This guide shows you how to set up your Python project in {% data variables.product.prodname_codespaces %}. It will take you through an example of opening your project in a codespace, and adding and modifying a dev container configuration from a template. - -#### Требования - -- You should have an existing Python 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/python-quickstart. -- You must have {% data variables.product.prodname_codespaces %} enabled for your organization. - -### Step 1: Open your project in a codespace - -1. Navigate to your project's repository. Use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. If you don’t see this option, your project isn’t available for {% data variables.product.prodname_codespaces %}. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. To create a new codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -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 Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano. - -You can customize your codespace by adjusting the amount of vCPUs and RAM, [adding dotfiles to personalize your environment](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account), or by modifying the tools and scripts installed. - -{% data variables.product.prodname_codespaces %} uses a file called `devcontainer.json` to store configurations. On launch {% data variables.product.prodname_codespaces %} uses the file to install any tools, dependencies, or other set up that might be needed for the project. For more information, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -### Step 2: Add a dev container to your codespace from a template - -The default codespaces container comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you set up a custom container to define the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_codespaces %} users in your repository. - -To set up your project with a custom container, you will need to use a `devcontainer.json` file to define the environment. In {% data variables.product.prodname_codespaces %} you can add this either from a template or you can create your own. For more information on dev containers, see "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)." - - -1. Access the command palette (`shift command P` / `shift control P`), then start typing "dev container". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgresSQL. ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. Click the recommended version of Python. ![Python version selection](/assets/images/help/codespaces/add-python-version.png) -4. Accept the default option to add Node.js to your customization. ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png) -5. To rebuild your container, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### Anatomy of your dev container - -Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files: - -- `devcontainer.json` -- Файл Dockerfile - -The newly added `devcontainer.json` file defines a few properties that are described after the sample. - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // 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` is a reference to the Dockerfile that was also added from the template. - - **Args** - - **Variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile. -- **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-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), 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. -- **postCreateCommand** - If you want to run anything after you land in your codespace that’s not defined in the Dockerfile, like `pip3 install -r requirements`, you can do that here. -- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`. - -##### Файл Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 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. - -### Step 3: Modify your devcontainer.json file - -With your dev container added and a basic understanding of what everything does, you can now make changes to configure it for your environment. In this example, you'll add properties to install extensions and your project dependancies when your codespace launches. - -1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it. - - !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/devcontainers-options.png) - -2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project. - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process. - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. To rebuild your container and apply the devcontainer.json changes, access the command palette (`shift command P` / `shift control P`), then start typing "rebuild". Click **Codespaces: Rebuild Container**. - - ![Rebuild container option](/assets/images/help/codespaces/codespaces-rebuild.png) - - Rebuilding inside your codespace ensures your changes work as expected before you commit the changes to the repository. If something does result in a failure, you’ll be placed in a codespace with a recovery container that you can rebuild from to keep adjusting your container. - -5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed. - - ![Extensions list](/assets/images/help/codespaces/python-extensions.png) - -### Step 4: Run your application - -In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application. - -1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal. - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png) - -### Step 5: Commit your changes - -{% data reusables.codespaces.committing-link-to-procedure %} - -### Дальнейшие шаги - -You should now be ready start developing your Python project in {% data variables.product.prodname_codespaces %}. Here are some additional resources for more advanced scenarios. - -- [Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [Managing GPG verification for {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md b/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index 396851c0bb..0000000000 --- a/translations/ru-RU/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 'Getting Started with {% data variables.product.prodname_codespaces %}' -intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/guides.md b/translations/ru-RU/content/codespaces/guides.md deleted file mode 100644 index 8c3032ac5a..0000000000 --- a/translations/ru-RU/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Codespaces guides -shortTitle: Руководства -intro: 'Learn how to make the most of GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/ru-RU/content/codespaces/index.md b/translations/ru-RU/content/codespaces/index.md deleted file mode 100644 index d7c9926f2c..0000000000 --- a/translations/ru-RU/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: GitHub Codespaces Documentation -beta_product: true -shortTitle: GitHub Codespaces -intro: 'Create a codespace to start developing in a secure, configurable, and dedicated development environment that works how and where you want it to.' -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index 7d7055b862..0000000000 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Managing Codespaces for your organization -intro: 'You can manange and review how users in your organization can use {% data variables.product.prodname_github_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index f3d0f9eb29..0000000000 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Managing access and security for your organization's codespaces -shortTitle: Managing access and security for your organization -intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -Organization owners can manage which repositories a codespace can access. - -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. - -To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index ac148f188a..0000000000 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Managing encrypted secrets for your repository and organization for Codespaces -shortTitle: Managing secrets for your repository and organization -intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_codespaces %}.' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### About secrets - -Secrets are encrypted environment variables that you create in an organization or repository. The secrets that you create are available to use in {% data variables.product.prodname_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace. - -Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level. - - {% data reusables.codespaces.secret-precedence %} - -#### Limits for secrets - -You can store up to 100 secrets per organization and 100 secrets per repository. - -Secrets are limited to 64 KB in size. - -### Adding secrets for a repository - -To create secrets for an organization repository, you must have administrator access. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. At the top of the page, click **New repository secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the value for your secret. -1. Click **Add secret**. - -### Adding secrets for an organization - -When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. Scroll down the page and under **Secrets**, select **Codespaces**. ![Codespaces option in side bar](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. At the top of the page, click **New organization secret**. -1. Type a name for your secret in the **Name** input box. -1. Enter the **Value** for your secret. -1. From the **Repository access** dropdown list, choose an access policy. ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png) -1. Click **Add secret**. - -### Reviewing access to organization-level secrets - -You can check which access policies are applied to a secret in your organization. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. The list of secrets includes any configured permissions and policies. Например: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png) -1. For more details on the configured permissions for each secret, click **Update**. diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index f8c2c9ac71..0000000000 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Managing user permissions for your organization -intro: You can control which users in your organization can use {% data variables.product.prodname_codespaces %}. -permissions: To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner. -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### About user permissions for {% data variables.product.prodname_codespaces %} - -Organization owners can control which users in your organization can create and use codespaces. - -To use codespaces in your organization, your users must have at least write access to the repositories where they want to use a codespace. You can enable codespaces for all users in your organization, or only specific users. - -By default, a codespace can only access the repository where it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." - -### Configuring which users in your organization can use {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select one of the following options: - - * **Disabled** to not allow any organization members to use {% data variables.product.prodname_codespaces %}. - * **Allow for all users** to allow all your organization members to use {% data variables.product.prodname_codespaces %}. - * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}. - - ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index c438a70311..0000000000 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Reviewing your organization's audit logs for Codespaces -shortTitle: Reviewing your organization's audit logs -intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -When any member of your organization performs an action related to {% data variables.product.prodname_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)." - -![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) - -The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 142e6c292d..0000000000 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing your codespaces -intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index 44504fbaa6..0000000000 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Managing access and security for your codespaces -intro: You can manage the repositories that {% data variables.product.prodname_codespaces %} can access. -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -When you enable access and security for a repository owned by your user account, any codespaces that are created for that repository will have read and write permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index 6ad3cdee4a..0000000000 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Managing encrypted secrets for your codespaces -intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### About encrypted secrets for {% data variables.product.prodname_codespaces %} - -You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. - -- Personal access tokens to cloud services -- Service principals -- Subscription identifiers -- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. - -{% data reusables.codespaces.secrets-on-start %} - -#### Naming secrets - -{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. - - {% data reusables.codespaces.secret-precedence %} - -#### Limits for secrets - -You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}. - -Secrets are limited to 64 KB in size. - -### Adding a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. To the right of "Codespaces secrets", click **New secret**. !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Under "Name", type a name for your secret. !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Click **Add secret**. - -### Editing a secret - -You can update the value of an existing secret, and you can change which repositories can access a secret. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Under "Value", click **enter a new value**. !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. Optionally, to remove the secret's access to a repository, deselect the repository. ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Click **Save changes**. - -### Deleting a secret - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index c9492f1760..0000000000 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Managing GPG verification for Codespaces -intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)." - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. Under "GPG verification", select the setting you want for GPG verification. ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. If you chose "Selected repositories", select the drop-down menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index f7e213e258..0000000000 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Reviewing your security logs for Codespaces -shortTitle: Reviewing your security logs -intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_codespaces %}.' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### About security logs for {% data variables.product.prodname_codespaces %} - -When you perform an action related to {% data variables.product.prodname_codespaces %} in repositories owned by your user 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)." - -![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) - -The security log includes details on what action occured and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". diff --git a/translations/ru-RU/content/codespaces/quickstart.md b/translations/ru-RU/content/codespaces/quickstart.md deleted file mode 100644 index 4fc600a396..0000000000 --- a/translations/ru-RU/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Quickstart for GitHub Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes or less.' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### Introduction - -In this guide, you'll create a codespace from the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. - -The following example shows you how to create a codespace, connect to a forwarded port to view your running application, and personalize your setup with additional extensions and dotfiles. - -### Creating your codespace - -1. Navigate to the main page of the [sample repository](https://github.com/2percentsilk/haikus-for-codespaces). - -2. Under the repository name, use the {% octicon "download" aria-label="The download icon" %} **Code** drop-down menu, and select **Open with Codespaces**. - - ![Open with Codespaces button](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. To create a codespace, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. - - ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png) - -### Run the application - -With your project open in a codespace, you can now run the application and launch it in a browser. - -1. Start the application by entering `npm run dev` in the terminal. This command executes the `dev` script in the package.json file and starts up the web application defined in the sample repository. - - ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. When your project starts, you should see a toast in the bottom right corner with a prompt to connect to the port your project uses. - - ![Port forwarding toast](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. Click **Open in Browser** to view your running application in a new tab. - -### Personalize with a theme extension - -Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme but you can install any extension that is useful for your workflow. - -1. In the left sidebar, click the Extensions icon. - -2. In the search bar, enter `fairyfloss` and install the fairyfloss extension. - - ![Add an extension](/assets/images/help/codespaces/add-extension.png) - -3. Select the `fairyfloss` theme by selecting it from the list. - - ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) - -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically to other codespaces via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). - -### Personalize with dotfiles - -If your user account on GitHub owns a public repository named dotfiles, GitHub automatically uses this repository to personalize your codespace environment during codespace creation. - -This example guides you through creating a dotfiles repository for your codespaces. - -1. Navigate to the sample [dotfiles repository](https://github.com/aw-test-93/dotfiles/). - -2. Fork the repository to your account and ensure it's public. - - Verify the repository created under your account is named dotfiles, for example `yourname/dotfiles`. Any other name will cause {% data variables.product.prodname_codespaces %} to ignore the repository for personalization. - -3. Create a new codespace from the [sample application repository](https://github.com/2percentsilk/haikus-for-codespaces) as dotfile updates are only applied at creation time. The sample dotfiles will change the command prompt to bold purple and blue text. - - ![Custom command prompt](/assets/images/help/codespaces/custom-prompt.png) - -### Next Steps - -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_codespaces %}. - - "[Getting Started guides](/codespaces/getting-started-with-codespaces)" for using {% data variables.product.prodname_codespaces %} with specific languages - - [Create a custom configuration](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project) to configure {% data variables.product.prodname_codespaces %} for your project. \ No newline at end of file diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index 9df28ebec6..0000000000 --- a/translations/ru-RU/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Configuring Codespaces for your project -intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About dev containers - -A development container, or dev container, is the environment that {% data variables.product.prodname_codespaces %} uses to provide the tools and runtimes that your project needs for development. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a pre-defined configuration](#using-a-pre-defined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project. - -{% data variables.product.prodname_codespaces %} allows for customization on a per-project and per-branch basis with a `devcontainer.json` file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the `devcontainer.json` file in the `.devcontainer` folder to define everything required to create a container image. - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual [workspaces](https://code.visualstudio.com/docs/editor/workspaces) in a codespace in a file named `.vscode/settings.json`. - -For information about the settings and properties that you can set in a `devcontainer.json`, see [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) in the {% data variables.product.prodname_vscode %} documentation. - -#### Файл Dockerfile - -A Dockerfile also lives in the `.devcontainer` folder. - -You can add a Dockerfile to your project to define a container image and install software. In the Dockerfile, you can use `FROM` to specify the container image. - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -You can use the `RUN` instruction to install any software and `&&` to join commands. - -Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property. - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -For more information on using a Dockerfile in a dev container, see [Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) in the {% data variables.product.prodname_vscode %} documentation. - -### Using the default configuration - -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the url that the command outputs. - -Alternatively, for more information about everything that is included in the base Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) repository. - -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_codespaces %} provides. - - -### Using a predefined container configuration - -Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. - -Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup. - -1. To access the command palette, in the upper-left corner, select the Application Menu and click **Command Palette…** from the **View** menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click **Codespaces: Add Development Container Configuration Files...** !["Codespaces: Add Development Container Configuration Files..." in the command palette](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. Click the definition you want to use. ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. Follow the prompts to customize your definition. -1. Click **OK**. ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png) - - -### Creating a custom codespace configuration - -If none of the predefined configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} - -In the file, you can use [supported configuration keys](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. - -{% data reusables.codespaces.vscode-settings-order %} - -You can define default editor settings for {% data variables.product.prodname_vscode %} in two places. - -* Editor settings defined in `.vscode/settings.json` are applied as _Workspace_-scoped settings in the codespace. -* Editor settings defined in the `settings` key in `devcontainer.json` are applied as _Remote [Codespaces]_-scoped settings in the codespace. - -After updating the `devcontainer.json` file, you can rebuild the container for your codespace to apply the changes. For more information, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." - - - - -### Applying changes to your configuration - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -!["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - - To diagnose the error by reviewing the creation logs, click **View creation log**. - - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. {% data reusables.codespaces.rebuild-command %} diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index f47cc82ec3..0000000000 --- a/translations/ru-RU/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Setting up your codespace -intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your codespace with a dev container to install your dependencies or you can add a dotfile to personalize the user settings.' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index 79c3c244d9..0000000000 --- a/translations/ru-RU/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Personalizing Codespaces for your account -intro: 'You can personalize {% data variables.product.prodname_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### About personalizing {% data variables.product.prodname_codespaces %} - -When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_codespaces %} allows for two main ways of personalizing your codespaces. - -- [Settings Sync](#settings-sync) - You can use and share {% data variables.product.prodname_vscode %} settings between {% data variables.product.prodname_codespaces %} and other instances of {% data variables.product.prodname_vscode %}. -- [Dotfiles](#dotfiles) – You can use a public `dotfiles` repository to specify scripts, shell preferences, and other configurations. - -{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create. - -Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)." - -### Settings Sync - -Settings Sync allows you to share configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode %}. - -Settings Sync is on by default. To configure any settings, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Settings Sync is on**. From the dialog, you can choose to configure, show settings and data, or turn off Settings Sync. - -![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode %} documentation. - -### 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/). - -If your user account on {% data variables.product.prodname_dotcom %} owns a public repository named `dotfiles`, {% data variables.product.prodname_dotcom %} automatically uses this repository to personalize your codespace environment. Private `dotfiles` repositories are not currently supported. - -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. - -When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your `dotfiles` repository to the codespace environment, and looks for one of the following files to set up the environment. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -If none of these files are found, then any files or folders in `dotfiles` starting with `.` are symlinked to the codespace's `~` or `$HOME` directory. - -Any changes to your `dotfiles` repository will apply only to each new codespace, and do not affect any existing codespace. - -{% note %} - -**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the _User_ settings for the {% data variables.product.prodname_vscode %} editor 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 "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)." - -{% endnote %} - -You can also configure settings for your user account to add encrypted secrets, enable GPG verification, and allow your codespaces to access other repositories. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)", "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)", and "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." - -### Дополнительная литература - -* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/ru-RU/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/ru-RU/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 8a1128db5e..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} is free to use during the beta. When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage. diff --git a/translations/ru-RU/data/reusables/codespaces/about-configuration.md b/translations/ru-RU/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 398b2495a6..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -You can create a default codespace configuration for your repository that determines the environment of every new codespace anyone creates for that repository. The configuration defines a development container that can include frameworks, tools, extensions, and port forwarding. diff --git a/translations/ru-RU/data/reusables/codespaces/about-personalization.md b/translations/ru-RU/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index 958370ebd8..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -You can also use a [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to personalize aspects of the codespace environment for any codespace that you create. Personalization can include shell preferences and additional tools. diff --git a/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md b/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 39b29dc4a0..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -You can forward ports in your codespace to test and debug your application. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index 8031bfb4af..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -After the {% data variables.product.prodname_codespaces %} configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/beta-functionality-limited.md b/translations/ru-RU/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 25501d28f0..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -During the beta, functionality is limited. -- {% data reusables.codespaces.use-chrome %} -- Only a single size of codespace is available. -- Only Linux containers are supported. -- A codespace is not fully resumable. Processes that were running at the time the codespace was stopped will not be restarted. diff --git a/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index 5e0618af02..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/codespace-config-order.md b/translations/ru-RU/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index e785e51c45..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -Your `dotfiles` personalization is applied before a repository's default codespace configuration. diff --git a/translations/ru-RU/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/ru-RU/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index 146beb47e8..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -Each codespace is associated with a specific branch of a repository. diff --git a/translations/ru-RU/data/reusables/codespaces/codespaces-are-personal.md b/translations/ru-RU/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 771fe3f97c..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -Each codespace you create is only available to you. No one else can work in your codespace. diff --git a/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md b/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index 475114c1c5..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -You can run your codespace on a choice of three types of remote machine: Basic, Standard, or Premium. Each of these has a different level of resources and a different billing tier.{% note %} - -**Note:** {% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -Switching machine types gives you the flexibility to choose the most appropriate resources for your work. Certain tasks may require different machine types: - -* **Basic** for updating a file and raising a pull request -* **Standard** for editing a website -* **Premium** for high compute tasks such as data analysis diff --git a/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 87bfa539ff..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users. - -For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/ru-RU/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index 40126da0da..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -You can create more than one codespace per repository or even per branch. However, each user account has a two-codespace limit during limited public beta. If you've reached the limit and want to create a new codespace, you must delete a codespace first. diff --git a/translations/ru-RU/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/ru-RU/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index 045387a57b..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -You can connect to your codespace directly from {% data variables.product.prodname_vscode %}. For more information, see "[Using Codespaces in {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." diff --git a/translations/ru-RU/data/reusables/codespaces/devcontainer-location.md b/translations/ru-RU/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index 196fc006be..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -This file can be located in the root of the repository or in a folder called `.devcontainer`. If the file is located in the root of the repository, the filename must begin with a period: `.devcontainer.json`. diff --git a/translations/ru-RU/data/reusables/codespaces/navigate-to-codespaces.md b/translations/ru-RU/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index 4ba7c260e0..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. At the top of any page, click **Codespaces**. ![{% data variables.product.prodname_codespaces %} link in header](/assets/images/help/codespaces/header-link.png) diff --git a/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index fed860897b..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In your codespace, under the text editor, click "Ports". ![Ports tab](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/ru-RU/data/reusables/codespaces/rebuild-command.md b/translations/ru-RU/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index ea9e45b032..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -Access the command palette (`shift command P` / `shift control P`), then start typing "Codespaces: Rebuild Container". Click **Codespaces: Rebuild Container**. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/recovery-mode.md b/translations/ru-RU/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index fa4e73d013..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/release-stage.md b/translations/ru-RU/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 57e551dd72..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Note:** {% data variables.product.prodname_codespaces %} is currently in limited public beta and subject to change. For more information about joining the beta, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)." - -{% endnote %} diff --git a/translations/ru-RU/data/reusables/codespaces/secret-precedence.md b/translations/ru-RU/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index 582b91c1aa..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/secrets-naming.md b/translations/ru-RU/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index eddb8aa7f5..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -The following rules apply to secret names: - -* Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed. -* Secret names must not start with the `GITHUB_` prefix. -* Secret names must not start with a number. -* Secret names are not case-sensitive. -* Secret names must be unique at the level they are created at. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md b/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index c4a5bf3b41..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to suspend the codespace and resume it. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md b/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index 90b3503dcd..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. ![Source control view](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-display.md b/translations/ru-RU/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index 09917cd3c8..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the Activity Bar, click the **Source Control** view. - - ![Source control view](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/type-port-label.md b/translations/ru-RU/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 498c9eb752..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Type a label for your port, then press enter. ![Text box to type label for port](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/unsupported-repos.md b/translations/ru-RU/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index 03fd9189d9..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -During the beta, private repositories owned by organizations or any repositories owned by an organization that requires SAML single sign-on are not supported. diff --git a/translations/ru-RU/data/reusables/codespaces/use-chrome.md b/translations/ru-RU/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index c44bb64faf..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -For the best experience with {% data variables.product.prodname_codespaces %}, we recommend using a Chromium-based browser, like Google Chrome or Microsoft Edge. diff --git a/translations/ru-RU/data/reusables/codespaces/use-visual-studio-features.md b/translations/ru-RU/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index a5b1cf9151..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -You can edit code, debug, and use Git commands while developing in a codespace with {% data variables.product.prodname_vscode %}. For more information, see the [{% data variables.product.prodname_vscode %} documentation](https://code.visualstudio.com/docs). diff --git a/translations/ru-RU/data/reusables/codespaces/vscode-settings-order.md b/translations/ru-RU/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index fc4b840129..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -When you configure editor settings for {% data variables.product.prodname_vscode %}, there are three scopes available: _Workspace_, _Remote [Codespaces]_, and _User_. If a setting is defined in multiple scopes, _Workspace_ settings take priority, then _Remote [Codespaces]_, then _User_. diff --git a/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index afb626e71c..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -You can see every available codespace that you have created at [github.com/codespaces](https://github.com/codespaces). diff --git a/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index a5e98437c0..0000000000 --- a/translations/ru-RU/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. In the top right corner of {% data variables.product.product_name %}, click your profile photo, then click **Your codespaces**. - - !['Your codespaces' menu option](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/gated-features/codespaces.md b/translations/ru-RU/data/reusables/gated-features/codespaces.md deleted file mode 100644 index 1423451c5e..0000000000 --- a/translations/ru-RU/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -Codespaces is available for user accounts using {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ru-RU/data/reusables/organizations/click-codespaces.md b/translations/ru-RU/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index 6a15dd7757..0000000000 --- a/translations/ru-RU/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. !["Codespaces" tab in left sidebar](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index ae43f35c1f..0000000000 --- a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Select the "Repository access" drop-down menu, then click a repository you want to have access to the secret. Repeat for every repository you want to have access to the secret. !["Repository access" drop-down menu](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md b/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index 82cb0fbffe..0000000000 --- a/translations/ru-RU/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. Under "Value", type the value of your secret. !["Value" textbox](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md b/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index e4908fcf75..0000000000 --- a/translations/ru-RU/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Codespaces**. ![Codespaces tab in the user settings sidebar](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file diff --git a/translations/zh-CN/content/codespaces/about-codespaces.md b/translations/zh-CN/content/codespaces/about-codespaces.md deleted file mode 100644 index c9322f1344..0000000000 --- a/translations/zh-CN/content/codespaces/about-codespaces.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: 关于 Codespaces -intro: '{% data variables.product.prodname_codespaces %} 是一个可配置的在线开发环境，由 {% data variables.product.prodname_dotcom %} 托管并由 {% data variables.product.prodname_vscode %} 支持，允许您完全在云端开发。' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces - - /github/developing-online-with-codespaces/about-codespaces - - /codespaces/getting-started-with-codespaces/about-codespaces -versions: - free-pro-team: '*' -type: overview -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### 关于 {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} 是一个可配置的云开发环境，在 {% data variables.product.prodname_dotcom %} 上的浏览器或通过 {% data variables.product.prodname_vscode %} 提供。 - -![开放的代码空间](/assets/images/help/codespaces/codespace-overview.png) - -代码空间包括开发者为特定仓库进行开发所需的一切，包括 {% data variables.product.prodname_vscode %} 编辑体验和常见的语言、工具和实用程序。 {% data variables.product.prodname_codespaces %} 是完全可配置的，允许您为项目创建自定义开发环境，并允许开发者通过扩展和 dotfile 设置个性化他们的体验。 - -通过在整个团队中提供一致的环境、快速启动和创建安全的开发空间，代码空间可为团队提供许多好处。 - -### 一致的环境 - -您可以创建单个代码空间配置，以定义任何人为仓库创建的每个新代码空间的环境（或_开发容器_）。 一旦您完成了配置，开发者就不必担心安装合适的工具进行评论、审查或贡献。 一旦他们从仓库创建代码空间，就已经为他们提供了标准化的环境。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。 - -有关特定语言配置入门的帮助，请参阅[入门](/codespaces/getting-started-with-codespaces)教程。 - -虽然从仓库创建的每个代码空间都有一致的开发环境，但开发者可以在需要时在 {% data variables.product.prodname_dotcom %} 上或通过 {% data variables.product.prodname_vscode %} 使用 {% data variables.product.prodname_codespaces %}。 - -### 快速和个性化启动 - -在您的仓库中配置[开发容器](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#about-dev-containers)后，任何新开发者都可以通过使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单并选择 **Open with Codespaces（使用代码空间打开）**，快速为项目启动正确的开发环境。 - -![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -由于标准化了可重复的开发者环境，开发者可以在不做任何手动配置的情况下开始使用新的代码空间，并且不需要继续维护其开发者环境。 启动新功能时可以创建新的代码空间。 - -开发者也可以通过使用 [dotfiles](https://dotfiles.github.io/tutorials/) 仓库和 [Settings Sync（设置同步）](https://code.visualstudio.com/docs/editor/settings-sync)来个性化其代码空间环境的各个方面。 个性化可以包括 shell 首选项、其他工具、编辑器设置和扩展，例如 Live Share。 个性化定制是按用户存储的，因此开发者打开的每个代码空间都有即时可用的环境。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)”。 - -因为可以在浏览器中访问 {% data variables.product.prodname_codespaces %}，所以开发者可以通过在选项卡之间切换来处理多个项目。 - -### 安全的环境 - -{% data variables.product.prodname_codespaces %} 允许开发者在云端开发，而不是本地开发。 这将创造单一、可跟踪的真相来源。 开发者可以随时随地任何机器（包括平板电脑或 Chromebooks）上参与项目开发，无需维护知识产权的本地副本。 开发人员必须始终登录并有权访问 {% data variables.product.prodname_codespaces %} 和特定仓库。 这些权限可以随时撤销。 只要您撤销访问权限，这些开发者就会失去对受保护资源的所有访问权限。 此外，经过验证的开发者创建审核跟踪，以便您知道谁在做什么。 有关访问和安全的更多信息，请参阅“[管理您组织的代码空间的访问和安全](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)”。 - -当团队的所有成员都使用它时，使用 {% data variables.product.prodname_codespaces %} 是最安全的。 这意味着没有必要将仓库克隆到本地机器上，开发者也不需要本地安装为 `root`。 - -开发者和组织管理员还可以配置设置以添加加密密码并启用 GPG 验证。 更多信息请参阅“[管理 {% data variables.product.prodname_codespaces %} 的加密密码](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)”、“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”。 - -### 关于 {% data variables.product.prodname_codespaces %} 的计费 - -{% data reusables.codespaces.about-billing-for-codespaces %} 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %} 的计费](/github/developing-online-with-codespaces/about-billing-for-codespaces)”。 - -### 加入公测 - -将邀请有限数量的人加入公测。 要加入等待列表，请参阅[注册代码空间测试版](https://github.com/features/codespaces/signup)。 - -### 就 {% data variables.product.prodname_codespaces %} 联系我们 - -如果在使用 {% data variables.product.prodname_codespaces %} 时遇到问题，请参阅“[代码空间故障排除](/github/developing-online-with-codespaces/troubleshooting-your-codespace)”。 - -如果您仍需帮助或对 {% data variables.product.prodname_codespaces %} 有反馈，请使用 [Codespaces 反馈](https://github.com/github/feedback/discussions/categories/codespaces-feedback)。 diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md deleted file mode 100644 index 2ac5dc243c..0000000000 --- a/translations/zh-CN/content/codespaces/codespaces-reference/about-billing-for-codespaces.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: 关于代码空间的计费 -intro: '当 {% data variables.product.prodname_codespaces %} 公开发布时，将按存储和计算使用情况计费。' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/about-billing-for-codespaces - - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.about-billing-for-codespaces %} - -代码空间计费模型的更新将在即将发布的公告中分享。 diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md deleted file mode 100644 index e3cfd84de3..0000000000 --- a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: 允许代码空间访问私有映像注册表 -intro: '您可以使用密钥允许 {% data variables.product.prodname_codespaces %} 访问私有映像注册表' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -注册表是存储和管理私有容器映像（如 Azure 容器注册表或 DockerHub）的安全空间。 您可以在 GitHub 中创建密钥以存储私有注册表的访问权限信息，并使用它们授权代码空间访问存储在注册表中的映像。 - -启动代码空间时，{% data variables.product.prodname_codespaces %} 将检查三个密钥，它们定义了容器注册表的服务器名称、用户名和个人访问令牌 (PAT)。 如果找到这些密钥，{% data variables.product.prodname_codespaces %} 将在代码空间中提供注册表。 - -- `<*>_CONTAINER_REGISTRY_SERVER` -- `<*>_CONTAINER_REGISTRY_USER` -- `<*>_CONTAINER_REGISTRY_PASSWORD` - -您可以在用户、仓库或组织级别存储密钥，从而在不同的代码空间之间安全地共享它们。 当您为私有映像注册表创建一组密钥时，您需要用一致的标识符替换名称中的 “<*>”。 更多信息请参阅“[管理代码空间的加密密码](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)”和“[管理代码空间的仓库和组织加密密码](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)“。 - -例如，如果您在 Azure 中拥有私有映像注册表，则可以创建以下密钥： - -``` -ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io -ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = -``` -![映像注册表密钥示例](/assets/images/help/settings/codespaces-image-registry-secret-example.png) diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/index.md b/translations/zh-CN/content/codespaces/codespaces-reference/index.md deleted file mode 100644 index 8a07aab3c4..0000000000 --- a/translations/zh-CN/content/codespaces/codespaces-reference/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 参考 -intro: '本节包含帮助您成功使用 {% data variables.product.prodname_codespaces %} 的参考' -versions: - free-pro-team: '*' -children: - - /about-billing-for-codespaces - - /troubleshooting-your-codespace - - /allowing-your-codespace-to-access-a-private-image-registry - - /using-the-command-palette-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md b/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md deleted file mode 100644 index f40de7e6f4..0000000000 --- a/translations/zh-CN/content/codespaces/codespaces-reference/troubleshooting-your-codespace.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: 代码空间疑难解答 -intro: 使用本指南帮助您解决代码空间的常见问题。 -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace - - /github/developing-online-with-codespaces/troubleshooting-your-codespace - - /codespaces/working-with-your-codespace/troubleshooting-your-codespace -versions: - free-pro-team: '*' -type: reference -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### 已知限制 - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -### {% data variables.product.prodname_vscode %} 故障排除 - -在 [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) 仓库中使用**议题**来检查已知议题或记录有关 {% data variables.product.prodname_vscode %} 体验的议题。 - - -### 配置故障排除 - -{% data reusables.codespaces.recovery-mode %} - -``` -由于容器错误，这个代码空间正在恢复模式中运行。 -``` - -查看创建日志，根据需要更新配置，并在命令面板中运行 **Codespaces: Rebuild Container** 以重试。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)”。 - -### dotfiles 故障排除 - -- 确保您的 dotfiles 仓库是公开的。 如果您的代码空间中有密钥或敏感数据，请使用[代码空间密钥](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)，而不是私人 dotfiles。 -- 检查 `/workspaces/.codespaces/.persistedshare/dotfiles`，查看您的 dotfiles 是否被克隆。 - - 如果您的 dotfiles 被克隆，请尝试手动重新运行安装脚本以验证其可执行性。 - - 如果您的 dotfiles 未被克隆，请检查 `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` 是否存在克隆问题。 -- 检查 `/workspaces/.codespaces/.persistedshare/creation.log` 是否有可能的问题。 或者，您可以通过导航到命令面板并输入 **Codespaces: View Creation Log** 来查看 `creation.log`。 - - -### 浏览器故障排除 - -如果在使用非基于 Chromium 的浏览器时遇到问题，请尝试切换到基于 Chromium 的浏览器，或在 `microsoft/vscode` 仓库中搜索标有您的浏览器名称（如 [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) 或 [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari)）的议题，检查浏览器的已知问题。 - -如果您在使用基于 Chromium 的浏览器时遇到问题，您可以在e [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) 仓库中检查是否遇到 {% data variables.product.prodname_vscode %} 的另一个已知问题。 - -### 容器存储故障排除 - -创建代码空间时，存储量是有限的，随着时间的推移，可能需要释放空间。 尝试以下任何项以释放存储空间。 - -- 使用 `sudo apt autoremove` 删除不再使用的包 -- 使用 `sudo apt clean` 清理 apt 缓存 -- 删除不需要的文件，如构件和日志 (这些文件与项目的依存度很高) -- 查看代码空间中排名前 10 的大文件：`sudo find / -printf '%s %p\n'| sort -nr | head -10` - -更具破坏性的选项： -- 使用 `docker system prune`（如果要删除所有映像，请追加 `-a`；如果要删除所有卷，请追加 `--volumes`）删除不使用的 Docker 映像、网络和容器 -- 从工作树中删除不跟踪的文件：`git clear-i` - -### 联系我们 - -如果仍需帮助，请联系我们。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)”。 diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md deleted file mode 100644 index c58655b1a7..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: 创建代码空间 -intro: 您可以为仓库中的分支创建代码空间以便在线开发。 -permissions: 'Anyone can create a codespace for any public repository, or for any repository owned by their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace - - /github/developing-online-with-codespaces/creating-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 关于代码空间的创建 - -您可以在 {% data variables.product.prodname_dotcom_the_website %} 或 {% data variables.product.prodname_vscode %} 中创建代码。 {% data reusables.codespaces.codespaces-are-personal %} - -代码空间与仓库的特定分支相关联，且仓库不能为空。 {% data reusables.codespaces.concurrent-codespace-limit %} 更多信息请参阅“[删除代码空间](/github/developing-online-with-codespaces/deleting-a-codespace)”。 - - -创建代码空间时，需要执行一些步骤来实现对开发环境的完全访问。 - -- 分配了 VM 和容器存储等资源。 每次创建或启动代码空间时都会创建新的 VM，以确保您始终有最新的版本和安全补丁。 -- {% data variables.product.prodname_codespaces %} 接收有关您的仓库、分支、提交、公共 dotfiles 仓库以及您创建的所有密钥的信息。 -- {% data variables.product.prodname_codespaces %} 执行仓库的浅表克隆。 -- 如果仓库中有 `devcontainer.json` 文件，{% data variables.product.prodname_codespaces %} 将运行它。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。 -- Docker 容器、`docker-compose` 或其他其他初始化将运行。 -- 此时，代码空间标记为可用，您可以连接。 -- 一旦代码空间可用，根据开发容器中的命令，代码空间将继续进行一些设置。 - - 代码空间共享 `devcontainer.json` 文件中添加的端口。 - - 代码空间运行 `postCreateCommand` 中指定的任何操作。 - - {% data variables.product.prodname_codespaces %} 将 dotfiles 仓库克隆到代码空间并查找安装文件。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)”。 - - 最后，代码空间对仓库进行完整克隆，使您可以完全访问它。 - - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### 创建代码空间 - -{% data reusables.repositories.navigate-to-repo %} -2. 在仓库名称下，使用“Branch（分支）”下拉菜单选择您要为其创建代码的分支。 - - ![分支下拉菜单](/assets/images/help/codespaces/branch-drop-down.png) - -3. 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -4. 要使用标准机器类型创建代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 - - ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - - - diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md deleted file mode 100644 index d465e9eedf..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: 删除代码空间 -intro: 您可以删除不再需要的代码空间。 -permissions: Anyone can delete a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace - - /github/developing-online-with-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -1. 导航到您创建代码空间的仓库。 选择 **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces（代码空间）**，然后单击 {% octicon "gear" aria-label="The Settings gear" %}。 这将显示您在仓库中创建的所有 {% data variables.product.prodname_codespaces %}。 ![Codespaces 选项卡](/assets/images/help/codespaces/codespaces-manage.png) - - 您也可以在 [github.com/codespaces](https://github.com/codespaces)上查看您的用户帐户拥有的每个代码空间。 - -2. 在要删除的代码空间的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **{% octicon "trash" aria-label="The trash icon" %} Delete（删除）** ![删除按钮](/assets/images/help/codespaces/delete-codespace.png) - -### 在 {% data variables.product.prodname_vscode %} 中删除代码空间 - -有关在 {% data variables.product.prodname_vscode %} 中删除代码空间的信息，请参阅“[在 Visual Studio Code 中使用代码空间](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#deleting-a-codespace-in-visual-studio-code)”。 diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md deleted file mode 100644 index 3f739652a0..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: 在代码空间中开发 -intro: '您可以在 {% data variables.product.product_name %} 上打开代码空间，然后使用 {% data variables.product.prodname_vscode %} 的功能进行开发。' -permissions: Anyone can develop in a codespace owned by their user account. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace - - /github/developing-online-with-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 关于 {% data variables.product.prodname_codespaces %} 的开发 - -{% data variables.product.prodname_codespaces %} 为您提供 {% data variables.product.prodname_vscode %} 的完整开发体验。 {% data reusables.codespaces.use-visual-studio-features %} - -![带注释的代码空间概述](/assets/images/help/codespaces/codespace-overview-annotated.png) - -1. 侧栏 - 默认情况下，此区域显示您在资源管理器中的项目文件。 -2. 活动栏 - 显示视图并提供在视图之间切换的方法。 您可以通过拖放来重新排列视图。 -3. 编辑器 - 这是您编辑文件的地方。 您可以使用每个编辑器的选项卡将其准确定位到您需要的位置。 -4. 面板 - 这是您可以查看输出和调试信息的位置，以及集成终端的默认位置。 -5. 状态栏 - 此区域提供有关您的代码空间和项目的有用信息。 例如，分支名称、配置端口等。 - -有关使用 {% data variables.product.prodname_vscode %} 的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[用户界面指南](https://code.visualstudio.com/docs/getstarted/userinterface)。 - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.use-chrome %} 更多信息请参阅“[代码空间故障排除](/github/developing-online-with-codespaces/troubleshooting-your-codespace)”。 - -#### 个性化代码空间 - -{% data reusables.codespaces.about-personalization %} 更多信息请参阅“[个性化您帐户的 {% data variables.product.prodname_codespaces %}](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)”。 - -{% data reusables.codespaces.apply-devcontainer-changes %} 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)”。 - -#### 从代码空间运行应用程序 -{% data reusables.codespaces.about-port-forwarding %} 更多信息请参阅“[代码空间中的转发端口](/github/developing-online-with-codespaces/forwarding-ports-in-your-codespace)”。 - -#### 提交更改 - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 导航到现有代码空间 - -1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} -2. 单击您要在其中开发的代码空间的名称。 ![代码空间的名称](/assets/images/help/codespaces/click-name-codespace.png) - -或者，您可以通过导航到创建代码空间的仓库并选择 **{% octicon "codespaces" aria-label="The codespaces icon" %} 代码空间**来查看仓库的任何活动代码空间。 diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md deleted file mode 100644 index 560ee94a6a..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: 代码空间中的转发端口 -intro: '{% data reusables.codespaces.about-port-forwarding %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 关于转发的端口 - -通过端口转发，您可以访问在代码空间内运行的 TCP 端口。 例如，如果您在端口 4000 上运行 Web 应用程序，您可以从浏览器访问该应用程序以测试和调试它。 - -在代码空间内运行的应用程序向控制台输出端口时，{% data variables.product.prodname_codespaces %} 将检测到 localhost URL 模式并自动转发端口。 您可以单击终端中的 URL 在浏览器中打开端口。 例如，如果应用程序向控制台输出 `http://127.0.0.1:4000` 或 `http://localhost:4000`，则日志会自动将输出转换为端口 4000 的可单击 URL。 - -![自动端口转发](/assets/images/help/codespaces/automatic-port-forwarding.png) - -您还可以手动转发端口、标记转发的端口、公开共享转发的端口以及将转发的端口添加到代码空间配置中。 - -### 转发端口 - -您可以手动转发未自动转发的端口。 - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. 在端口列表下，单击 **Add port（添加端口）**。 ![添加端口按钮](/assets/images/help/codespaces/add-port-button.png) -1. 键入端口编号或地址，然后按 Enter。 ![输入端口按钮的文本框](/assets/images/help/codespaces/port-number-text-box.png) - -### 标记端口 - -您可以标记端口，使端口更容易在列表中识别。 - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. 悬停在要标记的端口上，然后单击标签图标。 ![端口的标签图标](/assets/images/help/codespaces/label-icon.png) -{% data reusables.codespaces.type-port-label %} - -### 共享端口 - -如果您想与他人共享转发的端口，您可以公开该端口。 当您公开端口后，任何拥有端口 URL 的人都可以查看正在运行的应用程序，而无需进行身份验证。 - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. 右键单击要共享的端口，然后单击 **Make Public（公开）**。 ![右键菜单中公开端口的选项](/assets/images/help/codespaces/make-public-option.png) -1. 在端口的本地地址右侧，单击复制图标。 ![端口 URL 的复制图标](/assets/images/help/codespaces/copy-icon-port-url.png) -1. 将复制的 URL 发送给您想要与其共享端口的人。 - -### 将端口添加到代码空间配置 - -您可以将转发的端口添加到仓库的 {% data variables.product.prodname_codespaces %} 配置中，因此该端口将自动为创建自仓库的所有代码空间转发。 更新配置后，必须重建任何以前创建的代码空间以应用更改。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。 - -您可以使用 `forwardPorts` 属性在 `.devcontainer.json` 文件中手动配置转发的端口，也可以使用代码空间中的“端口”面板。 - -{% data reusables.codespaces.navigate-to-ports-tab %} -1. 右键单击要添加到代码空间配置的端口，然后单击 **Set Label and Update devcontainer.json（设置标签和更新 devcontainer.json）**。 ![右键菜单中设置标签并将端口添加到 devcontainer.json 的选项](/assets/images/help/codespaces/update-devcontainer-to-add-port-option.png) -{% data reusables.codespaces.type-port-label %} - diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md deleted file mode 100644 index b81102923e..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: 在代码空间中开发 -intro: '创建代码空间，以便在专用云环境中开始开发您的项目。 您可以使用转发端口运行应用程序，甚至可以使用 {% data variables.product.prodname_vscode %} 内的代码空间' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /creating-a-codespace - - /developing-in-a-codespace - - /using-source-control-in-your-codespace - - /deleting-a-codespace - - /forwarding-ports-in-your-codespace - - /using-codespaces-in-visual-studio-code ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md deleted file mode 100644 index 130bbec088..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: 在 Visual Studio Code 中使用代码空间 -intro: '您可以将 {% data variables.product.prodname_github_codespaces %} 扩展连接到您在 {% data variables.product.product_name %} 上的帐户，直接在 {% data variables.product.prodname_vscode %} 代码空间中开发。' -redirect_from: - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code - - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code - - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Visual Studio Code - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 基本要求 - -要直接在 {% data variables.product.prodname_vscode %} 中开发代码空间，必须登录到 {% data variables.product.prodname_github_codespaces %} 扩展。 {% data variables.product.prodname_github_codespaces %} 扩展需要 {% data variables.product.prodname_vscode %} 2020 年 10 月 1 日版本 1.51 或更高版本。 - -使用 {% data variables.product.prodname_vs %} Marketplace 安装 [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 扩展。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[扩展 Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)。 - - -{% mac %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. 单击 **Sign in to view {% data variables.product.prodname_dotcom %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -3. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。 -4. 登录 {% data variables.product.product_name %} 以审批扩展。 - -{% endmac %} - -{% windows %} - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. 使用“REMOTE EXPLORER（远程资源管理器）”下拉列表，然后单击 **{% data variables.product.prodname_github_codespaces %}**。 ![{% data variables.product.prodname_codespaces %} 标头](/assets/images/help/codespaces/codespaces-header-vscode.png) -3. 单击 **Sign in to view {% data variables.product.prodname_codespaces %}...（登录以查看 Codespaces...）**。 ![登录以查看 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -4. 要授权 {% data variables.product.prodname_vscode %} 访问您在 {% data variables.product.product_name %} 上的帐户，请单击 **Allow（允许）**。 -5. 登录 {% data variables.product.product_name %} 以审批扩展。 - -{% endwindows %} - -### 在 {% data variables.product.prodname_vscode %} 中创建代码空间 - -将 {% data variables.product.product_name %} 帐户连接到 {% data variables.product.prodname_github_codespaces %} 扩展后，您可以在 {% data variables.product.prodname_vscode %} 或 {% data variables.product.product_name %} 上创建的代码空间中进行开发。 - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. 单击 Add（添加）图标，然后单击 **Create New Codespace（创建新代码空间）**。 ![{% data variables.product.prodname_codespaces %} 中的 Create new Codespace（创建新代码空间）选项](/assets/images/help/codespaces/create-codespace-vscode.png) -3. 键入，然后单击要在其中开发仓库的名称。 ![搜索仓库以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. 单击要在其中开发的分支。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the machine type you want to develop in. ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png) -### 在 {% data variables.product.prodname_vscode %} 中打开代码空间 - -{% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. 在“Codespaces（代码空间）”下，单击您要在其中开发的代码空间。 -3. 单击 Connect to Codespace（连接到代码空间）图标。 ![{% data variables.product.prodname_vscode %} 中的连接到代码空间图标](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) - -### 在 {% data variables.product.prodname_vscode %} 中更改机器类型 - -{% data reusables.codespaces.codespaces-machine-types %} - -您可以随时更改代码空间的机器类型。 - -1. 在 {% data variables.product.prodname_vscode %} 中，打开命令调色板 (`shift command P` / `shift control P`)。 -2. 搜索并选择“代码空间：更改机器类型”。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) -3. 单击您要更改的代码空间。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. 选择您要使用的机器类型。 ![搜索分支以创建新的 {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-type.png) - -如果代码空间正在运行，则会显示一条消息，询问您现在是否要重新启动并重新连接到代码空间。 如果您想立即更改用于此代码空间的机器类型，请单击 **Yes（是）** 。 如果您单击 **No（否）**，或者代码空间当前未运行，更改将在代码空间下次重启时生效。 - -### 在 {% data variables.product.prodname_vscode %} 中删除代码空间 - -1. 在“Codespaces（代码空间）”下，右键点击您要删除的代码空间。 -2. 在下拉菜单中，单击 **Delete Codespace（删除代码空间）**。 ![在 {% data variables.product.prodname_dotcom %} 中删除代码空间](/assets/images/help/codespaces/delete-codespace-vscode.png) diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md deleted file mode 100644 index 2ff4d8b6fb..0000000000 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: 在代码空间中使用源控制 -intro: 在对代码空间中的文件进行更改后，您可以快速提交更改并将更新推送到远程仓库。 -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Fundamentals - - Developer ---- - -{% data reusables.codespaces.release-stage %} - -### 关于 {% data variables.product.prodname_codespaces %} 中的源控制 - -您可以直接在代码空间内执行所需的所有 Git 操作。 例如，您可以从远程仓库获取更改、切换分支、创建新分支、提交和推送更改，以及创建拉取请求。 您可以使用代码空间内的集成终端输入 Git 命令，也可以单击图标和菜单选项以完成所有最常见的 Git 任务。 本指南解释如何使用图形用户界面来控制源代码。 - -在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[在 VS 代码中使用版本控制](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)”。 - -使用 {% data variables.product.prodname_github_codespaces %} 更新文件的典型工作流程将是： - -* 从 {% data variables.product.prodname_dotcom %} 上仓库的默认分支，创建代码空间。 请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。 -* 在代码空间中，创建一个新的分支来操作。 -* 进行更改并保存。 -* 提交更改。 -* 提出拉取请求。 - -### 创建或切换分支 - -1. 如果当前分支未显示在状态栏中，请在代码空间的底部右键单击状态栏，然后选择 **Source control（源控制）**。 -1. 单击状态栏中的分支名称。 ![状态栏中的分支](/assets/images/help/codespaces/branch-in-status-bar.png) -1. 在下拉菜单中，单击要切换到的分支或输入新分支的名称，然后单击 **Create new branch（创建新分支）**。 ![从分支菜单中选择](/assets/images/help/codespaces/create-new-branch.png) - -{% tip %} - -**提示**：如果有人在远程仓库上更改了文件，则在您切换到的分支中，只有将更改拉入代码空间后，您才能看到这些更改。 - -{% endtip %} - -### 从远程仓库拉取更改 - -您可以随时将远程仓库的更改拉取到您的代码空间。 - -{% data reusables.codespaces.source-control-display-dark %} -1. 在侧边栏的顶部，单击省略号 (**...**)。 ![查看和更多操作的省略号按钮](/assets/images/help/codespaces/source-control-ellipsis-button.png) -1. 在下拉菜单中，单击 **Pull（拉取）**。 - -如果自创建代码空间以来开发容器已更改，则可以通过为代码空间重建容器来应用更改。 更多信息请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。 - -### 设置代码空间以自动获取新更改 - -您可以设置代码空间，以自动获取对远程仓库所做的任何新提交的详细信息。 这允许您查看仓库的本地副本是否过时，如果是，您可以选择拉取新的更改。 - -如果获取操作检测到远程仓库上的新更改，您将在状态栏中看到新提交的数量。 然后，您可以将更改拉取到本地副本。 - -1. 单击活动栏底部的 **Manage（管理）**按钮。 ![管理按钮](/assets/images/help/codespaces/manage-button.png) -1. 在菜单中，单击 **Settings（设置）**。 -1. 在 Settings（设置）页面上，搜索：`autofetch`。 ![搜索自动获取](/assets/images/help/codespaces/autofetch-search.png) -1. 要获取当前仓库注册的所有远程仓库的更新详情，请将 **Git: Autofetch** 设置为 `all`。 ![启用 Git 自动获取](/assets/images/help/codespaces/autofetch-all.png) -1. 如果要更改自动获取的间隔秒数，请编辑 **Git: Autofetch Period** 的值。 - -### 提交更改 - -{% data reusables.codespaces.source-control-display-dark %} -1. 要暂存更改，请单击已更改文件旁边的 **+**；如果您更改了多个文件并且要全部暂存，请单击 **Changes（更改）**旁边的该按钮。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. 输入提交消息，描述您所做的更改。 ![带有提交消息的源控制侧栏](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. 要提交暂存的更改，请单击源控制侧栏顶部的复选标记。 ![单击复选标记图标](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - -### 提出拉取请求 - -1. 将更改提交到仓库的本地副本后，请单击 **Create Pull Request（创建拉取请求）**图标。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. 检查作为合并来源的本地分支和仓库以及作为合并目标的远程分支和仓库是否正确。 然后为拉取请求提供标题和描述。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. 单击 **Create（创建）**。 - -### 将更改推送到远程仓库 - -您可以推送所做的更改。 这将应用这些更改到远程仓库上的上游分支。 如果您尚未准备好创建拉取请求，或者希望在 {% data variables.product.prodname_dotcom %} 上创建拉取请求，则可能需要这样做。 - -1. 在侧边栏的顶部，单击省略号 (**...**)。 ![查看和更多操作的省略号按钮](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) -1. 在下拉菜单中，单击 **Push（推送）**。 diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md deleted file mode 100644 index e6256564c7..0000000000 --- a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: 开始在代码空间中使用 C# (.NET) 项目 -shortTitle: 开始使用 C# (.NET) 项目 -allowTitleToDifferFromFilename: true -intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 C# (.NET) 项目。' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### 简介 - -本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 C# (.NET) 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。 - -#### 基本要求 - -- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 C# (.NET) 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/2percentsilk/dotnet-quickstart。 -- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。 - -### 步骤 1：在代码空间中打开项目 - -1. 导航到项目的仓库。 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 如果您看不到此选项，则您的项目不能用于 {% data variables.product.prodname_codespaces %}。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. 要创建新的代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - -创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器具有多种语言和运行时，包括 .NET。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。 - -您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。 - -{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 更多信息请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -### 步骤 2：从模板将开发容器添加到您的代码空间 - -默认代码空间容器附带最新的 .NET 版本和预安装的常用工具。 但是，我们鼓励您设置自定义容器，以便根据项目的需求定制在代码空间创建过程中运行的工具和脚本，并确保为仓库中的所有 {% data variables.product.prodname_codespaces %} 用户提供完全可复制的环境。 - -要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 有关开发容器的更多信息，请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -1. 访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "dev container"。 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 对于此示例，单击 **C# (.NET)**。 如果需要其他功能，您可以选择任何特定于 C# (.NET) 或工具（如 C# (.NET) 和 MS SQL）组合的容器。 ![从列表中选择 C# (.NET) 选项](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png) -3. 单击推荐的 .NET 版本。 ![.NET 版本选择](/assets/images/help/codespaces/add-dotnet-version.png) -4. 接受默认选项，将 Node.js 添加到您的自定义中。 ![添加 Node.js 选择](/assets/images/help/codespaces/dotnet-options.png) -5. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### 开发容器的剖析 - -添加 C# (.NET) 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件： - -- `devcontainer.json` -- Dockerfile - -新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。 - -##### 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" - } - }, - - // 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" - ], - - // 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. Do one of the following depending on your scenario: - // * When using GitHub Codespaces and/or Remote - Containers: - // 1. Start the container - // 2. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer - // 3. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" - // - // * If only using Remote - Containers with a local container, uncomment this line instead: - // "mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ], - - // 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" -} -``` - -- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。 -- **Build** - 构建属性。 - - **Dockerfile** - 在构建对象中，`dockerfile` 是对 Dockerfile 的引用，该文件也是从模板中添加的。 - - **Args** - - **Variant**：此文件仅包含一个构建参数，即我们要使用的 .NET Core 版本。 -- **Settings** - 它们是 {% data variables.product.prodname_vscode %} 设置。 - - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。 -- **Extensions** - 它们是默认包含的扩展名。 - - **ms-dotnettools.csharp** - Microsoft C# 扩展为使用 C# 的开发提供丰富的支持，包括 IntelliSense、linting、调试、代码导航、代码格式化、重构、变量资源管理器、测试资源管理器等功能。 -- **forwardPorts** - 此处列出的任何端口都将自动转发。 -- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间（例如 `dotnet restore`）后执行任何操作，您可以在此处执行。 -- **remoteUser** - 默认情况下，您以 vscode 用户身份运行，但您可以选择将其设置为 root。 - -##### Dockerfile - -```bash -# [Choice] .NET version: 5.0, 3.1, 2.1 -ARG VARIANT="5.0" -FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Option] Install Azure CLI -ARG INSTALL_AZURE_CLI="false" -COPY library-scripts/azcli-debian.sh /tmp/library-scripts/ -RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \ - && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -您可以使用 Dockerfile 添加其他容器层，以指定要包含在容器中的操作系统包、节点版本或全局包。 - -### 步骤 3：修改 devcontainer.json 文件 - -添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将在代码空间启动时添加属性以安装扩展和恢复项目依赖项。 - -1. 在 Explorer 中，展开 `.devcontainer` 文件夹，从树中选择 `devcontainer.json` 文件并打开它。 - - ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png) - -2. 更新 `devcontainer.json` 文件中的 `extensions` 列表，以添加一些在处理项目时有用的扩展。 - - ```json{:copy} - "extensions": [ - "ms-dotnettools.csharp", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. 取消注释 `postCreateCommand` 以便在代码空间设置过程中恢复依赖项。 - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "dotnet restore", - ``` - -4. 要重建容器并应用 devcontainer.json 更改，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 - - ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - - 在代码空间内进行重建可确保在将更改提交到仓库之前，更改能够按预期工作。 如果某些问题导致了故障，您将进入带有恢复容器的代码空间中，您可以从该容器进行重建以继续调整容器。 - -5. 通过验证是否安装了 "Code Spell Checker" 扩展，检查更改是否成功应用。 - - ![扩展列表](/assets/images/help/codespaces/dotnet-extensions.png) - -### 步骤 4：运行应用程序 - -在上一节中，您使用 `postCreateCommand` 通过 pip3 安装了一组包。 现在安装了依赖项，我们可以运行应用程序。 - -1. 通过按 `F5` 或在终端中输入 `dotnet watch run` 来运行您的应用程序。 - -2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。 - - ![端口转发信息框](/assets/images/help/codespaces/python-port-forwarding.png) - -### 步骤 5：提交更改 - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 后续步骤 - -现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 C# (.NET) 项目。 以下是用于更高级场景的一些额外资源。 - -- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md deleted file mode 100644 index eabf34d9bb..0000000000 --- a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: 开始在代码空间中使用 Java 项目 -shortTitle: 开始使用 Java 项目 -intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 Java 项目。' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### 简介 - -本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 Java 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。 - -#### 基本要求 - -- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 Java 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/microsoft/vscode-remote-try-java -- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。 - -### 步骤 1：在代码空间中打开项目 - -1. 导航到项目的仓库。 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 如果您看不到此选项，则您的项目不能用于 {% data variables.product.prodname_codespaces %}。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. 要创建新的代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - -创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Java、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。 - -您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。 - -{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 更多信息请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -### 步骤 2：从模板将开发容器添加到您的代码空间 - -默认代码空间容器附带最新的 Java 版本、包管理器（Maven、Gradle）和其他预装的常用工具。 但是，我们建议您设置一个自定义容器来定义项目所需的工具和脚本。 这将确保仓库中的所有 {% data variables.product.prodname_codespaces %} 用户都拥有完全可复制的环境。 - -要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 有关开发容器的更多信息，请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -1. 访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "dev container"。 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. 对于此示例，单击 **Java**。 实际上，您可以选择任何特定于 Java 的容器或 Java 和 Azure 函数等工具的组合。 ![从列表中选择 Java 选项](/assets/images/help/codespaces/add-java-prebuilt-container.png) -4. 单击推荐的 Java 版本。 ![Java 版本选择](/assets/images/help/codespaces/add-java-version.png) -5. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### 开发容器的剖析 - -添加 Java 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件： - -- `devcontainer.json` -- Dockerfile - -新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。 - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java -{ - "name": "Java", - "build": { - "dockerfile": "Dockerfile", - "args": { - // Update the VARIANT arg to pick a Java version: 11, 14 - "VARIANT": "11", - // Options - "INSTALL_MAVEN": "true", - "INSTALL_GRADLE": "false", - "INSTALL_NODE": "false", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "java.home": "/docker-java-home", - "maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "vscjava.vscode-java-pack" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "java -version", - - // Uncomment to connect as a non-root user. 请参阅 https://aka.ms/vscode-remote/containers/non-root。 - "remoteUser": "vscode" -} -``` - -- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。 -- **Build** - 构建属性。 - - **Dockerfile** - 在构建对象中，dockerfile 是对 Dockerfile 的引用，该文件也是从模板中添加的。 - - **Args** - - **Variant**：此文件仅包含一个构建参数，即传递到 Dockerfile 的 Java 版本。 -- **Settings** - 它们是您可以设置的 {% data variables.product.prodname_vscode %} 设置。 - - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。 -- **Extensions** - 它们是默认包含的扩展名。 - - **Vscjava.vscode-java-pack** - Java 扩展包为 Java 开发提供了流行的扩展，以帮助您入门。 -- **forwardPorts** - 此处列出的任何端口都将自动转发。 -- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间后执行任何操作，您可以在此处执行。 -- **remoteUser** - 默认情况下，您以 `vscode` 用户身份运行，但您可以选择将其设置为 `root`。 - -##### Dockerfile - -```bash -# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile -ARG VARIANT="14" -FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT} - -# [Optional] Install Maven or Gradle -ARG INSTALL_MAVEN="false" -ARG MAVEN_VERSION=3.6.3 -ARG INSTALL_GRADLE="false" -ARG GRADLE_VERSION=5.4.1 -RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \ - && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi - -# [Optional] Install a version of Node.js using nvm for front end dev -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -您可以使用 Dockerfile 添加其他容器层，以指定要包含在 Dockerfile 中的操作系统包、Java 版本或全局包。 - -### 步骤 3：修改 devcontainer.json 文件 - -添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将在代码空间启动时添加属性以安装扩展和项目依赖项。 - -1. 在 Explorer 中，从树中选择 `devcontainer.json` 文件来打开它。 您可能需要展开 `.devcontainer` 文件夹才能看到它。 - - ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png) - -2. 在 `devcontainer.json` 文件中的 `extensions` 后面添加以下行。 - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - 有关 `devcontainer.json` 属性的更多信息，请参阅 Visual Studio 文档中的 [devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)。 - -3. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 - - ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - - 在代码空间内进行重建可确保在将更改提交到仓库之前，更改能够按预期工作。 如果某些问题导致了故障，您将进入带有恢复容器的代码空间中，您可以从该容器进行重建以继续调整容器。 - - -### 步骤 4：运行应用程序 - -在上一节中，您使用 `postCreateCommand` 通过 npm 安装了一组包。 您现在可以使用它来通过 npm 运行应用程序。 - -1. 按 `F5` 运行应用程序。 - -2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。 - - ![端口转发信息框](/assets/images/help/codespaces/codespaces-port-toast.png) - -### 步骤 5：提交更改 - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 后续步骤 - -现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 Java 项目。 以下是用于更高级场景的一些额外资源。 - -- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md deleted file mode 100644 index 281646ef37..0000000000 --- a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: 开始在代码空间中使用 Node.js 项目 -shortTitle: 开始使用 Node.js 项目 -intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 JavaScript、Node.js 或 TypeScript 项目。' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Node - - JavaScript ---- - -{% data reusables.codespaces.release-stage %} - -### 简介 - -本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 JavaScript、Node.js 或 TypeScript 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。 - -#### 基本要求 - -- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 JavaScript、Node.js 或 TypeScript 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/microsoft/vscode-remote-try-node -- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。 - -### 步骤 1：在代码空间中打开项目 - -1. 导航到项目的仓库。 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 如果您看不到此选项，则您的项目不能用于 {% data variables.product.prodname_codespaces %}。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. 要创建新的代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - -创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Node.js、JavaScript、Typescript、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。 - -您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。 - -{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 更多信息请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - -### 步骤 2：从模板将开发容器添加到您的代码空间 - -默认代码空间容器将支持运行 Node.js 项目，如开箱即用 [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node)。 通过设置自定义容器，您可以自定义在代码空间创建过程中运行的工具和脚本，并确保为仓库中的所有 {% data variables.product.prodname_codespaces %} 用户提供完全可复制的环境。 - -要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 有关开发容器的更多信息，请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - -1. 访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "dev container"。 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png) -3. 对于此示例，单击 **Node.js**。 如果需要其他功能，您可以选择任何特定于节点或工具（如节点和 MongoDB）组合的容器。 ![从列表中选择节点选项](/assets/images/help/codespaces/add-node-prebuilt-container.png) -4. 单击推荐的 Node.js 版本。 ![Node.js 版本选择](/assets/images/help/codespaces/add-node-version.png) -5. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### 开发容器的剖析 - -添加 Node.js 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件： - -- `devcontainer.json` -- Dockerfile - -新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。 - -##### devcontainer.json - -```json -// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: -// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node -{ - "name": "Node.js", - "build": { - "dockerfile": "Dockerfile", - // Update 'VARIANT' to pick a Node version: 10, 12, 14 - "args": { "VARIANT": "14" } - }, - - // 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": [ - "dbaeumer.vscode-eslint" - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "yarn install", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "node" -} -``` - -- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。 -- **Build** - 构建属性。 - - **dockerfile** - 在构建对象中，dockerfile 是对 Dockerfile 的引用，该文件也是从模板中添加的。 - - **Args** - - **Variant**：此文件仅包含一个构建参数，即我们要用于传递到 Dockerfile 的节点变量。 -- **Settings** - 它们是您可以设置的 {% data variables.product.prodname_vscode %} 设置。 - - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。 -- **Extensions** - 它们是默认包含的扩展名。 - - **Dbaeumer.vscode-eslint** - ES lint 是 linting 的良好扩展，但是对于 JavaScript，您还可以包括许多出色的 Marketplace 扩展。 -- **forwardPorts** - 此处列出的任何端口都将自动转发。 -- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间后执行任何操作，您可以在此处执行。 -- **remoteUser** - 默认情况下，您以 vscode 用户身份运行，但您可以选择将其设置为 root。 - -##### Dockerfile - -```bash -# [Choice] Node.js version: 14, 12, 10 -ARG VARIANT="14-buster" -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT} - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment if you want to install an additional version of node using nvm -# ARG EXTRA_NODE_VERSION=10 -# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}" - -# [Optional] Uncomment if you want to install more global node modules -# RUN su node -c "npm install -g " -``` - -您可以使用 Dockerfile 添加其他容器层，以指定要包含在 Dockerfile 中的操作系统包、节点版本或全局包。 - -### 步骤 3：修改 devcontainer.json 文件 - -添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将添加属性以在代码空间启动时安装 npm，并使容器内的端口列表在本地可用。 - -1. 在 Explorer 中，从树中选择 `devcontainer.json` 文件来打开它。 您可能需要展开 `.devcontainer` 文件夹才能看到它。 - - ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png) - -2. 在 `devcontainer.json` 文件中的 `extensions` 后面添加以下行： - - ```json{:copy} - "postCreateCommand": "npm install", - "forwardPorts": [4000], - ``` - - 有关 `devcontainer.json` 属性的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的 [devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)。 - -3. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 - - ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - - 在代码空间内进行重建可确保在将更改提交到仓库之前，更改能够按预期工作。 如果某些问题导致了故障，您将进入带有恢复容器的代码空间中，您可以从该容器进行重建以继续调整容器。 - - -### 步骤 4：运行应用程序 - -在上一节中，您使用 `postCreateCommand` 通过 npm 安装了一组包。 您现在可以使用它来通过 npm 运行应用程序。 - -1. 在终端中使用 `npm start` 运行启动命令。 - - ![终端的 npm 启动](/assets/images/help/codespaces/codespaces-npmstart.png) - -2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。 - - ![端口转发信息框](/assets/images/help/codespaces/codespaces-port-toast.png) - -### 步骤 5：提交更改 - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 后续步骤 - -现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 JavaScript 项目。 以下是用于更高级场景的一些额外资源。 - -- [管理代码空间的加密密码](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) -- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces) -- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md deleted file mode 100644 index 0cc1b6635c..0000000000 --- a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -title: 开始在代码空间中使用 Python 项目 -shortTitle: 开始使用 Python 项目 -intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 Python 项目。' -versions: - free-pro-team: '*' -type: tutorial -topics: - - Codespaces - - Developer - - Python ---- - -{% data reusables.codespaces.release-stage %} - -### 简介 - -本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 Python 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。 - -#### 基本要求 - -- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 Python 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/2percentsilk/python-quickstart. -- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。 - -### 步骤 1：在代码空间中打开项目 - -1. 导航到项目的仓库。 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 如果您看不到此选项，则您的项目不能用于 {% data variables.product.prodname_codespaces %}。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -2. 要创建新的代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - -创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Node.js、JavaScript、Typescript、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 nano。 - -您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。 - -{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 更多信息请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -### 步骤 2：从模板将开发容器添加到您的代码空间 - -默认代码空间容器附带最新的 Python 版本、包管理器（pip、Miniconda）和其他预装的常用工具。 但是，我们建议您设置一个自定义容器来定义项目所需的工具和脚本。 这将确保仓库中的所有 {% data variables.product.prodname_codespaces %} 用户都拥有完全可复制的环境。 - -要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 有关开发容器的更多信息，请参阅“[为项目配置代码空间](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 - - -1. 访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "dev container"。 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png) -2. 对于此示例，单击 **Python 3**。 如果需要其他功能，您可以选择任何特定于 Python 或工具（如 Python 3 和 PostgresSQL）组合的容器。 ![从列表中选择 Python 选项](/assets/images/help/codespaces/add-python-prebuilt-container.png) -3. 单击推荐的 Python 版本。 ![Python 版本选择](/assets/images/help/codespaces/add-python-version.png) -4. 接受默认选项，将 Node.js 添加到您的自定义中。 ![添加 Node.js 选择](/assets/images/help/codespaces/add-nodejs-selection.png) -5. 要重建容器，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - -#### 开发容器的剖析 - -添加 Python 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件： - -- `devcontainer.json` -- Dockerfile - -新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。 - -##### devcontainer.json - -```json -{ - "name": "Python 3", - "build": { - "dockerfile": "Dockerfile", - "context": "..", - "args": { - // Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9 - "VARIANT": "3", - // Options - "INSTALL_NODE": "true", - "NODE_VERSION": "lts/*" - } - }, - - // Set *default* container specific settings.json values on container create. - "settings": { - "terminal.integrated.shell.linux": "/bin/bash", - "python.pythonPath": "/usr/local/bin/python", - "python.linting.enabled": true, - "python.linting.pylintEnabled": true, - "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", - "python.formatting.blackPath": "/usr/local/py-utils/bin/black", - "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", - "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", - "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", - "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", - "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", - "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", - "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" - }, - - // Add the IDs of extensions you want installed when the container is created. - "extensions": [ - "ms-python.python", - ], - - // Use 'forwardPorts' to make a list of ports inside the container available locally. - // "forwardPorts": [], - - // Use 'postCreateCommand' to run commands after the container is created. - // "postCreateCommand": "pip3 install --user -r requirements.txt", - - // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. - "remoteUser": "vscode" -} -``` - -- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。 -- **Build** - 构建属性。 - - **Dockerfile** - 在构建对象中，`dockerfile` 是对 Dockerfile 的引用，该文件也是从模板中添加的。 - - **Args** - - **Variant**：此文件仅包含一个构建参数，即我们要用于传递到 Dockerfile 的节点变量。 -- **Settings** - 它们是 {% data variables.product.prodname_vscode %} 设置。 - - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。 -- **Extensions** - 它们是默认包含的扩展名。 - - **ms-python.python** - Microsoft Python 扩展为 Python 语言提供丰富的支持（对于所有积极支持的语言版本：>=3.6），包括 IntelliSense、linting、调试、代码导航、代码格式化、重构、变量资源管理器、测试资源管理器等功能。 -- **forwardPorts** - 此处列出的任何端口都将自动转发。 -- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间（例如 `pip3 install -r requirements`）后执行任何操作，您可以在此处执行。 -- **remoteUser** - 默认情况下，您以 `vscode` 用户身份运行，但您可以选择将其设置为 `root`。 - -##### Dockerfile - -```bash -# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6 -ARG VARIANT="3" -FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} - -# [Option] Install Node.js -ARG INSTALL_NODE="true" -ARG NODE_VERSION="lts/*" -RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi - -# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. -# COPY requirements.txt /tmp/pip-tmp/ -# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ -# && rm -rf /tmp/pip-tmp - -# [Optional] Uncomment this section to install additional OS packages. -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends - -# [Optional] Uncomment this line to install global node packages. -# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -``` - -您可以使用 Dockerfile 添加其他容器层，以指定要包含在容器中的操作系统包、节点版本或全局包。 - -### 步骤 3：修改 devcontainer.json 文件 - -添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将在代码空间启动时添加属性以安装扩展和项目依赖项。 - -1. 在 Explorer 中，展开 `.devcontainer` 文件夹，从树中选择 `devcontainer.json` 文件并打开它。 - - ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/devcontainers-options.png) - -2. 更新 `devcontainer.json` 文件中的 `extensions` 列表，以添加一些在处理项目时有用的扩展。 - - ```json{:copy} - "extensions": [ - "ms-python.python", - "cstrap.flask-snippets", - "streetsidesoftware.code-spell-checker", - ], - ``` - -3. 取消注释 `postCreateCommand` 以自动安装要求，作为代码空间设置过程的一部分。 - - ```json{:copy} - // Use 'postCreateCommand' to run commands after the container is created. - "postCreateCommand": "pip3 install --user -r requirements.txt", - ``` - -4. 要重建容器并应用 devcontainer.json 更改，请访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "rebuild"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 - - ![重建容器选项](/assets/images/help/codespaces/codespaces-rebuild.png) - - 在代码空间内进行重建可确保在将更改提交到仓库之前，更改能够按预期工作。 如果某些问题导致了故障，您将进入带有恢复容器的代码空间中，您可以从该容器进行重建以继续调整容器。 - -5. 通过验证是否安装了 Code Spell Checker 和 Flask Snippet 扩展，检查更改是否成功应用。 - - ![扩展列表](/assets/images/help/codespaces/python-extensions.png) - -### 步骤 4：运行应用程序 - -在上一节中，您使用 `postCreateCommand` 通过 pip3 安装了一组包。 现已安装您的依赖项，您可以运行应用程序。 - -1. 通过按 `F5` 或在代码空间终端中输入 `python -m flask run` 来运行您的应用程序。 - -2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。 - - ![端口转发信息框](/assets/images/help/codespaces/python-port-forwarding.png) - -### 步骤 5：提交更改 - -{% data reusables.codespaces.committing-link-to-procedure %} - -### 后续步骤 - -现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 Python 项目。 以下是用于更高级场景的一些额外资源。 - -- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces) -- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces) -- [代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace) diff --git a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md b/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md deleted file mode 100644 index 90420f650f..0000000000 --- a/translations/zh-CN/content/codespaces/getting-started-with-codespaces/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: '开始使用 {% data variables.product.prodname_codespaces %}' -intro: '了解如何开始使用 {% data variables.product.prodname_codespaces %}，包括特定语言的设置和配置。' -versions: - free-pro-team: '*' -children: - - /getting-started-with-your-nodejs-project-in-codespaces - - /getting-started-with-your-dotnet-project - - /getting-started-with-your-java-project-in-codespaces - - /getting-started-with-your-python-project-in-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/guides.md b/translations/zh-CN/content/codespaces/guides.md deleted file mode 100644 index 19e5d5d63c..0000000000 --- a/translations/zh-CN/content/codespaces/guides.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: 代码空间指南 -shortTitle: 指南 -intro: '了解如何充分利用 GitHub {% data reusables.gated-features.codespaces %}' -allowTitleToDifferFromFilename: true -layout: product-sublanding -versions: - free-pro-team: '*' -includeGuides: - - /codespaces/quickstart - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/deleting-a-codespace - - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace - - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces - - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces ---- - diff --git a/translations/zh-CN/content/codespaces/index.md b/translations/zh-CN/content/codespaces/index.md deleted file mode 100644 index d66f816e63..0000000000 --- a/translations/zh-CN/content/codespaces/index.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: GitHub 代码空间文档 -beta_product: true -shortTitle: GitHub Codespaces -intro: 创建一个代码空间，在一个安全、可配置、专用的开发环境中开始开发，该环境可以按照您希望的方式和位置工作。 -introLinks: - quickstart: /codespaces/quickstart - overview: /codespaces/about-codespaces -featuredLinks: - guides: - - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces - - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project - guideCards: - - /codespaces/developing-in-codespaces/creating-a-codespace - - /codespaces/developing-in-codespaces/developing-in-a-codespace - - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code - - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account - popular: - - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project - - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization - - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces - - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces - popularHeading: Managing GitHub Codespaces -product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' -redirect_from: - - /github/developing-online-with-github-codespaces - - /github/developing-online-with-codespaces -layout: product-landing -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /quickstart - - /getting-started-with-codespaces - - /setting-up-your-codespace - - /developing-in-codespaces - - /managing-your-codespaces - - /managing-codespaces-for-your-organization - - /codespaces-reference - - /guides ---- - diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md deleted file mode 100644 index b318354a5b..0000000000 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: 管理组织的代码空间 -intro: '您可以管理和审查您组织中的用户如何使用 {% data variables.product.prodname_github_codespaces %}。' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - - /managing-access-and-security-for-your-organizations-codespaces - - /managing-user-permissions-for-your-organization - - /reviewing-your-organizations-audit-logs-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md deleted file mode 100644 index fde2f9896e..0000000000 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: 管理组织代码空间的访问和安全 -shortTitle: 管理组织的访问和安全 -intro: '您可以管理 {% data variables.product.prodname_codespaces %} 可以访问的组织仓库。' -permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator -redirect_from: - - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces - - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -组织所有者可以管理代码空间有权访问哪些仓库。 - -默认情况下，代码空间只能访问创建它的仓库。 为组织拥有的仓库启用访问和安全后，则为该仓库创建的任何代码空间都将对该组织拥有的和代码空间创建者有权访问的所有其他仓库具有读取和写入权限。 如果要限制代码空间可以访问的仓库，您可以将其限制为创建代码空间的仓库或特定仓库。 您应该只对您信任的仓库启用访问和安全。 - -要管理组织中的哪些用户可以使用 {% data variables.product.prodname_codespaces %}，请参阅“[管理组织的用户权限](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)”。 - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. 在“Access and security（访问和安全）”下，为组织选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) -1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问组织拥有的其他仓库。 对于您要允许其代码空间访问其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md deleted file mode 100644 index 8c4f220e2d..0000000000 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: 为您的仓库和代码空间组织管理加密的密钥 -shortTitle: 管理仓库和组织的密钥 -intro: '加密密钥允许您将敏感信息存储在您的组织、仓库或 {% data variables.product.prodname_codespaces %} 中。' -permissions: 'To manage secrets for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -### 关于密钥 - -密钥是您在组织或仓库中创建的加密环境变量。 您创建的密钥可用于 {% data variables.product.prodname_codespaces %}。 GitHub 在密钥到达 GitHub 之前使用 [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) 对其加密，并且仅当您在代码空间中使用它们时才予以解密。 - -组织级密钥允许在多个仓库之间共享密钥，从而减少创建重复密钥的需要。 您可以使用访问策略来控制哪些仓库可以使用组织密钥。 - -{% data reusables.codespaces.secrets-on-start %} - -#### 命名密钥 - -{% data reusables.codespaces.secrets-naming %} 例如，在仓库级别创建的密钥必须在该仓库中具有唯一的名称， 而在组织级创建的密钥必须在该级别有独特的名称。 - - {% data reusables.codespaces.secret-precedence %} - -#### 密码的限制 - -每个组织最多可存储 100 个密钥，每个仓库最多可存储 100 个密钥。 - -密码大小限于 64 KB。 - -### 为仓库添加密钥 - -要为组织仓库创建密码，您必须具有管理员访问权限。 - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.github-actions.sidebar-secret %} -1. 向下滚动页面并在 **Secrets（密钥）**下选择 **Codespaces**。 ![侧栏中的代码空间选项](/assets/images/help/codespaces/codespaces-option-secrets.png) -1. 在页面顶部，单击 **New repository secret（新仓库密钥）**。 -1. 在 **Name（名称）**输入框中键入密码的名称。 -1. 输入密码的值。 -1. 单击 **Add secret（添加密码）**。 - -### 为组织添加密钥 - -在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。 - -{% data reusables.github-actions.permissions-statement-secrets-organization %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. 向下滚动页面并在 **Secrets（密钥）**下选择 **Codespaces**。 ![侧栏中的代码空间选项](/assets/images/help/codespaces/codespaces-option-secrets-org.png) -1. 在页面顶部，单击 **New organization secret（新组织密钥）**。 -1. 在 **Name（名称）**输入框中键入密码的名称。 -1. 输入密码的 **Value（值）**。 -1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 ![已选定私有仓库的仓库访问列表](/assets/images/help/codespaces/secret-repository-access.png) -1. 单击 **Add secret（添加密码）**。 - -### 审查对组织级别密码的访问权限 - -您可以检查哪些访问策略应用于组织中的密钥。 - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.github-actions.sidebar-secret %} -1. 密码列表包括任何已配置的权限和策略。 例如： ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png) -1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。 diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md deleted file mode 100644 index f65da25405..0000000000 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: 管理组织的用户权限 -intro: '您可以控制组织中的哪些用户可以使用 {% data variables.product.prodname_codespaces %}。' -permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Permissions - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -### 关于 {% data variables.product.prodname_codespaces %} 的用户权限 - -组织所有者可以控制组织中的哪些用户可以创建和使用代码空间。 - -要使用组织中的代码空间，用户必须对他们要使用代码空间的仓库至少具有写入权限。 您可以对组织中的所有用户启用代码空间，也可以仅对特定用户启用。 - -默认情况下，代码空间只能访问创建它的仓库。 如果您希望组织中的代码空间能够访问代码空间创建者可以访问的其他组织仓库，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的访问和安全](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)”。 - -### 配置组织中的哪些用户可以使用 {% data variables.product.prodname_codespaces %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.click-codespaces %} -1. 在“User permissions（用户权限）”下，选择以下选项之一： - - * **Disabled（禁用）**不允许任何组织成员使用 {% data variables.product.prodname_codespaces %}。 - * **Allow for all users（允许所有用户）**允许所有组织成员使用 {% data variables.product.prodname_codespaces %}。 - * **Selected users（所选用户）**选择特定组织成员使用 {% data variables.product.prodname_codespaces %}。 - - !["用户权限"单选按钮](/assets/images/help/codespaces/organization-user-permission-settings.png) diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md deleted file mode 100644 index fd55789c2a..0000000000 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: 查看组织的代码空间审核日志 -shortTitle: 查看组织的审核日志 -intro: '您可以使用审核日志查看与 {% data variables.product.prodname_codespaces %} 相关的所有操作。' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Security - - Administrator ---- - -{% data reusables.codespaces.release-stage %} - -当组织的任何成员执行与 {% data variables.product.prodname_codespaces %} 相关的操作时，您可以在审核日志中查看这些操作。 有关访问日志的信息，请参阅“[查看您的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)”。 - -![包含代码空间信息的审核日志](/assets/images/help/settings/codespaces-audit-log-org.png) - -审核日志包含操作执行人、操作内容和执行时间等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)”。 diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md deleted file mode 100644 index 979fe8be5e..0000000000 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: 管理代码空间 -intro: '您可以使用 {% data variables.product.prodname_github_codespaces %} 设置来管理代码空间可能需要的信息。' -versions: - free-pro-team: '*' -topics: - - Codespaces -redirect_from: - - /codespaces/working-with-your-codespace -children: - - /managing-encrypted-secrets-for-your-codespaces - - /managing-access-and-security-for-your-codespaces - - /reviewing-your-security-logs-for-codespaces - - /managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md deleted file mode 100644 index b008248c15..0000000000 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: 管理代码空间的访问和安全 -intro: '您可以管理 {% data variables.product.prodname_codespaces %} 可以访问的仓库。' -versions: - free-pro-team: '*' -topics: - - Codespaces ---- - -{% data reusables.codespaces.release-stage %} - -为用户帐户拥有的仓库启用访问和安全后，为该仓库创建的任何代码空间都将对您拥有的所有其他仓库具有读取和写入权限。 如果要限制代码空间可以访问的仓库，您可以将其限制为代码空间打开的仓库或特定仓库。 您应该只对您信任的仓库启用访问和安全。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. 在“Access and security（访问和安全）”下，为用户帐户选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问您拥有的其他仓库。 对于您要允许其代码空间访问您拥有的其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md deleted file mode 100644 index c06f352d13..0000000000 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: 管理代码空间的加密密码 -intro: 您可以在代码空间中存储要通过环境变量访问的敏感信息（如令牌）。 -versions: - free-pro-team: '*' -redirect_from: - - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces - - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces -type: how_to -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - - -### 关于 {% data variables.product.prodname_codespaces %} 的加密密码 - -您可以将要在代码空间中使用的加密密码添加到您的用户帐户。 例如，您可能想要存储和访问以下敏感信息作为加密密码。 - -- 对云服务的个人访问令牌 -- 服务主体 -- 订阅标识符 -- [私人映像注册表的凭据](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) - -您可以选择哪些仓库应有权访问每个密码。 然后，您可以在为有权访问密码的仓库创建的任何代码空间中使用该密码。 - -{% data reusables.codespaces.secrets-on-start %} - -#### 命名密钥 - -{% data reusables.codespaces.secrets-naming %} 例如，在仓库级别创建的密钥必须在该仓库中具有唯一的名称。 - - {% data reusables.codespaces.secret-precedence %} - -#### 密码的限制 - -您最多可以为 {% data variables.product.prodname_codespaces %} 存储 100 个密钥。 - -密码大小限于 64 KB。 - -### 添加密码 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. 在“Codespaces secrets（代码空间密码）”的右侧，单击 **New secret（新建密码）**。 !["新建密码"按钮](/assets/images/help/settings/codespaces-new-secret-button.png) -1. 在“Name（名称）”下，输入密码的名称。 !["名称"文本框](/assets/images/help/settings/codespaces-secret-name-field.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. 单击 **Add secret（添加密码）**。 - -### 编辑密码 - -您可以更新现有密码的值，也可以更改哪些仓库可以访问密码。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. 在“Codespaces secrets（代码空间密码）”下您要编辑的密码右侧，单击 **Update（更新）**。 !["更新" 按钮](/assets/images/help/settings/codespaces-secret-update-button.png) -1. 在“Value（值）”下，单击 **enter a new value（输入新值）**。 !["输入新值" 链接](/assets/images/help/settings/codespaces-secret-update-value-text.png) -{% data reusables.user_settings.codespaces-secret-value %} -{% data reusables.user_settings.codespaces-secret-repository-access %} -1. （可选）要删除密码对仓库的访问权限，请取消选择仓库。 ![删除对仓库访问权限的复选框](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. 单击 **Save changes（保存更改）**。 - -### 删除密码 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. 在“Codespaces secrets（代码空间密码）”下您要删除的密码右侧，单击 **Delete（删除）**。 !["删除" 按钮](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. 阅读警告，然后单击 **OK（确定）**。 ![确认删除密码](/assets/images/help/settings/codespaces-secret-delete-warning.png) diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md deleted file mode 100644 index 4e86415536..0000000000 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: 管理代码空间的 GPG 验证 -intro: '您可以允许 {% data variables.product.company_short %} 自动使用 GPG 对在代码空间中所做的提交进行签名，以便其他人可以确信更改来自受信任的源。' -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Developer - - Security -redirect_from: - - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces - - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces ---- - -{% data reusables.codespaces.release-stage %} - -启用 GPG 验证后，{% data variables.product.company_short %} 将自动对您在 {% data variables.product.prodname_codespaces %} 中所做的提交进行签名，并且该提交在 {% data variables.product.product_name %} 上具有已验证状态。 默认情况下，GPG 验证对您创建的代码空间禁用。 您可以选择对所有仓库或特定仓库允许 GPG 验证。 仅对您信任的仓库启用 GPG 验证。 有关 {% data variables.product.product_name %} 签名提交的更多信息，请参阅“[关于提交签名验证](/github/authenticating-to-github/about-commit-signature-verification)”。 - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.codespaces-tab %} -1. 在“GPG verification（GPG 验证）”下，选择您想要的 GPG 验证设置。 ![管理 GPG 验证的单选按钮](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) -1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击想要启用 GPG 验证的仓库。 对您要启用 GPG 验证的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md deleted file mode 100644 index eff0c29401..0000000000 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: 查看代码空间的安全日志 -shortTitle: 审查您的安全日志 -intro: '您可以使用安全日志查看与 {% data variables.product.prodname_codespaces %} 相关的所有操作。' -versions: - free-pro-team: '*' -topics: - - Codespaces - - Developer - - Security ---- - -{% data reusables.codespaces.release-stage %} - -### 关于 {% data variables.product.prodname_codespaces %} 的安全日志 - -当您在用户帐户拥有的仓库中执行与 {% data variables.product.prodname_codespaces %} 相关的操作时，您可以查看安全日志中的操作。 有关访问日志的信息，请参阅“[查看您的安全日志](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)”。 - -![包含代码空间信息的安全日志](/assets/images/help/settings/codespaces-audit-log.png) - -安全日志包括发生了什么操作以及何时执行的操作等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)”。 diff --git a/translations/zh-CN/content/codespaces/quickstart.md b/translations/zh-CN/content/codespaces/quickstart.md deleted file mode 100644 index 54fbd6fb46..0000000000 --- a/translations/zh-CN/content/codespaces/quickstart.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Codespaces 快速入门 -intro: '在 5 分钟或更短的时间内尝试 {% data variables.product.prodname_codespaces %}。' -allowTitleToDifferFromFilename: true -versions: - free-pro-team: '*' -type: quick_start -topics: - - Codespaces -redirect_from: - - /codespaces/codespaces-quickstart ---- - -{% data reusables.codespaces.release-stage %} - -### 简介 - -在本指南中， 您将从[样本仓库](https://github.com/2percentsilk/haikus-for-codespaces)创建一个代码空间，并探索代码空间中您可以使用的一些基本功能。 - -以下示例显示如何创建代码空间、连接到转发端口以查看您的运行应用程序，以及如何通过额外的扩展和 dotfile 个性化您的设置。 - -### 创建代码空间 - -1. 导航到[样本仓库](https://github.com/2percentsilk/haikus-for-codespaces)的主页。 - -2. 在仓库名称下，使用 {% octicon "download" aria-label="The download icon" %} **Code（代码）**下拉菜单选择 **Open with Codespaces（使用 Codespaces 打开）**。 - - ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/open-with-codespaces-button.png) - -3. 要创建代码空间，请单击 {% octicon "plus" aria-label="The plus icon" %} **New codespace（新建代码空间）**。 - - ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png) - -### 运行应用程序 - -在代码空间中打开项目后，您现在可以运行应用程序并在浏览器中启动它。 - -1. 通过在终端中输入 `npm run dev` 来启动应用程序。 此命令执行 package.json 文件中的 `dev` 脚本，并启动样本仓库中定义的 web 应用程序。 - - ![终端中的 npm run dev](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - -2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。 - - ![端口转发信息框](/assets/images/help/codespaces/quickstart-port-toast.png) - -3. 单击 **Open in Browser（在浏览器中打开）**，在新选项卡中查看正在运行的应用程序。 - -### 使用主题扩展进行个性化 - -在代码空间内，您可以访问 Visual Studio Code Marketplace。 在本示例中，您将安装可更改主题的扩展，但您可以安装对工作流程有用的任何扩展。 - -1. 在左侧栏中，单击扩展图标。 - -2. 在搜索栏中，输入 `fairyfloss` 并安装 fairyfloss 扩展。 - - ![添加扩展](/assets/images/help/codespaces/add-extension.png) - -3. 从列表中选择 `fairyfloss` 主题。 - - ![选择 fairyfloss 主题](/assets/images/help/codespaces/fairyfloss.png) - -4. 您在当前代码空间中对编辑器设置（如主题和键盘绑定）的更改通过 [Settings Sync（设置同步）](https://code.visualstudio.com/docs/editor/settings-sync)自动同步到其他代码空间。 - -### 使用 dotfile 个性化 - -如果您在 GitHub 上的用户帐户拥有名为 dotfiles 的公共仓库，GitHub 会在代码空间创建过程中自动使用此仓库来个性化您的代码空间环境。 - -此示例引导您为代码空间创建 dotfile 仓库。 - -1. 导航到样本 [dotfiles 仓库](https://github.com/aw-test-93/dotfiles/)。 - -2. 将仓库复刻到您的帐户，并确保它是公开的。 - - 验证在您的帐户下创建的仓库是否名为 dotfiles，例如 `yourname/dotfiles`。 任何其他名称将导致 {% data variables.product.prodname_codespaces %} 忽略个性化仓库。 - -3. 从[样本应用程序仓库](https://github.com/2percentsilk/haikus-for-codespaces)创建新的代码空间，因为 dotfile 更新仅在创建时应用。 样本 dotfiles 将命令提示符更改为粗体紫色和蓝色文本。 - - ![自定义命令提示符](/assets/images/help/codespaces/custom-prompt.png) - -### 后续步骤 - -您已经成功创建、个性化并在代码空间中运行了第一个应用程序，但还有很多需要探索的地方！ 以下是一些帮助您对 {% data variables.product.prodname_codespaces %} 执行后续操作的有用资源： - - 使用带有特定语言的 {% data variables.product.prodname_codespaces %} 的“[入门指南](/codespaces/getting-started-with-codespaces)” - - [创建自定义配置](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)以配置项目的 {% data variables.product.prodname_codespaces %}。 diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md deleted file mode 100644 index 66db1f03a9..0000000000 --- a/translations/zh-CN/content/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: 为项目配置 Codespaces -intro: '您可以使用 `devcontainer.json` 文件来定义仓库的 {% data variables.product.prodname_codespaces %} 环境。' -permissions: People with write permissions to a repository can create or edit the codespace configuration. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project - - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### 关于开发容器 - -开发容器是 {% data variables.product.prodname_codespaces %} 用于提供项目开发所需的工具和运行时的环境。 在 {% data variables.product.prodname_codespaces %} 中使用开发容器时，您可以[使用默认配置](#using-the-default-configuration)、[使用预先定义的配置](#using-a-pre-defined-container-configuration)或[创建自己的配置](#creating-a-custom-codespace-configuration)。 您选择的选项取决于用户在项目中取得成功可能需要使用的工具、运行时、依赖项和工作流程。 - -{% data variables.product.prodname_codespaces %} 允许使用 `devcontainer.json` 文件针对每个项目和每个分支进行自定义。 此配置文件通过定义可包括框架、工具、扩展和端口转发的开发容器，确定任何人为仓库创建的每个新代码空间的环境。 Dockerfile 还可与 `.devcontainer` 文件夹中的 `devcontainer.json` 文件一起使用，以定义创建容器映像所需的所有要素。 - -#### devcontainer.json - -{% data reusables.codespaces.devcontainer-location %} - -您可以使用 `devcontainer.json` 为整个代码空间环境设置默认设置，包括编辑器，但您也可以在 `.vscode/set.json` 文件中设置代码空间中单个[工作空间](https://code.visualstudio.com/docs/editor/workspaces)的编辑器特定设置。 - -有关在 `devcontainer.json` 中可以设置的设置和属性，请参阅 {% data variables.product.prodname_vscode %} 文档中的 [devcontainer.json 参考](https://aka.ms/vscode-remote/devcontainer.json)。 - -#### Dockerfile - -Dockerfile 也存在于 `.devcontainer` 文件夹中。 - -您可以将 Dockerfile 添加到项目中来定义容器映像和安装软件。 在 Dockerfile 中，您可以使用 `FROM` 来指定容器映像。 - -```Dockerfile -FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14 - -# ** [Optional] Uncomment this section to install additional packages. ** -# USER root -# -# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ -# && apt-get -y install --no-install-recommends -# -# USER codespace -``` - -您可以使用 `RUN` 指令安装任何软件并使用 `&&` 加入命令。 - -使用 `dockerfile` 属性，在您的 `devcontainer.json` 文件中引用 Dockerfile。 - -```json -{ - ... - "build": { "dockerfile": "Dockerfile" }, - ... -} -``` - -有关在开发容器中使用 Dockerfile 的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[创建开发容器](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)。 - -### 使用默认配置 - -如果您没有在仓库中定义配置，{% data variables.product.prodname_dotcom %} 将创建一个具有基本 Linux 映像的代码空间。 基本 Linux 映像包括语言和运行时，例如 Python、Node.js、JavaScript、TypeScript、C++、Java、.NET、PHP、PowerShell、Go、Ruby 和 Rust。 它还包括其他开发工具和实用程序，例如 git、GitHub CLI、yarn、openssh 和 vim。 要查看包含的所有语言、运行时和工具，请在代码空间终端内使用 `devcontainer-info content-url` 命令，然后遵循命令输出的 url。 - -或者，要详细了解基本 Linux 映像中包含的所有内容，请参阅 [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers) 仓库中的最新文件。 - -如果您要处理使用 {% data variables.product.prodname_codespaces %} 提供的语言和工具的小型项目，默认配置是个不错的选择。 - - -### 使用预定义的容器配置 - -预定义容器定义包括特定项目类型的共同配置，可帮助您利用现有的配置快速开始使用，配置中已经有适当的容器选项、{% data variables.product.prodname_vscode %} 设置和应该安装的 {% data variables.product.prodname_vscode %} 扩展。 - -如果您需要一些额外的扩展性，使用预先定义的配置是一个好主意。 您也可以从预定义的配置开始，然后根据项目的设置对其进行修改。 - -1. 要访问命令面板，请在左上角选择应用程序菜单，从 **View（视图）**菜单中单击 **Command Palette…（命令面板…）**，然后开始输入 "Codespaces: Add Development Container Configuration Files..."。 单击 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![命令选择板中的"Codespaces：添加开发容器配置文件..."](/assets/images/help/codespaces/add-prebuilt-container-command.png) -1. 单击要使用的定义。 ![预定义容器定义列表](/assets/images/help/codespaces/predefined-container-definitions-list.png) -1. 按照提示自定义您的定义。 -1. 单击 **OK（确定）**。 ![确定按钮](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。 ![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/rebuild-prompt.png) - - -### 创建自定义代码空间配置 - -如果任何预定义的配置都不能满足您的需要，您可以通过添加 `devcontainer.json` 文件来创建自定义配置。 {% data reusables.codespaces.devcontainer-location %} - -在该文件中，您可以使用[支持的配置键](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)来指定代码空间环境的各个方面，例如要安装哪些 {% data variables.product.prodname_vscode %} 扩展。 - -{% data reusables.codespaces.vscode-settings-order %} - -您可以在两个地方定义 {% data variables.product.prodname_vscode %} 的默认编辑器设置。 - -* `.vscode/settings.json` 中定义的编辑器设置在代码空间中用作 _Workspace_ 范围的设置。 -* `devcontainer.json` 的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。 - -在更新 `devcontainer.json` 文件后，您可以重建代码空间的容器来应用更改。 更多信息请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。 - - - - -### 应用对配置的更改 - -{% data reusables.codespaces.apply-devcontainer-changes %} - -1. {% data reusables.codespaces.rebuild-command %} -![命令面板中的"Codespaces：重建容器"](/assets/images/help/codespaces/rebuild-container-command.png) -1. {% data reusables.codespaces.recovery-mode %} 修复配置中的错误。 ![有关恢复模式的错误消息](/assets/images/help/codespaces/recovery-mode-error-message.png) - - 要通过查看创建日志来诊断错误，请单击 **View creation log（查看创建日志）**。 - - 要修复日志中发现的错误，请更新您的 `devcontainer.json` 文件。 - - 要应用更改，请重建容器。 {% data reusables.codespaces.rebuild-command %} diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md deleted file mode 100644 index a9469721fb..0000000000 --- a/translations/zh-CN/content/codespaces/setting-up-your-codespace/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: 设置代码空间 -intro: '{% data variables.product.prodname_codespaces %} 是您专用的环境。 您可以使用开发容器配置代码空间以安装依赖项，也可以添加 dotfile 以个性化用户设置。' -versions: - free-pro-team: '*' -topics: - - Codespaces -children: - - /configuring-codespaces-for-your-project - - /personalizing-codespaces-for-your-account ---- - -{% data reusables.codespaces.release-stage %} diff --git a/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md b/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md deleted file mode 100644 index fe2191be7e..0000000000 --- a/translations/zh-CN/content/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: 个性化您账户的 Codespaces -intro: '您可以通过使用 {% data variables.product.product_name %} 上的 `dotfiles` 仓库或使用设置同步来个性化 {% data variables.product.prodname_codespaces %}。' -permissions: 'Anyone can personalize {% data variables.product.prodname_codespaces %} for their user account.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account - - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account -versions: - free-pro-team: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals ---- - -{% data reusables.codespaces.release-stage %} - -### 关于个性化 {% data variables.product.prodname_codespaces %} - -在使用任何开发环境时，根据您的喜好和工作流程自定义设置和工具是一个重要步骤。 {% data variables.product.prodname_codespaces %} 允许两种主要方法个性化您的代码空间。 - -- [设置同步](#settings-sync) - 您可以在 {% data variables.product.prodname_codespaces %} 与其他 {% data variables.product.prodname_vscode %}实例之间使用和共享 {% data variables.product.prodname_vscode %} 设置。 -- [Dotfiles](#dotfiles) - 您可以使用公共 `dotfiles` 仓库来指定脚本、shell 首选项和其他配置。 - -{% data variables.product.prodname_codespaces %} 个性化适用于您创建的任何代码空间。 - -项目维护员还可以定义默认配置，将应用到任何人创建的仓库的每个代码空间。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)”。 - -### 设置同步 - -设置同步允许您在机器和 {% data variables.product.prodname_vscode %} 实例中共享配置，如设置、键盘快捷方式、片段、扩展和 UI 状态。 - -设置同步默认打开。 要配置任何设置，在活动栏的左下角，选择 {% octicon "gear" aria-label="The gear icon" %} 并单击 **Settings Sync is on（设置同步打开）**。 从对话框中，您可以选择配置、显示设置和数据，或关闭设置同步。 - -![在管理菜单中设置同步选项](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) - -更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的[设置同步指南](https://code.visualstudio.com/docs/editor/settings-sync)。 - -### Dotfiles - -Dotfiles 是类似 Unix 的系统上以 `.` 开头的文件和文件夹，用于控制系统上应用程序和 shell 的配置。 您可以在 {% data variables.product.prodname_dotcom %} 上的仓库中存储和管理 dotfiles。 有关 `dotfiles` 仓库中所含内容的建议和教程，请参阅 [GitHub 执行 dotfiles](https://dotfiles.github.io/)。 - -如果您在 {% data variables.product.prodname_dotcom %} 上的用户帐户拥有名为 `dotfiles` 的公共仓库，{% data variables.product.prodname_dotcom %} 会自动使用这个仓库来个性化设置您的代码空间环境。 私有 `dotfiles` 仓库目前不支持。 - -`dotfiles` 仓库可能包括 shell 别名和首选项、您想要安装的任何工具或您想要执行的任何其他代码个性化。 - -创建新的代码空间时，{% data variables.product.prodname_dotcom %} 会将 `dotfile` 仓库克隆到代码空间环境，并查找以下文件之一来设置环境。 - -* _install.sh_ -* _安装_ -* _bootstrap.sh_ -* _bootstrap_ -* _script/bootstrap_ -* _setup.sh_ -* _setup_ -* _script/setup_ - -如果未找到这些文件，则 `dotfiles` 中以 `.` 开头的文件或文件夹通过符号链接到代码空间的 `~` 或 `$HOME` 目录。 - -对 `dotfile` 仓库所做的任何更改只会应用到每个新的代码空间，而不影响任何现有的代码空间。 - -{% note %} - -**注：**目前，{% data variables.product.prodname_codespaces %} 不支持使用 `dotfiles` 仓库个性化 {% data variables.product.prodname_vscode %} 编辑器的_用户_设置。 您可以为项目仓库中的特定项目设置默认的 _Workspace_ 和 _Remote [Codespaces]_ 设置。 更多信息请参阅“[为项目配置 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)”。 - -{% endnote %} - -您还可以配置用户帐户的设置以添加加密密码、启用 GPG 验证以及允许代码空间访问其他仓库。 更多信息请参阅“[管理 {% data variables.product.prodname_codespaces %} 的加密密码](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)”、“[管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)”以及“[管理 {% data variables.product.prodname_codespaces %} 的访问权限和设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)”。 - -### 延伸阅读 - -* "[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)" diff --git a/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md deleted file mode 100644 index 72c8cd8a84..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_codespaces %} 在测试期间可免费使用。 当 {% data variables.product.prodname_codespaces %} 公开发布时，将按存储和计算使用情况计费。 diff --git a/translations/zh-CN/data/reusables/codespaces/about-configuration.md b/translations/zh-CN/data/reusables/codespaces/about-configuration.md deleted file mode 100644 index 2ce7536153..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/about-configuration.md +++ /dev/null @@ -1 +0,0 @@ -您可以为仓库创建默认代码空间配置，以确定任何人员为该仓库创建的每个新代码空间的环境。 配置定义一个可以包含框架、工具、扩展和端口转发的开发容器。 diff --git a/translations/zh-CN/data/reusables/codespaces/about-personalization.md b/translations/zh-CN/data/reusables/codespaces/about-personalization.md deleted file mode 100644 index d761204b51..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/about-personalization.md +++ /dev/null @@ -1 +0,0 @@ -您还可以使用 [dotfiles](https://dotfiles.github.io/tutorials/) 仓库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来针对您创建的任何代码空间而个性化代码空间环境的各个方面。 个性化可以包括 shell 首选项和其他工具。 diff --git a/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md b/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md deleted file mode 100644 index 3befc07c9d..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/about-port-forwarding.md +++ /dev/null @@ -1 +0,0 @@ -您可以转发代码空间中的端口以测试和调试应用程序。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md b/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md deleted file mode 100644 index a60d164f36..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md +++ /dev/null @@ -1 +0,0 @@ -在仓库的 {% data variables.product.prodname_codespaces %} 配置更改后，您可以通过重建代码空间的容器来将更改应用于现有代码空间。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/beta-functionality-limited.md b/translations/zh-CN/data/reusables/codespaces/beta-functionality-limited.md deleted file mode 100644 index 5b16ea0119..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/beta-functionality-limited.md +++ /dev/null @@ -1,5 +0,0 @@ -在测试期间，功能是有限的。 -- {% data reusables.codespaces.use-chrome %} -- 只有一个大小的代码空间可用。 -- 只支持 Linux 容器。 -- 代码空间无法完全恢复。 代码空间停止时正在运行的进程将不会重新启动。 diff --git a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md deleted file mode 100644 index c9ee5e8bfe..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ /dev/null @@ -1 +0,0 @@ -1. 在 {% data variables.product.prodname_vscode %} 中，从左侧边栏单击 Remote Explorer 图标。 ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/codespace-config-order.md b/translations/zh-CN/data/reusables/codespaces/codespace-config-order.md deleted file mode 100644 index bdfac0d210..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/codespace-config-order.md +++ /dev/null @@ -1 +0,0 @@ -`dotfiles` 个性化的应用先于仓库的默认码空间配置。 diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/zh-CN/data/reusables/codespaces/codespaces-are-per-branch.md deleted file mode 100644 index b25e402c60..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/codespaces-are-per-branch.md +++ /dev/null @@ -1 +0,0 @@ -每个代码空间与仓库的一个特定分支关联。 diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-are-personal.md b/translations/zh-CN/data/reusables/codespaces/codespaces-are-personal.md deleted file mode 100644 index 3c061e19f0..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/codespaces-are-personal.md +++ /dev/null @@ -1 +0,0 @@ -您创建的每个代码空间只有您才可以使用。 其他任何人都不能在您的代码空间中工作。 diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md b/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md deleted file mode 100644 index 3790918bb6..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/codespaces-machine-types.md +++ /dev/null @@ -1,11 +0,0 @@ -您可以在三种类型的远程机器上运行代码空间：基本、标准或高级。 每种类型都有不同的资源水平和不同的计费等级。{% note %} - -**注：**{% data reusables.codespaces.about-billing-for-codespaces %} - -{% endnote %} - -切换机器类型使您可以灵活地选择最适合您工作的资源。 某些任务可能需要不同的机器类型： - -* **基本**，适用于更新文件和提出拉取请求 -* **标准**，适用于编辑网站 -* **高级**，适用于数据分析等高计算任务 diff --git a/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md b/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md deleted file mode 100644 index 5cfe774ce3..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md +++ /dev/null @@ -1,3 +0,0 @@ -在对代码空间进行更改（无论是添加新代码还是更改配置）之后，您需要提交更改。 将更改提交到仓库可确保从此仓库创建代码空间的其他任何人都具有相同的配置。 这也意味着您所做的任何自定义，例如添加 {% data variables.product.prodname_vscode %} 扩展，都会显示给所有用户。 - -有关信息，请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)”。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/zh-CN/data/reusables/codespaces/concurrent-codespace-limit.md deleted file mode 100644 index 2cf2c0ee92..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/concurrent-codespace-limit.md +++ /dev/null @@ -1 +0,0 @@ -每个仓库甚至每个分支可创建多个代码空间。 但是，在有限的公测期间，每个用户帐户限于两个代码空间。 如果您已达到上限，想要创建一个新的代码空间，必须先删除一个旧代码空间。 diff --git a/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md deleted file mode 100644 index 795ded63dd..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ /dev/null @@ -1 +0,0 @@ -您可以直接从 {% data variables.product.prodname_vscode %} 连接至您的代码空间。 更多信息请参阅“[在 {% data variables.product.prodname_vscode %} 中使用代码空间](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)”。 diff --git a/translations/zh-CN/data/reusables/codespaces/devcontainer-location.md b/translations/zh-CN/data/reusables/codespaces/devcontainer-location.md deleted file mode 100644 index ee733ada20..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/devcontainer-location.md +++ /dev/null @@ -1 +0,0 @@ -此文件可位于存储库的根目录或名为 `.devtainer` 的文件夹中。 如果文件位于仓库的根目录中，文件名必须以一个点开头：`.devcontainer.json`。 diff --git a/translations/zh-CN/data/reusables/codespaces/navigate-to-codespaces.md b/translations/zh-CN/data/reusables/codespaces/navigate-to-codespaces.md deleted file mode 100644 index a8b97bfd40..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/navigate-to-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. 在任何页面顶部，单击 **Codespaces（代码空间）**。 ![标头中的 {% data variables.product.prodname_codespaces %} 链接](/assets/images/help/codespaces/header-link.png) diff --git a/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md deleted file mode 100644 index f0295e7701..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/navigate-to-ports-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. 在代码空间中的文本编辑器下，单击“Ports（端口）”。 ![端口选项卡](/assets/images/help/codespaces/ports-tab.png) diff --git a/translations/zh-CN/data/reusables/codespaces/rebuild-command.md b/translations/zh-CN/data/reusables/codespaces/rebuild-command.md deleted file mode 100644 index 71e4f05ade..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/rebuild-command.md +++ /dev/null @@ -1 +0,0 @@ -访问命令面板 (`shift command P` / `shift control P`)，然后开始输入 "Codespaces: Rebuild Container"。 单击 **Codespaces: Rebuild Container（代码空间：重建容器）**。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/recovery-mode.md b/translations/zh-CN/data/reusables/codespaces/recovery-mode.md deleted file mode 100644 index f2b5bae88a..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/recovery-mode.md +++ /dev/null @@ -1 +0,0 @@ -如果对代码空间的配置的更改导致容器错误，则代码空间将在恢复模式下运行，并且您将看到错误消息。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/release-stage.md b/translations/zh-CN/data/reusables/codespaces/release-stage.md deleted file mode 100644 index 3220d5951c..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**注：**{% data variables.product.prodname_codespaces %} 目前是有限公测版，可能会有变动。 有关加入公测的更多信息，请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)”。 - -{% endnote %} diff --git a/translations/zh-CN/data/reusables/codespaces/secret-precedence.md b/translations/zh-CN/data/reusables/codespaces/secret-precedence.md deleted file mode 100644 index a6c7d721bb..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/secret-precedence.md +++ /dev/null @@ -1 +0,0 @@ -如果具有相同名称的机密存在于多个级别，则较低级别的机密优先。 例如，如果组织级别密码的名称与仓库级别的密码相同，则仓库级别的密码优先。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/secrets-naming.md b/translations/zh-CN/data/reusables/codespaces/secrets-naming.md deleted file mode 100644 index a1a55d82be..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/secrets-naming.md +++ /dev/null @@ -1,7 +0,0 @@ -以下规则适用于密码名称： - -* 密码名称只能包含字母数字字符（`[a-z]`、`[A-Z]`、`[0-9]`）或下划线 (`_`)。 不允许空格。 -* 密码名称不能以 `GITHUB_` 前缀开头。 -* 密码名称不能以数字开头。 -* 机密名称不区分大小写。 -* 密码名称在所创建的级别上必须是唯一的。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md b/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md deleted file mode 100644 index 6a9dd8e3b7..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/secrets-on-start.md +++ /dev/null @@ -1 +0,0 @@ -一旦创建了密码，便可以在创建新的代码空间或重新启动代码空间时使用它。 要使用刚刚在当前代码空间中创建的密码，您需要暂停代码空间并恢复它。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md b/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md deleted file mode 100644 index d70b9ac93e..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/source-control-display-dark.md +++ /dev/null @@ -1 +0,0 @@ -1. 在活动栏中，单击 **Source Control（源控制）**视图。 ![源控制视图](/assets/images/help/codespaces/source-control-activity-bar-button.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-display.md b/translations/zh-CN/data/reusables/codespaces/source-control-display.md deleted file mode 100644 index e2a8cb8c77..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/source-control-display.md +++ /dev/null @@ -1,3 +0,0 @@ -1. 在活动栏中，单击 **Source Control（源控制）**视图。 - - ![源控制视图](/assets/images/help/codespaces/codespaces-commit-activity.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/type-port-label.md b/translations/zh-CN/data/reusables/codespaces/type-port-label.md deleted file mode 100644 index 150b8007e4..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/type-port-label.md +++ /dev/null @@ -1 +0,0 @@ -1. 键入端口的标签，然后按 enter。 ![输入端口标签的文本框](/assets/images/help/codespaces/label-text-box.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/unsupported-repos.md b/translations/zh-CN/data/reusables/codespaces/unsupported-repos.md deleted file mode 100644 index 498f150830..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/unsupported-repos.md +++ /dev/null @@ -1 +0,0 @@ -在测试阶段，不支持组织拥有的私有仓库或者组织拥有的需要 SAML 单点登录的任何仓库。 diff --git a/translations/zh-CN/data/reusables/codespaces/use-chrome.md b/translations/zh-CN/data/reusables/codespaces/use-chrome.md deleted file mode 100644 index f399152bdc..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/use-chrome.md +++ /dev/null @@ -1 +0,0 @@ -为获取 {% data variables.product.prodname_codespaces %} 最佳使用体验，建议使用基于 Chromium 的浏览器，如 Google Chrome 或 Microsoft Edge。 diff --git a/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md b/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md deleted file mode 100644 index dc30c73437..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md +++ /dev/null @@ -1 +0,0 @@ -使用 {% data variables.product.prodname_vscode %} 在代码空间中开发时，您可以编辑代码、调试和使用 Git 命令。 更多信息请参阅 [{% data variables.product.prodname_vscode %} 文档](https://code.visualstudio.com/docs)。 diff --git a/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md b/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md deleted file mode 100644 index 28c82030d8..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md +++ /dev/null @@ -1 +0,0 @@ -配置 {% data variables.product.prodname_vscode %} 的编辑器设置时，有三个可用的作用域：_工作区_、_远程 [Codespaces]_和_用户_。 如果在多个作用域中定义了设置，_工作区_设置优先级最高，_远程 [Codespaces]_ 次之，最后是_用户_。 diff --git a/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md deleted file mode 100644 index 7ed08ce28a..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/you-can-see-all-your-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -您可以在 [github.com/codespaces](https://github.com/codespaces) 上查看您创建的每一个可用代码空间。 diff --git a/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md deleted file mode 100644 index 1d02c80a2e..0000000000 --- a/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md +++ /dev/null @@ -1,3 +0,0 @@ -1. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your codespaces（您的代码空间）**。 - - ![“您的代码空间”菜单选项](/assets/images/help/codespaces/your-codespaces-option.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/gated-features/codespaces.md b/translations/zh-CN/data/reusables/gated-features/codespaces.md deleted file mode 100644 index ae5565955b..0000000000 --- a/translations/zh-CN/data/reusables/gated-features/codespaces.md +++ /dev/null @@ -1 +0,0 @@ -代码空间可用于使用 {% data variables.product.prodname_free_user %} 或 {% data variables.product.prodname_pro %} 的用户帐户。 {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/zh-CN/data/reusables/organizations/click-codespaces.md b/translations/zh-CN/data/reusables/organizations/click-codespaces.md deleted file mode 100644 index fa9c09b609..0000000000 --- a/translations/zh-CN/data/reusables/organizations/click-codespaces.md +++ /dev/null @@ -1 +0,0 @@ -1. 在左侧边栏中，单击 **Codespaces**。 ![左侧边栏中的"Codespaces"选项卡](/assets/images/help/organizations/codespaces-sidebar-tab.png) diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md deleted file mode 100644 index 0279c32bf5..0000000000 --- a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. 选择“Repository access（仓库访问）”下拉菜单，然后单击要访问该机密的仓库。 对每个您想要访问该机密的仓库重复操作。 !["仓库访问"下拉菜单](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md b/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md deleted file mode 100644 index d9aadc9325..0000000000 --- a/translations/zh-CN/data/reusables/user_settings/codespaces-secret-value.md +++ /dev/null @@ -1 +0,0 @@ -1. 在“Value（值）”下，输入密码的名称。 !["值"文本框](/assets/images/help/settings/codespaces-secret-value-field.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md b/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md deleted file mode 100644 index 0071bc8834..0000000000 --- a/translations/zh-CN/data/reusables/user_settings/codespaces-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. 在左侧边栏中，单击 **Codespaces**。 ![用户设置侧边栏中的 Codespaces 选项卡](/assets/images/help/settings/codespaces-tab.png) \ No newline at end of file