Merge pull request #66 from microsoft/sync-public-docs

Merge public docs into private repo

Author: ntrogh

.github/instructions/docs-writing.instructions.md

@@ -1,5 +1,5 @@
 ---
-applyTo: '**/*.md'
+applyTo: 'docs/**/*.md, api/**/*.md, remote/**/*.md'
 ---
 # Documentation Writing Instructions
 
@@ -108,3 +108,4 @@ These are our documentation writing style guidelines.
 * Avoid latin abbreviations like "e.g.". Use "for example" instead.
 * Use the verb "to enable" instead "to allow" unless you're referring to permissions.
 * Follow the terms and capitalization guidelines in #fetch [VS Code docs wiki](https://github.com/microsoft/vscode-docs/wiki/VS-Code-glossary)
+* Don't use the following terms: "simply", "just", "easy", "obviously", "of course", "etc.", "delve", "crucial", "utilize", "leverage", "prior to", "in order to", "harness".

.github/prompts/askvscode.prompt.md

@@ -1,7 +1,8 @@
 ---
+description: Ask questions about VS Code
 mode: agent
 model: Claude Sonnet 4
-tools: ['codebase', 'usages', 'vscodeAPI', 'githubRepo', 'search']
+tools: ['usages', 'vscodeAPI', 'githubRepo', 'search']
 ---
 You are an expert in answering questions about Visual Studio Code, its features, and how to use it effectively. Explain how specific features work, give examples of usage scenarios.
 

.github/prompts/review-release-notes.prompt.md

@@ -1,9 +1,22 @@
 ---
 mode: agent
 tools: ['search', 'vscodeAPI', 'problems', 'fetch', 'githubRepo', 'todos']
-description: You are a technical writer reviewing a VS Code release notes for clarity, conciseness, and adherence to the writing style guidelines.
+description: Review release notes
 ---
-Review the article for clarity, conciseness, and adherence to our [release notes writing style guidelines](../instructions/release-notes-writing.instructions.md).
+You are a technical writer specialized in VS Code and release note reviews. Perform a review of the provided release notes, focusing on clarity, conciseness, and adherence to [release notes writing style guidelines](../instructions/release-notes-writing.instructions.md).
 
-Provide a concise summary of the key changes and improvements highlighted in the release notes.
-Provide concrete and practical suggestions for improvement.
+Focus on the following elements:
+
+* Titles are descriptive, concise, and avoid unnecessary jargon.
+* Feature updates describe the change, its benefit, and any relevant context.
+* Feature updates are grouped under appropriate headings (e.g., "Chat", "Editor Experience", "Terminal").
+* If settings are mentioned in a section, start the section with "**Setting**: `setting(setting.name)`".
+* Feature updates follow the general [docs writing guidelines](../instructions/docs-writing.instructions.md).
+* Skip the Notable Fixes and Thank You sections.
+
+Outcome:
+
+* Markdown list of suggested improvements
+* Provide specific line numbers for each suggestion
+* Provide the current text and the suggested revision
+* Suggestions should be specific and actionable.

.vscode/extensions/doc-assistant/dist/extension.js

@@ -5067,6 +5067,9 @@ async function getReleaseFeatures(milestoneName) {
         });
         for (const edge of result.search.edges) {
             const issue = toIssue(edge);
+            if (!issue) {
+                continue;
+            }
             if (issue.labels.includes('*duplicate')) {
                 continue;
             }
@@ -5095,8 +5098,12 @@ async function getReleaseFeaturesWithTestPlanItems(milestoneName, onTestPlan, gq
         after: null
     });
     for (const edge of result.search.edges) {
+        const issue = toIssue(edge);
+        if (!issue) {
+            continue;
+        }
         const releaseFeature = {
-            ...toIssue(edge),
+            ...issue,
             related: []
         };
         releaseFeature.related.push(...await getIssuesFiledAgainst(edge.node.number, gqlClient));
@@ -5115,14 +5122,28 @@ async function getIssuesFiledAgainst(testPlanItem, gqlClient) {
             repositoryQuery: `repo:microsoft/vscode is:closed Testing ${testPlanItem}`,
             after: null
         });
-        return result.search.edges.map(edge => toIssue(edge));
+        const issues = [];
+        for (const edge of result.search.edges) {
+            const issue = toIssue(edge);
+            if (!issue) {
+                continue;
+            }
+            issues.push(issue);
+        }
+        return issues;
     }
     catch (error) {
         console.error('Error fetching issues:', error);
         throw error;
     }
 }
 function toIssue(edge) {
+    if (!edge.node) {
+        return undefined;
+    }
+    if (!edge.node.number) {
+        return undefined;
+    }
     return {
         number: edge.node.number,
         summary: edge.node.title,

.vscode/extensions/doc-assistant/dist/extension.js.map

@@ -90,11 +90,14 @@ export async function getReleaseFeatures(milestoneName: string): Promise<Release
 
 		for (const edge of result.search.edges) {
 			const issue = toIssue(edge);
+			if (!issue) {
+				continue;
+			}
 			if (issue.labels.includes('*duplicate')) {
-				continue
+				continue;
 			}
 			if (issue.labels.includes('*out-of-scope')) {
-				continue
+				continue;
 			}
 			if (issue.labels.includes('on-testplan')) {
 				onTestPlan.push(issue);
@@ -123,8 +126,12 @@ async function getReleaseFeaturesWithTestPlanItems(milestoneName: string, onTest
 	});
 
 	for (const edge of result.search.edges) {
+		const issue = toIssue(edge);
+		if (!issue) {
+			continue;
+		}
 		const releaseFeature: ReleaseFeature = {
-			...toIssue(edge),
+			...issue,
 			related: []
 		};
 		releaseFeature.related.push(...await getIssuesFiledAgainst(edge.node.number, gqlClient));
@@ -146,15 +153,29 @@ async function getIssuesFiledAgainst(testPlanItem: string, gqlClient: GraphqlCli
 			after: null
 		});
 
-		return result.search.edges.map(edge => toIssue(edge));
+		const issues: Issue[] = [];
+		for (const edge of result.search.edges) {
+			const issue = toIssue(edge);
+			if (!issue) {
+				continue;
+			}
+			issues.push(issue);
+		}
+		return issues;
 
 	} catch (error) {
 		console.error('Error fetching issues:', error);
 		throw error;
 	}
 }
 
-function toIssue(edge: any): Issue {
+function toIssue(edge: any): Issue | undefined {
+	if (!edge.node) {
+		return undefined;
+	}
+	if (!edge.node.number) {
+		return undefined;
+	}
 	return {
 		number: edge.node.number,
 		summary: edge.node.title,

.vscode/extensions/doc-assistant/src/tools/queries.ts

@@ -1,7 +1,7 @@
 ---
 # DO NOT TOUCH — Managed by doc writer
 ContentId: 106AA11C-DB26-493A-9E3C-16F513B2AEC8
-DateApproved: 09/11/2025
+DateApproved: 10/09/2025
 
 # Summarize the whole topic in less than 300 characters for SEO purpose
 MetaDescription: The Visual Studio Code Extension Host is responsible for managing extensions and ensuring the stability and performance of Visual Studio Code.

api/advanced-topics/extension-host.md

@@ -1,6 +1,6 @@
 ---
 ContentId: 5c708951-e566-42db-9d97-e9715d95cdd1
-DateApproved: 09/11/2025
+DateApproved: 10/09/2025
 
 # Summarize the whole topic in less than 300 characters for SEO purpose
 MetaDescription: A guide to adding Visual Studio Code Remote Development and GitHub Codespaces support to extensions

api/advanced-topics/remote-extensions.md

@@ -1,6 +1,6 @@
 ---
 ContentId: f00c4913-58e3-4a61-aa42-e769c3430906
-DateApproved: 09/11/2025
+DateApproved: 10/09/2025
 
 # Summarize the whole topic in less than 300 characters for SEO purpose
 MetaDescription: A guide to migrating extension projects from the TSLint linter to ESLint.

api/advanced-topics/tslint-eslint-migration.md

@@ -1,7 +1,7 @@
 ---
 # DO NOT TOUCH — Managed by doc writer
 ContentId: f4d4e9e0-8901-405c-aaf5-faa16c32588b
-DateApproved: 09/11/2025
+DateApproved: 10/09/2025
 
 # Summarize the whole topic in less than 300 characters for SEO purpose
 MetaDescription: Use Visual Studio Code's Proposed API