Skip to content

Fix Create on GitHub in Issue Reporter after extension bisect#314616

Open
yogeshwaran-c wants to merge 1 commit intomicrosoft:mainfrom
yogeshwaran-c:fix/issue-reporter-bisect-github-248339
Open

Fix Create on GitHub in Issue Reporter after extension bisect#314616
yogeshwaran-c wants to merge 1 commit intomicrosoft:mainfrom
yogeshwaran-c:fix/issue-reporter-bisect-github-248339

Conversation

@yogeshwaran-c
Copy link
Copy Markdown
Contributor

Summary

After extension bisect identifies a bad extension, choosing "Report Issue & Continue" opens the Issue Reporter and then immediately reloads the main window. The Issue Reporter lives in an auxiliary window whose services are owned by the main window, so reloading orphans those service references and makes the "Create on GitHub" button (and other "show" buttons) silently do nothing.

This change skips the trailing hostService.reload() only on the report path. Bisect storage is still reset and the chosen "keep this extension disabled" choice is honored. The user can reload the window themselves once they're done with the issue report.

Fixes #248339

Test plan

  • Run Extension Bisect: Start Extension Bisect and complete bisect to identify a bad extension.
  • In the final dialog, click "Report Issue & Continue".
  • Issue Reporter opens; "Create on GitHub" / "Preview on GitHub" / show buttons all work.
  • After closing the Issue Reporter, reloading the window restores the other (temporarily bisect-disabled) extensions.
  • Bisect path that does not report (cancel button, "no extension identified" path) still reloads as before.

The bisect "Report Issue & Continue" path opened the Issue Reporter and
then immediately reloaded the main window. The Issue Reporter lives in
an auxiliary window whose services are owned by the main window, so the
reload orphaned those services and made the Create on GitHub button
(and other "show" buttons) silently no-op.

Skip the trailing host reload when the user opted to report. Bisect state
is still reset so the bad extension stays identified, and the user can
manually reload to re-enable other temporarily disabled extensions once
they finish filing the issue.

Fixes microsoft#248339
Copilot AI review requested due to automatic review settings May 6, 2026 01:45
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the extension bisect completion flow to avoid reloading the main workbench window when the user chooses “Report Issue & Continue”, because the Issue Reporter runs in an auxiliary window that depends on main-window services (and a reload can orphan those services, breaking “Create on GitHub” / “show” actions).

Changes:

  • Skip the trailing hostService.reload() when the user selects the report path, to keep the main window (and its services) alive while the Issue Reporter is open.
  • Keep clearing bisect state via bisectService.reset() and continue to honor the “Keep this extension disabled” choice.

Comment on lines +325 to +327
await bisectService.reset();
await commandService.executeCommand('workbench.action.openIssueReporter', done.id);
return;
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.

Create on GitHub in Issue Reporter after extension bisect doesn't do anything

3 participants