SwarmCraft
Getting StartedGuide

Docs

Set up a git repository

Prepare a repository SwarmCraft can work against so the VS Code extension, packet files, and review flow all have a stable home.

Set up a git repository

Before you connect SwarmCraft to a project, make sure the code lives in a repository your team can clone, review, and deploy from.

GitHub, GitLab, Bitbucket, and similar platforms all work. The important part is not the brand. The important part is that the repository is ready for a normal delivery workflow.

Minimum setup

Your repository should have:

  • a default branch your team protects and reviews against
  • a clear README or project brief
  • a .gitignore that keeps secrets, build output, and local state out of version control
  • a local clone on the machine where you will run VS Code and the SwarmCraft extension

Why this matters for SwarmCraft

The extension writes packet files into your selected workspace under .swarmcraft/projects/. Those packet files are part of the working delivery loop, so they belong in the same repository as the code you are changing.

Good practice

Create the repository before discovery becomes implementation work. That way the board, packets, diffs, and deployment changes all have one shared history.

When the repository is ready, move to Download VS Code and install SwarmCraft.