{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":431062272,"defaultBranch":"main","name":"vscode-swift","ownerLogin":"swiftlang","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-11-23T10:47:27.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/42816656?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1726672615.0","currentOid":""},"activityList":{"items":[{"before":"f527210faf8ef09d222edc05639231639e8f1e08","after":"10deaf4ba2b3dea21e9d2c71fac8d2df9a140276","ref":"refs/heads/main","pushedAt":"2024-09-19T18:07:19.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Cross platform artifact cleanup in package.json scripts (#1080)\n\n* Cross platform artifact cleanup in package.json scripts\r\n\r\nThe scripts in the extension package.json relied on `rm -rf` to clean\r\nout build artifacts to ensure clean test runs and builds. To make it\r\neasier to build the extension on Windows, use a cross platform node\r\nmodule to perform this cleanup.\r\n\r\n* Few more fixes for a fresh windows install","shortMessageHtmlLink":"Cross platform artifact cleanup in package.json scripts (#1080)"}},{"before":"363ec5ad0a0af8445542baa8facb674cd7d817a4","after":"f527210faf8ef09d222edc05639231639e8f1e08","ref":"refs/heads/main","pushedAt":"2024-09-19T12:43:17.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"award999","name":null,"path":"/award999","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/78549403?s=80&v=4"},"commit":{"message":"Fix truncated diagnostics on Windows (#1082)\n\n* We never want to resize the terminal regardless of if\r\n deployed or debug environment\r\n* If we are using conpty don't put large cols values as it\r\n will throw an error when task terminal opens\r\n* When we aren't using conpty (debugging) need to set a\r\n large cols value\r\n\r\nIssue: #1074","shortMessageHtmlLink":"Fix truncated diagnostics on Windows (#1082)"}},{"before":"e0ec18298f3f234c6ef5fc04fa28515632c7f484","after":"363ec5ad0a0af8445542baa8facb674cd7d817a4","ref":"refs/heads/main","pushedAt":"2024-09-18T20:04:52.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Fix broken link in CONTRIBUTING.md (#1081)","shortMessageHtmlLink":"Fix broken link in CONTRIBUTING.md (#1081)"}},{"before":"5a4786f534082884f728996d0db5f5b503a18292","after":"e0ec18298f3f234c6ef5fc04fa28515632c7f484","ref":"refs/heads/main","pushedAt":"2024-09-18T17:34:43.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Ignore unnecessary files when packaging extension (#1079)\n\n* Ignore unnessary files when packaging extension\r\n\r\nSlim down the extension by ignoring files that don't need to\r\nbe included in the .vsix\r\n\r\nIssue: #1078","shortMessageHtmlLink":"Ignore unnecessary files when packaging extension (#1079)"}},{"before":"66ca41deb0a8adcccc94f9dd279c2466a556d567","after":"5a4786f534082884f728996d0db5f5b503a18292","ref":"refs/heads/main","pushedAt":"2024-09-17T16:59:11.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"award999","name":null,"path":"/award999","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/78549403?s=80&v=4"},"commit":{"message":"Add docstring and unit tests for attachDebugger (#1056)\n\n* Refactor to use showQuickPick to reduce test surface\r\n\r\nThe onButtonPressed param was never utilized, so opt to use the simpler\r\nshowQuickPick instead to keep things simple.\r\n\r\nIssue: #1023\r\n\r\n* Add docstring and unit tests for attachDebugger\r\n\r\nWe should hit 100% line coverage for this module now.\r\n\r\nIssue: #1023\r\n\r\n* Fix comment that does not reflect what the test is doing","shortMessageHtmlLink":"Add docstring and unit tests for attachDebugger (#1056)"}},{"before":"be8372e8cd00a036bbaa5ee90c5b22c34ae37665","after":"66ca41deb0a8adcccc94f9dd279c2466a556d567","ref":"refs/heads/main","pushedAt":"2024-09-17T16:43:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"award999","name":null,"path":"/award999","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/78549403?s=80&v=4"},"commit":{"message":"Release vscode-swift 1.11.1 (#1075)","shortMessageHtmlLink":"Release vscode-swift 1.11.1 (#1075)"}},{"before":"5d5cf2b59c65f2e54079c57fcc740c12b273ce50","after":"be8372e8cd00a036bbaa5ee90c5b22c34ae37665","ref":"refs/heads/main","pushedAt":"2024-09-16T20:34:24.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Fix extension activation for inisders build (#1073)\n\n* VSCode has moved node-pty out of the asar bundle and into a typical\r\n node_modules folder structure","shortMessageHtmlLink":"Fix extension activation for inisders build (#1073)"}},{"before":"690fd2a0cdcdf3c6989eb286063b90e9ddc59e6b","after":"5d5cf2b59c65f2e54079c57fcc740c12b273ce50","ref":"refs/heads/main","pushedAt":"2024-09-16T14:52:40.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Open version specific manifest if applicable (#1071)\n\nThe language status item has a link to the Package.swift file. If the\r\nuser has a version specific manifest file in the form\r\n`Package@swift-[version].swift` where the version matches their\r\ncurrently installed Swift version, open that Package.swift instead.\r\n\r\nIssue: #1070","shortMessageHtmlLink":"Open version specific manifest if applicable (#1071)"}},{"before":"335739be4400134d5628392cd3f43258c7700087","after":"690fd2a0cdcdf3c6989eb286063b90e9ddc59e6b","ref":"refs/heads/main","pushedAt":"2024-09-16T13:45:19.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Refresh the test explorer when the package changes (#1067)\n\nCurrently if the user adds or removes a test target from the package\r\nmanifest this change is not reflected in the test list of the test\r\nexplorer.\r\n\r\nWhen the package manifest is updated, refresh the test explorer by\r\nmaking a workspace/test's LSP request.","shortMessageHtmlLink":"Refresh the test explorer when the package changes (#1067)"}},{"before":"4fd1e410a8f04d5387e0474e0cfeafaacfb7f16a","after":"335739be4400134d5628392cd3f43258c7700087","ref":"refs/heads/main","pushedAt":"2024-09-13T18:44:07.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"matthewbastien","name":"Matthew Bastien","path":"/matthewbastien","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/65295938?s=80&v=4"},"commit":{"message":"Hide underlying debug adapter from the user (#1024)\n\nAlways generate swift-lldb launch configurations that delegate to the correct debug adapter.\r\nWork around the lack of CodeLLDB support on Windows arm64 by forcing the use of lldb-dap in this case.","shortMessageHtmlLink":"Hide underlying debug adapter from the user (#1024)"}},{"before":"9de90ab1308c2f3bed5da066d94d04fefbe22877","after":"4fd1e410a8f04d5387e0474e0cfeafaacfb7f16a","ref":"refs/heads/main","pushedAt":"2024-09-11T15:40:35.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add unit test for verifyDebugAdapterExists (#1063)\n\nIssue: #1023","shortMessageHtmlLink":"Add unit test for verifyDebugAdapterExists (#1063)"}},{"before":"7b62f58c935813daae117940e58cead7fafb08d5","after":"9de90ab1308c2f3bed5da066d94d04fefbe22877","ref":"refs/heads/main","pushedAt":"2024-09-11T15:26:23.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add command to run all tests in parallel (#1065)\n\n* Add command to run all tests in parallel\r\n\r\nThe command palette has entries for Running all tests, debugging all\r\ntests, and generating code coverage for all tests. However because the\r\nparallel profile is added as a 'standard' profile the same as 'run all\r\ntests' is it not automatically included in the command palette.\r\n\r\nThis patch adds a command to run all tests in parallel to the command\r\npalette. If a user wants to assign a keyboard shortcut to this command\r\nit should now be possible from the Keyboard Shortcuts view.\r\n\r\nNote that the parallel run only parallelizes XCTest executions.\r\nSwift-testing tests are run parallel by default, and can be run\r\nserialized on a per suite basis, but this test run profile has no effect\r\non them.\r\n\r\nIssue: #1064\r\n\r\n* Add licence header\r\n\r\n* Fixup newline in package.json","shortMessageHtmlLink":"Add command to run all tests in parallel (#1065)"}},{"before":"bc62cb339bd7143711bcd8e520a0b18ac88ee03f","after":"7b62f58c935813daae117940e58cead7fafb08d5","ref":"refs/heads/main","pushedAt":"2024-09-11T14:27:17.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Fixup lint issue (#1066)","shortMessageHtmlLink":"Fixup lint issue (#1066)"}},{"before":"1e6331b64b9b1ae4e95ab88572db28dbff1b591b","after":"bc62cb339bd7143711bcd8e520a0b18ac88ee03f","ref":"refs/heads/main","pushedAt":"2024-09-09T14:58:41.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Create minimal list of test args for `swift test` (#1053)\n\nWhen running tests in VS Code a list of arguments is produced that is\r\npassed to `swift test`. This list is determined by what the user has\r\nselected in the test explorer. If the user has several tests/suites\r\nselected the list was tests was paired down to a minimal list of\r\ntests/suites that covers the users selection.\r\n\r\nThis paring down process stopped at the suite level, so if the user ran\r\nan entire test target then all suites in the target were included in\r\nthe list. This works but only up to a point in larger projects. For\r\ninstance running all the tests in swift-format generates a list of test\r\nsuites so long that it breaks on Windows.\r\n\r\nImprove the pairing logic to work down to the test target level. If a\r\ntest target contains both XCTest and swift-testing tests it ends up in\r\nboth the `xcTestArgs` and `swiftTestingArgs` and the two separate runs\r\nof `swift test` with the test library enablement/disablement flags\r\ntakes care of excluding one type from the other.","shortMessageHtmlLink":"Create minimal list of test args for swift test (#1053)"}},{"before":"dceec6b0344ae999434c7f84f2abe2584941bd71","after":"1e6331b64b9b1ae4e95ab88572db28dbff1b591b","ref":"refs/heads/main","pushedAt":"2024-09-09T14:42:40.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Fixup failing `@slow` test (#1051)","shortMessageHtmlLink":"Fixup failing @slow test (#1051)"}},{"before":"61d5450496a51a1159fd7dfce52b2efa13c87ded","after":"dceec6b0344ae999434c7f84f2abe2584941bd71","ref":"refs/heads/main","pushedAt":"2024-09-09T14:14:16.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Use swift-testing stdout as test results log verbatim (#1058)\n\nInstead of reconstructing the swift-testing output from a combination of\r\nstdout and the JSON event stream, simply pass stdout through directly\r\nand use that as the test results log. Use the JSON event stream to drive\r\ntest pass/fail/skip/issue/etc behaviour.\r\n\r\nThis resolves a race condition between the JSON event stream and stdout\r\ninterleaving output in an incorrect order.\r\n\r\nThis approach has the drawback of no longer associating individual lines\r\nof output derived from the JSON event stream with a specific test,\r\nhowever this was offering limited benefit since user output wasn't\r\ncaptured in this way. Once every line of output can be accounted for in\r\nthe JSON event stream we can add this functionality back in with user\r\noutput included.\r\n\r\nIssue: #1054","shortMessageHtmlLink":"Use swift-testing stdout as test results log verbatim (#1058)"}},{"before":"c01b9a94763d20a8ea3d54ec8f5857ac17083673","after":"61d5450496a51a1159fd7dfce52b2efa13c87ded","ref":"refs/heads/main","pushedAt":"2024-09-09T13:38:12.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Remove `experimental` from swift-testing flags (#1061)\n\nThese have been stabilized and the `experimental` versions of the flags\r\nhave been deprecated.","shortMessageHtmlLink":"Remove experimental from swift-testing flags (#1061)"}},{"before":"8d031b076726afc9d7c3a826224458ef902cf1c9","after":"c01b9a94763d20a8ea3d54ec8f5857ac17083673","ref":"refs/heads/main","pushedAt":"2024-09-06T15:37:48.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Work around `Uri` round-tripping issue in VS Code for `sourcekit-lsp` scheme (#1026)","shortMessageHtmlLink":"Work around Uri round-tripping issue in VS Code for sourcekit-lsp…"}},{"before":"303d4d2365b25cb424c9d12631dc84a66e2e3d3b","after":"8d031b076726afc9d7c3a826224458ef902cf1c9","ref":"refs/heads/main","pushedAt":"2024-09-06T15:34:29.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Change `swift.sourcekit-lsp.serverPath` deprecation message to hint that it’s OK to change while developing SourceKit-LSP (#1057)","shortMessageHtmlLink":"Change swift.sourcekit-lsp.serverPath deprecation message to hint t…"}},{"before":"251972655638e936226c04ba46c597322332bcfd","after":"303d4d2365b25cb424c9d12631dc84a66e2e3d3b","ref":"refs/heads/main","pushedAt":"2024-09-03T12:57:56.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Show Swift test explorer context menu items only for Swift tests (#1048)\n\nKeep a flattened list of swift Test Explorer test IDs in the context and\r\nuse a `when` clause on the context menu items to only show them on Swift\r\ntests in the Text Explorer.\r\n\r\nIssue: #1047","shortMessageHtmlLink":"Show Swift test explorer context menu items only for Swift tests (#1048)"}},{"before":"ad9917595b9b2a46a908fcd3bb7662d6d08d16ac","after":"251972655638e936226c04ba46c597322332bcfd","ref":"refs/heads/main","pushedAt":"2024-08-29T20:04:44.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add tests for Run Tests Multiple Times (#1041)","shortMessageHtmlLink":"Add tests for Run Tests Multiple Times (#1041)"}},{"before":"ad15f0eae4265e055889b9b71c4581a08947d57e","after":"ad9917595b9b2a46a908fcd3bb7662d6d08d16ac","ref":"refs/heads/main","pushedAt":"2024-08-28T18:36:08.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"matthewbastien","name":"Matthew Bastien","path":"/matthewbastien","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/65295938?s=80&v=4"},"commit":{"message":"enforce prettier rules on JSON files (#1040)","shortMessageHtmlLink":"enforce prettier rules on JSON files (#1040)"}},{"before":"59f46d773e25288d8f8c6eb2b80ea860da83f1cb","after":"ad15f0eae4265e055889b9b71c4581a08947d57e","ref":"refs/heads/main","pushedAt":"2024-08-28T15:35:51.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Release 1.11.0 (#1039)\n\n* Release 1.11.0","shortMessageHtmlLink":"Release 1.11.0 (#1039)"}},{"before":"4b801644ee751cba7362325d93c0b7ebc257c2c4","after":"59f46d773e25288d8f8c6eb2b80ea860da83f1cb","ref":"refs/heads/main","pushedAt":"2024-08-28T15:09:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"award999","name":null,"path":"/award999","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/78549403?s=80&v=4"},"commit":{"message":"Fix coverage report (#1032)\n\n* Fix coverage report\r\n\r\nIssue was the dist/extension.js file was what vscode-test was running as\r\nthe extension as it was what was specified as the entry point in the\r\npackage.json. So The globalWorkspaceContextPromise helper we use in a lot\r\nof tests to make sure the extension is activated, returns an instance of\r\nthe WorkspaceContext. Any behaviour stimulated through that context is\r\nmissed from the coverage report, and also any breakpoint hits are ignored.\r\nSo for example the BackgroundCompilation instance that is created on\r\nextension activation was left out of the coverage report.\r\n\r\nTo fix, only bundle to a single extension.js file when packaging a vsix.\r\nWhen debugging or running tests we transpile all the files individually.\r\nThe dist/extension.js file is still used when activating, but sourcemap\r\nnow works so the coverage report is accurate.\r\n\r\nIssue: #1021\r\n\r\n* Make sure source bp can be hit when debugging test","shortMessageHtmlLink":"Fix coverage report (#1032)"}},{"before":"d7b377c204452275a27160a3ffb65b55fcd15c86","after":"4b801644ee751cba7362325d93c0b7ebc257c2c4","ref":"refs/heads/main","pushedAt":"2024-08-28T14:43:12.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Mark XCTests as passed without a second pass over the output (#1034)\n\nThe lastTestItem was not being set right away when a test succeeded\r\nbecause tests were being marked as passed in a second pass of the\r\nXCTest output after a run completed.\r\n\r\nGoing by the removed comment this second pass was added to disambiguate\r\npassing tests with the same suite/test name across multiple targets.\r\n\r\nHowever, the test target is present in the `testName` used to look up a\r\ntest's index. For instance, it may look like\r\n`TestTargetA/Suite/testFoo` and so would not be identical to\r\n`TestTargetB/Suite/testFoo`, and so we get the correct `testIndex` for\r\neither test.","shortMessageHtmlLink":"Mark XCTests as passed without a second pass over the output (#1034)"}},{"before":"d6c91dd379abd6a402dddb3503e35fd328c6ce21","after":"d7b377c204452275a27160a3ffb65b55fcd15c86","ref":"refs/heads/main","pushedAt":"2024-08-27T19:41:58.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add Run Multiple menu items to test item gutter (#1035)\n\nWe can add the Run Multiple Times and Run Until Failure menu items onto\r\nthe green play button icon in the gutter of the editor. This is in\r\naddition to having it on individual items in the test explorer.","shortMessageHtmlLink":"Add Run Multiple menu items to test item gutter (#1035)"}},{"before":"0c7ee916a68359e1d949a8ca68b5516fbe48b953","after":"d6c91dd379abd6a402dddb3503e35fd328c6ce21","ref":"refs/heads/main","pushedAt":"2024-08-27T14:15:19.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add swift.testBuildArguments Setting (#1020)\n\n* Add swift.testBuildArguments Setting\r\n\r\nAdds a new setting that allows users to specify extra arguments when\r\nrunning `swift test` and `swift build --build-tests` during a test run\r\nfrom inside VS Code.\r\n\r\nFor example users could set `swift.testBuildArguments: [\"-Xswiftc\",\r\n\"-DTEST\"]` to enable code guarded by an `#if TEST` compiler directive.\r\n\r\nThis patch required reworking how we do a build all before starting a\r\ndebug session since using the premade Build All tasks do not allow for\r\ndynamically customizing arguments.","shortMessageHtmlLink":"Add swift.testBuildArguments Setting (#1020)"}},{"before":"6fb2ee84cad7e4d2759d1db61da864241be4bfea","after":"0c7ee916a68359e1d949a8ca68b5516fbe48b953","ref":"refs/heads/main","pushedAt":"2024-08-27T12:59:59.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Mark XCTest suites as passed/failed immediately on suite completion (#1031)\n\nAdd back some code that was removed that marked XCTest suites as\r\npassed/failed as soon as all their tests completed. Currently the\r\nTestExplorer shows the test suites as pending until all tests in the\r\nwhole test run have completed. This is a regression from how the Test\r\nExplorer used to work, where suites were marked as passed/failed\r\nimmediately upon suite completion.\r\n\r\nIssue: #1029","shortMessageHtmlLink":"Mark XCTest suites as passed/failed immediately on suite completion (#…"}},{"before":"c1f8b9e2064d8a97d0cf7a9a6d916b2d982a7020","after":"6fb2ee84cad7e4d2759d1db61da864241be4bfea","ref":"refs/heads/main","pushedAt":"2024-08-27T11:45:10.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Add New Swift File command (#1018)\n\n* Add New Swift File command\r\n\r\nAdd a command that creates a new Swift File. Add it as an option to the\r\nFile > New File picker. Add it as an option when right clicking a\r\nfolder in a Swift project context. Add a keybinding of Opt+S Opt+N (or\r\nAlt+S Alt+N) to create a new Swift file.","shortMessageHtmlLink":"Add New Swift File command (#1018)"}},{"before":"e1f51396bdfa8dd5bddc64ec6158d2ea89a65035","after":"c1f8b9e2064d8a97d0cf7a9a6d916b2d982a7020","ref":"refs/heads/main","pushedAt":"2024-08-26T19:37:27.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"plemarquand","name":"Paul LeMarquand","path":"/plemarquand","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/667875?s=80&v=4"},"commit":{"message":"Organize commands in to folders (#1012)\n\nBreak out individual commands from src/commands.ts in to individual\r\nfiles that export their main command function.","shortMessageHtmlLink":"Organize commands in to folders (#1012)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEuy4IAgA","startCursor":null,"endCursor":null}},"title":"Activity · swiftlang/vscode-swift"}