Update screenshots for Remote extension rename
This commit is contained in:
gregvanl
Родитель
864961e09d
Коммит
65469e5468
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fcacf3fe92c8ac4c7c115002b9a4290ecceda61708e61a020c67eee75c7216d1
|
||||
size 11279
|
||||
oid sha256:07a96319132d1447b86de2420ecfe3b03bd801ad53fb23e6b85a10a86a0a210a
|
||||
size 17087
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0c20b6f84b48b97b11e7bca53d563c257aff620f320c143480f0ee2ade5958aa
|
||||
size 99815
|
||||
oid sha256:7f5beb2ff1267000eb0b6d0241de51032d6dfc2ae30363b495c1206e7848c0a8
|
||||
size 141437
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1d41373104ccc3f491fcfae0398dcd09c7885dc8823a3afaad5c77706cbb1eee
|
||||
size 37873
|
||||
oid sha256:abd55f21f291152fd9e58bf9a0eb6811913ee05be09d9c8359d843aedc053221
|
||||
size 21198
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:31d848a8fbccbeb6c7c93cca812cebdead66a2422bab4fd1111ef55f31f6a46d
|
||||
size 6954
|
||||
oid sha256:1865e71c75bd35536741bdc31abe30114335e65b8051ccbfdfedf88683c08ef0
|
||||
size 18720
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9ae3c753c890243897fa2e406a9b9b9ffe213d42d29a7a37dd5c9429c6ba78a2
|
||||
size 22491
|
||||
oid sha256:c6b6d36f2cea125d4c39e6c36c03a85774a360cb3b7d213d5c0cf7a487bae9cb
|
||||
size 64874
|
||||
|
|
|
|||
|
|
@ -355,10 +355,10 @@ While you can edit your [devcontainer.json](/docs/remote/create-dev-container.md
|
|||
|
||||
### "Always installed" extensions
|
||||
|
||||
If there are extensions that you would like always installed in any container, you can update the `remote.containers.defaultExtensions` User [setting](/docs/getstarted/settings.md). For example, if you wanted to install the [GitLens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) and [Resource Monitor](https://marketplace.visualstudio.com/items?itemName=mutantdino.resourcemonitor) extensions, you would specify their extension IDs as follows:
|
||||
If there are extensions that you would like always installed in any container, you can update the `dev.containers.defaultExtensions` User [setting](/docs/getstarted/settings.md). For example, if you wanted to install the [GitLens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) and [Resource Monitor](https://marketplace.visualstudio.com/items?itemName=mutantdino.resourcemonitor) extensions, you would specify their extension IDs as follows:
|
||||
|
||||
```json
|
||||
"remote.containers.defaultExtensions": [
|
||||
"dev.containers.defaultExtensions": [
|
||||
"eamodio.gitlens",
|
||||
"mutantdino.resourcemonitor"
|
||||
]
|
||||
|
|
|
|||
|
|
@ -468,9 +468,9 @@ In some cases, you may want to create a configuration for a repository that you
|
|||
|
||||
First, update the **Dev > Containers: Repository Configuration Paths** [User setting](/docs/getstarted/settings.md) with the local folder you want to use to store your repository container configuration files.
|
||||
|
||||
In the Settings editor:
|
||||
In the Settings editor, you can search for 'dev containers repo' to find the setting:
|
||||
|
||||
 <!-- TBD update screenshot -->
|
||||
|
||||
|
||||
Next, place your `.devcontainer/devcontainer.json` (and related files) in a sub folder that mirrors the remote location of the repository. For example, if you wanted to create a configuration for `github.com/microsoft/vscode-dev-containers`, you would create the following folder structure:
|
||||
|
||||
|
|
|
|||
|
|
@ -119,7 +119,7 @@ Yes. The [Remote Development extension pack](https://aka.ms/vscode-remote/downlo
|
|||
|
||||
As with [other parts of Visual Studio Code](/docs/getstarted/settings.md), you can customize each of the Remote Development extensions through their settings. Using Dev Containers as an example, you may review a list of all Dev Containers settings by opening the extension in the Extensions view (`kb(workbench.view.extensions)`), and navigating to **Feature Contributions**:
|
||||
|
||||
 <!-- TBD update screenshot -->
|
||||
|
||||
|
||||
## WSL
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:988540f7409a0051a4ace4ba787c6a23d84c8fc938608acf17820164e9e4d291
|
||||
size 89935
|
||||
oid sha256:d551df59b0b536c010dba36374d94c43510a4fab422c5618c87f9fe24f415bc3
|
||||
size 128749
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d2eb76d33186300809b18b6adc9b454c8380a7e2bd2ad7b68929818dda4a67a7
|
||||
size 316808
|
||||
oid sha256:3e8c706efc1dcc4a87cc355132c76aeebea0c2b33cab140d80039e29b0727344
|
||||
size 254022
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:481ced729ae9e574640035f783238f299d8131b0d1264f4b661027c3f5e2ef3d
|
||||
size 4110
|
||||
oid sha256:51f497f468e39d01c0b4c43770c9a975355a0087467a837668b813bb890e0334
|
||||
size 18999
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e4766c81c8f87d313264ae420866b36f3a5e9e64243ace97f6f988c544a590fa
|
||||
size 48604
|
||||
oid sha256:a9b9965e86258c0930cd9efcea5c3c6ac6eb55275406f9284d6e52068a58c572
|
||||
size 138670
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0e1bcabf61129378105f1af6cd39fcf016ccbea95b70cb97775b0af3ab99cb0e
|
||||
size 15150
|
||||
oid sha256:30f5d98afad6f997927bb2c739b1bf57e69ab3eeb3bff145f4d298d4f1caab9e
|
||||
size 44835
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ad2c522abaae88bee233d12e15d25a01e2e989d607ce066ae80480afed723b58
|
||||
size 14777
|
||||
oid sha256:e551e9b4e9986aed80682953a6c3c1696f38867337505f5b2ea0a2c3c261b43a
|
||||
size 43350
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:dd54ff9c8c0c96c57f68ec6b8c0ef0e8228b7bbd64ab807aa3419678730fd095
|
||||
size 6625
|
||||
oid sha256:04e21693f473d583121d792bda2c797084d587f03c58f481f72f498ff6cb7e3a
|
||||
size 30900
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fcf2a56a9a4125ade7d0a8fa54596538e3d57e1999dddd4f338b311a26ef3479
|
||||
size 24972
|
||||
oid sha256:a20050ce71c22a79fb65ad4ff6a0bf7b3bef6d53f45829ef9ebe5f5f4b9a0c0d
|
||||
size 68887
|
||||
|
|
|
|||
|
|
@ -636,7 +636,7 @@ If this doesn't solve your problem, you may want to see if CPU usage is actually
|
|||
If you'd like this extension to always be installed, add this to your `settings.json`:
|
||||
|
||||
```json
|
||||
"remote.containers.defaultExtensions": [
|
||||
"dev.containers.defaultExtensions": [
|
||||
"mutantdino.resourcemonitor"
|
||||
]
|
||||
```
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ With the WSL extension installed, you will see a new Status bar item at the far
|
|||
|
||||
The Remote Status bar item can quickly show you in which context VS Code is running (local or remote) and clicking on the item will bring up the WSL extension commands.
|
||||
|
||||
 <!-- TBD update screenshot -->
|
||||
|
||||
|
||||
## Enable WSL
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ In the diagram below, you'll see an example of three dev containers: one for Pyt
|
|||
|
||||
To get started with using dev containers in VS Code, you'll need to download the [Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension from the VS Code Marketplace.
|
||||
|
||||
 <!-- TBD update screenshot -->
|
||||
|
||||
|
||||
You'll also need to download [Docker](https://docs.docker.com/docker-for-windows/install-windows-home/), which is the industry standard for building and sharing containers.
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b523dca0959d1a03c29ed6b5197e39a311a5fd8cf01926dff3196bf21d32f341
|
||||
size 56961
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c995cf71b48569cb6b9d8b341fdda2bbbe05a96c89372d70335b6464099dd3f7
|
||||
size 124247
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8d322790b361925edcc5e5b04f3311361c943884a0432689bab61837f098dc39
|
||||
size 122003
|
||||
oid sha256:c76ec3202be6c347a21f99c140f8e0ff30b2e58d728eb21256e4a146ba276d03
|
||||
size 69214
|
||||
|
|
|
|||
|
|
@ -1,3 +0,0 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:90195cd0bdbb622255c958036a31f7306d8fd85bc0d5849eca2d9d240207a800
|
||||
size 136804
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:14903816bdd7975e0cd1f573c12dd7b2afad2bc3871936015c72822137c6350d
|
||||
size 60220
|
||||
|
|
@ -19,7 +19,7 @@ WSL especially helps web developers and those working with Bash and Linux-first
|
|||
|
||||
To get started with using WSL in VS Code, you'll need to download the [WSL extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl) from the Extension Marketplace.
|
||||
|
||||
 <!-- TBD new screenshot -->
|
||||
|
||||
|
||||
You'll also need WSL and a Linux distribution installed. We recommend using WSL 2, which is the newest version of WSL, as you will benefit from significant [performance advantages](https://learn.microsoft.com/windows/wsl/compare-versions) over WSL 1.
|
||||
|
||||
|
|
|
|||
|
|
@ -245,7 +245,7 @@ Work has continued on the [Remote Development extensions](https://marketplace.vi
|
|||
Feature highlights in 1.39 include:
|
||||
|
||||
* Remote Explorer now supports the WSL extension and lets you easily connect to installed Linux distros.
|
||||
* New **Open Repository in Container** command so you can work on source code repositories in isolation.
|
||||
* New **Clone Repository in Container Volume** command so you can work on source code repositories in isolation.
|
||||
* Experimental support for SSH connection sharing and using SSH to connect to Windows remote machines.
|
||||
|
||||
You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_39.md).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e8fb1c786cbeed3cab09c195a92a967ba22cc7830c2f06b4540263983f94f2fe
|
||||
size 65097
|
||||
oid sha256:34c10a1325d4c9f992dea4b8a535d4bff8410a62988cd4fb9cb9add19a53bbd5
|
||||
size 34111
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c42d724519c491be4018cc2978bdf1a27440ca5c3ae4fa4676bbfff41c61d1eb
|
||||
size 131708
|
||||
oid sha256:4ba003a95f0512e760380cfe9b49193f10245416ba9764480afb821e1f991ae6
|
||||
size 108178
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0c174b9228b06f2194ff7e74e5a5cdd679ebaa06343a6594d4c698874b8d8b82
|
||||
size 48535
|
||||
oid sha256:93f4b7cc0e8b008700bedd95d3f0ca25faf7fa0fd67356a9fc6544c434d99a4a
|
||||
size 27554
|
||||
|
|
|
|||
|
|
@ -58,13 +58,13 @@ The **Dev Containers: Open Container Configuration File** command will open the
|
|||
}
|
||||
```
|
||||
|
||||
### Open repository in a container
|
||||
### Clone repository in container volume
|
||||
|
||||
There is a new command **Dev Containers: Open Repository in Container...** to allow you to work on a repository in a container without locally cloning it first. This lets you work with an isolated copy of a repository, useful for a PR review or to investigate another branch, without impacting what you have currently checked out. The command requires that the repository has a `devcontainer.json` file and, in the current version, the repository must be be public.
|
||||
There is a new command **Dev Containers: Clone Repository in Container Volume...** to allow you to work on a repository in a container without locally cloning it first. This lets you work with an isolated copy of a repository, useful for a PR review or to investigate another branch, without impacting what you have currently checked out. The command requires that the repository has a `devcontainer.json` file and, in the current version, the repository must be be public.
|
||||
|
||||
Repository Containers use isolated, local Docker volumes instead binding to the local filesystem. In addition to not polluting your file tree, local volumes have the added benefit of improved performance on Windows and macOS.
|
||||
|
||||
To try out the feature, you can run **Dev Containers: Open Repository in Container...** and enter `microsoft/vscode-remote-try-node`, for example.
|
||||
To try out the feature, you can run **Dev Containers: Clone Repository in Container Volume...** and enter `microsoft/vscode-remote-try-node`, for example.
|
||||
|
||||
The **Container** section of the Remote Explorer shows the details of a Repository Container, such as the source repository and the local Docker volume. Removing a Repository Container from the explorer will prompt you whether you want to delete the volume.
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ See [issue #1823](https://github.com/microsoft/vscode-remote-release/issues/1823
|
|||
|
||||
### More flexible opening of a repository into a container
|
||||
|
||||
The command [Dev Containers: Open Repository in Container...](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-public-git-repository-in-an-isolated-container-volume) is now more flexible and supports picking the Docker volume the repository should clone into. This enables you to open the same repository into different volumes, for example to investigate different branches of the repository.
|
||||
The command [Dev Containers: Clone Repository in Container Volume...](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-public-git-repository-in-an-isolated-container-volume) is now more flexible and supports picking the Docker volume the repository should clone into. This enables you to open the same repository into different volumes, for example to investigate different branches of the repository.
|
||||
|
||||
You can now also clone multiple repositories into the same volume so that you do not have to manage multiple volumes.
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ The `devcontainer.json` file has a new `forwardPorts` property that lists the co
|
|||
|
||||
### Open private repositories in containers
|
||||
|
||||
The command **Dev Containers: Open Repository in Container** now supports private repositories. One remaining limitation is that the credentials need to be available in the local Git credentials manager when using HTTPS and the key needs to be available in the ssh-agent when using SSH to connect to the Git server.
|
||||
The command **Dev Containers: Clone Repository in Container Volume** now supports private repositories. One remaining limitation is that the credentials need to be available in the local Git credentials manager when using HTTPS and the key needs to be available in the ssh-agent when using SSH to connect to the Git server.
|
||||
|
||||
### Simplified adding extensions to the devcontainer.json
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Here is an example:
|
|||
|
||||
### Dotfiles repository settings
|
||||
|
||||
In the last iteration, we added support for [dotfiles repositories](https://github.com/microsoft/vscode-docs/blob/vnext/remote-release-notes/v1_42.md#dotfiles-repository-support) and corresponding settings `remote.containers.dotfiles.*`. Dotfiles are a generally useful mechanism, and are not only used by VS Code Dev Containers. With that in mind, there are now general settings named `dotfiles.*`, which will eventually allow you to define `dotfiles` preferences with a single setting.
|
||||
In the last iteration, we added support for [dotfiles repositories](https://github.com/microsoft/vscode-docs/blob/vnext/remote-release-notes/v1_42.md#dotfiles-repository-support). Dotfiles are a generally useful mechanism, and are not only used by VS Code Dev Containers. With that in mind, there are now general settings named `dotfiles.*`, which will eventually allow you to define `dotfiles` preferences with a single setting.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
[Repository Containers](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-in-an-isolated-container-volume) have been supported for several releases.
|
||||
These containers use isolated, local [Docker volumes](https://docs.docker.com/storage/volumes/) instead binding to the local filesystem. In addition to not polluting your file tree, local volumes have the added benefit of improved performance on Windows and macOS. In this release, we have added support to checkout a Pull Request directly into a repository container. You can checkout a Pull Request into a container using:
|
||||
|
||||
* The **Dev Containers: Open Repository in Container** command and entering the corresponding Pull Request, for example `https://github.com/microsoft/vscode-npm-scripts/pull/111`. <!-- TBD correct command name? -->
|
||||
* The **Dev Containers: Clone Repository in Container Volume** command and entering the corresponding Pull Request, for example `https://github.com/microsoft/vscode-npm-scripts/pull/111`.
|
||||
* The [GitHub Pull Request Extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github), where you can select the PR and use the command **Checkout Pull Request in Dev Container**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ You can now inspect the contents of a Docker volume using Visual Studio Code. Th
|
|||
|
||||
### Improved iterative development of a devcontainer's Dockerfile for Repository Containers
|
||||
|
||||
When **Dev Containers: Open Repository in Container...** fails to start the [Repository Container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume), for example, due to an error when building the Docker image, you can now open the cloned repository in a recovery container. The error dialog shown now provides an action **Reopen in Recovery Container**. This action opens the cloned repository in a minimal container that comes with Git and Docker so that you can correct the error. Once you have fixed the error you can reopen the container with **Dev Containers: Reopen in Container**.
|
||||
When **Dev Containers: Clone Repository in Container Volume...** fails to start the [Repository Container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume), for example, due to an error when building the Docker image, you can now open the cloned repository in a recovery container. The error dialog shown now provides an action **Reopen in Recovery Container**. This action opens the cloned repository in a minimal container that comes with Git and Docker so that you can correct the error. Once you have fixed the error you can reopen the container with **Dev Containers: Reopen in Container**.
|
||||
|
||||
### GPG forwarding
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ If you are connecting to a multi-user remote, you may not want the VS Code Remot
|
|||
|
||||
### Guidance to open a repository in a volume
|
||||
|
||||
When opening a Git repository folder, the **Reopen in Container** notification now offers to clone and reopen the repository in a Docker volume. Using a Docker volume has better disk performance because it uses a Linux filesystem without any extra layer between the Linux Kernel and the filesystem. (We do not show this guidance on Linux, but the feature is still available using the **Dev Containers: Open Repository in Container** command.)
|
||||
When opening a Git repository folder, the **Reopen in Container** notification now offers to clone and reopen the repository in a Docker volume. Using a Docker volume has better disk performance because it uses a Linux filesystem without any extra layer between the Linux Kernel and the filesystem. (We do not show this guidance on Linux, but the feature is still available using the **Dev Containers: Clone Repository in Container Volume** command.)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -34,8 +34,8 @@ There is also support for IntelliSense to edit the new `"features"` property in
|
|||
|
||||
### Execute in WSL setting
|
||||
|
||||
On Windows, to support having Docker CE or Podman installed in Windows Subsystem for Linux (WSL), the new **Execute in WSL** (`remote.containers.executeInWSL`) user setting lets the Dev Containers extension run all CLI commands in WSL.
|
||||
On Windows, to support having Docker CE or Podman installed in Windows Subsystem for Linux (WSL), the new **Execute in WSL** (`dev.containers.executeInWSL`) user setting lets the Dev Containers extension run all CLI commands in WSL.
|
||||
|
||||
 <!-- TBD update screenshot -->
|
||||
|
||||
|
||||
When not enabled, CLI commands are still run in WSL for workspace folders on a WSL filesystem.
|
||||
|
|
|
|||
|
|
@ -28,10 +28,9 @@ Let's set up a container for use with all of the Python projects in the `./Repos
|
|||
|
||||
1. Start Visual Studio Code, select **Dev Containers: Open Folder in Container...** from the Command Palette (`kbstyle(F1)`) or quick actions Status bar item, and select the `./Repos/python` folder.
|
||||
|
||||
> **Tip:** If you want to edit the container's contents or settings before opening the folder, you can run **Dev Containers: Add Dev Container Configuration Files...** instead.
|
||||
|
||||
|
||||
<!-- TBD old image -->
|
||||
|
||||
> **Tip:** If you want to edit the container's contents or settings before opening the folder, you can run **Dev Containers: Add Dev Container Configuration Files...** instead.
|
||||
|
||||
2. Now pick a starting point for your dev container. You can either select a base **dev container definition** from a filterable list, or use an existing [Dockerfile](https://docs.docker.com/engine/reference/builder/) or [Docker Compose file](https://docs.docker.com/compose/compose-file/#compose-file-structure-and-examples) if one exists in the folder you selected.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1b7b249b648de416baa6094150bb39efd624811973ef45b516a145d0c65d8f47
|
||||
size 12658
|
||||
oid sha256:0e81bd7f4d6af2398da3134b48dcf939a649830ab6ca9f132f6641a522636f7c
|
||||
size 12130
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0be5e2cf1056ea7064f173b2589649541eee3db831be882057f5a313144afe22
|
||||
size 109447
|
||||
oid sha256:23d958d2080b3919bce182946d5320bcb35d939ddc66fab497f163eeecc9134b
|
||||
size 91345
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче