Revision Management

Revision Management allows users to review historical revisions of a Workflow.

Each time a Workflow is saved, a new revision is generated and the historical revision is stored.

You can view a list of revisions of a Workflow from the Workflow Design Pane by clicking the Revision History button.

To see the design of a prior revision of a Workflow, click the Open link against the revision. If you'd like to roll back to that revision, you can save the Workflow which will cause a new revision to be created as the latest revision for the Test Environment.

When Release Management is not enabled, saving a Workflow stores the new revision in all Environments. When Release Management is enabled, the revision is stored only in th Test Environment and you'll be able to explicitly promote the Workflow into other Environments when you are ready.

Using GitHub

When a Site is configured to use GitHub as its backing store, Workflows are stored directly in GitHub and the revision number is a GitHub commit hash.

In this mode, each Environment maps to a specific GitHub branch which means you can use use GitHub Pull Requests so that merging changes from one branch to another in GitHub promotes them from one Environment to another in Flowgear.

See Version Control under Site Detail Pane for more information about configuring GitHub as your backing store.

Note that we do not recommend using GitHub as your backing store when you have Release Management 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.