Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Safe CheckpointNew to Visual Studio Code? Get it now.
Safe Checkpoint

Safe Checkpoint

XinChi Yang

|
1 install
| (0) | Free
Save, compare, and restore versions of your work in a simple way—starting with one-click Publish (add, commit, push).
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Safe Checkpoint

VS Code / Cursor extension to save, compare, and restore versions of your work in a simple way.
v0.1 focuses on Publish: one action runs git add, git commit (with your message), and git push—without using the Git UI yourself.

Requirements

  • Git installed and available on your PATH.
  • A folder opened in the editor that is a Git repository.
  • A remote configured (e.g. origin) and the current branch upstream set (e.g. after one git push -u origin <branch>).

Install (development)

  1. Clone this repo and open the folder in VS Code or Cursor.
  2. Run npm install.
  3. Run npm run compile.
  4. Press F5 (Run Extension) to open an Extension Development Host and try Safe Checkpoint: Publish from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).

Usage

  1. Open your project folder (the one that contains your .git folder).
  2. Run command Safe Checkpoint: Publish.
  3. Edit the suggested commit message if you want, then confirm.
  4. If there are no changes, you’ll see a short notice. If push fails after a successful commit, you’ll get guidance and optional error details.

On startup, if the folder is not a Git repo, Safe Checkpoint shows a one-time informational message.

Manual scenarios: docs/SMOKE_TESTS.md.

Package a VSIX (smoke test)

npm install
npm run compile
npx vsce package

This produces a .vsix file you can install: Extensions view → ... → Install from VSIX....

Publish to the VS Code Marketplace

  1. Create a publisher (Microsoft account).
  2. Install CLI: npm install -g @vscode/vsce (or use npx vsce).
  3. Create a Personal Access Token with Marketplace (Manage) scope.
  4. Run vsce login <your-publisher-id>.
  5. In package.json, set "publisher" to your publisher ID and update "repository" if needed.
  6. Run vsce publish (or vsce publish patch for subsequent versions).

Short copy-paste flow: docs/MARKETPLACE.md.

License

See LICENSE.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft