Skip to content

sessions: remove unused GitHub reference list - #341995

Merged
Dmitriy Vasyura (dmitrivMS) merged 2 commits into
mainfrom
dmitriv/remove-unused-github-reference-list
Oct 16, 2026
Merged

Dmitriy Vasyura (dmitrivMS) merged 2 commits into
mainfrom
dmitriv/remove-unused-github-reference-list

Conversation

@dmitrivMS

@dmitrivMS Dmitriy Vasyura (dmitrivMS) commented Oct 16, 2026 •

Copy link
Copy Markdown
Collaborator

Refs https://github.com/microsoft/vscode-internalbacklog/issues/9678

Remove the unused GitHubReferenceList component, its exclusive stylesheet, and its dedicated tests. The component has no production consumers; the GitHub pull-request polling tests remain intact.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings October 16, 2026 10:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The removal is self-contained, with no remaining references reported and unrelated polling coverage preserved.

0 open findings

What changed in this PR

Removes the unused GitHub reference-list component from the Agents Window.

Changes:

  • Deletes the component and its dedicated stylesheet.
  • Removes component-specific tests and imports while preserving pull-request polling tests.

No actionable findings remain. Build and test validation was blocked by unavailable dependencies.

File Description
src/​vs/​sessions/​contrib/​github/​test/​browser/​githubContribution.test.ts Removes reference-list tests; retains polling coverage.
src/​vs/​sessions/​contrib/​github/​browser/​media/​githubReferenceList.css Deletes component-only styles.
src/​vs/​sessions/​contrib/​github/​browser/​githubReferenceList.ts Deletes the unused component and entry type.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Co-authored-by: dmitrivMS <9581278+dmitrivMS@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Screenshot Changes

Base: e0361472 Current: 5335ebb2

Changed (1)

sessions/sessionToolbar/sessionToolbar/SubmenuOpen/Light
Before After
before after

@dmitrivMS
Dmitriy Vasyura (dmitrivMS) merged commit 4765bd3 into main Oct 16, 2026
42 checks passed
@dmitrivMS
Dmitriy Vasyura (dmitrivMS) deleted the dmitriv/remove-unused-github-reference-list branch October 16, 2026 14:15
@vs-code-engineering vs-code-engineering Bot added this to the 1.143.0 milestone Oct 16, 2026
Sandeep Somavarapu (sandy081) added a commit that referenced this pull request Oct 16, 2026
…race

Follow-up to #341995, which fixed the older-build check test by waiting for
the drain statement's own trace as well as its completion. The 'burst of
ten creates or ten deletes' test in the same suite still assumed traces of
finished statements arrive before the drain completes. @vscode/sqlite3
delivers trace events through a separate async callback, so its statement
count could miss late traces in the same way.

Use the same trace-fenced drain as the older-build test.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sandeep Somavarapu (sandy081) added a commit that referenced this pull request Oct 16, 2026
…race (#342054)

Follow-up to #341995, which fixed the older-build check test by waiting for
the drain statement's own trace as well as its completion. The 'burst of
ten creates or ten deletes' test in the same suite still assumed traces of
finished statements arrive before the drain completes. @vscode/sqlite3
delivers trace events through a separate async callback, so its statement
count could miss late traces in the same way.

Use the same trace-fenced drain as the older-build test.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants