Branching
Isolate feature work and experiments until they are ready to merge into main.
GoRules Version 2 is here - redesigned, now with managed cloud.GoRules Version 2 is here!
Watch the launch videoWatchBranches, commits, diffs, and instant rollback - a git-grade history for the people who own the rules, no git required. Never lose work, always know who changed what.
Analysts see drafts, history, and visual diffs. Underneath it's real branches and commits - every change isolated until it's merged, every merge attributable.
Everything engineering expects from version control, built into the rule editor for people who never open a terminal.
Isolate feature work and experiments until they are ready to merge into main.
Every change lands as a commit with a message, author, and timestamp.
Merge through change requests with reviews, so nothing reaches main unchecked.
See exactly what changed between any two versions - additions, deletions, edits.
Browse the full history and roll back to any previous version instantly.
Tag versions as releases and track which one runs in each environment.
A familiar path for every change, whether it comes from an analyst, an engineer, or GoRules AI - releases always stay with your reviewers.
Start from main and work in isolation.
Edit tables and graphs with the full editor.
Reviewers see the diff and sign off.
Merge to main and promote through environments.
Version control is what turns a rule editor into a system of record.
Changes are tested in isolation before they can touch production.
Several people work on the same rules without stepping on each other.
The complete history satisfies regulators - who, what, when, and why.
Start free on GoRules Cloud and bring real version control to the rules your business runs on.