docs(readme): mark Copilot CLI usage/sessions/dashboard as supported (#766) - #767
Merged
Merged
Conversation
…encent#766) PR Tencent#666 (feat: add privacy-safe Copilot telemetry) shipped Copilot support for the Team Improvement columns (usage, sessions, dashboard), but the support matrix in the README files still showed em-dashes for those three cells. Flip them to checkmarks in all five language variants so the matrix matches the shipped, tested behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #666 ("feat: add privacy-safe Copilot telemetry") shipped GitHub Copilot CLI support for the three Team Improvement columns —
usage,sessions, anddashboard— but the support matrix in the README files still showed em-dashes (—) for those cells. This is documentation drift: the matrix contradicts the shipped, tested behavior. This PR flips the three Copilot CLI cells from—to✓in all five README language variants. No code changes.Type of Change
Evidence per column (verified on current
main)src/dashboard-collector.ts(Copilot usage tail/scan constants,isCopilottoken handling) with the missing-token fallback covered by tests;src/usage-tracker.tsresolves the Copilot home.COPILOT_SESSION_END_SPECinsrc/builtin-hooks.ts(Copilot additionally getsSessionEnd) and thesession_end/isCopilotpath insrc/dashboard-collector.ts; path-free session IDs enforced insrc/utils/session-id.ts.src/dashboard-collector.ts(isCopilotevent handling, token snapshots).docs/usage-guide.mdalready documents this: "Session IDs, skill usage, prompt counts, lifecycle state, and final token totals feed the local dashboard."Five languages
README.md,README.zh-CN.md,README.ja.md,README.ko.md,README.th.md— one identical cell change each (—→✓on the Copilot CLI row), matrices remain structurally identical.Test Plan
npx tsc --noEmitpassesnpx vitest runon the Copilot telemetry suites passes:dashboard-collector(144),usage-tracking(93),session-id(9),builtin-hooks(7),copilot-adapter(16),hook-dispatch-cli(18) — 287 tests, all green.src/__tests__/e2e/copilot-agents.test.ts,src/__tests__/e2e/copilot-mcp.test.ts— 2/2 green.npm run buildsucceeds.git diffis exactly 5 files × (1 insertion / 1 deletion) on the Copilot CLI row only.Related Issues
Closes #766
Notes for Reviewers
Docs-only, minimal diff. The three capabilities are exercised by the telemetry unit suites against realistic Copilot session-state/log fixtures and by the Copilot built-CLI E2E. A live GitHub Copilot CLI session was not run because Copilot CLI is not installed on the build host; the shipped behavior is what PR #666 implemented and tested.