Use em-dashes in user-facing text

Author: j-256

CONTRIBUTING.md

@@ -49,10 +49,10 @@ npm version patch   # or minor, major
 
 This single command:
 
-1. **preversion** -- verifies you're on `main`, runs build + tests
+1. **preversion** — verifies you're on `main`, runs build + tests
 2. Bumps version in package.json
 3. Commits the version bump and creates a `v*` tag
-4. **postversion** -- pushes the commit and tag to origin
+4. **postversion** — pushes the commit and tag to origin
 
 CI then takes over:
 
@@ -71,7 +71,7 @@ Trigger the full build/package pipeline without publishing:
 gh workflow run ci.yml --ref dev
 ```
 
-This runs with `dry_run=true` (the default), which builds binaries, packages VSIX files, and verifies their contents -- but skips the GitHub release and marketplace publish steps. Uncheck `dry_run` in the GitHub UI to publish from a manual dispatch (only allowed from `main`).
+This runs with `dry_run=true` (the default), which builds binaries, packages VSIX files, and verifies their contents — but skips the GitHub release and marketplace publish steps. Uncheck `dry_run` in the GitHub UI to publish from a manual dispatch (only allowed from `main`).
 
 ### Recovery
 
@@ -91,13 +91,13 @@ npm version patch
 
 ### Branches
 
-- **main** -- releases happen here; `npm version` enforces this via a branch guard
-- **dev** -- CI runs tests and dry-run builds; publish steps are gated behind `dry_run` input and a main-branch guard
+- **main** — releases happen here; `npm version` enforces this via a branch guard
+- **dev** — CI runs tests and dry-run builds; publish steps are gated behind `dry_run` input and a main-branch guard
 
 ## CI
 
 GitHub Actions (`.github/workflows/ci.yml`):
 
-- **test** -- runs on every push to `main`/`dev` and on PRs to `main`
-- **build-git-crypt** -- compiles static git-crypt binaries on macOS (arm64 via macos-15) and Linux (x64 and arm64 via Alpine Docker, arm64 uses QEMU). Runs on tags and `workflow_dispatch`
-- **publish** -- packages platform-specific and universal VSIX files, verifies contents, optionally creates GitHub release and publishes to marketplace. Release/publish steps are controlled by the `dry_run` input (defaults to true on manual dispatch; always false on tag pushes)
+- **test** — runs on every push to `main`/`dev` and on PRs to `main`
+- **build-git-crypt** — compiles static git-crypt binaries on macOS (arm64 via macos-15) and Linux (x64 and arm64 via Alpine Docker, arm64 uses QEMU). Runs on tags and `workflow_dispatch`
+- **publish** — packages platform-specific and universal VSIX files, verifies contents, optionally creates GitHub release and publishes to marketplace. Release/publish steps are controlled by the `dry_run` input (defaults to true on manual dispatch; always false on tag pushes)

README.md

@@ -6,17 +6,17 @@ VSCode extension that makes [git-crypt](https://github.com/AGWA/git-crypt) repos
 
 ## The Problem
 
-VSCode's extension host process uses a minimal `PATH` that often excludes directories like `/opt/homebrew/bin` -- even when VSCode is launched from a terminal with the full PATH configured. This means the `git-crypt` clean/smudge filter fails with `git-crypt: command not found`, which can prevent the entire repository from loading in the SCM panel.
+VSCode's extension host process uses a minimal `PATH` that often excludes directories like `/opt/homebrew/bin` — even when VSCode is launched from a terminal with the full PATH configured. This means the `git-crypt` clean/smudge filter fails with `git-crypt: command not found`, which can prevent the entire repository from loading in the SCM panel.
 
 ## How It Works
 
-On macOS and Linux, the extension ships a bundled `git-crypt` binary. No separate installation needed -- the extension appends its binary to `PATH` so git's clean/smudge filters just work. If you already have git-crypt installed, your version takes precedence.
+On macOS and Linux, the extension ships a bundled `git-crypt` binary. No separate installation needed — the extension appends its binary to `PATH` so git's clean/smudge filters just work. If you already have git-crypt installed, your version takes precedence.
 
 Git-crypt files are also decorated with a lock badge so you can identify them at a glance.
 
 ## Usage
 
-With the extension installed, git-crypt files work like any other file in the Source Control panel -- double-click to diff, stage with the `+` icon, etc.
+With the extension installed, git-crypt files work like any other file in the Source Control panel — double-click to diff, stage with the `+` icon, etc.
 
 ## Requirements
 

src/extension.ts

@@ -57,7 +57,7 @@ export async function activate(context: vscode.ExtensionContext): Promise<void>
     log.appendLine('Aborting: git-crypt not found in PATH');
     vscode.window.showWarningMessage(
       'git-crypt was not found. On macOS and Linux, git-crypt is included ' +
-      'automatically -- reinstall the extension if you\'re on a supported platform. ' +
+      'automatically \u2014 reinstall the extension if you\'re on a supported platform. ' +
       'On Windows, install git-crypt manually.',
     );
     return;