Versioning
Git-based history for apps and data
Every change to your apps is a commit. Full history, meaningful messages, and the ability to roll back to any previous version. It's like time travel for your code.
Capabilities
Git-Based Storage
Apps stored with isomorphic-git. Real commits, real history, real version control.
Commit History
See every change with timestamps and messages. Understand how your app evolved.
Rollback Support
Restore any previous version instantly. Undo mistakes without panic.
GitHub Export
Push your code to GitHub. Own your code, store it where you want.
Template Updates
When base templates improve, merge updates into your apps with 3-way merge.
Use Cases
Why It Matters
- Every change is a commit. Full auditability.
- Portable. Take your work wherever you need.
- Template updates bring improvements without breaking your customizations
How It Works
Versioning in Runwork treats your apps as proper software projects with full version control. Every change you make—whether through the Work Assistant or direct code editing—becomes a Git commit with a timestamp, message, and complete diff of what changed.
This history isn't just for show. You can browse the entire evolution of your app: see how it started, what changed along the way, and why each modification was made. When something breaks, identify the exact change that caused the problem. When you need to understand a decision, the commit history tells the story.
Rollback support means mistakes are never permanent. If a change breaks functionality, roll back to any previous version instantly. The entire app state—code, configuration, and structure—reverts to how it was at that point in time. This gives you confidence to experiment knowing you can always return to a working state.
GitHub export extends this further. Push your app's code to your own GitHub repository for additional backup, code review workflows, or collaboration with external developers. Your code isn't locked into Runwork—you own it completely and can take it wherever you need.
Template updates showcase the power of Git-based versioning. When Runwork improves base templates (security patches, new capabilities, UI improvements), those updates can be merged into your apps using 3-way merge. Your customizations are preserved while you receive the improvements—just like updating a dependency in traditional development. Deployments then push your updated app live.