Skip to content

Actions: microsoft/vscode-dotnettools

Actions

Release Comment Handler

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
release-comment-handler.yml
776 workflow runs
776 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Cannot navigate to source file from failing test stack trace (file not found) in Dev Container Release Comment Handler #726: Issue #2694 labeled by joaoopereira
2s
2s
Unexpected behavior with run test at cursor when adding new tests Release Comment Handler #725: Issue #2693 labeled by vsccarl
1s
1s
Error while moving Program.cs Release Comment Handler #724: Issue #2692 labeled by ArabellaQi
1s
1s
The sequence numbers can only be 1 and 2 when nesting project folders Release Comment Handler #723: Issue #2691 labeled by ArabellaQi
1s
1s
Issues when creating .sln and .slnx using command Release Comment Handler #722: Issue #2690 labeled by ArabellaQi
1s
1s
Debug Attach Window May Exceed VS Code Window Size Release Comment Handler #721: Issue #2689 labeled by nagilson
1s
1s
[WebToolsE2E] Fail to debug the 11.0 Blazor WASM project using VS Code with error "System.IO.FileNotFoundException: Cannot start debug proxy because it cannot be found" Release Comment Handler #720: Issue #2680 labeled by claudiaregio
1s
1s
[WebToolsE2E] Fail to debug the 11.0 Blazor WASM project using VS Code with error "System.IO.FileNotFoundException: Cannot start debug proxy because it cannot be found" Release Comment Handler #719: Issue #2680 labeled by claudiaregio
1s
1s
[WebToolsE2E] [Mac] Unable to debug 11.0 web app using VS Code on MacOS Release Comment Handler #718: Issue #2681 labeled by claudiaregio
1s
1s
[WebToolsE2E] [Mac] Unable to debug 11.0 web app using VS Code on MacOS Release Comment Handler #717: Issue #2681 labeled by claudiaregio
1s
1s
[NETSDKE2E][Blue] When debugging the UT test with Omnisharp checked, the negative test method run failed with user‑handle dialog unshown. Release Comment Handler #716: Issue #2687 labeled by claudiaregio
1s
1s
[NETSDKE2E][Blue] When debugging the UT test with Omnisharp checked, the negative test method run failed with user‑handle dialog unshown. Release Comment Handler #715: Issue #2687 labeled by claudiaregio
1s
1s
Record C# DevKit Trace - Command to collect tracing information for project-system host && vs-green server host Release Comment Handler #714: Issue #2688 labeled by LittleLittleCloud
1s
1s
Test discovery not finding tests Release Comment Handler #713: Issue #2684 labeled by peterwald
2s
2s
Test discovery not finding tests Release Comment Handler #712: Issue #2684 labeled by claudiaregio
1s
1s
Conditional 'wait for breakpoint' list should update dynamically Release Comment Handler #711: Issue #2686 labeled by vsccarl
Skipped
Skipped
Test discovery not finding tests Release Comment Handler #710: Issue #2684 labeled by andrew-eldridge
1s
1s
Search Fails to Identify Members and Methods in Partial Classes Release Comment Handler #709: Issue #2683 labeled by stonstad
2s
2s
Cached tests cannot be run until discovery happens Release Comment Handler #708: Issue #2675 labeled by claudiaregio
1s
1s
Solution fails to build due to explicit AnyCPU platform setting Release Comment Handler #707: Issue #2678 labeled by claudiaregio
2s
2s
[BUG] sdk Release Comment Handler #706: Issue #2679 labeled by claudiaregio
2s
2s
[WebToolsE2E] Fail to debug the 11.0 Blazor WASM project using VS Code with error "System.IO.FileNotFoundException: Cannot start debug proxy because it cannot be found" Release Comment Handler #705: Issue #2680 labeled by WardenGnaw
1s
1s
[WebToolsE2E] Fail to debug the 11.0 Blazor WASM project using VS Code with error "System.IO.FileNotFoundException: Cannot start debug proxy because it cannot be found" Release Comment Handler #704: Issue #2680 labeled by WardenGnaw
1s
1s
[BUG] sdk Release Comment Handler #703: Issue #2679 labeled by moeemiso
1s
1s
Solution fails to build due to explicit AnyCPU platform setting Release Comment Handler #702: Issue #2678 labeled by alloy
1s
1s