You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://insiders.vscode.dev now supports reading files tracked with Git LFS in repositories hosted on GitHub and Azure Repos. Please verify the following:
You can view Git LFS files in https://insiders.vscode.dev as well as in VS Code desktop with the pre-releases of both GitHub Repositories and Azure Repos.
For Azure Repos, you can create your own Azure DevOps organization, create a test repository, and initialize it from the desktop git client with a few LFS-tracked files (see instructions for initializing LFS for files in your repo).
You can open individual files (png, jpg, mp4, gif) as well as view them inline in the Markdown preview, e.g. by opening the Markdown document for our release notes and choosing Markdown: Open Preview from the command palette.
When testing web support, please try opening the repo in at least two different browsers (Edge, Chrome, Safari, Firefox).
Setting "githubRepositories.experimental.lfs.read.enabled": false and "azureRepos.experimental.lfs.read.enabled": false disables LFS read support (the behavior in the stable releases today).
Note any performance issues that are perceptible to you as a result of the LFS read support.
⚠️ we do not yet support committing LFS files, nor do we support reading LFS files in github.dev due to outstanding CORS issues.
The text was updated successfully, but these errors were encountered:
Refs microsoft/vscode-remote-repositories-github#7
Complexity: 4
Create Issue
https://insiders.vscode.dev now supports reading files tracked with Git LFS in repositories hosted on GitHub and Azure Repos. Please verify the following:
Markdown: Open Preview
from the command palette."githubRepositories.experimental.lfs.read.enabled": false
and"azureRepos.experimental.lfs.read.enabled": false
disables LFS read support (the behavior in the stable releases today).The text was updated successfully, but these errors were encountered: