Revision Management

Revision Management keeps a history of saved Workflow source so you can inspect changes, identify who made them, and restore earlier content without deleting history.

Open a Workflow's designer and select Manage revisions. The revision history can show timestamps, commit messages, users, content hashes, backing GitHub commits, and links that open a revision in a separate designer tab. Search can highlight or filter loaded revisions, and Fetch earlier loads older history.

To restore an earlier design, open that revision in the Test Environment, review and test it, then save it as a new latest revision. Promote the new revision through later Environments when Release Management is enabled.

How Revision Management relates to Release Management

When Release Management is disabled, saving stores and publishes the new revision in every Environment. When it is enabled, saving affects the first Environment and later Environments change only through promotion.

Using GitHub

When a Site uses GitHub, each Environment maps to a GitHub branch and revision records can link to GitHub commits. A direct GitHub change or merge updates source; confirm that the matching revision is also compiled and published in Flowgear before relying on it at runtime.

GitHub pull requests can be used to review and merge changes between Environment branches. GitHub backing is not recommended with Release Management disabled because each save must commit the Workflow to every Environment branch and can take several seconds.

The exact revision controls differ between Workflow designers. Use the reference documentation for the Workflow's runtime.
It is not reccommended that GitHub is used as the backing store when Release Management is disabled because this requires that the Workflow is committed to each branch (one per Environment). This generally means that a save will take several seconds to complete.