fix: sign-in error caused by typo in telementry.

[jiashengguo]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated VSCode telemetry identify payload to use VSCODE_TELEMETRY_TRACKING_TOKEN instead of TELEMETRY_TRACKING_TOKEN in the VSCodeTelemetry class. No other logic or control flow changes.

Changes

Cohort / File(s)	Summary
VSCode Telemetry Token Update packages/schema/src/vscode/vscode-telemetry.ts	Switched identify payload token from TELEMETRY_TRACKING_TOKEN to VSCODE_TELEMETRY_TRACKING_TOKEN.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	No description was provided, so the pull request lacks any summary of the changes and fails to inform reviewers of what was modified.	Add a brief description explaining that the PR fixes a typo by replacing TELEMETRY_TRACKING_TOKEN with VSCODE_TELEMETRY_TRACKING_TOKEN in the VSCodeTelemetry.identify payload.
Title Check	⚠️ Warning	The title refers to a fix for a typo in telemetry that caused sign-in errors but contains a spelling mistake (“telementry”) and does not clearly summarize the specific change to the VSCodeTelemetry tracking token constant.	Revise the title to be concise, accurate, and error-free, for example “fix: correct VSCode telemetry tracking token constant” or similar without typos.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jiasheng-fix

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}