Save a local version¶

Save Local Version saves a checkpoint of your work on your machine without publishing it and without releasing your lock. Use it for restore points mid-task before you're ready to share.

Prerequisites¶

You hold the lock (Locked by Me) on the file.
You have saved the file in SolidWorks (so there's a change to checkpoint).

Steps¶

In the Files tab, find the checked-out file.
Right-click the file → 💾 Save Local Version.

Expected result¶

The file gains an L badge with a number: L1 for your first local version, L2 for the next, and so on.
Your lock stays held; the file stays writable; nothing is published to the team yet.

Publishing local versions later¶

When you're ready to share, check in. Check In publishes the file (with a Squash / Keep separate choice for its local versions) and releases the lock — this does not create a snapshot. After a successful check-in the L badge clears. To mark a whole-repo milestone, use Publish a snapshot.

Discarding local versions¶

If you decide not to keep your work, releasing the lock discards unpublished local versions. GitM warns you first, because this cannot be undone.

Troubleshooting¶

Symptom	Cause	Fix
L badge persists after a successful check-in	Known stale-count issue (fixed) — the count is the number of local commits not yet on GitHub.	Refresh the task pane; the badge clears once the count re-reads as zero.
Save Local Version does nothing	No saved change since the last version.	Save in SolidWorks first.

Known limitations¶

Local versions live only on your machine. They are stored in .gitm/local-versions.json, which is per-machine and never tracked. If you lose the machine before checking in, unpublished local versions are gone.
Releasing a lock or discarding a file drops unpublished local versions (with a warning).