Skip to content

Commit a160616

Browse files
HumbleBee14HumbleBee14
committed
Merge branch 'develop'
2 parents 4718b8d + 9727a2f commit a160616

3,276 files changed

Lines changed: 743621 additions & 67619 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.editorconfig‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,3 +13,6 @@ trim_trailing_whitespace = true
1313
[{*.yml,*.yaml,package.json}]
1414
indent_style = space
1515
indent_size = 2
16+
17+
# End of line
18+
end_of_line = lf

‎.eslint-ignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@
1212
**/extensions/markdown-math/notebook-out/**
1313
**/extensions/mermaid-chat-features/chat-webview-out/**
1414
**/extensions/notebook-renderers/renderer-out/index.js
15+
**/extensions/roopik-roo/**
1516
**/extensions/simple-browser/media/index.js
1617
**/extensions/terminal-suggest/src/completions/upstream/**
1718
**/extensions/terminal-suggest/src/shell/zshBuiltinsCache.ts

‎.eslint-plugin-local/code-no-redundant-has-before-delete.ts‎

Lines changed: 0 additions & 140 deletions
This file was deleted.

‎.eslint-plugin-local/tests/code-no-redundant-has-before-delete-test.ts‎

Lines changed: 0 additions & 38 deletions
This file was deleted.

‎.gitattributes‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,10 @@ ThirdPartyNotices.txt eol=crlf
99
*.sh eol=lf
1010
*.rtf -text
1111
**/*.json linguist-language=jsonc
12+
13+
# Standardize all text files to LF in the repo history
14+
* text=auto eol=lf
15+
16+
# Force specific Windows files to stay CRLF if required (e.g., Visual Studio solutions)
17+
*.sln text eol=crlf
18+
*.bat text eol=crlf

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
11+
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
12+
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
13+
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
14+
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
15+
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
16+
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
17+
Does this issue occur when all extensions are disabled?: Yes/No
18+
19+
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
20+
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
21+
- VS Code Version:
22+
- OS Version:
23+
24+
Steps to Reproduce:
25+
26+
1.
27+
2.

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Question
4+
url: https://stackoverflow.com/questions/tagged/visual-studio-code
5+
about: Please ask and answer questions here.
6+
- name: Extension Development
7+
url: https://github.com/microsoft/vscode-discussions/discussions
8+
about: Please use this for extension development questions and ideas.

‎.github/ISSUE_TEMPLATE/copilot_bug_report.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Copilot Bug report
3+
about: Create a report to help us improve Copilot's chat interface in VS Code
4+
title: ''
5+
labels: chat-ext-issue
6+
assignees: ''
7+
8+
---
9+
10+
<!-- Please search existing issues to avoid creating duplicates -->
11+
<!-- Please attach logs to help us diagnose your issue -->
12+
13+
- Copilot Chat Extension Version:
14+
- VS Code Version:
15+
- OS Version:
16+
- Feature (e.g. agent/edit/ask mode):
17+
- Selected model (e.g. GPT 4.1, Claude 3.7 Sonnet):
18+
- Logs:
19+
20+
Steps to Reproduce:
21+
22+
1.
23+
2.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
11+
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
12+
<!-- Please search existing issues to avoid creating duplicates. -->
13+
14+
<!-- Describe the feature you'd like. -->

‎.github/agents/data.md‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: Data
3+
description: Answer telemetry questions with data queries using Kusto Query Language (KQL)
4+
tools:
5+
['vscode/extensions', 'execute/runInTerminal', 'read/readFile', 'search', 'web/githubRepo', 'azure-mcp/kusto_query', 'todo']
6+
---
7+
8+
# Role and Objective
9+
10+
You are a Azure Data Explorer data analyst with expert knowledge in Kusto Query Language (KQL) and data analysis. Your goal is to answer questions about VS Code telemetry events by running kusto queries (NOT just by looking at telemetry types).
11+
12+
# Workflow
13+
14+
1. Read `vscode-telemetry-docs/.github/copilot-instructions.md` to understand how to access VS Code's telemetry
15+
- If the `vscode-telemetry-docs` folder doesn't exist (just check your workspace_info, no extra tool call needed), run `npm run mixin-telemetry-docs` to clone the telemetry documentation.
16+
2. Analyze data using kusto queries: Don't just describe what could be queried - actually execute Kusto queries to provide real data and insights:
17+
- If the `kusto_query` tool doesn't exist (just check your provided tools, no need to run it!), install the `ms-azuretools.vscode-azure-mcp-server` VS Code extension
18+
- Use the appropriate Kusto cluster and database for the data type
19+
- Always include proper time filtering to limit data volume
20+
- Default to a rolling 28-day window if no specific timeframe is requested
21+
- Format and present the query results clearly to answer the user's question
22+
- Track progress of your kusto analysis using todos
23+
- If kusto queries keep failing (up to 3 repeated attempts of fixing parameters or queries), stop and inform the user.
24+
25+
# Kusto Best Practices
26+
27+
When writing Kusto queries, follow these best practices:
28+
- **Explore data efficiently.** Use 1d (1-day) time window and `sample` operator to quickly understand data shape and volume
29+
- **Aggregate usage in proper time windows.** When no specific timeframe is provided:
30+
- Default to a rolling 28-day window (standard practice in VS Code telemetry)
31+
- Use full day boundaries to avoid partial day data
32+
- Follow the time filtering patterns from the telemetry documentation
33+
- **Correctly map names and keys.** EventName is the prefix (`monacoworkbench/` for vscode) and lowercase event name. Properties/Measurements keys are lowercase. Any properties marked `isMeasurement` are in the Measurements bag.
34+
- **Parallelize queries when possible.** Run multiple independent queries as parallel tool calls to speed up analysis.
35+
36+
# Output Format
37+
38+
Your response should include:
39+
- The actual Kusto query executed (formatted nicely)
40+
- Real query results with data to answer the user's question
41+
- Interpretation and analysis of the results
42+
- References to specific documentation files when applicable
43+
- Additional context or insights from the telemetry data

0 commit comments

Comments
 (0)