That's a good question. Instead of tracking the actual sketch files (or binaries) in git, Kactus transforms your sketch file into groups of individual text files – one for each layer/page – that are much more suited for
git to work with.
The basic workflow looks very similar to how many developers use
However, when working with multiple designers, the git-flow methodology works very well:
When Kactus is running (with your repository open), it watches your sketch files and re-parses them when a change is detected. This parsed (or exploded) view of your sketch file is what git tracks.
If your sketch files are already tracked in a git repository, there are few things you need to do to get the most out of Kactus.
git rm --cached *.sketch
*.sketchto your repo's
.gitignorefile (create it if it doesn't exist)
Note: When you create a new repository with Kactus, it is automatically configured to ignore sketch files.