Restore repo-tracked files after copying test binaries

[sean-mcmanus]

Summary

yarn install-and-copy-binaries-for-test (and yarn copy-extension-binaries) copies the installed extension's bin, debugAdapters, and LLVM folders into the repo so tests can run against real binaries. A few files under bin are checked into the repo — bin/cpp.hint and bin/messages/**/messages.json — and the copy overwrote them with the installed (pre-release) extension's versions, which differ in line endings (CRLF vs LF) and/or content. That left spurious local modifications (plus an untracked bin/binaryVersion.json) that had to be reverted by hand after every run.

This change makes copyExtensionBinaries.ts restore any repo-tracked files that the copy modified (via git ls-files --modified + git checkout), so only the untracked binaries remain, and gitignores the generated bin/binaryVersion.json marker. The result is a clean git status after running the script.

This PR was created by Copilot with Claude Opus 4.8 (in VS Code). Any PR comments starting with Copilot says: are generated by Copilot.

[Copilot]

Pull request overview

This PR updates the Extension’s binary-copy test workflow to avoid leaving the working tree in a modified state after copying installed binaries into the repo, by restoring repo-tracked files that were overwritten during the copy and ignoring a generated marker file.

Changes:

• Add a post-copy step in copyExtensionBinaries.ts to restore repo-tracked files overwritten by the copy.
• Add bin/binaryVersion.json to Extension/.gitignore to prevent untracked marker noise.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Extension/.scripts/copyExtensionBinaries.ts	Restores tracked files modified by the copy step so tests can use real binaries without leaving spurious git changes.
Extension/.gitignore	Ignores bin/binaryVersion.json generated by the copy workflow to keep git status clean.

Suppressed comments (1)

Extension/.scripts/copyExtensionBinaries.ts:173

• restoreTrackedFiles() is invoked after the copy, but without capturing what was already modified beforehand. That means any pre-existing unstaged edits to tracked files under these folders will be reverted by the restore step.

Capture the modified-tracked-file set before copying and pass it to restoreTrackedFiles so it only restores files newly modified by the copy.

    note(`Copied installed binaries into ${$root}`);

    await restoreTrackedFiles();

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.