Git-backed projects
Suites are code, so WeftKit treats them like code. Every project can live in a git repository on your disk (the default), and the app covers the everyday operations — no terminal required, though the repository is a completely normal one if you prefer the terminal.
What the app can do
- Init — new projects start as repositories with an initial commit.
- Clone — create a project from an existing repository URL.
- Connect a remote — attach or replace the origin remote.
- Commit — stage and commit your changes with a message.
- Push / pull — sync with the remote; pull is fast-forward only, so the app never invents merges.
What stays out of the repo
A generated .gitignore keeps sensitive and heavy files out of version control. Suites and project configuration are committed; secrets and evidence are not:
.gitignore (generated)
# WeftKit — never commit secrets or heavy evidence
.replay-secrets.json
.provider-credentials.json
provider-ledger.jsonl
recordings/
runs/
exports/
profile/Commit is also guarded: if a staged path looks like a secret file, the commit is refused — belt and suspenders.
Authentication
Pushing over HTTPS uses a personal access token you store per project. Like every other secret, it goes into the OS credential vault — write-only from the UI, read only at push time, never written to disk or logs.
