[pull] main from microsoft:main

.eslint-ignore

@@ -3,6 +3,7 @@
 **/extensions/**/*.d.ts
 **/extensions/**/build/**
 **/extensions/**/colorize-fixtures/**
+**/extensions/copilot/**
 **/extensions/css-language-features/server/test/pathCompletionFixtures/**
 **/extensions/html-language-features/server/lib/jquery.d.ts
 **/extensions/html-language-features/server/src/test/pathCompletionFixtures/**

.gitattributes

@@ -9,5 +9,3 @@ ThirdPartyNotices.txt eol=crlf
 *.sh eol=lf
 *.rtf -text
 **/*.json linguist-language=jsonc
-
-test/componentFixtures/.screenshots/**/*.png filter=lfs diff=lfs merge=lfs -text

.github/skills/update-screenshots/SKILL.md

@@ -5,92 +5,23 @@ description: Download screenshot baselines from the latest CI run and commit the
 
 # Update Component Screenshots from CI
 
-When asked to update, accept, or refresh screenshot baselines from CI — or when the `Screenshot Tests` GitHub Action has failed with screenshot differences — follow this procedure to download the CI-generated screenshots and commit them as the new baselines.
+Screenshot baselines are **no longer stored in the repository**. They are managed by an external screenshot service (`hediet-screenshots.azurewebsites.net`). The CI workflow uploads screenshots to this service and diffs them automatically.
 
-## Why CI Screenshots?
+When the `Checking Component Screenshots` GitHub Action detects changes, it posts a PR comment with before/after comparisons. No manual baseline updates are needed — the screenshots on the `main` branch commit become the new baselines automatically after merge.
 
-Screenshots captured locally may differ from CI due to platform differences (fonts, rendering, DPI). The CI (Linux, ubuntu-latest) is the source of truth. This skill downloads the CI-produced screenshots and commits them as baselines.
+## What Changed
 
-## Prerequisites
+- Baseline images were removed from `test/componentFixtures/.screenshots/baseline/`.
+- Git LFS is no longer used for screenshot storage.
+- The screenshot service stores images keyed by commit SHA and handles diffing.
 
-- The `gh` CLI must be authenticated (`gh auth status`).
-- The `Screenshot Tests` GitHub Action must have run and produced a `screenshot-diff` artifact.
+## If Screenshots Need Investigation
 
-## Procedure
-
-### 1. Find the latest screenshot artifact
-
-If the user provides a specific run ID or PR number, use that. Otherwise, find the latest run:
-
-```bash
-# For a specific PR:
-gh run list --workflow screenshot-test.yml --branch <branch> --limit 5 --json databaseId,status,conclusion,headBranch
-
-# For the current branch:
-gh run list --workflow screenshot-test.yml --branch $(git branch --show-current) --limit 5 --json databaseId,status,conclusion
-```
-
-Pick the most recent run that has a `screenshot-diff` artifact (runs where screenshots matched won't have one).
-
-### 2. Download the artifact
+1. Check the PR comment posted by the CI workflow for visual diffs.
+2. Download the `screenshots` artifact from the CI run for the raw captured images:
 
 ```bash
-gh run download <run-id> --name screenshot-diff --dir .tmp/screenshot-diff
+gh run download <run-id> --name screenshots --dir .tmp/screenshots
 ```
 
-The artifact is uploaded from two paths (`test/componentFixtures/.screenshots/current/` and `test/componentFixtures/.screenshots/report/`), but GitHub Actions strips the common prefix. So the downloaded structure is:
-- `current/` — the CI-captured screenshots (e.g. `current/baseUI/Buttons/Dark.png`)
-- `report/report.json` — structured diff report
-- `report/report.md` — human-readable diff report
-
-### 3. Review the changes
-
-Show the user what changed by reading the markdown report:
-
-```bash
-cat .tmp/screenshot-diff/report/report.md
-```
-
-### 4. Copy CI screenshots to baseline
-
-```bash
-# Remove old baselines and replace with CI screenshots
-rm -rf test/componentFixtures/.screenshots/baseline/
-cp -r .tmp/screenshot-diff/current/ test/componentFixtures/.screenshots/baseline/
-```
-
-### 5. Clean up
-
-```bash
-rm -rf .tmp/screenshot-diff
-```
-
-### 6. Stage and commit
-
-```bash
-git add test/componentFixtures/.screenshots/baseline/
-git commit -m "update screenshot baselines from CI"
-```
-
-### 7. Push LFS objects before pushing
-
-Screenshot baselines are stored in Git LFS. The `git lfs pre-push` hook is not active in this repo (husky overwrites it), so LFS objects are NOT automatically uploaded on `git push`. You must push them manually before pushing the branch, otherwise the push will fail with `GH008: Your push referenced unknown Git LFS objects`.
-
-```bash
-git lfs push --all origin <branch-name>
-git push
-```
-
-### 8. Verify
-
-Confirm the baselines are updated by listing the files:
-
-```bash
-git diff --stat HEAD~1
-```
-
-## Notes
-
-- If no `screenshot-diff` artifact exists, the screenshots already match the baselines — no update needed.
-- The `--filter` option on the CLI can be used to selectively accept only some fixtures if needed.
-- After committing updated baselines, the next CI run should pass the screenshot comparison.
+3. Compare locally if needed. The artifact contains the full set of captured screenshots.

.github/workflows/monaco-editor.yml

@@ -21,6 +21,7 @@ jobs:
     steps:
       - uses: actions/checkout@v6
         with:
+          lfs: true
           persist-credentials: false
 
       - uses: actions/setup-node@v6

.github/workflows/pr-darwin-test.yml

@@ -25,6 +25,8 @@ jobs:
     steps:
       - name: Checkout microsoft/vscode
         uses: actions/checkout@v6
+        with:
+          lfs: true
 
       - name: Setup Node.js
         uses: actions/setup-node@v6

.github/workflows/pr-linux-cli-test.yml

@@ -17,6 +17,8 @@ jobs:
     steps:
       - name: Checkout microsoft/vscode
         uses: actions/checkout@v6
+        with:
+          lfs: true
 
       - name: Install Rust
         run: |

.github/workflows/pr-linux-test.yml

@@ -25,6 +25,8 @@ jobs:
     steps:
       - name: Checkout microsoft/vscode
         uses: actions/checkout@v6
+        with:
+          lfs: true
 
       - name: Setup Node.js
         uses: actions/setup-node@v6

.github/workflows/pr-win32-test.yml

@@ -25,6 +25,8 @@ jobs:
     steps:
       - name: Checkout microsoft/vscode
         uses: actions/checkout@v6
+        with:
+          lfs: true
 
       - name: Setup Node.js
         uses: actions/setup-node@v6