video1.0<iframe src="https://www.loom.com/embed/d8f75127a5d344c39c4090dbbb17bde8" frameborder="0" width="1728" height="1296" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12961728Loomhttps://www.loom.com12961728https://cdn.loom.com/sessions/thumbnails/d8f75127a5d344c39c4090dbbb17bde8-0b2133779ab631fc-full.jpg440.845This Loom explains how to use AnchorPoint with GitHub for version control in SOLIDWORKS design projects, focusing on selective auto-locking and submitting meaningful changes. After working normally and saving parts and rebuilding assemblies, AnchorPoint lists modified, added, deleted, and moved files, and calculates thumb data that can take time while locking files. The video shows that assemblies may rebuild frequently without meaningful changes, so auto-locking is limited to parts, with locked files set to read-only and treated as inspection only to avoid conflicts. It also demonstrates how to adjust auto-lock behavior by creating a config.ini in the hidden AP folder to disable auto-logging paths like *.ldsm, and notes that reverting a commit requires closing loaded SOLIDWORKS documents, not the application itself.