Skip to content

Check in a part

Checking in publishes one file: it saves, pushes to GitHub, and releases that file's lock in one action. It adds a new cloud version of the file and is the everyday way to share your work.

Check In does not create a snapshot. A snapshot is a deliberate milestone of the whole repository — see Publish a snapshot. Use Check In for routine file-by-file changes; use Publish Snapshot to mark a milestone.

Prerequisites

  • You hold the lock (Locked by Me) on the file you want to check in.
  • You have saved your changes in SolidWorks. A changed file shows an M badge.

Steps

  1. Right-click the file → Check In.
  2. Type a short description of what you changed.
  3. Click Check In.

If the file has several unpublished local versions, GitM offers a choice:

  • Squash — collapse the local versions into one commit.
  • Keep separate — publish each local version as its own commit, preserving the step history.

Both publish your work; pick whichever history you want to keep.

Expected result

  • GitM commits, pushes, and releases the lock for that file.
  • The file returns to read-only and Not Locked.
  • The file's Cx badge advances to its new cloud version (e.g. C3 → C4).
  • Any L (local version) badges on the file clear.
  • No new snapshot appears on the Snapshots tab — that only happens when you Publish Snapshot.

Troubleshooting

Symptom Cause Fix
"Publish failed" / push rejected The remote moved ahead of you. GitM retries by pulling first; if it still fails, Get Latest and try again. See Troubleshoot everyday issues.
The L badge stays after check-in Stale count, or the push didn't complete. Refresh. If the commit truly didn't push, check your connection and check in again.
A squash prompt appears You have several unpublished local versions. Choose Squash or Keep separate; both publish your work.
You expected a snapshot to appear Check In is per-file and creates no snapshot. To cut a milestone, use Publish a snapshot.

Known limitations

  • Check In is commit + push + unlock together, by design. There is no "commit without push" on this button — for that, use Save Local Version.
  • A failed push can leave the file partially published; re-running Check In or Get Latest then Check In resolves it.