Version control
for the things
you build.

GigaCAD puts your SolidWorks projects in a drive in File Explorer. Work on a branch, save as usual, and release to main when the assembly rebuilds clean.

Start a project

Desktop apps for Windows and Mac are coming soon. Start in the browser today.

rc-buggy / Release requests / #12

Longer-travel rear suspension

Opensuspension into main v7

FilePick

rear_suspension.SLDASM

Changed on both sides

Pick for rear_suspension.SLDASM

rear_arm_L.SLDPRT

Changed on branch

Pick for rear_arm_L.SLDPRT

chassis_plate.SLDPRT

Changed on main in v7

Pick for chassis_plate.SLDPRT

shock_long.SLDPRT

New on branch

Pick for shock_long.SLDPRT

Rebuild

Rebuild passed

0 rebuild errors, 0 mate errors in rear_suspension.SLDASM.

Approvals 1 of 2

  • A @alexApproved
  • S @sarahWaiting

This is a working release request. Change a pick and see what happens to the approvals.

Work on a branch. Release when it rebuilds.

Main is a series of releases that never change. Everything else happens on branches, one person at a time.

A branch forks from release v6, collects autosaves and two versions, and becomes v8 through release request 12.Check out12Longer arms3Stiffer mountRelease request #124v6v7v85mainautosaves, cleared at each version
  1. Check out

    Take the branch. Everyone else sees it read-only until you check it in.

  2. Save as usual

    Every save in SolidWorks becomes an autosave. No extra clicks.

  3. Commit a version

    Name what changed. Earlier autosaves are cleared.

  4. Open a release request

    Pick what ships and rebuild the assembly against it.

  5. Release

    Once approved, the branch becomes the next locked version of main.

It’s a folder you already know how to use.

Projects show up under GigaCAD in the File Explorer sidebar. Open an assembly from your branch folder and SolidWorks finds every reference, even offline. Releases and other people’s branches are there too, read-only.

GigaCAD › alex › rc-buggy › branches › suspension
  • GigaCAD
  • rc-buggy
  • main
  • releases
  • branches
  • suspension
  • battery-tray
  • candidates
NameStatus
rear_suspension.SLDASM Synced
rear_arm_L.SLDPRT Uploading
rear_arm_R.SLDPRT Synced
shock_long.SLDPRT Synced
chassis_plate.SLDPRT Synced

One person edits a branch at a time.

Checking out a branch gives you the only write access to it. Anyone else who opens those files gets them read-only, with a note saying who has them. Nobody overwrites anybody. Maintainers can take back a lock someone forgot about, and it’s logged.

battery-tray is checked out by @sarah. This file opened read-only.

  • suspensionChecked out by you
  • battery-tray @sarah, 2h
  • steering-reworkChecked in

Pick what ships, file by file.

A release request lists every file that differs from main. Take the branch’s copy or keep main’s. If you remade a part under a new name, let it replace the old one: it keeps the old part’s history, and the assembly is rebuilt to use it.

shock.SLDPRTmain, 9 versions
shock_long.SLDPRTcontinues the same history

Releases stay exactly as you shipped them.

Every release is locked the moment it’s made. Nobody can edit or delete one, including the project owner. Choose who has to approve a release request, and how many of them.

  1. v8Longer-travel rear suspension 2 of 2 approved
  2. v7Battery tray moved forward Locked
  3. v6Steel chassis plate Locked
  4. v5First drivable build Locked

Autosaves clean up after themselves

Every save is kept until you commit a version. Then the in-between saves are cleared, so storage holds what matters.

Look before you download

Each version has thumbnails and a 3D preview in the browser, so you can check a part without opening SolidWorks.

Share a project, or keep it private

Make a project public and anyone can browse its releases and fork one to start their own.

Put your next build under version control.

Start a project