Environment History¶
Each ComfyGit environment is a Git repository. Commits are environment snapshots: manifest changes, workflow files, model metadata, node metadata, and workflow contract artifacts.
Model bytes and runtime directories are not committed.
Check Status¶
Use verbose status for more detail:
Commit Changes¶
Before committing, ComfyGit checks the environment for unresolved workflow, model, and reproducibility issues.
If you deliberately need to commit with issues:
View History¶
Branch And Switch¶
Create and switch in one command:
After switching, ComfyGit reconciles the runtime toward the checked-out manifest.
Explore Older State¶
Return to a branch:
Undo Changes¶
Create a new commit that undoes an older commit:
Move the current branch pointer while keeping changes in the working tree:
Discard local changes only when you really mean it:
Merge¶
Preview a merge:
Merge a branch:
Push And Pull¶
Remote collaboration is covered in Git remotes.
Quick example:
Repairing Environments¶
If a branch switch, pull, reset, or manual filesystem edit leaves the runtime in an inconsistent state, repair the environment from the tracked manifest:
For more detail, see Sync and repair.
What Git Tracks¶
Git tracks portable environment truth:
pyproject.toml- workflow JSON files
- workflow API prompt artifacts
- shared overlays
- metadata needed to reinstall nodes and dependencies
Git does not track:
- model bytes
.venv- ComfyUI runtime checkout state
- local overlays
- caches
- logs