Managing KiCad revision history without breaking project links

The Git Trap in KiCad Revision Control

Software developers solved revision control decades ago. Hardware maintainers are still stuck emailing zip files named board_v2_final_final.kicad_pcb. When you rename project files to track revisions in KiCad, you break internal project references, relative footprint libraries, and shared web links. ECAD version tracking requires a different approach than simple file renaming.

Stop Renaming KiCad Files for Version Tracking

KiCad source files are plain text. A .kicad_sch file or a .kicad_pcb file relies on stable file names to keep project dependencies intact. Renaming a project file every time you rev a board creates a trail of broken links. It breaks symbols, unlinks footprints, and forces teammates to re-associate files manually.

Hardware versioning works best when file names stay constant across every commit. The root file should always keep its base name. Revisions belong in git commits, release tags, and repo hosting platforms, not in file names.

When you push clean KiCad source files to a hardware host like BoardRepo, the platform preserves your project structure across every revision. External reviewers can open a single web link to inspect the board. They do not need to install local CAD desktop tools or uncompress zips. Every commit tracks version history cleanly while keeping project file links permanent.

Synchronizing BOM Changes Across Board Revisions

Schematic revisions naturally trigger bill-of-materials changes. Replacing an obsolete component changes your BOM lines, component footprints, and copper routing simultaneously.

In a broken workflow, schematic changes live in git while the BOM sits in an unversioned spreadsheet on a local drive. This disconnect creates procurement errors. A manufacturer builds revision B using revision A's spreadsheet because nobody updated the shared file link.

BoardRepo extracts and displays the BOM directly from hosted KiCad files for every revision. When you push a new version, the browser view updates the interactive 3D render, schematic, PCB copper layers, and bill of materials in one place. Anyone opening the web link sees the exact component list associated with that specific revision tag.

Maintaining Permanent Shareable Links for Reviewers

Design reviews fall apart when stakeholders look at different board revisions. Supplying direct web links solves this breakdown. Instead of generating static PDF exports or emailing Gerber archives, maintainers send a link to the hosted repository.

BoardRepo gives every hosted board a persistent URL that renders the schematic, PCB copper, 3D model, and BOM in the browser without software installation. Non-designer stakeholders can inspect the layout and verify component availability without touching KiCad.

This workflow aligns with how to run asynchronous PCB design reviews in the browser. Maintainers post the link, reviewers inspect the rendered CAD layers, and everyone operates on the exact same commit history.

Querying Hardware Revisions with MCP

As revision histories grow, searching across old commits becomes tedious. Finding which past revision used a specific pinout or controller chip usually requires opening multiple CAD sessions locally.

BoardRepo includes an MCP server integration that connects AI assistants directly to hosted KiCad and Altium projects. Maintainers can query project files using natural language to locate specific parts or reference designs across repos. If you want to configure automated lookups for your repositories, see our guide on how to connect AI assistants to hardware repos using MCP.

Trade-offs and Practical Limits

No workflow is entirely frictionless. Git handles plain text KiCad schematic and PCB files well, but binary assets like heavy STEP models or custom visual assets bloat repositories quickly.

Furthermore, web-based rendering does not replace local layout work. Maintainers still need local KiCad or Altium installations for routing and thermal analysis. What hosted repos solve is distribution, inspection, and revision tracking. By separating local design work from browser-based review links, hardware teams keep project files clean, avoid broken links, and keep BOMs perfectly in sync across every revision.